Changes touching this path

• CONTEXT.md gets its Proposal entry checked against the tree. the two sentences the ticket names had already been made true by later lands, so they stay in the present tense and gain the ticket that built them: ingest closing a proposal row from the head set it declares was built by #2177 (3ea3edc) and moved onto propose::landed_by_declaration by #2235 (6844205), and the land reading the required roles off the .lootpipeline on main was built by #2178 (cd10e16). the rest of the entry and one neighbour were not true, and are corrected: the entry said the land refuses without its verdicts, where it refuses on what that .lootpipeline declares and is advisory with no require line there, which is now said; the ingest transaction is no longer called pure writes, which #2273 narrowed in store.rs and ADR 0075 to the landing decision reading nothing inside it; until #2162 becomes when #2162 was decided, since that land was docs only and the producers came with #2174, #2176 and #2177, and the owner read routes and the web views of #2175 are named; an owner cannot propose, which nothing enforces for a new row, becomes the reason the declined arm exists; may_push is named as the rule require_pusher decides, since no function carries that name; the reaper sentence names #493, where an inserted paragraph had left that reaper without its antecedent; and Foreign authorship said loot-first reads no change author, false since #2178, now in the past tense. docs only: no code, migration, format byte or wire byte moves, so this owes no deploy. CONTEXT.md holds 0 CR bytes, and the tests that read it are green, published_surfaces (6 passed), opt_in_halves (4 passed) and work_counters (12 passed); the full suite was not run (#2207) c0bc64a3 · 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.