[anandhu-eng]

Fixes #162

The checker read the §4.4 steady_state block from point.yaml, but nothing writes it there. The client writes its verdict to result_summary.json, so submitters copied it by hand, and some copies were wrong (for example, an off-by-one super-pass count).

Changes:

• steady-state-basis reads steady_state from result_summary.json and works out the §4.4 status and verdict from the client's fields.
• A missing field (old client), null (detection off) and an unreadable block each get their own warning.
• Agentic points and a dedicated Offline run are skipped. §4.4 covers fixed-concurrency points only, and the client does not run detection for agentic.
• §6.2 uses the window duration only when the client accepted the window.
• steady-state-valid and steady-state-consistency are removed. They only checked the hand-written block. A steady_state block left in point.yaml is ignored.
• The fixture tool moves the corpus verdict into result_summary.json (101 points regenerated, --check clean).

Mapping from the client's block:

§4.4	From the client
window	sp_lo .. sp_hi - 1 (sp_hi is exclusive); duration = end_ns - start_ns
partial_dataset	fewer than 1 super-pass after warmup
insufficient_passes	no window, or a window under 4 super-passes
insufficient_duration	found: false with a 4+ pass window (client rejected it as short), or a window under the §6.2 minimum
windowable	otherwise
verdict	not found if found is false, else anomaly, else drifting_up / drifting_down from global_trend, else STEADY STATE

Severities do not change: everything here is still a warning or info.

Open questions for the rules (not changed here):

• §8.3 still lists steady_state as a point.yaml field.
• §4.4 names the gating metrics as TPOT P50/P90 in one place and TTFT and TPOT P50/P90 in another. This PR treats drift in any of the four as a drift verdict, which is a warning.

🤖 Generated with Claude Code