mandrel 2.37.0 → 2.38.0

package/.agents/workflows/{deliver.md → mandrel-deliver.md}

@@ -5,7 +5,7 @@ description:
   deliver-story engine — story-<id> → PR → main.
 ---
 
-# /deliver
+# /mandrel-deliver
 
 > **Lean spine.** Happy path + gate list. Sequencing, dispatch mechanics,
 > intent phrases, ceremony and the epilogue live in on-demand
@@ -16,7 +16,7 @@ description:
 
 ## Role
 
-One delivery door. `/deliver` owns input resolution, sequencing and the
+One delivery door. `/mandrel-deliver` owns input resolution, sequencing and the
 close-and-land tail; Stories are implemented via
 [`helpers/deliver-story.md`](helpers/deliver-story.md).
 
@@ -32,11 +32,11 @@ you read:
 
 | Invocation | Shape | Behavior |
 | --- | --- | --- |
-| `/deliver` | bare | List the open `agent::ready` Stories and ask which to deliver. Deliver nothing until answered. |
-| `/deliver 4712` | ids | One Story via `helpers/deliver-story.md`, **inline in this session** — no `story-worker` spawn. |
-| `/deliver 4712 4713 …` | ids | Resolve the set, sequence by the discovered graph via `stories-wave-tick.js`, dispatch sub-agents. |
-| `/deliver 4712 - 4716` | ids | A **range** — every id in the inclusive span. |
-| `/deliver add a --json flag to doctor` | prompt | Unplanned work: gate, author a receipt Story, land it — [`helpers/deliver-light.md`](helpers/deliver-light.md). |
+| `/mandrel-deliver` | bare | List the open `agent::ready` Stories and ask which to deliver. Deliver nothing until answered. |
+| `/mandrel-deliver 4712` | ids | One Story via `helpers/deliver-story.md`, **inline in this session** — no `story-worker` spawn. |
+| `/mandrel-deliver 4712 4713 …` | ids | Resolve the set, sequence by the discovered graph via `stories-wave-tick.js`, dispatch sub-agents. |
+| `/mandrel-deliver 4712 - 4716` | ids | A **range** — every id in the inclusive span. |
+| `/mandrel-deliver add a --json flag to doctor` | prompt | Unplanned work: gate, author a receipt Story, land it — [`helpers/deliver-light.md`](helpers/deliver-light.md). |
 
 **The discriminator is lexical and total.** An argument matching `^#?\d+$` is an
 id, and `^#?\d+\s*[-–—]\s*#?\d+$` an inclusive **range** — pass one on as a
@@ -92,14 +92,10 @@ it to an operator or add it to an attended run.
    - **0** — dispatch each `ready` id (already capped and overlap-free); an
      empty `ready` with work in flight means "waiting", so keep looping;
      `epilogueDue: true` means every Story is done — step 4.
-   - **2** — `cycleError`: the graph is self-referential; fix `depends_on`, do
-     not retry. **3** — `wedged`: nothing dispatchable, nothing in flight, the
-     undone Stories and their unmet blockers named; land a blocker or add it to
-     `--ids`. **4** — `blocked`: a Story carries `agent::blocked` with
-     `blockedReason`, the protocol's HITL pause
-     ([`instructions.md` § 1.J](../instructions.md)) — **stop the loop and
-     surface it; do not poll**, resuming once the operator unblocks it. Blocked
-     outranks a wedge, not a cycle.
+   - **2 / 3 / 4** — `cycleError` / `wedged` / `blocked`: stop the loop and
+     route per reference § Sequencing edge cases. **4** is the protocol's HITL
+     pause ([`instructions.md` § 1.J](../instructions.md)) — surface it and
+     wait for the operator; never poll.
 
 4. **Close each hand-off** (§ Closing what the workers hand back), then, with
    every Story landed, run the **per-run epilogue (N>1)**:
@@ -143,13 +139,13 @@ it): reference § Ceremony.
 - **Land or block — never a silent local build** (digest § 2). Attended delivers
   default to close-and-land (`delivery.routing.closeAndLand: true`); rest at
   `agent::closing` only when a human owns it.
-- **`/deliver` never plans.** Planned tickets come from [`/plan`](plan.md), and
-  an over-scope prompt **escalates and ends** — never invoke `/plan` in this
+- **`/mandrel-deliver` never plans.** Planned tickets come from [`/mandrel-plan`](mandrel-plan.md), and
+  an over-scope prompt **escalates and ends** — never invoke `/mandrel-plan` in this
   session to rescue it ([`helpers/deliver-light.md`](helpers/deliver-light.md)
   § Escalation is terminal).
 
 ## See also
 
