Changes touching this path

• loot ticket and loot tickets read the ticket-only changes on the forge that have not landed, as a layer between landed main and this position (ADR 0098 §6, the overlay): forge_view asks the default remote for its heads when it answers as a forge, loads what the shared graph holds and stows the rest in memory through the relay append-only ingest, after which the handle refuses to persist, so no head, pointer or conflict of any position moves and #2390 is untouched; a head is overlaid only when every forge-only change it reaches passes the land judgment and its tree matches its base outside tickets/, and the layer holds only what that line wrote under tickets/. a write reads the ticket it names through the same layer, so a web ticket takes a comment before it lands, and a ticket the forge moved to another space is refused as #2454 refuses one landed main moved. every ticket leaf and loot tickets take --offline; a read says on stderr what it took from the forge or why it read locally (no forge, unreachable, --offline), human rows mark forge tickets, and a forge file this identity cannot open reads as an S row naming loot pull-grants in the primary. the bundles a read fetched are recorded in .loot/forge-view, a new position-owned store artifact excluded from undo, and a read inside forge_view::FRESH_SECS answers from it without asking. ADR 0098, the spec §6 note, CONTEXT.md and the usage lines say so, and the Workspace width census moves to 411. pinned against an in-process forge with a second clone of the identity as the web writer; red under named mutations, each restored: a read persisting what it stowed (0 passed and 1 failed), the persist guard off (0 and 1), --offline ignored (0 and 1), the judgment not read and the tree property off (each 0 and 1 over the judgment pin, and together 0 and 1 over the end-to-end pin, which each alone leaves green since the other still keeps a code write out), the layer ignoring its base (0 and 1), no forge_elsewhere (0 and 1), the record never fresh (0 and 1), a sealed forge file not counted (0 and 1), the layer not folded (0 and 1), and a leaf or the listing without --offline (0 and 1 each). cargo test green, 4707 passed over 143 binaries with 13 ignored. client only, no deploy (#2430) 8ca351c0 · 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.