@pmelab/gtd 14.1.0 → 15.1.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@pmelab/gtd",
-  "version": "14.1.0",
+  "version": "15.1.0",
   "private": false,
   "description": "Git-aware CLI that emits the next prompt for an autonomous coding agent based on the current repository state",
   "bin": {

package/src/workflows/prose.ts

@@ -180,10 +180,11 @@ export const fixFeedbackPrompt = `- The only state file this turn writes is \`.g
 
 export const footnoteRules = `- Leave a footnote anywhere: mark the exact spot with \`[^name]\` (any
   name, no whitespace or \`]\`), then define it below as \`[^name]:
-  explain what you mean\` — indent a longer comment's continuation
-  lines. (The literal words "your comment" are this format's seeded
-  placeholder body — a definition still holding them exactly is
-  flagged as unfilled, so write your own words there)
+  explain what you mean\` — indent continuation lines by 4 spaces or
+  more. (A newly seeded definition starts with an empty body — a
+  definition whose body is still empty or whitespace-only is flagged
+  as unfilled, so write your own words there; words left under-indented
+  are flagged separately, naming the indent as the fix)
 - A footnote is a comment on that exact spot — the hunk, line, or
   paragraph it marks — never a whole-file remark
 - \`name\` is yours to pick; only a definition's name must be unique in

package/src/workflows/text.ts

@@ -621,17 +621,19 @@ review the changes:
 - At least one \`## <Chunk Title>\` heading grouping hunks
   semantically (same feature/refactor/fix, across files), each
   with a short explanation of what changed and why, then one
-  pointer per hunk (\`./\`-relative path, optional \`#line\`;
-  checkboxes are for the human, not you). Put the note's
-  opening line right on the pointer's line:
+  pointer per hunk (\`./\`-relative path, mandatory \`#start-end\`;
+  checkboxes are for the human, not you). A pointer into a NEW file
+  gets a range covering only the region the note is about — never
+  the whole file. Put the note's opening line right on the
+  pointer's line:
 
-      - [ ] ./path/to/file.ts#42 — what this hunk does
+      - [ ] ./path/to/file.ts#42-70 — what this hunk does
 
   Continue a longer note below the pointer, indented exactly two spaces
   — never four or more, which reads as a code block and never
   reflows:
 
-      - [ ] ./path/to/file.ts#42 — what this hunk does
+      - [ ] ./path/to/file.ts#42-70 — what this hunk does
         and here is more detail, continued below it
 
   A note sitting entirely on the line(s) beneath the pointer is