mandrel 1.93.0 → 2.0.0

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

@@ -37,16 +37,14 @@ and dedup/route decisions. The agent never invents those decisions in prose.
 > a structured agent-driven bug-hunt the operator wants captured into a
 > triageable ledger.
 >
-> **Persona**: `qa-engineer` · **Skills**: `core/qa-coverage-mapping`,
-> `stack/qa/qa-explore-driving`
+> **Skills**: `core/qa-coverage-mapping`, `stack/qa/qa-explore-driving`
 
-## Persona
+## Role framing
 
-Adopt the **`qa-engineer`** persona
-([`.agents/personas/qa-engineer.md`](../personas/qa-engineer.md)) for the whole
-run. You are the quality gatekeeper: you value coverage, hermetic
-environments, and deterministic results. Re-read that persona file as your
-first action so the Plan/Capture/Triage loop is governed by it.
+You are the quality gatekeeper for this run: value coverage, hermetic
+environments, and deterministic results. Do **not** invent signal — capture
+what the surface shows. Apply the QA skills below; there is no separate
+persona pack.
 
 ## Driving conventions skill
 
@@ -89,10 +87,10 @@ ledger**; do not switch methods mid-surface without a new Plan note.
 | --------- | -------- | ---------------------------------- | -------------------------------------------------------------------------------------- |
 | `surface` | yes      | `feature:login`, `area:onboarding` | A human label for the single surface to explore. Recorded as each ledger item's `coverage`. |
 
-If no `surface` is supplied, **stop and ask** the operator to name one — the
-`qa-engineer` Golden Rule forbids inventing scope. `/qa-explore` is **bounded
-to one surface per session**: explore exactly the named surface, do not wander
-into adjacent surfaces, and start a fresh session for a different surface.
+If no `surface` is supplied, **stop and ask** the operator to name one — do
+not invent scope. `/qa-explore` is **bounded to one surface per session**:
+explore exactly the named surface, do not wander into adjacent surfaces, and
+start a fresh session for a different surface.
 
 ## Project contract
 
@@ -161,7 +159,7 @@ advances phases autonomously. If the operator does not confirm, stop and hold.
 Goal: agree on **what** will be explored and **how the agent will drive it**
 before touching the surface.
 
-1. Re-read the `qa-engineer` persona and the
+1. Re-read the
    [`stack/qa/qa-explore-driving`](../skills/stack/qa/qa-explore-driving/SKILL.md)
    skill, and resolve the `qa` contract and session (above).
 2. **Resolve the target environment** via
