@dtlabs/ai-toolkit 0.19.1 → 0.19.2

package/CHANGELOG.md

@@ -1,4 +1,12 @@
 ## 0.1.4 (2026-07-21)
+## [0.19.2](https://github.com/dtlab-tech/ai-toolkit/compare/v0.19.1...v0.19.2) (2026-10-19)
+
+
+### Bug Fixes
+
+* **workflow-control, tech-spec-assembler:** unwrap whole response fences in Markdown documents to prevent content loss ([fe88582](https://github.com/dtlab-tech/ai-toolkit/commit/fe885821bb7b813237a1d53ed827c70e09b6c9d0))
+* **workflow-control, tech-spec-assembler:** unwrap whole response fences in Markdown documents to prevent content loss ([358e484](https://github.com/dtlab-tech/ai-toolkit/commit/358e4847fe74c314c3c1158dbeda08669530c1f8))
+
 ## [0.19.1](https://github.com/dtlab-tech/ai-toolkit/compare/v0.19.0...v0.19.1) (2026-10-19)
 
 

package/lib/workflow-control.js

@@ -238,6 +238,13 @@ function createControl(options) {
         const candidate = extractDelimitedStructuredOutput(result.result.result, opts.schema);
         if (candidate != null) { payload = candidate; usedTextFallback = true; }
       }
+      // A non-schema worker's payload IS the document — unwrap a whole-response fence/preamble
+      // before anything downstream (the caller's own write, or this function's own outputTarget
+      // write below) ever sees it. See extractMarkdownDocument's own comment for the full story.
+      if (!opts.schema && typeof payload === 'string') {
+        const cleaned = extractMarkdownDocument(payload);
+        if (cleaned !== payload) { payload = cleaned; usedTextFallback = true; }
+      }
       if (payload == null || (typeof payload === 'string' && !payload.trim())) {
         if (opts.schema) {
           const fields = (opts.schema.required || []).join(', ') || '(see requested schema)';
@@ -476,6 +483,65 @@ function extractJsonDocument(text) {
   return text;
 }
 
+// Same problem extractJsonDocument fixes, for a Markdown document deliverable (a component/
+// use-case/task detail file, or a Requirements/Tech-Spec skeleton) instead of a JSON one: a
+// worker's entire response becomes the file verbatim (these agents have no Write tool, see
+// worker()'s own comment on why — the host writes whatever text they return), and a model that
+// wraps its deliverable in conversational prose and/or an outer code fence silently corrupts the
+// saved file. Found empirically in a real spec/components/*.md file: the agent's own real
+// "## Change"/"## Tests" headings ended up INSIDE an outer ```markdown fence and were (correctly)
+// treated as fenced, non-heading content by tech-spec-assembler.js's own fence-aware parser
+// (FTR-025) — the file wrote to disk with its real content unreachable, surfacing only much later
+// as an opaque "component file is missing its ## Change section" error during final assembly, with
+// no filename attached to say which one (see loadTechSpec's own fix for that half of the bug).
+//
+// Same "try as-is first, re-validate the candidate, never a blind substring guess, never throws"
+// discipline as extractJsonDocument: "valid" here means "has at least one unfenced Markdown
+// heading" — the same fence-length-aware scan tech-spec-assembler.js's own
+// _nonFencedHeadingIndexes uses, reimplemented here as a presence check rather than a line-index
+// list, for the identical "sandboxed runtime has no require()"-shaped reason these two files are
+// already siblings, not shared, elsewhere in this codebase. A document that legitimately ends in
+// its own small fenced code example (a real Tests section's last line) is never mistaken for a
+// whole-response wrap: its real headings already appear BEFORE that trailing fence, unfenced, so
+// the as-is candidate already satisfies this check and no unwrapping is even attempted.
+function _hasUnfencedHeading(text) {
+  let fenceLen = 0;
+  for (const line of text.split('\n')) {
+    const m = line.match(/^(`{3,})/);
+    if (m) { const n = m[1].length; fenceLen = fenceLen === 0 ? n : (n >= fenceLen ? 0 : fenceLen); continue; }
+    if (fenceLen === 0 && /^#{1,6}\s/.test(line)) return true;
+  }
+  return false;
+}
+// Line-range based, not regex-based: a regex scan for the "first ``` ... last ```" span would
+// wrongly stop at the first NESTED closing fence instead of the real outer one (exactly the shape
+// a Markdown document's own "## Data Model" section legitimately needs — a fenced JSON example
+// nested inside the model's outer ```markdown wrap). Only the LAST non-blank line being a bare
+// fence-close, matched back to the first fence-open of the SAME backtick-run length, correctly
+// identifies the true outer boundary regardless of what's nested between them.
+function _unwrapWholeResponseFence(text) {
+  const lines = text.split('\n');
+  let end = lines.length;
+  while (end > 0 && lines[end - 1].trim() === '') end--;
+  if (end === 0) return null;
+  const closeMatch = lines[end - 1].match(/^(`{3,})\s*$/);
+  if (!closeMatch) return null;
+  const fenceLen = closeMatch[1].length;
+  let start = -1;
+  for (let i = 0; i < end - 1; i++) {
+    const openMatch = lines[i].match(/^(`{3,})\S*\s*$/);
+    if (openMatch && openMatch[1].length === fenceLen) { start = i; break; }
+  }
+  if (start === -1) return null;
+  return lines.slice(start + 1, end - 1).join('\n').trim() + '\n';
+}
+function extractMarkdownDocument(text) {
+  if (_hasUnfencedHeading(text)) return text;
+  const unwrapped = _unwrapWholeResponseFence(text);
+  if (unwrapped != null && _hasUnfencedHeading(unwrapped)) return unwrapped;
+  return text;
+}
+
 function validateSchema(value, schema) {
   if (schema.type === 'object') {
     if (!value || typeof value !== 'object' || Array.isArray(value)) throw new Error('Invalid structured object');

package/package.json

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

package/src/claude/scripts/tech-spec-assembler.js

@@ -148,7 +148,18 @@ function loadTechSpec(inputPath) {
   for (const c of components) {
     const compPath = path.join(inputPath, 'components', c.fileSlug)
     if (!fs.existsSync(compPath)) throw new AssemblyError(`component "${c.filePath}" has no detail file at ${compPath}`)
-    detailByPath[c.filePath] = parseComponentDetail(fs.readFileSync(compPath, 'utf8'))
+    try {
+      detailByPath[c.filePath] = parseComponentDetail(fs.readFileSync(compPath, 'utf8'))
+    } catch (err) {
+      // parseComponentDetail's own error names only the symptom ("missing its ## Change
+      // section"), never which file — a real diagnosability bug, found when exactly this error
+      // surfaced during final assembly with nothing identifying which of ~60 component files was
+      // actually malformed (the real culprit here was a whole-response-wrapped-in-a-fence worker
+      // reply — see lib/workflow-control.js's extractMarkdownDocument for the fix to that other
+      // half of this same incident). Re-thrown with the file identified, never silently swallowed.
+      if (err instanceof AssemblyError) throw new AssemblyError(`${err.message} (component "${c.filePath}" at ${compPath})`)
+      throw err
+    }
   }
 
   let doc = rewriteSection9(indexContent, components)