Story
As a user, I want the complete adversarial implementation loop to run under explicit supervision, so I retain product authority while deterministic XMD components own operational effects.
Scope
Compose the root workflow through discovery, handoff validation, planning convergence, authorization, read-only Agent implementation proposals, constrained generated XMD, local Git effects, explicit Push, PullRequest review, deferred Issue creation, revision, and final acceptance.
The user starts or resumes the WorkflowRun through #366. Each execution rehydrates the same retained Workspace through #291/#365 and uses the lifecycle in #367. This issue composes capabilities; it does not implement its own persistence, Git, Agent authority, or provider replay policy.
Do not add file-watcher or unattended arbitration here.
Acceptance
- One supervised WorkflowRun reaches final acceptance across process interruption.
- Failed plan and pull-request verdicts return prescriptive prompts to the responsible retained Agent context.
- Material choices suspend for user authority and never default to approval.
- Agents remain read-only; admitted generated XMD performs every Workspace mutation.
- Two repositories can participate through explicit named Repository/Worktree composition.
- Commit, Push, PullRequest, and deferred Issue remain distinct durable or reconciled effects.
- Every declared artifact and effect result is available to a later execution without manual copy/paste or hidden transcript state.
- Failure and cancellation halt live resources while retaining explicit recoverable or terminal state.
Dependencies
Story
As a user, I want the complete adversarial implementation loop to run under explicit supervision, so I retain product authority while deterministic XMD components own operational effects.
Scope
Compose the root workflow through discovery, handoff validation, planning convergence, authorization, read-only Agent implementation proposals, constrained generated XMD, local Git effects, explicit Push, PullRequest review, deferred Issue creation, revision, and final acceptance.
The user starts or resumes the WorkflowRun through #366. Each execution rehydrates the same retained Workspace through #291/#365 and uses the lifecycle in #367. This issue composes capabilities; it does not implement its own persistence, Git, Agent authority, or provider replay policy.
Do not add file-watcher or unattended arbitration here.
Acceptance
Dependencies