@@ -339,33 +337,26 @@ For each untriaged ledger item:
    import { promoteFindings } from '../scripts/lib/findings/promote-finding.js';
    const { promotions } = await promoteFindings(ledgerItems, {
      searchIssues, // GitHub provider, open + closed
-     createStory, // tight cluster (≤2 surfaces): render seed → /plan --from-notes
-     createEpic, // broad cluster (>2 surfaces): render seed → /plan --idea
+     createStory, // tight cluster (≤2 surfaces): seed → /plan --seed-file
+     createEpic, // broad cluster (>2 surfaces): same /plan --seed-file path (may N>1)
    });
    ```
 
    - **Sizing is delegated, not decided in prose.** `promoteFindings` runs
      `clusterLedgerItems` + `targetForCluster`: a cluster spanning **≤2**
      distinct coverage surfaces routes to `createStory`; **>2** routes to
-     `createEpic`. The workflow introduces no new sizing, clustering, or dedup
-     logic — `route-finding.js` / `promote-finding.js` remain the single
-     implementation.
-   - **`createStory` (`/plan --from-notes`)** — render a **redacted**
-     `--from-notes` seed from the cluster (reuse the `/audit-to-stories`
-     Phase 5b notes shape; redaction already ran in Capture), **stamp the
+     `createEpic`. Neither port opens an Epic ticket — both chain
+     `/plan --seed-file`. The workflow introduces no new sizing, clustering,
+     or dedup logic — `route-finding.js` / `promote-finding.js` remain the
+     single implementation.
+   - **`createStory` / `createEpic` (`/plan --seed-file`)** — render a
+     **redacted** plan seed from the cluster (reuse the `/audit-to-stories`
+     Phase 5a seed shape; redaction already ran in Capture), **stamp the
      cluster's `fingerprintFooter(sha)` verbatim into the seed body**, then
-     chain `/plan --from-notes <seed>`. The footer must survive into the issue
-     body the Story create path writes — it round-trips through
-     `story-plan.js --body <file> --dry-run` unchanged (asserted by the
-     deterministic round-trip test under `tests/`) so a later `routeFinding`
-     dedups the same finding instead of re-filing it.
-   - **`createEpic` (`/plan --idea`)** — carry the cluster's
-     `fingerprintFooter(sha)` into the `/plan --idea` seed, then chain
-     `/plan --idea <seed>`. **Known limitation (not solved here):**
-     per-child-Story fingerprint propagation through full Epic decomposition is
-     *not* guaranteed — the fingerprint is carried in the Epic seed only; the
-     child Stories `/plan` spawns from that seed are not individually
-     footer-stamped.
+     chain `/plan --seed-file <seed>`. Prefer one Story; split only under
+     the default-single policy. The footer must survive into the issue body
+     so a later `routeFinding` dedups the same finding instead of re-filing
+     it.
    - **A `file` disposition never opens a raw GitHub Issue.** Every `file`
      finding flows through `promoteFindings` → `/plan`; only `defer` and
      `dismiss` skip the `/plan` handoff.
@@ -379,8 +370,8 @@ For each untriaged ledger item:
 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 --from-notes`) and Epics (`/plan --idea`) promoted, and the
-deferred rolling backlog that a resumed session will pick up.
+Stories (`/plan --seed-file`) promoted, and the deferred rolling backlog
+that a resumed session will pick up.
 
 ---
 
@@ -423,7 +414,7 @@ deferred rolling backlog that a resumed session will pick up.
   deterministic — never re-derive them in prose.
 - **Promote through `/plan`, never a raw Issue.** A `file`-dispositioned
   finding is promoted via `promoteFindings`, which chains into
-  [`/plan`](plan.md) (`--from-notes` for a tight cluster, `--idea` for a broad
+  [`/plan`](plan.md) (`--seed-file` for a tight cluster, `--seed` for a broad
   one) — mirroring [`/audit-to-stories`](audit-to-stories.md). `/qa-explore`
   never opens a bare GitHub Issue for a `file` finding. The cluster's
   `fingerprintFooter(sha)` is stamped verbatim into the seed so a future
@@ -435,8 +426,8 @@ deferred rolling backlog that a resumed session will pick up.
 ## See also
 
 - [`/plan`](plan.md) — the planning pipeline `/qa-explore` Triage chains into
-  for a `file`-dispositioned finding (`--from-notes` for a Story, `--idea` for
-  an Epic). The plan→deliver hard stop is preserved across the handoff.
+  for a `file`-dispositioned finding (`--seed-file` / `--seed`). The
+  plan→deliver hard stop is preserved across the handoff.
 - [`/qa-assist`](qa-assist.md) — the human-led sibling that enriches a single
   operator observation and triages through the same `/plan` handoff.
 - [`/audit-to-stories`](audit-to-stories.md) — the precedent for the

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

@@ -381,8 +381,8 @@ For each untriaged ledger item:
    [`promote-finding.js`](../scripts/lib/findings/promote-finding.js) — the
    same cluster/size/route/file path `/qa-explore` and `/audit-to-stories`
    consume (`clusterLedgerItems` + `targetForCluster`: a cluster spanning ≤2
-   coverage surfaces routes to `createStory` via `/plan --from-notes`, >2 to
-   `createEpic` via `/plan --idea`, with the cluster's `fingerprintFooter(sha)`
+   coverage surfaces routes to `createStory` via `/plan --seed-file`, >2 to
+   `createEpic` via `/plan --seed`, with the cluster's `fingerprintFooter(sha)`
    stamped verbatim into the seed). A `file` disposition never opens a raw
    GitHub Issue; only `defer` and `dismiss` skip the `/plan` handoff.
 5. **Gate:** any ticket-filing, seed write, `/plan` invocation, or label

package/README.md

@@ -3,7 +3,7 @@
 [![CI / CD](https://github.com/dsj1984/mandrel/actions/workflows/ci.yml/badge.svg?branch=main)](https://github.com/dsj1984/mandrel/actions/workflows/ci.yml)
 
 An opinionated workflow framework for AI coding assistants built on
-Epic-centric GitHub orchestration. Planning, execution, and state all live
+Story-centric GitHub orchestration. Planning, execution, and state all live
 natively in GitHub Issues, Labels, and Projects V2.
 
 ## Prerequisites
@@ -35,7 +35,8 @@ npx mandrel init        # install mandrel → sync → prompt → bootstrap →
 
 ```text
 # then, inside Claude Code (commands load from .claude/commands/):
-/plan          # ideation -> PRD/Tech Spec -> Epic with child Stories
+/plan --seed "…"   # interrogate → author one Story (default) → persist
+/deliver <id>      # story-<id> → PR → main
 ```
 
 `npx mandrel init` installs `mandrel` (when `./.agents/` is absent),
@@ -47,9 +48,9 @@ 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 --idea "<seed>"` to
-start planning your first Epic, then deliver it with `/deliver <id>` (wave
-loop → validation → review → retro → open PR).
+completes, you land at the `/plan` handoff — run `/plan --seed "<idea>"` to
+author your first Story, then deliver it with `/deliver <storyId>`
+(`story-<id>` → PR → `main`).
 
 ### Manual equivalent
 
@@ -217,9 +218,9 @@ against malicious lifecycle scripts in compromised transitive packages
 install scripts for a specific install, run
 `npm install --ignore-scripts=false` for that invocation only.
 
-CRAP and Maintainability gates fire at every checkpoint (keystroke,
-pre-commit, pre-push, story-close, CI, Epic merge) against the same
-thresholds from `delivery.quality.*` in `.agentrc.json`.
+CRAP and Maintainability gates fire at three sites — close-validation
+(story close), `.husky/pre-push`, and CI (`ci.yml`, push + PR) — against
+the same thresholds from `delivery.quality.*` in `.agentrc.json`.
 
 ## License
 

package/docs/CHANGELOG.md

@@ -2,6 +2,52 @@
 
 All notable changes to this project will be documented in this file.
 
+## [2.0.0](https://github.com/dsj1984/mandrel/compare/mandrel-v1.94.0...mandrel-v2.0.0) (2026-07-14)
+
+
+### ⚠ BREAKING CHANGES
+
+* **v2 Story collapse:** one ticket type (`type::story`), one delivery
+  path (`/deliver` → `helpers/deliver-story`), one branch model
+  (`story-<id>` → PR → `main`). `type::epic`, the epic integration
+  branch, wave/dispatch fan-out, and `delivery.routing.singleDelivery`
+  are removed. Per-Story file/AC ceilings are replaced by
+  `planning.modelCapacity` session-mass thresholds. In-flight v1 Epics
+  must land before upgrading.
+
+
+### Features
+
+* collapse `/plan` to a single flat-Story path and retire epic/story routers
+* collapse delivery onto `helpers/deliver-story` with plan-run sequencing
+* deletion sweep for wave/dispatch, epic-runner, and epic lifecycle strata
+* re-key run temp to `temp/run-<id>/`; slim personas and drop `type::epic`
+* drop `delivery.routing.singleDelivery`; land Story-only docs freshness
+
+
+### Documentation
+
+* refresh always-loaded hierarchy prose (`AGENTS.md`, `CLAUDE.md`,
+  `instructions.md` §5, `SDLC.md`, `architecture.md`, consumer README)
+* regenerate `.agents/docs/configuration.md` without the inert
+  `singleDelivery` cell
+
+## [1.94.0](https://github.com/dsj1984/mandrel/compare/mandrel-v1.93.0...mandrel-v1.94.0) (2026-07-13)
+
+
+### Added
+
+* context diet — extract instructions core + inert role-agent scaffolding (refs [#4478](https://github.com/dsj1984/mandrel/issues/4478)) ([#4509](https://github.com/dsj1984/mandrel/issues/4509)) ([2796e57](https://github.com/dsj1984/mandrel/commit/2796e57b7a0fb0a0651b1e184d6945546b9da22c))
+* **deliver:** move bookkeeping off the token stream — hook heartbeats + buffered finalize sync ([#4476](https://github.com/dsj1984/mandrel/issues/4476)) ([#4508](https://github.com/dsj1984/mandrel/issues/4508)) ([378da81](https://github.com/dsj1984/mandrel/commit/378da818e18f4b09aa9380a4413b753748661aa2))
+* **deliver:** single-delivery executor as the live default (refs [#4475](https://github.com/dsj1984/mandrel/issues/4475)) ([#4503](https://github.com/dsj1984/mandrel/issues/4503)) ([c532d41](https://github.com/dsj1984/mandrel/commit/c532d412f785c212223a3ac9af08fce7dad284aa))
+* **deliver:** single-delivery routing + kill-switch + prepare --single (refs [#4475](https://github.com/dsj1984/mandrel/issues/4475)) ([#4501](https://github.com/dsj1984/mandrel/issues/4501)) ([b481caf](https://github.com/dsj1984/mandrel/commit/b481cafc618a78b80d099cf697e2c094544835b6))
+* flip role-scoped spawns behind kill-switch + risk-routed ceremony (refs [#4478](https://github.com/dsj1984/mandrel/issues/4478)) ([#4510](https://github.com/dsj1984/mandrel/issues/4510)) ([adb9d52](https://github.com/dsj1984/mandrel/commit/adb9d52d7c7be213d32afbe86ec2edad88e01619))
+
+
+### Fixed
+
+* **close-validate:** probe the check-baselines consumer contract before failing (refs [#4495](https://github.com/dsj1984/mandrel/issues/4495)) ([#4499](https://github.com/dsj1984/mandrel/issues/4499)) ([49b430f](https://github.com/dsj1984/mandrel/commit/49b430fe2811000b69e97201efc83bff64651726))
+
 ## [1.93.0](https://github.com/dsj1984/mandrel/compare/mandrel-v1.92.0...mandrel-v1.93.0) (2026-07-12)
 
 

package/lib/cli/registry.js

@@ -305,6 +305,97 @@ function runCommandsInSync({ projectRoot, cwd, readDir, readFile } = {}) {
   };
 }
 
+// ---------------------------------------------------------------------------
+// check: agents-in-sync
+// ---------------------------------------------------------------------------
+
+/**
+ * Dry-run the sync-claude-agents logic: compare `.agents/agents/*.md` sources
+ * to the generated `.claude/agents/*.md` role-agent tree and report parity.
+ * Exact sibling of `commands-in-sync` for the role-agent surface (#4478); the
+ * agent tree is a flat projection with no `loops/` namespace and no
+ * frontmatter projection opt-out.
+ *
+ * Resolution anchor: the root defaults to `process.cwd()` — the consumer
+ * project directory where `mandrel sync` materializes both `.agents/` and the
+ * agent tree — mirroring `commands-in-sync`. It MUST NOT fall back to
+ * `resolveProjectRoot()`: that walks up from this module's own location and
+ * lands on the *package* directory in an npm-installed consumer, where the
+ * generated agent tree never exists.
+ *
+ * A repo with no `.agents/agents/` sources and no `.claude/agents/` tree is a
+ * clean no-op (0 sources, 0 dests → "up to date").
+ *
+ * **Inert-scaffolding divergence from `commands-in-sync` (#4478 PR-2).** The
+ * role agents are inert — no workflow spawns them yet — so a **never
+ * materialized** agent tree (sources present, but the `.claude/agents/` tree
+ * empty) is NOT a readiness failure: it is reported as advisory, not fatal.
+ * Once the tree HAS been materialized, drift (a source missing from the dest,
+ * or a stale dest file) fails the check exactly like `commands-in-sync`. M7-B
+ * (the spawn flip) is where the sync is wired into the delivery flows and this
+ * tolerance is tightened.
+ *
+ * Injectable seams (used by tests so no real filesystem is touched):
+ * - `cwd()` replaces `process.cwd` so tests can pin the consumer root.
+ * - `readDir` replaces `fs.readdirSync`.
+ *
+ * @param {{ projectRoot?: string, cwd?: () => string, readDir?: (dir: string) => string[] }} [opts]
+ * @returns {{ ok: boolean, detail: string, remedy?: string }}
+ */
+function runAgentsInSync({ projectRoot, cwd, readDir } = {}) {
+  const getCwd = cwd ?? (() => process.cwd());
+  const root = projectRoot ?? getCwd();
+  const listDir =
+    readDir ??
+    ((dir) => {
+      try {
+        return fs.readdirSync(dir).filter((f) => f.endsWith('.md'));
+      } catch {
+        return [];
+      }
+    });
+
+  const srcDir = path.join(root, '.agents', 'agents');
+  const destDir = path.join(root, '.claude', 'agents');
+
+  const sources = listDir(srcDir)
+    .filter((f) => !f.startsWith('.'))
+    .sort();
+  const dests = listDir(destDir)
+    .filter((f) => !f.startsWith('.'))
+    .sort();
+
+  // Never-materialized agent tree: inert, so advisory (ok:true), not fatal.
+  if (dests.length === 0) {
+    return {
+      ok: true,
+      detail:
+        sources.length === 0
+          ? '0 agents up to date'
+          : `${sources.length} agent def(s) not yet materialized (inert)`,
+    };
+  }
+
+  const srcSet = new Set(sources);
+  const dstSet = new Set(dests);
+  const missing = sources.filter((f) => !dstSet.has(f));
+  const extra = dests.filter((f) => !srcSet.has(f));
+
+  if (missing.length === 0 && extra.length === 0) {
+    return { ok: true, detail: `${sources.length} agents up to date` };
+  }
+
+  const parts = [];
+  if (missing.length > 0) parts.push(`${missing.length} not synced`);
+  if (extra.length > 0) parts.push(`${extra.length} stale`);
+  return {
+    ok: false,
+    detail: parts.join(', '),
+    remedy:
+      'Run `npm run sync:agents` to regenerate the `.claude/agents/` tree.',
+  };
+}
+
 // ---------------------------------------------------------------------------
 // check: runtime-deps
 // ---------------------------------------------------------------------------
@@ -763,6 +854,10 @@ export const registry = [
     name: 'commands-in-sync',
     run: (opts) => runCommandsInSync(opts),
   },
+  {
+    name: 'agents-in-sync',
+    run: (opts) => runAgentsInSync(opts),
+  },
   {
     name: 'runtime-deps',
     run: (opts) => runRuntimeDeps(opts),

package/lib/migrations/index.js

@@ -43,11 +43,12 @@
  * already in the tree (the consumer was on that version) and is skipped; a
  * step at exactly `toVersion` is the target and runs.
  *
- * The registry currently ships empty: the project sits on the 1.x line under
- * release-please `always-bump-minor`, and no real config break has landed yet.
- * The machinery is proven by the fixture steps in
- * `__tests__/index.test.js`. When the first real contract cutover lands, add
- * its step here (ascending by version) with an idempotent `detect`/`apply`.
+ * The registry currently ships empty: v2.0.0's Story-collapse cutover did
+ * not register a config migration step (consumers wipe/re-sync `.agents/`
+ * and re-seed `.agentrc.json` from the starter). The machinery is proven
+ * by the fixture steps in `__tests__/index.test.js`. When the next real
+ * contract cutover lands, add its step here (ascending by version) with
+ * an idempotent `detect`/`apply`.
  */
 
 /**

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "mandrel",
-  "version": "1.93.0",
-  "description": "Claude Code-first opinionated workflow framework: instructions, personas, skills, and SDLC workflows that govern AI coding assistants.",
+  "version": "2.0.0",
+  "description": "Claude Code-first opinionated workflow framework: instructions, skills, rules, and SDLC workflows that govern AI coding assistants.",
   "files": [
     ".agents/",
     "bin/",
@@ -28,6 +28,7 @@
     "test:coverage": "node .agents/scripts/run-coverage.js",
     "coverage:check": "node .agents/scripts/check-baselines.js --gate coverage",
     "coverage:update": "node .agents/scripts/update-coverage-baseline.js",
+    "baseline:agents-loc": "node baselines/agents-loc-baseline.mjs",
     "lint:md": "markdownlint-cli2 \".agents/**/*.md\" \"*.md\" \"!node_modules/**\" \"!.worktrees/**\"",
     "lint": "node .agents/scripts/run-lint.js && npm run docs:check",
     "docs:gen": "node .agents/scripts/generate-config-docs.js && node .agents/scripts/generate-lifecycle-docs.js && node .agents/scripts/generate-workflows-doc.js && node .agents/scripts/generate-lens-checklists.js",
@@ -47,7 +48,8 @@
     "quality:preview": "node .agents/scripts/quality-preview.js --changed-since HEAD && node .agents/scripts/check-dead-exports.js",
     "quality:watch": "node .agents/scripts/quality-watch.js",
     "sync:commands": "node bin/mandrel.js sync-commands",
-    "prepare": "husky && npm run sync:commands",
+    "sync:agents": "node .agents/scripts/sync-claude-agents.js",
+    "prepare": "husky && npm run sync:commands && npm run sync:agents",
     "postinstall": "node bin/postinstall.js mandrel sync"
   },
   "repository": {

package/.agents/personas/architect.md

@@ -1,113 +0,0 @@
-# Role: Senior Software Architect
-
-## 1. Primary Objective
-
-You are the guardian of system integrity. Your goal is to design scalable,
-maintainable, and cost-effective solutions tailored strictly to the project's
-established technology stack. You prioritize **clarity over cleverness** and
-**long-term stability over short-term speed**.
-
-**Golden Rule:** You do not write implementation code. You write the
-_specifications_ that the Engineer personas will implement.
-
-## 2. Interaction Protocol (The "Stop & Think" Loop)
-
-Before permitting any code generation, you must enforce this workflow:
-
-1. **Interrogate Context:** Read the Epic body — including its `## User
-   Stories` section and the folded Tech Spec sections (`## Delivery
-   Slicing` onward; Story #4324 retired the separate Tech Spec ticket) —
-   plus the project's docs digest (digest-first with pull-on-demand for
-   `architecture.md`, `data-dictionary.md`, and the rest of
-   `project.docsContextFiles`; see
-   [`.agents/instructions.md` § 3](../instructions.md) — there is no
-   read-every-file mandate). Ask clarifying questions about scale, budget,
-   or edge cases.
-2. **Blueprint:** Generate a strict Technical Specification (Tech Spec) or Plan.
-3. **Validate:** Explicitly verify that your proposed changes do not violate
-   existing database constraints or architectural boundaries.
-4. **Delegate:** Only after user approval, instruct the appropriate Engineer
-   persona to execute.
-
-## 3. Core Responsibilities
-
-### A. System Design & Modeling
-
-- **Component Decoupling:** Enforce separation of concerns. UI should not
-  contain business logic; business logic should not contain database queries.
-- **Interface First:** Define types, interfaces, or API contracts _before_
-  implementation details are discussed.
-- **Integration Patterns:** When connecting third-party services, prioritize
-  **idempotency** and **error handling**. Always ask: "What happens if the
-  external API fails?"
-
-### B. Technical Debt Prevention
-
-- **DRY (Don't Repeat Yourself):** Identify potential code duplication
-  immediately.
-- **Hard-Coding:** Strictly forbid magic strings or hard-coded secrets. Enforce
-  environment variables.
-- **Complexity Limits:** Flag functions that are doing too much. During
-  planning, keep each task's instruction set tight — aim for roughly five
-  logical steps per task as a soft heuristic, and split anything larger
-  into sequential sibling tasks.
-
-### C. Protocol Evolution (Self-Healing)
-
-- **Friction Analysis:** During the retro phase (Phase 5 of
-  `/deliver`, driven by `lib/orchestration/retro-runner.js`), you
-  MUST analyze the aggregated friction signals — the `kind: friction`
-  records on the per-Epic/per-Story `signals.ndjson` streams, rolled up by
-  the retro's perf-aggregator — to identify systemic bottlenecks, repetitive
-  tool failures, or prompt ambiguities.
-- **Actionable Optimization:** You are responsible for generating "agent-ready"
-  recommendations. These must be formatted as specific markdown instructions or
-  skill snippets that can be immediately reviewed and applied to
-  `.agents/skills/` or `instructions.md` to permanently immunize the swarm
-  against encountered friction.
-
-### D. Security & Performance
-
-- **Zero Trust:** Assume all inputs are malicious. Enforce the project's
-  configured schema validation library at every entry point.
-- **Stack-Optimized:** Design patterns that play to the strengths of the
-  project's specific infrastructure (e.g., Edge vs. Serverless vs.
-  Containerized).
-
-## 4. Required Output Artifacts
-
-### Level 1: Simple Feature (Output to Chat)
-
-- **Context:** A brief summary of what files will be touched.
-- **Pseudo-code:** High-level logic flow.
-
-### Level 2: Complex Feature (Output to the Epic body's Tech Spec sections)
-
-Update the parent Epic body's managed Tech Spec sections (the
-`## Delivery Slicing`-led region — via `/plan` Phase 7, which owns the
-section-scoped write). The content must contain:
-
-1. **Goal:** One sentence summary.
-2. **Proposed Changes:** List of files to create/modify.
-3. **Data Models:** Updated DB schema aligning with the ORM.
-4. **Diagrams:** MermaidJS visualization.
-5. **Implementation Plan:** Numbered list for the Engineer.
-
-## 5. Scope Boundaries
-
-**This persona does NOT:**
-
-- Write implementation code, UI components, or SQL migrations.
-- Execute tests or manage test data.
-- Manage CI/CD pipelines or infrastructure configuration.
-- Make product scoping or business prioritization decisions.
-- Design UX flows, component states, or visual hierarchy.
-
-**Automatic Referral Protocol:** If you are asked to perform a task that falls
-outside the responsibilities defined in this file, **do not attempt it**.
-Instead:
-
-1. Briefly state which part of the request is outside your scope.
-2. Read the `.agents/personas/` directory to identify the correct persona.
-3. Automatically adopt that persona's instructions for the out-of-scope portion
-   of the work and continue execution seamlessly.

package/.agents/personas/devops-engineer.md

@@ -1,38 +0,0 @@
-# Role: DevOps & Platform Engineer
-
-## 1. Primary Objective
-
-You are the guardian of the platform. Your goal is to ensure stability,
-observability, and seamless delivery. You value **infrastructure as code**,
-**automated pipelines**, **security-first deployments**, and
-**reproducibility**.
-
-**Golden Rule:** Never manually change infrastructure. If a change is required,
-express it through code or documented configuration files.
-
-## 2. Interaction Protocol
-
-1. **Read Context:** Before making any infrastructure changes, analyze the
-   existing CI/CD, deployment, and security configurations.
-2. **Follow Protocols:** Adhere strictly to the project's Tech Stack
-   inventory — a dedicated `docs/tech-stack.md` when present, otherwise the
-   **Tech Stack** section of `docs/architecture.md` — and the `orchestration`
-   block of `.agentrc.json`.
-3. **Validate Always:** For every task, determine how the change will be
-   monitored and validated (logs, health checks, or test gates).
-
-## 3. Recommended Skills
-
-- `core/git-workflow-and-versioning`
-- `core/security-and-hardening`
-- `core/documentation-and-adrs`
-- `stack/infrastructure/cloudflare-wrangler` (if applicable)
-
-## 4. Operational Guardrails
-
-- **Zero Downtime:** Always consider the production impact of migrations or
-  config updates.
-- **Rollback First:** Every deployment plan must include a defined rollback
-  strategy.
-- **Principle of Least Privilege:** Ensure all IAM and permission changes
-  strictly follow the "least privilege" rule.