Changes touching this path

• the site loads clerk-js at the exact version the installed clerk-react was built with, not the floating major: both ClerkProviders asked the CDN for @clerk/clerk-js@5, which it answers with an uncached 307 to its newest release, so whatever Clerk published ran unreviewed on the page that holds the seed. vite.config.ts now defines __CLERK_JS_VERSION__ from tools/clerk-js-version.ts, which asks the @clerk/shared under @clerk/clerk-react for the clerk-js it was released with (5.127.1 today), and each ClerkProvider passes it as clerkJSVersion; the CDN serves that URL with no redirect and as immutable. no subresource integrity: the clerk-react loader takes no option for one. pinned in vitest: the version is exact, is the one the installed shared names, lands in the script URL clerk-react builds, every ClerkProvider under src passes it, and the build carries it. red under named mutations, each restored: the private gate without the prop (1 failed and 4 passed), the account page without it (1 and 4), the helper returning the major (3 and 2, and 2 and 3 with its check off), a typed 5.128.0 (1 and 4), shared resolved from the site (3 and 2), and the build without the define (1 failed and 7 passed). local trace, signed out, warm: the script comes from cache at 30 ms against 51 to 60 over the redirect, and Clerk.load still starts at about 137 ms either way, on the 100 ms poll in clerk-react. cargo test green, 4886 passed over 144 test result lines with 15 ignored, and the site gate green at 945 passed. CONTEXT.md and ADR 0096 say so. owes a site deploy (lzxtqwxq) f80b7345 · 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.