@azure-id/orc 1.9.1 → 2.0.2

package/templates/skills/orc/SKILL.md

@@ -3,17 +3,15 @@ name: orc
 description: >
   Use when orchestrating a multi-task build through a full pipeline: intake →
   planning → scored parallel execution → review → verify → ship. Triggers:
-  "orchestrate this", "build this in parallel", "run this with subagents",
-  "use orc", or any request to take a feature/spec from intent to PR with
-  subagents. Routes planning to Superpowers, OpenSpec, or its own planner;
-  schedules conflict-free waves; scores each task to pick the cheapest capable
-  model; checkpoints eagerly; survives compaction and fresh-session resume.
-  Stack-agnostic.
+  "orchestrate this", "build this in parallel", "run this with subagents", "use
+  orc", or any request to take a feature/spec from intent to PR with subagents.
+  Scores each task to pick the cheapest capable model, and survives compaction
+  and fresh-session resume. Stack-agnostic.
 ---
 
 # ORC (orchestrator spine)
 
-You are the **orchestrator**: **Opus 4.8 high — or Opus 5 / Fable 5 at medium+**
+You are the **orchestrator**: **Opus 4.8 high — or Opus 5.5 / Fable 5 at medium+**
 (never downgrade yourself). You own the schemas, the dependency/conflict graph, wave
 scheduling, per-task model scoring, all checkpoint writes, user Q&A relay, and
 every decision below. Workers stay dumb and isolated.
@@ -24,8 +22,8 @@ version of a reference you haven't loaded this run. Detect the stack from the re
 
 ## Preflight gate (before Phase 0 — do this FIRST)
 
-Confirm you are **Opus 4.8 high**, or **Opus 5 / Fable 5 at medium+** (both clear
-the guard from medium up; Opus 5 also unlocks the [90,100] executor band). Effort
+Confirm you are **Opus 4.8 high**, or **Opus 5.5 / Fable 5 at medium+** (both clear
+the guard from medium up; Opus 5.5 also unlocks the [90,100] executor band). Effort
 is hard-blocked by the `orc-effort-guard.js` PreToolUse hook; the model cannot be
 (hooks can't see it) — the statusline warns. On a weaker tier **STOP immediately**
 and tell the user to switch the main session and re-run — never intake below it
@@ -69,11 +67,11 @@ themselves are this lane's own and stay here.
 
 ## Dispatched roles (you never do this work yourself)
 
-**Analyst** `orc-analyze` (Opus 5 high): doc OR bare request →
+**Analyst** `orc-analyze` (Opus 5.5 high): doc OR bare request →
 scope-bounded, code-grounded report + spec; standard or opt-in DEEP (scouts).
-**Context-combiner** (Opus 5 high): merges 2+ related confirmed analyses
+**Context-combiner** (Opus 5.5 high): merges 2+ related confirmed analyses
 into ONE combined spec; build only on `handoff_ready` with `coverage_pct` =
-100; full lane only. **Planner** `subskills/orc-planner` (Opus 5 medium):
+100; full lane only. **Planner** `subskills/orc-planner` (Opus 5.5 medium):
 request or spec → planning-output. Scout dispatch, analyst-return gates,
 combiner tracking, the `git_head` staleness valve, and the Phase 1 exit gate
 are YOURS and deterministic — load `../_shared/phases/analyst-gates.md` at their
@@ -81,7 +79,7 @@ trigger points; emit `GATE` trace lines.
 
 ## Dispatch via named agents (not prose)
 
-**`orc run inflight` before ANY re-dispatch** (0 clear · 1 in-flight · 2 unknown).
+**`orc run inflight` before ANY re-dispatch.**
 A Task error does not kill the agent behind it, and exit 2 REFUSES by default —
 `a lane that re-dispatches over a live attempt` has broken the contract. Canonical: `_shared/return-validation.md` §0.
 
@@ -96,63 +94,39 @@ requeue) run the same formula, inherit the original task's risk floor, and never
 dispatch below the finding-task's band. Fixed roles dispatch BY NAME (analyst /
 combiner / planner / reviewer / verifier — see `config.md`'s fixed-role table +
 `.claude/agents/MODEL-MAPPING.md`). If `opus5_only`, EVERY role (scored and fixed)