-[`/plan`](plan.md), [`helpers/deliver-story.md`](helpers/deliver-story.md) (the
+[`/mandrel-plan`](mandrel-plan.md), [`helpers/deliver-story.md`](helpers/deliver-story.md) (the
 engine), [`helpers/deliver-light.md`](helpers/deliver-light.md) (the unplanned
-prompt path, shared with `/plan` Gate #1).
+prompt path, shared with `/mandrel-plan` Gate #1).

package/.agents/workflows/{plan.md → mandrel-plan.md}

@@ -5,7 +5,7 @@ description:
   policy.
 ---
 
-# /plan
+# /mandrel-plan
 
 > **Lean spine.** Happy path + gate list; edge-case detail lives on demand in
 > [`helpers/plan-reference.md`](helpers/plan-reference.md).
@@ -18,11 +18,11 @@ it, act**:
 
 | Invocation | Mode | Behavior |
 | --- | --- | --- |
-| `/plan` | ask | Ask what to plan; nothing runs first. |
-| `/plan add a --json flag to doctor` | seed | Ideation from prose: interrogate → author **one Story by default** → persist. |
-| `/plan temp/notes/idea.md` | seed-file | Same, from notes. An existing file is a path, not prose. |
-| `/plan 4712[,4713…]` | tickets | Fetch issue(s), analyze into proper Stories (prefer N=1 rewrite). |
-| `/plan 4712`, already delivered | amends | Amend a shipped Story from a **delta envelope**, not a re-interrogation. |
+| `/mandrel-plan` | ask | Ask what to plan; nothing runs first. |
+| `/mandrel-plan add a --json flag to doctor` | seed | Ideation from prose: interrogate → author **one Story by default** → persist. |
+| `/mandrel-plan temp/notes/idea.md` | seed-file | Same, from notes. An existing file is a path, not prose. |
+| `/mandrel-plan 4712[,4713…]` | tickets | Fetch issue(s), analyze into proper Stories (prefer N=1 rewrite). |
+| `/mandrel-plan 4712`, already delivered | amends | Amend a shipped Story from a **delta envelope**, not a re-interrogation. |
 
 **Resolving a bare id.** Read live state rather than asking: `agent::done` can
 only be amended, an open unplanned issue can only be planned. **Announce the
@@ -156,14 +156,14 @@ JSON. Tickets mode also comments on and closes each source id
 
 ## Constraints
 
-- `/plan` starts delivery **only** through a confirmed Gate #1 light route —
-  never off its own authored Stories, which land via [`/deliver`](deliver.md).
+- `/mandrel-plan` starts delivery **only** through a confirmed Gate #1 light route —
+  never off its own authored Stories, which land via [`/mandrel-deliver`](mandrel-deliver.md).
 - Duplicate search targets open Stories (`type::story`), not Epics; and
   deterministic gates still fail closed under `--yes`.
 
 ## See also
 
-[`/deliver`](deliver.md), [`/audit-to-stories`](audit-to-stories.md),
+[`/mandrel-deliver`](mandrel-deliver.md), [`/audit-to-stories`](audit-to-stories.md),
 [`helpers/plan-reference.md`](helpers/plan-reference.md) (on-demand detail),
 [`core/scope-triage`](../skills/core/scope-triage/SKILL.md) — optional
 split-advisory notes only (no routing verdict).

package/.agents/workflows/memory-consolidate.md

@@ -2,7 +2,7 @@
 description: >-
   Attended consolidation pass over this project's agent memory pool — merge
   duplicates, verify claims against the current tree, prune with operator
-  confirmation, rewrite the index, and stamp the pool so the /plan advisory
+  confirmation, rewrite the index, and stamp the pool so the /mandrel-plan advisory
   goes quiet.
 ---
 
@@ -96,7 +96,7 @@ Then write the receipt to `.consolidation-stamp.json` in the pool root:
 { "lastConsolidatedAt": "<ISO-8601 timestamp>" }
 ```
 
-The `/plan` Phase 0 advisory reads this file; until it is written, the nudge
+The `/mandrel-plan` Phase 0 advisory reads this file; until it is written, the nudge
 keeps firing. Write it **only** after Gate #2 — the stamp asserts an operator
 reviewed the pass, so writing it early makes it a lie.
 
@@ -112,5 +112,5 @@ Close with counts: entries read, corrected, merged, pruned, and the new total.
 
 ## See also
 
-[`/plan`](plan.md) (surfaces the advisory at its Gate #1),
-[`/deliver`](deliver.md) (point-of-write corrections as work lands).
+[`/mandrel-plan`](mandrel-plan.md) (surfaces the advisory at its Gate #1),
+[`/mandrel-deliver`](mandrel-deliver.md) (point-of-write corrections as work lands).

package/.agents/workflows/prototype.md

@@ -13,7 +13,7 @@ active runs" says nothing about layout, density, or interaction, so delivery
 resolves those by taste. `/prototype` puts a reviewable artifact in front of the
 operator before the criteria are written.
 
-**Operator-invoked only.** `/plan` may report that a plan touches UI and that
+**Operator-invoked only.** `/mandrel-plan` may report that a plan touches UI and that
 this command exists; it must never run it. No workflow, gate, or script invokes
 `/prototype` — the whole design rests on the operator asking for it.
 
@@ -89,7 +89,7 @@ documentation-freshness gate already carries that failure mode.
 - **One file, under the temp tree.** Never a second artifact, never outside the
   gitignored workspace-root temp tree, and never a committed prototype
   directory by default.
-- **Never invoked automatically.** `/plan` records the offer and proceeds with
+- **Never invoked automatically.** `/mandrel-plan` records the offer and proceeds with
   planning; no workflow, gate, or script may call this command.
 - **Read-only over the codebase.** The prototype file is the only write. Do not
   edit application source, tokens, or components to make a prototype render.
@@ -100,5 +100,5 @@ documentation-freshness gate already carries that failure mode.
 
 - [`/audit-ux-ui`](audit-ux-ui.md) — the same design-system SSOT discovery,
   applied as a review lens after the UI ships.
-- [`/plan`](plan.md) — where the advisory `complexitySignals.uiSurface` offer
+- [`/mandrel-plan`](mandrel-plan.md) — where the advisory `complexitySignals.uiSurface` offer
   surfaces. It names this command; it never runs it.

package/.agents/workflows/qa-assist.md

@@ -1,5 +1,5 @@
 ---
-description: Human-led QA assist loop — set up, then ride a rolling multi-observation intake session. The operator reports observations in any order; the agent enriches each (repro + root-cause file:line + coverage verdict for bugs; analysis + options + recommendation for enhancements), asks clarifying questions only when ambiguous, and appends a redacted ledger item — recording, never planning — to a persistent, resumable session under temp/qa/. Only when the operator says they are done does it review the full ledger and hand off to /plan.
+description: Human-led QA assist loop — set up, then ride a rolling multi-observation intake session. The operator reports observations in any order; the agent enriches each (repro + root-cause file:line + coverage verdict for bugs; analysis + options + recommendation for enhancements), asks clarifying questions only when ambiguous, and appends a redacted ledger item — recording, never planning — to a persistent, resumable session under temp/qa/. Only when the operator says they are done does it review the full ledger and hand off to /mandrel-plan.
 ---
 
 # /qa-assist
@@ -21,7 +21,7 @@ high-quality, triage-ready ledger. The session has four movements:
    a final review of the **entire** ledger and asks any last clarifying
    questions.
 4. **Triage & Plan** (Phase 4) — only then does it route the full ledger through
-   [`/plan`](plan.md) to generate Stories.
+   [`/mandrel-plan`](mandrel-plan.md) to generate Stories.
 
 Unlike [`/qa-explore`](qa-explore.md) (where the *agent* drives open-ended
 exploration of a named surface), `/qa-assist` is **human-led**: the human owns
@@ -89,12 +89,12 @@ rolling loop stays fluid:
   to **ask clarifying questions when the observation is ambiguous**. After each
   append it **echoes the recorded item** for correction, then **loops back** for
   the next observation. It does **not** triage, route, file tickets, or invoke
-  `/plan` during intake.
+  `/mandrel-plan` during intake.
 - **Two things always require explicit operator confirmation** (the HITL write
   gate in [`helpers/qa-core.md`](helpers/qa-core.md)). First, the session-level
   transition into **Phase 4 — Triage & Plan** — the operator must say they are
   done. Second, **every write that leaves the local ledger** — filing a ticket,
-  invoking `/plan`, or mutating a label. Present the artifact, ask, and wait.
+  invoking `/mandrel-plan`, or mutating a label. Present the artifact, ask, and wait.
 
 In short: appending to the rolling ledger is the natural product of intake and
 needs no gate beyond the echo-back; **planning and anything that leaves the
@@ -198,7 +198,7 @@ every decision to the shared helpers; never re-derive them in prose.
 ## Phase 3 — Record (per observation), then loop
 
 Goal: persist the enriched finding to the rolling ledger and **return to
-intake**. **No triage, routing, ticket-filing, or `/plan` happens here** — that
+intake**. **No triage, routing, ticket-filing, or `/mandrel-plan` happens here** — that
 is Phase 4, and only after the operator says they are done.
 
 1. **Append a `QaLedgerItem`** to the ledger (shape per
@@ -232,17 +232,17 @@ its transition is **explicitly operator-gated**.
 2. **Triage the ledger** through the shared classify → route → disposition →
    promote procedure in [`helpers/qa-core.md`](helpers/qa-core.md): dedup/route
    each `file` finding against open + closed Issues, then promote the
-   `file`-dispositioned findings through `promoteFindings` → `/plan` (never a raw
+   `file`-dispositioned findings through `promoteFindings` → `/mandrel-plan` (never a raw
    Issue), stamping each cluster's `fingerprintFooter(sha)` into the seed.
    `defer` carries an item forward as backlog; `dismiss` marks it non-actionable.
 3. **Gate:** the move into this phase, and every write inside it (seed write,
-   `/plan` invocation, ticket-filing, label mutation), is **operator-gated** —
+   `/mandrel-plan` invocation, ticket-filing, label mutation), is **operator-gated** —
    confirm each one. The plan→deliver hard stop is preserved; redaction has
    already run, so nothing unredacted reaches disk or GitHub.
 
 After planning, summarize: the findings recorded, the route/promotion decisions
 (`new`/`update-existing`/`duplicate`/`regression-of-closed`), whether each
-cluster became a Story via `/plan --seed-file`, and any `defer` backlog a
+cluster became a Story via `/mandrel-plan --seed-file`, and any `defer` backlog a
 resumed session will pick up.
 
 ---
@@ -259,7 +259,7 @@ the `/qa-assist`-specific deltas are:
   records each. **Never invent an observation**; ask clarifying questions only
   when one is ambiguous, batched across the dump.
 - **Record during intake; plan only on "done".** Phases 1–3 enrich, append, and
-  loop — never triage, route, file, or invoke `/plan`. All of that is Phase 4,
+  loop — never triage, route, file, or invoke `/mandrel-plan`. All of that is Phase 4,
   entered only on explicit operator confirmation that testing is done.
 - **Light intake gate, firm boundary gate.** Intake → Enrich → Record is fluid
   (echo-back, no ceremony); the move into Phase 4 and every write that leaves the
@@ -275,11 +275,11 @@ the `/qa-assist`-specific deltas are:
 
 ## See also
 
-- [`/plan`](plan.md) — the planning pipeline `/qa-assist` chains into in Phase 4.
+- [`/mandrel-plan`](mandrel-plan.md) — the planning pipeline `/qa-assist` chains into in Phase 4.
   The plan→deliver hard stop is preserved across the handoff.
 - [`/qa-explore`](qa-explore.md) — the agent-led sibling that drives a named
-  surface and triages through the same `/plan` handoff.
+  surface and triages through the same `/mandrel-plan` handoff.
 - [`/audit-to-stories`](audit-to-stories.md) — the precedent for the
-  findings → `/plan` handoff and the shared fingerprint-footer dedup contract.
+  findings → `/mandrel-plan` handoff and the shared fingerprint-footer dedup contract.
 - [`helpers/qa-core.md`](helpers/qa-core.md) — the shared contract/session/
   redaction/QaLedgerItem/triage/HITL core.

package/.agents/workflows/qa-explore.md

@@ -31,7 +31,7 @@ workflow states only the `/qa-explore`-specific phases (Plan / Capture) plus a
 Constraints delta.
 
 > **When to run**: ad-hoc agent-driven exploration of a freshly delivered Story
-> or Feature, a regression sweep over a risky surface before `/deliver`, or a
+> or Feature, a regression sweep over a risky surface before `/mandrel-deliver`, or a
 > structured agent-driven bug-hunt captured into a triageable ledger.
 >
 > **Skills**: `core/qa-coverage-mapping`, `stack/qa/qa-explore-driving`
@@ -198,14 +198,14 @@ For each observation the agent makes while driving:
 Route the captured ledger through the shared classify → route → disposition →
 promote procedure in [`helpers/qa-core.md`](helpers/qa-core.md), with the
 operator deciding each `file` / `defer` / `dismiss` and every write
-operator-gated. `file` findings are promoted through `/plan` (never a raw
+operator-gated. `file` findings are promoted through `/mandrel-plan` (never a raw
 Issue); `defer` carries an item forward as backlog; `dismiss` marks it
 non-actionable.
 
 After triage, write the updated dispositions back to the ledger (still under
 `temp/qa/`), and summarize: items captured, the driving method used, classes,
 routes (`new`/`update-existing`/`duplicate`/`regression-of-closed`), the
-Stories (`/plan --seed-file`) promoted, and the deferred rolling backlog a
+Stories (`/mandrel-plan --seed-file`) promoted, and the deferred rolling backlog a
 resumed session will pick up.
 
 ---
@@ -238,11 +238,11 @@ the `/qa-explore`-specific deltas are:
 
 ## See also
 
-- [`/plan`](plan.md) — the planning pipeline Triage chains into for a
+- [`/mandrel-plan`](mandrel-plan.md) — the planning pipeline Triage chains into for a
   `file`-dispositioned finding. The plan→deliver hard stop is preserved.
 - [`/qa-assist`](qa-assist.md) — the human-led sibling that enriches a single
-  operator observation and triages through the same `/plan` handoff.
+  operator observation and triages through the same `/mandrel-plan` handoff.
 - [`/audit-to-stories`](audit-to-stories.md) — the precedent for the
-  findings → `/plan` handoff and the shared fingerprint-footer dedup contract.
+  findings → `/mandrel-plan` handoff and the shared fingerprint-footer dedup contract.
 - [`helpers/qa-core.md`](helpers/qa-core.md) — the shared contract/session/
   redaction/QaLedgerItem/triage/HITL core.

package/.agents/workflows/qa-run.md

@@ -26,7 +26,7 @@ the agent never invents those decisions in prose.
 
 > **When to run**: during sprint testing to exercise a targeted slice of the
 > acceptance suite (a feature, a tag expression, or a domain), for regression
-> passes before `/deliver`, or on demand while debugging a Story's
+> passes before `/mandrel-deliver`, or on demand while debugging a Story's
 > user-visible behavior in a live browser.
 >
 > **Skills**: `stack/qa/gherkin-authoring`, `stack/qa/playwright-bdd`

package/README.md

@@ -30,26 +30,26 @@ provisions both as part of a cold start (`git init` → `gh repo create --push`
 The canonical cold-start path is one command, then one slash command:
 
 ```bash
-npx mandrel init        # install mandrel → sync → prompt → bootstrap → onboarding tail → /plan handoff
+npx mandrel init        # install mandrel → sync → prompt → bootstrap → onboarding tail → /mandrel-plan handoff
 ```
 
 ```text
 # then, inside Claude Code (commands load from .claude/commands/):
-/plan --seed "…"   # interrogate → author one Story (default) → persist
-/deliver <id>      # story-<id> → PR → main
+/mandrel-plan --seed "…"   # interrogate → author one Story (default) → persist
+/mandrel-deliver <id>      # story-<id> → PR → main
 ```
 
 `npx mandrel init` installs `mandrel` (when `./.agents/` is absent),
 materializes it via `mandrel sync`, then asks whether to **configure now**
 (option 1 → runs `bootstrap.js`, then the onboarding tail: stack detection,
-docs scaffolding offer, `mandrel doctor` readiness gate, and a `/plan`
+docs scaffolding offer, `mandrel doctor` readiness gate, and a `/mandrel-plan`
 handoff) or stop at **just the files** (option 2 → re-run `mandrel init`
 any time to configure). Pass `--assume-yes` for a non-interactive run that
 proceeds straight to configure (and forwards the flag to bootstrap). When
 `./.agents/` is already present (you ran `npm install mandrel` first), `init`
 skips the install/sync and goes straight to the prompt. Once `mandrel init`
-completes, you land at the `/plan` handoff — run `/plan --seed "<idea>"` to
-author your first Story, then deliver it with `/deliver <storyId>`
+completes, you land at the `/mandrel-plan` handoff — run `/mandrel-plan --seed "<idea>"` to
+author your first Story, then deliver it with `/mandrel-deliver <storyId>`
 (`story-<id>` → PR → `main`).
 
 ### Manual equivalent
@@ -164,7 +164,7 @@ npx mandrel doctor                      # verify the install
 Mandrel's effectiveness is measured by a separate companion repo,
 **[mandrel-bench](https://github.com/dsj1984/mandrel-bench)** — a *consumer* of
 the published `mandrel` package. It pins a specific framework version,
-materializes it via `mandrel sync`, and drives Mandrel's own `/plan`→`/deliver`
+materializes it via `mandrel sync`, and drives Mandrel's own `/mandrel-plan`→`/mandrel-deliver`
 pipeline (plus a bare-model control) over a scenario corpus. Each run is scored
 across five dimensions — Quality, Planning fidelity, and Autonomy (what the
 scaffolding *buys*) versus Efficiency and Overhead ratio (what it *costs*) —

package/docs/CHANGELOG.md

@@ -15,6 +15,17 @@ All notable changes to this project will be documented in this file.
 -->
 <!-- markdownlint-disable-file MD004 MD012 MD037 -->
 
+## [2.38.0](https://github.com/dsj1984/mandrel/compare/mandrel-v2.37.0...mandrel-v2.38.0) (2026-09-04)
+
+
+### ⚠ BREAKING CHANGES
+
+* the `/plan` and `/deliver` slash commands are renamed to `/mandrel-plan` and `/mandrel-deliver`. Run `mandrel sync` (or `npm run sync:commands`) to reap the old command files and project the new ones. No `/plan` or `/deliver` alias remains.
+
+### Added
+
+* rename /plan and /deliver to /mandrel-plan and /mandrel-deliver ([#5126](https://github.com/dsj1984/mandrel/issues/5126)) ([#5127](https://github.com/dsj1984/mandrel/issues/5127)) ([945d8de](https://github.com/dsj1984/mandrel/commit/945d8de4a41aeca7adc89c009a0252f5bb5387b4))
+
 ## [2.37.0](https://github.com/dsj1984/mandrel/compare/mandrel-v2.36.0...mandrel-v2.37.0) (2026-09-03)
 
 

package/lib/cli/doctor.js

@@ -122,7 +122,7 @@ export function formatClosureReport({
 
 /**
  * Best-effort write of the doctor verdict to `temp/doctor-result.json` under
- * the consumer root so downstream workflows (e.g. the `/plan` first-run
+ * the consumer root so downstream workflows (e.g. the `/mandrel-plan` first-run
  * preflight) can read the last recorded verdict without re-running doctor.
  * `temp/` is the gitignored scratch root, so neither git nor the sync prune
  * pass ever sees the cache. Any write failure is swallowed — the cache is

package/lib/cli/init.js

@@ -299,7 +299,7 @@ export async function planInit({
     }
 
     // Bootstrap succeeded — run the onboarding tail: stack detection, docs
-    // scaffolding offer, doctor gate, and /plan handoff. A tail that reports
+    // scaffolding offer, doctor gate, and /mandrel-plan handoff. A tail that reports
     // `ok: false` (the doctor gate failed) makes the whole init exit
     // non-zero; the tail already printed its own remediation message, and the
     // earlier install/sync/bootstrap phases' results stand as completed.

package/lib/migrations/steps/2.2.0-retire-epic-ac-tags.js

@@ -4,7 +4,7 @@
  * from consumer feature files.
  *
  * The v2 Epic removal deleted `acceptance-spec-reconciler.js`, the only
- * consumer of the namespaced per-Epic AC tags, and the `/plan` authoring
+ * consumer of the namespaced per-Epic AC tags, and the `/mandrel-plan` authoring
  * prompt no longer mandates them. Surviving tags in consumer `.feature`
  * files are inert and violate the gherkin-standards tag taxonomy's
  * no-ad-hoc-tags rule, so this step removes them: each `@epic-<digits>-ac-<digits>`

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "mandrel",
-  "version": "2.37.0",
+  "version": "2.38.0",
   "description": "Claude Code-first opinionated workflow framework: instructions, skills, rules, and SDLC workflows that govern AI coding assistants.",
   "files": [
     ".agents/",