Repository navigation
Application diff regression: CRM#5 and MIS_TALENT#7 lost established rows after 2026-10-05 (likely #963) #1001
Description
Regression: two of three Q2 cases lost established rows on main
The frozen development corpus (benchmark/application-q2/) shows two Q2 cases from the 2026-10-05 ledger losing their established rows on current main. Only attest#3 still reads as before, so Q2 on the development corpus falls from 3/49 to at most 1/49.
| Case | 2026-10-05 (0e58e6ff) |
main since 2026-10-06 |
|---|---|---|
| kkmiecik-coder/CRM#5 | 4 established rows on Wycena (wyslij_obraz added; policz_wycene, policz_wysylke, znajdz_klienta changed) |
0 established rows |
| Tiendat2703/MIS_TALENT#7 | 3 rows (Finance_Agent.load_and_validate, Finance_Agent_Preflight.load_and_validate, Finance_Agent_Preflight.load_service_catalog) |
2 rows: the Finance_Agent row is gone |
| jpka/attest#3 | 2 added rows | unchanged |
Saved runs (~/.cache/shipgate-q2/out-*, same pins and runner) narrow the change to the window between the 0e58e6ff run (2026-10-05 11:02) and the first run on main 7c160cfb (2026-10-06 22:46). The merges in that window were #960 (control), #962 (OpenShell links), #961 (benchmark ledger), #966 (dependencies) and #963 (follow caller-supplied agent lists, #874 increment 1). Only #963 changes the SDK/ADK readers, so it is the likely cause; this needs confirming by running both commits.
Both answers stay partial, so this is a lost row, not a false complete answer. But these are the cases #868's exit is counted on.
Acceptance
- Identify the introducing change by running the two pinned PRs on
0e58e6ffand7c160cfb(and the commit before feat(readers): follow caller-supplied agent lists #963). - Restore the CRM#5 and MIS_TALENT#7 rows the 2026-10-05 ledger scored, without dropping feat(readers): follow caller-supplied agent lists #963's own gains, and pin both shapes in a regression test.
- Re-run the 49-PR corpus: no established row present on
0e58e6ffmay be missing without a per-row justification.
Activity