Changes touching this path

• the probe memo #2226 asked for was built and measured and then refused, because the probe it removes is under a twentieth of the walk: locally_missing_objects asks its membership question once per change and manifest entry pair while the answer is a set of distinct addresses, which is 25600 probes for 327 answers on a 200 path missing fixture, and the obvious shape is the probed BTreeSet copied from offered_objects. the named signal reads WORSE with it, in a paired opt-in --missing A/B at the fixture depth, one binary built from each arm and the gate reporting an idle machine on every reading: 18.3 ms to 20.9 ms at width 200 and 96 ms to 110 ms at width 800, because the probe here is a single BTreeMap lookup in the store index rather than the object read the sibling spells, so a set insert over a map of the same order costs more than the lookup it skips. THE CEILING IS WHAT MAKES THAT A REFUTATION RATHER THAN ONE BAD MEMO: a knowingly wrong binary with the probe deleted outright reads 17.5 ms and 91.5 ms on those two fixtures, so any probe-side change on this walk is bidding for under a twentieth of it, and with the manifest walk deleted too the same measurement reads 0.03 ms, which says what the walk spends is materializing and walking each deferred manifest to read the addresses out of it, a loot-codec seam and not this one. so the code is UNCHANGED and what lands is the reading, recorded on the function where the next hunt reads it before refiling. one list-class defect is corrected in the same doc: three callers stood asserted as the whole set beside a pub passthrough on Workspace that is a fourth, and the sentence now names what the callers share instead of how many there are. no mutation proof, because nothing was fixed and no pin was added, and the measurement controls stand in its place: the ceiling binary moves the reading at all, so the half is not blind to the probe, and restoring the pristine body returned it to the landing band. no migration, no wire or format byte moves and no host behaviour moves, so this owes no deploy. the workspace suite is green (4174 passed over 132 binaries, 8 ignored) (#2226) cacd34af · 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.