mandrel 2.25.0 → 2.27.0

package/.agents/agents/acceptance-critic.md

@@ -115,10 +115,13 @@ For each acceptance item in your cluster:
 
 ## Verdict schema (MUST)
 
-Emit a verdict file under `temp/` conforming to
+Write a verdict file under `temp/` at a **cluster-unique path** (e.g.
+`temp/acceptance-verdict-<storyId>-r<round>-c<clusterIndex>.json`) so parallel
+sibling critics cannot overwrite each other, conforming to
 [`acceptance-eval-verdict.schema.json`](../schemas/acceptance-eval-verdict.schema.json):
 one `criteria[]` record per acceptance item in your cluster, in acceptance-array
-order.
+order. Each `index` is the criterion's position in the Story's **full**
+`acceptance[]` array, not within your cluster — the caller merges on it.
 
 ```json
 {
@@ -146,10 +149,11 @@ order.
 - `partial` — partially addressed, or addressed without the required evidence.
 - `unmet` — not addressed, or the evidence contradicts the claim.
 
-Hand the verdict path to the caller's `acceptance-eval.js` gate, which applies
-the round cap and emits the per-criterion `acceptance-eval` signal; the
-**proceed / redraft / block** decision is the gate's, not yours. You score; the
-gate decides.
+**Return the verdict file's absolute path to your caller — never invoke
+`acceptance-eval.js` yourself.** The caller merges every cluster's records into
+one verdict and calls the gate **once** per round; a per-cluster call would burn
+a Story-level round per cluster. The **proceed / redraft / block** decision is
+the gate's, not yours. You score; the gate decides.
 
 ## Boundaries
 

package/.agents/audit-checklists/baselines.md

@@ -0,0 +1,21 @@
+<!-- GENERATED FILE — do not edit by hand.
+     Source of truth: .agents/workflows/audit-baselines.md
+     Regenerate: node .agents/scripts/generate-lens-checklists.js
+     Drift is gated by: npm run docs:check
+-->
+
+# Baseline & Ratchet Audit — authoring checklist
+
+> Audit the committed baseline surface — dead instruments, stale baselines, cross-gate hotspot clusters, trend drift, and floor-tightening headroom — and emit findings whose remediation burns the measured debt down and tightens the ratchet behind it.
+
+Self-check your change against this lens's concerns before you ship:
+
+- [ ] `configError` non-null.
+- [ ] `degradations`.
+- [ ] Dead Instruments.
+- [ ] Staleness.
+- [ ] Hotspot Clusters.
+- [ ] Trend Drift.
+- [ ] Tightening Headroom.
+- [ ] Hotspot Cluster template
+- [ ] Tightening Headroom template

package/.agents/docs/quality-gates.md

@@ -102,13 +102,18 @@ npm run coverage:update # writes baselines/coverage.json from the run
 runners that orchestrate coverage capture separately).
 
 The files-out-of-scope list is declared in [`.c8rc.cjs`](../../.c8rc.cjs) —
-thin CLI shells (e.g. `agents-bootstrap-github.js`, `plan-context.js`,
-`plan-persist.js`) plus the larger Story #1702 carve-out of
-top-level/orchestration/git CLIs and `lib/*` glue, each with a per-entry
-rationale in the `.c8rc.cjs` header comment (the authoritative list). Every
-excluded file also carries `/* node:coverage ignore file */` at the top of its
-source as a second line of defence; the header comment MUST be updated when the
-list changes.
+thin CLI shells plus the larger Story #1702 carve-out of
+top-level/orchestration/git CLIs and `lib/*` glue. The `exclude[]` array is
+the **single** declaration: each entry carries its rationale as an inline
+comment on the line above it. Story #4922 removed the prose inventory the
+header used to duplicate — two copies of one list in one file, 27 files
+apart by the time it was measured. Do not reintroduce one. Every excluded
+file also carries `/* node:coverage ignore file */` at the top of its source
+as a second line of defence.
+
+`.c8rc.cjs`'s `include` globs and `delivery.quality.gates.coverage.targetDirs`
+in [`.agentrc.json`](../../.agentrc.json) MUST name the same roots — the gate
+scores what c8 measures. `tests/c8rc-scope.test.js` asserts both invariants.
 
 ---
 
@@ -123,11 +128,30 @@ touched it:
 
 | Metric | Floor | Scope |
 | --- | --- | --- |
-| Coverage — lines | ≥ 90 % | per file |
-| Coverage — branches | ≥ 85 % | per file |
-| Coverage — functions | ≥ 90 % | per file |
-| Maintainability Index | ≥ 70 | per file |
-| CRAP | ≤ 20 | per method |
+| Coverage — lines | ≥ 94 % | repo rollup |
+| Coverage — branches | ≥ 85 % | repo rollup |
+| Coverage — functions | ≥ 87 % | repo rollup |
+| Maintainability Index | ≥ 70 | repo rollup |
+| CRAP — methods above 20 | ≤ 13 | repo rollup |
+
+Floors are enforced against the baseline's `rollup` components — the
+`applyFloors` phase compares `rollup["*"]` (and any named component), never
+individual rows. Story #4922 corrected this table, which previously read
+"per file" and quoted 90/85/90 for coverage; those numbers came from the
+example in `.agents/docs/agentrc-reference.json`, which is validated only
+against itself, and the coverage gate was not configured at all.
+
+The live coverage floors are derived from the measurement in
+[`baselines/coverage.json`](../../baselines/coverage.json) — a full-tier run
+scored 95.65 / 86.16 / 88.52, and each floor sits ~1–1.7 points under its
+axis. Re-derive them, do not invent them, whenever the baseline is
+regenerated wholesale.
+
+The coverage gate deliberately declares **no `tolerance`**, so its
+head-vs-base ratchet arm reports regressions without failing the build (the
+same shape the `crap` gate uses). Story #4922's scope was making the
+instrument honest; arming the ratchet belongs with the debt burn-down that
+the widened measurement newly exposes.
 
 The floors are declared in [`.agentrc.json`](../../.agentrc.json) under
 `delivery.quality.gates.<gate>.floors.*` (defaults baked into the helper
@@ -173,11 +197,11 @@ The floor gate is only as strict as its scope, so the `exclude` list in
 [`.c8rc.cjs`](../../.c8rc.cjs) carries three hard requirements that are
 enforced by review (and partially by the audit suite):
 
-1. **One-line rationale per entry.** Every file in `exclude[]` MUST have
-   a bulleted justification in the `.c8rc.cjs` header comment naming
-   *why* it is excluded — typically "thin CLI shell, meaningful logic
-   lives in `lib/<X>` and is unit-tested there." A bare path with no
-   rationale is a review-block.
+1. **One-line rationale per entry.** Every file in `exclude[]` MUST carry
+   an inline comment on the line(s) directly above it naming *why* it is
+   excluded — typically "thin CLI shell, meaningful logic lives in
+   `lib/<X>` and is unit-tested there." A bare path with no rationale is a
+   review-block, and `tests/c8rc-scope.test.js` fails on one.
 2. **`/* node:coverage ignore file */` pragma at source.** Every
    excluded file MUST carry the Node coverage pragma at the top of its
    own source. This is the second line of defence: when `c8 report` and
@@ -260,6 +284,42 @@ default and the deep-merge extender form).
 
 ---
 
+## Cyclomatic ceiling ratchet
+
+`delivery.quality.codingGuardrails.cyclomaticMustFix` (default `12`) is the
+per-function complexity ceiling, enforced by `check-cyclomatic.js`. It is a
+**standalone ratchet** — the same slot as `check-arch-cycles.js`,
+`check-dead-exports.js`, and `check-context-budget.js` — not a
+`delivery.quality.gates` kind, so it needs no gate block and no floor.
+
+```bash
+node .agents/scripts/check-cyclomatic.js            # the gate
+node .agents/scripts/check-cyclomatic.js --update   # re-record the breaches
+```
+
+`baselines/cyclomatic.json` records, per file, how many functions currently
+sit above the ceiling and how bad the worst one is. The gate fails when a
+file's over-ceiling count rises (including `0 → 1`, a brand-new breach) or
+when its worst function gets worse than recorded. Shrinking and disappearing
+are the success signals and never fail.
+
+Recording existing breaches is what makes the ceiling adoptable: a repository
+with dozens of over-ceiling functions can turn the gate on today and burn them
+down on its own schedule, instead of disabling a gate that fails on the first
+commit. Re-run `--update` after a deliberate refactor; that is the only motion
+allowed to raise a recorded count, and it shows up in review as a baseline
+diff.
+
+The scan reuses `delivery.quality.gates.maintainability.targetDirs` /
+`ignoreGlobs` — both instruments read the same coverage-free escomplex
+surface, so a separate scope declaration could only ever restate it.
+
+`cyclomaticFlag` (default `8`) is the softer half of the pair: it is not
+gated, and names the ceiling `quality:preview` counts new methods against in
+its `new-method count over c=<flag>` column.
+
+---
+
 ## CRAP gate — Consumer onboarding
 
 > Baseline envelope, axes, and component model: see the
@@ -436,7 +496,9 @@ are not comparable to rows scored by this one, and neither `kernelVersion` nor
 therefore carries a `scoringSemantics` stamp; `check-baselines` fails closed on
 a mismatch with the exact re-baseline command rather than comparing across the
 boundary. Bump the stamp whenever the coverage join, the line coordinate
-system, or the unresolved-method policy changes.
+system, the unresolved-method policy, or the method identity rule changes —
+Story #4969 bumped it for the last of these, replacing escomplex's positional
+`<anon method-N>` label with an enclosing-scope-path identity.
 
 ---
 

package/.agents/docs/workflows.md

@@ -32,12 +32,13 @@ by `node .agents/scripts/generate-workflows-doc.js`; `npm run docs:check`
 fails when it drifts from the on-disk workflow set. To change a command’s
 description, edit the workflow file’s front-matter and regenerate.
 
-## Commands (25)
+## Commands (27)
 
 | Command | Description |
 | --- | --- |
 | `/audit-accessibility` | Audit WCAG accessibility conformance (static-first) with an optional runtime verification pass, and produce a structured findings report |
 | `/audit-architecture` | Audit architectural boundaries, module coupling, layering violations, and shipped-but-uncalled seams; emit a structured findings report keyed to the canonical severity scale. |
+| `/audit-baselines` | Audit the committed baseline surface — dead instruments, stale baselines, cross-gate hotspot clusters, trend drift, and floor-tightening headroom — and emit findings whose remediation burns the measured debt down and tightens the ratchet behind it. |
 | `/audit-clean-code` | Audit code smells, dead code, complexity hotspots, and maintainability-index outliers; emit a structured findings report. |
 | `/audit-data-model` | Audit the persistence layer as a first-class artifact — model↔migration↔seed drift, constraint completeness, migration hygiene, type fidelity, and access-pattern fit; gated by a persistence-layer applicability probe so DB-less repos skip cleanly. |
 | `/audit-dependencies` | Audit `package.json` for unused, outdated, and major-version-stale dependencies; surface Node-engine drift and propose upgrade batches. |
@@ -56,6 +57,7 @@ description, edit the workflow file’s front-matter and regenerate.
 | `/git-cleanup` | Tidy the local checkout in four phases: fast-forward `main`, prune stale remote-tracking refs, sweep merged branches (squash-aware), and triage `git stash` entries — each step gated by operator confirmation. |
 | `/git-deliver` | Single ad-hoc delivery command for working-tree changes. Detects the git setup and escalates to the right terminal step — commit only, commit + push, or commit + push + open a PR with native auto-merge — picking the default from observable state and letting flags pin any level explicitly. Replaces the retired git-commit-all, git-push, and git-pr-all trio. |
 | `/mandrel-update` | npm-era upgrade wraparound for a Mandrel consumer. Runs `npx mandrel update` (resolve newest published version → install → re-materialize `.agents/` → migrate → doctor → surface changelog) as the single mechanical step, then walks the operator through the judgment wraparound the CLI deliberately leaves unowned: reconcile `.agentrc.json`, install the stabilized quality-gate surface, refresh the harness permission allowlist, reconcile the consumer's `AGENTS.md` / runbooks against the surfaced changelog, and stage + commit the staged lockfile bump. |
+| `/memory-consolidate` | 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 goes quiet. |
 | `/plan` | Unified planning entry point. Interrogate → author → persist. Emits one Story by default; splits into N>1 only under the default-single split policy. |
 | `/prototype` | Operator-invoked UI prototype pass. Discovers the consumer's design-system SSOT first, then — only after the operator confirms — writes exactly one self-contained HTML file under the gitignored workspace-root temp tree, so a layout can be reviewed before its UI acceptance criteria are authored. |
 | `/qa-assist` | 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. |

package/.agents/instructions.md

@@ -79,7 +79,7 @@ present, else the **Tech Stack** section of `docs/architecture.md`.
 
 You MUST log operational friction (repeated tool errors, unrecoverable
 command failures, self-corrected ambiguity, automatable boilerplate):
-`node .agents/scripts/diagnose-friction.js --story [STORY_ID] --cmd [FAILED_COMMAND]`
+`node .agents/scripts/diagnose-friction.js --story [STORY_ID] --cmd <cmd> <args...>`
 — a **local NDJSON signal** (not posted to the ticket). Schema and the
 `AGENT_LOG_LEVEL` table:
 [`docs/execution-reference.md`](docs/execution-reference.md#friction-telemetry).

package/.agents/schemas/audit-rules.json

@@ -167,6 +167,21 @@
       "scope": "cumulative",
       "substitutionKeys": []
     },
+    "audit-baselines": {
+      "triggers": {
+        "gates": ["gate3"],
+        "keywords": [
+          "baseline",
+          "ratchet",
+          "floor",
+          "headroom",
+          "quality gate"
+        ],
+        "filePatterns": ["baselines/**", ".agentrc.json"]
+      },
+      "scope": "cumulative",
+      "substitutionKeys": []
+    },
     "audit-documentation": {
       "triggers": {
         "gates": ["gate1", "gate3"],

package/.agents/schemas/baselines/audit-baselines-envelope.schema.json

@@ -0,0 +1,242 @@
+{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "$id": "https://mandrel/.agents/schemas/baselines/audit-baselines-envelope.schema.json",
+  "title": "AuditBaselinesEnvelope",
+  "description": "Evidence envelope emitted by `.agents/scripts/audit-baselines.js` (Story #4902). Unlike its siblings in this directory it does NOT describe a committed baseline — it describes an engine's read-only report ABOUT the baseline surface, so it deliberately does not extend baseline-envelope.schema.json. Four sections: gateSurface (instrument health per kind), hotspots (ranked per-file clusters joining top-N outliers across gates), trend (rollup deltas from each baseline file's git history), and headroom (configured floor vs measured rollup).",
+  "type": "object",
+  "required": [
+    "kind",
+    "schemaVersion",
+    "generatedAt",
+    "cwd",
+    "topN",
+    "configError",
+    "degradations",
+    "gateSurface",
+    "hotspots",
+    "trend",
+    "headroom"
+  ],
+  "additionalProperties": false,
+  "properties": {
+    "kind": { "const": "audit-baselines-envelope" },
+    "schemaVersion": { "type": "string", "minLength": 1 },
+    "generatedAt": { "type": "string", "format": "date-time" },
+    "cwd": {
+      "type": "string",
+      "minLength": 1,
+      "description": "Repository root the engine ran against."
+    },
+    "topN": {
+      "type": "integer",
+      "minimum": 0,
+      "description": "Per-gate bound on extracted outlier rows. The envelope never embeds a full baseline; crap.json alone is ~650KB of per-method rows."
+    },
+    "configError": {
+      "type": ["string", "null"],
+      "description": "Message from a failed config resolution. Non-null means floors, targetDirs, and ignoreGlobs were unavailable and the engine fell back to default baseline paths."
+    },
+    "degradations": {
+      "type": "object",
+      "description": "Which optional inputs were unavailable. Each degradation collapses its rank multiplier to exactly 1.0 and never changes the exit code.",
+      "required": ["gitHistory", "importGraph", "frictionLedger"],
+      "additionalProperties": false,
+      "properties": {
+        "gitHistory": { "type": "boolean" },
+        "importGraph": { "type": "boolean" },
+        "frictionLedger": { "type": "boolean" }
+      }
+    },
+    "gateSurface": {
+      "type": "array",
+      "description": "One entry per kind across BOTH halves of the surface: the closed delivery.quality.gates kinds and the out-of-band ratchet baselines the CI baselines job owns.",
+      "items": {
+        "type": "object",
+        "required": [
+          "kind",
+          "surface",
+          "baselinePath",
+          "configured",
+          "baselineExists",
+          "stub",
+          "rowCount",
+          "measured",
+          "generatedAt",
+          "staleDays",
+          "staleCommits",
+          "surfaceStale",
+          "deadIgnoreGlobs",
+          "parseError"
+        ],
+        "additionalProperties": false,
+        "properties": {
+          "kind": { "type": "string", "minLength": 1 },
+          "surface": { "enum": ["gate", "ratchet"] },
+          "baselinePath": { "type": "string", "minLength": 1 },
+          "configured": {
+            "type": "boolean",
+            "description": "A gate block for this kind is present in the resolved config."
+          },
+          "baselineExists": { "type": "boolean" },
+          "stub": {
+            "type": "boolean",
+            "description": "Zero rows AND an all-zero rollup — an instrument that passes every run vacuously. Both halves are required, so a ratchet baseline with nothing to report (e.g. zero import cycles) is never mistaken for a dead instrument."
+          },
+          "rowCount": {
+            "type": "integer",
+            "minimum": 0,
+            "description": "Rows AFTER the kind's per-file aggregation, so it is a file count for kinds whose on-disk grain is finer (dead exports are one row per {file, symbol}). Read `measured` for the quantity the instrument reports."
+          },
+          "measured": {
+            "type": ["object", "null"],
+            "description": "The whole-repo quantity in the unit the instrument measures — symbols for dead exports, bytes for context budget. Null when the baseline is absent or unreadable. Sits beside rowCount because the two legitimately disagree.",
+            "required": ["unit", "value"],
+            "additionalProperties": false,
+            "properties": {
+              "unit": { "type": "string", "minLength": 1 },
+              "value": { "type": "number" }
+            }
+          },
+          "generatedAt": { "type": ["string", "null"] },
+          "staleDays": {
+            "type": ["integer", "null"],
+            "description": "Whole days since generatedAt. Null when the stamp is absent or unparseable — never a fabricated 0. Wall time only: a baseline can read 0 here and still predate the surface it scores, which is what staleCommits catches."
+          },
+          "staleCommits": {
+            "type": ["integer", "null"],
+            "description": "Commits touching the measured surface (the gate's targetDirs, else the baseline's own row paths) since the baseline was last committed. Null when git cannot answer or the surface is not path-keyed — an unknown count, never a reassuring 0.",
+            "minimum": 0
+          },
+          "surfaceStale": {
+            "type": ["boolean", "null"],
+            "description": "staleCommits > 0 — the baseline is older than the surface it scores, independent of wall-clock age. Null when staleCommits is unknown."
+          },
+          "deadIgnoreGlobs": {
+            "type": "array",
+            "description": "Configured ignoreGlobs matching zero files on disk.",
+            "items": { "type": "string" }
+          },
+          "parseError": { "type": ["string", "null"] }
+        }
+      }
+    },
+    "hotspots": {
+      "type": "array",
+      "description": "Per-file clusters, highest rank first. Severity sums across gate memberships, so a file that is an outlier in two gates outranks a single-gate outlier of equal per-gate severity.",
+      "items": {
+        "type": "object",
+        "required": [
+          "path",
+          "gates",
+          "gateKinds",
+          "gateCount",
+          "severityWeight",
+          "churnWeight",
+          "centralityWeight",
+          "frictionWeight",
+          "rank"
+        ],
+        "additionalProperties": false,
+        "properties": {
+          "path": {
+            "type": "string",
+            "minLength": 1,
+            "description": "Cluster key. A repository file path for every kind except lighthouse (route) and bundle-size (bundle name)."
+          },
+          "gates": {
+            "type": "array",
+            "minItems": 1,
+            "items": {
+              "type": "object",
+              "required": [
+                "kind",
+                "metric",
+                "value",
+                "rowCount",
+                "severityWeight"
+              ],
+              "additionalProperties": false,
+              "properties": {
+                "kind": { "type": "string", "minLength": 1 },
+                "metric": { "type": "string", "minLength": 1 },
+                "value": { "type": "number" },
+                "rowCount": { "type": "integer", "minimum": 1 },
+                "severityWeight": { "type": "number", "minimum": 0 }
+              }
+            }
+          },
+          "gateKinds": { "type": "array", "items": { "type": "string" } },
+          "gateCount": { "type": "integer", "minimum": 1 },
+          "severityWeight": { "type": "number", "minimum": 0 },
+          "churnWeight": { "type": "number", "minimum": 1 },
+          "centralityWeight": { "type": "number", "minimum": 1 },
+          "frictionWeight": { "type": "number", "minimum": 1 },
+          "rank": { "type": "number", "minimum": 0 }
+        }
+      }
+    },
+    "trend": {
+      "type": "array",
+      "description": "Newest-vs-previous rollup deltas parsed from each baseline file's git history. Empty when no history is readable.",
+      "items": {
+        "type": "object",
+        "required": [
+          "kind",
+          "baselinePath",
+          "sampleCount",
+          "from",
+          "to",
+          "deltas"
+        ],
+        "additionalProperties": false,
+        "properties": {
+          "kind": { "type": "string", "minLength": 1 },
+          "baselinePath": { "type": "string", "minLength": 1 },
+          "sampleCount": { "type": "integer", "minimum": 2 },
+          "from": { "$ref": "#/definitions/commitRef" },
+          "to": { "$ref": "#/definitions/commitRef" },
+          "deltas": {
+            "type": "object",
+            "description": "Axis-by-axis `to - from`. Each key NAMES THE UNIT the delta is denominated in — `symbols` for dead exports, `bytes` for context budget, `filesTracked` where the metric is a non-additive score with no honest whole-repo sum. A kind carrying its own rollup keeps that rollup's axes.",
+            "additionalProperties": { "type": "number" }
+          }
+        }
+      }
+    },
+    "headroom": {
+      "type": "array",
+      "description": "Configured floor vs measured rollup per axis. Positive headroom is slack the floor could be tightened into; negative means the floor is already breached.",
+      "items": {
+        "type": "object",
+        "required": [
+          "kind",
+          "axis",
+          "floor",
+          "measured",
+          "direction",
+          "headroom"
+        ],
+        "additionalProperties": false,
+        "properties": {
+          "kind": { "type": "string", "minLength": 1 },
+          "axis": { "type": "string", "minLength": 1 },
+          "floor": { "type": "number" },
+          "measured": { "type": ["number", "null"] },
+          "direction": { "enum": ["gte", "lte"] },
+          "headroom": { "type": ["number", "null"] }
+        }
+      }
+    }
+  },
+  "definitions": {
+    "commitRef": {
+      "type": "object",
+      "required": ["sha", "committedAt"],
+      "additionalProperties": false,
+      "properties": {
+        "sha": { "type": "string", "minLength": 7 },
+        "committedAt": { "type": "string", "minLength": 1 }
+      }
+    }
+  }
+}

package/.agents/schemas/baselines/baseline-envelope.schema.json

@@ -29,6 +29,10 @@
       "type": "string",
       "description": "Optional per-kind stamp identifying the TypeScript transpiler that produced the sourcemap these rows' line coordinates were resolved through (Story #4866). Only meaningful for kinds whose rows carry a line coordinate derived from transpiled sources; a transpiler change can move every such coordinate, and for kinds that key rows on a line that coordinate is half the row identity."
     },
+    "provenanceStamped": {
+      "type": "boolean",
+      "description": "Optional per-kind POSITIVE assertion that the writer which produced these rows recorded each row's coordinate provenance (Story #4901). Only meaningful for kinds whose rows carry a line coordinate that may be transpiled. Absence is the only evidence a baseline written before provenance existed leaves behind — such a baseline claims by omission that every row is an original-source coordinate — so the kind's compat axis fails it closed with re-seed guidance rather than letting the comparator key rows against a coordinate space they are not in."
+    },
     "rollup": {
       "type": "object",
       "description": "Aggregate metrics keyed by component. The '*' key is reserved for the whole-repo rollup and is REQUIRED; additional keys MAY be present, one per declared component.",

package/.agents/schemas/baselines/crap.schema.json

@@ -10,6 +10,10 @@
       "type": "string",
       "description": "Identifier for the per-method coverage-join semantics that produced these rows (Story #4775). Deliberately NOT constrained to the current value here: an old-semantics baseline must reach the gate's compat axis, which fails it closed with an explicit re-baseline command, rather than being rejected with a raw schema error."
     },
+    "provenanceStamped": {
+      "type": "boolean",
+      "description": "Positive assertion that the writer which produced these rows recorded coordinate provenance per row (Story #4901). Absence is the ONLY evidence a pre-Story-#4866 baseline leaves — such a baseline claims by omission that every row is an original-source coordinate while some are transpiled. Deliberately optional and unconstrained here for the same reason as scoringSemantics: an unstamped baseline must reach the `provenance-unstamped` compat axis, which fails it closed with the re-seed command when it also carries transpiled-source rows, rather than dying on a raw schema error. A pure-JavaScript baseline never needs it."
+    },
     "rollup": {
       "type": "object",
       "required": ["*"],
@@ -49,6 +53,10 @@
           "method": { "type": "string" },
           "startLine": { "type": "integer", "minimum": 1 },
           "crap": { "type": "number", "minimum": 0 },
+          "anonymous": {
+            "enum": [true],
+            "description": "Marks `method` as a DERIVED identity rather than a name the source carries (Story #4969). escomplex labels an unnamed function `<anon method-N>`, where N is a per-module counter, so inserting one anonymous function renumbers every later one and re-keys 34.6% of this baseline's rows; the derived identity is the method's enclosing-scope path plus its parameter list, which is invariant under edits elsewhere in the file. Written ONLY when true, mirroring `coordinateSystem`: a named row keeps the exact four-key shape it always had. Absence on a row whose `method` still looks anonymous is the signature of a half-migrated baseline — rows preserved verbatim by a diff-scoped refresh under an envelope stamped with the current semantics — which the `anon-identity-unstamped` compat axis fails closed."
+          },
           "coordinateSystem": {
             "enum": ["transpiled"],
             "description": "Coordinate provenance of startLine (Story #4866). Written ONLY when the row kept transpiled coordinates because its sourcemap lookup did not resolve — the absent-means-'original' default keeps a pure-JavaScript baseline byte-identical, since JavaScript coordinates already ARE original-source coordinates. A row carrying this key is not comparable to one without it: the compare refuses to resolve the two through its nearest-line drift heuristic rather than manufacturing a regression from the gap between two coordinate systems."

package/.agents/schemas/model-attribution.schema.json

@@ -3,6 +3,10 @@
   "$id": "https://github.com/dsj1984/mandrel/blob/main/.agents/schemas/model-attribution.schema.json",
   "title": "ModelAttribution",
   "description": "Payload of the <!-- structured:model-attribution --> comment upserted onto a Task ticket at the moment it transitions to agent::executing (Story #2813). One entry per Task. Story- and Epic-level breakdowns are derived at query time from the child Tasks' attribution comments — there is no Story/Epic-scope emission.",
+  "x-mandrel-uncompiled": {
+    "reason": "Deliberate: this document is the SSOT for the shape, but no AJV instance compiles it. The framework does not pull AJV into the structured-comment path — that path uses hand-rolled shape guards — so the runtime gate below mirrors this document by hand. Keep the two in step: an edit here is only real once the validator enforces it. Declared in-file per Story #4938 so a reader is never left inferring authority from the file's mere existence.",
+    "runtimeGate": ".agents/scripts/lib/orchestration/model-attribution.js#validateModelAttributionPayload"
+  },
   "type": "object",
   "additionalProperties": false,
   "required": ["kind", "ticketId", "model", "source", "recordedAt"],