mandrel 1.94.0 → 2.0.0

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

@@ -1,5 +1,5 @@
 {
-  "generatedAt": "2026-07-13T15:00:10.171Z",
+  "generatedAt": "2026-07-14T21:42:10.296Z",
   "generator": "generate-skills-index.js@1",
   "skills": [
     {
@@ -7,7 +7,7 @@
       "tier": "core",
       "category": "core",
       "path": ".agents/skills/core/analyze-execution/SKILL.md",
-      "description": "Aggregate per-Story or per-Epic execution signals into a structured perf-summary or perf-report and upsert it onto the corresponding GitHub ticket. Use after a Story closes (Story mode) or as part of `/deliver` Phase 6 (Epic mode). Reads NDJSON via `lib/signals/read` and writes a single structured comment.",
+      "description": "Aggregate per-Story or per-plan-run execution signals into a structured perf-summary or perf-report and upsert it onto the corresponding GitHub ticket. Use after a Story closes (Story mode) or during run closeout (plan-run mode). Reads NDJSON via `lib/signals/read` and writes a single structured comment.",
       "policyCapsuleBullets": 8,
       "allowedTools": ["Read", "Bash"],
       "vendor": null
@@ -72,46 +72,6 @@
       "allowedTools": null,
       "vendor": null
     },
-    {
-      "name": "epic-plan-consolidate",
-      "tier": "core",
-      "category": "core",
-      "path": ".agents/skills/core/epic-plan-consolidate/SKILL.md",
-      "description": "Run a holistic, pre-persist consolidation pass over the draft Story ticket array an Epic's decompose phase produced. Use during Phase 8 of `/plan`, after `epic-plan-decompose-author` writes `temp/epic-<Epic_ID>/tickets.json` and before `plan-persist.js` validates and persists it. Reconciles the draft against the Tech Spec \"Delivery Slicing\" ceiling via scope-preserving operations only.",
-      "policyCapsuleBullets": 9,
-      "allowedTools": ["Read", "Write", "Bash"],
-      "vendor": null
-    },
-    {
-      "name": "epic-plan-decompose-author",
-      "tier": "core",
-      "category": "core",
-      "path": ".agents/skills/core/epic-plan-decompose-author/SKILL.md",
-      "description": "Author the Story ticket JSON for an Epic from the decomposer authoring context emitted by `plan-context.js --epic <Epic_ID>`. Use during Phase 8 of `/plan` when the host LLM needs to write the ticket array before `plan-persist.js` validates and persists it.",
-      "policyCapsuleBullets": 15,
-      "allowedTools": ["Read", "Write", "Bash"],
-      "vendor": null
-    },
-    {
-      "name": "epic-plan-premortem",
-      "tier": "core",
-      "category": "core",
-      "path": ".agents/skills/core/epic-plan-premortem/SKILL.md",
-      "description": "Run a fresh-context, code-reading pre-mortem critic over the draft Story ticket array an Epic's decompose phase produced. Use during Phase 8 of `/plan`, after `epic-plan-decompose-author` / `epic-plan-consolidate` write `temp/epic-<Epic_ID>/tickets.json` and before `plan-persist.js` validates and persists it. Reads the sectioned Epic body AND the cited code surfaces, then emits predicted-rework findings before any GitHub write.",
-      "policyCapsuleBullets": 7,
-      "allowedTools": ["Read", "Write", "Bash", "Grep"],
-      "vendor": null
-    },
-    {
-      "name": "epic-plan-spec-author",
-      "tier": "core",
-      "category": "core",
-      "path": ".agents/skills/core/epic-plan-spec-author/SKILL.md",
-      "description": "Author the Tech Spec, Acceptance Table markdown, and risk-verdict JSON for an Epic from the planner authoring context emitted by `plan-context.js --epic <Epic_ID>`. Use during Phase 7 of `/plan` when the host LLM needs to write the three artifacts before `plan-persist.js` folds them into the Epic body's managed sections.",
-      "policyCapsuleBullets": 14,
-      "allowedTools": ["Read", "Write", "Bash"],
-      "vendor": null
-    },
     {
       "name": "gates-and-baselines",
       "tier": "core",
@@ -157,7 +117,7 @@
       "tier": "core",
       "category": "core",
       "path": ".agents/skills/core/scope-triage/SKILL.md",
-      "description": "Judge whether a piece of planned work is epic-sized or story-sized before the planning ceremony is paid for. Emits one of three verdicts — `epic` | `story` | `borderline` — over any planning artifact (a one-pager, an Epic body, or a Story draft). Use from `/plan` Phase 1.5 and any other planning gate that needs the canonical story-vs-epic rubric.",
+      "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).",
       "policyCapsuleBullets": 1,
       "allowedTools": null,
       "vendor": null

package/.agents/starter-agentrc.json

@@ -13,10 +13,5 @@
     "repo": "[REPO]",
     "operatorHandle": "@[USERNAME]",
     "projectNumber": null
-  },
-  "delivery": {
-    "ci": {
-      "skipForStoryPushes": true
-    }
   }
 }

package/.agents/templates/agent-protocol.md

@@ -5,14 +5,14 @@ Version: {{PROTOCOL_VERSION}}
 You are an AI coding assistant. This protocol governs your execution of the
 current work unit. You must follow these rules strictly.
 
-> **Hierarchy shape.** Mandrel uses a **2-tier hierarchy**
-> (Epic → Story). The work unit is the `type::story` issue
-> itself, with acceptance criteria and verification inlined on the
-> Story body. There is no per-Task sub-loop; the agent authors commit
+> **Hierarchy shape.** Mandrel uses a **Story-only** model. The work unit
+> is the `type::story` issue itself, with acceptance criteria and
+> verification inlined on the Story body and the folded Tech Spec in
+> `## Spec`. There is no per-Task sub-loop; the agent authors commit
 > subjects directly per `.agents/rules/git-conventions.md` and
-> references the parent Story via `(refs #<storyId>)`. Branch naming
-> (`{{BRANCH_NAME}}` from `{{EPIC_BRANCH}}`), the Epic-branch
-> integration target, and the close protocol are as documented below.
+> references the Story via `(refs #<storyId>)`. Branch naming
+> (`{{BRANCH_NAME}}` from `{{EPIC_BRANCH}}` / base), the PR target
+> (`main`), and the close protocol are as documented below.
 
 ## 1. Pre-Flight Verification
 
@@ -50,9 +50,8 @@ When your implementation is complete and verified:
    `{{TEST_CMD}}`) here. The close script's lint/test/format/maintainability
    chain is the authoritative gate, run at Story closure (`story-close.js`).
    Exception: you may run them interactively while iterating on a fix.
