@deftai/directive-content 0.66.0 → 0.66.1

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@deftai/directive-content",
-  "version": "0.66.0",
+  "version": "0.66.1",
   "description": "Shippable Directive framework content in the consumer .deft/core/ layout (C1 flatten), plus the engine surfaces (.githooks/, Taskfile.yml, tasks/) the deposit wires. Python-free per #2022 Phase 3. Refs #11, #1669, #1967.",
   "type": "module",
   "files": [

package/tasks/engine.yml

@@ -19,17 +19,19 @@ tasks:
     # `D:\a\directive\directive\D:\a\directive\directive`, #2126). Reference the
     # build root by absolute path so the guard stays cwd-independent.
     #
-    # Guard on SOURCE presence (packages/cli/package.json), NOT the dist/
-    # artifact: dist/ is gitignored, so a cold framework checkout (e.g. CI after
-    # a bare `pnpm install`) has source but no dist and MUST still build. A
-    # consumer deposit (`.deft/core` = @deftai/directive-content) ships no
-    # packages/ tree, so the guard is false and the build is a clean no-op --
-    # this is the #2126 fix (avoids `pnpm run build` -> Missing script: build).
+    # Guard on buildability, not source presence alone (#2142): a cold framework
+    # checkout has packages/cli/package.json AND a root `build` script, so it
+    # still builds when dist/ is gitignored/absent. A clean npm consumer deposit
+    # ships no packages/ tree (guard false -> no-op, #2126). Git-vendored-payload
+    # repos may carry a stray packages/ under .deft/core without a root `build`
+    # script — source-only presence must NOT run `pnpm run build` there.
     dir: '{{.USER_WORKING_DIR}}'
     cmds:
       - |
         set -eu
-        if [ -f "{{.DEFT_ROOT}}/packages/cli/package.json" ]; then
+        if [ -f "{{.DEFT_ROOT}}/packages/cli/package.json" ] \
+           && [ -f "{{.DEFT_ROOT}}/package.json" ] \
+           && node -e "const fs=require('fs');const j=JSON.parse(fs.readFileSync(process.argv[1],'utf8'));process.exit(j.scripts&&j.scripts.build?0:1)" "{{.DEFT_ROOT}}/package.json"; then
           pnpm --dir "{{.DEFT_ROOT}}" run build
         fi
 

package/templates/agent-prompt-preamble.md

@@ -233,19 +233,22 @@ task scm:body:pr:edit -- --repo OWNER/REPO --pr 42 --body-file "$bodyFile"
 
 The wrapper reads UTF-8 body text from a file or stdin, sends JSON to `gh api --input -` via `_safe_subprocess.run_text` with `shell=False`, and prints the live post-mutation read-back object. Use live `gh` for immediate verification after mutations; do not use `ghx` for the first read-back because it may serve a cached stale GET.
 
-## 5.6 Umbrella status — claim-cites-state-surface (#2066)
+## 5.6 Issue reading — body then comments (#2143 / #2066)
 
-Before stating an umbrella or epic's current status (what is done, what blocks, wave order), satisfy the claim-cites-state-surface rule:
+Before ingesting a GitHub issue, building a worker dispatch envelope, or concluding what an issue actually asks for, satisfy the body→comments reading discipline for **any** issue (not only umbrellas):
 
-1. ! Fetch issue comments via REST: `gh api repos/<owner>/<repo>/issues/<N>/comments` (or `ghx api ...` for cached read-only GET).
-2. ! Read the `## Current shape (as of pass-N)` comment and any linked context or `LockedDecisions` xBRIEF referenced there. Follow the AGENTS.md #1152 reading order: body -> current-shape comment -> amendment comments.
-3. ! Any "X is done" / "X is the blocker" assertion about an umbrella MUST cite the current-shape comment or another state artifact in the same message.
+1. ! Fetch the issue via REST: `gh api repos/<owner>/<repo>/issues/<N>` (or `ghx api ...` for cached read-only GET).
+2. ! Fetch the comment thread via REST: `gh api repos/<owner>/<repo>/issues/<N>/comments` (or `ghx api ...` for cached read-only GET). The issue-ingest path fetches `/comments` by default and folds the thread into the ingested overview (#2143).
+3. ! Read body first, then the comment thread in chronological order. Later maintainer comments may supersede the original body — the #2126 recurrence shipped the wrong fix because dispatch used a body-only fetch.
+4. ! Any scope, fix, or status conclusion about the issue MUST reflect the full thread, not the body alone.
 
-Anti-pattern: reading only the issue body (pass-1 plan, stale by design) and concluding umbrella status from it — e.g. `gh issue view <N> --json body` or REST `repos/.../issues/<N>` body field alone. The live recurrence on 2026-06-28 misread #2013 Wave 0 status this way despite #1152 being loaded.
+**Umbrellas and epics (#1152):** when the issue is an umbrella or epic, the reading order extends to body → `## Current shape (as of pass-N)` comment → amendment comments. Prefer `task umbrella:current-shape <N>` for the deterministic current-shape read path.
 
-⊗ Conclude umbrella or epic status from the issue body alone (#2066).
+Anti-pattern: reading only the issue body and building a dispatch envelope from it — e.g. `gh issue view <N> --json body` or REST `repos/.../issues/<N>` body field alone when `comments` count is greater than zero.
 
-Reference: AGENTS.md `## Umbrella current-shape convention (#1152)`, issue #2066.
+⊗ Conclude what an issue asks for, or build a dispatch envelope, from the issue body alone when the issue has comments (#2143 / #2066).
+
+Reference: AGENTS.md `## Issue body→comments reading (#2143)`, `## Umbrella current-shape convention (#1152)`, issue #2143.
 
 ## 6. No Draft re-toggling within a single review cycle
 

package/templates/agents-entry.md

@@ -96,6 +96,16 @@ Umbrella and epic issues carry a pass-1 body (plan, stale by design) and a canon
 
 Cross-references: `.deft/core/.agents/skills/deft-directive-refinement/SKILL.md` and `.deft/core/.agents/skills/deft-directive-triage/SKILL.md` (before reporting umbrella status). Refs #1152, #2066.
 
+## Issue body→comments reading (#2143)
+
+When ingesting or dispatching against **any** GitHub issue (not only umbrellas), later maintainer comments may supersede the original body — the #2126 recurrence shipped the wrong fix from a body-only fetch.
+
+- ! Fetch both the issue body and `repos/<owner>/<repo>/issues/<N>/comments` via REST before concluding what the issue asks for or building a worker dispatch envelope. Read body first, then the comment thread in chronological order.
+- ! `deft issue:ingest` / `task issue:ingest` fetches `/comments` by default and folds the thread into the ingested overview (#2143).
+- ⊗ Build a dispatch envelope from the issue body alone when the issue has comments.
+
+Cross-references: `.deft/core/content/templates/agent-prompt-preamble.md` § 5.6. Refs #2143, #1152, #2066, #2126.
+
 ## Content packs
 
 Deft ships versioned content packs (e.g. lessons learned from prior work) under `.deft/core/packs/`. Discover and LOAD pack content via the slice surface instead of reading whole pack files into context: