@dtlabs/ai-toolkit 0.24.6 → 0.24.7

package/CHANGELOG.md

@@ -1,4 +1,13 @@
 ## 0.1.4 (2026-07-21)
+## [0.24.7](https://github.com/dtlab-tech/ai-toolkit/compare/v0.24.6...v0.24.7) (2026-10-30)
+
+
+### Bug Fixes
+
+* **pm-phase1:** route validator findings to a document by their prefix when the flags are omitted ([7bd9a38](https://github.com/dtlab-tech/ai-toolkit/commit/7bd9a38de571c07d233a5212dfba9213a1b7d562))
+* **pm-phase1:** route validator findings to a document by their prefix when the flags are omitted ([f957d72](https://github.com/dtlab-tech/ai-toolkit/commit/f957d726294d2b563e67ba1c3f4e59f9c8d57be4))
+* **pm-phase1:** route validator findings to a document by their prefix when the flags are omitted ([e33faef](https://github.com/dtlab-tech/ai-toolkit/commit/e33faefc4488f256e42ec459cefa547f7b5efbf2))
+
 ## [0.24.6](https://github.com/dtlab-tech/ai-toolkit/compare/v0.24.5...v0.24.6) (2026-10-29)
 
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@dtlabs/ai-toolkit",
-  "version": "0.24.6",
+  "version": "0.24.7",
   "description": "AI Toolkit — reusable agents and procedures for developers to build AI-powered applications.",
   "files": [
     "docs/",

package/src/claude/workflows/pm-phase1.js

@@ -744,8 +744,14 @@ return c.run(meta.name, featureDir, prefix, async () => {
       // now-stale self-report. The only authoritative signal for the final verdict is whether any
       // finding remains, from any source, after every check this cycle has run.
       const mergedValid = mergedFindings.length === 0
-      const mergedNeedsTechSpecFix = result.needsTechSpecFix || newFindings.some(f => f.startsWith('Tech-Spec:'))
-      const mergedNeedsRequirementsFix = result.needsRequirementsFix || newFindings.some(f => f.startsWith('Requirements:'))
+      // Routing reads the prefix of EVERY finding, the validator's own included: the validator is
+      // required to prefix each finding with the document it concerns (gaia-validate-feature-docs,
+      // output contract), and its own example verdict omits needsRequirementsFix/needsTechSpecFix
+      // altogether. Reading the prefix only on host-computed findings made a verdict with prefixed
+      // findings and no flags fail with "flagged neither document" (seen on FTR-034). A finding
+      // with no prefix and no flag still fails closed below.
+      const mergedNeedsTechSpecFix = result.needsTechSpecFix || mergedFindings.some(f => f.startsWith('Tech-Spec:'))
+      const mergedNeedsRequirementsFix = result.needsRequirementsFix || mergedFindings.some(f => f.startsWith('Requirements:'))
 
       // c.worker() already wrote result.report verbatim via its own outputs[0] contract; only
       // overwrite it when this cycle actually added findings the LLM's own report text doesn't