-3. The Story branch is auto-merged into the Epic branch by
-   `helpers/epic-deliver-story` (via `story-close.js`) — do **not** merge
-   manually.
+3. The Story branch is opened as a PR to `main` by `helpers/deliver-story`
+   (via `single-story-close.js`) — do **not** merge manually.
 
 ## 6. Definition of Done
 

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

@@ -70,10 +70,10 @@ degrade to the sequential path.
 > read/search tools (`Read`, `Grep`, `Glob`) — no write/edit/shell-mutation
 > tools. The single write in an orchestrated run is the final report artifact.
 
-## Scope (Epic mode)
+## Scope (Story / plan-run mode)
 
-When this lens is invoked from `/deliver` Phase 4 (epic-audit), the
-following block is populated with the Epic's change-set file list.
+When this lens is invoked from `/deliver` close lenses (or a plan-run audit), the
+following block is populated with the Story (or plan-run) change-set file list.
 Otherwise — for any manual `/audit-<dimension>` invocation — the block
 renders the literal substitution token and you MUST treat it as **no
 scope filter — run the lens codebase-wide** exactly as you would have

package/.agents/workflows/audit-clean-code.md

@@ -15,10 +15,10 @@ quality. Your objective is to identify "code smells," technical debt, and
 violations of clean code principles (SOLID, DRY, KISS) that hinder long-term
 velocity.
 
-## Scope (Epic mode)
+## Scope (Story / plan-run mode)
 
-When this lens is invoked from `/deliver` Phase 4 (epic-audit), the
-following block is populated with the Epic's change-set file list.
+When this lens is invoked from `/deliver` close lenses (or a plan-run audit), the
+following block is populated with the Story (or plan-run) change-set file list.
 Otherwise — for any manual `/audit-<dimension>` invocation — the block
 renders the literal substitution token and you MUST treat it as **no
 scope filter — run the lens codebase-wide** exactly as you would have

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

@@ -14,10 +14,10 @@ Manage the lifecycle of project dependencies. Your goal is to identify outdated,
 vulnerable, or bloated packages and suggest a safe upgrade path that maintains
 system stability.
 
-## Scope (Epic mode)
+## Scope (Story / plan-run mode)
 
