From 3b29f26c773408a0b037793fdb87169774180a15 Mon Sep 17 00:00:00 2001 From: jochen Date: Sun, 22 Nov 2026 01:22:12 +0100 Subject: [PATCH] Design 47 H2: H-A-427, where the install archive's tree lies --- 03-DESIGN/01-to-be/47-milestones/H2-lead-answers.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/03-DESIGN/01-to-be/47-milestones/H2-lead-answers.md b/03-DESIGN/01-to-be/47-milestones/H2-lead-answers.md index 7eb891d9..47c996c2 100644 --- a/03-DESIGN/01-to-be/47-milestones/H2-lead-answers.md +++ b/03-DESIGN/01-to-be/47-milestones/H2-lead-answers.md @@ -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//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.