-resolves to its Opus 5 agent, FORCING over everything below — `_shared/opus5-only.md`.
+resolves to its Opus 5.5 agent, FORCING over everything below — `_shared/opus5-only.md`.
 Caveat: a subagent's model can't exceed the MAIN session's tier — run the main
 session on Opus or the Opus pins silently fall back (the original "wrong model" bug).
 
-## Config (read at run start)
-
-**ONE resolver, and it is not you:** `orc lane config orc --json`. Obey
-`effective`, print every line in `announce[]` VERBATIM at preflight, and honour
-`stops[]` before wave 1. Never re-derive a value, a precedence or an inertness
-from `.claude/orc.config.yaml` — a key this lane does not read is not in the
-answer, and a key another key shadows comes back already marked. Exit ≠ 0 → say
-the CLI is unavailable and fall back to `../_shared/config-precedence.md`'s
-documented defaults, out loud. Priorities and families:
-`../_shared/config-precedence.md`.
-
-## Rules — the anti-slop card (`../_shared/phases/rules.md`)
-
-`orc rules slice --lane orc --json` is the ONLY assembler; never build
-the card here. It rides under the house rules and above the task —
-**house rules > your project's rules > ORC's own packs** — and its `line` prints
-VERBATIM at preflight. Returns gain `rules_applied[]`, `rules_conflicts[]` (a gap,
-never a silent choice) and `rules_overridden[]`.
-## Calls
-
-**ONE catalogue, and it is not you:** `orc lane calls orc --json` names every
-CLI call this lane makes, each with its exit-code contract, its cost, when to run
-it, and what an EMPTY answer means. Never invent a spelling, never re-word an
-exit code, and never re-derive a state word — the CLI's state words are the only
-state words, and **an exit code is an ANSWER wherever that contract says so, not
-a failure**. A call the answer does not name is a call this lane does not make.
-Exit ≠ 0 from the catalogue itself → say the CLI is unavailable and name the
-command you are about to run, out loud, before running it.
+## Lane contract (`../_shared/lane-contract.md` — read it ONLY when a call exits ≠ 0)
+
+- **Calls:** `orc lane calls orc --json` names every call and its exit codes.
+  **An exit code is an ANSWER where it says so, not a failure.** Make no other call.
+- **Config:** `orc lane config orc --json`. Obey `effective`, print every line
+  in `announce[]` VERBATIM at preflight, and honour `stops[]` before wave 1.
+  Never merge `.claude/orc.config.yaml` yourself (`../_shared/config-precedence.md`).
+- **Rules:** `orc rules slice --lane orc --json` is the ONLY assembler
+  (`../_shared/phases/rules.md`). Its `line` prints VERBATIM at preflight.
 
 ## Behavior trace (PERMANENT — always on, no config toggle)
 
-Follow `../_shared/phases/trace.md` (ALWAYS load it at run start). The
-`orc-trace.js` hook writes the `SPAWN`/`RETURN`/`PHASE-EDGE` skeleton
-deterministically; the rich narrative is **dispatched, never remembered** — every
-`emit <VERB>` step below means RECORD that event, with its REAL timestamp, into
-the current **phase packet**; you never append a trace line yourself. Run start:
-create `log_dir`, write `log_dir/.current` = `run-orc-<slug>-<DDMMYY>-<HHMMSS>.txt`
-AND `touch the trace file` of that name in the SAME step; store `trace_path`.
+Follow `../_shared/phases/trace.md` (ALWAYS load it at run start; pairing rule,
+packet shape and run end are there). Lane token `orc`, tier **Build lanes**. The
+`orc-trace.js` hook writes the `SPAWN`/`RETURN`/`PHASE-EDGE` skeleton; the
+narrative is **dispatched, never remembered** — every `emit <VERB>` step below
+means RECORD that event, with its REAL timestamp, into the current **phase packet**. Run start: create `log_dir`, write `log_dir/.current`
+= `run-orc-<slug>-<DDMMYY>-<HHMMSS>.txt` AND `touch the trace file` of that name
+in the SAME step; store `trace_path`.
 **Under `ultra_mode` the lane segment is `ultra`, not `orc`** (`run-ultra-<slug>-…`)
 — the filename IS the per-lane data, so an ultra run named `orc` is counted as a
 plain `/orc` run forever, hiding the costliest lane in every usage report.
