Changes touching this path

• the two installers come off the prerender list, because a server handler needs no entry there and listing one made the BUILD execute it: /install.sh and /install.ps1 are proxyInstaller handlers rather than pages, so the prerender ran the handler and wrote .output/public/install.sh with the R2 rewrite baked in at build time. production has been serving the LIVE handler all along and the static copy was inert only by nitro route-versus-asset precedence - an accident, and three things were resting on it. ADR 0067 published half is rolled back by re-pointing R2 installers/ prefix, and against a copy frozen at deploy time that recourse changes NOTHING. the prerender also put a network fetch inside every land site gate, since it fetches dl.millerbyte.com and rewriteInstaller throws when dist anchor has drifted, so a land could fail on somebody else uptime. and once 1627 hop lands a frozen copy freezes the hop TAG too, which would 404 through our own hostname while the download count silently flatlined. verified the way the ticket asks rather than by reading config: after the change the build emits neither .output/public/install.sh nor install.ps1, and that absence IS the proof the handler was not executed at build time, since the file only exists if it ran. the shipper bundle is unaffected and the byte budget is untouched, which it would be - the list holds /install, the HTML page, and never held /install.sh. the guard added is not the pair of names it looks like it should be. it derives every route file defining a server handler, derives the prerender list, and asserts the INTERSECTION is exactly robots.txt - set equality rather than a subset, because a none-of-these-two assertion looks identical to a real guard and would let a THIRD handler route be prerendered silently. it carries its own control asserting the two derivations found anything at all, since an empty list intersects an empty list and reads green forever. ⚠ the ticket own text is wrong about the exception and the test says so rather than inheriting it: it says leave robots.txt alone because that one really is a static file with no handler. robots[.]txt.ts IS a handler. it is exempt for a better reason - it returns a compile-time constant string, so prerendering it fetches nothing and freezes nothing, and that is the real rule the installers break. not is a handler, but is a handler whose response depends on the outside world at build time (#1645) 4aea0e29 · 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.