mandrel 2.49.0 → 2.50.0

package/.agents/scripts/lib/audit-to-stories/audit-label-taxonomy.js

@@ -8,8 +8,8 @@
  *   - the **creator** — `audit-labels-bootstrap.js`, which ran `gh label create`
  *     over the `audit::<lens>` list and nothing else;
  *   - the **generator** — `audit-to-stories/build-story-body.js`, which emitted
- *     `type::story`, `agent::ready`, `audit::<lens>` and — as a bare string
- *     literal — `risk::high`.
+ *     `type::story`, `audit::<lens>` and — as a bare string literal —
+ *     `risk::high`.
  *
  * `risk::high` was therefore generated by the filer and defined by **no**
  * taxonomy: not `LABEL_TAXONOMY` (the repo-wide bootstrap), not the audit
@@ -136,6 +136,14 @@ const AUDIT_STORY_AXIS_LABELS = Object.freeze([
     color: hex(LABEL_COLORS.TYPE),
     description: 'Story work item',
   },
+  // Created, never generated — the one deliberate asymmetry in this module.
+  // The filer emits no `agent::` state (see `STATIC_LABELS` in
+  // build-story-body.js): a freshly-filed audit Story is not delivery-ready,
+  // and `/mandrel-plan` stamps this label as its terminal flip after
+  // enrichment. The bootstrap still creates it so that flip has a label to
+  // apply on a repo where only the audit bootstrap has been run. The drift
+  // this module guards runs the other way — a generator inventing names the
+  // creator never made — so a creator-only entry is safe (Story #5229).
   {
     name: AGENT_LABELS.READY,
     color: hex(LABEL_COLORS.AGENT),

package/.agents/scripts/lib/audit-to-stories/build-story-body.js

@@ -10,9 +10,9 @@
  * Pure: returns { title, body, labels }. Labels carry one canonical
  * `audit::<lens>` per distinct source report represented in the merge
  * (derived from each finding's `sourceReport` basename, NEVER from the
- * fine-grained `dimension` text — see Story #4195), plus the standard
- * `type::story`, `agent::ready`, and (when any finding is Critical)
- * `risk::high`.
+ * fine-grained `dimension` text — see Story #4195), plus `type::story` and
+ * (when any finding is Critical) `risk::high`. Deliberately **no `agent::`
+ * state label** — see {@link STATIC_LABELS}.
  *
  * The body is serialized via the canonical story-body serializer
  * (`.agents/scripts/lib/story-body/story-body.js`) so the output round-trips
@@ -23,7 +23,7 @@
  */
 
 import path from 'node:path';
-import { AGENT_LABELS, RISK_LABELS, TYPE_LABELS } from '../label-constants.js';
+import { RISK_LABELS, TYPE_LABELS } from '../label-constants.js';
 import { serialize } from '../story-body/story-body.js';
 import { definesAuditLabel } from './audit-label-taxonomy.js';
 import { auditLabelsForFindings } from './audit-lenses.js';
@@ -32,7 +32,26 @@ import {
   renderSemanticKeyFooter,
 } from './finding-adapter.js';
 
-const STATIC_LABELS = Object.freeze([TYPE_LABELS.STORY, AGENT_LABELS.READY]);
+// The story-axis labels every generated audit Story carries, and the one it
+// deliberately does NOT: an `agent::` state.
+//
+// This used to be `[TYPE_LABELS.STORY, AGENT_LABELS.READY]`, which put every
+// Story the sweep filed one step from execution. `agent::ready` is precisely
+// what `/mandrel-deliver` reads as "available for pickup", and the bodies
+// reaching this function are audit prose — a synthesized acceptance line per
+// finding and an Agent Prompts section that is empty whenever the lens
+// captured no `agentPrompt`. Filing them ready contradicted the sweep's own
+// shipped runbook, whose enrich-before-you-deliver step says not to point
+// `/mandrel-deliver` at a freshly-filed audit Story; the label said the
+// opposite of the prose, and the label is the half a machine reads.
+//
+// The state axis therefore belongs to whoever enriches the finding:
+// `/mandrel-plan` stamps `agent::ready` as its terminal flip once the Story
+// has a `## Spec`, real acceptance criteria and runnable verify lines. An
+// absent `agent::` label is a legal initial state — `isValidTransition`
+// treats a null from-state as the initial-entry edge and permits any target —
+// so nothing downstream has to special-case the gap (Story #5229).
+const STATIC_LABELS = Object.freeze([TYPE_LABELS.STORY]);
 
 // The verify[] contract every generated audit Story carries. These commands
 // exist in this repo's harness (package.json scripts) so the Story satisfies

package/.agents/templates/docs/audit-sweep-runbook.md

@@ -145,10 +145,18 @@ Audit-sourced Stories carry a closed label set, so they can be filtered out of
 | Label | Meaning |
 | --- | --- |
 | `type::story` | Every emitted Story — the sweep never opens Epics or tasks. |
-| `agent::ready` | Filed and available for pickup. |
 | `audit::<lens>` | One per lens represented in the group; a cross-audit merge carries several. |
 | `risk::high` | Added when any finding in the group is Critical. |
 
+**There is no `agent::` state label in that set, and that is the point.** The
+sweep files a Story it has deliberately not made deliverable — Step 5 above is
+the reason. `agent::ready` is what `/mandrel-deliver` reads as "available for
+pickup", so a sweep that applied it would route unenriched audit prose straight
+into delivery, which is the outcome Step 5 tells you to avoid. The label is
+applied by `/mandrel-plan`, at the end of planning, once the finding is a
+scoped slice. If you file these Issues by hand, apply the emitted `labels[]`
+verbatim and do not top it up with a state.
+
 The lens labels are a **closed taxonomy**: only the canonical `audit::<lens>`
 names are valid, and the filer refuses to emit a label the repository has never
 created. Create them once with `audit-labels-bootstrap.js` before the first live

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

@@ -211,11 +211,17 @@ shared helper's `fingerprintFooter(sha)`
 Labels applied:
 
 - `type::story`
-- `agent::ready`
 - `audit::<dimension>` — one per dimension represented in the merge
   (cross-audit groups carry multiple).
 - `risk::high` — added when any finding in the group is Critical.
 
+**No `agent::` state label, deliberately.** The filer used to emit
+`agent::ready`, which is exactly what `/mandrel-deliver` reads as "available
+for pickup" — and these bodies are audit prose, not a delivery-ready Spec. A
+Story with no `agent::` label is a legal initial state; `/mandrel-plan` stamps
+`agent::ready` as its terminal flip once the finding has become a scoped
+capability slice. Do not re-add it here or apply it by hand at create time.
+
 ### Phase 5c — Wire the cohort's declared ordering (**required**)
 
 Creating the Issues is only the first pass. `groupFindings` detects `edges[]`

package/docs/CHANGELOG.md

@@ -15,6 +15,13 @@ All notable changes to this project will be documented in this file.
 -->
 <!-- markdownlint-disable-file MD004 MD012 MD037 -->
 
+## [2.50.0](https://github.com/dsj1984/mandrel/compare/mandrel-v2.49.0...mandrel-v2.50.0) (2026-09-08)
+
+
+### Fixed
+
+* stop /audit-to-stories emitting agent::ready on generated audit Stories… ([#5229](https://github.com/dsj1984/mandrel/issues/5229)) ([#5230](https://github.com/dsj1984/mandrel/issues/5230)) ([d095608](https://github.com/dsj1984/mandrel/commit/d09560866c42084aed3fb92fb91d8c9a49fe66e3))
+
 ## [2.49.0](https://github.com/dsj1984/mandrel/compare/mandrel-v2.48.0...mandrel-v2.49.0) (2026-09-08)
 
 

package/package.json

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