@ngockhoale/ukit 2.0.7 → 2.1.2

package/templates/.claude/commands/ukit/handoff-fullstack.md

@@ -22,6 +22,66 @@ $ARGUMENTS
 
 ---
 
+## Autonomy Contract — read before anything else
+
+This command is a **one-shot pipeline**. The human is not watching. Treat every phase below
+as unattended: they may walk away after submitting `$ARGUMENTS` and come back to a finished
+result.
+
+**The single question window is P0, before any file is written.** If `$ARGUMENTS` leaves a
+choice that would change what gets built — not how it gets built — batch every such question
+into **one** `AskUserQuestion` call (max 4 questions, each with a `(Recommended)` first
+option) and resolve them all at once. Record the answers in `PLAN.md` §1.
+
+**After P0 closes, do not ask the human anything until the Final Report.** Every decision
+point in the phases below has a defined automatic resolution. Take it. Specifically:
+
+| Situation | Old behavior | Required behavior now |
+|-----------|--------------|----------------------|
+| Scope spans multiple subsystems | wait for confirmation | decompose into sequential cycles, run cycle 1 now, queue the rest in `INDEX.md` |
+| Plan review returns `Issues Found` | up to 3 rounds, then stop | 1 revision round; if round 2 still has findings, apply them and proceed — log to `## Plan Review Log` |
+| Two same-wave tasks share a file | STOP | move the later task to the next wave (add the dependency), continue |
+| INDEX has `pending_review`/`blocked` tasks | STOP | **resume** — see Resume below |
+| Reviewer returns `changes_requested`/`critical_block` | report and stop | run the Phase 4 auto-fix loop (max 2 rounds) |
+| Verification command fails | stop | fix and re-verify inside the auto-fix loop |
+
+Escalate to the human **only** for: a blocker outside the repo (missing credential, external
+service down), or a task still failing after both auto-fix rounds. Even then, finish every
+other task first and report what was left undone.
+
+**Never pause to ask for `/compact`.** Context is managed structurally — subagents write full
+logs to disk and return short summaries (see 3b), and the run cursor makes the pipeline
+resumable. If compaction does happen, the run resumes from the cursor automatically.
+
+### Run cursor — write after every step
+
+Maintain `docs/AI_HANDOFF/RUN.md`. Rewrite it (whole file, 6 lines) immediately after every
+numbered step completes:
+
+```
+Command: handoff-fullstack
+Goal: <one sentence from $ARGUMENTS>
+Base: <BASE branch>
+Phase: <P1|P2|P2.5|P3|I1|I2|I3|I4|R1|R2|R3|R4|R5|done>
+Cursor: wave <N> batch <M> — <what just finished>
+Next: <the exact next step to run>
+```
+
+This file is the resume contract. It costs one small write per step and is what turns an
+interrupted run into a continuable one.
+
+### Resume — when the run is re-invoked mid-flight
+
+If `docs/AI_HANDOFF/RUN.md` exists with `Phase:` not `done`, this is a **continuation, not a
+new cycle**. Do NOT re-plan, do NOT overwrite `PLAN.md`, do NOT ask the human whether to
+continue. Read the cursor, then jump straight to `Next:` and carry on. Tasks already `done`
+or `pending_review` are skipped; only `ready`, `in_progress`, `changes_requested` and
+`blocked` tasks are picked up.
+
+Only when `RUN.md` is absent or `Phase: done` does `$ARGUMENTS` start a fresh cycle.
+
+---
+
 ## Phase 1+2 — Plan (strong model)
 
 ### P1 — Read context (lite model)
@@ -45,7 +105,7 @@ The planner agent does the following (use P1 summary — do NOT re-read files):
 
 1. **Guard — check INDEX statuses:**
    - All tasks are `ready` (planning only) → re-run is allowed: overwrite `PLAN.md` and `TASK-xxx.md` freely (iterative refinement).
