buoy and bisect are counted by telemetry like every table verb: both are dispatched ahead of the table and returned before its note_dispatched call, so a report that says it counts each verb never carried either, and the release that ships the telemetry client would have published that gap. each early path now makes the same call with its own spec name, after the same gates and before the run, so help is still not a run and no new string is introduced. a new integration test runs both verbs and reads them back out of telemetry show beside a table verb as the control, and went red when the bisect call was removed. the dispatch comment and the telemetry module header stop saying every reported name is a member of COMMANDS, which was false for other and is false for these two, and say what holds: a spec name literal or other. items 1 and 3 of the ticket are not touched here (#1945) 11291b75 · dbf3dbe6…
Renames are not followed. loot's tree maps a path to an address, so a rename is a delete and an add. This list is the history of the name, not of the bytes.