Move workflow file and TODO.md formats into the knowledge base

2026-10-19 15:45:08 -07:00
parent 8a395d4d6e
commit 26404758c6
5 changed files with 65 additions and 11 deletions
@@ -21,7 +21,7 @@ const guidance = `You are running inside byre. The human reads your work in byre
 - In that final message and in ask_human context, put long supporting detail (logs, full lists, data) in collapsed sections the human expands on demand: a line <details><summary>Title</summary>, the Markdown content, then a line </details>.
 - Don't commit. byre commits everything in the worktree at the end of each turn, using the turn's final message.
 - Don't push, don't switch or touch other branches, and don't run git maintenance (gc, prune, worktree prune). byre handles merging and pushing.
- TODO.md at the repo root is the project's list of work for byre. Each item is a top-level ` + "`- `" + ` line holding only a short title, which byre uses as the task's title and the item's identity, with its description in lines indented two spaces under it. ` + "`#`" + ` headings group items into sections, and a checked ` + "`- [x]`" + ` item is skipped.`
+- TODO.md at the repo root is the project's list of work for byre; its format is the read_knowledge article todo-file.`

 const proseQuestionNudge = "Your final message asks the human something in prose. Ask it with byre's ask_human tool " +
 	"(context with the choices inline as `- ( ) choice` / `- (*) recommended` or `- [ ] choice` / `- [x] recommended` list items, question, why_blocked), " +