-   - Any task has status `pending_review`, `changes_requested`, `merge_conflict`, or `blocked` → **STOP**: warn the human — tasks are already in implement/review phase, cannot overwrite safely.
+   - Any task has status `pending_review`, `changes_requested`, `merge_conflict`, or `blocked` → **do not overwrite, and do not stop either.** Mid-flight work exists. Skip the rest of P2 entirely, write the run cursor with `Phase: I1`, and hand control back to the orchestrator to resume from Phase 3 with the surviving tasks (see Resume in the Autonomy Contract). Overwriting is what is unsafe here — stopping is not required.
    - No tasks → fresh cycle, proceed.
 
 2. **Resolve base branch:**
@@ -91,12 +151,19 @@ The planner agent does the following (use P1 summary — do NOT re-read files):
 
 ### P2.5 — Independent plan review (strong model, separate agent)
 
-**Loop cap — check first:** count `### Round` entries in PLAN.md's `## Plan Review Log` (0 if the section doesn't exist yet). If count ≥ 3 (3 prior rounds already returned `Issues Found`), do NOT invoke the reviewer again — STOP and escalate to the human: show the accumulated findings from all 3 rounds, ask them to manually revise PLAN.md, narrow scope, or explicitly approve an override. Otherwise, proceed below.
+**Loop cap — check first:** count `### Round` entries in PLAN.md's `## Plan Review Log` (0 if the section doesn't exist yet).
+
+- count = 0 → run the review below.
+- count = 1 and the round returned `Issues Found` → planner revises once, then run **one** more review round.
+- count ≥ 2 → do NOT invoke the reviewer again. **Do not stop and do not ask the human.** Have the planner apply every outstanding finding directly to `PLAN.md` and the affected `TASK-xxx.md` files, append `### Round <N> — findings applied without re-review` to the Plan Review Log listing what was changed, then proceed to P3.
+
+The gate still does its job — two independent opus passes shape the plan before a line of code
+is written. What it no longer does is hand a stalled plan back to a human who isn't there.
 
 **Claude Code — MANDATORY, do this before anything else in P2.5:** call the Agent tool with `subagent_type: "code-reviewer"`, passing `REVIEW_TARGET_TYPE=plan` and the path to `docs/AI_HANDOFF/PLAN.md`. This MUST be a separate agent invocation from P2's `handoff-planner` call (fresh context) — same-session self-review defeats the purpose of an independent gate.
 
 1. Reviewer reads `PLAN.md` only (no diff, no task files, no executor report), checks Completeness / Consistency / Clarity / Scope / YAGNI — see `.claude/agents/code-reviewer.md` → Spec/Plan Review — and appends its verdict to PLAN.md's `## Plan Review Log` (new round entry, prior rounds kept).
-2. `Issues Found` → route back to P2: `handoff-planner` revises `PLAN.md` and the affected `TASK-xxx.md` files to address every finding, then re-submit for another P2.5 review (this becomes the next round). Do NOT proceed to P3 on `Issues Found`.
+2. `Issues Found` → route back to P2: `handoff-planner` revises `PLAN.md` and the affected `TASK-xxx.md` files to address every finding, then re-submit for one more P2.5 review round — subject to the loop cap above.
 3. `Approved` → append `PLAN_REVIEW: Approved by <reviewer model>` to PLAN.md's `## Planner Report` footer, then proceed to P3.
 
 > Other tools without subagent support: manually switch to the strong model in a **separate** chat/session from P2, paste PLAN.md, review using the Spec/Plan Review checklist in `.claude/agents/code-reviewer.md`.
