Seam from the state-class strip: renderGraphContext tags nodes with raw latest-quiz outcomes ([miss] / [dont-know] / [correct] / [never probed]); 50-graph-context.md still taught the deleted state classes ([missed] / [known] / [candidate]). Re-aligned, guidance unchanged.
Prompt fragments
The teacher's system prompt is composed at agent creation:
src/agent/system-prompt.md— the base (owned by the orchestrator; do not edit from a worker).- Every numeric-prefix
*.mdfragment in this directory, in sorted filename order, joined with---separators. The loader enforces the numeric prefix (\d*-*.md) — other files (like this README) never enter the model's prompt.
Rules for adding a fragment:
- Name it with a numeric order prefix:
10-plan-tree.md,20-jobs.md,30-phases.md. - One fragment per workstream — your brief tells you which filename you own.
- Document YOUR tools/behaviors exactly; reference tool input field names verbatim (they must match the zod schemas).
- Keep it tight: fragments are always in context. No restating the base prompt.