You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Comparison reports could describe a controller takeover that was absent from the immutable attempt's intervention list, leaving publication validity unsupported.
What
Require a separately captured controller-intervention ledger when retaining an execution attempt and reject retention unless it exactly matches the attempt. The comparison procedure now records takeovers immediately and derives its visible summary from that ledger.
How to test
Run npm test -- src/dev/execution-comparison/__tests__/artifact-contract.test.ts and confirm a mismatched ledger is rejected.
Run npm test -- src/dev/execution-comparison/__tests__/operator-cli.test.ts and confirm attempt retention requires the ledger.
This stack of pull requests is managed by Graphite. Learn more about stacking.
kostandinang
changed the title
FE-1267: Record comparison controller takeovers
FE-1267: Record controller takeovers in comparison evidence
Jul 24, 2026
Low Risk
Scoped to dev execution-comparison tooling and operator prompts; tightens evidence validation without changing product runtime behavior.
Overview
Closes a gap where comparison reports could describe controller takeovers that were not reflected in immutable attempt evidence.
Procedure:compare-execution.md now requires logging every controller takeover immediately to <attempt-staging>/intervention-ledger.json (schema version 1, mechanical interventions with index/kind/description/timestamp). Visible-interaction summaries must come from that ledger; unledgered takeovers are not allowed.
Retention:retain-attempt gains a required --intervention-ledger flag. Before writing an attempt, the operator loads the ledger and runs assertExecutionAttemptInterventionLedger, which rejects invalid ledgers or any mismatch with the attempt’s interventions list.
Contract: Adds ExecutionInterventionLedger and assertExecutionAttemptInterventionLedger in artifact-contract.ts, plus unit/CLI tests for mismatch rejection and the missing-flag error.
Reviewed by Cursor Bugbot for commit c55f286. Bugbot is set up for automated code reviews on this repo. Configure here.
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
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.
Why
Comparison reports could describe a controller takeover that was absent from the immutable attempt's intervention list, leaving publication validity unsupported.
What
Require a separately captured controller-intervention ledger when retaining an execution attempt and reject retention unless it exactly matches the attempt. The comparison procedure now records takeovers immediately and derives its visible summary from that ledger.
How to test
npm test -- src/dev/execution-comparison/__tests__/artifact-contract.test.tsand confirm a mismatched ledger is rejected.npm test -- src/dev/execution-comparison/__tests__/operator-cli.test.tsand confirm attempt retention requires the ledger.