@@ -129,7 +196,11 @@ Verify working tree is clean after the plan commit:
 git status   # must be clean — plan commit already done in P3
 ```
 
-If working tree is dirty → stop. Ask human to resolve uncommitted changes first.
+If the working tree is dirty, do not stop. Commit the stragglers as a checkpoint so they stay
+recoverable and the wave copy-back starts from a known state:
+```bash
+git add -A && git commit -m "handoff: checkpoint before implement"
+```
 
 ### I2 — Infer wave groups
 
@@ -139,13 +210,17 @@ Read each `docs/AI_HANDOFF/tasks/TASK-xxx.md` for `Dependencies` field:
 - Chain A→B→C = 3 waves of 1 task each (sequential)
 - Independent A, B, C = 1 wave of 3 tasks (parallel)
 
-**Conflict check — mandatory, before spawning any wave.** For every pair of tasks landing
-in the same wave, compare their `Target Files` lists. If any file path appears in both,
-STOP — do not spawn that wave. This is the code-level safety net for the planner's own §2
-Scope constraint (same-wave tasks must not share a file) in case it slipped through
-review. Mark both conflicting tasks `needs_breakdown` in `INDEX.md` and report the
-conflicting file(s) to the human; do not resolve it yourself by reordering or guessing a
-dependency.
+**Conflict check — mandatory, before spawning any wave.** For every pair of tasks landing in
+the same wave, compare their `Target Files` lists. If any file path appears in both, **resolve
+it automatically — do not stop.** Keep the lower-numbered task in the current wave and push
+the other one into the next wave by adding `Dependencies: TASK-<lower>` to its task file. Two
+tasks that touch the same file are safe as long as they never run concurrently, and
+serializing them is the one resolution that is always correct. Note the demotion in the wave
+plan and in `RUN.md`.
+
+This is the code-level safety net for the planner's own §2 Scope constraint (same-wave tasks
+must not share a file) in case it slipped through review. Only mark a task `needs_breakdown`
+if it is missing required fields — never merely for sharing a file.
 
 **Batch each wave — mandatory.** Read `handoff.maxParallelAgents` from
 `.ukit/storage/config.json` (default **10**). A wave with more tasks than that is split
@@ -195,6 +270,20 @@ Executor Report (append to task file — do NOT touch INDEX.md):
   Verification Output: <paste full output>
   Status: PASS | FAIL
   Note: <issues or "none">
+
+Then RETURN TO THE ORCHESTRATOR AT MOST 10 LINES, in exactly this shape:
+  TASK: TASK-xxx
+  STATUS: PASS | FAIL
+  EXECUTOR_MODEL: <exact model ID>
+  FILES: <comma-separated changed paths>
+  RED: confirmed | not-confirmed
+  VERIFY: <n> commands, all pass | <first failing command + one-line reason>
+  NOTE: <one line or "none">
+
+Do NOT repeat RED_OUTPUT or verification logs in the returned message. They are already
+written to the task file on disk, which is where the reviewer reads them from. Pasting
+them back a second time is what blows up the orchestrator's context window and kills the
+run mid-pipeline.
 ```
 
 **3c — Copy changes back + delete worktrees** (orchestrator, after each task reports):
@@ -235,6 +324,36 @@ git branch -D handoff/task-xxx
 
 Worktrees are **always deleted immediately** — no exceptions.
 
+**3d — Wave boundary: commit + context checkpoint** (orchestrator, after every wave)
+
+A wave boundary is the only safe place to shed context, because everything of value is
+already on disk (task files hold the full logs, git holds the code). Do all four, in order:
+
+1. **Checkpoint the code** — one commit per wave, so every wave is independently revertible:
+   ```bash
+   git add -A && git commit -m "handoff: wave <N> — TASK-00x, TASK-00y"
+   ```
+   Do not push here; the single push happens at R5.
+
+2. **Update the run cursor** — rewrite `docs/AI_HANDOFF/RUN.md` with `Phase: I3`,
+   `Cursor: wave <N> done`, `Next: wave <N+1>` (or `I4` if that was the last wave).
+
+3. **Collapse the wave in working memory.** From this point on, refer to the finished wave
+   only by its one-line-per-task summary (`TASK-xxx PASS <files>`). Do not re-read the task
+   files, do not restate executor reports, do not quote diffs from earlier waves. Anything
+   the reviewer needs, the reviewer reads from disk itself.
+
+4. **Check the pressure before spawning the next wave.** If a UKit context warning has fired
+   this run, or the wave just finished involved more than ~5 agents, state one line —
+   `context checkpoint: wave <N> collapsed, <M> tasks summarized` — and continue anyway. Do
+   not ask the human to run `/compact`, and do not abandon the run. If the session is
+   compacted or restarted for any reason, `RUN.md` plus the `SessionStart` resume hook bring
+   the pipeline back exactly here.
+
+With a ~200k window and per-task returns capped at 10 lines (3b), a wave of 10 tasks costs
+the orchestrator roughly 100 lines instead of the thousands that pasted RED and verification
+logs used to cost. That difference is what makes a multi-wave cycle finish in one run.
+
 ### I4 — Consolidate + update INDEX (lite model)
 
 **Claude Code — MANDATORY:** call the Agent tool with `subagent_type: "ukit-small-task-maintainer"` for I4. After all waves complete, ask it to:
