Skip to content

Expose exact typed result recovery evidence - #703

Merged
flyingrobots merged 4 commits into
mainfrom
task/702-expose-typed-result-recovery-evidence
Jul 29, 2026
Merged

Expose exact typed result recovery evidence#703
flyingrobots merged 4 commits into
mainfrom
task/702-expose-typed-result-recovery-evidence

Conversation

@flyingrobots

Copy link
Copy Markdown
Owner

Exposes complete schema-neutral application-result records from applied execution, fresh-host recovery, and recovered WAL state through one fail-closed equality gate. Adds negative substitution coverage and the external three-way comparison contract.

Validation: xtask 132/132; generic runner 9/9; affected Clippy, formatting, documentation, and pre-push checks green.

Closes #702.

@flyingrobots

Copy link
Copy Markdown
Owner Author

@coderabbitai review

@flyingrobots

Copy link
Copy Markdown
Owner Author

@codex please review

@coderabbitai

coderabbitai Bot commented Jul 29, 2026

Copy link
Copy Markdown
Contributor
✅ Action performed

Review finished.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

@coderabbitai

coderabbitai Bot commented Jul 29, 2026

Copy link
Copy Markdown
Contributor

Warning

Review limit reached

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

Next review available in: 5 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

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 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 configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: cc0639e6-2ca9-46e5-8fe8-148cc4eb024b

📥 Commits

Reviewing files that changed from the base of the PR and between 28d7a0f and 423f9a1.

📒 Files selected for processing (5)
  • CHANGELOG.md
  • README.md
  • docs/topics/GeneratedRules.md
  • xtask/src/run_edict_operation.rs
  • xtask/tests/run_edict_operation.rs

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

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

@chatgpt-codex-connector

Copy link
Copy Markdown

Codex Review: Didn't find any major issues. Another round soon, please!

Reviewed commit: 423f9a16c5

ℹ️ 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".

@flyingrobots

Copy link
Copy Markdown
Owner Author

Merge gate: current head 423f9a1 is clean locally; every reported check passed; Codex found no major issues; CodeRabbit completed with an explicit rate-limit response; zero review threads are unresolved. The repository is solo-maintained and the available review metadata cannot supply an independent human approval, so criteria 1–4 substitute for human approval under the recorded operator authorization.

@flyingrobots
flyingrobots merged commit c03061b into main Jul 29, 2026
40 checks passed
@flyingrobots
flyingrobots deleted the task/702-expose-typed-result-recovery-evidence branch July 29, 2026 20:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Expose independently comparable typed result recovery evidence

1 participant