Ground workflow progress in controller state - #436
Merged
Conversation
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars. ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Advanced Run ID: 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 |
Wibias
marked this pull request as ready for review
September 9, 2026 06:00
This was referenced Sep 9, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Hardens workflow-state grounding from the Grok delivery trace:
nextActioninstead of requiring the model to reconstruct progress from history;refscommand that could inject caller-authored repository identity state;showoutput so stale or model-authorednextActiondata cannot regain authority after resume.Legacy checkpoints do not receive fabricated historical phase receipts. Missing receipts remain missing; only current actionable state is re-derived from trusted checkpoint fields.
Regression evidence
RED-first coverage reproduced the missing state-grounding behaviour and the public ref-injection path. A later RED compatibility test reproduced stale guidance surviving through old checkpoint resume. Both resume paths now normalise through the controller.
Verification
Exact head:
d8cf9e21d5d22b57c6cace9eafe063fa9005cef6Scope
Workflow state grounding only. Evidence integrity, publication reliability, and trace diagnostics are isolated in #434, #435, and #437.
Ready for review. Do not merge without explicit instruction.