Skip to content

Fix GC toast fallback corridor when Exit Battle is missing (v0.3.6) - #52

Merged
sbrants merged 2 commits into
mainfrom
fix/gc-toast-default-corridor
Aug 10, 2026
Merged

Fix GC toast fallback corridor when Exit Battle is missing (v0.3.6)#52
sbrants merged 2 commits into
mainfrom
fix/gc-toast-default-corridor

Conversation

@sbrants

@sbrants sbrants commented Aug 10, 2026

Copy link
Copy Markdown
Owner

Summary

  • Unanchored Golden Combo OCR used a fallback corridor at y≈0.14 while live Exit Battle locks sit ~0.35, so the band missed the toast zone and recall collapsed whenever Exit wasn't locked (cold start, folded menu with no prior cache, Exit line misread).
  • Fallback now uses the same geometry as a typical Exit lock at 0.35. Warm exit_y cache behavior is unchanged.

Test plan

  • Corridor unit tests (gc_toast_corridor_*) pass, including overlap with live Exit lock 0.35036495.
  • Full ocr::tests suite passes.
  • With menu folded and a fresh New run (no warm cache), GC hits should no longer sit at ~0%.
  • With menu open, hit rate should stay near the prior ~11–12% anchored rate.

When Exit Battle was missing, the toast band sat at y≈0.14 while live locks
are ~0.35, so unanchored GC polls missed the toast and recall collapsed. The
fallback now uses the same geometry as a typical Exit lock.

Co-authored-by: Cursor <cursoragent@cursor.com>
@sbrants
sbrants enabled auto-merge August 10, 2026 07:26
…tests.

Parallel debug-package tests hit the real app DB and failed with
"database is locked". db::open now waits up to 5s; the two zip tests
serialize on a module lock.

Co-authored-by: Cursor <cursoragent@cursor.com>
@sbrants
sbrants merged commit 2884f2e into main Aug 10, 2026
8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant