Changes touching this path

• a leaked secret in stored error text can be purged (ADR 0101): loot_metrics migration 0005 defines purge_error_text, callable only by the migrating superuser, which deletes every wide_event row holding the text as a literal substring in any text column, cuts a matching error issue title back to its type and keeps its fingerprint and counts, answers two counts, and refuses a text under 8 characters; the scripts repo errors:purge verb takes the text masked or from a file, never a command line. it also joins the lines Docker json-file splits past 16 KiB, which the first production tick of the error shipper dropped as partial=1 and which for a busy minute counter line loses the exact counts: parseDockerLog walks the bytes, joins consecutive entries per stream, drops a joined line only past 1 MiB, and reports safeBytes so the position never passes a line still being split. pinned in errors.pg.test.ts, 7 tests on Postgres 18, and errors-ship.test.ts, 17; red under named mutations, each restored, failed and passed: no delete, the title kept, anyone may purge, no length floor, the error text not searched (each 1 and 6), no join (1 and 16), the position past a split line (1 and 16, after the test put a whole stderr entry behind the split one, where it first survived), one pending line for both streams (2 and 15). owes a site deploy with the scripts change (ntkmpoqn) 568ee1cd · 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.