* feat(ghidra): admit RISC-V position-independent executables (#4487) Admit little-endian RISC-V ELF32 and ELF64 position-independent executables (ET_DYN with PT_INTERP) into the pinned generic Ghidra lane. - Collect `PT_INTERP` during the existing validated ELF table walk in `validateElfDeclaredRanges` and record `hasInterpreter` in target metadata, supporting arbitrary table offsets and extended program counts without duplicate scanning. - Admit ET_DYN images when `hasInterpreter` is present under lane identities `elf32-pie-le-double-float-generic-v1` and `elf64-pie-le-double-float-generic-v1`. - Preserve refusal for non-PIE ET_DYN targets (shared libraries without PT_INTERP) explaining that shared libraries require separate load verification. - Record load model facts (`load_model: "pie"`, `expected_default_image_base: "0x10000"` or `"0x100000"`, `has_interpreter: true`) in `riscv_elf` analysis profile parameters. - Record default image base analysis coordinates limitation for PIE targets. - Update `docs/ghidra-riscv.md` with PIE admission boundary and evidence semantics. - Add unit tests for PT_INTERP collection, high-offset program headers, and PIE profile resolution. - Add PIE fixture generation capability to `tests/conformance/ghidra/riscv-fixture.mjs` and pass `-Wl,-pie` to ensure bare-metal drivers generate ET_DYN. - Extend `scripts/verify-real-ghidra-riscv.mjs` to test both ET_EXEC and ET_DYN. Fixes #4487 * fix(ghidra): check structured facts and rethrow typed errors in PIE tests * style: format GhidraRiscvProfile.test.ts * fix(ghidra): restrict PIE admission to verified double-float RISC-V lanes
Source-built conformance fixtures
These sources are deliberately small semantic oracles for REA providers. Run
npm run verify:fixtures on macOS or Linux to compile them into the ignored
build/conformance/ directory, emit a hash-and-toolchain manifest, and verify
their platform-native symbols and strings with local command-line tools. The
portable C, version, and large-inventory fixtures build as Mach-O on macOS and
ELF on Linux; Objective-C, Swift, and N-API-like fixtures remain macOS-only.
Only source files are versioned. Generated binaries, generated large-fixture
source, debug information, and manifests must remain under build/.
ghidra/inventory.c is also compiled into temporary Linux ELF debug and
stripped variants by npm run verify:ghidra. It fixes local functions, external
puts linkage, defined strings, and writable/executable memory needed to prove
the read-only Ghidra inventory contracts without committing a binary.
scripts/create-ghidra-windows-fixture.mjs separately emits a deterministic,
ignored native x86-64 PE application for the controlled Windows Ghidra P0 lane.
The generator and fixed SHA-256 are versioned; the .exe is never committed or
executed. npm run verify:ghidra:windows uses it to verify the admitted read-only operation inventory,
digest linkage, transport, and cleanup on the self-hosted real-Ghidra runner.
The C fixture fixes a known call chain and strings. The version pair fixes an added symbol, changed string, and changed call relationship. The generated large fixture contains 1,205 uniquely named functions and strings to verify that providers return complete inventories. Objective-C, Swift, and N-API-like fixtures provide metadata-oriented inputs without package or network dependencies.
readiness/ adds source-only generated JavaScript CLI and Electron fixtures for
the repository's reconstruction-readiness verifier. npm run verify:readiness
inspects the compiled native fixture through CLI and checks JavaScript/Electron
static-analysis Evidence identity through CLI and MCP. It does not execute the
fixture applications. The development-owned evaluator under readiness/report/
separately checks synthetic report conformance; its nine stages do not describe
observed runtime journeys. The report keeps these scopes separate as documented
in docs/development/reconstruction-readiness.md.