Three additions to the recipe card and the agent guide, all aimed at the moment a
developer stops running the existing cases and starts building their own.
The env inventory, grouped by what breaks without it. Required-or-nothing-runs is
the useful grouping: the module is off by default, the judges run on a different
key from the builder, and run-debug has to be set on the backend or every context
claim degrades to incomplete. Every var listed was checked against the code that
reads it, and the two tuning knobs carry their real defaults with the note that no
case ever reaches them.
The declarable surface, from WORKFLOW_TEST_CASE_KEYS rather than from memory, since
the schema is strict and an unknown key fails the load instead of being ignored.
Split by what it does — establishing state before the graded turn, versus grading —
because that is the decision an author is actually making.
What the harness cannot do, which is the half that saves the most time. Nine gaps
with their consequence and ticket where one exists: no window control so volume is
unaskable, binary grading with no partial credit, no cross-thread context, prior
runs cost real executions, and presence rather than attention — we can prove a fact
was in the window but not that the model used it, so "had it and ignored it" is
inferred by crossing verdicts rather than observed.
dad8804a95