-**Phase close = dispatch `orc-trace-writer-haiku-4-5`** with that packet
-(`phase`, `events[]`, and `decisions` — the WHY: scoring rationale, the user's
-answers VERBATIM, what you rejected; `run_meta` on the FIRST packet only).
-**Pairing rule:** issue phase N's writer dispatch in the SAME tool block as phase
-N+1's first dispatch (a phase with no next dispatch sends it solo, before its
-user-facing output); the first packet is solo + synchronous — it repairs a
-hook-bootstrapped filename. `DISPATCH`/`VERIFY` models are derived from the agent
-NAME and checked against each return's `actual_model`/`actual_effort` — surface
-any ⛔ DOWNGRADE to the user, not just into the packet. A phase ending with
-`zero new trace lines is a protocol violation` — build and dispatch its packet
-NOW, with the events' real stamps. Run end (Phase 8 or abort): the `FINISH`
-packet goes out and RETURNS, then delete `log_dir/.current`.
+**Phase close = `orc trace write --packet -`** (exit ≠ 0 → `orc-trace-writer-haiku-4-5`).
+The first packet is solo — it repairs a hook-bootstrap filename.
+`DISPATCH`/`VERIFY` models are derived from the agent NAME and checked against
+each return's `actual_model`/`actual_effort` — surface any ⛔ DOWNGRADE to the
+user, not just into the packet. A phase ending with
+`zero new trace lines is a protocol violation` — build and write its packet
+NOW, with the events' real stamps.
 
 ## Extra — a band that executes OFF Claude (config `extra_enabled`, default false)
 
@@ -175,7 +149,7 @@ review/verify re-check the invariants + `validation_gate[]` lines. Load
 ## Ultra lane (`/orc-ultra`)
 
 `/orc-ultra` sets `ultra_mode: true` RUN-SCOPED (never persisted): full pipeline
-+ Opus 4.8 max Advisor (Phase U0) + three judge gates + forced overrides (deep
++ Opus 5.5 xhigh Advisor (Phase U0) + three judge gates + forced overrides (deep
 analyze, pattern/testgen/security on, executor tier floor); never on plain
 `/orc` or orc-mini. Load `references/ultra-mode.md` at Phase 0 when ultra_mode;
 orc-advisor / orc-judge load at their dispatch points.
@@ -214,10 +188,9 @@ them; they are never dispatched as subagents).
 
 ## Phases
 
-`orc lane phases orc --json` **is** the pipeline — the CLI owns the list and
-its order, and this table is the human index of it. Never derive the order
-from these filenames; a second idea of the pipeline is the drift the manifest
-exists to prevent.
+`orc lane phases orc --json` **is** the pipeline; this table is only its human
+index. **The CLI owns the order**: never derive it from these filenames
+(`../_shared/lane-contract.md` §Phases).
 
 **Read a row when its phase fires, not on activation.** Every row is
 `on-phase` — this spine deliberately carries no `always` phase pointer. **Read
@@ -228,8 +201,7 @@ each row.
 
 W13 gave those ten a second reader (`orc-diy`), so they moved to
 `_shared/phases/`. Intake and Integration have one consumer each and stay home
-— a file with one consumer stays home. W14 (`orc-mini`/`orc-fast`) is what adds
-a `trim` layer beside the `full` one.
+— a file with one consumer stays home.
 
 | # | Phase | File | Read | Trace |
 |---|-------|------|------|-------|
@@ -252,4 +224,4 @@ their config key is resolved by `orc lane config orc --json`, never read raw.
 ## Waiting mid-run (`/orc-wait`)
 
 Canonical: `../_shared/wait.md`. **`a lane that waits without a hand-back` has broken this contract.**
-Checkpoint **full** · safe point **wave or phase edge**. `soft` FORCES that checkpoint and does NOT stop if the write fails; `hard` skips it and can lose an in-flight return. Never begin a wait between a dispatch and its validated return, or before the smoke gate has reported.
+Checkpoint **full** · safe point **wave or phase edge**.

