gensokyo-dev
740c0f5615
Restore independent PE fixtures and dependency-complete standalone artifact verifier tests. Execute existing real Windows native behavior and inspection recovery proofs before unrelated curated tests. Validation: 101 focused tests; full typecheck; scoped lint, module/discovery/format/docs checks; valid/corrupt real-image verifier controls; real Windows artifact, behavior, and inspection recovery proof steps passed. Greptile found no actionable issues. Codex review quota exhausted. CI remains red from exact-base failures: Source 9, Windows 7 (base 15; loader 8 repaired), and built shard 4's 7 matching failures; 7 other shards cancelled by fail-fast. Later Windows package/Node 22/24 checks skipped. User explicitly authorized bypass of established main failures. No claim of complete CI or unavailable coverage. Fixes #7474.
Windows native controls
REA ships one Windows x64 Node-API 8 addon. Users do not compile it or install another runtime. Ghidra and a full JDK remain bring-your-own prerequisites. The addon uses Windows 10+ APIs and admits fixed local NTFS volumes only.
The package owns the artifact path. The loader checks the package version, ABI, Node-API compatibility, PE architecture, and SHA-256 before loading it. There is no environment override for loading an arbitrary native module.
Build
The artifact lane requires Linux, MinGW-w64 x86_64-w64-mingw32-g++,
x86_64-w64-mingw32-dlltool, and tar. It never installs these commands.
Node-API headers are reused from the build cache or downloaded from the
pinned official Node release with its published SHA-256 checked.
npm run build:windows-native
npm run verify:windows-native:artifact
npm pack
build/ is ignored by Git. The npm file inventory includes only the addon and
its manifest. Release CI builds both, and prepublishOnly rejects a missing,
stale, mismatched, or wrong-architecture artifact. A development tarball built
without this lane reports Windows native controls as unavailable.
Restore the artifact in a source checkout
The source tree omits native/windows/build/ from Git. To run Windows
provider-backed workflows from a checkout without the MinGW build lane, extract
the two files from the published rea-agents tarball whose version exactly
matches the checkout's package.json version. Do not use latest or copy files
from another REA version; the loader verifies the manifest version, ABI,
architecture, and addon digest before it grants authority.
From the checkout root, replace <matching-version> with the version in
package.json:
npm pack rea-agents@<matching-version>
tar -xzf rea-agents-<matching-version>.tgz
mkdir -p native/windows/build
cp package/native/windows/build/manifest.json native/windows/build/
cp package/native/windows/build/rea-windows-x64.node native/windows/build/
This is a manual recovery step. REA does not fetch or install the artifact automatically. Alternatively, build it using the Linux/MinGW lane above.
Boundaries
- Opaque Node objects carry a native type tag, resource kind, and closed state. A pathname, serialized object, or forged handle cannot grant authority.
- Input admission opens every com