-When this lens is invoked from `/deliver` Phase 4 (epic-audit), the
-following block is populated with the Epic's change-set file list.
+When this lens is invoked from `/deliver` close lenses (or a plan-run audit), the
+following block is populated with the Story (or plan-run) change-set file list.
 Otherwise — for any manual `/audit-<dimension>` invocation — the block
 renders the literal substitution token and you MUST treat it as **no
 scope filter — run the lens codebase-wide** exactly as you would have

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

@@ -15,10 +15,10 @@ infrastructure, developer experience (DX) tooling, and CI/CD pipelines. Your
 goal is to identify inefficiencies, security risks, and areas for modernization
 without making any immediate changes.
 
-## Scope (Epic mode)
+## Scope (Story / plan-run mode)
 
-When this lens is invoked from `/deliver` Phase 4 (epic-audit), the
-following block is populated with the Epic's change-set file list.
+When this lens is invoked from `/deliver` close lenses (or a plan-run audit), the
+following block is populated with the Story (or plan-run) change-set file list.
 Otherwise — for any manual `/audit-<dimension>` invocation — the block
 renders the literal substitution token and you MUST treat it as **no
 scope filter — run the lens codebase-wide** exactly as you would have

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

@@ -47,10 +47,10 @@ generator", not "edit the doc". Auto-generated changelog files
 (`docs/CHANGELOG.md`, release-please-owned) are likewise excluded from
 semantic review beyond Step 1's deterministic checks.
 
-## Scope (Epic mode)
+## Scope (Story / plan-run mode)
 
-When this lens is invoked from `/deliver` Phase 4 (epic-audit), the
-following block is populated with the Epic's change-set file list.
+When this lens is invoked from `/deliver` close lenses (or a plan-run audit), the
+following block is populated with the Story (or plan-run) change-set file list.
 Otherwise — for any manual `/audit-<dimension>` invocation — the block
 renders the literal substitution token and you MUST treat it as **no
 scope filter — run the lens codebase-wide** exactly as you would have
@@ -174,7 +174,7 @@ and check each one:
    renames).
 3. **Workflow & Contract Descriptions:** Described workflows, label
    taxonomies (`agent::*`, `type::*`, `meta::*`), branch shapes
-   (`story-<id>`, `epic/<id>`), and artifact contracts match how the
+   (`story-<id>`), and artifact contracts match how the
    current scripts actually behave — read the implementation when the
    prose makes a behavioural claim.
 4. **Version & Topology Claims:** Version numbers, package names, release
