fix: resume Main result follow-up within stored mandate #86
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "fix/main-result-followup"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Scope
Restore Main result-derived delegation and explicit/automatic continuation only within the stored original operator mandate. Preserve worker, permission, approval and review gates. Nine files; no reviewer-infrastructure changes or deployment.
Verification
711df0daf2e905d2c4692ffcf35a3da086b62a3308b231e91ed830b60f1f5b45againstc906195f0e577413af5301d5f95c48388fdb9da4; committed file hashes verified unchanged.result-delegation-depth-not-consumed: repeated result-to-dispatch hops preserve depth instead of consuming it. Explicitly retained as follow-up; no P0/P1. No review-budget reset or extra review churn.Interruption reconciliation
Both prior workers remain BLOCKED with unsafe intents and no tokens. Completed old tool calls and remote refs/PRs showed no prior publication for either candidate. This commit/push is the first publication. Separate reviewer candidate, all other worktrees and stash e7e8814 remain untouched.
Server CI: Actions runs and commit statuses empty on baseline; branch protection settings endpoint denied (403). Normal server merge policy must apply, no force/admin bypass.