package/templates/skills/orc/config.md

@@ -35,13 +35,13 @@ canonical 6-band table, and dispatches the matching **executor agent**.
 | [30,40)  | claude-sonnet-4-6 | medium | orc-executor-sonnet-4-6-med |
 | [40,55)  | claude-sonnet-4-6 | high   | orc-executor-sonnet-4-6-high |
 | [55,65)  | claude-sonnet-5   | high   | orc-executor-sonnet-5-high |
-| [65,90)  | claude-opus-5     | low    | orc-executor-opus-5-low |
-| [90,100] | claude-opus-5     | medium | orc-executor-opus-5-med |
+| [65,90)  | claude-opus-5-5     | low    | orc-executor-opus-5-low |
+| [90,100] | claude-opus-5-5     | medium | orc-executor-opus-5-med |
 
 (Haiku has no effort ladder — that agent carries no `effort:` field.) The risk
 floor (≥70) lands `orc-executor-opus-5-low` at minimum in THIS table. Above ~65
 the useful dial stopped being the model GENERATION and became the EFFORT, which
-is why the old four Opus rows are two. **Every band from 65 needs an Opus 5 MAIN
+is why the old four Opus rows are two. **Every band from 65 needs an Opus 5.5 MAIN
 session** or it silently falls back to the session model (the tier-honesty rule
 reports the downgrade) — two bands where it used to be one, and that is the cost
 of this table.
@@ -59,15 +59,15 @@ One model, EFFORT as the cost dial. Off by default; nothing changes until set.
 
 | Score | Model | Effort | Executor agent |
 |-------|-------|--------|----------------|
-| [0,90)   | claude-opus-5 | low    | orc-executor-opus-5-low |
-| [90,100] | claude-opus-5 | medium | orc-executor-opus-5-med |
+| [0,90)   | claude-opus-5-5 | low    | orc-executor-opus-5-low |
+| [90,100] | claude-opus-5-5 | medium | orc-executor-opus-5-med |
 
 Two bands, sharing the 90 edge with the default table's top two rows. That
-symmetry is the point: once the default table's high end is already Opus 5 with
+symmetry is the point: once the default table's high end is already Opus 5.5 with
 effort as the dial, this mode differs from it only BELOW 65, so a third band
 would be a distinction the default table stopped making.
 
-**Tier cost:** today TWO bands in six need an Opus 5 main session; with this on,
+**Tier cost:** today TWO bands in six need an Opus 5.5 main session; with this on,
 EVERY dispatch does, so a lower session downgrades every task (warn-only — a
 hook can gate effort, never model). **Scope:** it is NOT executor-only — it also
 forces every fixed role below, across every lane. orc-diy's table
@@ -93,8 +93,8 @@ un-shown number.
 | Ultra advisor (/orc-ultra only) | orc-advisor-opus-5-xhigh |
 | Ultra judge (/orc-ultra only) | orc-judge-opus-5-xhigh |
 
-Under `opus5_only`, every role above that is not already `claude-opus-5`
-dispatches its Opus 5 variant instead — plus the roles owned by other lanes
+Under `opus5_only`, every role above that is not already `claude-opus-5-5`
+dispatches its Opus 5.5 variant instead — plus the roles owned by other lanes
 (scout, wiki scanner, CLAUDE.md writer, retro miner, fast executor).
 
 ## Where each subsystem's rule is written down

package/templates/skills/orc/examples/full-run-mock.md

