mandrel 2.37.0 → 2.38.0

package/.agents/scripts/lib/ticket-body-sections.js

@@ -12,7 +12,7 @@
  * Section-scoped writes are the load-bearing contract (extending the
  * single-writer discipline #4303 established for the body trailer):
  *
- *   - The `/plan` persist path upserts the `techSpec` and `acceptanceTable`
+ *   - The `/mandrel-plan` persist path upserts the `techSpec` and `acceptanceTable`
  *     regions.
  *   - The close-time acceptance reconciler
  *     (`acceptance-spec-reconciler.js`) reads and rewrites the

package/.agents/scripts/lib/util/concurrent-map.js

@@ -16,7 +16,7 @@
 /**
  * The one bound every independent-write fan-out over the GitHub API uses
  * (Story #4952 raised those loops off serial; Story #4961 made this the single
- * owner of the number they share). Imported by the `/plan` context gathers,
+ * owner of the number they share). Imported by the `/mandrel-plan` context gathers,
  * the persist checkpoint fan-out, the `agent::ready` flips and the supersede
  * close loop, so re-tuning the policy is one edit rather than six.
  *

package/.agents/scripts/lib/util/parse-id-list.js

@@ -2,7 +2,7 @@
  * parse-id-list — expand a Story-id list that may contain dash ranges.
  *
  * Operators name a contiguous span of Stories the way they read one — as a
- * range: `/deliver 4922 - 4926`. Enumerating it by hand is the kind of
+ * range: `/mandrel-deliver 4922 - 4926`. Enumerating it by hand is the kind of
  * transcription step that silently drops or invents an id, so the range is a
  * first-class shape of every delivery id list rather than something the host
  * expands from prose.

package/.agents/scripts/lib/wave-runner/live-probe.js

@@ -7,7 +7,7 @@
  * in-flight count, and it decides. Until now the only adapter was the
  * flag-driven one (`stories-wave-tick.js --dag/--done/--in-flight`), which
  * pushed the *gathering* of those inputs onto the caller — in practice onto
- * the host LLM following `/deliver`'s prose, re-seeding `--done` and counting
+ * the host LLM following `/mandrel-deliver`'s prose, re-seeding `--done` and counting
  * `--in-flight` by hand every beat. That is hand-maintained accounting on the
  * one correctness-critical path where a mistake silently wedges a run (a
  * dropped foreign blocker) or double-dispatches a Story (a miscounted slot).
@@ -47,7 +47,7 @@
  * The graph resolution is **not** reimplemented here — it reuses
  * `resolve-stories.js`'s machinery wholesale (body `depends_on` ∪ native
  * `blocked_by` edges, foreign-blocker resolution, `files[]` footprints), so
- * the probe and `/deliver`'s step-1 resolution cannot disagree about what
+ * the probe and `/mandrel-deliver`'s step-1 resolution cannot disagree about what
  * depends on what.
  *
  * @module lib/wave-runner/live-probe
@@ -127,7 +127,7 @@ function deriveInFlightIds(storyRecords, dispatched = []) {
  * in-flight, so `detectWedge` dropped it (its "undone work with no unmet
  * blockers would have been dispatched" invariant is precisely what probe mode
  * broke) and the beat reported exit 0 / `ready: []` / `wedged: null` forever.
- * `/deliver` reads that as "waiting", so the `agent::blocked` HITL pause — the
+ * `/mandrel-deliver` reads that as "waiting", so the `agent::blocked` HITL pause — the
  * one runtime gate in the protocol — was never surfaced to the operator.
  *
  * @param {Array<{id?: number, number?: number, labels?: string[], state?: string}>} storyRecords
@@ -193,7 +193,7 @@ function deriveForeignHeld(storyRecords, self, warn) {
  * Resolve the provider + repo coordinates the probe reads through.
  *
  * Shares `resolve-stories.js`'s provider seam, so probe mode authenticates and
- * targets exactly the same repo `/deliver`'s resolution step does. Tests
+ * targets exactly the same repo `/mandrel-deliver`'s resolution step does. Tests
  * inject a stub provider instead of calling this.
  *
  * @param {object} [deps]

package/.agents/scripts/lib/wave-runner/ready-set.js

@@ -2,7 +2,7 @@
  * lib/wave-runner/ready-set.js — the path-agnostic ready-set scheduling
  * core.
  *
- * This module is the scheduling kernel the v2 `/deliver` multi-Story path
+ * This module is the scheduling kernel the v2 `/mandrel-deliver` multi-Story path
  * dispatches through (`stories-wave-tick.js`). It replaces wave-*batch* selection
  * (group N must fully drain before group N+1 opens) with *continuous*,
  * dependency-driven selection: a Story becomes dispatchable the instant

package/.agents/scripts/lib/workflow-closure.js

@@ -345,7 +345,7 @@ function loadDocs(root, fs) {
  * (`helpers/deliver-story.md` → `# /deliver-story …`). The self-naming test is
  * what separates an invocable helper from an appendix that merely titles itself
  * after the command it documents (`helpers/deliver-reference.md` →
- * `# /deliver — reference appendix`), which is read on demand, never invoked.
+ * `# /mandrel-deliver — reference appendix`), which is read on demand, never invoked.
  *
  * @param {WorkflowDoc} doc
  * @returns {boolean}

package/.agents/scripts/lib/worktree/lifecycle/pending-cleanup.js

@@ -7,7 +7,7 @@
  * on a Windows lock-class failure, the entry is appended to
  * `.worktrees/.pending-cleanup.json`. The plan-time `worktree-sweep.js`
  * reader (shipped in Epic #349) picks up the manifest on the next
- * `/plan` run and retries removal
+ * `/mandrel-plan` run and retries removal
  * (`git worktree remove` then `fs.rm`) — by then the live file handles from Node / AV / the Windows
  * Search indexer are almost always gone. If `MAX_SWEEP_ATTEMPTS` elapses
  * without clearing, an `OPERATOR ACTION REQUIRED: persistent-lock` line
@@ -17,7 +17,7 @@
  * git-ignored; no tracked state is mutated.
  *
  * **Story #5112 — the manifest is shared mutable state.** `recordPendingCleanup`
- * runs from the close reap and `drainPendingCleanup` runs from the `/plan`
+ * runs from the close reap and `drainPendingCleanup` runs from the `/mandrel-plan`
  * boot, so two concurrent delivery sessions can read-modify-write the same
  * file. Three properties close that:
  *

package/.agents/scripts/lint-issue-body.js

@@ -10,8 +10,8 @@
  * human files a ticket whose body `parse()` rejects (or which lacks the
  * binding `goal` / `acceptance` / `verify` sections), the lint surfaces a
  * **comment** on the issue rather than failing silently — the supported
- * human entry points (`/plan` from an existing Epic ID, the qa-assist →
- * `/plan` handoff) depend on a parseable body.
+ * human entry points (`/mandrel-plan` from an existing Epic ID, the qa-assist →
+ * `/mandrel-plan` handoff) depend on a parseable body.
  *
  * ## Design
  *
@@ -157,7 +157,7 @@ export function renderConformanceComment(verdict) {
     '### ⚠️ Ticket body does not round-trip through the Mandrel parser',
     '',
     'Agents build ticket bodies from a canonical schema that this body does ' +
-      'not match, so the supported human entry points (e.g. `/plan` from an ' +
+      'not match, so the supported human entry points (e.g. `/mandrel-plan` from an ' +
       'existing Epic ID) will reject it. Please fix the following:',
     '',
     ...verdict.problems.map((p) => `- ${p}`),

package/.agents/scripts/plan-context.js

@@ -2,9 +2,9 @@
 /* node:coverage ignore file */
 
 /**
- * plan-context.js — step 1 of the collapsed `/plan` pipeline.
+ * plan-context.js — step 1 of the collapsed `/mandrel-plan` pipeline.
  *
- * Emits one stdout-pure JSON envelope for the `/plan` authoring middle.
+ * Emits one stdout-pure JSON envelope for the `/mandrel-plan` authoring middle.
  *
  * Two operator modes (exactly one is required):
  *
@@ -25,7 +25,7 @@
  *
  * Flags:
  *   --out <path>     Write the envelope to <path> (parent dirs created).
- *                    `/plan` points this at `<plan-dir>/plan-context.json`,
+ *                    `/mandrel-plan` points this at `<plan-dir>/plan-context.json`,
  *                    which is where `plan-persist.js` auto-discovers the
  *                    `--tickets` source ids from (Story #4554). Without a
  *                    captured envelope persist cannot know a `--tickets` run
@@ -348,7 +348,7 @@ runAsCli(import.meta.url, main, {
     invocation:
       'node .agents/scripts/plan-context.js (--seed "<text>" | --seed-file <path> | --tickets <ids> | --amends <id>) [--out <path>] [--pretty]',
     summary:
-      'Build the /plan authoring-context envelope on stdout. Exactly one entry form must be supplied.',
+      'Build the /mandrel-plan authoring-context envelope on stdout. Exactly one entry form must be supplied.',
     flags: [
       ['--seed "<text>"', 'Inline seed prose.'],
       ['--seed-file <path>', 'Seed document to read.'],

package/.agents/scripts/plan-critics.js

@@ -1,9 +1,9 @@
 #!/usr/bin/env node
 
 /**
- * plan-critics.js — the /plan critic-dispatch verdict CLI (Story #4592).
+ * plan-critics.js — the /mandrel-plan critic-dispatch verdict CLI (Story #4592).
  *
- * `/plan` step 2.5 (between Author and Persist) runs this against the draft
+ * `/mandrel-plan` step 2.5 (between Author and Persist) runs this against the draft
  * `stories.json`. It evaluates the consolidation + pre-mortem dispatch
  * conditions and prints the verdict as JSON on stdout so the workflow can
  * act on it — dispatching a fresh-context critic sub-agent and folding its

package/.agents/scripts/plan-persist.js

@@ -1,7 +1,7 @@
 #!/usr/bin/env node
 
 /**
- * plan-persist.js — flat Story GitHub-write surface for v2 `/plan`
+ * plan-persist.js — flat Story GitHub-write surface for v2 `/mandrel-plan`
  * (Stage 3 — `docs/roadmap.md`).
  *
  * Given the author-written planning artifacts (`stories.json`, optional shared
@@ -201,7 +201,7 @@ async function loadArtifacts(paths) {
  *
  * Exported for tests: this is the join where the envelope-derived source ids
  * meet the persist engine, so a regression here silently un-wires
- * `/plan --tickets` superseding (Story #4554).
+ * `/mandrel-plan --tickets` superseding (Story #4554).
  *
  * @param {object} values Parsed `parseArgs` values.
  * @param {ReturnType<typeof resolveInputPaths>} paths

package/.agents/scripts/plan-run-epilogue.js

@@ -1,7 +1,7 @@
 #!/usr/bin/env node
 /**
  * plan-run-epilogue.js — execute the real per-run closeout for a
- * multi-Story `/deliver`.
+ * multi-Story `/mandrel-deliver`.
  *
  * Usage:
  *   node .agents/scripts/plan-run-epilogue.js --stories 1,2,3
@@ -67,7 +67,7 @@ export async function main(argv = process.argv.slice(2), deps = {}) {
   // along with the label itself. The epilogue is keyed on the delivered id
   // set, and the synthesized `adhoc-<ids>` id it already used for positional
   // runs is now the only id it needs.
-  // Range tokens expand here too (`--stories 101-104`): /deliver blesses the
+  // Range tokens expand here too (`--stories 101-104`): /mandrel-deliver blesses the
   // dash range at the operator surface, so the id set the epilogue is keyed on
   // must read the same shape. Rejecting a bad token is deliberate — the old
   // silent filter turned a typo into an empty, wrongly-keyed rollup.

package/.agents/scripts/providers/github/board-add.js

@@ -3,7 +3,7 @@
  *
  * Story #3822 — single source of truth for the post-create board-add
  * step. Issues created through any create path (`createTicket`,
- * `createIssue` — which backs `/plan` persist and the `/plan`
+ * `createIssue` — which backs `/mandrel-plan` persist and the `/mandrel-plan`
  * Phase 4 Epic open) must land on the configured Projects V2 board
  * without relying on GitHub's "Auto-add to project" built-in workflow,
  * which is off by default on fresh boards and cannot be enabled via API.

package/.agents/scripts/providers/github/errors.js

@@ -156,7 +156,7 @@ export function classifyGithubError(err) {
 // Read-path callers (paginateRest, getTicket, getNativeSubIssues, …) all
 // absorb the same jittered exponential backoff on transient GitHub errors
 // through this one primitive, instead of bubbling a one-shot
-// 502/429/ECONNRESET that kills a longer pipeline (e.g. the /deliver
+// 502/429/ECONNRESET that kills a longer pipeline (e.g. the /mandrel-deliver
 // Phase E retro). The network consumers repointed here
 // (branch-protection, labels, projects-v2-graphql) call with no opts, so
 // they adopt these defaults; their retry *classes* (the network blips) are

package/.agents/scripts/providers/github/tickets.js

@@ -15,7 +15,7 @@
  * Epic-hierarchy write surface. It composed the exact `Epic: #N` footer that
  * `pr-base-guard.js` hard-refuses at delivery, so the framework retained the
  * ability to generate work it would then reject; it had no production caller
- * (`/plan` persists through the bare `createIssue` below).
+ * (`/mandrel-plan` persists through the bare `createIssue` below).
  *
  * Public surface: `GitHubProvider.createIssue / getTicket /
  * getTickets / updateTicket / getTicketDependencies / primeTicketCache /
@@ -251,8 +251,8 @@ export class TicketGateway {
 
   /**
    * Create a **bare** issue — no footer composition and no sub-issue link.
-   * Since Story #4545 this is the *only* create path: `/plan` persist and the
-   * `/plan` Phase 4 Epic open (`openEpicFromOnePager`'s `createIssue` port)
+   * Since Story #4545 this is the *only* create path: `/mandrel-plan` persist and the
+   * `/mandrel-plan` Phase 4 Epic open (`openEpicFromOnePager`'s `createIssue` port)
    * both route through it.
    *
    * After the POST, the new issue is added to the configured Project V2
@@ -264,13 +264,13 @@ export class TicketGateway {
    * The POST is wrapped in `withTransientRetry` (Story #4541) so it absorbs
    * the same 502/429/ECONNRESET blips the read surfaces already do. It used
    * to post bare, which made a single transient failure at story *k* of *N*
-   * abort `/plan` persist with `1..k-1` already live on the tracker.
+   * abort `/mandrel-plan` persist with `1..k-1` already live on the tracker.
    *
    * Retry alone is not sufficient for that failure mode — a POST whose
    * response is lost would double-create on the retry. Story #5112 closed
    * that: `findExisting` is consulted **before every retry POST**, and a hit
    * is adopted instead of re-created, so a response-lost first attempt files
-   * exactly one issue. `/plan` persist supplies the plan-fingerprint lookup
+   * exactly one issue. `/mandrel-plan` persist supplies the plan-fingerprint lookup
    * its resume path already uses (`plan-persist`'s `createStoryIssues`);
    * callers with no content identity omit it and keep the pre-#5112
    * retry-only behaviour.
@@ -405,7 +405,7 @@ export class TicketGateway {
    *
    * The additive POST goes through `withTransientRetry` (Story #4961) on the
    * same policy as every other call in this file. Story #4952 raised the
-   * `/plan` write loops that reach this endpoint — the `agent::ready` flips
+   * `/mandrel-plan` write loops that reach this endpoint — the `agent::ready` flips
    * and the checkpoint fan-out — off serial, which is precisely what makes
    * GitHub's secondary rate limit likelier; `gh-exec` already classifies that
    * as transient, so the only thing missing was a backoff behind it.

package/.agents/scripts/resolve-stories.js

@@ -2,9 +2,9 @@
 
 /**
  * resolve-stories.js — resolve a list of Story ids into the
- * `{ stories, dag, done }` envelope `/deliver` sequences from.
+ * `{ stories, dag, done }` envelope `/mandrel-deliver` sequences from.
  *
- * This is the ONE resolution step for multi-Story delivery. `/deliver` takes
+ * This is the ONE resolution step for multi-Story delivery. `/mandrel-deliver` takes
  * only Story ids; the graph is discovered here, from live state, rather than
  * hand-transcribed by the host or implied by a batch label.
  *
@@ -63,7 +63,7 @@ const HELP = `\
 Usage:
   resolve-stories.js --ids <n,n,...> [--pretty] [--no-native]
 
-Resolve Story ids into the { stories, dag, done } envelope /deliver sequences
+Resolve Story ids into the { stories, dag, done } envelope /mandrel-deliver sequences
 from. Dependencies are discovered from live state: body edges union native
 blocked_by edges, with every blocker (in-set or foreign) resolved against its
 real issue state.

package/.agents/scripts/resync-status-column.js

@@ -5,7 +5,7 @@
  * resync-status-column.js — re-assert the GitHub Projects v2 Status
  * column for a ticket after auto-merge has fired (Story #2845).
  *
- * The `/single-story-deliver` and `/deliver` workflow docs call
+ * The `/single-story-deliver` and `/mandrel-deliver` workflow docs call
  * this CLI after Step 5 confirms `state: "MERGED"` so the orchestrator
  * wins the race against the GitHub built-in `Pull request merged`
  * workflow, which would otherwise overwrite Status to whatever value

package/.agents/scripts/run-lint.js

@@ -84,7 +84,7 @@ const tasks = [
   nodeGate('lifecycle-lint', '.agents/scripts/check-lifecycle-lint.js'),
   // Workflow prose surface (Epic #4474 PR5). No workflow may instruct calling
   // an exported library function that has no CLI entrypoint — the measured
-  // shim-writing failure mode the /plan collapse killed. See
+  // shim-writing failure mode the /mandrel-plan collapse killed. See
   // check-workflow-cli-lint.js for the paragraph-level heuristic.
   nodeGate('workflow-cli-lint', '.agents/scripts/check-workflow-cli-lint.js'),
   // Label-vocabulary citations in `.agents/docs/SDLC.md` and

package/.agents/scripts/single-story-close.js

@@ -1,9 +1,9 @@
 #!/usr/bin/env node
 
 /**
- * single-story-close.js — Close a Story against `main` (v2 `/deliver` path).
+ * single-story-close.js — Close a Story against `main` (v2 `/mandrel-deliver` path).
  *
- * Thin CLI entry for `/deliver` / `helpers/deliver-story`. Opens a PR from
+ * Thin CLI entry for `/mandrel-deliver` / `helpers/deliver-story`. Opens a PR from
  * `story-<id>` to `project.baseBranch`, runs Story-scope review, and arms
  * auto-merge. There is no Epic parent, epic-merge-lock, or wave merge.
  *

package/.agents/scripts/single-story-init.js

@@ -2,7 +2,7 @@
 /* node:coverage ignore file */
 
 /**
- * single-story-init.js — Initialize a Story for v2 `/deliver`.
+ * single-story-init.js — Initialize a Story for v2 `/mandrel-deliver`.
  *
  * Seeds `story-<id>` from `project.baseBranch` (default `main`), materialises
  * the per-Story worktree when isolation is enabled, upserts a `story-init`
@@ -122,7 +122,7 @@ export function assertDeliverableStory(story, storyId) {
   if (!story.labels.includes(TYPE_LABELS.STORY)) {
     throw new Error(
       `Issue #${storyId} is not a Story (labels: ${story.labels.join(', ')}). ` +
-        'v2 /deliver accepts type::story tickets only.',
+        'v2 /mandrel-deliver accepts type::story tickets only.',
     );
   }
   if (story.state === 'closed') {
@@ -132,7 +132,7 @@ export function assertDeliverableStory(story, storyId) {
   if (/\b(?:Epic|Parent):\s*#\d+/i.test(body)) {
     throw new Error(
       `Story #${storyId} still declares an Epic/Parent footer. ` +
-        'v2 delivery is Story-only — re-plan as a standalone Story before /deliver.',
+        'v2 delivery is Story-only — re-plan as a standalone Story before /mandrel-deliver.',
     );
   }
 }
@@ -189,7 +189,7 @@ export async function assertNotForeignExecuting({
       (lease.previousOwner
         ? ` (assignee @${lease.previousOwner})`
         : ' with no assignee') +
-      '. Another /deliver run may already own it. Confirm that run is dead, ' +
+      '. Another /mandrel-deliver run may already own it. Confirm that run is dead, ' +
       'then re-run with --steal to take it.',
   );
 }
@@ -607,7 +607,7 @@ export async function runSingleStoryInit({
   );
   progress('INIT', `Initializing standalone Story #${storyId}...`);
 
-  // Issue #4483 — deterministic remote evidence at the v2 `/deliver` entry
+  // Issue #4483 — deterministic remote evidence at the v2 `/mandrel-deliver` entry
   // seam (`single-story-init.js`). The
   // probe is read-only, so it runs under --dry-run too. The CLI records
   // the fact; the workflow owns the `agent::blocked` transition on

package/.agents/scripts/stories-wave-tick.js

@@ -2,7 +2,7 @@
 
 /**
  * stories-wave-tick.js — continuous ready-set planner for the standalone
- * `/deliver` story-list path.
+ * `/mandrel-deliver` story-list path.
  *
  * Thin **adapter** over the path-agnostic ready-set scheduling core
  * (`lib/wave-runner/ready-set.js#planReadySet`). It emits the set of
@@ -21,7 +21,7 @@
  * **Two modes, one kernel.**
  *
  *   - **Probe mode** (`--stories <csv> --probe-live [--dispatched <csv>]`) is
- *     the canonical `/deliver` beat: the graph, the done set, and the in-flight
+ *     the canonical `/mandrel-deliver` beat: the graph, the done set, and the in-flight
  *     count are resolved from **live state** via `lib/wave-runner/live-probe.js`.
  *     The caller supplies ids, so there is no accounting to hand-maintain
  *     across beats — the seed-the-first-beat's-`--done` footgun the workflow
@@ -97,14 +97,14 @@
  * `--done` and `ready` is empty.
  *
  * The per-beat concurrency cap is resolved from the same config seam
- * `/deliver` uses — `resolveConfig` + `getRunners` reading
+ * `/mandrel-deliver` uses — `resolveConfig` + `getRunners` reading
  * `delivery.deliverRunner.concurrencyCap` (default 3) — so a
  * `.agentrc.local.json` override is honored. A `--concurrency <n>` CLI flag
  * overrides the config-resolved value for that run only, and the envelope's
  * `capPrecedence` names which source won so the override is never silent
  * (Story #4875). This shares one
  * deterministic config source (`delivery.deliverRunner.concurrencyCap`) and
- * one scheduling kernel with every `/deliver` multi-Story invocation.
+ * one scheduling kernel with every `/mandrel-deliver` multi-Story invocation.
  *
  * Exit codes: 0 ok · 1 input error · 2 dependency cycle (`cycleError`) ·
  * 3 wedged (`wedged`) — ready is empty, nothing is in flight, and undone
@@ -170,7 +170,7 @@ and the same file-overlap guard as planReadySet.
 
 Two modes:
   --probe-live  Resolve the graph and derive done / in-flight from LIVE state
-                (the canonical /deliver beat). Nothing is hand-maintained
+                (the canonical /mandrel-deliver beat). Nothing is hand-maintained
                 across beats. Mutually exclusive with --dag/--dag-file/--done/
                 --in-flight. Adds "done" and "epilogueDue" to the envelope.
   --dag         Legacy flag mode: the caller supplies the graph and the run
@@ -662,7 +662,7 @@ export function parseConcurrencyOverride(raw) {
 /**
  * Resolve the per-beat concurrency cap.
  *
- * Mirrors the `/deliver` multi-Story seam (`helpers/deliver-story.md`): resolve the
+ * Mirrors the `/mandrel-deliver` multi-Story seam (`helpers/deliver-story.md`): resolve the
  * project config (which deep-merges `.agentrc.local.json` over `.agentrc.json`)
  * then read `delivery.deliverRunner.concurrencyCap` via `getRunners` (default
  * 3). An explicit `override` (the `--concurrency <n>` CLI flag) wins over
@@ -855,7 +855,7 @@ export function buildReadySetEnvelope(
     return {
       envelope: {
         ...base,
-        cycleError: `Dependency cycle detected: ${cycle.join(' → ')}. Fix the depends_on declarations before running /deliver.`,
+        cycleError: `Dependency cycle detected: ${cycle.join(' → ')}. Fix the depends_on declarations before running /mandrel-deliver.`,
       },
       exitCode: 2,
     };
@@ -1087,7 +1087,7 @@ export function runStoriesWaveTick({
  *
  * This is the flag-free beat. The caller supplies only the Story ids it was
  * asked to deliver; `done` and `inFlight` are probed rather than transcribed,
- * which is what makes the `/deliver` loop's old seed-the-first-beat footgun
+ * which is what makes the `/mandrel-deliver` loop's old seed-the-first-beat footgun
  * structurally impossible instead of merely documented.
  *
  * The envelope is the flag mode's, plus three probe-only fields the caller can

package/.agents/skills/core/idea-refinement/SKILL.md

@@ -13,7 +13,7 @@ description:
 - Phase 1 MUST restate the idea as a "How Might We" statement, ask 3–5 sharpening questions via `AskUserQuestion`, and generate 5–8 variations (never 20+ shallow ones) — each carrying a reason it exists, told as a short story, not a bare bullet. Do not proceed until target user and success criteria are explicit.
 - Phase 2 grill loop poses **one** question at a time, each with a recommended answer + one-line rationale grounded in user input / codebase / first principles; never batch questions and never omit the recommendation.
 - Re-enumerate open branches after every grill answer; stop only when no unresolved decisions remain. Take the off-ramp directly to Phase 3 when the idea is already crisply scoped. A branch consciously deferred rather than resolved records its deferral reason.
-- Phase 3 emits a markdown one-pager with the canonical five planning headings exactly: `## Context`, `## Goal`, `## Non-Goals`, `## Scope`, `## Acceptance Criteria` (plus optional `## Open Questions`). No alternate heading text — the `/plan` clarity gate depends on this verbatim.
+- Phase 3 emits a markdown one-pager with the canonical five planning headings exactly: `## Context`, `## Goal`, `## Non-Goals`, `## Scope`, `## Acceptance Criteria` (plus optional `## Open Questions`). No alternate heading text — the `/mandrel-plan` clarity gate depends on this verbatim.
 - Surface every key assumption inside `## Context` (or `## Scope`); assumptions do not get their own heading. Unresolved decisions MUST NOT carry into the one-pager.
 - The `## Non-Goals` list is mandatory and each entry includes a reason — focus is created by explicit exclusion.
 - Be honest, not supportive: push back on weak ideas with kindness; never function as a yes-machine.
@@ -22,10 +22,10 @@ description:
 
 ## Activation
 
-Called from [`/plan`](../../../workflows/plan.md) during ideation when the
+Called from [`/mandrel-plan`](../../../workflows/mandrel-plan.md) during ideation when the
 operator supplies `--seed "<text>"` (or runs ideation with no seed and the host
 collects one interactively). The skill sharpens freeform intent into the
-canonical planning sections that `/plan` then folds into a Story. There is no
+canonical planning sections that `/mandrel-plan` then folds into a Story. There is no
 separate Epic Clarity Gate path in v2 — N=1 Story authoring with a folded
 `## Spec` is the lean default.
 
@@ -134,9 +134,9 @@ clothes — inside the grill loop, not after the one-pager is written.
 #### Phase 3: Sharpen & Ship
 
 Produce a markdown one-pager that moves work forward. The five canonical
-headings below match `.agents/templates/epic-from-idea.md` and the `/plan`
+headings below match `.agents/templates/epic-from-idea.md` and the `/mandrel-plan`
 clarity gate; emit them verbatim so the renderer can substitute the body into a
-`/plan` Story seed without translation.
+`/mandrel-plan` Story seed without translation.
 
 ```markdown
 # [Idea Name]

package/.agents/skills/core/scope-triage/SKILL.md

@@ -1,8 +1,8 @@
 ---
 name: scope-triage
 description:
-  Optional split-advisory for `/plan`. Under v2 there is no epic|story routing
-  verdict — `/plan` always authors Stories. Use this skill only when judging
+  Optional split-advisory for `/mandrel-plan`. Under v2 there is no epic|story routing
+  verdict — `/mandrel-plan` always authors Stories. Use this skill only when judging
   whether a draft should stay one Story or legitimately split (near-zero
   overlap or an architectural seam).
 ---
@@ -11,7 +11,7 @@ description:
 
 ## Policy Capsule
 
-- There is **no** `epic | story | borderline` routing verdict in v2. `/plan`
+- There is **no** `epic | story | borderline` routing verdict in v2. `/mandrel-plan`
   is a single path that emits **one Story by default**.
 - This skill is an optional **split advisory**: should the author keep one
   Story, or does the seed clear the default-single split policy?

package/.agents/skills/skills.index.json

@@ -97,7 +97,7 @@
       "tier": "core",
       "category": "core",
       "path": ".agents/skills/core/scope-triage/SKILL.md",
-      "description": "Optional split-advisory for `/plan`. Under v2 there is no epic|story routing verdict — `/plan` always authors Stories. Use this skill only when judging whether a draft should stay one Story or legitimately split (near-zero overlap or an architectural seam).",
+      "description": "Optional split-advisory for `/mandrel-plan`. Under v2 there is no epic|story routing verdict — `/mandrel-plan` always authors Stories. Use this skill only when judging whether a draft should stay one Story or legitimately split (near-zero overlap or an architectural seam).",
       "policyCapsuleBullets": 5,
       "allowedTools": null,
       "vendor": null

package/.agents/skills/stack/qa/qa-harness/SKILL.md

@@ -170,7 +170,7 @@ Record each `F#` finding as a `QaLedgerItem` on the shared session ledger under
 `temp/qa/`, then route the ledger through the shared classify → route →
 disposition → promote core — both stated once in
 [`qa-core.md`](../../../../workflows/helpers/qa-core.md). The harness **MUST
-NOT** create tickets autonomously: findings are promoted through `/plan` only
+NOT** create tickets autonomously: findings are promoted through `/mandrel-plan` only
 after the operator confirms each disposition at the HITL write gate. That gate
 is the safety boundary against spurious filing.
 

package/.agents/workflows/audit-data-model.md

@@ -27,7 +27,7 @@ than empty findings. The applicability probe (`hasPersistenceLayer` in
 [`lib/audit-suite/selector.js`](../scripts/lib/audit-suite/selector.js), gated
 by `target: "data-model"` in
 [`schemas/audit-rules.json`](../schemas/audit-rules.json)) makes this decision
-automatically in `/deliver` and plan-run modes; in a manual invocation you MUST
+automatically in `/mandrel-deliver` and plan-run modes; in a manual invocation you MUST
 make the same determination yourself before reading anything else.
 
 ## Scope

package/.agents/workflows/audit-documentation.md

@@ -188,7 +188,7 @@ auditable.
 ## Periodic full-scope sweep
 
 Context Economy findings accrete slowly — a doc that is lean today grows a
-bloated tail over many deliveries, and no single change-set-scoped `/deliver`
+bloated tail over many deliveries, and no single change-set-scoped `/mandrel-deliver`
 run sees the whole picture. Run this lens **full-scope** on a
 recurring cadence so the drift is caught before it compounds:
 
@@ -202,7 +202,7 @@ recurring cadence so the drift is caught before it compounds:
 Route the resulting `audit-documentation-results.md` through
 [`/audit-to-stories`](audit-to-stories.md), which groups the findings,
 deduplicates them against existing Issues by fingerprint, and opens
-remediation Stories (or chains into `/plan --seed`) so the Context-Economy
+remediation Stories (or chains into `/mandrel-plan --seed`) so the Context-Economy
 findings land as actionable, tracked work rather than a report nobody reads.
 
 ## Constraint (lens-specific carve-out)

package/.agents/workflows/audit-to-stories.md

@@ -3,7 +3,7 @@ description:
   Convert findings produced by the audit-* workflows into actionable
   GitHub Stories. Reads temp/audits/audit-*-results.md, groups findings
   cross-audit, deduplicates against existing Issues by fingerprint, and
-  either chains into /plan --seed-file or opens standalone Stories.
+  either chains into /mandrel-plan --seed-file or opens standalone Stories.
 ---
 
 # /audit-to-stories [audit-file-or-glob]
@@ -111,8 +111,8 @@ Ask:
 
 > How would you like these `<M>` Stories created?
 >
-> - **Single plan via `/plan`** **[Recommended]** — chains into
->   `/plan --seed-file <emitted.md>` so the standard Story authoring
+> - **Single plan via `/mandrel-plan`** **[Recommended]** — chains into
+>   `/mandrel-plan --seed-file <emitted.md>` so the standard Story authoring
 >   handles the seed. Prefer one Story; split only under the
 >   default-single policy.
 > - **Individual standalone Stories** — opens one GitHub Issue per
@@ -122,7 +122,7 @@ Ask:
 
 ## Phase 5a — Single-plan path
 
-Build the `/plan` seed from the filtered plan envelope:
+Build the `/mandrel-plan` seed from the filtered plan envelope:
 
 ```bash
 node .agents/scripts/audit-to-stories.js --emit-plan-seed \
@@ -132,16 +132,16 @@ node .agents/scripts/audit-to-stories.js --emit-plan-seed \
 
 The seed renders the canonical one-pager sections — Problem Statement,
 Recommended Direction, Key Assumptions (with links to every source
-report), MVP Scope (the M proposed Stories), Key Files (so `/plan`'s
+report), MVP Scope (the M proposed Stories), Key Files (so `/mandrel-plan`'s
 authoring step has concrete anchors), Not Doing.
 
 Chain into the existing planning entrypoint:
 
 ```text
-/plan --seed-file <path-to-seed>
+/mandrel-plan --seed-file <path-to-seed>
 ```
 
-(`/plan --seed "$(cat <path>)"` also works for small seeds). `/plan`
+(`/mandrel-plan --seed "$(cat <path>)"` also works for small seeds). `/mandrel-plan`
 then runs its author → persist path, as documented in its workflow.
 
 **Dedup provenance is carried mechanically — do not hand-copy it.** The seed's
@@ -210,9 +210,9 @@ every Story that has a resolvable blocker with a canonical
 GitHub `blocked_by` relations. An edge whose target was never opened (deduped,
 ledger-suppressed) drops rather than becoming a `blocked by #undefined`.
 
-**Do not skip this.** `/deliver` has no other source for this cohort's order:
+**Do not skip this.** `/mandrel-deliver` has no other source for this cohort's order:
 its footprint guard ignores the shared provenance footers, so an unwired cohort
-is genuinely unordered and `/deliver` will co-dispatch Stories the edges say
+is genuinely unordered and `/mandrel-deliver` will co-dispatch Stories the edges say
 must follow one another.
 
 ## Phase 6 — Idempotency (folded into Phase 1 scan)
@@ -288,7 +288,7 @@ summarising the run:
   · <L> skipped (re-occurring)"`.
 
 When the single-plan path ran, link the Story (or plan-run) the chained
-`/plan` opened. When the Standalone-Stories path ran, list every Issue URL.
+`/mandrel-plan` opened. When the Standalone-Stories path ran, list every Issue URL.
 
 ## Constraints
 
@@ -345,7 +345,7 @@ scheduler owns the cadence; this workflow owns the routing.
 
 ## See also
 
-- [`/plan`](plan.md) — the planning pipeline `/audit-to-stories`
+- [`/mandrel-plan`](mandrel-plan.md) — the planning pipeline `/audit-to-stories`
   chains into for Story creation.
 - [`lib/findings/route-finding.js`](../scripts/lib/findings/route-finding.js) —
   the shared fingerprint/dedup/route helper this workflow and `qa-explore`