@pmelab/gtd 11.0.0 → 12.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.
- package/README.md +9 -0
- package/dist/gtd.bundle.mjs +123 -88
- package/package.json +2 -3
package/README.md
CHANGED
|
@@ -319,6 +319,15 @@ noted in steps 2, 3, and 4 below.
|
|
|
319
319
|
every one of these correctly: it shows you the message and stops, same as any
|
|
320
320
|
other question.
|
|
321
321
|
|
|
322
|
+
A red suite that keeps failing past a few fix attempts escalates instead of
|
|
323
|
+
retrying forever: an agent turn reads the failing output and writes
|
|
324
|
+
`.gtd/ESCALATION.md` — what's failing, why the earlier attempts didn't fix
|
|
325
|
+
it, and what to try next — and the process stops for you to edit or land
|
|
326
|
+
as-is, handing that document to the next fix turn as its instruction. Two
|
|
327
|
+
such rounds with no fix is the terminal stop: the last analysis stays on disk
|
|
328
|
+
instead of a third being written, and editing it is what gets the next
|
|
329
|
+
attempt anywhere new.
|
|
330
|
+
|
|
322
331
|
4. **You review.** You get a review document listing what changed and what to
|
|
323
332
|
look at. Tick the boxes to approve, or write what is wrong. Approving ends
|
|
324
333
|
the process; feedback sends it back to step 2 for a fresh plan — it never
|