@@ -267,7 +386,13 @@ git status       # should show modified/new files, no handoff branches/worktrees
 git diff --stat  # summary of all changes
 ```
 
-If `git diff` is empty and `git status` is clean → implement was not completed. Stop and re-run Phase 3.
+Because 3d commits each wave, the changes under review are in **commits since the plan commit**, not only in the working tree. Resolve the review range once and use it everywhere below:
+```bash
+PLAN_COMMIT=$(git log --format=%H --grep='^handoff: plan' -n 1)
+git diff $PLAN_COMMIT   # all handoff changes: committed waves + anything uncommitted
+```
+
+If that diff is empty → implement was not completed. Do not stop: re-enter Phase 3 from the run cursor with the remaining `ready` tasks.
 
 > Orchestrator (this session) handles the R1 guard check directly.
 
@@ -297,8 +422,8 @@ If any command fails → verdict `critical_block`. Stop. Do NOT proceed to R4.
 ### R4 — Review unified diff + append verdict (strong model)
 
 ```bash
-git diff    # all uncommitted changes vs $BASE
-git status  # overview of modified/new/deleted files
+git diff $PLAN_COMMIT   # every handoff change: committed waves + working tree
+git status              # overview of modified/new/deleted files
 ```
 
 Review as one unified diff — correctness, regression risk, security, edge cases, maintainability. Cross-reference each task's intent in `docs/AI_HANDOFF/tasks/TASK-xxx.md`.
@@ -317,21 +442,70 @@ FINDINGS:
 NEXT_STATUS_FOR_INDEX: <status>
 ```
 
-### R5 — Commit + push or stop (orchestrator)
+Then return to the orchestrator **at most 6 lines** — the full verdict is already on disk:
+```
+TASK: TASK-xxx
+VERDICT: approved | approved_minor | changes_requested | critical_block
+REVIEWER_MODEL: <exact model ID>
+VERIFICATION_RERUN: PASS | FAIL
+BLOCKING: <one line per critical/important finding, or "none">
+```
+Do not paste the diff, the findings prose, or verification logs back into the orchestrator.
+
+### R4.5 — Auto-fix loop (max 2 rounds)
+
+Any task with `changes_requested` or `critical_block` enters this loop. **Do not report to
+the human and stop** — that is the single biggest reason a cycle used to stretch across days.
+
+For round in 1..2:
+
+1. Collect every task still not `approved`/`approved_minor`. If none, exit the loop.
+2. Group them into waves exactly as I2 does (dependencies + the same auto-serializing file
+   conflict rule). Spawn one `feature-implementer` per task **in parallel**, at most
+   `handoff.maxParallelAgents`, each in a fresh worktree per 3a. Each agent gets:
+   - the task file path (it reads its own `## Reviewer Verdict` from disk — do not paste
+     findings into the prompt),
+   - the instruction: fix every `critical` and `important` finding, leave `minor` alone
+     unless trivially safe, keep the existing tests green, add a regression test for each
+     critical finding, then re-run §Verification Commands and append a new
+     `## Executor Report (fix round <N>)` to the task file.
+   - the same ≤10-line return contract as 3b.
+3. Copy back and delete worktrees per 3c. Commit the round:
+   ```bash
+   git add -A && git commit -m "handoff: fix round <N> — TASK-00x"
+   ```
+4. Re-review **only the tasks touched this round**, in parallel, per R2–R4. A reviewer must
+   still differ from the executor model, and still re-runs verification itself.
+5. Update `INDEX.md` and `RUN.md`. If everything is now approved, exit the loop.
 
