feat(core): add causal WAL foundation and hardening#378
Conversation
|
Warning Review limit reached
Your plan includes 1 review of capacity. Refill in 48 minutes and 16 seconds. Your organization has run out of usage credits. Purchase more in the billing tab. ⌛ How to resolve this issue?After more review capacity refills, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than trial, open-source, and free plans. In all cases, review capacity refills continuously over time. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Pro Run ID: 📒 Files selected for processing (20)
✨ 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: e7bd734121
ℹ️ 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 self-audit found the following blocking issues before merge:
I am addressing these now with focused tests, fixes, verification, and a follow-up commit. |
Summary
PR / Commit
Testing
|
|
@codex Self-audit addendum before pushing fixes:
|
Summary
Commit / PR
Testing
|
|
@codex Activity Summary for PR #378 feedback pass:
Validation run before push:
Resolved the review thread for the stale WAL doctor behavior after pushing |
|
Understood — based on the trigger and PR context, there are no additional code follow-ups required from me right now. The activity summary indicates the blocking items were already addressed in commit I also checked the branch state locally: Testing / Checks
I did not make any new repository changes, so I did not create a commit and did not call |
Summary
This PR adds Echo's causal WAL foundation and hardening surface through the first runtime ACK integration cut.
Highlights:
submit_intent_with_runtime_wal_ack(...)commits submission acceptance evidence before returning, backfills exactly one WAL record for legacy duplicate retries, reports missing WAL explicitly, and rolls back intake on pre-ACK WAL failure;docs/BEARING.mdanddocs/design/causal-wal-hardening-matrix.md.Current Slice Progress
Validation
cargo test -p warp-core --features native_rule_bootstrap,trusted_runtime,host_test --test trusted_runtime_host_loop_testscargo clippy -p warp-core --features native_rule_bootstrap,trusted_runtime,host_test --test trusted_runtime_host_loop_tests -- -D warningscargo test -p warp-core --test causal_wal_testscargo test -p warp-core --test causal_wal_hardening_testscargo check -p warp-corescripts/check-no-app-nouns-in-core.shpnpm exec markdownlint-cli2 docs/BEARING.md docs/design/causal-wal-hardening-matrix.mdgit diff --checkPre-push also ran exact configured slices and passed.
Next PR Boundary
The next PR should continue Runtime WAL ACK Integration with scheduler/tick receipt publication: