| 2026-10-26 / quality |
Output integrity |
Frozen router source a5ccb7454ad49f47e5a953b130696fff69cdb829 collapses repeated spaces in buffered text, including indentation. Original HTTP bodies for historical Aider runs were not retained, so historical attribution remains unknown. |
PR #704 merged at 6b4d7dcd5078f06b1a0c992c67f0d03dd022c9d7; exact-merge CI passed. A separate fixed-router capture preserved returned code byte-for-byte; repaired verifier and offline exercises passed 16/16. The restored router uses the reviewed overlay. |
Fix present in restored router runtime; historical Aider attribution unresolved. |
| 2026-10-26 / quality |
Output budget |
Ignis Go 16K repair resolved the task. The true 32K follow-up used a declared 32,768-token cap; both responses ended with finish_reason=length. An earlier incorrectly clamped 32K attempt remains separate historical-invalid evidence. |
Preserve distinct run IDs and keep outside the six-task Aider result. |
Closed bounded diagnostic; task unresolved at true 32K. |
| 2026-10-26 / quality |
Step budget |
Flare SWE attempted five tasks; four empty patches hit LimitsExceeded at the declared, frozen 60-step ceiling. Django was the only nonempty graded submission and remained unresolved. |
Keep all five attempts in the denominator; no 90-step follow-up in this campaign. |
Closed for this campaign; qualification gate incomplete. |
| 2026-10-26 / scout |
Setup friction |
Flare C1 root launch failed before execution; r1 lacked an output directory; r2 failed the renamed-cell/path guard before activation. Corrected r3 returned eight HTTP responses and had 0/8 performance-eligible. |
Reconciliation preserves the native native_control_mismatch wrapper and all eight native output failures. |
Setup closed; strict output gate failed. |
| 2026-10-26 / scout |
Serving output |
vLLM and Flare C1 each received eight responses and had 0/8 eligible; Flare had five no-visible-content length stops and three strict 128-word misses. |
Preserve native artifacts; C4/C8 were not run. No retry or performance claim. |
Both C1 output gates failed; no performance qualification. |
| 2026-10-26 / restoration |
Configuration |
Temporary evaluation routes/output caps were changed. Final restoration returned exact prior configuration revision aadcc9ffd338c32ff44a52d45db1fbe276aeb0e6aaa643da64ad58f21d284225 and GLM incumbent at admitting generation 38. |
Direct and routed five-check preflights and one Pi real read-tool turn passed. |
Verified locally; no whole-fleet, reboot, or fresh-host claim. |
| 2026-10-26 / restoration |
Router runtime recovery |
An image attempt failed at the Python 3.11 WAL runtime guard. Recovery used the reviewed incumbent-runtime overlay with PR #704 splitter (image ID suffix DE213); this is not the original router image. |
Exact router configuration was restored and generation 38 is admitting. The exact-predecessor rollback capability is tracked separately in PR #705; the canonical image/Python 3.11 native-WAL failure is tracked in the product ticket .tickets/2026-10-26-router-python311-native-wal-image-compatibility.md. |
Router restored with explicit image difference; rollback capability tracked separately in PR #705. |
| 2026-10-26 / restoration |
Pi input |
First Pi acceptance attempt contained contaminated stdin and was not accepted. The clean r2 real read-tool turn returned the exact answer and passed. |
Preserve the contaminated first attempt privately; only publish the successful bounded outcome. |
One local Pi turn passed; not whole-client acceptance. |
| 2026-10-26 / diagnostic |
Post-stop trace |
Earlier marker trace had a worker-only token after the native API stop; retained API completion did not include it. The analyzer correctly remained unknown; no general runtime defect was proven. |
See marker trace finding and private offline packet assertion. |
No engine fix or upstream patch claimed; a stop-aware scheduler reconciliation test remains future work. |