@@ -293,7 +293,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 --idea`) so the Context-Economy
+remediation Stories (or chains into `/plan --seed`) so the Context-Economy
 findings land as actionable, tracked work rather than a report nobody reads.
 
 ## Constraint

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

@@ -30,10 +30,10 @@ inflate Performance scores misleadingly.
 (check `viewport` meta, responsive CSS, or operator instruction), run
 **Mobile** instead and note the choice in the report.
 
-## Scope (Epic mode)
+## Scope (Story / plan-run mode)
 
-When this lens is invoked from `/deliver` Phase 4 (epic-audit), the
-following block is populated with the Epic's change-set file list.
+When this lens is invoked from `/deliver` close lenses (or a plan-run audit), the
+following block is populated with the Story (or plan-run) change-set file list.
 Otherwise — for any manual `/audit-<dimension>` invocation — the block
 renders the literal substitution token and you MUST treat it as **no
 scope filter — run the lens codebase-wide** exactly as you would have

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

@@ -61,8 +61,9 @@ Read the consumer's navigability config (resolved from `.agentrc.json`):
 
 - `delivery.quality.navigability.routeGlobs` — globs identifying the
   route-adding files / route tree (e.g. `pages/**`, `app/**/route.ts`). Drives
-  both the route-tree enumeration here and the route-added routing in
-  [`epic-audit-prepare.js`](../scripts/epic-audit-prepare.js).
+  both the route-tree enumeration here and the plan-persist draft
+  reachability gate
+  ([`plan-reachability.js`](../scripts/lib/orchestration/plan-reachability.js)).
 - `delivery.quality.navigability.navRegistry` — path(s) to the consumer's
   nav-registry SSOT this lens reads.
 

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

@@ -14,10 +14,10 @@ Analyze the application for performance regressions, bottlenecks, and efficiency
 gaps. Your goal is to identify why a system is slow or where it might fail under
 load.
 
-## Scope (Epic mode)
+## Scope (Story / plan-run mode)
 
-When this lens is invoked from `/deliver` Phase 4 (epic-audit), the
-following block is populated with the Epic's change-set file list.
+When this lens is invoked from `/deliver` close lenses (or a plan-run audit), the
+following block is populated with the Story (or plan-run) change-set file list.
 Otherwise — for any manual `/audit-<dimension>` invocation — the block
 renders the literal substitution token and you MUST treat it as **no
 scope filter — run the lens codebase-wide** exactly as you would have

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

@@ -15,10 +15,10 @@ Personally Identifiable Information (PII) and ensure compliance with data
 protection standards (GDPR, CCPA). Your goal is to find accidental logging,
 insecure storage, or unnecessary collection of sensitive data.
 
-## Scope (Epic mode)
+## Scope (Story / plan-run mode)
 
-When this lens is invoked from `/deliver` Phase 4 (epic-audit), the
-following block is populated with the Epic's change-set file list.
+When this lens is invoked from `/deliver` close lenses (or a plan-run audit), the
+following block is populated with the Story (or plan-run) change-set file list.
 Otherwise — for any manual `/audit-<dimension>` invocation — the block
 renders the literal substitution token and you MUST treat it as **no
 scope filter — run the lens codebase-wide** exactly as you would have

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

@@ -24,10 +24,10 @@ and integration test coverage alongside their feature implementations. The QA
 Engineering function focuses on End-to-End (E2E) testing, complex system
 integrations, and test environment stability.
 
-## Scope (Epic mode)
+## Scope (Story / plan-run mode)
 
-When this lens is invoked from `/deliver` Phase 4 (epic-audit), the
-following block is populated with the Epic's change-set file list.
+When this lens is invoked from `/deliver` close lenses (or a plan-run audit), the
+following block is populated with the Story (or plan-run) change-set file list.
 Otherwise — for any manual `/audit-<dimension>` invocation — the block
 renders the literal substitution token and you MUST treat it as **no
 scope filter — run the lens codebase-wide** exactly as you would have

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

@@ -15,10 +15,10 @@ Conduct a comprehensive security review of the codebase. Your goal is to
 identify common vulnerabilities (OWASP Top 10), insecure configurations, and
 potential attack vectors.
 
-## Scope (Epic mode)
+## Scope (Story / plan-run mode)
 
-When this lens is invoked from `/deliver` Phase 4 (epic-audit), the
-following block is populated with the Epic's change-set file list.
+When this lens is invoked from `/deliver` close lenses (or a plan-run audit), the
+following block is populated with the Story (or plan-run) change-set file list.
 Otherwise — for any manual `/audit-<dimension>` invocation — the block
 renders the literal substitution token and you MUST treat it as **no
 scope filter — run the lens codebase-wide** exactly as you would have

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

@@ -18,10 +18,10 @@ codebase. Your goal is to surface structural, semantic, and content-level
 improvements that will increase discoverability in both traditional search
 indexes and AI-powered answer engines — without making any immediate changes.
 
-## Scope (Epic mode)
+## Scope (Story / plan-run mode)
 
-When this lens is invoked from `/deliver` Phase 4 (epic-audit), the
-following block is populated with the Epic's change-set file list.
+When this lens is invoked from `/deliver` close lenses (or a plan-run audit), the
+following block is populated with the Story (or plan-run) change-set file list.
 Otherwise — for any manual `/audit-<dimension>` invocation — the block
 renders the literal substitution token and you MUST treat it as **no
 scope filter — run the lens codebase-wide** exactly as you would have

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

@@ -15,10 +15,10 @@ release candidate. Your goal is to surface critical risks across configuration
 integrity, security, observability, and code quality — providing a prioritized,
 actionable report that can be handed off for remediation before deployment.
 
-## Scope (Epic mode)
+## Scope (Story / plan-run mode)
 
-When this lens is invoked from `/deliver` Phase 4 (epic-audit), the
-following block is populated with the Epic's change-set file list.
+When this lens is invoked from `/deliver` close lenses (or a plan-run audit), the
+following block is populated with the Story (or plan-run) change-set file list.
 Otherwise — for any manual `/audit-<dimension>` invocation — the block
 renders the literal substitution token and you MUST treat it as **no
 scope filter — run the lens codebase-wide** exactly as you would have

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 --idea or opens standalone Stories.
+  either chains into /plan --seed-file or opens standalone Stories.
 ---
 
 # /audit-to-stories [audit-file-or-glob]
@@ -22,8 +22,8 @@ Dimension / Category, Current State, Recommendation, Agent Prompt).
 `/audit-to-stories` closes the loop: it parses those reports, groups
 related findings (including across audit dimensions), classifies each
 group as eligible-to-create or already-tracked, and — at the operator's
-choice — either chains into `/plan --idea` for a single planned
-Epic or opens standalone Stories directly.
+choice — either chains into `/plan --seed-file` for a planned Story
+(or N>1 under the split policy) or opens standalone Stories directly.
 
 The audit producers themselves are **not modified** by this workflow.
 They remain read-only emitters of audit reports.
@@ -117,23 +117,23 @@ Ask:
 
 > How would you like these `<M>` Stories created?
 >
-> - **Single Epic via `/plan`** **[Recommended]** — opens one Epic,
->   then chains into `/plan --idea` so the standard spec-and-WBS
->   authoring handles decomposition. Grouped Stories become the
->   seed for the authoring step's decomposition.
+> - **Single plan via `/plan`** **[Recommended]** — chains into
+>   `/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
->   group directly, no Epic wrapper.
+>   group directly (no plan ceremony).
 
 **STOP** until the operator picks.
 
