mandrel 1.91.0 → 1.93.0

package/.agents/workflows/helpers/plan-story.md

@@ -41,9 +41,9 @@ If a Story-under-Epic needs replanning, use `/plan <epicId> --force`. If you
 have a refactor, framework-maintenance idea, or any standalone unit of
 work, use this workflow.
 
-**Inbound from `/plan` scope triage.** `/plan` Phase 1.5 runs the
-[`core/scope-triage`](../../skills/core/scope-triage/SKILL.md) rubric over the
-sharpened one-pager. On a `story` / `borderline` verdict the operator may route
+**Inbound from `/plan` scope triage.** The Epic path's interrogate step runs
+the [`core/scope-triage`](../../skills/core/scope-triage/SKILL.md) rubric over
+the sharpened one-pager. On a `story` / `borderline` verdict the operator may route
 the work here via `/plan --from-notes <path>`. That invocation is a
 **scope-triage handoff** — the triage decision is already made, so `/plan`
 MUST NOT re-triage it (the no-re-triage rule in the skill); it proceeds straight
@@ -116,7 +116,7 @@ when there is nothing to surface.
 (or empty). Pass `--refine` / `--no-refine` to override. When the
 envelope advises refinement, activate the
 [`core/idea-refinement`](../../skills/core/idea-refinement/SKILL.md) skill
-before drafting the body — same skill `/plan` Phase 1 drives.
+before drafting the body — same skill the Epic path's interrogate step drives.
 
 ## Phase 2 — Host LLM Authors a Draft Body
 
@@ -155,11 +155,11 @@ Check `corpusContext` before authoring the `## Context` section:
 
 Write the draft to `temp/single-story-draft.md`.
 
-### Scope-triage escalation gate (symmetric counterpart to `/plan` Phase 1.5)
+### Scope-triage escalation gate (symmetric counterpart to the Epic path's ideation triage)
 
 This gate runs the shared scope-triage gate over the **drafted Story body** to
 catch an Epic-sized scope before it is persisted as a standalone Story — the
-outbound mirror of `/plan` Phase 1.5's inbound downgrade gate. The gate
+outbound mirror of the Epic path's inbound downgrade gate. The gate
 mechanics (verdict meanings, the three-way operator choice, the `--yes`
 resolution, and the no-re-triage rule) live in the single-homed fragment
 [`scope-triage-gate.md`](scope-triage-gate.md); read it and follow it. This
@@ -172,13 +172,13 @@ phase supplies only its path-specific firing conditions:
   `refine` heuristic in `story-plan.js` is unchanged — it is a deterministic
   seed-length proxy, not a scope-size judgment.)
 - **When it is skipped**: entirely, when `/plan` was entered via a scope-triage
