@pmelab/gtd 15.0.0 → 15.1.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (4) hide show
  1. package/README.md +6 -5
  2. package/dist/gtd.bundle.mjs +142 -63
  3. package/package.json +1 -1
  4. package/src/workflows/prose.ts +5 -4
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@pmelab/gtd",
3
- "version": "15.0.0",
3
+ "version": "15.1.0",
4
4
  "private": false,
5
5
  "description": "Git-aware CLI that emits the next prompt for an autonomous coding agent based on the current repository state",
6
6
  "bin": {
package/src/workflows/prose.ts CHANGED
@@ -180,10 +180,11 @@ export const fixFeedbackPrompt = `- The only state file this turn writes is \`.g
180
180
 
181
181
  export const footnoteRules = `- Leave a footnote anywhere: mark the exact spot with \`[^name]\` (any
182
182
  name, no whitespace or \`]\`), then define it below as \`[^name]:
183
- explain what you mean\` — indent a longer comment's continuation
184
- lines. (The literal words "your comment" are this format's seeded
185
- placeholder body — a definition still holding them exactly is
186
- flagged as unfilled, so write your own words there)
183
+ explain what you mean\` — indent continuation lines by 4 spaces or
184
+ more. (A newly seeded definition starts with an empty body — a
185
+ definition whose body is still empty or whitespace-only is flagged
186
+ as unfilled, so write your own words there; words left under-indented
187
+ are flagged separately, naming the indent as the fix)
187
188
  - A footnote is a comment on that exact spot — the hunk, line, or
188
189
  paragraph it marks — never a whole-file remark
189
190
  - \`name\` is yours to pick; only a definition's name must be unique in