CODE-080: commitTs/blobTs have no production caller; INDEXES.mkd sells them as shipped

Now: OPEN
Sev: LOW
Rep: ///bee
Ask: gritzko
Rev: ///bee#8cb69a0
See: BEE-033

Input

Context

index/index.js:583:Wt commitTs and :594 blobTs are reached from tests only (grep over view/, main.js, door.js, index/), yet INDEXES.mkd:118:6K-124 presents BLOB -> DATE as the pure-index answer every view uses. On the real linux lane they are fast (commitTs 0 ms, blobTs 34-142 ms cold), so wiring them into the date columns is the cheap half. Found in the 2026-09-18 index review.

Goals

Wire them into the list/log date columns, or state the gap in INDEXES.mkd.

WIP

TODOs

[x] consumers on commitTs/blobTs, or the doc line
[ ] blobTs still has none: no view dates a blob, only a path

Design decisions

The list and log date columns cannot take commitTs: both rows read the same commit for its SUBJECT (and log for the author too), so the date rides a read already paid, and the log WALK keys on the COMMITTER time, which CTS lacks.
The one time-only date consumer in the tree is the todo board's stamp, view/todo.js lastTs, so that is what got wired; it falls back to readCommit on a CTS miss, per the BEE-033:46:3I ruling that an old lane is slow, never wrong.
The list/log finding is stated in INDEXES.mkd rather than left as an unwritten "nothing to do here".

Blockers and bummers

blobTs stays caller-less. Giving it one needs a view that dates CONTENT ("first seen at") rather than a path; that is a new column, gritzko's call, not this ticket's.