git:20261029.ed49b76 to git:20261030.75d93d5

- > **Mutual exclusion with `/handoff`.** This caps a workstream; `/handoff` passes one on. In-flight work → STOP, use `/handoff`. Two workstreams (one done, one live) → end each separately, naming which. Exception: the review-owed-close class (`coordinator/skills/handoff/SKILL.md` § Step 0, trigger 4) → the trampoline, § Resolve judgment points.

- This ceremony is computed end to end: directives ship as `directives[]`, what cannot be resolved as `judgment_points[]`. Never recompute by hand what a field already answers.

-

- **Fallback close:** an `emit-dispatch-workflow` run closes in-run; this is the relay fallback's last turn, every mode (hands-on, pm, ceo), fired with `dispatch.land_run` once the PM accepts the execute digest. It never commits the run's product changes; it is bookkeeping. The § Final Summary output IS the `close` wake digest: verdict → `outcome`, exceptions → `decision_required` and `deviations`.

- Shape W (PowerShell) shown; POSIX hosts take Shape A/B: `${CLAUDE_PLUGIN_ROOT}/snippets/resolve-coordinator-bin.md`.

- **Prefer `--decisions-file`;** `--decisions '<json>'` for short payloads (argv mangles prose); passing both fails loud.

- Plain `brief` returns `artifact`/`preflight`/`gates`/`directives`/`judgment_points`/`decisions`/`narration`/`next_move`. `preflight.session_shape` carries `sid`, `disposition` (`single-session`/`predecessor-consumed`), `consumed_handoff`, detector diagnostics. `jp-session-shape` is the untrusted-gate point for an uncertain resolution.

- **Dispatch authorization — invoking this skill IS the request.** The dispatches named below are constitutive steps of this skill, not a separate thing to get cleared: invoking a skill requests the actions that skill performs. A harness line permitting dispatch "unless the user requested it" is therefore **satisfied here, not overridden** — no precedence claim is needed and none is made. Re-asking spends the very context the dispatch exists to protect. The rule attaches to skill entry and dissolves no PM-authored gate: keyword-gated skills gate entry, and every gate a skill names for itself still binds — per-session cross-repo-commit assent, ask-before-external-action, and any other this skill's own body names. Tripwire: `UNATTRIBUTED-HARNESS-LINE-IS-NOT-PM`.

- - **Execution-observations fold**: read each sidecar's `divergence` as quoted narrative, never EM-authored prose; surface a crashed-executor marker before deleting it. A `## Tasks`-spine plan cites `plan-completeness status <plan-path>`'s divergence rollup (with its non-conformant count) instead of per-chunk sidecars; a pre-spine plan reads sidecars.

- - **Memo-resolution / self-clean disposition**: decide once, plain prose; evidence is surfaced, never picked.

- - **Session Ledger row append** (predecessor-consumed only): one row to the consumed handoff's `## Session Ledger`, via the `handoff.append_session_ledger` op, never hand-typed.

- - **Prime exit criterion assertion**: a run-stamped plan already carries `exit_criterion_met`; verify it, never recompute. Absent blocks; clear it by the re-judge route (terminal-judge § Closing a plan whose run judged `not_met`). `asserted: false` routes to `/handoff` or a Phase-5 halt. At L and above the run's ledger checker verdict is the close: no judge, falsifier or delivery check runs after it, except the fresh re-judge after a `not_met` remnant wave (the verdict's `remnant` object; `coordinator/contract/remnant-completion-fragment.json`). [terminal-judge](../../docs/wiki/reviewer-pipeline/terminal-judge.md); `A-PLAN-SELF-COMPLETES-ONLY-ON-A-MET-TERMINAL-JUDGE`.

- - **Stop the session's own watchers — MANDATORY, never opt-in.** `coordinator-invoke workstream_complete.stand_down_watchers '{"session_id":"<sid>"}'` stops this session's, never a peer's. Render `stopped` (name each), each `survivors` entry as **not verified** (never "done"), `expires_on_its_own` (`notify_when_idle`, no action), and every `unattributed` entry and `warnings` line. A Group EM holder relays the returned `notice`. `A-CLOSED-SESSION-LEAVES-NO-WATCHER-RUNNING`.

- - **Terminal-baton drain — MANDATORY, and the last thing this ceremony does.** No directive

- performs it.

- 1. Hand-stamp `deployment_state`/`shipped_in` on **only** the two batons § Apply's carve-out

- omits from the payload; **never re-stamp one the payload already stamped.**

- 2. **After** `apply`'s own disposal read, once every payload-stamped and hand-stamped baton carries a terminal `deployment_state`, run `sweep-terminal-handoffs`.

- 3. **Close condition: `state/handoffs/` holds no record carrying a terminal

- `deployment_state`** (`shipped`/`continued`/`closed` —

- `HANDOFF_TERMINAL_DEPLOYMENT`; `declined`/`superseded` are `status` values, never `deployment_state`) **when this ceremony reports complete.** Never

- defer the drain to the next ceremony.

- - **Kira runs only when the EM or PM names Kira**, never by default and never on every close.

- - **An idle subagent has not failed.** Recover a review that never delivered its verdict from its transcript under `subagents/`; never replace it with `em-verified`, which overwrites an independent finding. `AN-IDLE-SUBAGENT-HAS-NOT-NECESSARILY-FAILED`.

- **The discriminator: a judgment point earns its place only if a different competent EM, with the

- same artifacts on disk, could reasonably answer it differently.** `A-FACT-WITH-A-CLOSED-ENUM-IS-NOT-A-JUDGMENT-POINT`.

- **3 classes.** 1 = CLI-computable (not listed here). 2 = interpretation, but not *this EM's* — the passage already closes the output enum, so a differing answer is demonstrably wrong; demote when a path exists, else carry it as a judgment point by necessity, named as such. 3 = judgment/taste/tradeoff — two competent EMs can disagree and both be right. Never author a class-2 fact as a judgment point. A re-test names a class per item it **keeps**. Calibration: `coordinator/docs/wiki/ceremony-calibration/close-ceremony-residue.md`.

- **A shipped `recommendation` is applied by default and shown, not asked** — carry it into the decisions map and report what was filed. A null matters only when genuine: `jp-session-shape` always, tail-blocking scaffold/commit-subject/consumed-handoff when they fire. A blocked computation or missing producer is a break-class engine defect: resolve cheaply or memo, once confirmed absent. Unnamed points carry their own prompt/evidence on `judgment_points[]`.

- **Review — 4 class-3 survivors, none demotable:** `shared-schema-touch-check`, `governing-spec-identification`, `finding-tradeoff-escalation-check`, `shallow-row3-waive-check` (`coordinator/docs/wiki/ceremony-calibration/close-ceremony-residue.md` § Review class-3 survivors). The other four named there belong to the execute workflow's review stage (`coordinator/skills/execute-plan/SKILL.md`, `review-brightline-gate`), not this ceremony.

- **Verify once and trust it:** a close-time suite or oracle check runs once, foreground, no rerun loops or background waiters (`coordinator/docs/wiki/test-design-discipline.md`).

- **L+ code-quality trigger — a separate derivation, not a parameter on Scale's measurement.** Scale

- keys off *measured* `gross_loc`/`commit_count`/`surface_count`; L+ keys off the **cited sizing-object's `estimate.tshirt`** — resolve the closing plan's

- `sizing_object:` citation and read `estimate.tshirt` off the artifact it names. Fires at `L` or `XL`; never answer it from Scale's measured figures.

- **The review record is the plan's `review_stamp`; this ceremony neither runs nor dispatches it.**

- For a plan-bearing close, review ran per executor group in the emitted execute-plan workflow and

- `review-stamp mint` recorded it via `land_run` (never re-minted by hand);

- `gates.review_receipt` reads it; this ceremony reads the gate and writes no trail.

- **Review absent at close → this ceremony dispatches review; there is no skip.** No governing plan,

- or no `review_stamp` (mise-en-place included): run `/review-code` over the close's diff before

- `apply`, at least one reviewer, partitioned when PARTITION-MANDATORY. That clears this gate but

- mints no stamp: a stampless hand-worked plan reaches `implemented` only via

- `emit-dispatch-workflow --plan <p> --rejudge`, fired, then `reverify-delivery record --result-json

- <task output>`, then `review-stamp mint`; no hand-dispatched judge or `record-superseding-review`

- substitutes. Never dispose the gap with `proceed-unresolved` or any skip.

- The terminal-review Stop gate holds regardless.

- **Hand-measuring the brightline is a last resort** — only once `stage_paths` is supplied and `review_scale` still returns `resolved: false`. **Sum per-owned-commit diffs** (`<sha>~1..<sha>`, never `^`), **never an `oldest..newest` range**, and **count code only** (`.md`/`.yaml`/`.yml` excluded). Method: `coordinator/docs/wiki/ceremony-calibration/workstream-complete-review.md` § Hand-measuring the brightline.

- **The trampoline — hand the whole ceremony to a fresh session rather than cap with the review unrun.** Low

- context is not a trigger-4 reason. When the owed review is

- genuinely un-runnable here (`coordinator/skills/handoff/SKILL.md` § Step 0, trigger 4 — a closed class, never admitted by analogy), exit via `/handoff` naming which member fires and the

- event outside this session's reach that clears it.

- **Capping with the review unrun is forbidden; `verdict: pending` is not the escape hatch.** Tells you are about to cap (trampoline instead): "the next session can review this"; `reviewer: waived` paired with a non-`waived` verdict; a range narrowed because the honest range was refused; "mandatory" reasoned as advisory. Tripwire: `PARTITION-MANDATORY`.

- **Chain-ancestry is provenance, not review discharge — it does not clear a HALT.** `certifies_review: false` reads "ancestry NOT reviewed."

- **Case (c) is often a live peer's in-flight files, not an orphan.** `brief` classifies

- a/b/c mechanically and surfaces the peer-vs-orphan call as `concurrent-peer-attribution`;

- disposing case (c) is EM judgment; weak signals default to case (c).

- **If a peer is plausibly live, never adopt their paths** — commit only your own files by

- explicit path. Once ruled out, take exactly one: **commit** with provenance (per `snippets/scoped-commit-route.md`), or **leave it

- explicitly owned by X**; never leave case-(c) files dirty and unnamed. Never `git stash`. Orphan `.tmp.<pid>.<nanos>` files are Edit-tool crash

- artifacts: diff before deleting.

- `& "$env:COORDINATOR_SETTINGS_HOME\bin\workstream-complete-assemble.exe" apply --decisions-file <path>` — the file is a JSON

- object whose keys are *either* a `judgment_point_id` (value `{"disposition": "<value>"}`) *or* one of the non-JP decisions keys (`stage_paths`, `review`, ...), each with its own flat shape. **Never wrap a non-JP key's value in a `{"disposition": ...}` envelope** (it reads as the key being absent). `stage_paths` is a flat list: `{"stage_paths": ["<path>", ...]}`.

-

- `decisions` carries what the compute half can't read off disk: lessons, completion-nature/prose, memo/scratch dispositions, commit subject/prose.

-

- **`handoff_dispositions` is another non-JP key**, `{"<handoff-basename>.md": {...}, ...}` — one entry per baton this close disposes, each value an **object**, never a bare string. All four consumer-resolved values are carried: `shipped` (with `shipped_in`, below); `closed`/`abandoned` (each with `closed_reason` from `cancelled`/`displaced`/`stale` — **never defaulted, never fabricated**; anything else is refused); `continued` (neither field).

- **`shipped_in`:** one full-length sha per baton — the last commit in this session's own owned-commit list (sliced `<sha>~1..<sha>`; no code-only filter) touching the `writes:` paths of the plan spine whose `deliverable_id` matches the baton. Never a range, PR ref, list, or the close's own commit-tail sha. No such plan or commit → not `shipped`: `closed` (with `closed_reason`) or `continued`, never a placeholder.

- **An entry is silently dropped** unless it is an object, this session holds the claim, and the record is still active under `state/handoffs/` at `apply`; the leg also needs `decisions.subject`.

