jcwalker3andClaude Opus 4.8
ddc9b97d40
Adds the canonical cross-role handoff schema and its fail-closed validator, live-state recovery, role-limited continuation, mandatory durable posting, the merged-awaiting-controller boundary, controller accept/reject continuation, and workflow-failure escalation with duplicate handling. Co-Authored-By: Claude Opus 4.8 (1M context) <[email protected]>
1.5 KiB
1.5 KiB
Reconcile-landed controller handoff schema
Task mode: reconcile-landed-pr
End every reconciliation run with a section titled exactly Controller Handoff.
Use this canonical field set. Do not omit fields — use none or
not verified in this session where appropriate.
Reject stale author/reviewer fields: PR number opened, Pinned reviewed head,
Scratch worktree used, Workspace mutations, Mutations: None (when mutations
occurred).
## Controller Handoff
- Task:
- Repo:
- Role:
- Identity:
- Active profile:
- Runtime context:
- Selected PR:
- PR live state:
- Candidate head SHA:
- Target branch:
- Target branch SHA:
- Ancestor proof:
- Linked issue:
- Linked issue live status:
- Eligibility class:
- Capabilities proven:
- Missing capabilities:
- PR comments posted:
- Issue comments posted:
- PRs closed:
- Issues closed:
- File edits by reconciler:
- Worktree/index mutations:
- Git ref mutations:
- MCP/Gitea mutations:
- Reconciliation mutations:
- External-state mutations:
- Read-only diagnostics:
- Blockers:
- Current status:
- Safe next action:
- Safety statement:
- No review/merge confirmation:
Identity format: username / profile (not personal email unless required — #305).
git fetch belongs under Git ref mutations, not read-only diagnostics (#297).
The report must also carry the canonical self-propagating handoff block
(schemas/self-propagating-handoff.md, #626) and that block must be posted to
the Gitea issue or PR thread.