Design 47 H2: H-A-427, where the install archive's tree lies

This commit is contained in:
2026-11-22 01:22:12 +01:00
parent 13e53e498c
commit 3b29f26c77
@@ -479,3 +479,8 @@ The lead's one-line answers to the questions H2's develop and review raise (impl
P3. Noted for after H2 (§819's check): the integration count takes every test the integration run reports, untagged
ones and subtests included, so a fold hides rows behind a t.Fatal; the check should count the tagged top-level test
functions, and a module's fold then needs no plain loop.
- **H-A-427 (where the install archive's tree lies, 01:23)** §800, BM3. The install's archive holds
`modules/<module>/node_modules/…` and nothing else (never the synthesized package.json), so unpacking it at the
workspace tree's root lays the modules where the Go build module's tests expect them (BM2's layInstall). The install
writes the package.json npm ci needs from the lock's root entry (name, version, the four dependency maps, no scripts)
and refuses a lock with no root entry (lockfileVersion 1), naming it. P3, P-failure-loud.