Extend the 2026-11-16 Node CJS auto-wire so a same-directory Node.js
ESM loader (.mjs or ESM .js) whose static import/export-from specifiers
are Node builtins only also receives the already-landed WASM
bla.sidecar.v1 load-time hook (carrier: "module"). Record
wasm-sidecar-entangle and clear wasm-sidecar-host-verify-only only when
that hook was actually written. Browser fetch-only loaders and ESM
files that statically import user modules or .wasm stay untouched.
Honesty: jsModuleHasHoistedDependencyGraph no longer treats Node
builtin-only imports as a user hoisted graph.
Catalog REA tip 05be423ac inspection/walk ceilings (DWARF, ELF
debug-link/DT_NEEDED, Maven/Gradle, NuGet, Android OTA/boot) as
honesty-only REA_INTERNAL_LIMITS — not densify trip targets.
Cut 3.4.2 for the WASM JS-loader hook auto-wire (record
wasm-sidecar-entangle / clear wasm-sidecar-host-verify-only only when a
same-directory Node CJS loader was actually injected) and the REA
26d88826c catalog hygiene (SQLITE_WORKER_HEAP_BYTES). Also includes the
post-3.4.1 main work already on de982cb.
When sidecarEntangle is on, protectTarget and hardenProject inject the
already-landed WASM JS-loader hook into a same-directory Node.js CommonJS
loader that already uses fs and WebAssembly.instantiate/compile/
instantiateStreaming and mentions the .wasm basename (known names only:
<stem>.cjs/.js, loader.*, index.*). Browser, ESM, minified, already-
entangled, and unranked app entries such as license.cjs are left
untouched so baked self-seal digests stay valid. Record
wasm-sidecar-entangle and clear wasm-sidecar-host-verify-only only when
that hook was actually written. Default remains OFF.
Catalog REA tip 26d88826c SQLITE_WORKER_HEAP_BYTES (256 MiB) as honesty-
only; no new 1:1 densify counters in the +208 delta.
Update Skill B, DESIGN, STATE, CHANGELOG [Unreleased], MCP
sidecar_entangle descriptions, and CLI help so ESM-native preambles
are not described as full process-start strip⇒fail. Keep the
CJS-into-ESM functional-equivalence rule; document the hoist gap.
package.json requires `^22.23.4 || >=24.0.0` and STATE.md documents the final
gate matrix as Node 22.23.4 plus Node 24.22.1, but the CI matrix asked for the
floating `22` alias, so the leg could silently resolve below the supported
floor and never proved the minimum we declare. Pin it to 22.23.4 and describe
the matrix accurately in STATE.md.
Cut 3.4.1 for the optional WASM JS-loader sidecarEntangle hook and the
REA #11144 / #11181 catalog hygiene (JavaScript member-mutation work
allowance).
Add generateSidecarWasmLoaderSnippet / prependWasmSidecarLoaderHook /
entangleWasmLoaderWithSidecars / computeWasmSidecarCodeIdentity so a host JS
loader can wrap WebAssembly.instantiate, compile, and instantiateStreaming
and fail closed when a protected module's bla.sidecar.v1 custom section is
stripped or sibling sidecars are altered. Unrelated WASM passes through.
The hook is host-opt-in; wasm-sidecar-entangle stays unrecorded and the
wasm-sidecar-host-verify-only honesty gap remains until a protect/harden
path actually injects the hook. sidecarEntangle stays default OFF.
Catalogue REA #11144 / #11181 javascript.member_mutation_alias_states as
REA_INTERNAL_LIMITS (recoverable budget, not a densify trip target).
Cut 3.3.2 for the SQLite schema-comment sidecarEntangle increment and
the REA #4445 / #9756 catalog hygiene (NativeAOT work-budget scaling
and Android split-fact report allowances).
When sidecarEntangle is opted in, plant an unused bla_sidecar_v1 VIEW
(SELECT '<json>' AS "bla.sidecar.v1" WHERE 0) binding sibling sidecars
(generate/bind/entangle/verifySqliteSidecarSchemaComment). User tables,
rows, query results, WAL/FK, and application_id/user_version stay
unchanged. Host-verify only — do not record sqlite-sidecar-entangle
until a load-time hook lands; defenseScore annotates
sqlite-sidecar-host-verify-only (soft-cap 93). Default remains OFF.
Also catalogues REA #4445 NativeAOT work-budget scaling
(NATIVE_AOT_BASE_WORK_UNITS + 8 units/byte; a relaxation, not a new
densify target) and REA #9756 ANDROID_NATIVE_SPLIT_TYPES / _TYPE_CHARS
(report allowance only).
Cut 3.3.1 for the DEX string-pool sidecarEntangle increment, the
REA #10227 DEX_ARRAY_DIMENSIONS catalog, and the already-landed
post-3.3.0 work (MBA substitutions, hypothesis-revision decoys,
release-hygiene gate, verify-sidecar CLI, technical SEO).
README.md, STATE.md and the localized README each published a different
aggregate (639.5x vs 612.5x) and every per-target row in both benchmark tables
was stale. Refresh both tables and the aggregate line from a live run, and add
a guard that keeps the three surfaces equal and within 10% of the computed
showcase aggregate.
Extend opt-in sidecarEntangle to GGUF via a bla.sidecar.v1 STRING metadata KV
(generateSidecarGgufMetadataNote / bindGguf / entangleGguf / verifyGguf), with
alignment-safe rebuildGguf so tensor bytes stay bit-exact. Host-verify only
(loaders ignore unknown STRING keys); do not record gguf-sidecar-entangle until
a load-time hook lands; defenseScore gap gguf-sidecar-host-verify-only.
Also fix protectGgufBuffer which previously corrupted tensor data by splicing
KV bytes without re-padding the aligned data section. Default OFF.
* fix(crackme-v9): seal.json absence throws integrity check failed
loadSeal() used to let ENOENT from missing seal.json soft-fold through
verifyLicenseGate into [license] DENIED (same as a wrong key). Pin failures
must fail-closed: throw integrity check failed: seal.json missing so delete
matches digest-mismatch hard-fail. Published hardened still needs rebuild.
* test(crackme-v9): assert seal.json delete hard-fails on cleartext and fixture
Covers the ENOENT≡digest-mismatch invariant through materializeTarget and
full 4-stage fixture harden. Release hardened fixture still predates the
host fix until CRACKME_V9_* rebuild.
* docs(skill,state): pinned digests fail-closed on absence (v9 red 2026-11-10)
Skill B: EXPECTED_*_SHA256 pins must hard-fail on ENOENT, never soft DENIED.
STATE/CHANGELOG/DESIGN record the exposure, source fix, and published
hardened residual until release-secret rebuild.
* fix(sidecar): do not claim pyc-sidecar-entangle for a host-only trailer
The TYPE_ASCII marshal note is ignored by importlib, so strip or sibling
delete still execute. Recording pyc-sidecar-entangle (and clearing the
strip⇒fail defenseScore gap) was paper coverage. Keep planting the note
and host verifyPycSidecarMarshalNote; annotate pyc-sidecar-host-verify-only
until an import-time hook lands.
* test(sidecar): assert .pyc marshal notes stay host-verify only
protectTarget must not list pyc-sidecar-entangle; importlib still returns
the same RESULT after trailer strip or sidecar delete, while the host
verifier fails closed. defenseScore keeps cap 93 via the new gap when
the host-only note is enabled.
* docs(skill,state): sidecar vectors require a process-start hook
Skill B: only record a countered strip⇒fail sidecar vector when the
entry hook hard-fails at process start or import. Host-only verifiers
(such as verifyPycSidecarMarshalNote) are binding notes, not coverage.
CHANGELOG/STATE/DESIGN record the 2026-11-12 honesty residual.
Complete opt-in ASAR sidecar entanglement with an in-archive Electron main
JS preamble (generateSidecarAsarMainJsPreamble / selectAsarMainJsMember /
entangleAsarMainJsWithSidecars) that re-measures decoy members via
fs-patched readFileSync. Digest labels stay asar-root-relative for parity
with .bla/sidecar.v1.json; protect + harden wire when sidecarEntangle is
on (default OFF). REA +12 since e9b6c87c1 had no new 1:1 densify budgets.
Plant a bla.sidecar.v1 custom-section note with the sidecars-mode binding
digest + path labels (no export/behavior change). Host-side
verifyWasmSidecarCustomSection re-hashes siblings for strip/alter fail.
Wire protectTarget (.wasm) and harden WASM-only post-pass when
sidecarEntangle is on (default OFF). DESIGN/STATE/CHANGELOG updated.
Bust require.cache via realpathSync and re-verify strip/alter with a
fresh node process so /var→/private/var tmpdir aliases cannot leave a
stale module cached (CI macos failure on #93). Document #95 missing-
sibling hard-fail in STATE/CHANGELOG Unreleased.
The install guide advertised Node ^22.13.0 while package.json requires ^22.23.4; STATE.md called releases tag-only although the release workflow can publish to npm with provenance; and the README benchmark was a v1.4.0 run on a v2.1.0 project. Refresh the numbers from a local v2.1.0 benchmark (639.5x tokens / 304.4x cost, 14/14 runtime-exact) and align the AGENTS.md engine range.
Skill section B: entry counts as self-covered only when its runtime check
hard-fails on its own bytes; check integrityCoverageSelfVerified; keep
host-trust values inside covered artifacts. STATE/CHANGELOG/design note
record the 2026-11-05 CrackMe v8 round (NO PRIZE, REA unverified).
Bump package/identity/lock to 2.0.0; CHANGELOG + STATE + Skill v2.0.0
document packaging-gates, MCP write-safety, and R1–R12 refuse/recipe/honesty
vs 1.x. Release notes in docs/releases/v2.0.0.md.
Restructure Skill principles into A refuse gates, B product recipes
(SHA-256 KDF, commitment-outside-XOR, host FLAG+cert), C engine hygiene,
D white-box residual. Extend format-wasm appendix through R12; refresh
cli-and-mcp + CHANGELOG/STATE. No new refuse lint for P2 WASM RE.
The state header still said 1.4.6, called the publish blocker a missing
GitHub token, and listed firmware as skipped. Releases are now tag-only
(CHANGELOG carries 1.6.3), the CI matrix runs Node 24 on ubuntu/macos/
windows, and 1.6.2 shipped the UF2 firmware shield against REA #8230.
Update the version/status/publishing lines and split the firmware row
so UF2 is tracked separately from the still-skipped SPIR-V/CUDA/AMD
GPU objects. No code changes.
Critique #3/#4: npm run redteam:rea is the sole authoritative gate (JS now
trips real REA resourceLimits); verify:rea labeled drift-harness-only.
Anti-strip vitest proves grep -v cannot recover clean source. Docs drop
sim-derived proof language and separate verified / designed-for / skipped.