mirror of
https://github.com/garrytan/gstack.git
synced 2026-11-01 14:34:42 +01:00
garrytanandcapy-ai[bot]
229e874e0f
The perf-collection judge (run 40558235014, both attempts, six samples) named the same contradictions: Phase 3 offered an optional 3-run median while the mandatory vet section demands 5 alternating runs per side and a stored baseline cannot be interleaved; the budget example read '4/6 passing' against a rule that counts WARNING as below budget; the trend table showed Grade and Bundle columns no stored file defined; Phase 9 named two files with no contents. Phase 3 now runs 5 per page with median and range and names --quick as the one-run ballpark; the baseline schema carries runs and range_ms; Phase 5 says how the seven questions apply against a stored baseline (compare the delta with both spreads, name the limiter from Phase 6, inconclusive when either side is one run); the grade example counts 3 PASS, 1 WARNING, 2 FAIL; Phase 8 reads the benchmark and baseline JSON files by timestamp; Phase 9 defines the JSON as the Phase 4 object plus grade, verdict and per-metric status. Nearby prose tightened so the skeleton stays under its 31,300-byte cap (31,290). Judge after the repair: clarity, completeness and actionability 4/4/4 on all three samples, twice. Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>