docs(docs): R5.7 pre-merge record, final security audit, doc precisions
This commit is contained in:
1 parent
27bf59cd4b
commit
97529f95b8
5 files changed
+241
-5
No files matched your search
@@ -3817,7 +3817,8 @@ the N-1 suites (`n-1.reader`, `r5-6.n-1`, `n-1.scanner`), seed and sheet integri
|
||||
**Owner validation and pre-merge checks (2026-10-25, brief « Validation R5.7 et dernière vérification pré-fusion »).**
|
||||
R5.7 is validated. Decision C6: `tsx` may stay named in the lockfile as long as it is only the optional peer of vite
|
||||
(`pnpm why tsx -r`: `tsx` 4.23.15 reached only as `vite` 7.3.6's peer, `peerDependenciesMeta.tsx.optional: true`, through the
|
||||
devDependencies of the app, `core-wasm` and `supabase`; no importer lists it, no `node_modules/.bin/tsx`); no lockfile hand edit,
|
||||
devDependencies of the app, `core-wasm` and `supabase`; no importer lists it, no root `node_modules/.bin/tsx`; pnpm links the peer's bin under the three packages' own
|
||||
`node_modules/.bin`, which no script calls); no lockfile hand edit,
|
||||
no override; the contract records the clarification and the census still fails on a declared `tsx`, a manifest script naming it or an
|
||||
importer listing it. The 149 `replaced` rows were checked active: every cargo target runs in `cargo test` (none `#[ignore]`d,
|
||||
now asserted by the census), the two vitest targets name existing cases, and every cited oracle is read by a test (the 26
|
||||
|
||||
Reference in new issue
Block a user