CR-16 / NFR-3: million-event residency assertion and close-releases-residency test #157
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Review finding 2026-08-27 (D3). No million-event fixture asserts a residency cap — the bench
mainasserts nothing andDeepPagingGateTestmeasures store paging at 100k;TimelineWindow.close()is never asserted to release resident items (only the room list has that test); the off-live-edge "no Insert" clause is unasserted.Acceptance: a
TimelineWindowover a ≥1M-event sqlite store with a cap, resident size asserted per op and afterclose(); NFR-3 join-path/window cost asserted or the row amended (see the reconciliation sweep).