GitHub-Backed Happy Path

Use this flow when the task authority is a structured GitHub task issue or sub-issue.

First run

wap-flow install-hooks
wap-flow create-sub-issue --repo <owner/name> --parent <number> --title "<title>" --type Implementation --spec <path>
wap-flow issue-branch --issue <number>
wap-flow start --issue <number> --spec <path>
wap-flow plan record --summary "<summary>" --step "<step>" --step "<step>"
wap-flow check
wap-flow inspect issue
wap-flow complete --evidence "<what passed>"

Closeout

1. Open or bind the PR if the task is on a PR surface: wap-flow pr open --issue <number> If the PR already exists or was created before local state was written, rerun the same command to bind it. Use wap-flow pr refresh --issue <number> [--base <ref>] after external PR edits, and wap-flow pr draft|ready --issue <number> for draft/ready transitions.
2. Initialize the acceptance profile: wap-flow accept init --preset <name> --profile <name> --surface issue|pr [--pr <number>]
3. Run the review loop from flow/playbooks/acceptance-review-loop.md.
4. Finalize only after accept check --strict is clean: wap-flow accept finalize This is the step that records the task as accepted/finalized. It closes the GitHub task issue only when the active profile allows GitHub closeout.
5. If the PR is merged, reconcile the task issue: wap-flow pr reconcile --strict

Common guardrails

• start requires the branch name to contain issue-<number>.
• plan record must run before tracked edits on guarded work.
• accept works here for GitHub-backed closeout; pr remains GitHub-backed only in v1.