@@ -1,73 +1,73 @@
-# Example — Annotated Full Run (v2.2, dry run)
-
-O: = orchestrator (Opus 4.8 high, always) · U: = user. Nothing real. The
-orchestrator NEVER implements — it always spawns scored subagents.
-
-U: Orchestrate: merchant notification system — in-app, email digest, prefs page.
-
-## Phase 0 — Intake
-O: Creates run folder run/merchant-notifications/ FIRST.
-   [reads repo: TS/yarn/jest — asks nothing about stack] Rough size: medium+ → 4-question tier (one batched round):
-   1) What should exist when done? 2) Out of scope? 3) How do we know it's done? 4) Patterns/files to avoid?
-U: [answers] no push, no admin; bell count + both digest schedules + prefs persist; follow services/ pattern, don't touch auth_service.
-O: [drafts run/merchant-notifications/intent-spec.md] Sign-off: gate or soft? (default gate)
-U: gate → approved
-
-## Phase 1 — Planning
-O: Planner? U: OpenSpec
-O: [6 tasks with declared_files incl. tests + per-file grounding attestations + sliced acceptance[], depends_on, spec_ref] ⚠ T1/T2 share models/notification.ts → scheduling separates them.
-   Grounding spot-check (Phase 1 exit): globs all `exists` paths — 13/14 present, models/notifcation.ts MISSING (typo) → plan bounced to planner with the miss list → corrected to models/notification.ts ✓.
-
-## Phase 2 — Effort, dispatch style, scoring
-O: Refined: medium, partially dependent. Recommend PARALLEL waves. Confirm? U: yes. Batch pause? U: every 2 waves.
-O: Facet scoring (planner facets → formula → band; facet gate: breadth + fan recomputed, risk cites checked):
-   T1 3·new-surface·stateful·new-tests·fan0/3·low = 6+18+16+8+9 = 57 → sonnet-5-high (keystone — every later task imports its enum)
-   T2 3·imitate·branching·new-tests·fan1/0·low = 6+8+8+8+5 = 35 → sonnet-4-6-med
-   T3 3·imitate·branching·update-existing·fan1/0·low = 6+8+8+4+5 = 31 → sonnet-4-6-med
-   T4 2·imitate·branching·update-existing·fan1/0·low = 6+8+8+4+5 = 31 → sonnet-4-6-med
-   T5 1·mechanical·none·update-existing·fan0/0·low = 2+0+0+4 = 6 → haiku-4-5
-   T6 1·mechanical·none·none·fan0/0·low = 2+0+0+0 = 2 → haiku-4-5
-   Plan: 6 tasks, 3 waves W1{T1} W2{T2,T3,T4} W3{T5,T6}, all spawned. Anticipated escalations? U: none, go.
-
-## Phase 3 — Execution (ALL spawned; orchestrator coordinates only)
-O: [checkpoint + state-of-play written into run/merchant-notifications/ BEFORE dispatch]
-▶ W1: spawn Agent-A(T1, sonnet-5-high) — milestones 40%→100% — return validated ✓ (evidence: `yarn jest models/` exit 0, tail quoted; unmet[] empty) — log: DECISION type enum.
-▶ W2: spawn 3 agents (sonnet-4-6-med each).
-   Agent-C needs_context (1/2): "needs T1's enum interface" → O adjudicates in-scope → re-slices → resumes. (User never bothered.)
-   Agent-C user escalation: "digest send time?" → U: 07:00 fixed → ANSWER broadcast to log.
-   Returns validated ✓ · collision audit clean.
-⏸ BATCH PAUSE (stop sequence):
-   checkpoint ✓ → state-of-play ✓ → dispatch report shown (models/scores) → "Run /usage to see your remaining limits."
-   → resume block:
-   | Continue ORC run `merchant-notifications`.
-   | Read run/merchant-notifications/state-of-play.md, then run/merchant-notifications/checkpoint.json.
-   | Resume from checkpoint phase/wave. Intent-spec approved — do not re-plan. Do not redo done tasks.
-   "Reply continue here, or paste in a fresh session (recommended if long)."
-
-U: [next day, FRESH session, pastes block]
-O: [state-of-play → checkpoint → re-anchored] "Resuming: merchant notifications (in-app+digest+prefs). Still correct?" U: yes.
-▶ W3: spawn T5+T6 (haiku-4-5) → done. All 6 complete.
-
-## Phase 5 — Review (spawned worker, Opus 5 medium)
-O: Code pattern? U: none. Findings (P0–P3 ladder, each P0–P2 anchored file:line + verbatim quote):
-   P1 T2 no pagination — services/notification_list.ts:88 — O spot-checks: Reads line 88, quote matches ✓ → asks user, U: fix it
-   · P3 email_digest naming ×2 · 12 tests added. (An unanchored finding would be auto-P3 — never fixed unasked.)
-
-## Phase 6 — Verify (spawned worker, Opus 5 medium; criteria = definition-of-done)
-   criteria[] with per-line evidence: bell ✓ (test name) · both schedules ✗ (weekly cron missing = P0, unmet criterion, evidence: no cron entry in scheduler.ts) · prefs ✓ → FAILED → quote spot-check ✓ → P0 auto-fix (single attempt, no ask) → re-verify → PASSED. 14/14.
-
-## Phase 7 — Summary
-O: 6 tasks/3 waves/6 spawns/1 pause/1 fresh-session resume · 1 needs_context · 1 escalation · verify fixed_then_passed · branch green. P2 fix-batch: none · Apply the 2 P3 cosmetics? U: no.
-
-## Phase 8 — Ship (orc-pr, reads pr.md)
-O: Branch: feat/notifications. Commit? Push? PR? U: yes all.
-O: Ticket/title/target? U: DRP-482 / Add merchant notification system / develop
-O: ✓ committed → pushed → run/merchant-notifications/DRP-482-add-merchant-notification-system.md from pr.md (base develop).
-   Log deleted · checkpoint + dispatch log KEPT · completion dispatch report shown → "Run /usage to see your remaining limits."
-
-## What this exercises
-always-spawn (even cheap tasks get a subagent) · facet-scored arithmetic · 6-band ladder ·
-per-run folder run/merchant-notifications/ · usage reminder (no programmatic /usage) ·
-planner grounding spot-check catching a hallucinated path · executor evidence (verbatim
-build/test proof) · reviewer quote spot-check before any P0/P1 action ·
-definition-of-done catching the weekly-cron gap · needs_context resolved internally · fresh-session resume.
+# Example — Annotated Full Run (v2.2, dry run)
+
+O: = orchestrator (Opus 4.8 high, always) · U: = user. Nothing real. The
+orchestrator NEVER implements — it always spawns scored subagents.
+
+U: Orchestrate: merchant notification system — in-app, email digest, prefs page.
+
+## Phase 0 — Intake
+O: Creates run folder run/merchant-notifications/ FIRST.
+   [reads repo: TS/yarn/jest — asks nothing about stack] Rough size: medium+ → 4-question tier (one batched round):
+   1) What should exist when done? 2) Out of scope? 3) How do we know it's done? 4) Patterns/files to avoid?
+U: [answers] no push, no admin; bell count + both digest schedules + prefs persist; follow services/ pattern, don't touch auth_service.
+O: [drafts run/merchant-notifications/intent-spec.md] Sign-off: gate or soft? (default gate)
+U: gate → approved
+
+## Phase 1 — Planning
+O: Planner? U: OpenSpec
+O: [6 tasks with declared_files incl. tests + per-file grounding attestations + sliced acceptance[], depends_on, spec_ref] ⚠ T1/T2 share models/notification.ts → scheduling separates them.
+   Grounding spot-check (Phase 1 exit): globs all `exists` paths — 13/14 present, models/notifcation.ts MISSING (typo) → plan bounced to planner with the miss list → corrected to models/notification.ts ✓.
+
+## Phase 2 — Effort, dispatch style, scoring
+O: Refined: medium, partially dependent. Recommend PARALLEL waves. Confirm? U: yes. Batch pause? U: every 2 waves.
+O: Facet scoring (planner facets → formula → band; facet gate: breadth + fan recomputed, risk cites checked):
+   T1 3·new-surface·stateful·new-tests·fan0/3·low = 6+18+16+8+9 = 57 → sonnet-5-high (keystone — every later task imports its enum)
+   T2 3·imitate·branching·new-tests·fan1/0·low = 6+8+8+8+5 = 35 → sonnet-4-6-med
+   T3 3·imitate·branching·update-existing·fan1/0·low = 6+8+8+4+5 = 31 → sonnet-4-6-med
+   T4 2·imitate·branching·update-existing·fan1/0·low = 6+8+8+4+5 = 31 → sonnet-4-6-med
+   T5 1·mechanical·none·update-existing·fan0/0·low = 2+0+0+4 = 6 → haiku-4-5
+   T6 1·mechanical·none·none·fan0/0·low = 2+0+0+0 = 2 → haiku-4-5
+   Plan: 6 tasks, 3 waves W1{T1} W2{T2,T3,T4} W3{T5,T6}, all spawned. Anticipated escalations? U: none, go.
+
+## Phase 3 — Execution (ALL spawned; orchestrator coordinates only)
+O: [checkpoint + state-of-play written into run/merchant-notifications/ BEFORE dispatch]
+▶ W1: spawn Agent-A(T1, sonnet-5-high) — milestones 40%→100% — return validated ✓ (evidence: `yarn jest models/` exit 0, tail quoted; unmet[] empty) — log: DECISION type enum.
+▶ W2: spawn 3 agents (sonnet-4-6-med each).
+   Agent-C needs_context (1/2): "needs T1's enum interface" → O adjudicates in-scope → re-slices → resumes. (User never bothered.)
+   Agent-C user escalation: "digest send time?" → U: 07:00 fixed → ANSWER broadcast to log.
+   Returns validated ✓ · collision audit clean.
+⏸ BATCH PAUSE (stop sequence):
+   checkpoint ✓ → state-of-play ✓ → dispatch report shown (models/scores) → "Run /usage to see your remaining limits."
+   → resume block:
+   | Continue ORC run `merchant-notifications`.
+   | Read run/merchant-notifications/state-of-play.md, then run/merchant-notifications/checkpoint.json.
+   | Resume from checkpoint phase/wave. Intent-spec approved — do not re-plan. Do not redo done tasks.
+   "Reply continue here, or paste in a fresh session (recommended if long)."
+
+U: [next day, FRESH session, pastes block]
+O: [state-of-play → checkpoint → re-anchored] "Resuming: merchant notifications (in-app+digest+prefs). Still correct?" U: yes.
+▶ W3: spawn T5+T6 (haiku-4-5) → done. All 6 complete.
+
+## Phase 5 — Review (spawned worker, Opus 5.5 medium)
+O: Code pattern? U: none. Findings (P0–P3 ladder, each P0–P2 anchored file:line + verbatim quote):
+   P1 T2 no pagination — services/notification_list.ts:88 — O spot-checks: Reads line 88, quote matches ✓ → asks user, U: fix it
+   · P3 email_digest naming ×2 · 12 tests added. (An unanchored finding would be auto-P3 — never fixed unasked.)
+
+## Phase 6 — Verify (spawned worker, Opus 5.5 medium; criteria = definition-of-done)
+   criteria[] with per-line evidence: bell ✓ (test name) · both schedules ✗ (weekly cron missing = P0, unmet criterion, evidence: no cron entry in scheduler.ts) · prefs ✓ → FAILED → quote spot-check ✓ → P0 auto-fix (single attempt, no ask) → re-verify → PASSED. 14/14.
+
+## Phase 7 — Summary
+O: 6 tasks/3 waves/6 spawns/1 pause/1 fresh-session resume · 1 needs_context · 1 escalation · verify fixed_then_passed · branch green. P2 fix-batch: none · Apply the 2 P3 cosmetics? U: no.
+
+## Phase 8 — Ship (orc-pr, reads pr.md)
+O: Branch: feat/notifications. Commit? Push? PR? U: yes all.
+O: Ticket/title/target? U: DRP-482 / Add merchant notification system / develop
+O: ✓ committed → pushed → run/merchant-notifications/DRP-482-add-merchant-notification-system.md from pr.md (base develop).
+   Log deleted · checkpoint + dispatch log KEPT · completion dispatch report shown → "Run /usage to see your remaining limits."
+
+## What this exercises
+always-spawn (even cheap tasks get a subagent) · facet-scored arithmetic · 6-band ladder ·
+per-run folder run/merchant-notifications/ · usage reminder (no programmatic /usage) ·
+planner grounding spot-check catching a hallucinated path · executor evidence (verbatim
+build/test proof) · reviewer quote spot-check before any P0/P1 action ·
+definition-of-done catching the weekly-cron gap · needs_context resolved internally · fresh-session resume.