@dtlabs/ai-toolkit 0.16.6 → 0.16.8

package/CHANGELOG.md

@@ -1,4 +1,20 @@
 ## 0.1.4 (2026-07-21)
+## [0.16.8](https://github.com/dtlab-tech/ai-toolkit/compare/v0.16.7...v0.16.8) (2026-10-07)
+
+
+### Bug Fixes
+
+* **task-executor:** treat a zero-diff checkpoint as a valid no-op ([a587ee0](https://github.com/dtlab-tech/ai-toolkit/commit/a587ee0a88f24934235f64e9fbc9c395a76001fb))
+* **task-executor:** treat a zero-diff checkpoint as a valid no-op ([568e590](https://github.com/dtlab-tech/ai-toolkit/commit/568e590f8359c405561ef7e23ca626ddcecb9b12))
+
+## [0.16.7](https://github.com/dtlab-tech/ai-toolkit/compare/v0.16.6...v0.16.7) (2026-10-07)
+
+
+### Bug Fixes
+
+* **gaia-generate-work-breakdown:** require tracked placeholder for directory-only tasks ([63d2467](https://github.com/dtlab-tech/ai-toolkit/commit/63d246708508d199a25c9443a93c51c25bbfdf1b))
+* **gaia-generate-work-breakdown:** require tracked placeholder for directory-only tasks ([cd60691](https://github.com/dtlab-tech/ai-toolkit/commit/cd60691130a2c54fb40e6cee25da42a48cea68f0))
+
 ## [0.16.6](https://github.com/dtlab-tech/ai-toolkit/compare/v0.16.5...v0.16.6) (2026-10-06)
 
 

package/lib/task-executor/index.js

@@ -2119,6 +2119,30 @@ async function _runTaskToResolution(ctx) {
       continue;
     }
 
+    if (changedPaths.length === 0) {
+      // Verification and review both confirm the task's deliverable already
+      // matches its expected baseline — there is nothing for THIS attempt to
+      // stage or commit (a prior manual commit, an earlier attempt, or a
+      // prerequisite task already produced it). git.stageTaskFiles()
+      // deliberately refuses an empty changedPaths array ("must be a
+      // non-empty array — explicit enumeration, never a wildcard") — calling
+      // it here would throw STAGING_VALIDATION_ERROR uncaught by anything in
+      // this loop, crashing the whole execute() run instead of completing
+      // one task cleanly. Confirmed against a real run: a retried INFRA task
+      // whose deliverable had already been committed manually hit exactly
+      // this on its second attempt, after verification and review both
+      // legitimately passed. Mark the task 'skipped' instead of forcing it
+      // through a checkpoint pipeline that has nothing to stage — already a
+      // first-class terminal-success outcome (TASK_STATUSES; this loop's own
+      // allTerminalSuccess check above already includes it, and reconcile's
+      // _classifyTask already special-cases task.status === 'skipped' before
+      // ever looking at an attempt's stage).
+      state = store.readState(executionRoot, runId);
+      state = state.setTaskStatus(taskId, 'skipped');
+      store.writeState(executionRoot, runId, state);
+      return;
+    }
+
     // Checkpoint: stage first (US-05-TASK-BE-02) so its OWN write-tree
     // result becomes the checkpoint intent's expectedTreeSha, THEN persist
     // the intent (US-05-TASK-BE-01) with that now-known treeSha, THEN commit

package/package.json

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

package/src/claude/agents/gaia-generate-work-breakdown.md

@@ -318,6 +318,19 @@ For each task, supply one or more shell commands in `verification.commands` that
 - File existence: `test -f <path>`
 - Lint: `npx eslint <file>`
 
+**Directory-only tasks must never verify with `test -d` alone.** Git does not track empty
+directories — `test -d <path>` only confirms the directory exists in the *current* working tree,
+which is exactly what the agent that just created it will have. It tells you nothing about
+whether anything was actually committed: a fresh clone, or any downstream agent/review step that
+re-checks out the branch, will find the directory simply missing, even though this task's own
+verification reported success. If a task's sole outcome is creating one or more directories (no
+files):
+- Give it a `.gitkeep` (or equivalent) placeholder file in every leaf directory it creates, so
+  there is something for git to actually track.
+- Verify with a command that checks the directory is *tracked*, not just present on disk — e.g.
+  `git ls-files <path> | grep -q .` or `test -f <path>/.gitkeep` — instead of (or in addition to)
+  `test -d <path>`.
+
 ---
 
 ## Clarification Protocol