SQE Leaderboard/Laguna S 2.1
Laguna S 2.1
poolside/Laguna-S-2.1-INT4
SQE score
93
blended mean, 5 reps
Gate
5/5
all reps counted
Wilson 95% low
≥56.6%
lower confidence bound
Shots to green
1
median of 5 reps
Every published metric
Run configuration
- Endpoint model
- poolside/Laguna-S-2.1-INT4
- SWE-bench Pro
- 59.4% · SWE-bench Pro · Poolside (Laguna S 2.1)
- Reps
- 5
- Max shots
- 3
- Feedback tier
- 1
- Context cap
- 200K
- Token budget / run
- 4M
- Turn cap / shot
- 120
- Thinking budget
- 4.096K
- Sandbox digest
- quality-eval-sandbox@sha256:242ebd2f73c1c1ffa90c3ccb7913574f91e74a89dd1e4cf874f907a3129149c5
Review
Generated by claude-haiku-4-5Performance Review: fourline / poolside/Laguna-S-2.1-INT4
Overall Verdict
This INT4-quantized model successfully completed the Fourline task across all five repetitions with perfect gate compliance (5/5 pass) and no regressions. Typecheck, lint, and all 14 Playwright scenarios (including held-out tests for diagonal-win and draw detection) passed consistently. The model correctly implemented a pure-immutable Connect-Four game in TypeScript with proper domain separation (src/game/), full keyboard/UI controls, and conditional harness-API exposure (?test=1 only). Quality baseline is solid: 92–94% harness scores, single-shot repair (no flaky loops), zero trap-spec failures.
Context efficiency shows expected variance for this task. All five runs consumed their full token budgets (1.9–4.0M prompt tokens per rep, 67% average thrift), suggesting the task requires substantial iterative refinement; wall-clock times ranged 5–20 minutes, proportional to token burn. The model proactively ran typecheck and lint without prompting, indicating sound engineering discipline. Two minor tool-call errors (r1: 2 errors; r4: 5 errors; r2, r3, r5: 0–1 each) were transient and did not block progress or correctness.
Strengths
- Consistent correctness: 5/5 pass on gate; 100% scenario pass ratio (spread 0.083, meaning no flaky runs).
- Pure functional design: Domain logic properly separated under
src/game/; immutableGameSnapshot, readonly interface properties, recursive helpers instead oflet-based loops—fully compliant withfunctional/immutable-dataandno-letESLint rules. - Complete SPEC implementation: Board gravity (row 0 = bottom), 8×7 dimensions, 4-in-a-row win detection (all directions: horizontal, vertical, diagonal), rejection of out-of-range/full-column/post-game drops, draw detection (full board), playable interactive UI (visible board, cells with occupancy/player attributes, current-player and status indicators, column cursor, keyboard ArrowLeft/Right/Enter/Space/digits 1–8 + wrapping, optional click-to-drop).
- Harness API isolation:
window.__fourlinecorrectly exposed only inside?test=1URL branch; verified not leaking in normal mode. - Self-initiated verification: Model ran
pnpm typecheckandpnpm lintunprompted (observed in each run), catching and fixing errors autonomously.
Failure Modes
- Minor tool-call noise: r1 and r4 logged transient tool errors (r4: 5 errors over 96 turns = 5% rate). Logs show mostly "Unknown tool: read" (likely malformed params), not semantic failures. Did not corrupt state or require retries; final code was correct.
- Token thrift variance: Runs ranged from 0.327 (r2, r4, r5) to 0.676 (r1), suggesting inconsistent prompting or repeated file re-reads. r1 completed in 65 turns with high thrift; later runs needed 85–98 turns, each re-reading the full SPEC and earlier conversation. Typical for single-shot completion of moderate complexity; not a regression.
- No stalls or reasoning-only hangs: Conversion log from r1 shows one isolated "reasoning-only" nudge at turn 49, but the model recovered and finished at shot 1 with
stoppedAtGreen=true.
Serving & Harness Notes
- Single-shot reliability: All five reps achieved
shotsToGreen=1.0withrepairCurve="single-shot". Model generated working code on first attempt; no looping or retry spirals. - No token exhaustion: Maximum token consumption was 4.0M (r5), leaving 0.06M budgetLeft at the edge; well within typical task margins. Harmless; budget was sufficient for the task complexity.
- No context-burn or stalls observed: Conversation logs show clean forward progress. The one "finish rejected" event in r5 at turn 91/120 was a harness-level validation (not a model stall); model immediately resumed and completed successfully at turn 92 when prompted to continue.
- INT4 quantization transparent: Laguna-S-2.1-INT4 at ~4-bit weight precision executed without detectable quality loss. No instruction-following breakdowns, incorrect tool invocations, or logic errors attributable to low-bit weight degradation. Treat as full-precision for practical purposes.
Recommendation: Suitable for production inference on Connect-Four / board-game and general interactive TypeScript UI tasks. The consistent single-shot completion and proper SPEC adherence (including defensive rejection rules and hidden harness API) demonstrate solid reasoning and code-generation capability at this quantization level.