- **Omit the baton in exactly two states:** (1) the deliverable is carried only by the close's own commit; (2) the record was already archived. Any stamp still owed is the hand route (§ Genuine EM actions). Every other `closed`/`abandoned`/`continued` baton is emitted.

- Order is transition, dispose, archive: `continued` needs `deployment_state` already `continued`; disposal is refused once the record left `state/handoffs/`. Full rules: `coordinator/docs/wiki/ceremony-calibration/close-ceremony-residue.md` § Handoff-disposition payload rules.

- **`apply` commits — `_run_close_commit_tail` is not optional.** It runs after `_execute_directives`, gated only on a `decisions.subject` (and `sid`), folding the `handoff_dispositions` ship-stamps into its `stage_paths`. **Never read `apply`'s exit as leaving nothing landed.** Then, still yours:

- - **Scoped commit** of the completion entry, Session Ledger row, and your own files, per `snippets/scoped-commit-route.md` — a **second** commit after `apply`'s own close commit, never carrying the stamps.

- - **Nothing** for review — the plan's `review_stamp` was minted before this ceremony ran; confirm `gates.review_receipt.blocks` is `false` and name any gap in

- the summary.

- **`apply` runs the post-close steps itself, after its close commit:**

- `d-baton-chain-closure`, `d-structural-index-refresh`, `d-ceremony-reindex`, then a release of

- every touch claim the session holds. Read outcomes off `post_close[]`. `d-ceremony-reindex` is

- engine-owned; report its outcome, never re-run it (`A-REINDEX-IS-A-STALENESS-FLAG-NEVER-AN-AGENT-TRIGGER`).

- **A run-stamped plan already carries `implemented`; the ceremony verifies it, never restamps.** Where `land_run` did not stamp, `d-stamp-plan-implemented` is gated engine-side (a blocked stamp is not a failed one) with three empty-`resolves` judgment points on its `depends_on`: `jp-open-spine-rows-block-stamp` (unwaived `open` rows, or `indeterminate`), `jp-landed-reconciliation-block-stamp` (plan `landed` with unticked ACs), `jp-review-receipt-block-stamp`. An unresolved one lands in `report["blocked"]` under `HALTED_AT_JUDGMENT` — a close exits non-failing with no stamp. That covers the stamp leg only, never an open census gate (§ Completion verdict). `waived_open_spine_row_ids` clears leg 1's `applicable` arm only. Never build a doctrine gate beside these. Tripwire: `AN-HONEST-INCOMPLETE-DOES-NOT-EARN-THE-WRAP-OFFER`.

- Exit `2` (`DIRECTIVE_FAILED`) = nothing landed; exit `4` (`PARTIAL_MUTATION`) = a directive failed. **Exit `4` is a failed close, never "done with residue":** fix the cause and re-run `apply`. **`state/sizings/` files are committed by the engine's close commit**. A client-side timeout is no failure signal: reconcile against commit state before re-running.

- Push runs on a cadence, not on this commit: `push_status` `"cadence-pending"`, `"pushed"` and (older engines) `"deferred"` are all success. Only `"deferred"` wants confirming, via `git branch -r --contains <sha>`. **Never `git push` to "fix" an apparent delay.**

- A residual discovered mid-execution never counts in the harvest. One disposition per item; nothing to sweep: omit the line. **Default is fix it now**; routing elsewhere costs a named reason from a closed class: `peer-contention`, `other-repo`, `own-plan`, `irreversible`, `not-real` (`coordinator/docs/wiki/ceremony-calibration/workstream-complete-review.md` § Execution-residual reason classes). A break-class residual with none of the five is fixed, not filed. The auto-memory drain gate runs only at `/workday-complete`/`/workweek-complete`, never here.

- **Spinoff overlap re-check, same step.** Before reporting complete, for every open (`kind: spinoff`) handoff this session or its chain authored, run <!-- VERBATIM -->`git log --since=<its authored-at> -- <its named scope/paths>` against `state/handoffs/` and the scope paths. A hit means the scope landed since the fork — surface it to the PM as a `superseded`/`consumed` candidate. No hit: omit the line.

- **Consume `gates.completion_verdict` in the close narration.** It composes the five gates this

