Changes touching this path

• loot ticket comment, resolve, label, wait, edit and frontier ship as slices 2 and 3 of the native tracker (spec §12, map #2422): each write to a ticket adds one event file under it, c/ with author and created-at, r/ with a one-line gist and a body that are both required, l/ and w/ as add or remove events, or for edit rewrites meta or body and no other file, keeping every meta header it does not set; a write to a ticket this identity cannot open is refused. resolve prints the tickets its closing unblocks, and a second answer is kept beside the first, which stays the answer. frontier <map-id> is the open children with no open waits-on target, in causal order, where a target not filed yet counts as open; --porcelain is the tickets rows and nothing else, recorded in an ADR 0023 amendment, and the human form marks the rows a live lane holds and adds a line with the takeable count and the file opens. the index now counts every file it opens by kind, and the frontier opens each meta, the w/ files of each open child and the l/ files of each row, never a body, comment, attachment or resolution. show of a map renders its prose, then Decisions so far from the first gist of each closed child, then its frontier. the spec, CONTEXT.md and ADR 0066 record what shipped, and the usage line count moves to 143. red under sixteen named mutations, each restored, over the 26 ticket tests (23 passed and 3 failed for the first, 24 and 2 for three, 25 and 1 for the rest): events ordered by name not position, decisions taking the last answer, the frontier folding each child whole, an absent target read as closed, edit dropping unset headers, edit writing an event, a further answer unblocking again, unblocking past other open targets, a comma in a label, a sealed ticket writable, no lane holding a row, the summary in the porcelain, no index under a map, an empty gist, no note for an absent wait target, and a comment with no created-at. cargo test green, 4627 passed over 142 binaries with 13 ignored (#2427) 7d705601 · 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.