mandrel 1.59.0 → 1.61.0

package/.agents/scripts/agents-bootstrap-github.js

@@ -15,13 +15,7 @@
  * @see docs/v5-implementation-plan.md Sprint 1C
  */
 
-import fs from 'node:fs';
-import path from 'node:path';
 import { applyBranchProtection } from './lib/bootstrap/branch-protection.js';
-import {
-  CI_WORKFLOW_RELATIVE_PATH,
-  renderCiWorkflow,
-} from './lib/bootstrap/ci-workflow-template.js';
 import {
   compareSemver,
   MIN_GH_VERSION,
@@ -55,7 +49,7 @@ import {
 import { createProvider } from './lib/provider-factory.js';
 
 const PROJECTS_DOC_POINTER =
-  'See docs/project-board.md for the manual Projects V2 setup checklist.';
+  'Configure the board views manually in the GitHub Projects UI.';
 
 /**
  * Detect that an error is a not-found / 404 signal across the surfaces
@@ -266,106 +260,6 @@ async function ensureProjectFields(provider, project, log) {
   return fields;
 }
 
-/**
- * Create or additively-merge branch protection on `baseBranch` (typically
- * `main`) so the `delivery.quality.prGate.checks` suite is required
- * before merge. Behaviour rules:
- *
- *   - `enforceBranchProtection: false` → skip, log the opt-out, return a
- *     `{ status: 'skipped' }` summary.
- *   - `prGate.checks` empty or absent → skip with a clear log, since there
- *     is nothing to enforce.
- *   - Existing protection rule → preserve every existing required-check
- *     context and append only the missing prGate names.
- *   - No existing rule → create a fresh one carrying just the prGate
- *     contexts plus minimal sensible defaults (strict status checks).
- *
- * Errors (insufficient scopes, repo permission denied, etc.) are logged
- * and return a `{ status: 'failed' }` summary so the bootstrap CLI
- * surfaces a non-fatal warning rather than aborting the entire run —
- * matching how the project-board provisioning steps degrade.
- */
-async function ensureMainBranchProtection(
-  provider,
-  { baseBranch, prGate },
-  log,
-) {
-  if (prGate?.enforceBranchProtection === false) {
-    log(
-      `[bootstrap] Branch protection on '${baseBranch}': skipped (delivery.quality.prGate.enforceBranchProtection=false).`,
-    );
-    return { status: 'skipped', reason: 'opt-out' };
-  }
-
-  const checkNames = (prGate?.checks ?? [])
-    .map((c) => c?.name)
-    .filter((n) => typeof n === 'string' && n.length > 0);
-  if (checkNames.length === 0) {
-    log(
-      `[bootstrap] Branch protection on '${baseBranch}': skipped (no prGate.checks configured).`,
-    );
-    return { status: 'skipped', reason: 'no-checks' };
-  }
-
-  try {
-    const result = await provider.setBranchProtection(baseBranch, {
-      contexts: checkNames,
-    });
-    const verb = result.created ? 'Created' : 'Updated';
-    const addedSuffix = result.added.length
-      ? ` (added: ${result.added.join(', ')})`
-      : ' (all required checks already present)';
-    log(
-      `[bootstrap] Branch protection on '${baseBranch}': ${verb} rule${addedSuffix}.`,
-    );
-    return { status: result.created ? 'created' : 'merged', ...result };
-  } catch (err) {
-    log(
-      `[bootstrap] Branch protection on '${baseBranch}': failed — ${err.message}. Proceeding without it.`,
-    );
-    return { status: 'failed', reason: err.message };
-  }
-}
-
-/**
- * Render the stabilized-quality-gates CI workflow template into a project
- * checkout. Idempotent on the byte level: when `.github/workflows/ci.yml`
- * already matches the rendered template, no write occurs and the action is
- * `unchanged`. When the file is absent the action is `created`. When the
- * file exists with operator-authored differences the helper preserves it
- * and returns `custom-workflow-skip` along with the rendered body so the
- * bootstrap caller (or `/agents-update`) can offer a side-by-side diff.
- *
- * Network-free; safe to invoke under tests with a tmp `projectRoot`.
- *
- * @param {object} args
- * @param {string} args.projectRoot - Repo root (must contain or accept
- *   `.github/workflows/`).
- * @param {object} [args.template] - Forwarded to `renderCiWorkflow`.
- * @param {boolean} [args.write=true] - When `false`, the helper computes
- *   the would-be action without touching disk. Used by the
- *   bootstrap CLI's dry-run mode.
- * @returns {{ action: 'created'|'unchanged'|'custom-workflow-skip',
- *             path: string, rendered: string }}
- */
-export function ensureCiWorkflow(args) {
-  const projectRoot = args.projectRoot;
-  const rendered = renderCiWorkflow(args.template);
-  const target = path.join(projectRoot, CI_WORKFLOW_RELATIVE_PATH);
-  if (!fs.existsSync(target)) {
-    if (args.write !== false) {
-      fs.mkdirSync(path.dirname(target), { recursive: true });
-      fs.writeFileSync(target, rendered, 'utf8');
-    }
-    return { action: 'created', path: target, rendered };
-  }
-  const existing = fs.readFileSync(target, 'utf8');
-  if (existing === rendered) {
-    return { action: 'unchanged', path: target, rendered };
-  }
-  return { action: 'custom-workflow-skip', path: target, rendered };
-}
-
 /**
  * Run the idempotent bootstrap sequence.
  *
@@ -397,6 +291,7 @@ export function ensureCiWorkflow(args) {
  *   github?: object,
  *   baseBranch?: string,
  *   githubAdminApproved?: boolean,
+ *   isTTY?: boolean,
  * }} [opts] - `githubAdminApproved` MUST be `true` for any GitHub mutation to
  *   occur; any other value (absent / `false`) is treated as "not approved"
  *   and the run is a verified no-op.
@@ -463,12 +358,12 @@ export async function runBootstrap(config, opts = {}) {
   // Consumer-facing bootstrap promotes the framework's CI-gates-only
   // stance: branch protection with enforce_admins + 0-approval-count and
   // the squash-only merge-method allowlist. Behavior-shifting drift on
-  // either step routes through the HITL confirm gate — non-TTY runs abort
-  // with a clear stderr message rather than silently apply.
+  // branch protection routes through the HITL confirm gate — non-TTY runs
+  // abort with a clear stderr message rather than silently apply. The
+  // merge-method step differs by design (Story #4045 A4): non-TTY without an
+  // assume override default-applies the framework stance with an explicit
+  // log line (see mergeMethodsHitlConfirm below).
   //
-  // The legacy `ensureMainBranchProtection` helper is preserved (re-
-  // exported below) so the Epic #1142 Story #1157 contract tests stay
-  // green; `applyBranchProtection` is its consumer-parity successor.
   // Post-reshape: bootstrap reads from the new `project` + `github` blocks
   // exclusively. The legacy "agent settings" opt was removed in Epic #2880.
   const projectCfg = opts.project ?? config.project ?? {};
@@ -493,10 +388,22 @@ export async function runBootstrap(config, opts = {}) {
     hitlConfirm,
     log,
   });
+
+  // Merge-methods gate (Story #4045 A4): under non-TTY without an explicit
+  // assume override there is no operator to consult, and the default HITL
+  // gate declines every non-TTY prompt — which would make applyMergeMethods'
+  // documented non-TTY default-apply branch unreachable. Skip the gate in
+  // that case so the merge-method stance default-applies with its explicit
+  // log line. Interactive runs (and explicit --assume-yes/--assume-no, and
+  // injected gates) keep the loud confirm/decline behaviour.
+  const stdoutIsTTY = opts.isTTY ?? Boolean(process.stdout.isTTY);
+  const mergeMethodsHitlConfirm =
+    opts.hitlConfirm ??
+    (stdoutIsTTY || opts.assumeYes || opts.assumeNo ? hitlConfirm : undefined);
   const mergeMethods = await applyMergeMethods({
     provider,
     settings,
-    hitlConfirm,
+    hitlConfirm: mergeMethodsHitlConfirm,
     log,
   });
 
@@ -539,8 +446,9 @@ async function main() {
   }
 
   // Preflight runtime deps before the dynamic config-resolver import so
-  // a green-field consumer who skipped `/agents-bootstrap-project` gets
-  // a workflow hint instead of a raw `ERR_MODULE_NOT_FOUND`.
+  // a consumer who hasn't installed framework runtime deps yet gets a
+  // clear hint (`run mandrel init` or `npm install mandrel`) instead of
+  // a raw `ERR_MODULE_NOT_FOUND`.
   try {
     await preflightRuntimeDeps();
   } catch (err) {
@@ -569,7 +477,6 @@ async function main() {
     process.exit(1);
   }
 
-  const installWorkflows = process.argv.includes('--install-workflows');
   // Epic #1235 Story 5 — flags let CI / non-interactive callers pin the
   // HITL gate's answer deterministically. The bootstrap is non-interactive
   // by default in non-TTY contexts (the gate returns false and aborts);
@@ -594,7 +501,6 @@ async function main() {
 
   try {
     const result = await runBootstrap(config, {
-      installWorkflows,
       project: config.project,
       github: config.github,
       assumeYes,
@@ -617,12 +523,10 @@ async function main() {
   }
 }
 
-// Re-export internal helpers for test consumers (no production caller imports them).
 // Re-export the gh-preflight surface so existing test consumers can keep
 // importing it from this module after the Story #3349 split.
 export {
   compareSemver,
-  ensureMainBranchProtection,
   isApiAccessNotFoundError,
   MIN_GH_VERSION,
   parseGhVersion,

package/.agents/scripts/analyze-execution.js

@@ -18,7 +18,7 @@
  *     fetching each `story-perf-summary` structured comment from the
  *     ticketing provider. Posts the
  *     `<!-- structured:epic-perf-report -->` comment on the Epic ticket.
- *     Run from the retro composer / `/epic-deliver` Phase 6.0.
+ *     Run from the retro composer / `/deliver` Phase 6.0.
  *
  * Both modes are idempotent: `upsertStructuredComment` deletes the prior
  * marker before posting the new one.
@@ -27,7 +27,7 @@
  * NDJSON for a Story, no children for an Epic) so the close pipelines
  * never block on observability output. Hard failures (bad CLI args,
  * provider error, schema-violating payload) exit non-zero — the call
- * sites in post-merge-pipeline / `/epic-deliver` Phase 5 treat that
+ * sites in post-merge-pipeline / `/deliver` Phase 5 treat that
  * as a non-fatal warning.
  *
  * This file is a thin CLI: it wires the I/O readers from

package/.agents/scripts/audit-to-stories.js

@@ -13,7 +13,7 @@
  *     stdout when --json is set).
  *
  *   --emit-epic-seed --plan <plan.json> --out <path>
- *     Read the plan envelope from disk, render the `/epic-plan --idea`
+ *     Read the plan envelope from disk, render the `/plan --idea`
  *     seed markdown, persist to --out.
  *
  *   --emit-stories --plan <plan.json>

package/.agents/scripts/check-doc-links.js

@@ -5,7 +5,7 @@
 // Story #2662 — Internal-link and slash-command resolver for active docs.
 //
 // Scans every `*.md` under `docs/` and `.agents/` (excluding
-// `docs/CHANGELOG.md` and anything under `docs/archive/**`) and validates:
+// `docs/CHANGELOG.md`) and validates:
 //
 //   1. Every Markdown relative-path link `[text](relative/path[#anchor])`
 //      resolves to a real file on disk (anchors are not validated, only
@@ -19,7 +19,7 @@
 //
 //   3. No active doc mentions any retired slash command. The retired-command
 //      blocklist is seeded with `agents-bootstrap-github`,
-//      `single-story-plan` (renamed to `/story-plan`), and `mandrel`
+//      `single-story-plan` (renamed to `/plan`), and `mandrel`
 //      (retired in favor of the generated `.agents/docs/workflows.md`
 //      catalog) and takes precedence over the workflow-resolution check —
 //      a retired token is always a non-zero exit even if a stale workflow
@@ -125,7 +125,6 @@ export const SLASH_ALLOWLIST = new Set([
 
 function isExcludedRelPath(relPath) {
   if (relPath === 'docs/CHANGELOG.md') return true;
-  if (relPath.startsWith('docs/archive/')) return true;
   return false;
 }
 

package/.agents/scripts/diagnose-friction.js

@@ -134,7 +134,7 @@ function buildFrictionSignal({
     timestamp: new Date().toISOString(),
     epicId: epicId ?? null,
     storyId: storyId ?? null,
-    // 3-tier hierarchy (Epic #3163): no Task tier, so friction signals
+    // 2-tier hierarchy (Epic #3163): no Task tier, so friction signals
     // carry no Task id. The field is retained for schema compatibility
     // and always null.
     taskId: null,

package/.agents/scripts/dispatcher.js

@@ -72,12 +72,12 @@ import { loadSpec, loadState } from './lib/spec/index.js';
  * loaded state mapping. The spec-aware renderer (`buildManifestFromSpec`)
  * looks up each Story's status via `state.mapping[slug].lastObservedAgentState`;
  * that field is only refreshed by the structural reconciler, so during
- * `/epic-deliver` execution it stays `null` and every Story renders as ⬜
+ * `/deliver` execution it stays `null` and every Story renders as ⬜
  * pending even after the Story merges. The wave-runner replaced the
  * dispatcher-per-wave refresh loop and the local state.json never sees
  * the progress signal.
  *
- * Under the 3-tier hierarchy (Epic #3163) the runtime manifest's wave
+ * Under the 2-tier hierarchy (Epic #3163) the runtime manifest's wave
  * records carry `stories[]` (each with the live `storyId` + `status` from
  * `fetchEpicContext`'s GH query), not the retired `tasks[]` shape. The
  * overlay walks `manifest.waves[].stories[]` and copies each Story's

package/.agents/scripts/drain-pending-cleanup.js

@@ -8,7 +8,7 @@
  * any still-stuck entries by enumerating the processes holding handles
  * inside the worktree path and terminating them.
  *
- * Invoked by `/epic-deliver`, `/epic-plan-spec` / `/epic-plan-decompose`
+ * Invoked by `/deliver`, `/epic-plan-spec` / `/epic-plan-decompose`
  * (via `drainPendingCleanupAtBoot` → `worktree-sweep.js`), and
  * `story-close` so the pending-cleanup ledger drains automatically
  * across the sprint lifecycle. Operators can also run it standalone:

package/.agents/scripts/epic-audit-prepare.js

@@ -2,7 +2,7 @@
 /* node:coverage ignore file */
 
 /**
- * epic-audit-prepare.js — Phase 4 prepare CLI for `/epic-deliver`.
+ * epic-audit-prepare.js — Phase 4 prepare CLI for `/deliver`.
  *
  * Thin glue around the audit-suite `selectAudits` SDK. Reads the Epic
  * ticket, runs the change-set selector against the Epic branch diff
@@ -193,7 +193,7 @@ function resolveTaskSizing(config) {
  * Best-effort and total, mirroring `resolveRiskRoutedLenses`: a
  * missing/unparseable checkpoint, an absent `planningRisk` field, or a
  * provider read failure all degrade to `standard` — the neutral default that
- * preserves today's behavior — so an Epic that skipped `/epic-plan` (no
+ * preserves today's behavior — so an Epic that skipped `/plan` (no
  * checkpoint) still gets a passing `standard` pass with no new failure mode.
  * The changed-file count can only escalate a low-risk Epic to `deep` (a wide
  * diff) and never downgrades a high-risk one; an unknown/absent count is the
@@ -295,7 +295,7 @@ export async function runEpicAuditPrepare(values, deps = {}) {
   const runner = deps.selectAudits ?? selectAudits;
 
   // Pin the change set to the requested Epic's own branch rather than the
-  // shared checkout's HEAD (Story #3362). Under two concurrent /epic-deliver
+  // shared checkout's HEAD (Story #3362). Under two concurrent /deliver
   // runs sharing one working copy, a HEAD-relative diff silently reports the
   // *other* Epic's change set; `refs/heads/epic/<id>` is unambiguous.
   const epicBranch = `epic/${epicId}`;

package/.agents/scripts/epic-deliver-note-intervention.js

@@ -3,9 +3,9 @@
 
 /**
  * epic-deliver-note-intervention.js — record a manual-intervention event
- * against the active `/epic-deliver` run-state checkpoint.
+ * against the active `/deliver` run-state checkpoint.
  *
- * The host LLM driving `/epic-deliver` invokes this CLI whenever it does
+ * The host LLM driving `/deliver` invokes this CLI whenever it does
  * something out-of-band that disqualifies the Epic from auto-merge:
  *
  *   - `AskUserQuestion` to the operator mid-run

package/.agents/scripts/epic-deliver-preflight.js

@@ -4,7 +4,7 @@
 /**
  * epic-deliver-preflight.js — Story #2899 (Epic #2880, F13).
  *
- * Estimates the cost of an upcoming `/epic-deliver` run *before* Story
+ * Estimates the cost of an upcoming `/deliver` run *before* Story
  * fan-out and surfaces the result to the operator on two channels:
  *
  *   1. A JSON envelope on stdout (always) with the keys
@@ -19,7 +19,7 @@
  *
  * The CLI is intentionally side-effect-light when `--dry-run` is set: no
  * comment write, no lifecycle emit. The slash-command workflow
- * (`/epic-deliver` Phase 1) calls the CLI without `--dry-run` so the
+ * (`/deliver` Phase 1) calls the CLI without `--dry-run` so the
  * comment is upserted; if any threshold is breached, the workflow flips
  * the Epic to `agent::blocked` and surfaces the envelope in chat for
  * operator review. The CLI itself does NOT flip labels — the workflow
@@ -70,7 +70,7 @@ const HELP = `Usage: node .agents/scripts/epic-deliver-preflight.js \\
   [--per-story-claude-tokens <n>]
 
 Estimates Story count, install cost, wave count, GitHub API request volume,
-and Claude Max quota burn for an Epic *before* /epic-deliver fan-out.
+and Claude Max quota burn for an Epic *before* /deliver fan-out.
 
 Flags:
   --dry-run                        Compute the estimate and print the JSON
@@ -103,7 +103,7 @@ const DEFAULTS = Object.freeze({
   perStoryApiRequests: 25,
   perStoryClaudeTokens: 200_000,
   // Base GH API budget: snapshot getTicket + getSubTickets + plan/manifest
-  // reads/writes that happen once per /epic-deliver run regardless of
+  // reads/writes that happen once per /deliver run regardless of
   // Story count. Empirical observation from a 5-Story Epic shows ~30
   // requests for the non-per-Story floor.
   baseApiRequests: 30,
@@ -240,7 +240,7 @@ export function renderPreflightBody({
     );
   } else {
     lines.push(
-      '⛔ **Threshold breaches** — `/epic-deliver` will flip the Epic to `agent::blocked` for operator review:',
+      '⛔ **Threshold breaches** — `/deliver` will flip the Epic to `agent::blocked` for operator review:',
     );
     for (const b of breaches) {
       lines.push(`- \`${b.key}\` = ${b.observed} (max ${b.max})`);
@@ -284,7 +284,7 @@ export async function runPreflight({
   const provider = injectedProvider ?? createProvider(config);
   const thresholds = getPreflight(config);
 
-  // Compose the same two phases /epic-deliver Phase 1 runs so the
+  // Compose the same two phases /deliver Phase 1 runs so the
   // preflight numbers match the actual dispatch plan.
   const ctx = { epicId, provider };
   let state = {};

package/.agents/scripts/epic-deliver-prepare.js

@@ -2,7 +2,7 @@
 /* node:coverage ignore file */
 
 /**
- * epic-deliver-prepare.js — Step 0/1 of the operator-driven `/epic-deliver`.
+ * epic-deliver-prepare.js — Step 0/1 of the operator-driven `/deliver`.
  *
  * Composes the existing engine phases that the in-process epic-runner used to
  * call sequentially, but does NOT dispatch any waves. The CLI is the single

package/.agents/scripts/epic-execute-record-wave.js

@@ -6,7 +6,7 @@
  * advance the `epic-run-state` checkpoint, and re-render the unified
  * `epic-run-progress` rollup on the Epic.
  *
- * The slash-command (`/epic-deliver`) calls this CLI once per wave, after
+ * The slash-command (`/deliver`) calls this CLI once per wave, after
  * its host-level Agent-tool fan-out drains. It is the only writer of the
  * `epic-run-progress` structured comment for the wave-completion path —
  * there is no separate `/wave-execute` skill, no `wave-run-progress`
@@ -95,7 +95,7 @@ const HELP = `Usage: node .agents/scripts/epic-execute-record-wave.js \\
 
 Records the wave's per-Story outcomes, advances the epic-run-state
 checkpoint, and upserts the unified epic-run-progress rollup on the Epic.
-Prints the next action for the /epic-deliver slash command.
+Prints the next action for the /deliver slash command.
 `;
 
 /**
@@ -237,7 +237,7 @@ export async function runEpicExecuteRecordWave({
   //     Closes the start/end pairing the wave-tick reconciler and the
   //     `--check-idle` watchdog use to derive in-flight Stories. Before this
   //     the only producer was `wave-session.js`, which the host-LLM driven
-  //     /epic-deliver path never imports — so every dispatched Story stayed
+  //     /deliver path never imports — so every dispatched Story stayed
   //     "in-flight" forever and completed Stories tripped the watchdog.
   //     Best-effort: a failed append must not block the wave loop.
   emitWaveDispatchEnds({ epicId, verified, config });
@@ -257,7 +257,7 @@ export async function runEpicExecuteRecordWave({
 
   // 7. Fire the curated webhook events for this wave boundary. Mirrors the
   //    wave-loop emits in `lib/orchestration/epic-runner/phases/iterate-waves.js`
-  //    for the host-LLM driven /epic-deliver path (which does not pass
+  //    for the host-LLM driven /deliver path (which does not pass
   //    through `runEpic`). Each helper is fire-and-forget — webhook
   //    misconfig or a transient Slack outage must not block the wave loop.
   await emitWaveBoundaryNotifications({

package/.agents/scripts/epic-plan-healthcheck.js

@@ -5,7 +5,7 @@
 /**
  * epic-plan-healthcheck.js — Post-Plan Readiness Check
  *
- * Runs at the end of /epic-plan (Phase 10) to validate the backlog and
+ * Runs at the end of /plan (Phase 10) to validate the backlog and
  * optionally prime the execution environment before handing off to
  * /epic-deliver.
  *
@@ -27,7 +27,7 @@
  *   node epic-plan-healthcheck.js --epic <EPIC_ID> \
  *     [--paranoid] [--prime-install] [--dry-run]
  *
- * @see .agents/workflows/epic-plan.md Phase 10
+ * @see .agents/workflows/helpers/plan-epic.md Phase 10
  */
 
 import { spawnSync } from 'node:child_process';
@@ -131,7 +131,7 @@ function checkGitRemote(baseBranch, cwd) {
 
 /**
  * Detect whether a Story body carries an inline `## Acceptance` section with
- * at least one checklist item. Epic #3078 — under 3-tier hierarchy, Stories
+ * at least one checklist item. Epic #3078 — under 2-tier hierarchy, Stories
  * carry acceptance inline, so the hierarchy check uses this signal as the
  * mark of a complete, executable Story.
  *
@@ -152,7 +152,7 @@ function hasInlineAcceptance(body) {
 }
 
 /**
- * Validate Epic ticket hierarchy. 3-tier is the only supported hierarchy
+ * Validate Epic ticket hierarchy. 2-tier is the only supported hierarchy
  * after Task #3154 deleted `planning.hierarchy`: every Story must carry an
  * inline `## Acceptance` checklist; there is no Task layer to graph.
  *
@@ -181,13 +181,9 @@ async function checkTickets(provider, epicId) {
     return { ok: false, detail: `Epic #${epicId} has no child tickets.` };
   }
 
-  const features = tickets.filter((t) =>
-    t.labels.includes(TYPE_LABELS.FEATURE),
-  );
   const stories = tickets.filter((t) => t.labels.includes(TYPE_LABELS.STORY));
 
   const errors = [];
-  if (features.length === 0) errors.push('no type::feature tickets');
   if (stories.length === 0) errors.push('no type::story tickets');
 
   const missingAcceptance = stories.filter(
@@ -214,7 +210,7 @@ async function checkTickets(provider, epicId) {
 
   return {
     ok: true,
-    detail: `${features.length} features, ${stories.length} stories (3-tier, inline acceptance) — hierarchy valid${advisory}.`,
+    detail: `${stories.length} stories (2-tier, inline acceptance) — hierarchy valid${advisory}.`,
   };
 }
 
@@ -313,7 +309,7 @@ export async function runPlanHealthcheck(opts = {}) {
     await timed('git-remote', async () => checkGitRemote(baseBranch, cwd)),
   );
 
-  // Paranoid lane: ticket-hierarchy revalidation (3-tier only).
+  // Paranoid lane: ticket-hierarchy revalidation (2-tier only).
   if (paranoid) {
     const provider = opts.injectedProvider || createProvider(config);
     progress('CHECK', 'Validating ticket hierarchy...');

package/.agents/scripts/epic-plan-spec-validate.js

@@ -3,7 +3,7 @@
 /**
  * epic-plan-spec-validate.js — Phase 7.5 Tech Spec post-authoring gate CLI.
  *
- * `/epic-plan` Phase 7 authors the Tech Spec; Phase 8.3 (Holistic
+ * `/plan` Phase 7 authors the Tech Spec; Phase 8.3 (Holistic
  * Consolidation) reconciles the draft ticket array against the Tech Spec's
  * `## Delivery Slicing` section, which the decompose-author skill uses as the
  * capability-boundary anchor. When that section is absent the consolidation

package/.agents/scripts/epic-reconcile.js

@@ -195,11 +195,11 @@ export async function fetchGhState(provider, epicId) {
 }
 
 /**
- * Walk the spec depth-first and yield one `{ slug, entity, title,
- * parentSlug, dependsOn }` record per logical entity (epic → feature →
- * story → task), mirroring the diff engine's `flattenSpec`. Local to the
- * CLI so the reseed pass (below) can map spec slugs onto live GH issues
- * without importing the diff engine's private walker. Pure.
+ * Walk the spec and yield one `{ slug, entity, title, parentSlug,
+ * dependsOn }` record per logical entity (epic → story), mirroring the
+ * diff engine's `flattenSpec`. Local to the CLI so the reseed pass
+ * (below) can map spec slugs onto live GH issues without importing the
+ * diff engine's private walker. Pure.
  *
  * @param {object} spec
  * @returns {Array<{slug: string, entity: string, title: string, parentSlug: string|null, dependsOn: string[]}>}
@@ -216,32 +216,14 @@ export function flattenSpecForReseed(spec) {
       dependsOn: [],
     });
   }
-  for (const feature of spec.features ?? []) {
+  for (const story of spec.stories ?? []) {
     out.push({
-      slug: feature.slug,
-      entity: 'feature',
-      title: String(feature.title ?? ''),
+      slug: story.slug,
+      entity: 'story',
+      title: String(story.title ?? ''),
       parentSlug: 'epic',
-      dependsOn: [],
+      dependsOn: story.dependsOn ?? [],
     });
-    for (const story of feature.stories ?? []) {
-      out.push({
-        slug: story.slug,
-        entity: 'story',
-        title: String(story.title ?? ''),
-        parentSlug: feature.slug,
-        dependsOn: story.dependsOn ?? [],
-      });
-      for (const task of story.tasks ?? []) {
-        out.push({
-          slug: task.slug,
-          entity: 'task',
-          title: String(task.title ?? ''),
-          parentSlug: story.slug,
-          dependsOn: [],
-        });
-      }
-    }
   }
   return out;
 }
@@ -255,7 +237,7 @@ export function flattenSpecForReseed(spec) {
  * file is absent (a fresh checkout, a reaped temp dir, the exact
  * situation `--resume` exists to recover from), `loadState` returns an
  * empty mapping, the diff engine sees every spec slug as unmapped, and
- * `apply` recreates the entire Feature/Story tree on top of the existing
+ * `apply` recreates the entire Story set on top of the existing
  * one — duplicating every child. This is precisely the failure `--resume`
  * is meant to prevent.
  *

package/.agents/scripts/evidence-gate.js

@@ -3,7 +3,7 @@
 /**
  * evidence-gate.js — evidence-aware wrapper around a single shell gate.
  *
- * Tech Spec #819 §"Evidence record (Story 7)" — `/epic-deliver` Phase 3
+ * Tech Spec #819 §"Evidence record (Story 7)" — `/deliver` Phase 3
  * (close-validation) runs `npm run lint` and `npm test` against the Epic
  * branch before opening the PR.
  * If the same gate has already passed against the current `git rev-parse

package/.agents/scripts/generate-workflows-doc.js

@@ -91,7 +91,7 @@ export function renderWorkflowsDoc(catalog) {
     'Every command file lives at `.agents/workflows/<name>.md` and is projected',
     'into a flat `.claude/commands/` tree by `npm run sync:commands` (the',
     'UserPromptSubmit hook keeps it current) so it shows up as a bare `/<name>`',
-    'slash command (e.g. `/epic-deliver`). The projection writes only',
+    'slash command (e.g. `/deliver`). The projection writes only',
     '`.claude/commands/<name>.md` — there is no plugin manifest and no',
     'marketplace listing. The commands load in every Claude Code environment.',
     '',