* feat(ghidra)!: import recognized DOS COM files with ComLoader Select Ghidra 12.2 ComLoader for an admitted .com image and do not pass a base address, so the file stays at 0000:0100. Images ComLoader rejects use the explicit BinaryLoader import at 1000:0100 and record the typed reason. BREAKING CHANGE: A DOS COM file that ComLoader accepts now loads at linear 0x100 instead of 0x10100. Read load_address. The BinaryLoader fallback remains at 1000:0100. * fix(ghidra): score COM dollar-strings in one pass ComLoader's printable-run walk restarts at every offset, so a 64 KiB image of printable bytes blocked profile resolution. The same capped count now skips a run once an earlier start has seen every later dollar sign. Co-authored-by: morluto <morluto@users.noreply.github.com> * fix(ghidra): align COM import facts with the image Ghidra receives Mismatch load-image coordinates follow the measured loader and address. A dotfile named .com keeps that suffix on the snapshot, and selection uses that snapshot name. The COM fallback verifier owns its MCP connection before connect. Co-authored-by: morluto <morluto@users.noreply.github.com> * style(ghidra): format COM snapshot and verifier files Co-authored-by: morluto <morluto@users.noreply.github.com> * fix(ghidra): keep measured COM facts and required MZ coordinates DOS MZ and a verified COM image keep load_segment and entry required. A COM mismatch emits a known loader or load address on its own, and omits the segment and entry only when that pair is not a known layout. Co-authored-by: morluto <morluto@users.noreply.github.com> * fix(ghidra): require the verified COM layout and document both entries A verified COM image is either ComLoader at 0000:0100 or BinaryLoader at 1000:0100 with a fallback reason. The DOS guide queries 0x100 only for the ComLoader entry and 0x10100 for the fallback. Co-authored-by: morluto <morluto@users.noreply.github.com> * fix(ghidra): attest COM imports against the committed loader --------- Co-authored-by: Cursor Agent <cursoragent@cursor.com> Co-authored-by: morluto <morluto@users.noreply.github.com>
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.