@haposoft/cafekit 0.13.2 → 0.13.3

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@haposoft/cafekit",
-  "version": "0.13.2",
+  "version": "0.13.3",
   "description": "Claude Code-first spec-driven workflow for AI coding assistants. Bundles CafeKit hapo: skills, runtime hooks, agents, and installer scaffolding.",
   "author": "Haposoft <nghialt@haposoft.com>",
   "license": "MIT",

package/src/claude/scripts/validate-spec-output.cjs

@@ -132,6 +132,28 @@ function validateTaskSections(taskPath, content, errors) {
   }
 }
 
+/**
+ * Task files are created from the scaffold template (the scaffold-guard hook
+ * forces creation through it), so every task starts as a stub full of `{{...}}`
+ * placeholders. The hook guarantees the stub is CREATED via scaffold, but
+ * nothing guaranteed the model FILLED it. An unfilled `{{...}}` is an
+ * incomplete task — SKILL.md: "Leave NO {{...}} placeholder ... fails DoCT" —
+ * so it is a hard error here. A `.../` path fragment is a not-yet-resolved path
+ * placeholder; it is only a warning, because it usually survives in prose Steps
+ * while the Related Files table (which spec-ground.cjs does verify) is already
+ * concrete. Matching `\.\.\.\/` (three dots + slash) avoids flagging a relative
+ * `../` path or a prose ellipsis.
+ */
+function validateTaskPlaceholders(taskPath, content, errors, warnings) {
+  const stub = content.match(/\{\{[^}\n]+\}\}/);
+  if (stub) {
+    errors.push(`${taskPath}: unfilled scaffold placeholder ${stub[0]} — task stub was not completed`);
+  }
+  if (/\.\.\.\//.test(content)) {
+    warnings.push(`${taskPath}: contains a '.../' path placeholder — replace with a concrete path`);
+  }
+}
+
 /**
  * Each phase completion must carry its own timestamp. Reusing `timestamps.init`
  * for a later phase is forbidden (SKILL.md spec.json Update Rules). This used to
@@ -344,6 +366,7 @@ function validateSpec(specDir) {
     const fullPath = path.join(specDir, taskFile);
     const content = fs.readFileSync(fullPath, 'utf8');
     validateTaskSections(taskFile, content, errors);
+    validateTaskPlaceholders(taskFile, content, errors, warnings);
 
     const idRe = /\b((?:REQ-\d+)|(?:R\d+))\b/gi;
     let match;

package/src/claude/skills/specs/SKILL.md

@@ -335,7 +335,7 @@ Rules:
 - Load `references/ask-user-question-gates.md`; if scoring reveals unapproved scope expansion or an unresolved user-owned choice, pause before writing task files.
 - **Scaffold is mandatory — raw `Write` to a task file is blocked.** A PreToolUse hook (`task-scaffold-guard.cjs`) rejects any `Write` whose path matches `specs/<feature>/tasks/task-*.md`. The only path to a task file is scaffold → Edit. Once the task list is decided, generate the stubs:
   `node .claude/scripts/spec-scaffold.cjs <feature> --tasks "R0-01-slug,R1-01-slug,..." --tasks-only`
-  This creates each `tasks/task-R*.md` from `templates/task.md` and merges `task_files` + `task_registry` into the existing `spec.json` (pending, no overwrite of already-filled tasks). Then **Edit-fill** the `{{...}}` placeholders in each stub (`Edit`/`MultiEdit` are allowed; `Write` is not). Hand-writing whole task files is the single biggest output-token cost — scaffold + fill cuts it. (The guard fails open if the scaffold script is absent, and can be disabled via `"spec": { "scaffold_guard": false }` in `.claude/runtime.json`.)
+  This creates each `tasks/task-R*.md` from `templates/task.md` and merges `task_files` + `task_registry` into the existing `spec.json` (pending, no overwrite of already-filled tasks). Then **Edit-fill** the `{{...}}` placeholders in each stub (`Edit`/`MultiEdit` are allowed; `Write` is not). (The guard fails open if the scaffold script is absent, and can be disabled via `"spec": { "scaffold_guard": false }` in `.claude/runtime.json`.)
 - Each task file follows template `templates/task.md` (scaffold already applies it). **Leave NO `{{...}}` placeholder unfilled** — a stub with placeholders is an incomplete task.
 - `Related Files` and test plans must inherit paths, contracts, and test targets from the codebase scout. If exact files/tests cannot be named for an enhancement, run targeted inspect before generating tasks. Every `Related Files` path will be grounded (Layer 2) at Step 8.5 — phantom paths hard-fail, so cite real paths.
 - Each task file MUST include `Completion Criteria` and `Evidence` sections detailed enough that a downstream quality gate can prove the task is truly done. Existing specs may use `Task Test Plan & Verification Evidence` or legacy `Verification & Evidence`.