CODE-034: the reader's commit memo is unbounded — resident bee http leaks

Now: DONE
Sev: MED
Rep: ///bee
Ask: gritzko
Rev: ///bee#184fddf

Input

Context

index/index.js reader() keeps three memos; trees and subs are swept at TREE_CACHE_MAX (index.js:196:Mw, :216) but commits grows without a cap (index.js:287:Mw). Since BEE-048 the ctx — and so the reader — outlives the request (TIPS.set(root, { rev, ctx, tree }), index.js:866:Mw), so a resident bee http accumulates one parsed commit record per commit ever touched, for the life of the process. Found in the 2026-08-21 review.

Goals

Sweep commits exactly as its siblings are swept (or size-cap it); a test or measurement showing the memo stays bounded across many log/diff requests.

Constraints

The sweep must not regress the log walk that motivated the memo.

WIP

TODOs

[ ] bound r.commits like r.trees/r.subs
[ ] before/after residency measurement on a long-lived server