Add retained evidence boundary posture#648
Conversation
|
Warning Review limit reached
Next review available in: 23 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Pro Run ID: 📒 Files selected for processing (2)
📝 WalkthroughWalkthroughAdds public retained-evidence posture facets and ChangesRetained evidence posture
Estimated code review effort: 4 (Complex) | ~45 minutes Possibly related PRs
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 177031fec5
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
|
@codex Code Lawyer audit for PR #648, commit
No additional Markdown, export-surface, formatting, or whitespace violations found in this pass. CI is green, but merge remains locked until these two invariant leaks are fixed or explicitly waived. |
Summary
Testing
Committed changes on the current branch with commit |
Activity Summary — Code Lawyer Execution
Validation:
@codex please confirm the two retained-evidence boundary invariant fixes are now structurally sound. |
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@crates/warp-core/tests/retained_evidence_ref_tests.rs`:
- Around line 513-515: Rename the local variable `content_hash` in
`retained_content_hash_does_not_identify_semantic_evidence` to a distinct name,
such as `retained_hash`, and update all references within the test while keeping
the `content_hash(...)` helper unshadowed.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: ASSERTIVE
Plan: Pro
Run ID: c333ec80-8c97-49f7-9154-d2288ef4511a
📒 Files selected for processing (4)
CHANGELOG.mdcrates/warp-core/src/lib.rscrates/warp-core/src/retained_evidence.rscrates/warp-core/tests/retained_evidence_ref_tests.rs
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: d57e2df022
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
Activity Summary — Follow-up Review Threads
Validation:
@codex please re-check PR #648 for any remaining retained-evidence boundary invariant or test-style issues. |
|
Codex Review: Didn't find any major issues. Breezy! Reviewed commit: ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
If Codex has suggestions, it will comment; otherwise it will react with 👍. Codex can also answer questions or update the PR. Try commenting "@codex address that feedback". |
Summary
RetainedEvidenceBoundaryPostureas the observer-facing posture surface above local retained byte references.Validation
cargo test -p warp-core --test retained_evidence_ref_testscargo checkcargo fmt --all -- --checkgit diff --checkcargo clippy -p warp-core --lib,cargo check -p warp-core, markdownlintcargo fmt --all -- --check,cargo test -p warp-core --lib,cargo check -p warp-core --quiet,cargo test -p warp-core --test retained_evidence_ref_tests, Prettier markdown checkSummary by CodeRabbit
New Features
Bug Fixes
Tests
Documentation