- ceremony reads (`session_shape`, `review_receipt`, spine-row completeness, plan-landed

- reconciliation, consumed-handoff completeness) into one verdict — read it off `gates`, never

- hand-derived.

- **Two census gates force completion — the close never reports complete while either is open.**

- `owned_uncommitted` (files this session owns, still uncommitted) and `unstamped_run_batons` (run

- batons never stamped shipped). Either open goes into `failed` (exit

- `4`): commit the owned files through the close commit, stamp the batons — never report it as residue or `indeterminate`. Tripwire:

- `A-CLOSE-WITH-OWNED-UNCOMMITTED-OR-UNSTAMPED-BATONS-IS-NOT-COMPLETE`.

- **For the five gates it is not a pass/fail lens.** `indeterminate` is the ordinary case, so **render it as `indeterminate`, never as "incomplete"**, naming only the ones a

- gate-specific reading says are worth naming. Readings:

- **Residue → verb lookup, for whatever the verdict leaves outstanding** (never the two census gates):

- | Residue shape | Verb |

- |---|---|

- | Blocked on further work this session should still finish | trampoline (`/handoff`) |

- | Not worth doing | won't-do |

- | Worth doing, not now | backlog |

- | A distinct workstream someone else should pick up | spinoff |

- **Then append the changelog:** `& "$env:COORDINATOR_SETTINGS_HOME\bin\workday-complete-step9-append-changelog.exe" --no-push` (POSIX `$COORDINATOR_SETTINGS_HOME/bin/workday-complete-step9-append-changelog --no-push`). Rerun-safe.

- **Report by exception.** One line always; everything else only when *not* clean. A Group EM

- session additionally follows `coordinator/snippets/group-em-output-contract.md` — one emission

- form only (a decision awaiting the PM), filtered at source, never appended at the end.

- A baton shipping here can newly close its chain: relay `d-baton-chain-closure`'s `post_close[].output` when it carries one; never run `chains`.

- **A leg parked as blocked on a sibling repo carries its exchange, or it is not parked.** Check

- the three conjuncts in `coordinator/snippets/cross-repo-block-exchange.md` — declared, addressed,

- answered — name the one that failed. Tripwire: `A-SENT-MEMO-IS-NOT-AN-EXCHANGE`.

- | `**Consumed-handoff completeness:**` | element reports `blocks`/`indeterminate` — name handoff+leg (`not-applicable` is a 4th leg-A verdict, NOT reported) |

- | `**Pushed:**` | the push did **not** land — `deferred`/`detached` is success and stays silent |

- | `**Publish lag:**` | `compute_publish_lag_advisory` reports a lag worth naming — silent when clean |

- | `**PM ask:**` | the closing plan resolves ≥1 PM verbatim — one line, `pm-brief render <closing-plan>` names each ask, then `met` or the residue verb from § Completion verdict; read via the plan's own `sizing_object` (`A-ROUTED-SIZING-IS-NOT-A-LIVE-ASK`); all-met collapses to one `met` |

- **`not-applicable` is not `indeterminate`.** `not-applicable` = nothing to look at — silent, like `clean`. `indeterminate` = the gate tried and couldn't — report it. Tripwire: `NOT-APPLICABLE-SPANS-TWO-SILENCES`.

- **Do not print** `Lessons captured`/`Work archived`/`Docs updated`/`Orientation refreshed` — the commit records them. **An automated mechanism's routine success is never a PM line**: report it only when it *failed*. This ceremony emits NO archival directive; the drain moves the record (§ Genuine EM actions). Never author a second sweep beside it.

- **Classify flags by severity first.** A break-class defect is fix-by-default — fix it, report the fix, never a passive `Flag to PM:`; only direction-class items go there. → global `CLAUDE.md § Flag Severity`.

- - Rebuild the Step-0 session-shape gate, the coverage judgment point, or `resolve_repo_root`.

- - Compose or extend `apply_base.py`, or propagate `/workday-complete`'s dirty-tree auto-disposition.

- - Auto-resolve tier-A oracle disagreement — a hard stop; needs `/autonomous` plus a recorded reviewer.