Changes touching this path

• the site bundles @clerk/clerk-js 5.127.1 from the lockfile, pinned exactly at the version the installed clerk-react 5.61.9 was built with, and hands each ClerkProvider a Clerk that src/lib/clerk-instance.ts constructs once per document, through its Clerk prop, so clerk-react loads that instance at once where it inserted a CDN script with no integrity and polled window.Clerk every 100 ms. the clerk-js npm build is one module that carries its UI components and fetches no chunk at run time, 2.96 MB or 949 KB at gzip -9, which the private gate and /account load on demand; no public page fetches it, and on a build with a key each public surface weighs 21 to 29 B more for the import entry. the private CSP drops the Clerk frontend API from script-src and keeps it in connect-src. red under named mutations, each restored: the frontend API back in script-src (2 failed and 14 passed), a provider without the instance on the private gate or on /account (each 1 failed and 12 passed), clerkJSVersion beside the instance (1 and 12), a new Clerk per call or one kept across keys (each 1 and 12), /account constructing its own Clerk (1 and 12), clerk-js pinned at another version or at a range (each 1 and 12); on the built server, the frontend API in script-src and the instance imported eagerly by private.tsx (2 failed and 6 passed, one test each) and another expected version (1 failed and 7 passed). site gate green at 1142 passed; cargo test green, 5021 passed over 144 test result lines with 15 ignored. CONTEXT.md and ADR 0096 say so. owes a site deploy; also carries a comment on lnmntzxw with its live reading (svlsyqkr) 9388597a · 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.