feat(worker): render task descriptions into the list-handler brief
Phase 0 forced a batch_get_tasks full-fetch across every task just to see descriptions, which blew past the client's token limit on larger lists. brief.md lives on disk and has no such limit, so descriptions now render there directly (fenced with an extended backtick run, indented under the list bullet, so embedded headings/lists/code fences can't break the task list's own structure). Phase 0 now treats the brief as the primary source and only falls back to batch_get_tasks for fields it doesn't carry.
This commit is contained in:
@@ -236,7 +236,7 @@ public static class PromptFiles
|
||||
Work the five phases in order. Do not start a phase before the previous one is finished.
|
||||
|
||||
## Phase 0 — Read everything
|
||||
Call batch_get_tasks with every id from the brief and read each task's title, description, status and parent/child links. Do not act on any single task before you have read them all — Phase 1 needs the whole set in view.
|
||||
The brief is the primary source: it already lists every task's title, id, status and full description. Read it in full before acting. Only call batch_get_tasks if you need something the brief does not carry for a specific task, e.g. parent/child links. Do not act on any single task before you have read them all — Phase 1 needs the whole set in view.
|
||||
|
||||
## Phase 1 — Dedupe
|
||||
Compare the tasks pairwise for overlap: same goal stated twice, one task fully contained in another, two tasks that would edit the same thing for the same reason.
|
||||
|
||||
Reference in New Issue
Block a user