feat(workflows): tier the standing reading for schema-bound stages

The anonymous script stages received the full standing-reading
instruction (project CLAUDE.md + git log -10 --format=full) although
a tree-footprint or text-extraction stage consumes none of it and a
verify stage needs only the build/test commands — re-executed on
every dispatch including tight repair rounds, at ~40k+ real tokens
per freshly-primed context.

Two slim variants in both workflow scripts: STANDING_FACTS
(verify-type stages — mini-verify, standard end-verify,
compiler-driven build/suite verify: project-facts build/test commands
only) and STANDING_NONE (tree/extraction stages — preflight,
plan-index, plan-extract[-all], snapshot: nothing beyond their own
instructions). Judgment roles (implementer, spec/quality reviewers,
tester/e2e, compiler-driven edit stage) keep the full read.
conventions.md § Standing reading and agent-template.md § Standing
reading list carry the tiering sentence; the precedent is the
narrowed per-role reading the named agents already practise
(tester -3, plan-recon/grounding-check -5, fieldtester -8,
docwriter --oneline).

closes #31

docs/agent-template.md

@@ -201,6 +201,12 @@ the per-role standing reading the project lists in its CLAUDE.md project
 facts. The agent's body says, prosaically: "Read everything in the
 standing reading list before doing anything else."
 
+The always list binds every *role* (agent file). The anonymous
+schema-bound stages inside `implement/workflows/*.js` are tiered
+below it (issue #31): verify-type stages read only the project-facts
+build/test commands, tree/extraction stages read nothing — see
+`conventions.md` § Standing reading.
+
 When the project's CLAUDE.md project facts name a glossary path, that
 glossary is implicitly part of the always list, so every role reads the
 project glossary without a per-role entry.

docs/conventions.md

@@ -122,6 +122,19 @@ project facts (`standing reading`). If the project declares a
 glossary, that file is implicitly standing reading for every role
 too.
 
+**Schema-bound workflow stages are tiered down** (issue #31). The
+anonymous script stages in `implement/workflows/*.js` have no agent
+file and author no code, and a freshly-primed context costs ~40k+ real
+tokens regardless of task size — so they do not take the full read:
+verify-type stages (mini-verify, the standard end-verify, the
+compiler-driven build/suite verify) read only the project-facts
+build/test commands; tree/extraction stages (preflight, plan-index,
+plan-extract[-all], snapshot) read nothing beyond their own
+instructions. This extends the narrowed per-role standing reading the
+named agents already practise (`tester` reads `git log -3`,
+`plan-recon`/`grounding-check` `-5`, `fieldtester` `-8`, `docwriter`
+`--oneline`); judgment roles keep the full convention.
+
 ## Git discipline
 
 - **Only the orchestrator commits.** No skill agent runs `git commit`.