Changes touching this path

• an npm gate skips npm ci when it would install what node_modules already holds: after an npm ci of its own passes, the site and sdk gates write a stamp into node_modules, from the new loot_first npm_install, holding a blake3 hash of the npm ci arguments, package.json, package-lock.json, .npmrc, the hidden lockfile node_modules/.package-lock.json and the output of npm version --json, and the next pass skips the install only when those match and the rule npm itself uses to trust its hidden lockfile holds (every package and scope folder listed and no newer than it, every listed package on disk, no links), less the time of node_modules itself, which the site tools move. any doubt runs npm ci as before, with the offline classification unchanged, and every later step runs on every pass. measured driving the rows against this lane: the site gate 33.06 and 33.18 s with npm ci and 21.94 to 22.25 s skipped, the sdk gate 5.96 and 6.14 s against 5.00 to 5.10 s. running the npm gates beside cargo test is parked in the ADR 0071 amendment: faster on this desktop at CARGO_BUILD_JOBS=4 (234.9, 283.9, 232.9 and 230.8 s against 257.9, 274.2, 266.3 and 265.8 s in series), but the workspace suite walks site/src while build:wasm rewrites site/src/wasm. pinned in 5 new orchestrator tests; red under named mutations, each restored, over those 5: never skipping (0 passed and 5 failed), stamp inputs not compared (3 and 2), the npm version left out of the stamp (4 and 1), the trust rule unchecked (4 and 1), folder times unchecked (4 and 1), an unlisted folder accepted (4 and 1), and the whole npm rule with the time of node_modules (3 and 2). cargo test green, 4805 passed over 144 test result lines with 14 ignored. no deploy owed; lands use it once the primary loot-first is rebuilt (ywuxnuxp) 66b5db04 · 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.