Require REA for future original-binary investigations

This commit is contained in:
UnixNight committed 2026-10-26 12:32:52 -04:00
1 parent 4a4b1cfc1b
commit 6a7a53c90d
2 files changed
+9

No files matched your search

+4
View File
@@ -42,6 +42,10 @@ docs/checkpoint/README.md, coverage.md and implementation-plan.md before gamepla
changes. Only evidence probes or directly evidenced corrections belong in this
checkpoint; distinguish static recovery, port tests and original runtime evidence.
Use REA for original-binary investigations from now on, including delegated
investigations. Preserve its Evidence and cross-check relevant addresses/bytes;
record provider gaps explicitly and use supporting analysis when needed. Ordinary
source edits and builds do not require a REA call.
Local REA/Ghidra is available through scripts/rea.sh; see docs/rea.md for the
ignored launcher environment and JDK paths. Existing client MCP registration was
not changed. Use generated copies, preserve complete Evidence/snapshots, and keep
+5
View File
@@ -1,5 +1,10 @@
# Local REA and Ghidra
User requirement: use REA for future original-binary investigations, including
subagent work. Retain Evidence, addresses and byte cross-checks; document provider
limitations explicitly. Supplementary disassembly and runtime probes remain useful
when a REA result is incomplete. Ordinary source maintenance needs no REA call.
REA is an analysis dependency, absent from the packaged game's runtime. The
installed MCP tools connected successfully and opened a generated EXE copy with
the authoritative hash. Native decompilation initially lacked an engine. The