-**All tasks `approved` or `approved_minor`:**
+After round 2, any task still not approved is genuinely stuck: leave it `blocked`, record why
+in its `## Discussion` thread, and carry it into the Final Report. **Every other task still
+proceeds to R5** — one stubborn task must never hold the whole cycle hostage.
 
-Update `docs/AI_HANDOFF/INDEX.md`: all approved tasks → `done`.
+### R5 — Commit + push (orchestrator)
+
+R4.5 has already run, so by this point every task is either approved or genuinely stuck.
+
+Update `docs/AI_HANDOFF/INDEX.md`: approved tasks → `done`; anything still failing after both
+fix rounds → `blocked`.
+
+Commit whatever remains uncommitted (the per-wave commits from 3d are already in), then push
+once — this is the run's only push:
 
 ```bash
-git add . && git commit -m "handoff: implement <goal>" && git push origin $BASE
+git add -A && git commit -m "handoff: implement <goal>"   # skip if nothing left to commit
+git push origin $BASE
 ```
 
-Replace `<goal>` with the one-sentence goal from ACTIVE.md.
+Replace `<goal>` with the one-sentence goal from ACTIVE.md. Push without asking — `git push`
+is in the settings `allow` list precisely so a one-shot run never stalls at the last step.
+Force-push stays denied, so this can only ever fast-forward.
 
-**Any task `changes_requested` or `critical_block`:**
+**If some tasks are `blocked`:** still push. The approved work is reviewed, tested, and
+committed; withholding it helps no one, and the per-wave commits make any subset revertible.
+Name the blocked tasks in the Final Report.
 
-Report which tasks need fixes. Do NOT push. Executor re-runs Phase 3 for those tasks.
+Finally set `Phase: done` in `docs/AI_HANDOFF/RUN.md`.
 
 ---
 
@@ -362,7 +536,19 @@ Re-run assertions after removal to confirm clean state.
 handoff-fullstack complete:
   Cycle: <ID>
   Tasks: <N> approved, <M> blocked
-  Git: committed + pushed to <branch> | pending human (<M> blocked)
+  Fix rounds used: <0|1|2>
+  Git: <K> wave commits + pushed to <branch>
   Worktrees: all cleaned
   Branches: all cleaned