-  handoff — from `/plan` Phase 1.5 (the inbound route above) or the `/plan`
-  Phase 5.5 existing-Epic conversion path (the no-re-triage rule in the
+  handoff — from the Epic path's ideation triage (the inbound route above) or
+  its existing-Epic story-sized conversion path (the no-re-triage rule in the
   fragment).
 - **Recommended branch on an `epic` verdict**: escalate to `/plan --idea` —
   persist the notes/draft to a notes file and hand off to `/plan --idea` (or
   `--from-notes <path>`), identifying the invocation as a scope-triage handoff
-  so `/plan` skips its own Phase 1.5 gate, then **abandon the draft and exit
+  so `/plan` skips its own ideation triage gate, then **abandon the draft and exit
   `/plan`** (no standalone Story is created). The alternative branches are
   **persist as a standalone Story anyway** (proceed to Phase 3 with the draft
   unchanged) and **abort**.
@@ -186,8 +186,8 @@ phase supplies only its path-specific firing conditions:
 ### HITL — operator confirms the draft (verdict folded in)
 
 Display the draft to the operator and **STOP**. Do not call the persist phase
-until the operator explicitly confirms the draft. This mirrors the HITL gate
-`/plan` Phase 3 enforces before opening the Epic Issue. This is the
+until the operator explicitly confirms the draft. This mirrors the Epic
+path's gate #1 at the exit of its interrogate step. This is the
 story-path face of `/plan`'s **gate #1** (the ideation one-pager /
 scope-triage confirm). The scope-triage verdict folds into this same stop, per
 the branch bindings above; on a **`story` verdict (or gate skipped via
@@ -229,8 +229,8 @@ exact `gh issue create` shape that would run.
 ## Constraints
 
 - **No `Epic: #N` references.** This is the standalone contract; persist
-  fails fast if one is present. To attach a Story to an Epic, use
-  `/plan` Phase 8 instead.
+  fails fast if one is present. To attach a Story to an Epic, plan it
+  through the Epic path (`/plan <epicId>`) instead.
 - **No external LLM APIs.** Mirrors the v5.6 contract: the host LLM does
   the authoring; the Node wrapper does the I/O.
 - **Idempotent.** Re-running `--emit-context` is safe. Re-running
@@ -245,7 +245,7 @@ exact `gh issue create` shape that would run.
 
 - [`/single-story-deliver`](single-story-deliver.md) — the consumer
   workflow that picks the Story up after this one creates it.
-- [`/plan`](plan-epic.md) — the Epic-tier equivalent. Phases 1–4
+- [`/plan`](plan-epic.md) — the Epic-tier equivalent. Its ideation entry
   inspired the seed-capture + envelope-emit pattern used here.
 - [`core/idea-refinement`](../../skills/core/idea-refinement/SKILL.md) —
   optional pre-authoring skill activated when the seed is short.

package/.agents/workflows/helpers/scope-triage-gate.md

@@ -11,7 +11,8 @@ caller: plan-epic.md, plan-story.md
 
 > **Not a slash command.** This file lives in `helpers/` and is a
 > path-included fragment (not projected into the plugin command tree). It is
-> referenced by [`plan-epic.md`](plan-epic.md) (Phases 1.5 and 5.5) and
+> referenced by [`plan-epic.md`](plan-epic.md) (its interrogate step — the
+> ideation triage and the existing-Epic story-sized advisory) and
 > [`plan-story.md`](plan-story.md) (Phase 2), which supply only their
 > path-specific firing conditions and defer the gate mechanics here.
 
@@ -44,7 +45,7 @@ The rubric emits exactly one verdict:
   presented so the operator makes the call.
 
 The verdict is **advisory**. Being wrong in the `epic` direction is cheap
-(Phase 8.3 consolidation and the sizing validator catch an over-planned Story
+(the consolidation critic and the sizing validator catch an over-planned Story
 later), so the gate never costs the operator a stop on an `epic` verdict; the
 gate exists to avoid the ceremony tax of pushing a story-sized scope through
 the full Epic pipeline.
@@ -86,11 +87,21 @@ meanings; it only forces the Recommended resolution where the gate would
 otherwise STOP. See
 [`plan.md` § Headless / non-interactive mode](../plan.md#headless--non-interactive-mode---yes).
 
+**Headless seed entry — the verdict is already in the envelope (#4496).**
+On the `--idea` `--yes` path the rubric is applied **CLI-side** by
+`plan-context.js --seed` and shipped as the envelope's `scopeTriage` field
+(`{ verdict, reasons, advisory: true, appliedBy: "cli" }`), anchored to the
+same sizing SSOT this skill anchors to. Do **not** Read the
+`core/scope-triage` skill headless — use the envelope verdict and resolve it
+per this section. The attended paths keep the skill-based judgment
+unchanged.
+
 ## No-re-triage rule
 
 A **scope-triage handoff** is a triage decision *already made*. When `/plan` is
-entered via a handoff (from the ideation-path Phase 1.5, the existing-Epic
-Phase 5.5 conversion, or the standalone-Story Phase 2 escalation), the
+entered via a handoff (from the Epic path's ideation triage, its
+existing-Epic story-sized conversion, or the standalone-Story Phase 2
+escalation), the
 receiving path **MUST NOT** re-run this gate. Re-triaging a settled call would
 re-litigate it and risk a ping-pong between the two `/plan` paths. Each
 referencing path states its own skip-on-handoff condition and defers the

package/.agents/workflows/helpers/single-story-deliver.md

@@ -351,13 +351,14 @@ When the watch exits, branch on the exit code:
   commit on `story-<storyId>`, then re-watch. Auto-merge stays enabled
   across retries; no need to re-arm it. The Story stays at
   `agent::closing` throughout, so a failed/abandoned PR never strands a
-  CLOSED issue. If the same failure class recurs, hand convergence off to
-  the host loop: `/loop /loops:fix-failing-tests`.
+  CLOSED issue. If the same failure class recurs, hand convergence off to a
+  self-paced host loop (`/loop`) that re-runs the failing check and applies
+  the smallest fix until it exits green.
 - **Exit 2 (still-running — slow CI, not red)** — the poll cap fired with
   checks still pending and the watcher exhausted its resume budget with
   nothing red. This is **never** a failure. Hand the wait off to the
-  host's interval loop rather than ending your turn:
-  `/loop 5m /loops:watch-ci`.
+  host's interval loop rather than ending your turn: `/loop 5m` polling
+  `gh pr checks` until the checks settle.
 
 > **Triage authority.** How to classify and remediate a red (or repeatedly
 > slow) check — the root-cause-only decision tree for infra/transient and

package/.agents/workflows/helpers/worktree-lifecycle.md

@@ -102,7 +102,7 @@ or stale locks.
 
 `.worktrees/.pending-cleanup.json` accumulates entries when
 `story-close.js` cannot remove a worktree on Windows because of an
-EBUSY-class lock. Plan boot ([`drainPendingCleanupAtBoot`](../../scripts/epic-plan-spec.js) → [`worktree-sweep.js`](../../scripts/lib/orchestration/plan-runner/worktree-sweep.js))
+EBUSY-class lock. Plan boot ([`drainPendingCleanupAtBoot`](../../scripts/lib/orchestration/epic-plan-spec/phases/drain.js), run by `plan-persist.js` → [`worktree-sweep.js`](../../scripts/lib/orchestration/plan-runner/worktree-sweep.js))
 retries the entries — but if the holder
 is a long-lived user-mode process (a stranded test runner, a lingering
 biome/tsc, a node REPL), the lock never clears and the entry pins.
@@ -127,7 +127,7 @@ PowerShell `Get-CimInstance Win32_Process`, terminating them with
 | Trigger          | Caller                                                                       |
 | ---------------- | ---------------------------------------------------------------------------- |
 | `/deliver`    | [`Cleaner` lifecycle listener](../../scripts/lib/orchestration/lifecycle/listeners/cleaner.js) at the close-tail cleanup phase (before `wm.gc()`)   |
-| `/plan`     | [`drainPendingCleanupAtBoot`](../../scripts/epic-plan-spec.js) → [`worktree-sweep.js`](../../scripts/lib/orchestration/plan-runner/worktree-sweep.js) |
+| `/plan`     | [`drainPendingCleanupAtBoot`](../../scripts/lib/orchestration/epic-plan-spec/phases/drain.js) (run by `plan-persist.js`) → [`worktree-sweep.js`](../../scripts/lib/orchestration/plan-runner/worktree-sweep.js) |
 | Story merge close | [`story-close.js`](../../scripts/story-close.js) (`drainPendingCleanupAfterClose`) |
 
 All automatic paths call `forceDrainPendingCleanup()` (or are folded into
@@ -242,7 +242,8 @@ Symlink strategy:
   content-addressable store at `~/.local/share/pnpm/store` (or the platform
   equivalent) — reused packages are hard-linked into the worktree instead of
   re-downloaded and re-extracted. First-run on a cold store is no faster than
-  `per-worktree`, and `epic-plan-healthcheck.js` primes the store in the
+  `per-worktree`, and the plan healthcheck (`epic-plan-healthcheck.js
+  --prime-install`, an opt-in manual run) primes the store in the
   main checkout to avoid paying that cost in parallel story windows.
 
 ## Windows notes
@@ -334,8 +335,9 @@ Set `delivery.worktreeIsolation.enabled: false` (or omit the block) to
 restore v5.5.1 single-tree behavior:
 
 - No `git worktree add` / `remove` calls.
-- `assert-branch.js` and `computeStoryWaves` focus-area serialization remain in
-  place as the primary race guards.
+- The native `git branch --show-current` pre-commit check and
+  `computeStoryWaves` focus-area serialization remain in place as the primary
+  race guards.
 - All existing v5.5.1 tests pass in this mode.
 
 Pick single-tree mode when:
@@ -370,8 +372,8 @@ Human reviewers should **keep using the main checkout** — not a worktree:
 - **Always** use the main checkout for code review — not a per-story worktree.
 - **Always** respect `delivery.worktreeIsolation.enabled: false` as a
   first-class fallback mode, not a degraded one. v5.5.1 single-tree guards
-  (`assert-branch.js`, focus-area serialization) remain the primary defense in
-  that mode.
+  (the `git branch --show-current` pre-commit check, focus-area serialization)
+  remain the primary defense in that mode.
 
 ## Operator escape hatches