* feat(ghidra): edit function annotations atomically Return annotation readback and refreshed function analysis through CLI and MCP. Own each database transaction, invalidate caches and immutable snapshots, preserve executable bytes, and retain the Windows mutation boundary. Assisted-by: Nitori (gensokyo-skills:nitori-reverse-engineering) * fix(ghidra): preserve qualified function annotation identity Preserve namespaces during local name writes and match qualified readback to the refreshed dossier. Add a producer-shaped regression and verify a real namespaced C++ function through the CLI. Assisted-by: Nitori (gensokyo-skills:nitori-reverse-engineering) * test(ghidra): align verification with annotation authority Keep strict capability and profile checks while admitting the explicit session metadata operation. Verify packaged transport authority and atomic transaction commitments and preserve a read-only Windows expectation. Assisted-by: Nitori (gensokyo-skills:nitori-reverse-engineering) |
||
|---|---|---|
| .. | ||
| 0001-provider-selection-and-analysis-profiles.md | ||
| 0002-controlled-replay-authority-and-sandbox.md | ||
| 0003-managed-code-evidence-and-provider-boundary.md | ||
| README.md | ||
README.md
Architecture decision records
Accepted decisions describe the architecture that implementation PRs must follow. Acceptance does not by itself mean the behavior is shipped; each record states its implementation status separately.
| ADR | Status | Implementation |
|---|---|---|
| 0001: Provider selection and analysis profiles | Accepted | Provider selection and 22 Ghidra operations shipped on Linux/macOS; experimental Windows x64 P0 with bundled native controls |
| 0002: Controlled JavaScript replay authority and sandbox policy | Superseded | Historical design; the controlled JavaScript replay tool was removed |
| 0003: Managed-code evidence and provider boundary | Partially superseded | Seven static managed tools remain; runtime planning removed |