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.3 KiB
1.3 KiB
Create-issue controller handoff schema
Task mode: create-issue
End every create-issue 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.
Do not use legacy fields: Workspace mutations, Mutations: None (when
mutations occurred).
## Controller Handoff
- Task:
- Repo:
- Role:
- Identity:
- Active profile:
- Runtime context:
- Requested issue task:
- Workflow source:
- Capability proof:
- Duplicate search terms:
- Duplicate search pagination proof:
- Duplicates found:
- Issues created:
- Issues commented:
- Issues edited:
- Issues skipped as duplicates:
- Labels/assignees/milestones changed:
- File edits by issue creator:
- Worktree/index mutations:
- Git ref mutations:
- MCP/Gitea mutations:
- Issue mutations:
- Label/assignment/milestone mutations:
- External-state mutations:
- Read-only diagnostics:
- Blockers:
- Current status:
- Safe next action:
- Safety statement:
Identity format: username / profile (not personal email unless required — #305).
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 thread.