Lock retained material WAL ordering

[flyingrobots]

Summary

• add retained-material WAL ordering witnesses for crash-before-WAL and crash-after-WAL recovery boundaries
• lock typed retained-material loss scopes across submission, receipt/ticket, runtime-global, reading, and diagnostic material
• document the fast local witness path by validating the containing integration test binary directly

Closes #571.

Validation

• cargo test -p warp-core --test causal_wal_tests retained_material_wal_commit_order
• cargo clippy -p warp-core --test causal_wal_tests -- -D warnings
• cargo fmt --check
• git diff --check
• pre-commit: cargo clippy -p warp-core --lib; cargo check -p warp-core
• pre-push: cargo fmt --all -- --check; cargo test -p warp-core --test causal_wal_tests

Test speed note

• Avoid cargo test -p warp-core retained_material_wal_commit_order for local iteration: Cargo compiles unrelated warp-core integration binaries before applying the test-name filter.
• Use cargo test -p warp-core --test causal_wal_tests retained_material_wal_commit_order for the same witness; warm run completed in 0.17s locally.

[coderabbitai]

Warning

Review limit reached

@flyingrobots, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 23 minutes and 7 seconds. Learn how PR review limits work.

Your organization has run out of usage credits. Purchase more credits in the billing tab to continue.

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

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 credits.

🚦 How do rate 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 see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

Run ID: 8b2a2638-6e2f-40c1-8bb0-1a2afe8261d9

📥 Commits

Reviewing files that changed from the base of the PR and between a7d4b1c and 674bf66.

📒 Files selected for processing (1)

• crates/warp-core/tests/causal_wal_tests.rs

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch cycle/571-retained-material-wal-ordering

---

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.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[flyingrobots]

Code Lawyer update

Issue	Resolution	Resolving commit
No unresolved review threads	GraphQL review-thread scan returned zero threads; PR is non-draft and mergeable.	674bf664
CI/check suite	All GitHub checks are passing, including clippy lanes, tests, determinism guards, DIND PR set, rustdoc, audit, and CodeRabbit status.	674bf664
CodeRabbit review availability	CodeRabbit posted a rate-limit/credits warning instead of actionable findings; this is treated as clean under the approved workflow.	674bf664
Test-speed concern	PR body documents the fast witness command: cargo test -p warp-core --test causal_wal_tests retained_material_wal_commit_order; the broad package-filter form was avoided because it compiles unrelated integration binaries.	674bf664