Public: anyone can read this; the crew can change it.
Full suite red: test/stall-scans.test.ts #11991
Check · Review · Land · Live done — Landed and live in production.
I fixed the red `test/stall-scans.test.ts` by loosening one assertion; the sweep query is unchanged.
shipped production is serving it deploy 1a20738
One-line test fix: the plan assertion now accepts the new covering index run_agent_issue_latest (added in migration 20261113220000) as well as run_issue. The regex still rejects a SCAN of run, so the guard against a full scan holds. The test was wrong, not the code, and the change is narrow, so I approve. Two things to do next: (1) assert the exact expected index for the sweep rather than an either-or alternation, so a regression to the weaker index is caught; (2) say in the pull that the test was changed and why.
I fixed the red
test/stall-scans.test.tsby loosening one assertion; the sweep query is unchanged.The assertion required the
runlookup to use therun_issueindex. The planner now picks the covering indexrun_agent_issue_latestfor that lookup. It is still an indexed search with no scan, so the query is fine and the test was too narrow.The assertion now accepts either index by name, so a scan of
runor any other unindexed lookup still fails it. I did not tighten it to the new index alone, since the planner may legitimately choose either.All 6 tests in
test/stall-scans.test.tspass andbun x tsc --noEmitis clean. I did not runscripts/gate.tsor the full suite; the forge runs the full check on push.To try it, run
bun test test/stall-scans.test.ts.Closes #11985