CODE-074: the blob round lexes every blob when only the TRI round owes work

Now: OPEN
Sev: MED
Rep: ///bee
Ask: gritzko
Rev: ///bee#8cb69a0
See: BEE-071
See: BEE-067

Input

Context

index/lindex.js:327:PS calls hk.parse on every moved blob regardless of which rounds owe: forcing the TRI-only round on git.git gives links:0 syms:0 with parse = 1.85 s and 4807 lexes, 100% waste. That is exactly the BEE-071 upgrade path every existing repo takes (LINK/SYM marks at the tip, no tri mark) and the path after any failed tix.commit at :293. Also :319 builds a progress() in blobRound but never ticks it, so the 8-43 s scan shows nothing, and N workers interleave their note lines. Found in the 2026-09-18 index review.

Goals

toks = (gates.linkUp && gates.symUp) ? null : hk.parse(...); tick the progress per blob.

WIP

TODOs

[ ] repro: TRI-only round lexes nothing
[ ] progress ticks in the blob round

Design decisions

The gate is read where the lex is: toks stays null when both text rounds are up, and linkRows/symRowsOf are the only readers, so nothing downstream sees the null.
The tick counts EVERY blob of the list, binary and over-cap ones included, since the list is what the round walks.
prog.done() closes the line the ticks opened, as the commit walk does at index/index.js:1162:Wt.
The repro is in test/lindex/rows.js: tri.laneOf stubbed to null builds the pre-BEE-071 index (LINK/SYM marked, no tri mark), then a counting hk.parse and a counting idx.progress measure the TRI-only round — 5 lexes and 0 ticks before, 0 lexes and 6 ticks after.