+  Blocked (needs you): <TASK-xxx — one-line reason> | none
 ```
+
+Then, as the last line of the run:
+
+> Cycle finished. Run `/compact` before starting the next cycle — this session is carrying
+> the whole pipeline's history and the next cycle deserves a clean window.
+
+This is the **only** place in the pipeline that may ask for a compaction. Asking at a cycle
+boundary costs nothing: all state is in git, `INDEX.md` and `RUN.md`, so a compacted or
+brand-new session picks the next cycle up with no loss. Asking mid-cycle is forbidden — see
+the Autonomy Contract.

package/templates/.claude/commands/ukit/handoff-implement.md

@@ -8,7 +8,48 @@
 $ARGUMENTS
 _Empty = all `ready` tasks. Or: "TASK-001" for a specific task._
 
-> **NO git commit. NO git push. Ever.** AI only makes file changes. Human commits when ready.
+> **Commits: yes, one per wave. Push: no.** Each wave is checkpointed to git so any step is
+> revertible, but nothing leaves the machine — `/ukit:handoff-review` decides what gets pushed.
+
+---
+
+## Autonomy Contract — read before anything else
+
+Run every `ready` task to completion in this one invocation. The human is not watching and
+will not answer mid-run.
+
+**Ask nothing after the run starts.** Every decision below has a defined automatic
+resolution — take it, and note it in the wave summary:
+
+| Situation | Required behavior |
+|-----------|------------------|
+| Working tree dirty at Step 1 | commit a checkpoint, continue |
+| Two same-wave tasks share a file | move the later task to the next wave, continue |
+| A task's agent reports FAIL | leave it `blocked`, finish every other task, report at the end |
+| Context warning fires | collapse the finished wave to one line per task, continue |
+| No `ready` tasks but `changes_requested` ones exist | treat those as the work — this is a fix pass |
+
+Escalate only for a blocker outside the repo. Never pause mid-wave to ask for `/compact`:
+context is managed structurally (short agent returns + wave-boundary collapse), and the run
+cursor makes an interrupted run resumable. A compaction request belongs at the end of the
+command, never inside it.
+
+### Run cursor — write after every step
+
+Maintain `docs/AI_HANDOFF/RUN.md`, rewritten (whole file) after every numbered step:
+
+```
+Command: handoff-implement
+Goal: <one sentence>
+Base: <BASE>
+Phase: <1|2|3|4|done>
+Cursor: wave <N> batch <M> — <what just finished>
+Next: <the exact next step to run>
+```
+
+If this file already exists with `Phase:` not `done` when the command starts, this is a
+**continuation**: read the cursor, jump to `Next:`, skip tasks already `pending_review` or
+`done`. Do not restart from Step 1 and do not ask whether to continue.
 
 ---
 
@@ -16,14 +57,19 @@ _Empty = all `ready` tasks. Or: "TASK-001" for a specific task._
 
 Read `docs/AI_HANDOFF/ACTIVE.md` → get `Base: <BASE>`.
 Read `docs/AI_HANDOFF/INDEX.md` → collect `ready` tasks (or specific task from $ARGUMENTS).
-If no ready tasks → report and stop.
+If there are no `ready` tasks, check for `changes_requested`/`blocked` ones and run those
+instead. Only if nothing is actionable → report and stop.
 
-Verify working tree is clean before starting:
+Verify working tree state:
 ```bash
-git status   # must be clean — no uncommitted changes
+git status
 ```
 
-If working tree is dirty → stop. Ask human to commit or stash first.
+If the working tree is dirty, do not stop — commit a checkpoint so the wave copy-back starts
+from a known state and the pre-existing edits stay recoverable:
+```bash
+git add -A && git commit -m "handoff: checkpoint before implement"
+```
 
 ## Step 2 — Build wave groups
 
@@ -35,12 +81,16 @@ Read each `tasks/TASK-xxx.md` for `Dependencies` field:
 
 ### Conflict check — mandatory, before spawning any wave
 
-For every pair of tasks landing in the same wave, compare their `Target Files` lists. If
-any file path appears in both, STOP — do not spawn that wave. This is the code-level
-safety net for the planner's own §2 Scope constraint (same-wave tasks must not share a
-file) in case it slipped through review. Mark both conflicting tasks `needs_breakdown` in
-`INDEX.md` and report the conflicting file(s) to the human; do not resolve it yourself by
-reordering or guessing a dependency.
+For every pair of tasks landing in the same wave, compare their `Target Files` lists. If any
+file path appears in both, **resolve it automatically — do not stop.** Keep the
+lower-numbered task in the current wave and push the other into the next wave by adding
+`Dependencies: TASK-<lower>` to its task file. Two tasks touching the same file are safe as
+long as they never run concurrently, and serializing them is the one resolution that is
+always correct.
+
+This is the code-level safety net for the planner's own §2 Scope constraint (same-wave tasks
+must not share a file) in case it slipped through review. Only mark a task `needs_breakdown`
+when it is missing required fields — never merely for sharing a file.
 
 ### Batch each wave — mandatory
 
@@ -96,6 +146,19 @@ Executor Report (append to task file — do NOT touch INDEX.md):
   Verification Output: <paste>
   Status: PASS | FAIL
   Note: <issues or "none">
+
+Then RETURN TO THE ORCHESTRATOR AT MOST 10 LINES, in exactly this shape:
+  TASK: TASK-xxx
+  STATUS: PASS | FAIL
+  EXECUTOR_MODEL: <exact model ID>
+  FILES: <comma-separated changed paths>
+  RED: confirmed | not-confirmed
+  VERIFY: <n> commands, all pass | <first failing command + one-line reason>
+  NOTE: <one line or "none">
+
+Do NOT repeat RED_OUTPUT or verification logs in the returned message. They are already on
+disk in the task file, which is where the reviewer reads them from. Pasting them back a
+second time is what blows up the orchestrator's context window and kills the run mid-wave.
 ```
 
 > Other tools without subagent support: open each task in a separate session with the code model.
