Changes touching this path

• a browser error's frames are traced back to their source file, line and name before its stack is parsed, through the serving release's own source maps, which the client build writes hidden and tools/stash-maps.mjs moves out of the public directory, refusing a build that leaves one there, names one from a chunk, or writes none; so a browser fingerprint names source functions and holds across releases. only a bare hashed chunk name is looked up. ADR 0101 section 4 amended. pinned, red under named mutations, each restored (yyypksru) Perf-Baseline: reset object_gets and graph_sorts moved with 587f93b, whose negotiation workload now builds the forge push a land makes (opywoozo); this change touches no Rust d0d1df9d · dbf3dbe6…
• the errors view renders the same text on the server and in the browser: every ago counts from the time the server read the page, counts are written in en-US and instants in UTC, where a clock and a locale read on each side made React throw on hydration, the two open error issues the new source maps traced into react-dom; and the client build takes its source maps out of the bundle itself, so the server's asset manifest names none, where moving them after the build left each listed and a request for one answered 500. pinned, red under named mutations, each restored; mwvpnyss and wvyoprtz noted (lrysrpyt) Perf-Baseline: reset object_gets and graph_sorts moved with 587f93b, whose negotiation workload now builds the forge push a land makes (opywoozo); this change touches no Rust de0c6d21 · dbf3dbe6…diff

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.