valent-pipeline 0.19.43 → 0.19.45

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "valent-pipeline",
-  "version": "0.19.43",
+  "version": "0.19.45",
   "description": "v3 multi-agent AI pipeline for software development lifecycle",
   "type": "module",
   "bin": {

package/pipeline/steps/orchestration/bug-intake.md

@@ -35,6 +35,7 @@ Write `stories/{story_id}/output/qa-test-spec.md` so QA-B can prove the fix:
 - **Affected-AC tests:** the existing test cases for the violated AC(s) (reference the source story's `qa-test-spec.md`) — they must still pass.
 - **Real-dependency evidence:** for each active profile, keep the profile's mandatory black-box check (live HTTP + real DB for `api`, real browser for `ui`, etc.) — a fix is only proven against the real boundary, not a mock. The defect class that caused the REJECT (CORS, serialization, auth header, wire-format) lives exactly there.
 - Do NOT invent broad new coverage — the point is to prove the defect is gone and nothing regressed.
+- **Embed each case ID in its test NAME** (same rule as `steps/qa-a/write-acceptance-tests.md` / `steps/bend/write-tests.md`): every regression + affected-AC case carries a `TC-…` id, and the test title MUST contain it — `it('TC-B1: P95 percentile uses the right rank', …)`. `check-spec-conformance` + `trace check` locate each spec'd case by its id in the EXECUTED junit test name; a case id that appears in no test name reads as a MISSING case and fails the evidence gate. State this explicitly in the spec so the dev embeds the ids up front — it is the recurring first-pass miss on bug fixes (a wasted rework cycle every time).
 - Also write the spec manifest `stories/{story_id}/output/qa-test-spec.manifest.json` (same shape as `steps/qa-a/write-spec.md` Step 10, including each case's `ac` mapping to the minimal reqs manifest) — the spec-conformance and trace gates run on bug items too.
 
 ## Step 4: Hand off

package/src/commands/evidence.js

@@ -16,7 +16,7 @@ import { dirname, join, isAbsolute } from 'path';
 import { randomBytes } from 'crypto';
 import { parse as parseYaml } from 'yaml';
 import {
-  runEvidence, pinGate, formatRunTrailer, formatRunDigest, resolveRoot, evidenceDir, latestRun, resolveRunForAssert, detectLabelMultiplex, latestPins,
+  runEvidence, pinGate, formatRunTrailer, formatRunDigest, resolveRoot, evidenceDir, latestRun, resolveRunForAssert, requiredCaseIdsForRun, detectLabelMultiplex, latestPins,
   verifyIntegrity, assertRules, assertRedRules, pinSourceDelta, snapshotFiles, buildProof, utcCompact,
   latestAssert, collectFailingCases, authenticateBaseline, verifyShipEvidence, sha256Hex,
   validStoryId, recordStageResults,
@@ -180,15 +180,18 @@ export async function evidenceAssertCmd(options) {
     process.exit(2);
   }
 
-  // Required acceptance case ids, read early so the run resolver can bind to the suite that actually
-  // carries them when a project multiplexes suites under one label (HARNESS-GAPS 2026-06-18 Gap 2).
+  // Required case ids, read early so the run resolver can bind to the suite that actually carries them
+  // when a project multiplexes suites under one label (HARNESS-GAPS 2026-06-18 Gap 2). Prefers
+  // acceptance-tagged cases (normal stories) but falls back to all required id'd cases for bug-fix
+  // manifests (regression cases carry no `kind`) — else requiredCaseIds is empty and the resolver
+  // binds to the newest full-suite run, false-rejecting a clean bug fix on the count check.
   // The full manifest is re-read below for the count/skips rules.
   let requiredCaseIds = [];
   try {
     const mp = options.manifest ? abs(options.manifest) : join(root, 'stories', story, 'output', 'qa-test-spec.manifest.json');
     if (existsSync(mp)) {
       const m = JSON.parse(readFileSync(mp, 'utf-8'));
-      if (Array.isArray(m?.cases)) requiredCaseIds = m.cases.filter((c) => c?.kind === 'acceptance' && c?.required !== false && c?.id).map((c) => c.id);
+      requiredCaseIds = requiredCaseIdsForRun(m?.cases);
     }
   } catch { requiredCaseIds = []; }