@@ -144,21 +207,44 @@ git branch -D handoff/task-xxx
 **Orchestrator writes INDEX.md** — agents never touch INDEX directly.
 **Worktrees are always deleted immediately** — no exceptions.
 
-### 3d — Next wave
-Create new worktrees from `$BASE`. Repeat 3a–3c.
+### 3d — Wave boundary: commit + context checkpoint
+
+A wave boundary is the only safe place to shed context, because everything of value is
+already on disk (task files hold the full logs, git holds the code). Do all four, in order:
+
+1. **Checkpoint the code** — one commit per wave, so every wave is independently revertible:
+   ```bash
+   git add -A && git commit -m "handoff: wave <N> — TASK-00x, TASK-00y"
+   ```
+   Do not push. `/ukit:handoff-review` owns that decision.
+
+2. **Update the run cursor** — rewrite `docs/AI_HANDOFF/RUN.md` with `Cursor: wave <N> done`,
+   `Next: wave <N+1>` (or `Step 4` if that was the last wave).
+
+3. **Collapse the wave in working memory.** From here on, refer to the finished wave only by
+   its one-line-per-task summary. Do not re-read task files, restate executor reports, or
+   quote earlier diffs. The reviewer reads what it needs from disk itself.
+
+4. **Continue.** If a UKit context warning has fired, say one line —
+   `context checkpoint: wave <N> collapsed` — and start the next wave anyway. Do not ask for
+   `/compact` here. If the session ends regardless, `RUN.md` plus the `SessionStart` resume
+   hook bring the run back to exactly this point.
+
+Then create the next wave's worktrees from `$BASE` and repeat 3a–3c.
 
 ## Step 4 — Finalize: verify cleanup
 
 All waves complete. Verify:
 
 ```bash
-git worktree list        # must show only main worktree
+git worktree list          # must show only main worktree
 git branch | grep handoff  # must be empty
-git status               # shows uncommitted changes — this is expected
-git diff --stat          # summary of everything that changed
+git log --oneline -n 10    # one commit per wave
+git status                 # clean, or only trailing edits from the last wave
 ```
 
-All changes are in the **main working tree as uncommitted files**. No branches or worktrees remain.
+All changes are committed as **one commit per wave on `$BASE`**, nothing pushed. No branches
+or worktrees remain. Set `Phase: done` in `docs/AI_HANDOFF/RUN.md`.
 
 ## Step 5 — Report
 
@@ -166,8 +252,13 @@ All changes are in the **main working tree as uncommitted files**. No branches o
 Wave summary:
   Wave 1: TASK-001 [pending_review], TASK-002 [blocked]
   Wave 2: TASK-003 [pending_review]
+Commits: <K> wave commits on <BASE>, not pushed
 All worktrees and branches removed.
-Uncommitted changes in working tree — human commits when ready.
+Blocked (needs you): <TASK-xxx — one-line reason> | none
 ```
 
 **Next:** switch to strong model → `/ukit:handoff-review`
+
+If this session is now heavy, this is the right moment to `/compact` — the wave commits,
+`INDEX.md` and `RUN.md` hold all the state the review phase needs. Suggest it here, at the
+command boundary, never inside a wave.