-## Phase 5a — Single-Epic path
+## Phase 5a — Single-plan path
 
-Build the `/plan` idea seed from the filtered plan envelope:
+Build the `/plan` seed from the filtered plan envelope:
 
 ```bash
-node .agents/scripts/audit-to-stories.js --emit-epic-seed \
+node .agents/scripts/audit-to-stories.js --emit-plan-seed \
   --plan temp/audits/audit-to-stories-plan.json \
-  --out "temp/audits/audit-epic-seed-$(date +%Y%m%dT%H%M%S).md"
+  --out "temp/audits/audit-plan-seed-$(date +%Y%m%dT%H%M%S).md"
 ```
 
 The seed renders the canonical one-pager sections — Problem Statement,
@@ -144,11 +144,11 @@ authoring step has concrete anchors), Not Doing.
 Chain into the existing planning entrypoint:
 
 ```text
-/plan --idea "<path-to-seed>"
+/plan --seed-file <path-to-seed>
 ```
 
-`/plan` then runs its 3-step Epic path (interrogate → author →
-persist), as documented in its workflow.
+(`/plan --seed "$(cat <path>)"` also works for small seeds). `/plan`
+then runs its author → persist path, as documented in its workflow.
 Each Story it spawns from the seed carries `context::audit:
 <reportLink>` and `audit-fingerprint: <sha>` in its body so future
 Phase 6 idempotency works on the next run.
@@ -220,13 +220,13 @@ Persist `temp/audits/audit-to-stories-$(date +%Y%m%dT%H%M%S).md`
 summarising the run:
 
 - Per-group breakdown: which findings merged, fingerprints, dependency
-  edges, created/skipped Issue link (or new Epic link).
+  edges, created/skipped Issue link (or plan-run / Story links).
 - The severity threshold and grouping mode the operator chose.
 - Final tally: `"<M> groups planned · <K> created · <J> skipped (open)
   · <L> skipped (re-occurring)"`.
 
-When the Single-Epic path ran, link the Epic the chained `/plan`
-opened. When the Standalone-Stories path ran, list every Issue URL.
+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.
 
 ## Constraints
 
@@ -261,8 +261,8 @@ issue 4482.)
 
 ## See also
 
-- [`/plan`](helpers/plan-epic.md) — the planning pipeline `/audit-to-stories`
-  chains into for the Single-Epic grouping mode.
+- [`/plan`](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`
   both consume. There is no second dedup implementation.

package/.agents/workflows/audit-ux-ui.md

@@ -14,10 +14,10 @@ Evaluate the frontend implementation for UI consistency, UX best practices, and
 adherence to the project's design system. Ensure the application feels premium
 and cohesive.
 
-## Scope (Epic mode)
+## Scope (Story / plan-run mode)
 
-When this lens is invoked from `/deliver` Phase 4 (epic-audit), the
-following block is populated with the Epic's change-set file list.
+When this lens is invoked from `/deliver` close lenses (or a plan-run audit), the
+following block is populated with the Story (or plan-run) change-set file list.
 Otherwise — for any manual `/audit-<dimension>` invocation — the block
 renders the literal substitution token and you MUST treat it as **no
 scope filter — run the lens codebase-wide** exactly as you would have