Repository navigation
v1.91.150.0 test(evals): re-pin older paid models to the current generation; prosons and cookie-judge repairs (GSTA-49 TM3) - #3293
Conversation
…s Fable (GSTA-49 TM1) Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
Repair the prosons capture prompt that tripped the reasoning_extraction classifier, and restructure /setup-browser-cookies so the Aside probe, decisions and target order are unambiguous. Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com> # Conflicts: # TODOS.md # scripts/harness-version.json
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
|
😎 This pull request was merged. |
E2E Evals: ✅ PASS29 executed, 0 reused rule/judge records | 0 manual accepted (unscored; no score-cache credit) | $3.06 rule/judge cost | reconcile exit: 0 Profile: pr / mode Rule and judge shards
Fail-closed reconciliationSliced lane: planner → duration-packed executors → fail-closed report. Behavior cases run a pre-registered 3-trial panel (PASS at 2/3 with no contract violation); a PASS 2/3 is shown with its failed trial, never as a clean pass. Reused results retain their original provenance and expiry. |
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com> # Conflicts: # CHANGELOG.md
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com> # Conflicts: # CHANGELOG.md
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com> # Conflicts: # CHANGELOG.md
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
|
flaky: test/gstack-doctor.test.ts (the CSO row reads the build-result record, windows-free-shard (1)), failed in 39304879908 attempt 1, passed on rerun 39304879908 attempt 2, logged for the daily flaky-fix pass |
Lane TM3 of GSTA-49. It moves every paid case still pinned to an older frontier model onto the current generation. Garry's direction, 2026-10-18: "We don't have to test the older frontier models."
Re-pinned cases
Pins to
claude-opus-4-7now follow the capture model,resolveEvalModel('capture')(Opus 5.5 since #3275). These cases test skills, not a particular model, so they track the capture model:The tests that mirror these pins are updated.
Fixed per-model references keep a literal id, moved to the new generation:
claude-opus-5-5claude-sonnet-5-5claude-sonnet-5-5gpt-6.1-solThe cookie judge's manual-review JSON is unchanged. It records Garry's approval of Fable refusals.
Fresh baselines. Each re-pinned case ran once on its new model as a fresh measured reference. Thresholds, assertions, trial counts and case kinds are unchanged.
Repairs from that run (GStack Minder, 2026-10-18)
plan-review-prosons-hardstop-neg. The provider refused the capture-writing turn (
stop_reason: refusal, categoryreasoning_extraction). The refusal was triggered by the capture instruction's "verbatim … Do NOT paraphrase. This is a format-capture test" wording. In replays of the exact request, the old wording was refused 7 times in 16 and the reworded instruction 0 times in 24. The shared capture helper now asks for "the text of the single AskUserQuestion you would have made". The plan content, assertions and trials are unchanged. All four prosons cases then passed 3/3.Cookie workflow judge on sonnet-5-5. The judge scored the /setup-browser-cookies workflow below threshold for real text defects:
The template is restructured: probe, then decisions first, then prepare, import and report. Both hosts are regenerated. The judge passes 4/4/4 with the thresholds unchanged.
Results on the new models
18 of 20 re-pinned cases passed on the first run. The two reds were repaired as above and pass. Recorded paid spend for the lane is about $13.5.
Gate-integrity edits
Checks