index/mount.js:182:pN-197 keys subsOf's memo on cache.rev(root) (the CODE-044
fix), but rev() returns a FRESH negative token whenever the tree is big or
blind, so on such a tree the memo can never hit and every mounts() pays a
full openRepo + readCommit + tree walk per root (measured 147 ms cold vs 0
ms memoized with no watcher). Needs a >32768-dir tree or a failed arm
(CODE-058). Found in the 2026-09-18 index review.
Treat a token as "don't cache and don't invalidate", or key on (rev, tokenCount).
S.big and S.blind holding
for the run, never will. So it is never a key (the walk
is stored under the null the watcher-less run already
uses) and never a reason to drop what stands.refs/ fan past GITDIRS) has
a LIVE worktree spot — armTree succeeded, only the git side
did not — and a mount coming or going is a worktree event.
rev() rightly hides that behind a token, so mount.js
cannot use it; a cache.js that told the two blindnesses
apart would keep both the speed and the freshness here.
Wants a ticket of its own (BEE-048 scope).