Pin Behaviors Across Model Swaps

<p>A patch touches zero test files. No assertion changes, no new skips, no fixture edits. The suite goes green on the first run.</p> <p>Then someone opens the job duration graph

<!-- SC_OFF --><div class="md"><p>Projects are <a href="https://github.com/snap-research/locomo/issues/31">still submitting new scores on LoCoMo as of March 2026.</a> but the

<p>The pull request looked finished. Twenty-three files. Tests green. A free coding model had been left on the ticket overnight. Then a reviewer opened

<h2> The retry trap </h2> <p>A free model CI job fails on a timeout.</p> <p>You click retry.</p> <p>The whole pipeline starts over: checkout, build, dependencies, model call.</p>

<!-- SC_OFF --><div class="md"><p><strong>Submitted by:</strong> Adam Kruger <strong>Date:</strong> March 23, 2026 <strong>Models Solved:</strong> 3/3 (M1, M2, M3) + Warmup</p>

<p>Anthropic shipped Opus 4.7 on April 16, 2026. Same $5/$25 pricing as 4.6. Same 1M context. Same 128K output ceiling. Different model entirely when you put it in an agentic

<p>At 02:40 the triage queue stopped draining. The worker process was healthy. The Redis length grew. The HTTP client saw 200 OK. The JSON decoder returned objects. But the bucket

<h1> Draft Freely, Publish Narrowly: A Page Ownership Gate for Model-Written Docs </h1> <p>Documentation pipelines rarely fail because the model writes badly; they fail because