goop-accept

/goop-accept

Run the verification-to-archive lifecycle. The milestone is not complete until the user explicitly accepts.

Gate check

Call goop_state({ action: "get" }). If allWavesComplete is not true or blockers exist, return BLOCKED with:

Run /goop-execute first.

Load references

goop_reference({ name: "phase-gates" })
goop_reference({ name: "security-checklist" })

Steps

1. Read goop_read_db({ doc_types: ["spec", "blueprint", "chronicle"] }) for non-wave planning context and progress log; read wave/task/verification context via goop_acceptance_audit (which wraps goop_read_wave).

2. Spawn goop-verifier to check must-have coverage, artifacts, key links, and quality.

3. Spawn goop-tester for full test and build verification (top-rung, full-suite context).

4. Present a verification matrix. Require explicit user acceptance.

5. PR summary and merge offer — enumerate all open PRs for this workflow. Run gh pr list --json number,title,url,baseRefName filtered to the workflow's wave branches. Present them as a numbered list in merge order, newest-first (highest-numbered wave first, cascading down to Wave 1): PR number, title, URL, and target base branch. Then ask in plain text (NOT the question tool):

   All verifications passed. Want me to merge these PRs in order? (Yes / No — I'll do it myself)

   This is the one place lazy autopilot stops for a literal user reply, because merging is irreversible. Wait for the user's answer before proceeding.

6. On acceptance:

   • Copy workflow docs to .goopspec/archive/<workflowId>-<timestamp>/.
   • Verify the copy before deleting originals.
   • Generate RETROSPECTIVE.md and extract learnings to memory.
   • Optionally tag git.
   • Update AGENTS.md with verified learnings where appropriate.

7. On rejection or issues, return to /goop-execute or /goop-amend.

Auto-merge sequence

If the user replies Yes to the merge offer:

1. Merge newest-first cascade — merge the highest-numbered wave's PR into the next-lower wave's branch first (e.g. Wave 3 into Wave 2), then that branch's PR (now carrying the merged work) into the wave below it, and so on, until Wave 1 — whose PR already targets main — merges last, landing the entire stack on main in one final step. For each merge: run gh pr merge <number> --merge --delete-branch. --merge (merge commit) is GoopSpec's default merge method and preserves per-wave commit history; do not substitute --squash unless a human explicitly overrides.
2. Log each merge — append a brief entry via goop_append_chronicle after each successful merge.
3. Failure handling — if any merge fails (conflict, CI failure, protected branch): stop immediately and report which PR failed and the reason. Leave all remaining PRs open. Never force-merge. Return to the user for resolution.
4. Post-merge sync — after all PRs are merged: run git checkout main && git pull to sync locally. Confirm the final commit is on main and report its hash. Remote branches are deleted via --delete-branch; do not delete local branches — that is the user's responsibility.