instar 1.3.100 → 1.3.102

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -39,3 +39,17 @@ Revert the commit. No persisted state or schema affected; the load-test gate is
39
39
  ## Tests
40
40
 
41
41
  `tests/unit/server-supervisor-preflight.test.ts` (+3: PATH-pin, prebuilt-first, restore-on-failure) and `tests/unit/NativeModuleHealer.test.ts` (+1: prebuilt-first + PATH-pin). 32 tests across the two files green; existing 37 healer tests + preflight tests still pass; `tsc --noEmit` clean. At-scale: `npm install better-sqlite3@12.10.0` (PATH-pinned) fetched the ABI-141 prebuilt in ~2s on the affected box.
42
+
43
+ ## Fix-forward note (CI green-up)
44
+
45
+ The first cut of this change (shipped functionally in v1.3.100) tripped two CI
46
+ checks that are non-functional: (1) the destructive-tool-containment lint —
47
+ the backup cleanup/restore used direct `fs.unlinkSync` instead of
48
+ `SafeFsExecutor.safeUnlinkSync`; and (2) a stale source-text test
49
+ (`version-skew-recovery.test.ts`) that asserted the rebuild "uses
50
+ --build-from-source" as its only strategy — the exact policy this change
51
+ replaces with prebuilt-first. This follow-up swaps the `fs.unlinkSync` calls for
52
+ `SafeFsExecutor.safeUnlinkSync` and updates that test to assert the new
53
+ invariants (ABI-pinned + prebuilt-first, with `--build-from-source` retained as
54
+ the compile fallback). Pure compliance/test correctness — no runtime behavior
55
+ change beyond what v1.3.100 already shipped.