fix(docs): update browser capture guide link after move (#2820)

Refresh gettext protected-link comments alongside the authored href.

Co-authored-by: Codex <noreply@openai.com>

.agents/skills/rea-analysis-optimization/SKILL.md

@@ -1,113 +0,0 @@
----
-name: rea-analysis-optimization
-description: Optimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit.
----
-
-# REA analysis optimization
-
-Find a concrete source of unnecessary work, change it at its owner, and verify
-equivalent completed investigations. A useful outcome can also be a measured
-decision to leave an implementation alone.
-
-Follow the checkout's [performance priorities](../../../AGENTS.md#performance),
-[tool design](../../../docs/tool-design.md), and
-[testing guide](../../../docs/testing.md). This skill supplies an optimization
-workflow, not additional permission to execute targets, publish, or merge.
-Use the current contracts, provider prerequisites, and user authorization.
-
-Read [the Kuna case study](references/kuna-case-study.md) when selecting a
-reuse strategy or interpreting a benchmark. Its pinned observations illustrate
-tradeoffs; they are not current-provider guarantees or universal speedups.
-
-## Pin the question and the correctness oracle
-
-Describe the analyst's completed task, including the facts and relationships
-needed to answer it, requested detail, source access, and meaningful unknowns.
-Choose a representative real artifact and a small or empty case. Record the
-baseline revision, target digest, engine identity, options, host, and entrypoint.
-Use a separate checkout for changes without disturbing other work.
-
-Establish an oracle independent of the changed implementation: source-built
-fixture expectations, independently mapped file bytes, or a native producer
-paired with checks of its interpretation. Comparing two wrappers around the
-same faulty decoder does not establish correctness. Preserve address widths,
-same-address alternatives, unresolved endpoints, coverage, and source linkage.
-An empty result proves absence only within the actually examined scope.
-
-## Locate the earliest unnecessary work
-
-Trace one public CLI or MCP task through shared application code to its producer.
-Measure relevant phases: admission and identity checks, native analysis,
-decoding, lookup, projection, serialization, Evidence retention, and cleanup.
-Include catalog discovery and extra calls when they affect the completed task.
-
-Use the evidence to choose the smallest structural correction:
-
-| Observed cost                     | Candidate correction                                       | Condition to establish                                                               |
-| --------------------------------- | ---------------------------------------------------------- | ------------------------------------------------------------------------------------ |
-| Repeated scans of validated facts | Reuse existing order or lookup structure                   | The owner establishes ordering and identity; every matching alternative survives     |
-| Repeated equivalent engine work   | Share a validated result or in-flight producer             | Inputs, freshness, lifetime, and per-caller outcomes remain explicit                 |
-| Full reports for selected facts   | Push selection or projection to the earliest capable owner | Required facts and evidence remain reachable; examined coverage is reported          |
-| Large temporary transport buffers | Decode incrementally or use bounded source reads           | Validate the whole admitted document; retained facts and copies still consume memory |
-| Many repeated homogeneous reads   | Share admission, decoding, or batch work                   | Preserve item identity, order where required, and individual failures                |
-
-Do not introduce an index, generic cache, batch endpoint, or orchestration layer
-without identifying the work it removes and its maintenance/resource cost.
-Projection after materializing a full report may reduce output while leaving
-analysis time and peak memory unchanged. Fix missing or incorrect facts before
-benchmarking an alternative composition against a better-covered workflow.
-
-## Keep one interpretation and a defined reuse lifetime
-
-Let the producer boundary validate and normalize facts once. Consumers query
-that representation through the shared CLI/MCP implementation; adapters should
-not rebuild relationships or independently reinterpret raw reports. Keep lookup
-identity separate from display formatting. Reuse contracts when their intent
-matches, honoring requested detail and complete Evidence access.
-
-For every cache or shared producer, state its key, owner, invalidation, retained
-size, and lifetime. Account for result-affecting target bytes, engine contents,
-analysis options, architecture/load mapping, and parser/schema versions where
-they affect reuse. Validate live state before calling a cached observation
-current. Cache a refusal only when it is deterministic for that validated key;
-malformed, partial, transient, or cancelled attempts need explicit retry policy.
-
-One cancelled waiter must not invalidate a successful peer. Preserve producer
-failure context and each caller's cancellation reason. Retain ownership and
-capacity charges until shared work and cleanup settle; preserve completed
-observations when cleanup fails. Exercise invalidation, concurrent consumers,
-last-waiter cancellation, close, and cleanup retry when those paths change.
-
-Bound the process family and retained state, not just a parent heap or worker
-count. Account for decoding and serialization expansion before allocation.
-Choose CPU, memory, concurrency, and disk limits from the host and workload;
-stop before OOM and verify owned cleanup. A guard-stopped task is incomplete.
-Do not replace a transport buffer cap with an unbounded retained inventory or
-hide partial results behind a success status.
-
-## Compare completed tasks and limit the claim
-
-Run the affected real public workflow before and after with equivalent inputs,
-results, coverage, and Evidence semantics. Include small inputs so setup costs
-and regressions are visible. Distinguish fresh sessions, warm runtime caches,
-and OS file caches. Alternate or repeat runs when variance affects the decision.
-Choose meaningful boundary regressions for cases the actual engine cannot
-reliably reproduce; a fake engine does not qualify a real provider.
-
-Report task outcome, relevant phase timings, total elapsed and CPU time, peak
-process-family memory and its accounting method, resource stops, and cleanup.
-Check the payload exit status as well as the profiler's. Keep failed attempts
-and identify unmeasured costs; a passing retry does not explain a failure.
-
-For token claims, count schemas/discovery, arguments, replies, retries, and
-continuations needed to finish the task. Label tokenizer estimates separately
-from actual model usage and record the client/catalog behavior. Smaller JSON
-alone establishes neither fewer model tokens nor better investigation quality.
-Do not claim a complex-software advantage without completed representative
-investigations and comparable correctness/coverage.
-
-Finish with the bottleneck, owning change, preserved semantics, executed
-checks, before/after measurements, and remaining limits. Keep any integration
-record current with its tested revision and distinguish merged production work
-from experiment-only code. Stop when the demonstrated bottleneck is resolved
-or further benefit remains speculative.

.agents/skills/rea-analysis-optimization/agents/openai.yaml

@@ -1,4 +0,0 @@
-interface:
-  display_name: "REA analysis optimization"
-  short_description: "Optimize analysis with preserved Evidence and measured costs"
-  default_prompt: "Use $rea-analysis-optimization to find and verify a concrete analysis bottleneck while preserving correctness and Evidence."

.agents/skills/rea-analysis-optimization/references/kuna-case-study.md

@@ -1,112 +0,0 @@
-# Kuna: reuse before adding machinery
-
-Read this reference for concrete examples of the skill's decisions. The records
-below concern static Linux analysis with caller-supplied Kuna. They do not
-establish parity with another provider or a general advantage for Code Mode,
-atomic tools, or any particular orchestration design.
-
-## Exact-address lookup: a measured, narrow improvement
-
-[PR #4695](https://github.com/morluto/rea/pull/4695) reused the validated string
-inventory's numeric address order. Previously, each `list_strings(address)`
-filtered all cached facts. The owner now performs a binary lower-bound lookup
-and returns every encoding at that address: O(log n + matches), without a
-second retained lookup index.
-
-The owning implementation is
-[`KunaStringInventory.ts`](../../../../src/kuna/KunaStringInventory.ts), consumed
-by [`KunaStringQueries.ts`](../../../../src/kuna/KunaStringQueries.ts). Inspect
-their current versions before adapting the example. Numeric u64 addresses,
-same-address encodings, duplicate rejection, source digests, caller selection,
-and the existing session lifetime were part of the contract. Full listings and
-literal/regex searches kept their semantics. An attempted removal of the
-duplicate-detection set was dropped: no stable memory benefit was established,
-and it delayed malformed-input rejection.
-
-### Recorded workload and results
-
-The benchmark used unmodified Kuna 1.833 and LLVM 16 on Linux x86-64, with
-602,544 string facts. Baseline was `be0b2d138`; the final feature was
-`5f564962da0e1b17f00a68a74a312539f0209a01`, subsequently integrated in
-`c6b62754b095a134d6d67877508fa34311a2eda2`. These are historical observations,
-not a benchmark of every subsequent main revision.
-
-The same production stdio MCP task discovered the catalog, opened the binary,
-made one cold selected read and 28 warm exact reads, checked retained Evidence,
-and closed the session. Five selected addresses and two absent selectors were
-read four times. A native filtered scan selected the strings; an independent
-ELF load-header mapping checked the source bytes and terminators. Returned
-facts, source linkage, target digests, and cleanup were checked.
-
-Three alternating fresh sessions per implementation used one CPU, a 4 GiB
-process-family hard limit, a 3 GiB early stop, and no swap. OS file caches were
-warm. Whole-harness costs include the independent native oracle, hashing,
-catalog/client work, and correctness checks.
-
-| Median                                   |     Before |      After |
-| ---------------------------------------- | ---------: | ---------: |
-| 28 warm exact MCP reads                  |   495.2 ms |    90.8 ms |
-| Cold selected MCP read                   |    11.30 s |    11.01 s |
-| Whole harness elapsed                    |    28.24 s |    27.43 s |
-| Whole process-family CPU                 |    27.71 s |    26.89 s |
-| Kernel family peak, including file cache | 2237.6 MiB | 2240.6 MiB |
-
-Warm totals ranged from 491.7–544.3 ms before to 84.8–99.5 ms after: about
-5.5 times faster at this phase. Cold/whole-task timing and memory overlapped;
-no stable improvement in those costs was established. One small SQLite pair
-(7,985 facts) measured 20 warm reads at 88.6 → 80.5 ms and the whole harness at
-13.68 → 13.94 s. The large-inventory lookup benefit does not generalize to a
-whole-task speedup on small inputs.
-
-Catalog hashes, call counts, and normalized facts were unchanged. A
-`cl100k_base` estimate over one pass of raw catalog JSON, arguments, and replies
-was about 846,000 tokens in both lanes, with about 802,562 from the catalog.
-This was transport serialization, not rendered model context or actual usage;
-client discovery, prompts, replay, and protocol framing were unmeasured.
-**No token reduction or improved agent investigation outcome was established.**
-
-Pinned target SHA-256:
-`f62d254b7f2bf42df8c8b07d46ee3bb4c2cafeca436b2e6bc6ccbe4581f58f40`.
-Pinned engine SHA-256:
-`d858918b0766435cd96b999a77f2d5a31a0cc4f07256421c883b5b9dc4dd58e4`.
-All six normalized-result sequence digests were
-`4d2f90269da8568984090b20274163c4a7c2a0538aab63530bd2fe44840a0bba`.
-Selected byte agreement does not prove native discovery completeness; missing
-strings and relationships can remain unknown.
-
-## Other transferable changes and their limits
-
-- [Cached string inventory and search, #4095](https://github.com/morluto/rea/pull/4095):
-  share validated facts across queries in a defined session. Audit key inputs
-  and lifetime before extending reuse across targets or engine revisions.
-- [Shared single-function work, #4045](https://github.com/morluto/rea/pull/4045)
-  and [repeat-request reuse, #4169](https://github.com/morluto/rea/pull/4169):
-  avoid duplicate native work while retaining per-caller cancellation and
-  cleanup ownership. A query count alone cannot reveal duplicate subprocesses.
-- [Streamed strings, #4318](https://github.com/morluto/rea/pull/4318)
-  and [streamed call graph, #4329](https://github.com/morluto/rea/pull/4329):
-  remove fixed aggregate transport-buffer failures through incremental parsing.
-  Streaming transport does not bound every retained object or final reply.
-  These links establish changes; no numerical speedup is asserted here.
-
-Typed reference facts, native string-query projection, and shared native byte
-reads remained experimental at the 2026-10-17 checkpoint
-`65f2f9a22bc892f61d2b00f9a4611124f57d4bff` on
-`experiment/atomic-codemode-20261016`. Some experiments used a patched native
-engine. Check current integration and bring-your-own engine capabilities before
-proposing them; a working experiment is not a stock-provider guarantee.
-
-## Applying the reasoning elsewhere
-
-For another provider or format, inspect its actual representation and native
-capabilities before borrowing the implementation. Existing numeric ordering
-may support range reads; an on-disk native query may avoid materializing an
-inventory; an immutable parse may support several views. Measure the relevant
-alternative rather than requiring every provider to use Kuna's cached array.
-
-For live observations, immutable artifact caching rules are insufficient:
-validate the process/session identity and freshness required by the caller.
-For compact replies, preserve access to source Evidence and report examined
-coverage; projection must not silently turn an unresolved edge into no edge.
-For batching, test mixed successes and failures and measure the entire task,
-including discovery, extra calls, native work, and serialization.

.agents/skills/rea-changelog-update/SKILL.md

@@ -6,7 +6,7 @@ description: Prepare or rewrite REA release changelogs and GitHub release notes
 # REA changelog update
 
 Use this for release-note preparation and contributor attribution. Read
-[docs/releasing.md](../../../docs/releasing.md) from the repository root for
+[docs/development/releasing.md](../../../docs/development/releasing.md) from the repository root for
 publication authority and the existing checkpoint checks. This skill prepares
 notes; it does not authorize merging, tagging, or publishing.
 
@@ -68,9 +68,9 @@ closing-issue reporters. Grouping preserves all those credits in one line.
 When Highlights, detailed entries or migrations reference the same work,
 put its thanks in one of those entries, not all of them. Include issue links.
 Direct-commit bullets carry the commit link and known human credit.
-Exclude GitHub bots and known agent accounts. REA's observed Anthropic, Cursor
-and Codex co-author trailers resolve to `@claude`, `@cursoragent` and `@codex`
-with GitHub type `User`; the credit policy excludes them while retaining their metadata.
+Exclude GitHub bots and known agent accounts. REA's observed Anthropic and
+Cursor co-author trailers resolve to `@claude` and `@cursoragent` with GitHub
+type `User`; the credit policy excludes them while retaining their metadata.
 At the REA maintainer's request, omit `@morluto` self-thanks while preserving
 authorship in the inventory. Other human contributors remain eligible.
 Use explicit GitHub links for cross-repository references to avoid ambiguous

.agents/skills/rea-ci-tests-audit/SKILL.md

@@ -9,7 +9,7 @@ Establish which checks still catch real regressions and which costs can be
 removed without losing that protection. The outcome may be a verified fix,
 an evidence-backed recommendation, or an explicit decision to stop.
 
-Follow the checkout's `AGENTS.md`, [testing guide](../../../docs/testing.md),
+Follow the checkout's `AGENTS.md`, [testing guide](../../../docs/development/testing.md),
 and [contribution rules](../../../CONTRIBUTING.md). Use their current commands
 and pinned toolchain, rather than commands remembered from an earlier audit.
 Preserve the requested scope: investigation alone does not authorize edits;

.agents/skills/rea-tool-design/SKILL.md

@@ -5,7 +5,7 @@ description: Design or change REA investigation tools, CLI/MCP contracts, provid
 
 # REA tool design
 
-Use the [tool-design guide](../../../docs/tool-design.md) for tool boundaries,
+Use the [tool-design guide](../../../docs/development/tool-design.md) for tool boundaries,
 contract semantics, provider ownership, and discoverability. Inspect the current
 contract and nearest existing tool relevant to the analyst question; source,
 documentation, and live catalogs may describe different versions.
@@ -14,7 +14,7 @@ For a design request, return the proposed boundary, input/result shape, Evidence
 semantics, nearest alternative, and verification approach. Implement when
 requested, preserving the user's scope and existing authorization.
 
-For implementation or verification, consult [testing](../../../docs/testing.md)
+For implementation or verification, consult [testing](../../../docs/development/testing.md)
 for the affected consumer and provider lanes, and
 [contributing](../../../CONTRIBUTING.md) for generated-file ownership. Read
 provider/workflow guides only as the task requires.

.agents/skills/reverse-engineer-anything/SKILL.md

@@ -2,7 +2,7 @@
 name: reverse-engineer-anything
 description: Reverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.
 metadata:
-  version: "43"
+  version: "41"
 ---
 
 # REA
@@ -31,55 +31,12 @@ Diagnose the observed blocker, continue useful supported work, and resume the
 original task after repair. Client approval, shell PATH, registration and engine
 availability have different remedies; avoid repeating setup for all of them.
 
-1. Diagnose without changing REA or client configuration. `npx` may download
-   the package and write to npm's cache. For Codex, run
-   `npx -y rea-agents@latest doctor --client codex --json`. Substitute the current
-   supported client: `claude_code`, `claude_desktop`, `codex`, `cursor`,
-   `gemini_cli`, `windsurf`, `devin`, `opencode`, `antigravity`, `copilot_cli`,
-   `commandcode`, `vscode`, `grok_build`, `omp`, or `grok_bot`. `grok_bot` has no local
-   file registration: doctor reports the Grok Bot chat step, and setup does not
-   write `mcp.json`. If the client is unknown, use `doctor --json` and
-   inspect its registration results before choosing a setup scope.
-2. Distinguish the reason. Missing, malformed, or stale registration needs a
-   scoped configuration repair. An aligned registration with no tools in the
-   active session needs a restart/reconnection; doctor cannot prove that the
-   current agent has connected. A missing provider affects only tasks requiring
-   that provider: static JavaScript inspection needs neither Hopper nor Ghidra,
-   and Android inspection has separate bring-your-own JADX/Java prerequisites.
-3. For a configuration repair, prepare the read-only plan:
-   `npx -y rea-agents@latest setup --client codex --dry-run --json`.
-   Use the current client's ID, show its exact proposed paths, backups, and
-   changes, and obtain approval before setup writes configuration or installs
-   Hopper. Setup normally installs the matching bundled skill too; include that
-   replacement in the reviewed plan. After approval, apply the same scope with
-   `npx -y rea-agents@latest setup --client codex --yes`. Add `--install-hopper`
-   only if that separate installation was needed and explicitly approved.
-4. Restart/reconnect the affected agent. Verify that REA tools actually appear
-   in the session, then resume the original investigation. If they remain
-   absent, inspect the client's MCP launch error rather than repeating setup.
-
-REA setup never installs or upgrades Node.js, npm, Homebrew, Java, Ghidra, IDA,
-JADX, Kuna, Binwalk, or Unblob. Use existing prerequisites; do not install unrelated
-software to repair
-MCP registration. For an unsupported client, use manual stdio registration
-with a version-pinned `rea-agents` package or continue through the CLI.
-
-A concrete CLI fallback for an operator-supplied JavaScript tree or ASAR is:
-
-```bash
-npx -y rea-agents@latest analyze-javascript-application /absolute/path/to/app --json
-```
-
-No MCP registration or native engine is required. Read the returned Evidence,
-graph, limitations, and unknowns with the same care as an MCP result; the CLI
-returns the Evidence record directly. This fallback does not establish that
-MCP is configured. Native CLI tasks still require their selected engine.
 Prefer an existing `rea` CLI. When none is installed and REA package acquisition
 is within the authorized scope, use `npx -y rea-agents@latest` in its place.
 Configuration repair starts with a read-only setup plan; show paths, backups and
 skill replacement before applying authorized changes. Preserve existing approval
 and target-execution boundaries. REA setup never installs or upgrades unrelated
-software, including Node.js, npm, Homebrew, Java, Ghidra, IDA, JADX, Kuna, Binwalk or Unblob.
+software, including Node.js, npm, Homebrew, Java, Ghidra, IDA, JADX, Binwalk or Unblob.
 
 ## Route the target first
 
@@ -99,15 +56,11 @@ explicit path or endpoint and do not need it.
 - Firmware image: `inspect_firmware_regions` when advertised. Use
   `extract_firmware` when extraction is requested, with a caller-selected new
   absolute output directory. These tools use caller-supplied Binwalk/Unblob on
-  Linux; see the [firmware guide](https://github.com/morluto/rea/blob/main/docs/firmware-analysis.md).
+  Linux; see the [firmware guide](https://github.com/morluto/rea/blob/main/docs/guides/firmware/firmware-analysis.md).
 - .NET NativeAOT PE/ELF: native Ghidra analysis. Native code can yield pseudocode;
   consult the NativeAOT workflow in `references/native-and-artifacts.md` for
   optional metadata recovery and its supported host/layout boundary.
 - User-owned browser page already open: `list_browser_targets`.
-- Browser action the agent must perform (click, type, navigate):
-  `capture_browser_scenario` with declared actions. See
-  [runtime observation](references/runtime-observation.md) for connect/launch
-  and the focused follow-up browser tools.
 - Fiddler Everywhere traffic or a native `.saz` capture: read the
   [Fiddler workflow](references/runtime-observation.md#fiddler-everywhere-traffic-debugging).
   Inspect saved SAZ with `inspect_web_network_capture` and `format: "saz"`;
@@ -115,20 +68,20 @@ explicit path or endpoint and do not need it.
 - Retained HAR/SAZ/native mitmproxy/aioquic qlog capture: `inspect_web_network_capture`. Select
   original record ordinals when useful; inspect producer fields and byte/number
   sidecars without fetching recorded URLs or claiming live attribution. See
-  [historical captures](https://github.com/morluto/rea/blob/main/docs/web-network-captures.md) for the exact upstream
+  [historical captures](https://github.com/morluto/rea/blob/main/docs/guides/web/web-network-captures.md) for the exact upstream
   profile and credential exclusions. Qlog support starts with aioquic 1.5.0
   JSON 0.3; stream coverage and endpoint loss declarations do not recover bodies
   or establish network loss. Prefer detail summary, then kind qlog trace/stream
   pages; select one trace, stream ID and direction for contribution/range pages.
   Facts retain all-recorded-events-before-selection scope. Other qlog layouts
   and PCAP correlation are unsupported.
-- User-owned Electron runtime already open: `list_electron_targets`. Before an electron-main Inspector attempt, check packaged fuses with `inspect_electron_fuses`; disabled `EnableNodeCliInspectArguments` means the app ignores `--inspect`.
+- User-owned Electron runtime already open: `list_electron_targets`.
 - Packet-field discovery: `inspect_packet_fields` searches installed protocols
   and field names/types before choosing fields for `inspect_packet_capture`.
   Query/page the relevant records; registrations do not establish observed traffic.
 - Recorded packet captures: `inspect_packet_capture` with selected TShark fields,
   display filters and decode-as rules. Requires Linux, util-linux prlimit and `REA_TSHARK_COMMAND`; see
-  [capture guide](https://github.com/morluto/rea/blob/main/docs/packet-captures.md).
+  [capture guide](https://github.com/morluto/rea/blob/main/docs/guides/data/packet-captures.md).
   Packet limits count input packets before filtering. Output defaults to 50 matching
   frames; use `match_offset` / `match_limit` for later pages, or explicit null
   limit for complete matching output. Preserve the source digest across pages.
@@ -136,7 +89,7 @@ explicit path or endpoint and do not need it.
   For address/DNS/SNI/protocol summaries use `inspect_pcap_capture` with MCP
   detail summary, then retained kind pcap pages. Requires Wireshark 4.x tshark
   and capinfos, with Linux prlimit or Windows Job Objects; see
-  [packet summaries](https://github.com/morluto/rea/blob/main/docs/pcap-analysis.md).
+  [packet summaries](https://github.com/morluto/rea/blob/main/docs/guides/data/pcap-analysis.md).
   Select an exact DNS question for address pages; page exhaustion does not prove
   network completeness. This reads recordings and does not acquire traffic.
 - Decoder discovery: `inspect_signal_decoders` searches installed decoder IDs
@@ -144,7 +97,7 @@ explicit path or endpoint and do not need it.
   relevant details before choosing settings; this does not scan hardware.
 - Recorded logic/signal traces: `decode_signal_recording` with explicit decoder,
   channel and protocol settings. On Linux with util-linux prlimit, supply sigrok-cli 0.7.2 through
-  `REA_SIGROK_COMMAND`; see [recording guide](https://github.com/morluto/rea/blob/main/docs/signal-recordings.md).
+  `REA_SIGROK_COMMAND`; see [recording guide](https://github.com/morluto/rea/blob/main/docs/guides/signals/signal-recordings.md).
   Output defaults to 50 literal lines; select annotation classes and page with
   `line_offset` / `line_limit`, or explicit null for all remaining output.
   Window counts are display lines, not annotations or samples. Preserve source digests across pages.
@@ -153,7 +106,7 @@ explicit path or endpoint and do not need it.
   through `REA_WABT_BIN_DIRECTORY`; retain exact byte/tool identity and decoded WAT.
   Select JavaScript glue and candidate paths explicitly and preserve URL/path
   ambiguity. No implicit fetch or target execution; WAT is not original source.
-  See the [WASM guide](https://github.com/morluto/rea/blob/main/docs/wasm-artifacts.md).
+  See the [WASM guide](https://github.com/morluto/rea/blob/main/docs/guides/wasm/wasm-artifacts.md).
 - Explicit local EVM bytecode carrier: `inspect_evm_interface` with caller-selected
   `raw` or `hex` encoding. Preserve carrier/decoded digests and treat selectors,
   argument strings and mutability as inferred candidates; this performs no chain
@@ -162,32 +115,13 @@ explicit path or endpoint and do not need it.
   Evidence stays retained under its original identity. Use the returned
   `parent_evidence_id` for exact function or `bytecode_hex`/stdout/stderr pages.
   Candidate coverage does not establish interface completeness. See the
-  [EVM bytecode guide](https://github.com/morluto/rea/blob/main/docs/evm-bytecode.md).
+  [EVM bytecode guide](https://github.com/morluto/rea/blob/main/docs/guides/evm/evm-bytecode.md).
 - Embedded Go compiler, module or build-setting metadata: `inspect_go_binary`
   with the explicit local file. This built-in target-free inspection requires no
   Go installation or disassembler. Preserve raw module bytes and source ranges;
   absent metadata does not prove a binary is not Go, and unparsed text records
   remain explicit. See the
-  [Go binary guide](https://github.com/morluto/rea/blob/main/docs/go-binaries.md).
-- Unity IL2CPP names, member owners and string literals from `global-metadata.dat`:
-  `inspect_il2cpp_metadata` with the explicit local file; MCP defaults to compact
-  counts. Query sections, images, types, methods, fields, properties, events,
-  parameters or string_literals through `inspect_analysis_view`
-  with the returned `parent_evidence_id`, using exact filters, batch indices and
-  selected fields. Parameters accept `method_indices`, avoiding a scan of all
-  parameter pages. Missing collections in historical Evidence remain unknown.
-  Versions 24, 27, 29, 31 and 39; no Unity, IL2CPP
-  binary or disassembler is run. Unrecognized magic (possibly encrypted) and
-  other versions are unsupported. Optional matching `binary_path` enables static native addresses and type references; query `method_addresses` with indices or addresses/states, preserving every shared-body method and both artifact identities. Without a linked binary native counts remain unknown. Byte-pattern fallback is inferred; no runtime behavior or same-build pairing is proved. See the
-  [IL2CPP metadata guide](https://github.com/morluto/rea/blob/main/docs/il2cpp-metadata.md).
-- Embedded cargo-auditable Rust dependency metadata: `inspect_rust_binary`
-  with the explicit local ELF, PE, or thin Mach-O file. This built-in
-  target-free inspection requires no Rust installation or disassembler. Preserve
-  package order, dependency indices, and the section file range. A missing
-  `.dep-v0` section is null metadata, not proof the binary has no dependencies.
-  A rustc commit hash is an inference from a read-only `/rustc/<40-hex>/` path.
-  See the
-  [Rust binary guide](https://github.com/morluto/rea/blob/main/docs/rust-binaries.md).
+  [Go binary guide](https://github.com/morluto/rea/blob/main/docs/guides/native/go-binaries.md).
 
 - Explicit local SQLite database snapshot: `inspect_sqlite_database`. Inspect
   with Node.js 24.x >=24.15 or 26+ providing native SQLite limits. Read schema
@@ -196,17 +130,17 @@ explicit path or endpoint and do not need it.
   20 rows; request `schema_scope: "database"` for the complete stored schema. Preserve both database and existing sibling WAL identity; row samples
   report truncation and have unspecified order. Use a quiescent snapshot rather
   than assuming a live database/WAL pair was copied atomically. See the
-  [SQLite guide](https://github.com/morluto/rea/blob/main/docs/sqlite-databases.md).
+  [SQLite guide](https://github.com/morluto/rea/blob/main/docs/guides/data/sqlite-databases.md).
 - Explicit Linux ELF file for offline layout, symbols, relocations or static
   mitigation evidence: `inspect_binary_layout`. This target-free operation uses
   caller-supplied pwntools without opening a disassembler database. Preserve its
   raw locations and inference/coverage limits; see the
-  [offline binary guide](https://github.com/morluto/rea/blob/main/docs/binary-diagnostics.md).
+  [offline binary guide](https://github.com/morluto/rea/blob/main/docs/guides/native/binary-diagnostics.md).
 - Supplied Linux x86-64 ELF core: `inspect_recorded_crash`. Read every recorded
   thread, raw note and source-bound register without opening a live target.
   Historical PIDs do not select live processes. Request `include_debugger_context`
   only when core-only mapping candidates help; see the
-  [recorded crash guide](https://github.com/morluto/rea/blob/main/docs/recorded-crashes.md).
+  [recorded crash guide](https://github.com/morluto/rea/blob/main/docs/guides/native/recorded-crashes.md).
 - PE resource type/name/language trees and static icon group references:
   `inspect_pe_resources` with an explicit path. This portable operation requires
   no active target or engine; opaque payloads retain file ranges and SHA-256.
@@ -220,26 +154,12 @@ The legacy attached profile binds the already-open GUI input by SHA-256 and
 leaves its database open. The modern headless profile creates and closes an
 owned private database without saving. Installation and registration reuse
 [mrexodia/ida-pro-mcp](https://github.com/mrexodia/ida-pro-mcp); see the
-[IDA provider guide](https://github.com/morluto/rea/blob/main/docs/ida-provider.md).
+[IDA provider guide](https://github.com/morluto/rea/blob/main/docs/providers/ida-provider.md).
 Proceed directly to `analyze_function`, pseudocode, or function/string searches
 after opening; IDA does not supply `binary_overview`. Consult session availability
 when composing broader workflows. Modern direct callers and unsupported dossier
 facets remain unknown; live IDA results are not replayed from snapshots.
 
-With `REA_KUNA_COMMAND` configured, `provider_id: "kuna"` answers procedure
-lists, lookups, pseudocode, assembly and `analyze_function` from Kuna's cached
-whole-program export. Callers/callees use a separate body-free graph shared by
-the session; `xrefs` returns exact-address incoming sites and filters forwarding
-aliases. These queries and inventory lookups do not trigger a C export. Indirect
-targets remain unknown and can make relationship coverage partial. Reference
-caches expire on close; a fresh CLI process repeats the native reference walk.
-Typed references, CFG, raw-memory tools and annotations remain unsupported. A cold first
-answer can come from a single-function run (its limitations say so); assembly
-waits for the export. For pseudocode and assembly, `raw_result.source` names the
-cached `.c`/`.asm` file and byte span, which you may search directly instead of
-calling per function. See the
-[Kuna provider guide](https://github.com/morluto/rea/blob/main/docs/kuna-provider.md).
-
 If the user says only "my app" without a name, path, or target already selected
 for this task, ask which app before searching for artifacts. Paths in unrelated
 saved reports and nearby test fixtures do not select the user's target. Resolve
@@ -258,12 +178,6 @@ Provider candidate facts describe possible providers, while top-level session
 capabilities describe the current route and `analysis_provider_binding` names the
 selected provider. Do not treat those scopes as interchangeable.
 
-For a Ghidra startup timeout on a large native target, follow
-[deadline recovery](references/native-and-artifacts.md#ghidra-startup-deadline-recovery)
-before abandoning deep analysis or repeating the same cold import. The default
-330 seconds is configurable; changing the server's environment requires a new
-REA process.
-
 ## Work summary-first
 
 Start with the default result and use its inline Evidence and graph context.
@@ -358,8 +272,7 @@ as complete while required questions remain open.
   [references/javascript-applications.md](references/javascript-applications.md)
 - Android APK declarations, classes, methods, and static references:
   [references/android-applications.md](references/android-applications.md)
-- Browser/Electron observation (passive and scenario) and static/runtime
-  reconciliation:
+- Passive browser/Electron observation and static/runtime reconciliation:
   [references/runtime-observation.md](references/runtime-observation.md)
 - Evidence paging, comparisons, residual unknowns, and verification:
   [references/evidence-workflows.md](references/evidence-workflows.md)

.agents/skills/reverse-engineer-anything/references/android-applications.md

@@ -24,9 +24,7 @@ matching bundled native controls and uses an owned Job Object with bidirectional
 stdio. A full JDK, including `jdk.compiler`, is required on every host; Windows
 `JAVA_HOME` selects `bin\java.exe`. Consult the Android guide for actual host
 verification coverage. Calls use one worker and provider deadlines; optional
-`REA_JADX_HEAP_MIB` selects the JVM heap and `REA_JADX_OPERATION_TIMEOUT_MS`
-the per-operation deadline (default 120000 ms; the MCP client's tool timeout
-must also allow it). The APK is never launched,
+`REA_JADX_HEAP_MIB` selects the JVM heap. The APK is never launched,
 and no emulator is required.
 
 Manifest entries and decompiled text are static observations, not execution or

.agents/skills/reverse-engineer-anything/references/evidence-workflows.md

@@ -24,17 +24,6 @@ retain its complete source and receive that view immediately. Without that
 advertised choice, keep the existing complete call. CLI inspection returns
 portable complete Evidence; save it before projecting a selected inline view.
 
-For native procedure/name/string inventories, select `detail: "summary"` when
-the connected tool advertises it and the task needs counts or selected rows.
-Use its parent Evidence ID with
-`view: {kind: "native-inventory", offset: 0, limit: 32, fields: ["value"]}`.
-Search tools retain the existing pattern/mode/case/document selection. Omit
-`fields` for complete records; `record.address` and `source_index` remain on
-selected rows. Selecting `value` keeps its string/decoding qualifications.
-Parent Evidence ID plus source index preserves same-address
-alternatives. Follow `coverage.next_offset` only as far as the question needs;
-exhausting retained rows does not establish complete program discovery.
-
 Use `record_unknown` to track unresolved questions in the user's investigation
 and name the authority or environment still required. Supply supporting and
 contradicting evidence IDs. It updates the session registry directly.
@@ -76,21 +65,3 @@ Use `inspect_analysis_view` with `view: {kind: "api-surface"}` on retained
 method, origin and path template. Format matches are inferences, not handler
 identity or schemas. Group pages cite parent record ordinals; consult record
 coverage and exclusions before claiming completeness. No requests are replayed.
-When the connected schema advertises `include_query_parameter_names`, select
-it in the view for distinct observed names with original record ordinals. Query
-values are omitted; the names establish neither required parameters nor a
-complete server schema. Keep the original parent Evidence for exact URLs.
-
-Use `inspect_analysis_view` with `view: {kind: "environment-manifest"}` on the
-same retained HAR Evidence to project the primary origin's request lines into
-named tools with path templates, parameters, observed query names, value-free
-body shapes and record pointers for an agent environment. Opt into
-`template_rules` only when recorded identifiers need them; every template,
-parameter and merged sibling is an inference, no header, cookie or body value is
-copied, and the three stated unknowns stay unresolved.
-
-Use `view: {kind: "environment-state"}` with the manifest's `template_rules` to
-extract the data those reads observed instead: entity types and identity
-fields, entities with recorded values, documents, and per-tool render plans
-checked against the recordings. The state comes only from reads before the
-first related write; types, identity and list membership are inferences.

.agents/skills/reverse-engineer-anything/references/javascript-applications.md

@@ -6,7 +6,7 @@ For captured or bundled JavaScript that needs readable source recovery, use
 `additional_paths` when advertised, then analyze the returned `analysis_input`
 directory together. Each input retains its own snapshot, digest and byte-range
 provenance; inputs and recovered code are never executed. Recovery requires a
-caller-supplied Wakaru on Linux x64; see [the recovery guide](https://github.com/morluto/rea/blob/main/docs/javascript-recovery.md).
+caller-supplied Wakaru on Linux x64; see [the recovery guide](https://github.com/morluto/rea/blob/main/docs/guides/javascript/javascript-recovery.md).
 
 Use `analyze_javascript_application` directly on the operator-supplied ASAR or
 extracted tree. When the question concerns known source paths and the connected
@@ -94,36 +94,6 @@ recorded observations, identity, hashes, exports and source ranges; it does not
 include every child syntax observation, related edge or original source file.
 An absent item fact is not evidence of absence from the whole application.
 
-For canonical identities and retained source-range counts, use a typed reference
-page instead of reading every full item:
-
-```json
-{
-  "source": {
-    "kind": "retained-evidence",
-    "evidence_id": "ev_ACTUAL_PARENT_ID"
-  },
-  "view": {
-    "kind": "javascript",
-    "collection": "modules",
-    "projection": "references",
-    "where": { "path": "main.js", "kind": "javascript-module" },
-    "offset": 0,
-    "limit": 16
-  }
-}
-```
-
-Filters match exact retained strings; omit a filter to include all values, use
-`path: null` for unavailable paths, and `path: ""` for a recorded empty path.
-Rows preserve canonical `identity` and distinct observation support states in
-`basis`. `retained_source_range_count` counts retained source-range observations,
-not runtime imports or unique reference sites. Use a row's `node_id` with the item
-view above for exact locations and full supporting observations. Follow
-`coverage.next_offset`; page exhaustion describes matching retained rows only.
-Check `source_coverage` for source selection, partial/unknown graph coverage and
-unknown counts before drawing a negative conclusion.
-
 ## Trace only the remaining question
 
 Use `trace_application_feature` on the parent application Evidence for one
@@ -195,8 +165,7 @@ accept complete inline Evidence or
 `{"kind":"retained-evidence","evidence_id":"ev_<64 lowercase hex characters>"}`
 for their application input (`application`, or `left`/`right`). `inspect_analysis_view`
 uses the same retained-reference form in `source`, or portable inline Evidence,
-to project a summary, module page, or one module with its recorded observations.
-This notation is
+to project a summary, module page, or one module with its recorded observations. This notation is
 a template: replace it with the actual returned ID. Versions before 4.1.0 accept only full
 inline Evidence. Use the exact ID
 returned by the producer on the same MCP connection. Resolution does not run
@@ -204,15 +173,3 @@ analysis or select a provider; findings remain inline. Native observation
 arrays still take full Evidence. `close_binary` clears retained references;
 export a bundle before closing, or supply portable inline Evidence in another
 connection. A missing reference includes its ID and recovery guidance.
-
-For exact file/native metadata or processing gaps, use
-`view: {kind: "javascript-facts", where: {paths: ["package.json"]}, property_keys: ["name", "operation", "analysis_status"], limit: 32}`.
-Rows retain canonical node/observation identity and original Evidence. Paths
-match Evidence artifact-path/source-range locations; missing properties remain
-omitted and source coverage stays separate from page exhaustion. Batch paths and
-select only needed property keys; complete Evidence remains accessible by export.
-If names are unknown, opt into `include_available_property_keys: true`; it lists
-the original keys per returned observation without unselected values. Keep each
-row's node/observation identity paired when composing facts.
-These rows select application-graph observations; semantic relationships and
-semantic unknown records remain in the complete parent Evidence and trace tools.

.agents/skills/reverse-engineer-anything/references/native-and-artifacts.md

@@ -1,32 +1,5 @@
 # Native, managed, and packaged artifacts
 
-For release comparisons, export `list_procedures` Evidence from each target before
-closing it. Close clears session records: import both bundles after collecting the
-two targets, or supply portable inline Evidence. `match_native_functions` pairs unique exact names and, when supplied,
-complete observed body bytes. Reuse optional same-context `list_names`,
-`procedure_info`, `read_bytes` and existing `analyze_function` Evidence; avoid
-decompiling every function merely to match it. Its summary retains a parent for
-`inspect_analysis_view` `function-matches` collections `matches` and `functions`.
-Select columns, batch IDs and page individual facts; aliases remain unresolved.
-Unpaired observations do not prove additions/removals. Existing matched dossier
-pairs include inputs for `compare_functions`; otherwise analyze just chosen pairs.
-
-## Desktop installation directories
-
-When an installation directory is supplied and its runtime is unknown, use
-`inspect_desktop_application` with its absolute path. Default MCP summary
-delivery retains complete Evidence. Read `files`, `omissions`, `candidates`, `components` or
-`next_probes` with `inspect_analysis_view` kind `desktop-application`, selecting
-exact paths, batched file/omission IDs or families and only needed fields and pages.
-Summary `probe_issues` retains counts and bounded previews. Select files with
-`has_issues: true` and fields `path`, `read_status`, `issues` to retrieve exact
-failures directly; preview text is display data, while `file_id` selects full facts. Preserve source
-coverage, read-range identity and unknowns; directory snapshot identity is not
-a digest of every file's contents. Component path markers do not establish
-runtime presence. For compact CLI output, use
-`inspect-desktop-application PATH --detail summary --evidence_output BUNDLE`.
-See [desktop installations](https://github.com/morluto/rea/blob/main/docs/desktop-applications.md).
-
 ## Go build metadata
 
 Use `inspect_go_binary` for an explicit local ELF, PE or thin Mach-O when the
@@ -38,36 +11,6 @@ unparsed module-text line. A missing record is an unknown, not proof of a
 non-Go binary; observed metadata does not authenticate its claims. Function,
 source and type recovery remain a separate native-analysis question.
 
-## IL2CPP metadata
-
-Use `inspect_il2cpp_metadata` for an explicit local Unity `global-metadata.dat`
-(versions 24, 27, 29, 31 and 39) when the question concerns assembly images,
-names, member owners, string literals, namespaces or index ranges. No `open_binary`, Unity installation or target
-execution is required. The CLI equivalent is `inspect-il2cpp-metadata PATH`.
-MCP defaults to counts with complete retained Evidence. Query `sections`,
-`images`, `types`, `methods`, `fields`, `properties`, `events`, `parameters` or
-`string_literals` through `inspect_analysis_view`; use exact names,
-batch indices and selected fields. Row indices are scoped by artifact SHA-256
-and collection; page offsets count filtered matches. Parameters support batch
-`method_indices` to read one method's parameters directly. Historical reports
-without member collections retain unknown counts rather than empty inventories. Preserve
-artifact SHA-256 and index widths. Unrecognized magic may mean encryption and
-is unsupported, not decrypted. Linking names to `GameAssembly` or
-`UnityFramework` code addresses remains a separate native-analysis question.
-See [IL2CPP metadata](https://github.com/morluto/rea/blob/main/docs/il2cpp-metadata.md).
-
-## Rust dependency metadata
-
-Use `inspect_rust_binary` for an explicit local ELF, PE, or thin Mach-O when
-the question concerns the cargo-auditable crate list embedded in `.dep-v0`
-(Mach-O: `__DATA,.dep-v0`). No `open_binary`, Rust installation, or target
-execution is required. The CLI equivalent is `inspect-rust-binary PATH`.
-Preserve artifact SHA-256, package order, dependency indices, and the section
-file range. A missing section is null metadata, not proof the binary has no
-dependencies. An omitted package kind stays null. A rustc commit hash is
-inferred from a read-only `/rustc/<40-hex>/` path and does not by itself
-identify the compiler. See [Rust binaries](https://github.com/morluto/rea/blob/main/docs/rust-binaries.md).
-
 ## SQLite snapshots
 
 Use `inspect_sqlite_database` with an explicit local database snapshot for its
@@ -81,7 +24,7 @@ Choose `row_limit` when a finite sample is useful and keep truncation and
 unspecified row order explicit. Virtual tables, shadow tables and views are
 schema facts, not row-read targets. REA inspects private copies and leaves
 the source files untouched; obtain a coherent quiescent database/WAL snapshot
-before inspection. See [SQLite snapshots](https://github.com/morluto/rea/blob/main/docs/sqlite-databases.md).
+before inspection. See [SQLite snapshots](https://github.com/morluto/rea/blob/main/docs/guides/data/sqlite-databases.md).
 
 ## Recorded Linux crashes
 
@@ -96,7 +39,7 @@ The optional `include_debugger_context` facet adds mapping candidates through
 caller-supplied GDB/pwndbg in an owned core-only session. Display names do not
 establish current file identity; zero reported flags leave permissions unknown.
 Requested unavailable context fails with setup guidance. See
-[recorded crashes](https://github.com/morluto/rea/blob/main/docs/recorded-crashes.md)
+[recorded crashes](https://github.com/morluto/rea/blob/main/docs/guides/native/recorded-crashes.md)
 for exact upstream profiles, bounds and verification coverage.
 
 ## Offline ELF layout
@@ -169,56 +112,6 @@ operation's full ordered list. Candidate capabilities describe possible
 providers. Top-level session capabilities describe the current route, and
 `analysis_provider_binding` identifies the selected provider.
 
-## Ghidra startup deadline recovery
-
-`provider_timeout` during the first Ghidra query can cover import, auto-analysis,
-bridge startup, and readiness. The default 330,000 ms is configurable through
-`REA_GHIDRA_STARTUP_TIMEOUT_MS`; a smaller query still needs the same cold import.
-
-Preserve useful Evidence before closing the session or restarting REA. Check
-`close_binary` and resolve reported cleanup failures. Set a larger startup budget
-in the environment that launches REA, then restart REA and reconnect the MCP
-client before reopening the same target. Closing and reopening a binary in the
-existing server keeps its original configuration and starts import again.
-Environment changes in an agent's shell do not update an already running MCP
-server. If its launch configuration cannot be changed, report that constraint
-and the exact retry setting instead of claiming a fixed technical limit.
-
-The client's tool-call deadline must allow startup plus the requested query;
-server settings and progress notifications cannot override it. CLI analysis
-avoids the MCP client deadline, but retains the provider deadline. For example:
-
-```sh
-REA_GHIDRA_STARTUP_TIMEOUT_MS=1800000 rea analyze /absolute/path/to/app.exe --provider ghidra --json
-```
-
-Thirty minutes is an example budget, not a completion guarantee. Keep host CPU
-and memory controls in place. Disable specific expensive analyzers only when
-their missing coverage is acceptable and retain the resulting limitations.
-Exported C and embedded resources remain useful independent evidence, but a
-timeout does not establish complete analysis or absence of code. See the
-[deadline and client guide](https://github.com/morluto/rea/blob/main/docs/mcp-contracts.md#ghidra-first-query-deadlines-and-recovery).
-
-## Static memory and original file bytes
-
-For Ghidra, `read_bytes` reads initialized analysis memory, including loader
-fixups; it does not read a running process. Check `returned_bytes` and `complete`
-before decoding a table. An incomplete read is missing coverage, not a zero-filled
-tail. Use `list_segments` to inspect the selected block's initialization and address-space
-facts, and retain unavailable facts as unknown.
-
-Use `address_to_file_offset` to anchor one observed address to original file
-bytes. A mapping for the first address does not establish a contiguous mapping
-for an entire table, and loader fixups can make analysis bytes differ from source
-bytes. Keep source ranges and analysis-memory observations separate.
-
-A pointer table can refer to writable slots populated by a constructor rather
-than directly to immutable resources. An uninitialized block or an observed zero
-does not establish the slot's later runtime value. Follow `xrefs` and the relevant
-writer's assembly or pseudocode; distinguish recorded assignments from inferred
-execution order. Do not replace unreadable bytes with zeros or conclude that a
-resource is absent without the necessary initialization evidence.
-
 ## DOS MZ with Ghidra
 
 For an admitted DOS MZ target, use `inspect_native_load_image` to check measured
@@ -228,8 +121,10 @@ reported static image, not runtime DOS or PC-98 hardware behavior.
 
 For Ghidra decompilation, `procedure_pseudo_code` also accepts `procedure: "file-offset:0x..."`; CLI `rea decompile <path> --file-offset=0x... --provider ghidra` resolves the source byte offset internally. An unresolved 0x-prefixed numeric procedure selector also falls back to a unique file mapping. Existing symbols and analysis addresses win; multiple mappings fail as ambiguous. Preserve the returned file-offset and address locations and raw selection observations. ELF virtual addresses are distinct from file offsets; never assume an arbitrary offset plus image base is an analysis address.
 
-Complete function body ranges use inclusive ends and can contain gaps. Do not
-treat the enclosing span as code.
+Use `read_bytes` for initialized analysis memory and `address_to_file_offset` to
+anchor one observed address to original file bytes. Loader fixups can change a
+word; a source offset does not imply byte equality. Complete function body ranges
+use inclusive ends and can contain gaps. Do not treat the enclosing span as code.
 For packed targets, retain the original and separately derived artifact identities;
 decompiling an unpacking stub does not recover the unpacked program.
 
@@ -262,14 +157,6 @@ repeat parsing. Returned-row exhaustion
 does not prove complete metadata or absence under partial/unavailable coverage;
 preserve build-local tokens and their artifact/MVID scope.
 
-`inspect_managed_members` always returns the assembly-wide `member_refs`, even
-for one selected type. For questions about a selected type, select
-`detail: "summary"` with `type_names`; it returns the selection (with unmatched
-names), coverage and per-collection counts. Page rows with
-`view: {kind: "managed-members", collection: "call_edges", offset: 0, limit: 64}`
-over `types`, `exported_types`, `fields`, `methods`, `member_refs`, `call_edges`,
-`field_accesses` or `user_strings`.
-
 ### .NET NativeAOT
 
 NativeAOT binaries contain native machine code, so ordinary CIL decompilers
@@ -291,7 +178,7 @@ broader metadata recovery on Linux; it requires an explicitly configured
 NativeAOT JAR. These are separate routes. The built-in parser also runs on
 Windows Ghidra P0; read frozen literals from its report, because
 `search_strings` does not include them. See the
-[NativeAOT guide](https://github.com/morluto/rea/blob/main/docs/ghidra-nativeaot.md)
+[NativeAOT guide](https://github.com/morluto/rea/blob/main/docs/providers/ghidra-nativeaot.md)
 for setup, supported layouts, and host restrictions. Preserve binary identity
 and distinguish derived metadata from Ghidra database observations. Recovered
 types and native pseudocode are not original C# source. Windows Ghidra P0 has
@@ -320,7 +207,7 @@ every executable in the bundle. It also lists missing or weak loads and earlier
 provides them.
 
 Use `extract_artifact` when materialized files are needed. It extracts the active
-target and accepts optional `integrity_policy`; see the [MCP contracts](https://github.com/morluto/rea/blob/main/docs/mcp-contracts.md).
+target and accepts optional `integrity_policy`; see the [MCP contracts](https://github.com/morluto/rea/blob/main/docs/reference/mcp-contracts.md).
 It materializes all regular files into a fresh temporary directory chosen by
 REA. Symlinks and encrypted entries are inventory facts, not extractable files.
 The result reports the materialized directory; callers do not choose the
@@ -335,19 +222,17 @@ separate filesystem-writing operation.
 For headerless DOS COM, explicitly open with `format: "dos-com"` (CLI
 `--target-format dos-com`). Inspect the load image before trusting function
 analysis: the entry is `0x10100`, file offset zero, with imposed real-mode segment
-context. PSP/stack/device state remains unmodeled. See [DOS guide](https://github.com/morluto/rea/blob/main/docs/ghidra-dos.md).
+context. PSP/stack/device state remains unmodeled. See [DOS guide](https://github.com/morluto/rea/blob/main/docs/providers/ghidra-dos.md).
 
 For other headerless images (embedded firmware without ELF/Mach-O/PE/MZ
 headers), open with `format: "raw-binary"`, `architecture` (`x86`, `x86_64`,
-`arm`, `arm64`, `6502`, or `m68k`), and `entry_point` (`0x` hex). File offset 0 is mapped at
+`arm`, `arm64`, or `6502`), and `entry_point` (`0x` hex). File offset 0 is mapped at
 that address. Hopper and IDA refuse this interpretation; Ghidra uses
-`BinaryLoader` with a generic language: big-endian for `m68k`, little-endian
-otherwise. Big-endian ARM, Thumb-only, and Cortex-M variants are unsupported.
-`6502` selects NMOS 6502; the entry and complete file mapping must fit within
-`0x0000..0xffff`. 65C02, 65816, cartridge containers, bank switching, and mapper
-semantics are unsupported. `m68k` requires an even entry and decodes the 68040
-superset of the 68000 family; Amiga/Atari containers and vector-table entry
-discovery are unsupported. Windows Ghidra P0 admits raw images only for `6502`. See [raw binary guide](https://github.com/morluto/rea/blob/main/docs/raw-binary.md).
+`BinaryLoader` with a little-endian generic language. Big-endian, Thumb-only,
+and Cortex-M variants are unsupported. `6502` selects NMOS 6502; the entry and
+complete file mapping must fit within `0x0000..0xffff`. 65C02, 65816, cartridge
+containers, bank switching, and mapper semantics are unsupported. Windows
+Ghidra P0 admits raw images only for `6502`. See [raw binary guide](https://github.com/morluto/rea/blob/main/docs/providers/raw-binary.md).
 
 ### Function annotations in Ghidra
 
@@ -363,29 +248,10 @@ code pages, payload hashes and static icon-group references. Same-language icon
 resolution is explicit; missing references and size mismatch remain visible.
 Other payloads are opaque, and this operation does not decode images or simulate
 Windows resource loading. Consult the budgets and supported tree profile in
-[offline binary diagnostics](https://github.com/morluto/rea/blob/main/docs/binary-diagnostics.md).
+[offline binary diagnostics](https://github.com/morluto/rea/blob/main/docs/guides/native/binary-diagnostics.md).
 
 For exact core-module import/export differences, use `compare_wasm_interfaces`
 with two complete inspection Evidence records (or current-session retained
 references) and explicit scope. Preserve unknown types/duplicate names; static
 interface equality is not runtime compatibility. CLI accepts complete inline
 Evidence in `rea compare-wasm-interfaces input.json --json`.
-
-## Godot PCK
-
-For a standalone PCK, `open_binary` then `inspect_artifact` with
-`detail: "summary"` retains the complete static inventory. Use the returned
-`parent_evidence_id` with `inspect_analysis_view` inventory occurrences filtered
-by exact `logical_paths` or `occurrence_ids`, and join `artifact_id` to nodes
-filtered by `artifact_ids`. Select only needed fields; identity links remain.
-Prefer `inspect-artifact --detail summary --evidence_output PATH` for CLI tasks;
-the same CLI discovers embedded packs via their EOF trailer without opening a
-native analysis provider. Normal native opening remains unchanged.
-
-Distinguish declared MD5 from observed SHA-256 and graph/page completeness from
-`source_coverage`. Encrypted directories and sparse bundles have unknown entry
-coverage; encrypted members have unknown content identity. An empty filtered
-page cannot prove absence in unknown coverage. Retained views are historical,
-not fresh filesystem checks. No decryption, Godot resource decoding, GDScript
-decompilation or target execution is provided. See
-[Godot PCK](https://github.com/morluto/rea/blob/main/docs/godot-pck.md).

.agents/skills/reverse-engineer-anything/references/runtime-observation.md

@@ -1,4 +1,4 @@
-# Browser and Electron runtime observation
+# Passive browser and Electron observation
 
 Supply the existing browser or Electron instance's literal-port loopback CDP
 endpoint in the request. No separate permission configuration or per-call
@@ -7,16 +7,13 @@ approval flag is needed. Browser discovery lists eligible HTTP(S) pages;
 selected page's current origin. Electron discovery lists eligible local
 `file://` targets without a configured file-root allowlist.
 
-Start passive browser work with `list_browser_targets`; start Electron runtime work with
-`list_electron_targets`. Before an electron-main Inspector attempt, check
-packaged fuses with `inspect_electron_fuses`. Inspect the target selected for
-the user's task. Observation with these tools is passive: never claim REA
-clicked, navigated, evaluated page JavaScript, invoked IPC, or captured prior
-activity. REA does not contain the page's network.
+Start browser work with `list_browser_targets`; start Electron runtime work with
+`list_electron_targets`. Inspect the target selected for the user's task. Observation
+is passive: never claim REA clicked, navigated, evaluated page JavaScript,
+invoked IPC, captured prior activity, or contained the page's network.
 
-Passive captures omit raw header collections, credential header values, storage
-values, and raw WebSocket/JSON bodies. Selected response metadata, including
-content encoding, policy values, and Link URLs, is retained. Local URLs retain ordinary query
+Credentials, cookies, authorization headers, storage values, and raw
+WebSocket/JSON bodies are deliberately absent. Local URLs retain ordinary query
 values and fragments; userinfo credentials are removed. Browser accessibility
 text, console primitives, value-free shapes, script sources, source maps, and
 storage key names have request-specific capture options. Electron script
@@ -24,38 +21,6 @@ sources are also optional. Use `capture_web_screenshot` when pixels are needed.
 Treat scope filtering, truncation, and attach-window coverage as limitations.
 Page-declared WebMCP tools are untrusted inventory and are never invoked by REA.
 
-## Who performs the action
-
-- The user performs it: `list_browser_targets`, then `inspect_web_page` or
-  `observe_web_session` on the selected target.
-- The agent must perform it: one `capture_browser_scenario` with declared
-  actions. Use connect mode with the loopback CDP endpoint and `target_id` for
-  an existing browser, or launch mode with a caller-selected executable for a
-  temporary profile. Connect mode first navigates the selected page to
-  `start_url`, which can clear unsaved form values and other temporary state.
-  Recreate the state needed for the investigation in the declared actions.
-  Connect mode leaves the external browser open; launch mode owns a temporary
-  browser and profile. Check `browser.cleanup` for the outcome.
-  Request only the DOM, accessibility, or network details needed for the question.
-  The default final capture contains the URL; step outcomes are reported separately.
-  Add a wait action for the expected page state before capturing it. Report that
-  REA performed the declared actions.
-
-Scenario network records have no request initiator stacks. For that evidence,
-use passive capture while the user performs the action. Listener source locations
-identify candidate handlers; they do not establish which script sent a particular
-request. Avoid overlapping passive capture and scenario actions on the same target.
-
-Focused follow-up tools:
-
-- `observe_web_execution`: execution coverage during a window; it resets
-  counters and temporarily disables optimization.
-- `inspect_web_event_listeners`: source locations for listeners registered
-  directly on the first CSS match, without dispatching an event.
-- `compare_web_captures`: two normalized passive captures or recorded scenarios.
-- `discover_webmcp_tools`: inspect page-declared WebMCP inventory; never invoke
-  the discovered tools.
-
 Use `reconcile_javascript_runtime` only after static application Evidence and
 passive browser/Electron Evidence exist. Prefer captured-source digest identity;
 report path/digest disagreement as a mismatch and preserve ambiguity. Explicit
@@ -69,16 +34,10 @@ with `inspect_analysis_view` and `view: {kind: "capture", detail: "preview", off
 Select complete record pages only for needed headers, metadata or payloads; views
 read the historical parent without repeating capture decoding.
 
-For selected protobuf/gRPC bodies, keep raw bytes as the source and use
-`inspect_analysis_view` kind `protobuf`, collection `bodies`, `frames` or
-`fields`. Batch exact record ordinals and field numbers/IDs, and select
-`schema_value` or `text` only when needed. Supply a local descriptor set and
-message type for schema interpretation; compressed payloads remain unknown.
-
 Inspect native `.saz` snapshots with `inspect_web_network_capture` and
 `format: "saz"`; encrypted archives are unsupported. For live
 traffic analysis, connect Everywhere's separate MCP server and use its
 advertised session tools with an explicit `sessionsSource` (`LiveTraffic` or
 `AgentCalls`). Preserve existing sessions and filters when inspecting a
-recorded run. See the [capture and MCP guide](https://github.com/morluto/rea/blob/main/docs/web-network-captures.md)
+recorded run. See the [capture and MCP guide](https://github.com/morluto/rea/blob/main/docs/guides/web/web-network-captures.md)
 for the workflow and Telerik's public setup and traffic-debugging skills.

.github/ISSUE_TEMPLATE/bug_report.yml

@@ -1,5 +1,5 @@
 name: Bug report
-description: Report a problem in REA with observations or source evidence
+description: Report a reproducible problem in REA
 title: "[Bug] "
 labels:
   - bug
@@ -8,12 +8,8 @@ body:
   - type: markdown
     attributes:
       value: |
-        Report one primary behavior per issue. Keep answers concise and grounded
-        in available evidence. Distinguish observed behavior, source-derived
-        reasoning, and suspected causes; do not claim a reproduction you did not run.
-        If a narrative answer is not known, write `NOT_ENOUGH_INFO` and describe
-        what is missing. Intermittent failures and clearly labeled source-only
-        reports are welcome. Do not include credentials or sensitive target data.
+        Please report one primary behavior per issue. Keep observed behavior
+        separate from suspected causes, and remove credentials and private paths.
 
   - type: checkboxes
     id: before-submitting
@@ -46,7 +42,7 @@ body:
     id: observed-behavior
     attributes:
       label: Observed behavior
-      description: Describe the actual result, including the exact command or MCP request, relevant provider/target, and supporting evidence below. Label source-only findings instead of claiming execution.
+      description: What happened? Include the command, MCP tool, provider, target type, and conditions that matter.
     validations:
       required: true
 
@@ -54,7 +50,7 @@ body:
     id: reproduction
     attributes:
       label: Reproduction
-      description: Give the shortest steps you actually ran, with the relevant input or configuration. State how often they reproduced the problem when known. If reproduction is unavailable, say so and provide the observations or source reference you have.
+      description: Give the smallest realistic command, configuration, input, or event sequence that demonstrates the problem.
       placeholder: |
         1. Configure or start ...
         2. Run ...
@@ -66,7 +62,7 @@ body:
     id: expected-behavior
     attributes:
       label: Expected behavior
-      description: State the expected result, contract, or recovery action. Cite documentation, source, or a known-good version when available; mark an unverified expectation or unknown reference clearly.
+      description: What result, contract, invariant, recovery action, or state transition should have occurred?
     validations:
       required: true
 
@@ -74,7 +70,7 @@ body:
     id: impact-scope
     attributes:
       label: Impact and scope
-      description: Describe observed impact and frequency, including effects on evidence integrity, process isolation, compatibility, or recovery when known. Leave untested scope and severity unknown rather than guessing.
+      description: What is affected, what is not affected, and does this affect evidence integrity, process isolation, compatibility, or recovery?
     validations:
       required: true
 
@@ -83,7 +79,7 @@ body:
     attributes:
       label: REA version
       description: Use `rea --version` or provide the source revision.
-      placeholder: Exact rea --version output or source commit SHA
+      placeholder: 3.1.0 or git revision
     validations:
       required: true
 
@@ -120,7 +116,7 @@ body:
     id: failure-stage
     attributes:
       label: Earliest failure stage
-      description: Select where the incorrect behavior first becomes observable. Choose Unknown if this has not been established.
+      description: Select where the incorrect behavior first becomes observable.
       options:
         - Request parsing or validation
         - Setup or provider admission
@@ -137,14 +133,8 @@ body:
     id: relevant-evidence
     attributes:
       label: Relevant output or evidence
-      description: Include the smallest useful output, MCP result, error, screenshot, artifact, or exact source reference. Say how it was obtained and which claim it supports. If unavailable, write NOT_ENOUGH_INFO and explain what is missing. Redact credentials and sensitive target data.
-      placeholder: |
-        Command or MCP request actually run:
-        Relevant result, error, or artifact:
-        For source-only findings, link the file/revision and relevant code:
-        Missing evidence or remaining uncertainty:
-    validations:
-      required: true
+      description: Paste the smallest useful CLI output, MCP result, error, trace, or evidence excerpt. Redact sensitive values.
+      render: text
 
   - type: textarea
     id: typed-outcome
@@ -156,10 +146,10 @@ body:
     id: analysis
     attributes:
       label: Analysis or suspected cause
-      description: Optional. Link supporting source and distinguish source-derived reasoning from a hypothesis. A root-cause analysis or proposed fix is not required.
+      description: Optional. Clearly mark source-derived reasoning or a hypothesis; do not present an unverified cause as fact.
 
   - type: textarea
     id: additional-context
     attributes:
       label: Additional context
-      description: Add reduced fixtures, screenshots, or related issues. For observed regressions, include the last known good and first known bad versions when available. Label untested checks as proposals.
+      description: Add links, reduced fixtures, screenshots, or a proposed regression test.

.github/ISSUE_TEMPLATE/design_discussion.yml

@@ -41,7 +41,7 @@ body:
     id: context-evidence
     attributes:
       label: Context and evidence
-      description: Explain the problem or motivation and link relevant evidence when available. Distinguish observed behavior, source-derived reasoning, proposed behavior, and unknowns. A question without measurements or a finished design is welcome.
+      description: Explain the problem or motivation. If you have evidence, distinguish observed behavior from ideas or guesses.
     validations:
       required: true
 

.github/ISSUE_TEMPLATE/documentation.yml

@@ -5,13 +5,6 @@ labels:
   - documentation
   - triage
 body:
-  - type: markdown
-    attributes:
-      value: |
-        Report one documentation problem with the exact location and the smallest
-        useful supporting passage, example, or result. Keep answers concise.
-        If something is unknown, write `NOT_ENOUGH_INFO` and explain what is missing.
-
   - type: checkboxes
     id: before-submitting
     attributes:
@@ -27,7 +20,7 @@ body:
     attributes:
       label: Documentation location
       description: Link the page, section, command, API, skill, or inline comment.
-      placeholder: README.md#quick-start or docs/mcp-contracts.md
+      placeholder: README.md#quick-start or docs/reference/mcp-contracts.md
     validations:
       required: true
 
@@ -35,7 +28,7 @@ body:
     id: problem
     attributes:
       label: Problem
-      description: Quote or describe the current content, explain what is unclear, missing, outdated, or incorrect, and say how to observe the problem. State who is affected when known.
+      description: What is unclear, missing, outdated, or incorrect, and who is affected?
     validations:
       required: true
 
@@ -43,7 +36,7 @@ body:
     id: expected-content
     attributes:
       label: Expected content
-      description: Describe the accurate behavior or example that should be documented, with a reference when available. Label a proposed clarification or unknown behavior clearly.
+      description: Describe the accurate behavior or example that should be documented.
     validations:
       required: true
 
@@ -51,9 +44,7 @@ body:
     id: evidence
     attributes:
       label: Supporting evidence
-      description: Include an exact passage, source reference, command output, provider documentation, or screenshot supporting the report. For missing or unclear guidance, point to the relevant section and explain the gap. If evidence is unavailable, write NOT_ENOUGH_INFO and explain what is missing.
-    validations:
-      required: true
+      description: Add source, command output, provider documentation, or a link that supports the correction.
 
   - type: textarea
     id: additional-context

.github/ISSUE_TEMPLATE/feature_request.yml

@@ -11,8 +11,6 @@ body:
         Describe one problem and the outcome you would like. Short answers are
         welcome. Choose "Not sure yet" wherever needed; you do not need code, a
         finished design, or a complete test plan to propose an idea.
-        Use concrete examples when available, distinguish current limitations
-        from proposed behavior, and leave unmeasured impact or unknowns explicit.
 
         Read the [contribution scope](https://github.com/morluto/rea/blob/main/CONTRIBUTING.md#contribution-scope).
         Maintainers can help resolve scope and technical questions. Unresolved
@@ -60,7 +58,7 @@ body:
     id: use-cases
     attributes:
       label: Use cases
-      description: Optional examples of affected workflows, targets, or callers and their practical impact. Include observed frequency or measurements when available; do not invent them. Leave blank if covered above.
+      description: Optional additional examples of applications, targets, or callers. Leave blank if covered above.
 
   - type: textarea
     id: desired-outcome
@@ -140,4 +138,4 @@ body:
     id: references
     attributes:
       label: References
-      description: Optional supporting examples, provider documentation, source, measurements, artifacts, issues, or prior art. Distinguish observed results from expected benefits; an idea without evidence is welcome.
+      description: Link relevant provider documentation, source, measurements, artifacts, issues, or discussions.

.github/actions/npm-cache/action.yml

@@ -1,42 +0,0 @@
-name: Cache npm package downloads
-description: Restore npm's download cache and save it only from trusted default-branch events.
-outputs:
-  can-save:
-    description: Whether this run may update the shared npm download cache.
-    value: ${{ steps.context.outputs.can-save }}
-  path:
-    description: The npm download-cache directory.
-    value: ${{ steps.context.outputs.path }}
-runs:
-  using: composite
-  steps:
-    - id: context
-      shell: bash
-      env:
-        DEFAULT_BRANCH: ${{ github.event.repository.default_branch }}
-        LOCKFILES_HASH: ${{ hashFiles('package-lock.json', 'npm-shrinkwrap.json', '.npmrc') }}
-      run: |
-        cache_path="$(npm config get cache)"
-        runtime_arch="$(node -p 'process.arch')"
-        can_save=false
-        if [[ -n "${DEFAULT_BRANCH}" && "${GITHUB_REF}" == "refs/heads/${DEFAULT_BRANCH}" && ( "${GITHUB_EVENT_NAME}" == "push" || "${GITHUB_EVENT_NAME}" == "schedule" || "${GITHUB_EVENT_NAME}" == "workflow_dispatch" ) ]]; then
-          can_save=true
-        fi
-        cache_key="npm-download-${RUNNER_OS}-${runtime_arch}-${LOCKFILES_HASH}"
-        {
-          printf 'can-save=%s\n' "${can_save}"
-          printf 'path=%s\n' "${cache_path}"
-          printf 'key=%s\n' "${cache_key}"
-        } >> "${GITHUB_OUTPUT}"
-    - name: Restore and save npm package downloads
-      if: steps.context.outputs.can-save == 'true'
-      uses: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830 # v4.3.0
-      with:
-        path: ${{ steps.context.outputs.path }}
-        key: ${{ steps.context.outputs.key }}
-    - name: Restore npm package downloads without saving
-      if: steps.context.outputs.can-save != 'true'
-      uses: actions/cache/restore@0057852bfaa89a56745cba8c7296529d2fc39830 # v4.3.0
-      with:
-        path: ${{ steps.context.outputs.path }}
-        key: ${{ steps.context.outputs.key }}

.github/actions/portable-build-cache/action.yml

@@ -24,7 +24,19 @@ runs:
         BUILD_CACHE_PREFIX: rea-portable-build-v2-${{ runner.os }}-${{ runner.arch }}-${{ hashFiles('.npmrc', '.nvmrc', 'package-lock.json') }}
       run: |
         npm run --silent test:prepare -- --dry=json |
-          node scripts/ci/portable-build-cache.mjs key >> "$GITHUB_OUTPUT"
+          node --input-type=module -e '
+            import { createHash } from "node:crypto";
+            import { readFileSync } from "node:fs";
+            const { tasks } = JSON.parse(readFileSync(0, "utf8"));
+            const hashes = tasks.map(({ taskId, hash }) => {
+              if (typeof hash !== "string")
+                throw new Error(`Build task ${taskId} must have an eager Turbo hash`);
+              return `${taskId}:${hash}`;
+            }).sort();
+            const hash = createHash("sha256").update(hashes.join("\n")).digest("hex");
+            console.log(`key=${process.env.BUILD_CACHE_PREFIX}-${hash}`);
+            console.log(`prefix=${process.env.BUILD_CACHE_PREFIX}-`);
+          ' >> "$GITHUB_OUTPUT"
     - name: Restore portable build outputs
       if: inputs.build_cache_artifact == '' && inputs.save != 'true'
       uses: actions/cache/restore@0057852bfaa89a56745cba8c7296529d2fc39830 # v4.3.0

.github/actions/prepare-release-package/action.yml

@@ -1,26 +0,0 @@
-name: Prepare qualified release inputs
-description: Restore and validate the exact qualified tarball and its verifier runtime
-outputs:
-  version:
-    description: Package version validated against the source and qualified manifest
-    value: ${{ steps.package.outputs.version }}
-  tarball:
-    description: Absolute path to the validated qualified npm tarball
-    value: ${{ steps.package.outputs.tarball }}
-runs:
-  using: composite
-  steps:
-    - name: Download the exact qualified package
-      uses: actions/download-artifact@d3f86a106a0bac45b974a628896c90dbdf5c8093 # v4.3.0
-      with:
-        name: verified-release-package
-        path: .cache/verified-package/
-    - name: Verify qualified package provenance and digest
-      id: package
-      shell: bash
-      run: node scripts/ci/verified-package.mjs validate .cache/verified-package
-    - name: Restore qualified verifier runtime
-      uses: actions/download-artifact@d3f86a106a0bac45b974a628896c90dbdf5c8093 # v4.3.0
-      with:
-        name: rea-test-runtime
-        path: .

.github/actions/publish-mcp/action.yml

@@ -1,41 +0,0 @@
-name: Publish MCP Registry metadata
-description: Validate and publish one released server.json, preserving an identical existing version
-inputs:
-  directory:
-    description: Directory containing the released server.json
-    default: .
-runs:
-  using: composite
-  steps:
-    - name: Install MCP Registry publisher
-      shell: bash
-      working-directory: ${{ inputs.directory }}
-      env:
-        MCP_PUBLISHER_VERSION: v1.8.0
-        MCP_PUBLISHER_SHA256_LINUX_AMD64: 1370446bbe74d562608e8005a6ccce02d146a661fbd78674e11cc70b9618d6cf
-      run: |
-        archive="mcp-publisher_linux_amd64.tar.gz"
-        curl -fsSLo "${archive}" \
-          "https://github.com/modelcontextprotocol/registry/releases/download/${MCP_PUBLISHER_VERSION}/${archive}"
-        echo "${MCP_PUBLISHER_SHA256_LINUX_AMD64}  ${archive}" | sha256sum --check --strict
-        tar xzf "${archive}" mcp-publisher
-        chmod +x mcp-publisher
-    - name: Validate MCP Registry metadata
-      shell: bash
-      working-directory: ${{ inputs.directory }}
-      run: ./mcp-publisher validate
-    - name: Check existing registry version
-      id: registry
-      shell: bash
-      working-directory: ${{ inputs.directory }}
-      run: node "${GITHUB_ACTION_PATH}/registry-state.mjs"
-    - name: Authenticate to MCP Registry
-      if: steps.registry.outputs.exists != 'true'
-      shell: bash
-      working-directory: ${{ inputs.directory }}
-      run: ./mcp-publisher login github-oidc
-    - name: Publish MCP Registry metadata
-      if: steps.registry.outputs.exists != 'true'
-      shell: bash
-      working-directory: ${{ inputs.directory }}
-      run: ./mcp-publisher publish

.github/actions/publish-mcp/registry-state.d.mts

@@ -1,4 +0,0 @@
-export function registryPublicationState(
-  server: Readonly<{ name: string; version: string } & Record<string, unknown>>,
-  request?: (url: URL, init: RequestInit) => Promise<Response>,
-): Promise<"present" | "absent">;

.github/actions/publish-mcp/registry-state.mjs

@@ -1,89 +0,0 @@
-import assert from "node:assert/strict";
-import { appendFile, readFile } from "node:fs/promises";
-import { resolve } from "node:path";
-import { fileURLToPath } from "node:url";
-
-/** Exact-version routes currently return false 404s; enumerate the filtered listing. */
-export async function registryPublicationState(server, request = fetch) {
-  assert.equal(typeof server?.name, "string");
-  assert.equal(typeof server?.version, "string");
-  const cursors = new Set();
-  let cursor;
-  const matches = [];
-  do {
-    const url = new URL(
-      "https://registry.modelcontextprotocol.io/v0.1/servers",
-    );
-    url.search = new URLSearchParams({
-      search: server.name,
-      version: server.version,
-      include_deleted: "true",
-      limit: "100",
-    }).toString();
-    if (cursor !== undefined) url.searchParams.set("cursor", cursor);
-    const response = await request(url, {
-      signal: AbortSignal.timeout(30_000),
-    });
-    if (!response.ok)
-      throw new Error(`Registry lookup failed: HTTP ${response.status}`);
-    const page = await response.json();
-    assert(Array.isArray(page?.servers), "Registry response omitted servers");
-    assert(
-      page.metadata && typeof page.metadata === "object",
-      "Registry response omitted metadata",
-    );
-    for (const entry of page.servers) {
-      assert(
-        typeof entry?.server?.name === "string" &&
-          typeof entry.server.version === "string",
-        "Malformed registry server record",
-      );
-      if (
-        entry.server.name === server.name &&
-        entry.server.version === server.version
-      )
-        matches.push(entry);
-    }
-    cursor = page.metadata.nextCursor;
-    if (cursor !== undefined) {
-      assert(
-        typeof cursor === "string" && cursor.length > 0 && !cursors.has(cursor),
-        "Registry returned a non-advancing cursor",
-      );
-      cursors.add(cursor);
-    }
-  } while (cursor !== undefined);
-  assert(
-    matches.length <= 1,
-    "Registry returned ambiguous exact-version records",
-  );
-  if (matches.length === 0) return "absent";
-  assert.equal(
-    matches[0]._meta?.["io.modelcontextprotocol.registry/official"]?.status,
-    "active",
-    "Existing registry version is not active",
-  );
-  assert.deepEqual(
-    matches[0].server,
-    server,
-    "Existing registry version differs from released metadata",
-  );
-  return "present";
-}
-
-if (
-  process.argv[1] !== undefined &&
-  resolve(process.argv[1]) === fileURLToPath(import.meta.url)
-) {
-  const state = await registryPublicationState(
-    JSON.parse(await readFile("server.json", "utf8")),
-  );
-  assert(process.env.GITHUB_OUTPUT, "GITHUB_OUTPUT is required");
-  await appendFile(
-    process.env.GITHUB_OUTPUT,
-    `exists=${state === "present"}\n`,
-  );
-  process.stdout.write(
-    `Registry version is ${state}; ${state === "present" ? "preserving identical published metadata" : "publication may proceed"}.\n`,
-  );
-}

.github/pull_request_template.md

@@ -24,7 +24,7 @@ Unresolved scope, authority, side effects, or required verification block
 integration. Link the required maintainer scope decision for new providers or
 capabilities involving target execution, injection, mutation, or protection
 recovery; ordinary fixes within existing boundaries may state "not applicable".
-Draft PRs may leave the scope decision pending and the readiness and merge checklists
+Draft PRs may leave the scope decision pending and the final review checklist
 unchecked. Maintainers can help resolve open questions.
 
 ## Contract and boundary impact
@@ -55,10 +55,7 @@ Unchecked items do not establish absence; leave uncertainties visible.
 ## Evidence and regression coverage
 
 <!-- State whether evidence is executed, source-derived, or proposed. For fixes,
-show the original failure and explain how the regression would fail on the affected
-base revision when practical. Include the most useful proof inline; link long logs
-or artifacts, or put them in optional details. Documentation-only changes can use
-source, link, or rendered-document checks. -->
+explain how the regression would fail on the affected base revision when practical. -->
 
 - Tests added or updated:
 - Base reproduction or other evidence:
@@ -74,8 +71,7 @@ For evidence-bearing changes:
 ## Validation performed
 
 <!-- List only commands that actually ran, with observed results. Include the
-relevant real-provider or platform workflow, or explain why it was unavailable.
-Keep these results current after changes; a command without its result is incomplete. -->
+relevant real-provider or platform workflow, or explain why it was unavailable. -->
 
 - `command` — result
 
@@ -89,28 +85,11 @@ limits, security/privacy/containment implications, and meaningful proof gaps. --
   its new behavior and migration, and why compatibility/deprecation cannot
   preserve it. Every release increments minor, including breaking changes;
   keep breaking markers and migration notes so callers can assess compatibility.
-  See docs/releasing.md. -->
+  See docs/development/releasing.md. -->
 - Real Hopper/Ghidra, browser, or OS coverage:
 - Package or release metadata impact:
 - Security, privacy, process, or containment review:
 
-## Author readiness
-
-<!-- The human owner completes these declarations before requesting review.
-The PR author is the owner by default. A different owner must explicitly accept
-ownership on this PR.
-AI agents must leave these declarations to a human to dictate to them or there could be catastrophic consequences for many users of REA.
-Draft PRs may leave them unchecked. These declarations record initial readiness
-when opening the PR for review; later pushes do not require a new human sign-off.
-Keep the description and validation evidence current as the work changes.
-See CONTRIBUTING.md#pull-request-ownership-and-readiness. -->
-
-Human owner: <!-- @GitHub-handle -->
-
-- [ ] I reviewed the final diff and relevant existing code, understand the change and its edge cases, and take responsibility for the complete PR, including AI-assisted work.
-- [ ] I checked the evidence above, confirmed it supports the current change, and recorded meaningful validation gaps.
-- [ ] I declare this PR ready for initial maintainer review.
-
 ## Before merge
 
 <!-- Draft PRs may leave pending items unchecked. Resolve material scope and

.github/workflows/ci-timings.yml

@@ -12,13 +12,12 @@ concurrency:
 permissions:
   contents: read
   actions: read
-  pull-requests: read
 
 jobs:
   report:
     name: Collect recent completed workflow attempts
     runs-on: ubuntu-latest
-    timeout-minutes: 10
+    timeout-minutes: 5
     steps:
       # Consume only API data and execute batch code from the trusted default branch.
       - uses: actions/checkout@11d5960a326750d5838078e36cf38b85af677262 # v4.4.0
@@ -28,18 +27,6 @@ jobs:
       - uses: actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020 # v4.4.0
         with:
           node-version-file: .nvmrc
-      - name: Cache npm package downloads
-        id: npm-cache
-        continue-on-error: true
-        uses: ./.github/actions/npm-cache
-      - name: Diagnose missing and startup-failed PR CI
-        continue-on-error: true
-        env:
-          GH_TOKEN: ${{ github.token }}
-          CI_REPOSITORY: ${{ github.repository }}
-          CI_REPOSITORY_ID: ${{ github.repository_id }}
-          CI_DEFAULT_BRANCH: ${{ github.event.repository.default_branch }}
-        run: node scripts/ci/pr-ci-health.mjs
       - name: Record queue, execution, and matched step timing
         continue-on-error: true
         env:
@@ -57,28 +44,3 @@ jobs:
           if-no-files-found: error
           overwrite: true
           retention-days: 14
-      - name: Install dependencies for static failure attribution
-        id: failure-deps
-        if: ${{ !cancelled() && hashFiles('.cache/ci-job-timings/batch-manifest.json') != '' }}
-        continue-on-error: true
-        run: npm ci
-      - name: Attribute supported static failures against main
-        if: ${{ !cancelled() && steps.failure-deps.outcome == 'success' && hashFiles('.cache/ci-job-timings/batch-manifest.json') != '' }}
-        continue-on-error: true
-        env:
-          GH_TOKEN: ${{ github.token }}
-          CI_REPOSITORY: ${{ github.repository }}
-          CI_DEFAULT_BRANCH: ${{ github.event.repository.default_branch }}
-        run: node scripts/ci/failure-report.mjs
-      - name: Upload CI health and failure diagnostics
-        if: ${{ !cancelled() }}
-        continue-on-error: true
-        uses: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02 # v4.6.2
-        with:
-          name: ci-health-diagnostics
-          path: |
-            .cache/ci-pr-health/
-            .cache/ci-failures/
-          include-hidden-files: true
-          if-no-files-found: warn
-          retention-days: 14

.github/workflows/ci.yml

@@ -42,7 +42,6 @@ jobs:
       tier: ${{ steps.plan.outputs.tier }}
       qualification_run_id: ${{ steps.qualification.outputs.run_id }}
       code: ${{ steps.plan.outputs.code }}
-      reverse_tools: ${{ steps.plan.outputs.reverse_tools }}
       sqlite: ${{ steps.plan.outputs.sqlite }}
       runtime: ${{ steps.plan.outputs.runtime }}
       package: ${{ steps.plan.outputs.package }}
@@ -59,9 +58,7 @@ jobs:
       web_network: ${{ steps.plan.outputs.web_network }}
       web_runtime: ${{ steps.plan.outputs.web_runtime }}
       web_source_map: ${{ steps.plan.outputs.web_source_map }}
-      agentenv: ${{ steps.plan.outputs.agentenv }}
       nativeaot: ${{ steps.plan.outputs.nativeaot }}
-      ghidra_bridge: ${{ steps.plan.outputs.ghidra_bridge }}
       website: ${{ steps.plan.outputs.website }}
       matrix: ${{ steps.plan.outputs.matrix }}
       test_selection: ${{ steps.plan.outputs.test_selection }}
@@ -125,33 +122,11 @@ jobs:
       - uses: actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020 # v4.4.0
         with:
           node-version-file: .nvmrc
-      - name: Cache npm package downloads
-        id: npm-cache
-        uses: ./.github/actions/npm-cache
+          cache: npm
       - run: npm ci
-      - name: Restore static task cache
-        if: needs.changes.outputs.code == 'true'
-        id: static-cache
-        uses: actions/cache/restore@0057852bfaa89a56745cba8c7296529d2fc39830 # v4.3.0
-        with:
-          path: .turbo/cache/
-          key: rea-static-v1-${{ runner.os }}-${{ runner.arch }}-${{ hashFiles('.nvmrc', '.npmrc', 'package-lock.json') }}-${{ github.sha }}
-          # Turbo validates each task's inputs after restoring this snapshot.
-          restore-keys: rea-static-v1-${{ runner.os }}-${{ runner.arch }}-${{ hashFiles('.nvmrc', '.npmrc', 'package-lock.json') }}-
       - name: Validate workflow syntax and expressions
         if: needs.changes.outputs.workflows == 'true'
         run: go run github.com/rhysd/actionlint/cmd/actionlint@v1.7.7 -shellcheck= -pyflakes=
-      # Code tiers run this source-only policy test in their existing shards.
-      # Workflow-only changes need the guard, without preparing runtime artifacts.
-      - name: Check action pins for workflow-only changes
-        if: needs.changes.outputs.workflows == 'true' && needs.changes.outputs.code != 'true'
-        run: node scripts/run-exact-tests.mjs run tests/boundary/filesystem/workflowActionPinning.test.ts
-      - name: Record static task source and execution identity
-        continue-on-error: true
-        if: needs.changes.outputs.code == 'true'
-        env:
-          CI_PR_HEAD_SHA: ${{ github.event.pull_request.head.sha }}
-        run: npm run ci:static-context
       - if: needs.changes.outputs.code == 'true'
         run: npm run check:ci
       - if: needs.changes.outputs.code == 'true'
@@ -161,15 +136,6 @@ jobs:
         run: npm run test:python
       - if: needs.changes.outputs.code != 'true'
         run: npm run format:check
-      - name: Save validated static task cache
-        if: >-
-          success() && needs.changes.outputs.code == 'true' &&
-          steps.npm-cache.outputs.can-save == 'true' &&
-          steps.static-cache.outputs.cache-hit != 'true'
-        uses: actions/cache/save@0057852bfaa89a56745cba8c7296529d2fc39830 # v4.3.0
-        with:
-          path: .turbo/cache/
-          key: ${{ steps.static-cache.outputs.cache-primary-key }}
       - name: Upload complete static diagnostics
         if: always() && needs.changes.outputs.code == 'true'
         uses: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02 # v4.6.2
@@ -180,34 +146,6 @@ jobs:
           if-no-files-found: ignore
           retention-days: 7
 
-  test-source:
-    name: Source tests
-    needs: changes
-    if: needs.changes.outputs.code == 'true' && needs.changes.outputs.tier == 'fast'
-    runs-on: ubuntu-latest
-    timeout-minutes: 10
-    steps:
-      - uses: actions/checkout@11d5960a326750d5838078e36cf38b85af677262 # v4.4.0
-      - uses: actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020 # v4.4.0
-        with:
-          node-version-file: .nvmrc
-      - name: Cache npm package downloads
-        id: npm-cache
-        uses: ./.github/actions/npm-cache
-      - run: npm ci
-      - name: Run source tests without waiting for build
-        run: npm run test:fast -- --reporter=default --reporter=blob
-        env:
-          VITEST_BLOB_LABEL: source
-      - uses: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02 # v4.6.2
-        if: ${{ !cancelled() }}
-        with:
-          name: vitest-report-source
-          path: .vitest/blob/*
-          include-hidden-files: true
-          if-no-files-found: error
-          retention-days: 7
-
   test-shard:
     name: Test shard (${{ matrix.shard }})
     needs: [changes, build]
@@ -215,21 +153,15 @@ jobs:
     runs-on: ubuntu-latest
     timeout-minutes: 30
     strategy:
-      # Failed PRs release the remaining matrix slots; qualification retains
-      # every shard's diagnostics and coverage. Passing PRs run the full suite.
-      fail-fast: ${{ github.event_name == 'pull_request' && needs.changes.outputs.tier == 'fast' }}
+      fail-fast: false
       matrix:
-        # Fast feedback spends the same six test jobs on one source group and
-        # five built groups; full qualification retains six complete shards.
-        shard: ${{ fromJSON(needs.changes.outputs.tier == 'fast' && '["1/5","2/5","3/5","4/5","5/5"]' || '["1/6","2/6","3/6","4/6","5/6","6/6"]') }}
+        shard: [1/6, 2/6, 3/6, 4/6, 5/6, 6/6]
     steps:
       - uses: actions/checkout@11d5960a326750d5838078e36cf38b85af677262 # v4.4.0
       - uses: actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020 # v4.4.0
         with:
           node-version-file: .nvmrc
-      - name: Cache npm package downloads
-        id: npm-cache
-        uses: ./.github/actions/npm-cache
+          cache: npm
       - run: npm ci
       - uses: actions/download-artifact@d3f86a106a0bac45b974a628896c90dbdf5c8093 # v4.3.0
         with:
@@ -240,55 +172,21 @@ jobs:
         run: npm run test:ci:shard:run -- --shard=${{ matrix.shard }}
         env:
           REA_CI_TEST_HISTORY: .cache/ci-test-history/test-results.json
-      - name: Run built-dependent tests for fast feedback
+      - name: Run complete portable suite for fast feedback
         if: needs.changes.outputs.tier == 'fast'
-        run: npm run test:built -- --reporter=default --reporter=blob --shard=${{ matrix.shard }}
+        run: npm run test:run -- --reporter=default --reporter=blob --shard=${{ matrix.shard }}
         env:
-          VITEST_BLOB_LABEL: built
           REA_CI_TEST_HISTORY: .cache/ci-test-history/test-results.json
       - uses: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02 # v4.6.2
         if: ${{ !cancelled() }}
         with:
-          name: vitest-report-built-${{ strategy.job-index }}
+          name: vitest-report-${{ strategy.job-index }}
           path: .vitest/blob/*
           include-hidden-files: true
           if-no-files-found: error
           overwrite: true
           retention-days: 7
 
-  reverse-tools-quality:
-    name: Reverse tools quality
-    needs: [changes, static]
-    if: needs.changes.outputs.reverse_tools == 'true'
-    runs-on: ubuntu-latest
-    timeout-minutes: 60
-    steps:
-      - uses: actions/checkout@11d5960a326750d5838078e36cf38b85af677262 # v4.4.0
-      - uses: actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020 # v4.4.0
-        with:
-          node-version-file: .nvmrc
-      - name: Cache npm package downloads
-        id: npm-cache
-        uses: ./.github/actions/npm-cache
-      - run: npm ci
-      - name: Run reverse tools tests with coverage
-        run: npm run test:coverage:reverse-tools
-      - name: Preflight both reverse tools mutation configurations
-        run: |
-          node scripts/prepare-reverse-tools-mutation.mjs
-          npx --no-install stryker run stryker.config.mjs --dryRunOnly
-          npx --no-install stryker run stryker.semantics.config.mjs --dryRunOnly
-      - name: Retain available reverse tools diagnostics
-        if: ${{ !cancelled() }}
-        uses: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02 # v4.6.2
-        with:
-          name: reverse-tools-quality-${{ needs.changes.outputs.tier }}-${{ github.run_attempt }}
-          path: |
-            coverage/reverse-tools/
-            reports/mutation/
-          if-no-files-found: warn
-          retention-days: 7
-
   build:
     name: Build package
     needs: changes
@@ -303,8 +201,7 @@ jobs:
       needs.changes.outputs.recorded_crash == 'true' ||
       needs.changes.outputs.web_network == 'true' ||
       needs.changes.outputs.web_runtime == 'true' ||
-      needs.changes.outputs.web_source_map == 'true' ||
-      needs.changes.outputs.agentenv == 'true'
+      needs.changes.outputs.web_source_map == 'true'
     runs-on: ubuntu-latest
     timeout-minutes: 10
     permissions:
@@ -315,9 +212,7 @@ jobs:
       - uses: actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020 # v4.4.0
         with:
           node-version-file: .nvmrc
-      - name: Cache npm package downloads
-        id: npm-cache
-        uses: ./.github/actions/npm-cache
+          cache: npm
       - run: npm ci
       - name: Reuse portable build outputs across runs
         uses: ./.github/actions/portable-build-cache
@@ -359,15 +254,10 @@ jobs:
       # test:prepare caches only portable JS, skill, and catalog outputs.
       # Native package jobs still run their build and prepack checks; Turbo
       # restores matching outputs or rebuilds when their inputs differ.
-      - name: Stage current portable build task cache
-        shell: bash
-        run: |
-          # A new Turbo dry run can evict the entries this build just used.
-          node scripts/ci/portable-build-cache.mjs snapshot < .cache/ci-build-plan.json
       - uses: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02 # v4.6.2
         with:
           name: rea-build-cache
-          path: .cache/ci-build-cache/
+          path: .turbo/cache/
           include-hidden-files: true
           if-no-files-found: error
           retention-days: 7
@@ -381,7 +271,7 @@ jobs:
 
   test:
     name: Portable tests
-    needs: [changes, test-source, test-shard]
+    needs: [changes, test-shard]
     if: ${{ !cancelled() && needs.changes.outputs.tier != 'reused' }}
     runs-on: ubuntu-latest
     timeout-minutes: 10
@@ -396,18 +286,13 @@ jobs:
         if: needs.changes.outputs.code == 'true' && success()
         with:
           node-version-file: .nvmrc
-      - name: Cache npm package downloads
-        if: needs.changes.outputs.code == 'true' && success()
-        id: npm-cache
-        uses: ./.github/actions/npm-cache
+          cache: npm
       - if: needs.changes.outputs.code == 'true' && success()
         run: npm ci
       - uses: actions/download-artifact@d3f86a106a0bac45b974a628896c90dbdf5c8093 # v4.3.0
         if: >-
           !cancelled() && needs.changes.outputs.code == 'true' &&
-          (needs.test-shard.result == 'success' || needs.test-shard.result == 'failure' ||
-           (needs.changes.outputs.tier == 'fast' &&
-            (needs.test-source.result == 'success' || needs.test-source.result == 'failure')))
+          (needs.test-shard.result == 'success' || needs.test-shard.result == 'failure')
         with:
           path: .vitest/blob
           pattern: vitest-report-*
@@ -435,8 +320,7 @@ jobs:
         if: >-
           !cancelled() && needs.changes.outputs.code == 'true' &&
           needs.changes.outputs.tier == 'fast' &&
-          (needs.test-shard.result == 'success' || needs.test-shard.result == 'failure' ||
-           needs.test-source.result == 'success' || needs.test-source.result == 'failure')
+          (needs.test-shard.result == 'success' || needs.test-shard.result == 'failure')
         run: >-
           npm exec -- vitest --merge-reports
           --reporter=default
@@ -446,11 +330,9 @@ jobs:
           --outputFile.junit=test-results.xml
           --outputFile.json=test-results.json
       - name: Summarize slowest test files
-        if: needs.changes.outputs.code == 'true' && !cancelled()
+        if: needs.changes.outputs.code == 'true' && !cancelled() && hashFiles('test-timings.json') != ''
         env:
           SHARD_RESULT: ${{ needs.test-shard.result }}
-          SOURCE_REQUIRED: ${{ needs.changes.outputs.tier == 'fast' }}
-          SOURCE_RESULT: ${{ needs.test-source.result }}
           MERGE_RESULT: ${{ needs.changes.outputs.tier == 'full' && steps.merge.outcome || steps.merge-fast.outcome }}
           CI_VERIFY_TEST_INVENTORY: "true"
           CI_TEST_SELECTION: ${{ needs.changes.outputs.test_selection }}
@@ -483,13 +365,7 @@ jobs:
         env:
           CODE_REQUIRED: ${{ needs.changes.outputs.code }}
           SHARD_RESULT: ${{ needs.test-shard.result }}
-          SOURCE_REQUIRED: ${{ needs.changes.outputs.tier == 'fast' }}
-          SOURCE_RESULT: ${{ needs.test-source.result }}
-        run: |
-          if [ "${CODE_REQUIRED}" = "true" ]; then
-            test "${SHARD_RESULT}" = "success" || exit 1
-            test "${SOURCE_REQUIRED}" != "true" || test "${SOURCE_RESULT}" = "success"
-          fi
+        run: test "${CODE_REQUIRED}" != "true" || test "${SHARD_RESULT}" = "success"
 
   conformance-fixtures:
     name: Source-built conformance fixtures
@@ -574,9 +450,7 @@ jobs:
       - uses: actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020 # v4.4.0
         with:
           node-version-file: .nvmrc
-      - name: Cache npm package downloads
-        id: npm-cache
-        uses: ./.github/actions/npm-cache
+          cache: npm
       - name: Verify native runtime identity
         env:
           EXPECTED_CI_PLATFORM: ${{ matrix.platform }}
@@ -598,6 +472,11 @@ jobs:
       - run: npm run verify:windows-native:artifact
       - name: Verify NativeAOT diagnostic applicability on this host
         run: npm run test:focused -- tests/evaluation/package/nativeAotDiagnostics.test.ts
+      - name: Resolve npm cache before verifier HOME isolation
+        id: npm-cache
+        run: |
+          cache_path="$(npm config get cache)"
+          echo "path=${cache_path}" >> "${GITHUB_OUTPUT}"
       - run: npm run verify:package
         env:
           npm_config_cache: ${{ steps.npm-cache.outputs.path }}
@@ -627,9 +506,7 @@ jobs:
       - uses: actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020 # v4.4.0
         with:
           node-version-file: .nvmrc
-      - name: Cache npm package downloads
-        id: npm-cache
-        uses: ./.github/actions/npm-cache
+          cache: npm
       - run: npm ci
       - uses: actions/download-artifact@d3f86a106a0bac45b974a628896c90dbdf5c8093 # v4.3.0
         with:
@@ -655,13 +532,11 @@ jobs:
           tests/boundary/cli/nativePlistPrototypeKeyCli.test.ts
           tests/boundary/cli/nativePlistSelectionFailureCli.test.ts
           tests/boundary/cli/nativeDemangleCli.test.ts
-          tests/boundary/cli/nativeDispatchPropertyAttributes.test.ts
           tests/boundary/mcp/nativeDemangleMcp.test.ts
           tests/boundary/providers/native/nativeSignatureTargetBinding.test.ts
           tests/boundary/cli/nativeSignatureCli.test.ts
           tests/boundary/mcp/nativeSignatureTargetBindingMcp.test.ts
           src/process/capture/FilesystemSnapshot.test.ts
-          tests/process-global/filesystemSnapshotFallbackCancellation.test.ts
           tests/boundary/process/darwinProcessRunTokenReader.test.ts
           tests/boundary/process/directAnalysisSignals.test.ts
           tests/boundary/process/processCaptureLifecycle.test.ts
@@ -679,9 +554,7 @@ jobs:
       - uses: actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020 # v4.4.0
         with:
           node-version-file: .nvmrc
-      - name: Cache npm package downloads
-        id: npm-cache
-        uses: ./.github/actions/npm-cache
+          cache: npm
       - run: npm ci
       - name: Run the public CLI/MCP reconstruction journey
         env:
@@ -710,20 +583,18 @@ jobs:
       - uses: actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020 # v4.4.0
         with:
           node-version-file: .nvmrc
-      - name: Cache npm package downloads
-        id: npm-cache
-        uses: ./.github/actions/npm-cache
+          cache: npm
       - run: npm ci
       - uses: actions/download-artifact@d3f86a106a0bac45b974a628896c90dbdf5c8093 # v4.3.0
         with:
           name: rea-build-cache
           path: .turbo/cache/
+      - run: npm run build:cached
       - uses: actions/download-artifact@d3f86a106a0bac45b974a628896c90dbdf5c8093 # v4.3.0
         with:
           name: windows-native-controls
           path: native/windows/build/
       - run: npm run verify:windows-native:artifact
-      - run: npm run build:cached
       - name: Record named Windows host capabilities
         run: node scripts/windows-capabilities.mjs | Out-File -Encoding utf8NoBOM windows-capabilities.json
       - name: Validate Windows host capability report
@@ -742,25 +613,17 @@ jobs:
       - name: Run curated Windows capability tests
         run: >-
           npx vitest run --coverage.enabled=false
-          src/process/capture/FilesystemSnapshot.test.ts
-          tests/process-global/filesystemSnapshotFallbackCancellation.test.ts
           tests/boundary/filesystem/binaryTarget.test.ts
           tests/boundary/filesystem/safeOutputTree.test.ts
           tests/boundary/providers/native/artifactProvider.archiveSafety.test.ts
           tests/boundary/providers/native/artifactProvider.extractionCompleteness.test.ts
           tests/boundary/filesystem/setupUnavailableProvider.test.ts
           tests/boundary/filesystem/windowsNpxRegistration.test.ts
-          tests/boundary/filesystem/clientConfigurationEnvironment.test.ts
-          tests/boundary/filesystem/clientConfigurationLayeredEnvironment.test.ts
-          tests/acceptance/setup/registrationRuntimeEnvironmentCli.test.ts
           tests/boundary/android/workspaceGuardianRetry.test.ts
           tests/acceptance/setup/homeDirectoryFallback.test.ts
           tests/boundary/filesystem/javascriptApplicationWorkflows.test.ts
           tests/boundary/filesystem/webScriptManifestPaths.test.ts
           tests/boundary/process/ProcessEvidence.host.test.ts
-          tests/boundary/process/packageNpmInvocation.test.ts
-          tests/boundary/process/packedBridgeVerification.test.ts
-          tests/boundary/process/windowsOutputCapture.test.ts
           tests/acceptance/webModuleCli.test.ts
           tests/acceptance/webSourceLocationCli.test.ts
           tests/boundary/cli/referenceSourceImportStatus.test.ts
@@ -782,8 +645,6 @@ jobs:
           src/process/ProcessOwnership.validation.test.ts
           src/application/Update.test.ts
           tests/process-global/updateMaintenance.test.ts
-          tests/process-global/runnerCancellation.test.ts
-          tests/process-global/windowsOwnedCommand.test.ts
           tests/conformance/providers/ghidra/realGhidraWindowsWorkflow.test.ts
       - uses: actions/download-artifact@d3f86a106a0bac45b974a628896c90dbdf5c8093 # v4.3.0
         with:
@@ -842,11 +703,11 @@ jobs:
       - uses: actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020 # v4.4.0
         with:
           node-version-file: .nvmrc
-      - name: Cache npm package downloads
-        id: npm-cache
-        uses: ./.github/actions/npm-cache
+          cache: npm
       - run: npm ci
       - run: npm run docs:check
+      - name: Verify published routes, source links and local anchors
+        run: npm run verify:docs:routes
       - name: Generation leaves authored files unchanged
         run: git diff --exit-code
       - uses: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02 # v4.6.2
@@ -914,23 +775,11 @@ jobs:
     with:
       build_cache_artifact: rea-build-cache
 
-  agentenv:
-    needs: [changes, static, build]
-    if: needs.changes.outputs.agentenv == 'true'
-    uses: ./.github/workflows/real-agentenv.yml
-    with:
-      build_cache_artifact: rea-build-cache
-
   nativeaot:
     needs: [changes, static]
     if: needs.changes.outputs.nativeaot == 'true'
     uses: ./.github/workflows/nativeaot-fixtures.yml
 
-  ghidra_bridge:
-    needs: [changes, static]
-    if: needs.changes.outputs.ghidra_bridge == 'true'
-    uses: ./.github/workflows/ghidra-bridge-sources.yml
-
   website:
     needs: [changes, static]
     if: needs.changes.outputs.website == 'true'
@@ -945,9 +794,7 @@ jobs:
         changes,
         static,
         build,
-        reverse-tools-quality,
         test-shard,
-        test-source,
         sqlite-runtime,
         test,
         conformance-fixtures,
@@ -965,9 +812,7 @@ jobs:
         web_network,
         web_runtime,
         web_source_map,
-        agentenv,
         nativeaot,
-        ghidra_bridge,
         website,
       ]
     runs-on: ubuntu-24.04

.github/workflows/ghidra-bridge-sources.yml

@@ -1,48 +0,0 @@
-name: Ghidra bridge source compilation
-
-on:
-  workflow_dispatch:
-  workflow_call:
-
-permissions:
-  contents: read
-
-env:
-  HUSKY: "0"
-
-jobs:
-  ghidra-bridge-sources:
-    name: Compile packaged Ghidra bridge sources
-    runs-on: ubuntu-24.04
-    timeout-minutes: 15
-    env:
-      GHIDRA_RELEASE_URL: https://github.com/NationalSecurityAgency/ghidra/releases/download/Ghidra_12.1.4_build/ghidra_12.1.4_PUBLIC_20260921.zip
-      GHIDRA_RELEASE_SHA256: ddac49f903da9d5bac833e5cc79395098b9c33cfd3279be5f31bd00387d2d4db
-    steps:
-      - uses: actions/checkout@11d5960a326750d5838078e36cf38b85af677262 # v4.4.0
-      - uses: actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020 # v4.4.0
-        with:
-          node-version-file: .nvmrc
-      - name: Validate the SDK pin against the provider's verified release
-        run: node scripts/verify-ghidra-bridge-sources.mjs --check-sdk-pin >> "$GITHUB_ENV"
-      # Only the jars and application.properties are extracted: the check
-      # compiles against them and never launches Ghidra or imports a target.
-      - name: Acquire checksum-verified Ghidra jars in isolated runner storage
-        shell: bash
-        run: |
-          ghidra_root="${RUNNER_TEMP}/rea-ghidra"
-          mkdir -p "${ghidra_root}"
-          curl -fsSL --retry 3 --write-out 'ghidra_download_bytes=%{size_download} ghidra_download_seconds=%{time_total}\n' -o "${ghidra_root}/ghidra.zip" "${GHIDRA_RELEASE_URL}"
-          echo "${GHIDRA_RELEASE_SHA256}  ${ghidra_root}/ghidra.zip" | sha256sum -c -
-          unzip -q "${ghidra_root}/ghidra.zip" '*/Ghidra/*.jar' '*/Ghidra/application.properties' -d "${ghidra_root}"
-          rm "${ghidra_root}/ghidra.zip"
-          properties="$(find "${ghidra_root}" -path '*/Ghidra/application.properties' -print -quit)"
-          test -n "${properties}"
-          echo "GHIDRA_INSTALL_DIR=$(dirname "$(dirname "${properties}")")" >> "${GITHUB_ENV}"
-      # JAVA_HOME_<major>_X64 comes from the runner image, not the env context.
-      - name: Compile bridge sources with the verified runner JDK
-        shell: bash
-        run: |
-          java_home_variable="JAVA_HOME_${GHIDRA_JAVA_MAJOR}_X64"
-          test -n "${!java_home_variable}"
-          JAVA_HOME="${!java_home_variable}" npm run verify:ghidra:bridge-sources -- --verified-sdk

.github/workflows/mutation.yml

@@ -1,62 +0,0 @@
-name: Mutation sweep
-
-on:
-  schedule:
-    - cron: "47 4 * * *"
-  workflow_dispatch:
-
-permissions:
-  contents: read
-
-concurrency:
-  group: mutation-${{ github.ref }}
-  cancel-in-progress: false
-
-env:
-  HUSKY: "0"
-
-jobs:
-  mutation:
-    name: Mutation sweep (${{ matrix.suite }})
-    runs-on: ubuntu-latest
-    timeout-minutes: 60
-    strategy:
-      fail-fast: false
-      max-parallel: 2
-      matrix:
-        include:
-          - suite: reverse-tools
-            config: stryker.config.mjs
-          - suite: reverse-tools-semantics
-            config: stryker.semantics.config.mjs
-    steps:
-      - uses: actions/checkout@11d5960a326750d5838078e36cf38b85af677262 # v4.4.0
-      - uses: actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020 # v4.4.0
-        with:
-          node-version-file: .nvmrc
-      - name: Cache npm package downloads
-        uses: ./.github/actions/npm-cache
-      - run: npm ci
-      - run: npm run test:prepare
-      - name: Run the complete configuration
-        env:
-          MUTATION_CONFIG: ${{ matrix.config }}
-        run: |
-          node scripts/prepare-reverse-tools-mutation.mjs
-          npx --no-install stryker run "${MUTATION_CONFIG}"
-      - name: Require both reports from the completed sweep
-        env:
-          REPORT_BASE: reports/mutation/${{ matrix.suite }}
-        run: |
-          test -s "${REPORT_BASE}.json"
-          test -s "${REPORT_BASE}.html"
-      - name: Retain available mutation diagnostics
-        if: ${{ !cancelled() }}
-        uses: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02 # v4.6.2
-        with:
-          name: mutation-${{ matrix.suite }}-${{ github.run_attempt }}
-          path: |
-            reports/mutation/${{ matrix.suite }}.json
-            reports/mutation/${{ matrix.suite }}.html
-          if-no-files-found: warn
-          retention-days: 7

.github/workflows/pages.yml

@@ -23,8 +23,6 @@ jobs:
       - uses: actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020 # v4.4.0
         with:
           node-version-file: .nvmrc
-      - name: Cache npm package downloads
-        id: npm-cache
-        uses: ./.github/actions/npm-cache
+          cache: npm
       - run: npm ci
-      - run: npm run docs:build
+      - run: npm run verify:docs:routes

.github/workflows/pr-readiness.yml

@@ -1,51 +0,0 @@
-name: PR readiness
-
-on:
-  pull_request_target:
-    branches: [main, "release/*"]
-    types:
-      [
-        opened,
-        edited,
-        synchronize,
-        reopened,
-        ready_for_review,
-        converted_to_draft,
-      ]
-  workflow_dispatch:
-    inputs:
-      pull_request_number:
-        description: Open PR to recheck
-        required: true
-        type: string
-
-permissions: {}
-
-concurrency:
-  group: pr-readiness-${{ github.event.pull_request.number || inputs.pull_request_number }}
-  cancel-in-progress: true
-
-jobs:
-  readiness:
-    name: Validate author declaration
-    runs-on: ubuntu-24.04
-    timeout-minutes: 3
-    permissions:
-      contents: read
-      pull-requests: read
-      statuses: write
-    steps:
-      - uses: actions/checkout@d23441a48e516b6c34aea4fa41551a30e30af803 # v6.1.0
-        with:
-          ref: ${{ github.event.repository.default_branch }}
-          persist-credentials: false
-      - name: Check initial readiness
-        uses: actions/github-script@373c709c69115d41ff229c7e5df9f8788daa9553 # v9
-        with:
-          script: |
-            const { pathToFileURL } = require("node:url");
-            const entry = pathToFileURL(
-              `${process.env.GITHUB_WORKSPACE}/scripts/ci/pr-readiness.mjs`,
-            );
-            const { runReadinessCheck } = await import(entry.href);
-            await runReadinessCheck({ github, context, core });

.github/workflows/real-agentenv.yml

@@ -1,82 +0,0 @@
-name: Real agentenv environment bundle
-
-on:
-  workflow_dispatch:
-  workflow_call:
-    inputs:
-      build_cache_artifact:
-        description: Portable build cache artifact from the calling CI run.
-        required: false
-        type: string
-        default: ""
-
-permissions:
-  contents: read
-
-env:
-  HUSKY: "0"
-  NODE_OPTIONS: --max-old-space-size=768
-  PIP_DISABLE_PIP_VERSION_CHECK: "1"
-
-jobs:
-  real-agentenv:
-    name: Export and run an environment bundle with the agentenv runner
-    runs-on: ubuntu-24.04
-    timeout-minutes: 30
-    steps:
-      - uses: actions/checkout@11d5960a326750d5838078e36cf38b85af677262 # v4.4.0
-      - uses: actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020 # v4.4.0
-        with:
-          node-version-file: .nvmrc
-      - name: Cache npm package downloads
-        id: npm-cache
-        uses: ./.github/actions/npm-cache
-      - run: npm ci
-      - uses: ./.github/actions/portable-build-cache
-        with:
-          build_cache_artifact: ${{ inputs.build_cache_artifact }}
-      - uses: actions/setup-python@a26af69be951a213d495a4c3e4e4022e16d87065 # v5.6.0
-        with:
-          python-version: "3.12"
-      # Public ECR caps anonymous pulls by data per source IP and hosted runners share IPs, so the
-      # framework's image builds can fail here for hours. mirror.gcr.io serves the same Docker
-      # official images under the same digests, so each base image the pinned framework builds from
-      # is pulled there and named as its Dockerfile names it, as the framework's own CI does.
-      # Digest-pinned names are set in containerd, whose images Docker reads only on the containerd
-      # image store; switching stores restarts dockerd, so it happens before anything uses Docker.
-      - name: Use the containerd image store
-        run: |
-          [ -s /etc/docker/daemon.json ] || echo '{}' | sudo tee /etc/docker/daemon.json >/dev/null
-          jq '.features["containerd-snapshotter"] = true' /etc/docker/daemon.json > "$RUNNER_TEMP/daemon.json"
-          sudo mv "$RUNNER_TEMP/daemon.json" /etc/docker/daemon.json
-          sudo systemctl restart docker
-          docker info --format '{{json .DriverStatus}}' | grep -q io.containerd.snapshotter
-      - name: Acquire the pinned agentenv runner in isolated runner storage and check host Docker
-        shell: bash
-        run: |
-          runner_root="${RUNNER_TEMP}/rea-agentenv-runner"
-          python -m venv "${runner_root}"
-          "${runner_root}/bin/python" -m pip install --require-virtualenv --no-cache-dir 'agentenv-framework==0.9.1334'
-          "${runner_root}/bin/agent-env" --version
-          docker version --format '{{.Server.Version}}'
-          echo "REA_AGENT_ENV_COMMAND=${runner_root}/bin/agent-env" >> "${GITHUB_ENV}"
-          echo "REA_DOCKER_COMMAND=$(command -v docker)" >> "${GITHUB_ENV}"
-      - name: Pull the pinned framework's public ECR base images from mirror.gcr.io
-        shell: bash
-        run: |
-          package="$("${REA_AGENT_ENV_COMMAND%/agent-env}/python" -c 'import agent_env, pathlib; print(pathlib.Path(agent_env.__file__).parent)')"
-          grep -rhoE '^FROM +public\.ecr\.aws/docker/library/[^ ]+' --include='Dockerfile*' "${package}" | awk '{print $2}' | sort -u |
-            while read -r image; do
-              name=${image#public.ecr.aws/docker/library/}
-              source=mirror.gcr.io/library/$name
-              case $name in *@*) source=mirror.gcr.io/library/${name%%[:@]*}@${name#*@} ;; esac
-              for attempt in 1 2 3; do
-                docker pull --quiet "$source" && break
-                if [ "$attempt" = 3 ]; then echo "::warning::couldn't pull $source; $image's build will pull it"; continue 2; fi
-                sleep $((attempt * 10))
-              done
-              case ${name%@*} in *:*) docker tag "$source" "${image%@*}" ;; esac
-              case $image in *@*) sudo ctr --namespace moby images tag "$source" "$image" >/dev/null ;; esac
-            done
-      - name: Export a bundle from the source-owned capture and run it with the agentenv runner
-        run: npm run verify:agentenv:environment

.github/workflows/real-binary-layout.yml

@@ -32,9 +32,7 @@ jobs:
       - uses: actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020 # v4.4.0
         with:
           node-version-file: .nvmrc
-      - name: Cache npm package downloads
-        id: npm-cache
-        uses: ./.github/actions/npm-cache
+          cache: npm
       - run: npm ci
       - uses: ./.github/actions/portable-build-cache
         with:

.github/workflows/real-browser.yml

@@ -25,9 +25,7 @@ jobs:
       - uses: actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020 # v4.4.0
         with:
           node-version-file: .nvmrc
-      - name: Cache npm package downloads
-        id: npm-cache
-        uses: ./.github/actions/npm-cache
+          cache: npm
       - run: npm ci
       - uses: ./.github/actions/portable-build-cache
         with:

.github/workflows/real-cutter.yml

@@ -1,76 +0,0 @@
-name: Real upstream Cutter verification
-
-on:
-  workflow_dispatch:
-  repository_dispatch:
-    types: [real-cutter-upstream]
-
-permissions:
-  contents: read
-
-jobs:
-  windows-native-artifact:
-    name: Build Windows bridge security boundary
-    runs-on: ubuntu-latest
-    steps:
-      - uses: actions/checkout@11d5960a326750d5838078e36cf38b85af677262 # v4.4.0
-      - uses: actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020 # v4.4.0
-        with:
-          node-version-file: .nvmrc
-      - name: Install the cross compiler used by the Windows native lane
-        run: |
-          sudo apt-get update
-          sudo apt-get install --no-install-recommends -y g++-mingw-w64-x86-64
-      - run: npm run build:windows-native
-      - uses: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02 # v4.6.2
-        with:
-          name: cutter-windows-native
-          path: native/windows/build/
-          if-no-files-found: error
-
-  cutter-upstream:
-    name: Cutter upstream smoke (${{ matrix.platform }})
-    needs: windows-native-artifact
-    runs-on: ${{ matrix.runner }}
-    timeout-minutes: 20
-    strategy:
-      fail-fast: false
-      matrix:
-        include:
-          - platform: linux
-            runner: [self-hosted, cutter-upstream, linux]
-          - platform: macOS
-            runner: [self-hosted, cutter-upstream, macOS]
-          - platform: Windows
-            runner: [self-hosted, cutter-upstream, Windows]
-    steps:
-      - uses: actions/checkout@11d5960a326750d5838078e36cf38b85af677262 # v4.4.0
-      - uses: actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020 # v4.4.0
-        with:
-          node-version-file: .nvmrc
-      - name: Cache npm package downloads
-        id: npm-cache
-        uses: ./.github/actions/npm-cache
-      - run: npm ci
-      - if: matrix.platform == 'Windows'
-        uses: actions/download-artifact@d3f86a106a0bac45b974a628896c90dbdf5c8093 # v4.3.0
-        with:
-          name: cutter-windows-native
-          path: native/windows/build/
-      - if: matrix.platform == 'Windows'
-        run: npm run verify:windows-native:artifact
-      - if: matrix.platform == 'Windows'
-        run: npm run build:cached
-      - if: matrix.platform == 'Windows'
-        run: npm run verify:windows-native
-      - name: Verify host and real Cutter bridge
-        env:
-          EXPECTED_PLATFORM: ${{ matrix.platform }}
-        run: npm run verify:cutter
-      - uses: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02 # v4.6.2
-        if: always()
-        with:
-          name: cutter-upstream-${{ matrix.platform }}
-          path: cutter-smoke.json
-          if-no-files-found: ignore
-          retention-days: 30

.github/workflows/real-evm-interface.yml

@@ -26,9 +26,7 @@ jobs:
       - uses: actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020 # v4.4.0
         with:
           node-version-file: .nvmrc
-      - name: Cache npm package downloads
-        id: npm-cache
-        uses: ./.github/actions/npm-cache
+          cache: npm
       - run: npm ci
       - uses: ./.github/actions/portable-build-cache
         with:

.github/workflows/real-go-binary.yml

@@ -48,9 +48,7 @@ jobs:
       - uses: actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020 # v4.4.0
         with:
           node-version-file: .nvmrc
-      - name: Cache npm package downloads
-        id: npm-cache
-        uses: ./.github/actions/npm-cache
+          cache: npm
       - uses: actions/setup-go@40f1582b2485089dde7abd97c1529aa768e1baff # v5.6.0
         with:
           go-version: "1.26.1"

.github/workflows/real-hopper-linux.yml

@@ -19,9 +19,7 @@ jobs:
       - uses: actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020 # v4.4.0
         with:
           node-version-file: .nvmrc
-      - name: Cache npm package downloads
-        id: npm-cache
-        uses: ./.github/actions/npm-cache
+          cache: npm
       - run: npm ci
       - name: Pack CLI for setup verification
         shell: bash
@@ -42,9 +40,7 @@ jobs:
       - uses: actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020 # v4.4.0
         with:
           node-version-file: .nvmrc
-      - name: Cache npm package downloads
-        id: npm-cache
-        uses: ./.github/actions/npm-cache
+          cache: npm
       - run: npm ci
       - name: Install packed CLI in isolation
         shell: bash

.github/workflows/real-hopper.yml

@@ -19,9 +19,7 @@ jobs:
       - uses: actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020 # v4.4.0
         with:
           node-version-file: .nvmrc
-      - name: Cache npm package downloads
-        id: npm-cache
-        uses: ./.github/actions/npm-cache
+          cache: npm
       - run: npm ci
       - name: Install packed CLI in isolation
         shell: bash

.github/workflows/real-javascript-recovery.yml

@@ -27,9 +27,7 @@ jobs:
       - uses: actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020 # v4.4.0
         with:
           node-version-file: .nvmrc
-      - name: Cache npm package downloads
-        id: npm-cache
-        uses: ./.github/actions/npm-cache
+          cache: npm
       - run: npm ci
       - uses: ./.github/actions/portable-build-cache
         with:

.github/workflows/real-packet-capture.yml

@@ -47,13 +47,11 @@ jobs:
       - uses: actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020 # v4.4.0
         with:
           node-version-file: .nvmrc
-      - name: Cache npm package downloads
-        id: npm-cache
-        uses: ./.github/actions/npm-cache
+          cache: npm
       - run: sudo apt-get update && sudo DEBIAN_FRONTEND=noninteractive apt-get install -y tshark util-linux python3
       - run: npm ci
       - run: npm run build:cached
-      - run: npm run test:focused -- tests/boundary/captures/fieldDiscovery.test.ts src/process/LinuxResourceLimits.test.ts tests/boundary/captures/captureProvider.test.ts tests/boundary/captures/captureDescriptorCleanup.test.ts tests/boundary/pcap/pcapProvider.test.ts tests/boundary/pcap/pcapProviderCrossPlatform.test.ts tests/boundary/captures/resourceLimits.test.ts tests/boundary/captures/packetOutput.test.ts tests/boundary/mcp/packetCaptureMcp.test.ts tests/boundary/cli/captureCleanup.test.ts
+      - run: npm run test:focused -- tests/boundary/captures/fieldDiscovery.test.ts src/process/LinuxResourceLimits.test.ts tests/boundary/captures/captureProvider.test.ts tests/boundary/captures/captureDescriptorCleanup.test.ts tests/boundary/captures/resourceLimits.test.ts tests/boundary/captures/packetOutput.test.ts tests/boundary/mcp/packetCaptureMcp.test.ts tests/boundary/cli/captureCleanup.test.ts
       - run: node scripts/verify-packet-capture.mjs
         env:
           REA_TSHARK_COMMAND: /usr/bin/tshark

.github/workflows/real-recorded-crash.yml

@@ -24,30 +24,21 @@ jobs:
   real-recorded-crash:
     runs-on: ubuntu-24.04
     timeout-minutes: 15
-    strategy:
-      fail-fast: false
-      matrix:
-        image: ["ubuntu:24.04", "debian:trixie-slim"]
-    container: ${{ matrix.image }}
     steps:
-      - name: Install fixture and debugger prerequisites in the disposable container
-        shell: bash
-        run: |
-          apt-get update -qq
-          apt-get install --yes --no-install-recommends \
-            ca-certificates git python3-venv gcc libc6-dev strace gdb
-
       - uses: actions/checkout@11d5960a326750d5838078e36cf38b85af677262 # v4.4.0
       - uses: actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020 # v4.4.0
         with:
           node-version-file: .nvmrc
-      - name: Cache npm package downloads
-        id: npm-cache
-        uses: ./.github/actions/npm-cache
+          cache: npm
       - run: npm ci
       - uses: ./.github/actions/portable-build-cache
         with:
           build_cache_artifact: ${{ inputs.build_cache_artifact }}
+      - name: Install GDB on the disposable CI runner
+        shell: bash
+        run: |
+          sudo apt-get update -qq
+          sudo apt-get install --yes --no-install-recommends gdb
       - name: Acquire exact unchanged upstreams in isolated runner storage
         shell: bash
         run: |

.github/workflows/real-signal-recording.yml

@@ -40,9 +40,7 @@ jobs:
       - uses: actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020 # v4.4.0
         with:
           node-version-file: .nvmrc
-      - name: Cache npm package downloads
-        id: npm-cache
-        uses: ./.github/actions/npm-cache
+          cache: npm
       - run: sudo apt-get update && sudo apt-get install -y sigrok-cli util-linux python3
       - run: npm ci
       - run: npm run build:cached

.github/workflows/real-web-network-captures.yml

@@ -26,9 +26,7 @@ jobs:
       - uses: actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020 # v4.4.0
         with:
           node-version-file: .nvmrc
-      - name: Cache npm package downloads
-        id: npm-cache
-        uses: ./.github/actions/npm-cache
+          cache: npm
       - name: Use pinned package manager
         run: npm install --global npm@11.16.0
       - run: npm ci

.github/workflows/real-web-runtime.yml

@@ -21,14 +21,12 @@ jobs:
       - uses: actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020 # v4.4.0
         with:
           node-version-file: .nvmrc
-      - name: Cache npm package downloads
-        id: npm-cache
-        uses: ./.github/actions/npm-cache
+          cache: npm
       - run: npm ci
       - uses: ./.github/actions/portable-build-cache
         with:
           build_cache_artifact: ${{ inputs.build_cache_artifact }}
-      - run: env -u DBUS_SESSION_BUS_ADDRESS npm run verify:browser:runtime
+      - run: npm run verify:browser:runtime
         env:
           REA_BROWSER_EXECUTABLE: /usr/bin/google-chrome
           REA_BROWSER_NO_SANDBOX: "true"

.github/workflows/real-web-source-map.yml

@@ -21,9 +21,7 @@ jobs:
       - uses: actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020 # v4.4.0
         with:
           node-version-file: .nvmrc
-      - name: Cache npm package downloads
-        id: npm-cache
-        uses: ./.github/actions/npm-cache
+          cache: npm
       - run: npm ci
       - uses: ./.github/actions/portable-build-cache
         with:

.github/workflows/release-recovery.yml

@@ -1,109 +0,0 @@
-name: Recover published release
-
-on:
-  workflow_dispatch:
-    inputs:
-      version:
-        description: Existing npm and GitHub release version
-        required: true
-        type: string
-      release_run_id:
-        description: Original Release run with successful exact-source qualification and npm publication
-        required: true
-        type: string
-
-concurrency:
-  group: release-recovery-${{ inputs.version }}
-  cancel-in-progress: false
-
-jobs:
-  verify:
-    name: Verify existing published package
-    if: github.ref == 'refs/heads/main'
-    runs-on: ubuntu-latest
-    timeout-minutes: 30
-    permissions:
-      contents: read
-      actions: read
-    outputs:
-      source_sha: ${{ steps.release.outputs.source_sha }}
-      version: ${{ steps.release.outputs.version }}
-    steps:
-      - uses: actions/checkout@d23441a48e516b6c34aea4fa41551a30e30af803 # v6.1.0
-        with:
-          fetch-depth: 0
-          persist-credentials: false
-      - uses: actions/setup-node@249970729cb0ef3589644e2896645e5dc5ba9c38 # v6.5.0
-        with:
-          node-version-file: .nvmrc
-          package-manager-cache: false
-      - run: npm ci
-      - name: Validate original release authority
-        id: release
-        env:
-          GH_TOKEN: ${{ github.token }}
-          RECOVERY_VERSION: ${{ inputs.version }}
-          RECOVERY_RUN_ID: ${{ inputs.release_run_id }}
-        run: node scripts/ci/release-recovery.mjs resolve
-      - name: Check out released metadata
-        uses: actions/checkout@d23441a48e516b6c34aea4fa41551a30e30af803 # v6.1.0
-        with:
-          ref: ${{ steps.release.outputs.source_sha }}
-          path: .cache/release-source
-          persist-credentials: false
-      - name: Download original qualified package
-        uses: actions/download-artifact@d3f86a106a0bac45b974a628896c90dbdf5c8093 # v4.3.0
-        with:
-          name: verified-release-package
-          run-id: ${{ steps.release.outputs.run_id }}
-          github-token: ${{ github.token }}
-          path: .cache/verified-package
-      - name: Restore original verifier runtime
-        uses: actions/download-artifact@d3f86a106a0bac45b974a628896c90dbdf5c8093 # v4.3.0
-        with:
-          name: rea-test-runtime
-          run-id: ${{ steps.release.outputs.run_id }}
-          github-token: ${{ github.token }}
-          path: .
-      - name: Match published npm bytes to the qualified package
-        env:
-          RECOVERY_VERSION: ${{ steps.release.outputs.version }}
-          RECOVERY_RUN_ID: ${{ steps.release.outputs.run_id }}
-          RECOVERY_RUN_ATTEMPT: ${{ steps.release.outputs.run_attempt }}
-          RECOVERY_SOURCE_SHA: ${{ steps.release.outputs.source_sha }}
-          RECOVERY_SOURCE_DIRECTORY: .cache/release-source
-          RECOVERY_ARTIFACT_DIRECTORY: .cache/verified-package
-        run: node scripts/ci/release-recovery.mjs verify
-      - name: Rehearse the original qualified tarball
-        env:
-          RECOVERY_VERSION: ${{ steps.release.outputs.version }}
-        run: node scripts/verify-release-artifact.mjs .cache/verified-package/package.tgz "$RECOVERY_VERSION"
-      - name: Verify published CLI, MCP and update
-        env:
-          RECOVERY_VERSION: ${{ steps.release.outputs.version }}
-        run: node scripts/verify-published-package.mjs "$RECOVERY_VERSION"
-      - name: Validate released registry metadata
-        working-directory: .cache/release-source
-        run: npm run mcp-registry:check
-
-  publish-mcp:
-    name: Finish MCP Registry publication
-    needs: verify
-    runs-on: ubuntu-latest
-    timeout-minutes: 10
-    permissions:
-      contents: read
-      id-token: write
-    steps:
-      - uses: actions/checkout@d23441a48e516b6c34aea4fa41551a30e30af803 # v6.1.0
-        with:
-          persist-credentials: false
-      - name: Check out verified released metadata
-        uses: actions/checkout@d23441a48e516b6c34aea4fa41551a30e30af803 # v6.1.0
-        with:
-          ref: ${{ needs.verify.outputs.source_sha }}
-          path: .cache/release-source
-          persist-credentials: false
-      - uses: ./.github/actions/publish-mcp
-        with:
-          directory: .cache/release-source

.github/workflows/release.yml

@@ -304,41 +304,12 @@ jobs:
     with:
       source_sha: ${{ needs.merged-release.outputs.sha || needs.release-please.outputs.sha }}
 
-  rehearsal:
-    name: Rehearse qualified release on a clean runner
+  publish:
+    name: Publish to npm
     needs: [merged-release, release-please, qualification]
     if: >-
       always() && !cancelled() && needs.qualification.result == 'success'
     runs-on: ubuntu-latest
-    timeout-minutes: 15
-    permissions:
-      contents: read
-      actions: read
-    steps:
-      - uses: actions/checkout@d23441a48e516b6c34aea4fa41551a30e30af803 # v6.1.0
-        with:
-          ref: ${{ needs.merged-release.outputs.sha || needs.release-please.outputs.sha }}
-          persist-credentials: false
-      - uses: actions/setup-node@249970729cb0ef3589644e2896645e5dc5ba9c38 # v6.5.0
-        with:
-          node-version-file: .nvmrc
-          package-manager-cache: false
-      - run: npm ci
-      - uses: ./.github/actions/prepare-release-package
-        id: package
-      - name: Exercise the exact qualified tarball
-        env:
-          VERIFIED_PACKAGE_TARBALL: ${{ steps.package.outputs.tarball }}
-          VERIFIED_PACKAGE_VERSION: ${{ steps.package.outputs.version }}
-        run: node scripts/verify-release-artifact.mjs "$VERIFIED_PACKAGE_TARBALL" "$VERIFIED_PACKAGE_VERSION"
-
-  publish:
-    name: Publish to npm
-    needs: [merged-release, release-please, qualification, rehearsal]
-    if: >-
-      always() && !cancelled() &&
-      needs.qualification.result == 'success' && needs.rehearsal.result == 'success'
-    runs-on: ubuntu-latest
     permissions:
       contents: read
       id-token: write
@@ -356,36 +327,58 @@ jobs:
 
       - run: npm ci
 
-      - uses: ./.github/actions/prepare-release-package
-        id: package
+      - name: Download the exact qualified package
+        uses: actions/download-artifact@d3f86a106a0bac45b974a628896c90dbdf5c8093 # v4.3.0
+        with:
+          name: verified-release-package
+          path: .cache/verified-package/
 
-      - name: Inspect existing npm version
-        id: registry
-        env:
-          VERIFIED_PACKAGE_TARBALL: ${{ steps.package.outputs.tarball }}
-          VERIFIED_PACKAGE_VERSION: ${{ steps.package.outputs.version }}
-        run: node scripts/ci/npm-release.mjs inspect "$VERIFIED_PACKAGE_TARBALL" "$VERIFIED_PACKAGE_VERSION"
+      - name: Verify qualified package provenance and digest
+        id: package
+        run: node scripts/ci/verified-package.mjs validate .cache/verified-package
 
       - name: Publish
-        if: steps.registry.outputs.published == 'false'
         shell: bash
         env:
           VERIFIED_PACKAGE_TARBALL: ${{ steps.package.outputs.tarball }}
-          VERIFIED_PACKAGE_VERSION: ${{ steps.package.outputs.version }}
         run: |
-          tag="$(node scripts/release-npm-tag.mjs "$VERIFIED_PACKAGE_VERSION")"
-          npm publish "${VERIFIED_PACKAGE_TARBALL}" --access public --tag "${tag}"
-
-      - name: Verify published npm bytes and dist-tag
-        env:
-          VERIFIED_PACKAGE_TARBALL: ${{ steps.package.outputs.tarball }}
-          VERIFIED_PACKAGE_VERSION: ${{ steps.package.outputs.version }}
-        run: node scripts/ci/npm-release.mjs verify "$VERIFIED_PACKAGE_TARBALL" "$VERIFIED_PACKAGE_VERSION"
+          version="$(node --input-type=module -e 'import packageJson from "./package.json" with { type: "json" }; process.stdout.write(packageJson.version)')"
+          published_version="$(npm view "rea-agents@${version}" version --json 2>/dev/null || true)"
+          if [ "${published_version}" = "\"${version}\"" ]; then
+            echo "rea-agents@${version} is already published; verifying the existing package."
+          else
+            tag="$(node scripts/release-npm-tag.mjs "${version}")"
+            npm publish "${VERIFIED_PACKAGE_TARBALL}" --access public --tag "${tag}"
+          fi
 
       - name: Verify published CLI from npm
-        env:
-          VERIFIED_PACKAGE_VERSION: ${{ steps.package.outputs.version }}
-        run: node scripts/verify-published-package.mjs "$VERIFIED_PACKAGE_VERSION"
+        shell: bash
+        run: |
+          version="$(node --input-type=module -e 'import packageJson from "./package.json" with { type: "json" }; process.stdout.write(packageJson.version)')"
+          verification_root="$(mktemp -d)"
+          trap 'rm -rf -- "${verification_root}"' EXIT
+          cd "${verification_root}"
+          max_attempts=120
+          sleep_seconds=15
+          total_window_minutes=$((max_attempts * sleep_seconds / 60))
+          for attempt in $(seq 1 "${max_attempts}"); do
+            published_version="$(npm view --prefer-online "rea-agents@${version}" version --json 2>/dev/null || true)"
+            if [ "${published_version}" = "\"${version}\"" ]; then
+              echo "rea-agents@${version} is visible on npm after attempt ${attempt}/${max_attempts}; verifying the published CLI."
+              npm exec --yes --package="rea-agents@${version}" -- rea --help
+              npm exec --yes --package="rea-agents@${version}" -- rea --llms
+              node "${GITHUB_WORKSPACE}/scripts/verify-published-package.mjs" "${version}"
+              exit 0
+            else
+              echo "rea-agents@${version} is not visible on npm yet (attempt ${attempt}/${max_attempts}; up to ${total_window_minutes} minutes)" >&2
+            fi
+            if [ "${attempt}" -lt "${max_attempts}" ]; then
+              sleep "${sleep_seconds}"
+            fi
+          done
+          echo "rea-agents@${version} did not become visible on npm within ${total_window_minutes} minutes (${max_attempts} attempts × ${sleep_seconds}s)" >&2
+          echo "This indicates npm registry propagation delay, not a CLI verification failure." >&2
+          exit 1
 
   publish-mcp:
     name: Publish to MCP Registry
@@ -407,4 +400,23 @@ jobs:
       - name: Verify package and registry metadata versions
         run: npm run mcp-registry:check
 
-      - uses: ./.github/actions/publish-mcp
+      - name: Install MCP Registry publisher
+        env:
+          MCP_PUBLISHER_VERSION: v1.8.0
+          MCP_PUBLISHER_SHA256_LINUX_AMD64: 1370446bbe74d562608e8005a6ccce02d146a661fbd78674e11cc70b9618d6cf
+        run: |
+          archive="mcp-publisher_linux_amd64.tar.gz"
+          curl -fsSLo "${archive}" \
+            "https://github.com/modelcontextprotocol/registry/releases/download/${MCP_PUBLISHER_VERSION}/${archive}"
+          echo "${MCP_PUBLISHER_SHA256_LINUX_AMD64}  ${archive}" | sha256sum --check --strict
+          tar xzf "${archive}" mcp-publisher
+          chmod +x mcp-publisher
+
+      - name: Validate MCP Registry metadata
+        run: ./mcp-publisher validate
+
+      - name: Authenticate to MCP Registry
+        run: ./mcp-publisher login github-oidc
+
+      - name: Publish MCP Registry metadata
+        run: ./mcp-publisher publish

.github/workflows/sqlite-runtime.yml

@@ -27,9 +27,7 @@ jobs:
         with:
           node-version: ${{ matrix.node }}
           check-latest: true
-      - name: Cache npm package downloads
-        id: npm-cache
-        uses: ./.github/actions/npm-cache
+          cache: npm
       - run: npm ci
       - uses: actions/download-artifact@d3f86a106a0bac45b974a628896c90dbdf5c8093 # v4.3.0
         with:

.gitignore

@@ -33,8 +33,6 @@ codedb.snapshot
 htmlcov/
 .coverage
 coverage/
-.stryker-tmp/
-reports/mutation/
 .vitest/
 .vitest-reports/
 test-results.xml

.release-please-manifest.json

@@ -1,3 +1,3 @@
 {
-  ".": "6.7.0"
+  ".": "6.4.0"
 }

AGENTS.md

@@ -14,14 +14,12 @@ Preserve caller-selected inputs and local evidence, including output, URLs, path
 
 ## Architecture and Cleanup
 
-Dependencies flow inward: domain semantics and contracts, provider adapters, shared application workflows, then CLI/MCP adapters. Keep engine protocols and provider-specific code out of domain/application layers. See [docs/architecture.mermaid](docs/architecture.mermaid) when changing composition.
+Dependencies flow inward: domain semantics and contracts, provider adapters, shared application workflows, then CLI/MCP adapters. Keep engine protocols and provider-specific code out of domain/application layers. See [docs/architecture/architecture.mermaid](docs/architecture/architecture.mermaid) when changing composition.
 
 Give each interpretation and resource a clear owner. Consumers must use that owner's parsed facts rather than reinterpret raw source. Preserve identity, omission, uncertainty, and source evidence across boundaries. Retain ownership of resources whose cleanup failed. Reuse `src/process/` supervision and identity primitives; a PID and executable path alone do not establish ownership after exit or reuse.
 
 Keep proof of ownership separate from validity, editability, and readiness. Malformed owned data may still be safely removable. Unresolved identity or applicability must remain unknown rather than be treated as absent, foreign, or aligned.
 
-For lifecycle changes, follow [ownership and completion invariants](docs/tool-design.md#own-the-lifecycle) and select the applicable [lifecycle regressions](docs/testing.md#lifecycle-regressions). Include late handshakes, cancellation during final cleanup, mixed child outcomes, and cleanup retry where those stages exist; active-execution cancellation alone does not cover finalization.
-
 Assess brittleness in touched code during implementation, debugging, review, and maintenance. Fix the producing representation or ownership rule before adding downstream repairs. Normalize once at the owning boundary using format-aware parsers. Remove superseded representations, aliases, wrappers, and redundant tests after verifying affected consumers. Introduce abstractions only when they remove observed complexity.
 
 When fixing a bug, inspect the producing boundary and affected consumers for duplicated interpretation or unclear ownership. Complete any directly related refactor in the same change and remove superseded code. Passing regression tests alone does not establish that the brittleness is resolved. If related cleanup remains, explain what remains and why.
@@ -59,6 +57,12 @@ do not establish fewer tokens or faster analysis.
 
 ## Development
 
+Documentation ownership and authoring conventions live in
+[docs/development/documentation.md](docs/development/documentation.md). A feature
+uses `docs/specs/<domain>/<feature-slug>/spec.md`, one `plan.md` and `tasks.md`;
+individual architectural decisions use `docs/adr/<domain>/<decision-slug>.md`.
+Consult the [documentation directory](docs/README.md) before adding a guide.
+
 Use [.nvmrc](.nvmrc) and `package.json#packageManager` for the pinned toolchain. Cursor Cloud may place older Node.js first on `PATH`; environment setup installs the pinned toolchain under `/usr/local/bin`.
 
 - `npm ci`: install locked dependencies.
@@ -74,43 +78,12 @@ Use relevant checks for the change. The complete local gate, `npm run check:pr`,
 
 ## Tool and Test Changes
 
-For tool design, follow [docs/tool-design.md](docs/tool-design.md): start from the analyst question, reuse existing contracts, preserve caller choices, and return useful evidence inline. Limits must follow real format, protocol, authority, or resource constraints. Account for representation expansion before allocation; derive completeness from examined coverage.
+For tool design, follow [docs/development/tool-design.md](docs/development/tool-design.md): start from the analyst question, reuse existing contracts, preserve caller choices, and return useful evidence inline. Limits must follow real format, protocol, authority, or resource constraints. Account for representation expansion before allocation; derive completeness from examined coverage.
 
-For test changes or provider claims, use [docs/testing.md](docs/testing.md). Prefer real public CLI/MCP workflows, then production-boundary integration, then producer goldens. Keep module tests for distinct semantics stronger workflows cannot reliably reproduce. Preserve malformed-input, cancellation, cleanup, permission, capacity, and target-identity coverage when pruning. Report unverified coverage explicitly; simulated providers do not establish real-provider behavior.
+For test changes or provider claims, use [docs/development/testing.md](docs/development/testing.md). Prefer real public CLI/MCP workflows, then production-boundary integration, then producer goldens. Keep module tests for distinct semantics stronger workflows cannot reliably reproduce. Preserve malformed-input, cancellation, cleanup, permission, capacity, and target-identity coverage when pruning. Report unverified coverage explicitly; simulated providers do not establish real-provider behavior.
 
 Use Conventional Commit subjects and PR titles. Mark breaking changes with `!` or a `BREAKING CHANGE:` footer. Describe behavior changes, relevant validation, and real-provider verification scope.
 
-## Issue Reports
-
-Follow [issue reporting guidance](CONTRIBUTING.md#reporting-issues) and the matching
-issue form. Keep reports concise and cite the smallest useful evidence.
-Distinguish observed results, source-derived reasoning, hypotheses, and proposed
-checks. Never claim runtime reproduction or measurements you did not perform.
-Use `NOT_ENOUGH_INFO` with an explanation for missing narrative answers or evidence.
-Incomplete reports, source-only findings, and early feature or design ideas are
-welcome when their limitations are explicit; a completed diagnosis or fix is not
-required to open an issue.
-
-## Pull Request Readiness
-
-Follow [human ownership and readiness](CONTRIBUTING.md#pull-request-ownership-and-readiness)
-when preparing a PR. AI-assisted contributions are welcome; a human must review
-and own the final diff, check the validation evidence and its limitations, and
-explicitly declare the PR ready for initial maintainer review.
-
-Keep the PR body concise and current, with the concrete problem, observable
-outcome, approach, and evidence. Report only checks that actually ran as executed;
-distinguish source-derived conclusions, proposed checks, and unavailable coverage.
-Address actionable automated review findings and explain disagreements.
-
-Leave the template's **Author readiness** declarations unchecked for the human
-owner to complete. Never attest to human review on their behalf. Keep the PR in
-draft until the human declares the PR initially ready. Later pushes do not
-invalidate that declaration or require another human sign-off. Keep the PR body
-and affected validation current as work changes. The readiness check validates
-the filled declaration; CI and automated review results do not establish that
-human review occurred, maintainer scope approval, or merge permission.
-
 <!-- BEGIN:turborepo-agent-rules -->
 
 # This is NOT the Turborepo you know

CHANGELOG.md

@@ -1,206 +1,5 @@
 # Changelog
 
-## [6.7.0](https://github.com/morluto/rea/compare/rea-agents-6.6.0...rea-agents-6.7.0) (2026-10-18)
-
-### Highlights
-
-- Client configuration edits follow the duplicate-member semantics used by MCP clients.
-
-### Changes
-
-- Includes the [6.6.0 changes and migration notes](https://github.com/morluto/rea/releases/tag/rea-agents-6.6.0). That version was tagged but was not published to npm.
-
-### Fixes
-
-- **Client configuration:** Setup edits the last repeated JSON/JSONC member, matching the value clients actually read. Setup and uninstall refuse a removal that would reactivate a shadowed duplicate, preserving the original configuration. ([#4957](https://github.com/morluto/rea/pull/4957), [morluto/rea#4952](https://github.com/morluto/rea/issues/4952)). Thanks @kaoru0822-kitauji, @xu91102.
-
-Full contribution record: [4 commits and 1 merged PR](https://github.com/morluto/rea/blob/rea-agents-6.7.0/docs/releases/6.7.0.contributions.json).
-
-## [6.6.0](https://github.com/morluto/rea/compare/rea-agents-6.5.0...rea-agents-6.6.0) (2026-10-18)
-
-### Highlights
-
-- Add Kuna as a caller-supplied static-analysis provider.
-- Query selected JavaScript facts and multiple APK locale tables without repeating the underlying analysis.
-- Extend Ghidra analysis to Windows ARM PE targets and explicit raw m68k images.
-- Preserve completed Evidence, cancellation reasons and retryable cleanup across provider and CLI finalization.
-
-### Changes
-
-- **Kuna analysis:** Use a caller-installed Kuna for procedure listings, pseudocode, assembly, call relationships, exact-address xrefs and cached string searches. Project exports retain source spans and digests; repeated requests reuse completed work. Recorded real-provider coverage uses Kuna 1.833 on Linux; Windows, PE and universal Mach-O are unsupported. See [the provider guide](docs/kuna-provider.md). ([#3832](https://github.com/morluto/rea/pull/3832), [#3854](https://github.com/morluto/rea/pull/3854), [#4071](https://github.com/morluto/rea/pull/4071), [#4095](https://github.com/morluto/rea/pull/4095)). Thanks @gensokyo-dev, @kaoru0822-kitauji, @N0zoM1z0.
-- **Retained JavaScript facts:** Query exact application paths, selected properties and filtered module references through `inspect_analysis_view`, with paging and complete row Evidence. These views reuse completed analysis and preserve source selection and unknown coverage. ([#4265](https://github.com/morluto/rea/pull/4265), [morluto/rea#4190](https://github.com/morluto/rea/issues/4190), [#4097](https://github.com/morluto/rea/pull/4097), [morluto/rea#4092](https://github.com/morluto/rea/issues/4092)). Thanks @kaoru0822-kitauji, @N0zoM1z0.
-- **APK locale tables:** Request several resource locales in one decode with repeatable CLI `--locales` or MCP `locales`. Each table reports its status and coverage; existing single-locale fields remain available. ([#4804](https://github.com/morluto/rea/pull/4804), [morluto/rea#4777](https://github.com/morluto/rea/issues/4777)). Thanks @abhay-2108, @N0zoM1z0.
-- **Windows ARM binaries:** Ghidra admits ARMNT/Thumb-2 and ARM64 PE applications and DLLs on the Windows x64 host lane. Recorded Ghidra 12.1.4 verification uses `WindowsResourceReference` disabled and raised startup budgets; default-analyzer completion, ARM64EC/ARM64X and Windows-on-Arm hosts remain unverified or unsupported. See [the exact scope](docs/windows-ghidra-p0.md#native-authority-and-target-identity). ([#3965](https://github.com/morluto/rea/pull/3965), [morluto/rea#2186](https://github.com/morluto/rea/issues/2186)). Thanks @N0zoM1z0, @WestLabsAI.
-- **Raw m68k images:** Analyze explicitly selected big-endian m68k raw binaries using Ghidra’s fixed 68000 profile and a caller-supplied aligned entry. Real CLI/MCP verification used Ghidra 12.1.4 on macOS arm64; Linux is unverified and Windows P0 does not admit m68k. See [mapping requirements](docs/raw-binary.md). ([#4018](https://github.com/morluto/rea/pull/4018)). Thanks @icedac.
-- **JADX deadlines:** Set `REA_JADX_OPERATION_TIMEOUT_MS` to extend APK loading and upstream operation deadlines together. Doctor reports the effective value and setup forwards an explicit selection. ([#4466](https://github.com/morluto/rea/pull/4466), [morluto/rea#3918](https://github.com/morluto/rea/issues/3918)). Thanks @jaychou813, @SandstromPL.
-- **Electron window options:** Resolve stable local constant `BrowserWindow` options while retaining source provenance. Relevant writes and escapes keep the result unknown. ([#4400](https://github.com/morluto/rea/pull/4400), [morluto/rea#4366](https://github.com/morluto/rea/issues/4366)). Thanks @kaoru0822-kitauji, @N0zoM1z0.
-- **Language editions:** Add the Greek website edition and Malayalam documentation, with Korean typography and translation corrections across the site. ([#3520](https://github.com/morluto/rea/pull/3520), [#4792](https://github.com/morluto/rea/pull/4792), [#3821](https://github.com/morluto/rea/pull/3821), [morluto/rea#3820](https://github.com/morluto/rea/issues/3820), [#3799](https://github.com/morluto/rea/pull/3799), [morluto/rea#3798](https://github.com/morluto/rea/issues/3798), [#4344](https://github.com/morluto/rea/pull/4344), [#3856](https://github.com/morluto/rea/pull/3856), [#4166](https://github.com/morluto/rea/pull/4166)). Thanks @gensokyo-dev, @hi2242, @kalayciburak, @kaoru0822-kitauji, @kraken-503, @kukinghan, @N0zoM1z0, @yeseong0412.
-
-### Fixes
-
-- **Cancellation and cleanup:** Keep completed observations, exact cancellation reasons and the original physical failure through finalization. Failed cleanup retains its process or file owner for retry; recovered resources disappear from pending-cleanup reports without replacing the original error. ([#4238](https://github.com/morluto/rea/pull/4238), [morluto/rea#4232](https://github.com/morluto/rea/issues/4232), [#4274](https://github.com/morluto/rea/pull/4274), [morluto/rea#3923](https://github.com/morluto/rea/issues/3923), [3e82366](https://github.com/morluto/rea/commit/3e8236639abffa39deb5d5e939ec8baf6aaf3ca3), [16924e2](https://github.com/morluto/rea/commit/16924e275e939d0543ba01493324959a9e1d731c), [bbfe6ed](https://github.com/morluto/rea/commit/bbfe6edd60290f9bfbec68c8a0bcf605d8bbf5b3), [1f23e97](https://github.com/morluto/rea/commit/1f23e977b50301e91f02a4a17c9f8d48bb7b60f3), [08fbeb8](https://github.com/morluto/rea/commit/08fbeb8bdab27118b6c57039aef7c0fa8b6463bc)). Thanks @coygeek.
-- **Provider startup:** Join prerequisite probes and in-flight readiness work before shutdown, preserve typed timeout and JVM-memory failures, and retain startup diagnostics through cleanup. Ghidra recognizes keg-only Homebrew JDKs and names the setting responsible for a startup timeout. ([376eeca](https://github.com/morluto/rea/commit/376eeca770820b31f7f8d4c5fcc397315621643e), [ceeff5a](https://github.com/morluto/rea/commit/ceeff5a41788e47e5aee96a4baf191a6ce7fde4b), [3ad1032](https://github.com/morluto/rea/commit/3ad1032b11edea2dcb054e78f951cc43159ae83d), [964decd](https://github.com/morluto/rea/commit/964decd989acfa84c4bfc3295362c4c46877fc20), [3fa972a](https://github.com/morluto/rea/commit/3fa972af7c7cb6cf014ffc426bdf7130dc6f2fd2), [#4557](https://github.com/morluto/rea/pull/4557), [morluto/rea#4556](https://github.com/morluto/rea/issues/4556), [#4590](https://github.com/morluto/rea/pull/4590), [morluto/rea#4241](https://github.com/morluto/rea/issues/4241)). Thanks @DanielCvz1, @J0UH, @Rinkia, @RishTheFish21, @vadlachary2002.
-- **Client configuration:** Preserve the selected launcher, destination file, caller timeout choices and unresolved configuration evidence. Setup/uninstall recovery stays bound to the exact published file, keeps current verified backups, and transfers failed cleanup ownership for retry. ([d0253c9](https://github.com/morluto/rea/commit/d0253c99d65afbbd12732a2fdaf711640574e17f), [7e4eed9](https://github.com/morluto/rea/commit/7e4eed9dd48485b6a7100300aa98401811c2deb9), [2fb5e20](https://github.com/morluto/rea/commit/2fb5e204a35723f6f843d56ca47b0db94d8fcc44), [8235210](https://github.com/morluto/rea/commit/823521085a28f825e7fee1929d852d420042d1f7), [d818c3d](https://github.com/morluto/rea/commit/d818c3d2639d3115edb8a5269a754101aea6c3bd), [19329e4](https://github.com/morluto/rea/commit/19329e43bb38ca9d64512d801b25abcb188d2512), [dadf909](https://github.com/morluto/rea/commit/dadf909dce2e8b3d055541de69b4118d21276316), [333e0ab](https://github.com/morluto/rea/commit/333e0ab0dfc126a9915907d5079ed6195190e38e), [c15c206](https://github.com/morluto/rea/commit/c15c2062ad815cc9a3222ccfaeb7ef53cacd8b72)). Thanks @Adolanium.
-- **Configuration formats:** Read signed 64-bit TOML integers without rounding, handle large TOML documents without argument-spread failures, preserve JSONC trivia and Hermes YAML scalar text, and reject NUL bytes in registration environment values. ([#4937](https://github.com/morluto/rea/pull/4937), [morluto/rea#4917](https://github.com/morluto/rea/issues/4917), [c43bc0b](https://github.com/morluto/rea/commit/c43bc0bf66a4e245a0cafa40def0d0207bcbd73c), [4fd28fc](https://github.com/morluto/rea/commit/4fd28fc9e0c4f8358147af38c72ab9e814f52d61), [#3568](https://github.com/morluto/rea/pull/3568), [#4335](https://github.com/morluto/rea/pull/4335)). Thanks @alfredo1491, @gensokyo-dev, @kaoru0822-kitauji, @N0zoM1z0, @ShuaixinHuang, @xu91102.
-- **Claude Code configuration:** Setup, doctor and uninstall now accept only the strict JSON format Claude Code reads, including a leading UTF-8 BOM. Comments and trailing commas are refused before backup or writing; clients that support JSONC retain their existing behavior. ([#4944](https://github.com/morluto/rea/pull/4944), [morluto/rea#4940](https://github.com/morluto/rea/issues/4940)). Thanks @kaoru0822-kitauji, @xu91102.
-- **CLI output and dispatch:** Accept `--flag=value` and spaced global output values, keep array positions in filtered JSON, validate integer tokens before coercion, and exit quietly when the output reader closes. Cancellation remains effective through command finalization; app bundles and static native inspections select the intended workflow. ([#3811](https://github.com/morluto/rea/pull/3811), [#4823](https://github.com/morluto/rea/pull/4823), [2ae4e16](https://github.com/morluto/rea/commit/2ae4e1608f290c95ff7cff28c4d16a79b301d03d), [8d82579](https://github.com/morluto/rea/commit/8d8257928bbe8d43fedffc4db5fca26c8108820f), [#3781](https://github.com/morluto/rea/pull/3781), [279c590](https://github.com/morluto/rea/commit/279c590ef6bb737d4a48ea696a0ae5eb30010b3d), [#3511](https://github.com/morluto/rea/pull/3511), [morluto/rea#3321](https://github.com/morluto/rea/issues/3321), [f31b231](https://github.com/morluto/rea/commit/f31b231a92a61be6bd1800b16be0b3210ae82944)). Thanks @arjunprabhulal, @coygeek, @kaoru0822-kitauji, @ShuaixinHuang, @Sriram-PR, @Tapraj-Pathak.
-- **Updates:** Route `--update` through the verified updater and bound retained package-manager diagnostics. ([4f7b5fb](https://github.com/morluto/rea/commit/4f7b5fb6023ce2ec449561782d09e3c7e5ac7c7b), [01cdbbd](https://github.com/morluto/rea/commit/01cdbbdc556262c47d04a5b3391dd9c17946d3fc)).
-- **MCP contracts:** Advertise self-contained tool inputs while preserving tuple, array, Boolean and nested-JSON constraints across schema profiles. Schema-reference handling no longer rewrites literal metadata; catalog identity includes the output-schema profile. ([5e30969](https://github.com/morluto/rea/commit/5e30969cc5f1255d44ec7a1f1ca8dbac0af5e7c4), [10aa74d](https://github.com/morluto/rea/commit/10aa74dfedc3ae776f50d1fa1eb83b64ae82d3d6), [204b9f3](https://github.com/morluto/rea/commit/204b9f3ac140a993c3e458bb0e117de31818ab29), [b3389a5](https://github.com/morluto/rea/commit/b3389a5b0834265fe7a40391be315d810a53a97e), [a2e3016](https://github.com/morluto/rea/commit/a2e30168a046f3b79319eb7fbaf807b802104199), [ba98130](https://github.com/morluto/rea/commit/ba98130049fa40ade66b03611ff70c7ddc011a1d), [c5fb86d](https://github.com/morluto/rea/commit/c5fb86d1948af0a287a581b29b2b1d554743c607)). Thanks @akushonkamen, @HarsH-1877, @kaoru0822-kitauji, @xingzihai.
-- **Session ordering:** Keep snapshot admission ahead of later calls on the same connection, retain shutdown signals until cleanup succeeds, and preserve inspection authority through investigation publication. ([#3661](https://github.com/morluto/rea/pull/3661), [morluto/rea#3334](https://github.com/morluto/rea/issues/3334), [8873b39](https://github.com/morluto/rea/commit/8873b39770e89eae22b7693bc492d7e423b22bea), [663d07f](https://github.com/morluto/rea/commit/663d07f02cd62c99d81c59391d2c6d745c875335)). Thanks @coygeek, @rudycelekli, @Swatantra-66.
-- **JavaScript exports and resolution:** Retain CommonJS exports created with `Object.defineProperty` and track export receiver lifetimes. Resolve scoped packages, package `main`, JSON requires and `.mts`/`.cts` imports using the owning loader; overwritten `require` bindings and erased type-only imports no longer create false runtime links. ([#4725](https://github.com/morluto/rea/pull/4725), [morluto/rea#4724](https://github.com/morluto/rea/issues/4724), [#3567](https://github.com/morluto/rea/pull/3567), [morluto/rea#3541](https://github.com/morluto/rea/issues/3541), [#4838](https://github.com/morluto/rea/pull/4838), [morluto/rea#4632](https://github.com/morluto/rea/issues/4632), [#3844](https://github.com/morluto/rea/pull/3844), [morluto/rea#3383](https://github.com/morluto/rea/issues/3383), [#4164](https://github.com/morluto/rea/pull/4164), [morluto/rea#3915](https://github.com/morluto/rea/issues/3915), [#4223](https://github.com/morluto/rea/pull/4223), [#3801](https://github.com/morluto/rea/pull/3801), [morluto/rea#3393](https://github.com/morluto/rea/issues/3393), [#4165](https://github.com/morluto/rea/pull/4165), [morluto/rea#3932](https://github.com/morluto/rea/issues/3932)). Thanks @Abishek0070, @coygeek, @JNTMTMTM, @kaoru0822-kitauji, @prasad2512, @rodricksz4h5, @xu91102.
-- **JavaScript value flow:** Preserve values captured before later assignments, guarded factory fallthrough and nested destructuring. Track exact property keys and setter writes; direct `eval`, compound assignments and incoming callbacks preserve unresolved effects instead of inventing certainty. ([#4196](https://github.com/morluto/rea/pull/4196), [morluto/rea#3881](https://github.com/morluto/rea/issues/3881), [#4341](https://github.com/morluto/rea/pull/4341), [morluto/rea#3963](https://github.com/morluto/rea/issues/3963), [bfb7ed0](https://github.com/morluto/rea/commit/bfb7ed0bd43edc605e00fc52c6e21e735b285904), [#3480](https://github.com/morluto/rea/pull/3480), [#3831](https://github.com/morluto/rea/pull/3831), [morluto/rea#3312](https://github.com/morluto/rea/issues/3312), [9ac76d3](https://github.com/morluto/rea/commit/9ac76d3d9486856d25395b413d7ac5ffa744cad0), [#4342](https://github.com/morluto/rea/pull/4342), [morluto/rea#4206](https://github.com/morluto/rea/issues/4206), [#4243](https://github.com/morluto/rea/pull/4243), [morluto/rea#3880](https://github.com/morluto/rea/issues/3880)). Thanks @coygeek, @kaoru0822-kitauji, @maxazure, @N0zoM1z0, @ShuaixinHuang.
-- **JavaScript relationships:** Distinguish `Map` reads from network endpoints, associate response endpoints only with writes that reach the read, and preserve child-process receiver ownership and effective stdio choices. Version comparisons keep relocation and unknown relationships distinct from application changes. ([fbfdb6a](https://github.com/morluto/rea/commit/fbfdb6abe9d663be0be146a15a489e33ccba0f68), [#4759](https://github.com/morluto/rea/pull/4759), [morluto/rea#4606](https://github.com/morluto/rea/issues/4606), [#3819](https://github.com/morluto/rea/pull/3819), [morluto/rea#3362](https://github.com/morluto/rea/issues/3362), [#4336](https://github.com/morluto/rea/pull/4336), [morluto/rea#3355](https://github.com/morluto/rea/issues/3355), [556504e](https://github.com/morluto/rea/commit/556504edcbb0f8cd9eaf81a91b18ff891b8f5457), [4d980d0](https://github.com/morluto/rea/commit/4d980d017622d3175d86aaf3b0dcfbdf4ca3d091)). Thanks @Abdooo2235, @coygeek, @kaoru0822-kitauji, @Xinglan233.
-- **JavaScript source admission:** Parse JavaScript with its own grammar, refuse FIFO recovery inputs without blocking, and report oversized or resource-skipped files with their actual capacity and coverage state. Malformed runtime events stay excluded rather than becoming policy-filtered facts. ([#3782](https://github.com/morluto/rea/pull/3782), [morluto/rea#3780](https://github.com/morluto/rea/issues/3780), [#3788](https://github.com/morluto/rea/pull/3788), [morluto/rea#3332](https://github.com/morluto/rea/issues/3332), [#4757](https://github.com/morluto/rea/pull/4757), [morluto/rea#4629](https://github.com/morluto/rea/issues/4629), [#3852](https://github.com/morluto/rea/pull/3852), [morluto/rea#3670](https://github.com/morluto/rea/issues/3670), [#4755](https://github.com/morluto/rea/pull/4755), [morluto/rea#4685](https://github.com/morluto/rea/issues/4685)). Thanks @andresaragon, @coygeek, @kaoru0822-kitauji, @sx4im.
-- **Browser capture:** Bound CDP handshakes and command responses, preserve malformed inventory uncertainty and partial cleanup diagnostics, and report cancellation after content reads and final cleanup. Accessibility comparisons require observed coverage; attached emulation teardown limits remain explicit. ([#3555](https://github.com/morluto/rea/pull/3555), [morluto/rea#3553](https://github.com/morluto/rea/issues/3553), [#3901](https://github.com/morluto/rea/pull/3901), [morluto/rea#3379](https://github.com/morluto/rea/issues/3379), [4cc044b](https://github.com/morluto/rea/commit/4cc044be68f813e96907e6cedcf422d0a3170de3), [#4406](https://github.com/morluto/rea/pull/4406), [morluto/rea#4403](https://github.com/morluto/rea/issues/4403), [#2893](https://github.com/morluto/rea/pull/2893), [0123d59](https://github.com/morluto/rea/commit/0123d5976828bfe621bd51daa4cf39fee48a1349), [2ff0867](https://github.com/morluto/rea/commit/2ff086796ad7b8f60397956750584e170dbe2910)). Thanks @coygeek, @dakjdakd, @kaoru0822-kitauji, @maxazure, @N0zoM1z0, @YunzhouLi-hub.
-- **Browser page facts:** Preserve URL path bytes when removing credentials, repeated document `Link` headers and complete COOP/COEP structured items. WebMCP discovery reads the actual schema properties and exact receiver path. ([#4731](https://github.com/morluto/rea/pull/4731), [df2fc25](https://github.com/morluto/rea/commit/df2fc251e318a1255309dba232f9f73c700777b6), [c360cfc](https://github.com/morluto/rea/commit/c360cfcd6d7901514b16dd6113eba2e0b0fdf422), [ebd5a82](https://github.com/morluto/rea/commit/ebd5a82c439f6deb3a06062225ce009eb03257cf), [38f92d1](https://github.com/morluto/rea/commit/38f92d108e3148cdf47e4ffbfe3de8a76e795d51)). Thanks @Abdooo2235, @geekwolf, @ShuaixinHuang.
-- **Electron runtime capture:** Keep native IPC listener and one-shot dispatch behavior, block synchronous shell effects during capture, refuse active scenarios when the inspect fuse is disabled, and preserve fuse/transport cleanup ownership. ([#4389](https://github.com/morluto/rea/pull/4389), [morluto/rea#4390](https://github.com/morluto/rea/issues/4390), [#4605](https://github.com/morluto/rea/pull/4605), [morluto/rea#4593](https://github.com/morluto/rea/issues/4593), [#4562](https://github.com/morluto/rea/pull/4562), [morluto/rea#4393](https://github.com/morluto/rea/issues/4393), [#3605](https://github.com/morluto/rea/pull/3605), [morluto/rea#3453](https://github.com/morluto/rea/issues/3453), [f9de413](https://github.com/morluto/rea/commit/f9de41371f7536e2e22ce6e43c9314fa2f238a30), [e7df00e](https://github.com/morluto/rea/commit/e7df00e80777757b329bbe8aba6d421d8892b9d5)). Thanks @Adolanium, @gensokyo-dev, @gkobayashi0, @HarsH-1877, @kaoru0822-kitauji, @keeponlight, @N0zoM1z0, @Nitin13-git, @xu91102.
-- **APK resource accuracy:** Retain completed tables and decode facts after interrupted or failed reads. Derive locale limits from resource configuration fields, disclose unselectable qualified tables, distinguish document failures from omitted entries, and bind Evidence to the decoded snapshot. ([34a88d6](https://github.com/morluto/rea/commit/34a88d6c1674710953e2c94bd0a17332cd69ca6f), [f5fcf52](https://github.com/morluto/rea/commit/f5fcf5216ffb3a266b8c00f6d9a0943051084ab5), [6385ef4](https://github.com/morluto/rea/commit/6385ef4355d7a794b3154ee38529cbddee583336), [98886ad](https://github.com/morluto/rea/commit/98886adddfcbd7b4f4236b3a9825f91878c3cb11), [dc2e811](https://github.com/morluto/rea/commit/dc2e8117b60c4481372ed89b077e6c1cf81ee653), [#4771](https://github.com/morluto/rea/pull/4771), [morluto/rea#4768](https://github.com/morluto/rea/issues/4768)). Thanks @abhay-2108, @gensokyo-dev, @Iyanuoluwa007, @kaoru0822-kitauji, @N0zoM1z0.
-- **Apktool guidance:** Retain the observed version and disclose the matching platform/release advisory windows without treating a version string as proof of decoder safety. Missing prerequisites and decode refusals identify the selected APK or launcher. ([d38f099](https://github.com/morluto/rea/commit/d38f099692394ec90c582f9f0a14b036b421b160), [63696d2](https://github.com/morluto/rea/commit/63696d277328f556c971d1fc9f81ae83128d468b), [cc038da](https://github.com/morluto/rea/commit/cc038da218cada68c87700477aba3db4739791ff)). Thanks @GovinduSasanka, @peter-research.
-- **Android method bodies:** Recover original bytecode bodies when Java source is omitted while preserving genuine native/abstract body absence and primary failures during retryable cleanup. ([63c65a2](https://github.com/morluto/rea/commit/63c65a22430a4bbc0c1807a0298edb867775001f), [742b6f5](https://github.com/morluto/rea/commit/742b6f587f3c4ef1b8212e7376d6f3a305b194dc), [9fa6d2b](https://github.com/morluto/rea/commit/9fa6d2b254cc390665974efb52463386a029e9fc)). Thanks @balkan16, @Chessing234.
-- **ADB observations and transfers:** Preserve display-scoped focus, distinguish missing declarations from absent focus, retain numeric physical density and mark unknown permission coverage partial. Transfers use consumed snapshot identity and refuse unknown destination existence; uninstall requests explicitly select user zero. ([7086768](https://github.com/morluto/rea/commit/7086768a27242a15daa93486aefbaacc3c891e78), [3d028db](https://github.com/morluto/rea/commit/3d028dbc74a465f6f8df1813a931fbb5362e7dc3), [#4074](https://github.com/morluto/rea/pull/4074), [morluto/rea#3942](https://github.com/morluto/rea/issues/3942), [#4663](https://github.com/morluto/rea/pull/4663), [#4665](https://github.com/morluto/rea/pull/4665), [1342127](https://github.com/morluto/rea/commit/1342127e91d4db8b4113a7a4e85be909bc96e1db), [61e6880](https://github.com/morluto/rea/commit/61e688070f48016b6d178cd04c02fcc2f33e19ad), [be0b2d1](https://github.com/morluto/rea/commit/be0b2d138c46bb951fc3c8ee57ef7b0d57fed312)). Thanks @Copilot, @coygeek, @gongfpp, @Tapraj-Pathak, @yankikucuk.
-- **Apple metadata:** Preserve exact plist/keyed-archive integers, negative zero, non-finite real identity and dictionary keys. Reject malformed XML before value decoding, retain undecodable dates as unknown and report unsupported OpenStep entries explicitly. ([#4324](https://github.com/morluto/rea/pull/4324), [morluto/rea#4292](https://github.com/morluto/rea/issues/4292), [2cf9c28](https://github.com/morluto/rea/commit/2cf9c28f27261b7e64af2ba7ecb4e23ea7714aee), [#4839](https://github.com/morluto/rea/pull/4839), [morluto/rea#4834](https://github.com/morluto/rea/issues/4834), [f2b7bbb](https://github.com/morluto/rea/commit/f2b7bbb31279a820f4cf32d439570f8e5381d010), [6c98708](https://github.com/morluto/rea/commit/6c98708793c23615de8053b2cd14d9f164b960c5), [78cf610](https://github.com/morluto/rea/commit/78cf6100f33ad2412c0a3d60b83f8a44a43fbbb5), [c7e9e09](https://github.com/morluto/rea/commit/c7e9e096d3e2444e4c251123b8e914e9c0941f4e), [#3793](https://github.com/morluto/rea/pull/3793), [#4105](https://github.com/morluto/rea/pull/4105), [morluto/rea#3892](https://github.com/morluto/rea/issues/3892)). Thanks @coygeek, @kaoru0822-kitauji, @mertkayacs, @pablodiazjorge, @pollychen-lab, @xu91102.
-- **Apple application structure:** Derive bundle components and launchd domains from their owning directories, retain unavailable components, and select only exact `Assets.car` names as asset catalogs. Interface Builder keeps unresolved classes and counts hierarchy records beyond the returned object page. ([149a0fc](https://github.com/morluto/rea/commit/149a0fc06c3c67ee45624e6da14dfb0754473758), [5d6029e](https://github.com/morluto/rea/commit/5d6029ea62a65ec34fd739ee40223c77c6fdb63b), [c192c58](https://github.com/morluto/rea/commit/c192c58815ddeaf5cf30159e7082c742c0bc36b7), [#4094](https://github.com/morluto/rea/pull/4094), [morluto/rea#3914](https://github.com/morluto/rea/issues/3914), [#4118](https://github.com/morluto/rea/pull/4118), [morluto/rea#3958](https://github.com/morluto/rea/issues/3958), [#4162](https://github.com/morluto/rea/pull/4162), [morluto/rea#3950](https://github.com/morluto/rea/issues/3950)). Thanks @coygeek, @kaoru0822-kitauji.
-- **Native names and layout:** Keep valid Objective-C records beside malformed neighbors, preserve leading U+FEFF and repeated load-command fields, and select exact arm64e.x1 slices. PE resource ownership and NativeAOT reads stay within declared image/header ranges. ([#3833](https://github.com/morluto/rea/pull/3833), [morluto/rea#3336](https://github.com/morluto/rea/issues/3336), [#4549](https://github.com/morluto/rea/pull/4549), [morluto/rea#4540](https://github.com/morluto/rea/issues/4540), [morluto/rea#4541](https://github.com/morluto/rea/issues/4541), [#4730](https://github.com/morluto/rea/pull/4730), [#4048](https://github.com/morluto/rea/pull/4048), [morluto/rea#4008](https://github.com/morluto/rea/issues/4008), [#3500](https://github.com/morluto/rea/pull/3500), [morluto/rea#3389](https://github.com/morluto/rea/issues/3389), [#4463](https://github.com/morluto/rea/pull/4463), [morluto/rea#4373](https://github.com/morluto/rea/issues/4373), [morluto/rea#4455](https://github.com/morluto/rea/issues/4455), [3fc0075](https://github.com/morluto/rea/commit/3fc007534bb2104d662b43cc712281f9d1d6a7d3), [4a076f3](https://github.com/morluto/rea/commit/4a076f368c62bdfb19415accad342e03a38d1005)). Thanks @coygeek, @Iyanuoluwa007, @jayinvers, @kaoru0822-kitauji, @kevinjosh10, @maxazure, @ShuaixinHuang.
-- **Native analysis providers:** Keep Ghidra byte matches within examined coverage, retain PE PDB/function-boundary limitations and preserve configured MIPS choices. Attached IDA refuses universal Mach-O rather than silently choosing a slice; request timeout identity and captured output survive adapter handling. ([#4531](https://github.com/morluto/rea/pull/4531), [#2933](https://github.com/morluto/rea/pull/2933), [morluto/rea#2259](https://github.com/morluto/rea/issues/2259), [01a1b3f](https://github.com/morluto/rea/commit/01a1b3fda6a7dacd24a0b10619d41d12153080d4), [50dd9fc](https://github.com/morluto/rea/commit/50dd9fcad1efb47cb404192c30bdf190dcdaca58), [#4765](https://github.com/morluto/rea/pull/4765), [morluto/rea#3871](https://github.com/morluto/rea/issues/3871), [c0cfccb](https://github.com/morluto/rea/commit/c0cfccb45fe43e7eeff18e56c64caa5b121988f9)). Thanks @BeLit-Development-2, @coygeek, @kaoru0822-kitauji, @N0zoM1z0, @ShuaixinHuang.
-- **Recorded crashes:** Prevent GDB from discovering an executable named by an untrusted core, reject core mapping paths that escape the isolated sysroot, and preserve pwntools worker ownership across launcher exec. Completed decode facts and cancellation reasons remain available through failed final cleanup. ([5bf4fff](https://github.com/morluto/rea/commit/5bf4fffc1b835130ddb16f96db9ce13b639591db), [b33c0df](https://github.com/morluto/rea/commit/b33c0df02e93fabca00a44f2de625b1a63637ee9), [#4435](https://github.com/morluto/rea/pull/4435), [morluto/rea#4011](https://github.com/morluto/rea/issues/4011)). Thanks @coygeek, @N0zoM1z0.
-- **Cutter and Rizin:** Read Cutter’s active document from core configuration and attribute its host version correctly. Keep interrupted Rizin frames and output whitespace before completion markers, with exact command and cleanup failure attribution. ([#4507](https://github.com/morluto/rea/pull/4507), [morluto/rea#4497](https://github.com/morluto/rea/issues/4497), [#4514](https://github.com/morluto/rea/pull/4514), [morluto/rea#4498](https://github.com/morluto/rea/issues/4498), [#4459](https://github.com/morluto/rea/pull/4459), [morluto/rea#4015](https://github.com/morluto/rea/issues/4015), [d5fc7e6](https://github.com/morluto/rea/commit/d5fc7e6ebf9af050081fc4c6e18b9079cfaa5cdc), [199396f](https://github.com/morluto/rea/commit/199396f61c8f61da326d059606a992304a760147)). Thanks @coygeek, @N0zoM1z0, @Xander-AJ.
-- **Windows cleanup:** Retain unpublished runtimes after failed removal, handle read-only attributes and sharing conflicts, preserve primary snapshot failures and honor caller environment overrides. ([f78d137](https://github.com/morluto/rea/commit/f78d137b42741a0ed5fb8ac161286f9a50220c4d), [d69acc3](https://github.com/morluto/rea/commit/d69acc3455c33f90a2fc4381db43d38b6af50622), [0679a79](https://github.com/morluto/rea/commit/0679a7972b4f2b02eee6a86a44f50f4c2967d3cb), [5f9ac2c](https://github.com/morluto/rea/commit/5f9ac2c98a6fe11988c41afb737df9b6d5c3a1b3), [1bbf4bd](https://github.com/morluto/rea/commit/1bbf4bd16ca134cdb2187eaf29291cae90d14a57)). Thanks @DeryFerd.
-- **Managed metadata:** Compare nominal signatures and declaring identities across builds, preserve empty names without display substitutions, verify ABI-prefixed Mach-O exports exactly, and charge cached metadata once. Metadata errors report artifact file offsets; mixed-mode assemblies retain their actual boundary classification. ([#3059](https://github.com/morluto/rea/pull/3059), [#3079](https://github.com/morluto/rea/pull/3079), [#3853](https://github.com/morluto/rea/pull/3853), [morluto/rea#3352](https://github.com/morluto/rea/issues/3352), [#3974](https://github.com/morluto/rea/pull/3974), [morluto/rea#3961](https://github.com/morluto/rea/issues/3961), [#3491](https://github.com/morluto/rea/pull/3491), [morluto/rea#3449](https://github.com/morluto/rea/issues/3449), [#4418](https://github.com/morluto/rea/pull/4418), [morluto/rea#4372](https://github.com/morluto/rea/issues/4372), [#3516](https://github.com/morluto/rea/pull/3516), [morluto/rea#3366](https://github.com/morluto/rea/issues/3366)). Thanks @8rulerstar, @coygeek, @duckhunt113, @Hahaa909, @JayOfTheKeyboard, @kaoru0822-kitauji, @keeponlight, @N0zoM1z0, @tomyrms.
-- **Archive and filesystem identity:** Reject colliding extraction paths before writing, classify ZIP offsets beyond EOF as malformed, normalize ZIP current-directory prefixes once, and preserve symlink and unreadable-path provenance. A directory named `*.map` is no longer mistaken for a source-map file. ([862a0b2](https://github.com/morluto/rea/commit/862a0b2631785492f8dc20c8acd396646c545fd1), [c209dcb](https://github.com/morluto/rea/commit/c209dcb209118069f123e789949eeba1ef78853e), [6b1c36e](https://github.com/morluto/rea/commit/6b1c36e336eeacbb7159b211e687b4b84f99b9f5), [25c2222](https://github.com/morluto/rea/commit/25c22222abe7a681491bdb4d7316250fdcf32973), [d6e4fe4](https://github.com/morluto/rea/commit/d6e4fe4a4dd8914ec3db50d2a7fc3d0802649262), [#4131](https://github.com/morluto/rea/pull/4131), [morluto/rea#3909](https://github.com/morluto/rea/issues/3909)). Thanks @Adkid-Zephyr, @coygeek, @jackie-cqz, @kaoru0822-kitauji, @maxazure, @XY-code1.
-- **Evidence and reconstruction:** Authenticate all retained inventory substeps, preserve source-attributed caveats in composed workflows, and require comparable cited Evidence before declaring reconstruction coverage or readiness. Missing Evidence and residual replay uncertainty stay explicit. ([9ac91e0](https://github.com/morluto/rea/commit/9ac91e0c1e13e91cd21341635ad5be89b0e8642d), [c4608a2](https://github.com/morluto/rea/commit/c4608a29620ea3e7bb8259b47357b942fe4e4709), [#4075](https://github.com/morluto/rea/pull/4075), [morluto/rea#3357](https://github.com/morluto/rea/issues/3357), [#3526](https://github.com/morluto/rea/pull/3526), [morluto/rea#3363](https://github.com/morluto/rea/issues/3363), [153017d](https://github.com/morluto/rea/commit/153017d750322188c1a112b2284c1b8065c67320)). Thanks @coygeek, @gensokyo-dev, @kaoru0822-kitauji, @N0zoM1z0, @rudycelekli.
-- **Offline data:** Preserve exact UTC packet-capture instants, SQLite column identity and snapshot admission failures, and cooked WASM directive literals. Cleanup cancellation retains completed EVM/WASM observations rather than losing them. ([796faa0](https://github.com/morluto/rea/commit/796faa0e4e6bf745bcdc33acef65af8ccfc3622d), [748ac7f](https://github.com/morluto/rea/commit/748ac7f0df340f0d0569eca2e803a59cd51ffdbd), [bc51d0e](https://github.com/morluto/rea/commit/bc51d0ea5df7dcee1fcc42dfae3ab0c62c9cca5e), [4f87f02](https://github.com/morluto/rea/commit/4f87f02bb19bf77349a683a5bcb2da2d1da427d0), [d694aef](https://github.com/morluto/rea/commit/d694aef227e90164e6654ea9e5ce6a854d099404), [321cacb](https://github.com/morluto/rea/commit/321cacb84a020f447e1110df5c58fa71d99b7bf1)). Thanks @himamaheswarreddy, @mertkayacs, @rollroyces, @viniciusdsandrade.
-- **Kuna recovery:** Share concurrent single-function requests and cache repeats, validate warm exports once, stream string inventories beyond the former fixed buffer ceiling, and keep unproven processes in their run slots until close confirms release. Failure messages distinguish final buffer refusals from configurable deadlines. ([#4045](https://github.com/morluto/rea/pull/4045), [#4169](https://github.com/morluto/rea/pull/4169), [#4049](https://github.com/morluto/rea/pull/4049), [#4318](https://github.com/morluto/rea/pull/4318), [#4052](https://github.com/morluto/rea/pull/4052), [#4098](https://github.com/morluto/rea/pull/4098), [#4343](https://github.com/morluto/rea/pull/4343)). Thanks @kaoru0822-kitauji.
-- **Flutter snapshots:** Check symbol-table ranges against loadable segments and retain completed inspection facts when cancellation occurs during snapshot cleanup. ([#3859](https://github.com/morluto/rea/pull/3859), [morluto/rea#3346](https://github.com/morluto/rea/issues/3346), [#4766](https://github.com/morluto/rea/pull/4766), [morluto/rea#4717](https://github.com/morluto/rea/issues/4717), [#4762](https://github.com/morluto/rea/pull/4762), [morluto/rea#4640](https://github.com/morluto/rea/issues/4640)). Thanks @coygeek, @kaoru0822-kitauji.
-- **Native metadata recovery:** Keep unknown Objective-C category classes, empty protocol names, undecoded Swift aliases and unfinished property types explicit instead of discarding neighboring valid records. Preserve unnamed segment identity and exclude a dylib’s own install name from dependencies. ([#4093](https://github.com/morluto/rea/pull/4093), [morluto/rea#4012](https://github.com/morluto/rea/issues/4012), [#4078](https://github.com/morluto/rea/pull/4078), [morluto/rea#3873](https://github.com/morluto/rea/issues/3873), [#4085](https://github.com/morluto/rea/pull/4085), [morluto/rea#3934](https://github.com/morluto/rea/issues/3934), [#3825](https://github.com/morluto/rea/pull/3825), [morluto/rea#3345](https://github.com/morluto/rea/issues/3345), [#4051](https://github.com/morluto/rea/pull/4051), [morluto/rea#3875](https://github.com/morluto/rea/issues/3875), [#4050](https://github.com/morluto/rea/pull/4050), [morluto/rea#3872](https://github.com/morluto/rea/issues/3872)). Thanks @coygeek, @kaoru0822-kitauji.
-- **Document selection:** Preserve explicitly selected plist paths and bundle defaults, and only use document fallback after confirming its applicability. Finalization keeps completed selection facts and cancellation outcomes. ([e6c4877](https://github.com/morluto/rea/commit/e6c487799bb64f559e66b69be1863e6ec5187548), [#3774](https://github.com/morluto/rea/pull/3774), [9df559b](https://github.com/morluto/rea/commit/9df559b7e712298a761ff26e9caae8d659b7e54b)). Thanks @kaoru0822-kitauji.
-- **Capture and comparison accuracy:** Admit schema-valid HAR numeric values while retaining exact-publication limits, preserve empty URL path segments, and keep unrelated process traces and unnamed reference endpoints distinct or unknown. ([#3159](https://github.com/morluto/rea/pull/3159), [morluto/rea#3145](https://github.com/morluto/rea/issues/3145), [#3792](https://github.com/morluto/rea/pull/3792), [morluto/rea#3307](https://github.com/morluto/rea/issues/3307), [#4178](https://github.com/morluto/rea/pull/4178), [morluto/rea#3931](https://github.com/morluto/rea/issues/3931), [#3809](https://github.com/morluto/rea/pull/3809), [morluto/rea#3388](https://github.com/morluto/rea/issues/3388)). Thanks @coygeek, @gensokyo-dev, @kaoru0822-kitauji, @N0zoM1z0, @pablodiazjorge, @xu91102.
-- **Evidence publication:** Recheck staged output identity after its final write, classify missing review Evidence and duplicate ledger entries as caller input, and preserve the selected freshness requirement in comparison parameters. ([#4764](https://github.com/morluto/rea/pull/4764), [morluto/rea#4613](https://github.com/morluto/rea/issues/4613), [#4452](https://github.com/morluto/rea/pull/4452), [morluto/rea#4444](https://github.com/morluto/rea/issues/4444), [#4065](https://github.com/morluto/rea/pull/4065), [morluto/rea#4000](https://github.com/morluto/rea/issues/4000)). Thanks @amyanger, @coygeek, @kaoru0822-kitauji, @Rinkia, @Swatantra-66.
-
-### ⚠ BREAKING CHANGES
-
-- **Saved Evidence:** Evidence and analysis snapshots now require explicit nullable `relationship_coverage` in their identity commitments. Artifact inventories require scoped coverage and explicit `integrity_contradictions`; obsolete `coverage_status` and prose-based coverage inference are removed. Regenerate old Evidence/snapshots and inventory observations with this release: saved files are not migrated and omitted facts are not filled with guessed defaults. ([db8128d](https://github.com/morluto/rea/commit/db8128dc0d1c4f731f3d19877fa00d25cf17f657), [0405c9d](https://github.com/morluto/rea/commit/0405c9d361de6d904dfa16cc0b6d8350407f2c9b), [a9588be](https://github.com/morluto/rea/commit/a9588be4ebdd20eeda975cb63ffcdb1cd868b340)).
-- **Browser capture results:** Consumers must retain resolved capture limits, event families and omission facts. Set desired budgets through the supported capture options; omitted caller inputs still select defaults, but stored observations must report the resolved values. Admitted content reads queue behind bounded concurrency. ([57a23f0](https://github.com/morluto/rea/commit/57a23f0a2da0fdc3835e203718ded8acea5a34e6)).
-- **Android version codes:** `inspect_adb_package.version_code` is a decimal string rather than a JSON number. Read it as a string, or use `BigInt` for numeric comparison. ([#3485](https://github.com/morluto/rea/pull/3485), [morluto/rea#3368](https://github.com/morluto/rea/issues/3368), [7666a48](https://github.com/morluto/rea/commit/7666a482b69dc7cabdbac3bbaf89a43e32300192)). Thanks @coygeek, @kaoru0822-kitauji.
-- **Native UI failures:** Failed or cancelled native UI scenarios now return typed errors with the collected report in `partial_observation`. Handle the error path and read that report instead of expecting a successful result containing failed steps. ([d909919](https://github.com/morluto/rea/commit/d9099190ab3a819bd3a9fd62a8714cef398016d5)).
-- **Provider status:** `binary_session` candidate availability can be unknown during owner finalization. Preserve that state rather than treating it as unavailable; internal consumers must await the asynchronous session status API. ([150e996](https://github.com/morluto/rea/commit/150e996a86f2bec4982ba87f37bf502a8d5e8214)).
-- **Swift symbol locations:** `swift_symbols` entries may have a null `address` when the provider supplies no location. Handle unknown addresses; optional `evidence.reported_address` retains the original provider value. ([8116dc0](https://github.com/morluto/rea/commit/8116dc06512b4609d8db63cebc9f2ff8cb964151)).
-- **Linux Hopper admission:** Older builds previously admitted by a fixed allowlist need retained publisher-signed package evidence or an approved update to the current public demo. Update explicit `HOPPER_LAUNCHER_PATH` selections when migrating; the live feed offers only its current release. The official RPM metadata mismatch remains unresolved and is refused. ([#3590](https://github.com/morluto/rea/pull/3590), [morluto/rea#3577](https://github.com/morluto/rea/issues/3577), [70cd4cb](https://github.com/morluto/rea/commit/70cd4cbfb849b61f05d97d2690372a9782831426)). Thanks @gensokyo-dev, @kaoru0822-kitauji, @N0zoM1z0.
-
-Full contribution record: [571 commits and 236 merged PRs](https://github.com/morluto/rea/blob/rea-agents-6.6.0/docs/releases/6.6.0.contributions.json).
-
-## [6.5.0](https://github.com/morluto/rea/compare/rea-agents-6.4.0...rea-agents-6.5.0) (2026-10-13)
-
-Provider prerequisites and recorded verification scope are listed in [the testing guide](docs/testing.md).
-
-### Highlights
-
-- Analyze selected JavaScript files and recover cross-bundle relationships without expanding the selected source scope.
-- Read compact summaries and page retained Evidence across binary, managed, Android, Dart, WASM and network workflows.
-- Inspect SQLite snapshots, packet and signal recordings, WebAssembly, Rust dependency metadata and Electron fuses offline.
-- Keep completed Evidence and partial observations available when analysis or cleanup fails.
-
-### Changes
-
-- **JavaScript source selection:** analyze exact application paths without expanding imports into the selected scope. Unselected files retain identity and explicit unknown coverage; summary delivery remains separate from source selection. ([#1944](https://github.com/morluto/rea/pull/1944), [issue morluto/rea#1848](https://github.com/morluto/rea/issues/1848)). Thanks @kaoru0822-kitauji, @N0zoM1z0.
-- **Code-split recovery:** recover related bundles from multiple selected inputs, retaining per-file provenance and downstream cross-chunk imports. Recorded CLI/MCP coverage is Linux x64 with Wakaru 1.14.0 and source-owned esbuild/webpack fixtures; other hosts, releases and arbitrary application equivalence remain unverified. ([#1686](https://github.com/morluto/rea/pull/1686), [issue morluto/rea#1605](https://github.com/morluto/rea/issues/1605)). Thanks @JingHao-Leon, @pionxzh.
-- **Package imports:** resolve exact package import aliases using the selected loader and package ancestry, rather than guessing sibling files. ([#1862](https://github.com/morluto/rea/pull/1862), [issue morluto/rea#1838](https://github.com/morluto/rea/issues/1838)). Thanks @AWUQAQ, @mvanhorn.
-- **Retained analysis views:** opt into compact inventory/WASM, managed metadata, Android manifest, Dart AOT, Mach-O and EVM summaries, then page retained Evidence without rerunning analysis. Summary delivery preserves the complete recorded result and its original coverage. ([#2122](https://github.com/morluto/rea/pull/2122), [#2193](https://github.com/morluto/rea/pull/2193), [#2413](https://github.com/morluto/rea/pull/2413), [#2438](https://github.com/morluto/rea/pull/2438), [#2455](https://github.com/morluto/rea/pull/2455), [#2634](https://github.com/morluto/rea/pull/2634), [#2308](https://github.com/morluto/rea/pull/2308), [9a18251](https://github.com/morluto/rea/commit/9a18251426f891e6a24856b715ef8002ab8b9610)). Thanks @kaoru0822-kitauji, @N0zoM1z0.
-- **Managed assemblies:** Select declaring types when inspecting members, decode inspected `ldstr` literals with independent coverage, and page retained member summaries. Call and field targets expose `target_declaring_type` and `field_declaring_type`, including supported generic method targets; unresolved metadata remains unknown. ([#1706](https://github.com/morluto/rea/pull/1706), [#2125](https://github.com/morluto/rea/pull/2125), [issue morluto/rea#2121](https://github.com/morluto/rea/issues/2121), [#2162](https://github.com/morluto/rea/pull/2162), [issue morluto/rea#2158](https://github.com/morluto/rea/issues/2158), [#3061](https://github.com/morluto/rea/pull/3061), [issue morluto/rea#3010](https://github.com/morluto/rea/issues/3010), [#2163](https://github.com/morluto/rea/pull/2163), [issue morluto/rea#2160](https://github.com/morluto/rea/issues/2160)). Thanks @kaoru0822-kitauji, @N0zoM1z0, @Nelglor, @skoodster.
-- **Packet captures:** inspect saved packets with bounded TShark output, compact capture summaries and retained pages; discover installed protocol/field definitions. Recorded real-engine coverage uses Linux and Wireshark 4.6.6; native Windows/macOS and Bun behavior remain unverified. ([#2318](https://github.com/morluto/rea/pull/2318), [#2340](https://github.com/morluto/rea/pull/2340), [#2496](https://github.com/morluto/rea/pull/2496)). Thanks @3QL, @N0zoM1z0, @Olorinm.
-- **Recorded signals:** decode existing recordings and discover installed decoders/options through caller-supplied sigrok-cli 0.7.2. This is Linux-only and requires util-linux `prlimit`; it acquires no hardware samples. ([#2339](https://github.com/morluto/rea/pull/2339), [#2487](https://github.com/morluto/rea/pull/2487)). Thanks @N0zoM1z0, @Olorinm.
-- **Web captures:** derive an inferred method/origin/path-template API surface from retained HAR data including observed query-parameter names while retaining unknowns; query values, headers and bodies remain excluded. ([#1891](https://github.com/morluto/rea/pull/1891), [#2982](https://github.com/morluto/rea/pull/2982), [issue morluto/rea#2913](https://github.com/morluto/rea/issues/2913)). Thanks @mvanhorn, @wunianze666-netizen, @zhangguiping-xydt.
-- **QUIC captures:** inspect retained aioquic 1.5.0 JSON qlog 0.3 objects and page traces/streams/observations. Other qlog layouts remain unsupported; overlap and loss declarations do not prove retransmission or network loss. ([#2277](https://github.com/morluto/rea/pull/2277)). Thanks @LuisTaffelli, @N0zoM1z0.
-- **Fiddler captures:** inspect native SAZ archives with retained HTTP provenance and bounded decoding. Recorded producer coverage is the pinned public encoding corpus; current Fiddler Everywhere variants and Bun-native execution remain unverified. ([#2409](https://github.com/morluto/rea/pull/2409)). Thanks @N0zoM1z0, @zahhak.
-- **SQLite snapshots:** inspect an explicitly selected offline database with table/column selection and bounded Evidence. This operation requires Node 24.x >=24.15 or 26+ with `DatabaseSync.limits`; supported Node 22 and earlier 24 runtimes cannot use it. A live database/WAL copy does not establish an atomic snapshot. ([#2271](https://github.com/morluto/rea/pull/2271)). Thanks @N0zoM1z0, @Y0UW1SH.
-- **WASM artifacts:** Inspect local modules with bring-your-own WABT 1.0.42 without executing them. Compare imports/exports from two complete core-module inspection Evidence records without requiring an active WABT installation; unsupported signatures and duplicate identities remain unknown, and comparisons do not establish runtime compatibility. Recorded real-tool inspection coverage is macOS arm64. ([#1533](https://github.com/morluto/rea/pull/1533), [issue morluto/rea#884](https://github.com/morluto/rea/issues/884), [#2464](https://github.com/morluto/rea/pull/2464), [issue morluto/rea#2356](https://github.com/morluto/rea/issues/2356)). Thanks @matbrgz, @N0zoM1z0, @thangldw.
-- **Go binaries:** inspect embedded build metadata, including file-backed unmapped Mach-O debug segments. ([#1363](https://github.com/morluto/rea/pull/1363), [7fb097d](https://github.com/morluto/rea/commit/7fb097d72c9931dd5dfae481ad2b9d3bb6029f15)). Thanks @Y0UW1SH.
-- **Flutter APKs:** identify snapshot/engine builds and inspect AOT structure without an external engine. Recorded real APK coverage uses the documented Flutter Gallery fixture; macOS/Windows and complete pool semantics remain unverified, and pool coverage stays partial. ([#1582](https://github.com/morluto/rea/pull/1582)). Thanks @3QL.
-- **HarmonyOS packages:** inventory HAP/HSP/App Pack structures without executing code. The recorded real workflow covers one pinned HAP through repository-built CLI/MCP; installed-package and real HSP/App Pack coverage remain unverified. ([#1447](https://github.com/morluto/rea/pull/1447)). Thanks @BaaRai.
-- **Ghidra raw inputs and references:** compatible Linux/macOS Ghidra profiles accept caller-selected raw architecture/entry information and expose typed incoming references at exact addresses. Windows Ghidra P0 admits the raw NMOS 6502 profile described below; other raw targets and the incoming-reference facet remain outside Windows P0. ([#1868](https://github.com/morluto/rea/pull/1868), [issue morluto/rea#1836](https://github.com/morluto/rea/issues/1836), [#1715](https://github.com/morluto/rea/pull/1715), [issue morluto/rea#1245](https://github.com/morluto/rea/issues/1245)). Thanks @bugstan, @casesolved-co-uk, @mvanhorn, @N0zoM1z0.
-- **Ghidra MIPS:** Add bounded MIPS32r2/o32 relocatable objects, soft-float integer-register storage, admitted MIPS16 shared ELF, and a narrowly admitted recordless legacy MIPS32 executable profile. The latter pins an endian-matched 32-bit language and records inferred o32 as an analysis assumption. Admission follows each documented ABI/flag/relocation boundary. ([#1949](https://github.com/morluto/rea/pull/1949), [issue morluto/rea#1937](https://github.com/morluto/rea/issues/1937), [#1950](https://github.com/morluto/rea/pull/1950), [issue morluto/rea#1938](https://github.com/morluto/rea/issues/1938), [#1991](https://github.com/morluto/rea/pull/1991), [issue morluto/rea#1851](https://github.com/morluto/rea/issues/1851), [#1898](https://github.com/morluto/rea/pull/1898), [issue morluto/rea#1620](https://github.com/morluto/rea/issues/1620)). Thanks @AurelioB, @BaaRai, @bqw371, @kaoru0822-kitauji, @N0zoM1z0.
-- **Ghidra RISC-V:** admit little-endian RV32/RV64 `ET_EXEC` ELF declaring the supported double-float ABI. Relocatable/shared, big-endian and other ABI profiles remain refused; see [the profile and recorded lane](docs/ghidra-riscv.md). ([#2151](https://github.com/morluto/rea/pull/2151)). Thanks @NIU-123370.
-- **PSP static ELF profile:** the Ghidra profile is Linux x64, bounded little-endian ELF32 `ET_EXEC` with the documented PSP/ABI declarations and a compatible caller-installed Allegrex extension. PRX, shared/relocatable images, PBP/ISO/CSO and runtime emulation are outside scope. Historical extension experiments are separate from public-provider verification; real public Ghidra PSP coverage remains unverified. ([#1599](https://github.com/morluto/rea/pull/1599)). Thanks @jaelliot.
-- **Ghidra analysis settings:** apply validated analyzer overrides before analysis while retaining the selected analysis profile. ([#1913](https://github.com/morluto/rea/pull/1913)). Thanks @akushonkamen, @kaoru0822-kitauji, @N0zoM1z0.
-- **Attached native IDA MCP:** add an optional native bridge alongside existing legacy/headless profiles. Recorded native runs use Linux IDA Free 9.4 with a navigation correction and Windows IDA Pro 9.3 with a loopback-listener change; stock native switching, native macOS and Windows IDA Free remain unverified. Attached databases remain read-only and are never saved or closed. ([#1544](https://github.com/morluto/rea/pull/1544)). Thanks @imissapixel, @N0zoM1z0.
-- **Frida instrumentation:** add explicit local/remote target selection, caller-supplied scripts and retained messages, with script-read/input diagnostics and bounded message eviction. Recorded real coverage is the Linux local Node marker workflow; macOS, Windows and remote devices/servers remain unverified. Instrumentation executes foreign code and is destructive, not read-only. ([#1359](https://github.com/morluto/rea/pull/1359), [#2211](https://github.com/morluto/rea/pull/2211), [issue morluto/rea#2209](https://github.com/morluto/rea/issues/2209), [#2217](https://github.com/morluto/rea/pull/2217), [issue morluto/rea#2213](https://github.com/morluto/rea/issues/2213), [#2628](https://github.com/morluto/rea/pull/2628)). Thanks @dandgabr, @kaoru0822-kitauji, @N0zoM1z0.
-- **Client setup:** register Qoder, Trae, ZCode, DeepSeek Harness, Kimi Code, Factory Droid and WorkBuddy through the existing scoped setup flow. DeepSeek is included from 6.5.0; the historical npm 6.4 check did not cover it. Live Trae and DeepSeek API integration remain unverified. ([#1564](https://github.com/morluto/rea/pull/1564), [#1572](https://github.com/morluto/rea/pull/1572), [#1573](https://github.com/morluto/rea/pull/1573), [#1929](https://github.com/morluto/rea/pull/1929), [issue morluto/rea#1839](https://github.com/morluto/rea/issues/1839), [#2744](https://github.com/morluto/rea/pull/2744), [#2309](https://github.com/morluto/rea/pull/2309), [#3041](https://github.com/morluto/rea/pull/3041), [issue morluto/rea#3040](https://github.com/morluto/rea/issues/3040)). Thanks @0xRafie, @BaaRai, @cainiao1992, @IvenKooLab, @whoishaha, @ysntony.
-- **Website:** Add maintained language editions, persistent/system-aware themes, keyboard styling and nested Evidence indentation, plus the reverse-engineering models essay. A simpler home page and beginner journey connect platform prerequisites, client/provider setup and a supplied first investigation. ([#1779](https://github.com/morluto/rea/pull/1779), [issue morluto/rea#1022](https://github.com/morluto/rea/issues/1022), [#1699](https://github.com/morluto/rea/pull/1699), [#1714](https://github.com/morluto/rea/pull/1714), [#1894](https://github.com/morluto/rea/pull/1894), [#2250](https://github.com/morluto/rea/pull/2250), [#2432](https://github.com/morluto/rea/pull/2432), [#2732](https://github.com/morluto/rea/pull/2732), [#3274](https://github.com/morluto/rea/pull/3274)). Thanks @CassieFox23, @kaoru0822-kitauji, @N0zoM1z0.
-
-- **Rust dependency metadata:** Inspect embedded cargo-auditable package/dependency records in ELF, PE and thin Mach-O without executing the file. Missing metadata and inferred compiler hashes retain explicit limitations; universal Mach-O requires a selected thin slice. ([#2456](https://github.com/morluto/rea/pull/2456)). Thanks @mvanhorn.
-- **Electron fuses:** Read packaged fuse bytes and per-slice runtime implications without launching or modifying the app. Missing, truncated and unknown wires remain explicit; fuse observations do not prove other Inspector-enablement paths. ([#2399](https://github.com/morluto/rea/pull/2399)). Thanks @kaoru0822-kitauji, @mvanhorn, @N0zoM1z0.
-- **Ghidra PowerPC:** Admit bounded ELF32 big-endian `ET_EXEC` PowerPC with an explicit language profile on supported Linux/macOS hosts. PPC64, DOL and other variants remain outside this lane; see [the profile and verification prerequisites](docs/ghidra-ppc.md). ([#1747](https://github.com/morluto/rea/pull/1747)). Thanks @arielfikru.
-
-- **Reference-source summaries:** Use CLI `import-reference-source --detail summary` for compact manifest, count, state and path-outline output. The complete graph remains available and is still the default; hidden outline entries retain separate coverage counts. ([#2768](https://github.com/morluto/rea/pull/2768), [issue morluto/rea#2442](https://github.com/morluto/rea/issues/2442)). Thanks @matbrgz, @To3akaRin.
-
-- **Recorded AArch64 crashes:** Decode 34 ABI register values per thread from supported Linux ELF64 little-endian core notes using the documented caller-provided Python dependencies. These are recorded facts, not proof of current process or library identity. ([#2505](https://github.com/morluto/rea/pull/2505), [issue morluto/rea#2353](https://github.com/morluto/rea/issues/2353)). Thanks @matbrgz, @NIU-123370.
-
-- **Ghidra byte search:** Search initialized analyzed memory using wildcards, bit masks, address bounds and paged results. Unloaded, overlay and uninitialized blocks retain skipped coverage; this is not a raw-file search. ([#2341](https://github.com/morluto/rea/pull/2341)). Thanks @mvanhorn.
-
-- **Raw NMOS 6502 images:** Analyze explicitly selected headerless images with Ghidra, including Windows P0, using a caller-selected entry and source mapping within the 16-bit address space. Cartridge parsing, reset-vector inference and 65C02/65816 are outside this profile. ([#2079](https://github.com/morluto/rea/pull/2079)). Thanks @Zhong-fan.
-
-- **Swift String observations:** Ghidra function dossiers derive supported AArch64 Swift String literals from constant-register pairs at recognized use sites, retaining instruction/register provenance and explicit omissions. This is a bounded derivation, not a complete string inventory. ([#2049](https://github.com/morluto/rea/pull/2049), [issue morluto/rea#2030](https://github.com/morluto/rea/issues/2030)). Thanks @thefolahan.
-
-- **Headless IDA procedure lookup:** Resolve addresses to canonical containing-procedure entries and identify the session’s admitted program document in the modern headless profile. Incomplete surveys remain errors; attached profiles do not advertise this containment capability. ([#2374](https://github.com/morluto/rea/pull/2374), [issue morluto/rea#2335](https://github.com/morluto/rea/issues/2335)). Thanks @nikolay-dementiev.
-
-- **Passive browser attachment:** Six existing passive browser tools accept an explicit-port loopback browser WebSocket endpoint when HTTP target discovery is unavailable. Existing consent and target/origin checks remain required; this does not launch a browser or enable runtime instrumentation. ([#2346](https://github.com/morluto/rea/pull/2346)). Thanks @all-black-493.
-
-- **Android DEX references:** Retain exact method descriptors and individual direct-invoke observations with source method, DEX entry, opcode and code-unit offset. These are static references; unavailable instruction facts remain separate from method-level usage totals. ([#2439](https://github.com/morluto/rea/pull/2439)). Thanks @LcokHcak.
-
-- **Offline EVM metadata:** Retain bounded, lossless facts from plausible terminal Solidity CBOR root-map candidates. Candidates do not prove Solidity origin or source/compiler identity, and linked metadata is not fetched. ([#2790](https://github.com/morluto/rea/pull/2790)). Thanks @matbrgz.
-
-### Fixes
-
-- **JavaScript loader and export identity:** Respect import/require conditions and unavailable package metadata, keep export links separate from writes, and resolve default identifier exports to the value captured at the export statement. ([7e5cffa](https://github.com/morluto/rea/commit/7e5cffa2ae9dfc9afaeca0715110d4dd41c0dcdd), [322506d](https://github.com/morluto/rea/commit/322506d0c0d39d3cd1e2e1c285c2cc23cfa73ee7), [81f7638](https://github.com/morluto/rea/commit/81f763820319a762f003cf95651ed14ce9326a4c), [dae1e55](https://github.com/morluto/rea/commit/dae1e55381f0d6cfee7f2082d5d27b938e55704c)). Thanks @paoValle, @VarunGore36, @xu91102.
-- **JavaScript traces:** Retain nested bridge calls and surviving early-return predicates. Honor node-ID match options, match route seeds against source values, and keep ambiguous runtime candidates unknown. ([0351328](https://github.com/morluto/rea/commit/0351328e54ce70ea3f2814482e76b132774aff48), [5031099](https://github.com/morluto/rea/commit/503109995f9dcf8a955585d39a344fc846d2f59e), [44c9d29](https://github.com/morluto/rea/commit/44c9d2924d5b95d7a86595e8d7b7cf4fd4f0f6ac), [5e79d46](https://github.com/morluto/rea/commit/5e79d468e5864204cbe79a7ca2898541cee5e012)). Thanks @jpdefo.
-- **Browser comparison coverage:** Compare only known redirect response fields and retain network-selection recovery guidance alongside independent event changes. Missing response facts do not prove equality or a change. ([2b60e09](https://github.com/morluto/rea/commit/2b60e097f281f7708c69f1f7ba9263694547bcc0)).
-- **Evidence comparison and ledger input:** Report display-only bundle differences as unchanged while retaining digests, and classify noncanonical bundle records as invalid caller input. ([030c477](https://github.com/morluto/rea/commit/030c47732833c9cedcc31db1309eb3a1ca2c62e8), [3a34ad3](https://github.com/morluto/rea/commit/3a34ad37bdb7b8debba0f6515ba85b80141f2716)).
-- **Capture and admission cleanup:** Keep deleted-file observations and original bytes when a parent becomes a file, preserve unrelated I/O failures during cancellation, and require explicit pre-launch proof before releasing an unknown LLDB target owner. LLDB failure controls used simulated boundaries. ([e67c364](https://github.com/morluto/rea/commit/e67c3642c8920a2a9c0e231ee2f16f50b245df31), [2daeff4](https://github.com/morluto/rea/commit/2daeff4b243e1cd137c591ca394e18a1c05c8bbc), [45b6a7f](https://github.com/morluto/rea/commit/45b6a7fe8f51a89951aaa823ffa627f6f5453a33)). Thanks @SII-YDD, @xu91102.
-- **Client configuration:** Validate MCP output-schema profiles before setup writes, ignore untrusted Gemini workspace settings before parsing them, and identify installed skills independently of marker-only client roots. ([0930e94](https://github.com/morluto/rea/commit/0930e94e077ab7fb4d695f62785919a8a25c2e21), [aade9bb](https://github.com/morluto/rea/commit/aade9bbcb79aa8504ab6921b25f8ab082aba78e7), [ba33c70](https://github.com/morluto/rea/commit/ba33c706d26b63e43308be50c0249c72cff62cc6)). Thanks @CmsChase, @paoValle, @sx4im.
-- **Host tool discovery:** Share macOS Hopper launcher discovery across setup and runtime, preserve explicit paths, and report validated ADB and Apktool availability. ([7582f0d](https://github.com/morluto/rea/commit/7582f0dff29ae0e80c97b885ddd386ac61a92570), [e5deb83](https://github.com/morluto/rea/commit/e5deb832cb09bb524877d0df40f49d5b5bb7dea4)). Thanks @Chessing234, @kaoru0822-kitauji, @viniciusdsandrade.
-- **SAZ encoding validation:** Reject invalid XML bytes, unsupported encodings and declarations that contradict the archive bytes, including records outside the selected request. ([1250aae](https://github.com/morluto/rea/commit/1250aaedd8b4d1e471d8a382f76418bde65c05d2)).
-- **Managed member matching:** Keep malformed TypeDef list ownership unknown, distinguish constants during structural method matching, and accept legacy small exception-section sizes. ([3f6b575](https://github.com/morluto/rea/commit/3f6b5755b3e699bd9373641acffe0f2c5d2ab094), [ee5cfbe](https://github.com/morluto/rea/commit/ee5cfbe05cd309a88003c711721e67a3bee36554)).
-- **Bounded diagnostics:** Bound SDK validation messages and terminal normalization before allocation while retaining diagnostics and explicit unknown final output sizes. ([7fb0a0c](https://github.com/morluto/rea/commit/7fb0a0cc577f7c9033a2674d877d8242b5864556), [1d826f3](https://github.com/morluto/rea/commit/1d826f304f032acfe69dad3ff824b300aacaeb43)). Thanks @CRYPTONIKAV.
-
-- **Windows artifact classification:** identify `.exe`, `.com`, `.bat` and `.cmd` artifacts as launchable host executables. ([#1823](https://github.com/morluto/rea/pull/1823), [#1824](https://github.com/morluto/rea/pull/1824), [issue morluto/rea#1819](https://github.com/morluto/rea/issues/1819)). Thanks @dollarsmoney, @JasonBuildAI, @kaoru0822-kitauji.
-
-- **CLI/MCP delivery:** defer command-specific startup work, bundle runtime entries, retain field/input correction details across output formats and preserve shared optional-provider lifetime. MCP selectors, paging continuation and retained partial-error references remain explicit; session liveness/provider-attribution corrections retain their controlled-provider verification limits. ([#1691](https://github.com/morluto/rea/pull/1691), [issue morluto/rea#1685](https://github.com/morluto/rea/issues/1685), [#1705](https://github.com/morluto/rea/pull/1705), [issue morluto/rea#1695](https://github.com/morluto/rea/issues/1695), [#1755](https://github.com/morluto/rea/pull/1755), [issue morluto/rea#1746](https://github.com/morluto/rea/issues/1746), [#1773](https://github.com/morluto/rea/pull/1773), [issue morluto/rea#1771](https://github.com/morluto/rea/issues/1771), [#1780](https://github.com/morluto/rea/pull/1780), [#1814](https://github.com/morluto/rea/pull/1814), [#1910](https://github.com/morluto/rea/pull/1910), [issue morluto/rea#1849](https://github.com/morluto/rea/issues/1849), [#1996](https://github.com/morluto/rea/pull/1996), [#2140](https://github.com/morluto/rea/pull/2140), [issue morluto/rea#2135](https://github.com/morluto/rea/issues/2135), [#2205](https://github.com/morluto/rea/pull/2205), [issue morluto/rea#2195](https://github.com/morluto/rea/issues/2195), [#2230](https://github.com/morluto/rea/pull/2230), [issue morluto/rea#2180](https://github.com/morluto/rea/issues/2180), [#2294](https://github.com/morluto/rea/pull/2294), [#2482](https://github.com/morluto/rea/pull/2482), [a82d14e](https://github.com/morluto/rea/commit/a82d14e4db4dca989ffa2e7dbe78fd43551da256), [a4dd4e8](https://github.com/morluto/rea/commit/a4dd4e8e8700ce350e1a0c612ebd61b91ca5e585), [48c352b](https://github.com/morluto/rea/commit/48c352b6bfa34c820a530272cd36600158c37b1e), [07b36c1](https://github.com/morluto/rea/commit/07b36c148946f46b99a4ce04e55726e97d0ee03a), [570c40c](https://github.com/morluto/rea/commit/570c40cde55d31e455ef9bc484b7b908658ded58), [8fc2043](https://github.com/morluto/rea/commit/8fc2043eb8bcedbf34dce064f977e455438635d6), [7fc0b5e](https://github.com/morluto/rea/commit/7fc0b5ec9c2532bbf789d7783b7a0cab6fc054d8)). Thanks @369Apps, @chqcjq, @cold-atom, @coygeek, @JackOdegard, @kaoru0822-kitauji, @N0zoM1z0, @sx4im.
-- **Evidence import/replay:** import bundles across session transitions while authenticating selected target and file identities, preserve literal keys, metadata/mutation intent and relationship coverage, and honor cancellation before session mutation. Reuse authenticated snapshots and comparisons within their owned lifetime; reject malformed/non-object snapshots and unsupported metadata without disguising uncertainty. ([#1694](https://github.com/morluto/rea/pull/1694), [#1716](https://github.com/morluto/rea/pull/1716), [issue morluto/rea#1680](https://github.com/morluto/rea/issues/1680), [#1721](https://github.com/morluto/rea/pull/1721), [issue morluto/rea#1718](https://github.com/morluto/rea/issues/1718), [#1733](https://github.com/morluto/rea/pull/1733), [issue morluto/rea#1723](https://github.com/morluto/rea/issues/1723), [issue morluto/rea#1724](https://github.com/morluto/rea/issues/1724), [#1776](https://github.com/morluto/rea/pull/1776), [#1873](https://github.com/morluto/rea/pull/1873), [#2001](https://github.com/morluto/rea/pull/2001), [#2013](https://github.com/morluto/rea/pull/2013), [issue morluto/rea#2009](https://github.com/morluto/rea/issues/2009), [#2083](https://github.com/morluto/rea/pull/2083), [#2303](https://github.com/morluto/rea/pull/2303), [#2685](https://github.com/morluto/rea/pull/2685), [issue morluto/rea#2675](https://github.com/morluto/rea/issues/2675), [c002b89](https://github.com/morluto/rea/commit/c002b89e2d8130a3c07e25e5fd604876be18c703), [9c85114](https://github.com/morluto/rea/commit/9c8511409c0706f9979c2b68dd56aaaf9f21e191), [aada0ca](https://github.com/morluto/rea/commit/aada0ca8126bf14c60750a4ccd4a79667770a1e4), [4a4d36f](https://github.com/morluto/rea/commit/4a4d36f881861bbab3c734b0dd459f805766caec), [1c64fe3](https://github.com/morluto/rea/commit/1c64fe3eff48679c6880f42d2f0a4af46686ade7), [6fb3a34](https://github.com/morluto/rea/commit/6fb3a345fe952b8e8f59221aec993acc37ccbf31), [3bcc68c](https://github.com/morluto/rea/commit/3bcc68c037e9415c78093cb286069c1fcca6a2f8), [6bae774](https://github.com/morluto/rea/commit/6bae774328724403255590aa2ddad4d7a2aa727f), [e997085](https://github.com/morluto/rea/commit/e9970855ba16ba711816ac30212c5ca17ae085cd), [d1dcebc](https://github.com/morluto/rea/commit/d1dcebce2c0820469ed63e33497a14258971b710), [b123b2e](https://github.com/morluto/rea/commit/b123b2e51cc7d6d2157525664be2df88fb1ba3bd), [049132a](https://github.com/morluto/rea/commit/049132ab43fa962d31774f2b258c15a71217148b), [042dcaa](https://github.com/morluto/rea/commit/042dcaa1ee66f1b8668f08b193f38ab01bceaacb), [acf75e6](https://github.com/morluto/rea/commit/acf75e6700ace28bb1db25e54e56673ac15e0ed3), [1f7f808](https://github.com/morluto/rea/commit/1f7f808c4f3bb5eca6b13bcc71d5cceb2ace6614), [26bffb9](https://github.com/morluto/rea/commit/26bffb94bf80355c35e22a98a8fc629c6210307e)). Thanks @coygeek, @DeryFerd, @jiangjiang248, @kaoru0822-kitauji, @khanukov, @N0zoM1z0, @NIU-123370, @rohitg00, @sx4im.
-- **Ghidra setup and analysis:** preserve launcher/JVM diagnostics, Java-property and extension identity, stale-client recovery, UTF-8 bridge output and pending-startup progress. File-offset decompilation is Ghidra-specific; recorded coverage is Linux x64 with Ghidra 12.1.4. Startup/progress/compiler failure paths that use simulations remain unverified with a real engine. ([#1698](https://github.com/morluto/rea/pull/1698), [#1877](https://github.com/morluto/rea/pull/1877), [#1931](https://github.com/morluto/rea/pull/1931), [#2011](https://github.com/morluto/rea/pull/2011), [issue morluto/rea#1992](https://github.com/morluto/rea/issues/1992), [#2014](https://github.com/morluto/rea/pull/2014), [#2101](https://github.com/morluto/rea/pull/2101), [issue morluto/rea#2078](https://github.com/morluto/rea/issues/2078), [#2206](https://github.com/morluto/rea/pull/2206), [issue morluto/rea#2204](https://github.com/morluto/rea/issues/2204), [2187e16](https://github.com/morluto/rea/commit/2187e16f149a7a7b512a4cb45d5f468cc04091fe), [b953f96](https://github.com/morluto/rea/commit/b953f96c0aae27e1876c317a8f7db1d6f292b8ff)). Thanks @EDMND-SRC, @Ha1baraA11, @kaoru0822-kitauji, @lovecontroing, @lyly-bonbon, @N0zoM1z0, @nosmile99, @Petru101, @sx4im, @Zhong-fan.
-- **Process and cleanup ownership:** retain private runtime/file owners and detailed incomplete-cleanup observations, bound trace cycles/order state, preserve caller paths, and use monotonic time for budgets while retaining wall dates. Windows affinity/admission ([#2202](https://github.com/morluto/rea/pull/2202), [issue morluto/rea#2181](https://github.com/morluto/rea/issues/2181)) and Bun memory-enforcement paths retain their recorded native-versus-controlled-fixture limits; these fixes are not a general process-ownership guarantee. ([#1700](https://github.com/morluto/rea/pull/1700), [issue morluto/rea#1697](https://github.com/morluto/rea/issues/1697), [#1730](https://github.com/morluto/rea/pull/1730), [#1756](https://github.com/morluto/rea/pull/1756), [issue morluto/rea#1753](https://github.com/morluto/rea/issues/1753), [#1760](https://github.com/morluto/rea/pull/1760), [issue morluto/rea#1757](https://github.com/morluto/rea/issues/1757), [#1826](https://github.com/morluto/rea/pull/1826), [#1907](https://github.com/morluto/rea/pull/1907), [issue morluto/rea#1856](https://github.com/morluto/rea/issues/1856), [#1999](https://github.com/morluto/rea/pull/1999), [issue morluto/rea#1993](https://github.com/morluto/rea/issues/1993), [#2232](https://github.com/morluto/rea/pull/2232), [issue morluto/rea#2170](https://github.com/morluto/rea/issues/2170), [#2252](https://github.com/morluto/rea/pull/2252), [issue morluto/rea#2218](https://github.com/morluto/rea/issues/2218), [#2467](https://github.com/morluto/rea/pull/2467), [issue morluto/rea#2257](https://github.com/morluto/rea/issues/2257), [#2468](https://github.com/morluto/rea/pull/2468), [#2488](https://github.com/morluto/rea/pull/2488), [09b6828](https://github.com/morluto/rea/commit/09b68285166bef2b7633402c8adf7eb25823b47e), [7285e15](https://github.com/morluto/rea/commit/7285e15839a4fecf9940683699b781a60ccc4775), [b5ededd](https://github.com/morluto/rea/commit/b5ededd0f9c28d0f696a205103066928117368ee), [d8c76b6](https://github.com/morluto/rea/commit/d8c76b629639bda4405afa9ae2f7676b694f2f10), [98d8470](https://github.com/morluto/rea/commit/98d8470d36cfbf7cd25820a4ed430aebae20c0c5), [c22111e](https://github.com/morluto/rea/commit/c22111eca2c4bc84a084f12711f405b3e7422a40), [cecc6ec](https://github.com/morluto/rea/commit/cecc6ecbffe84689a173d1634f342e046b0c8ceb), [10935b7](https://github.com/morluto/rea/commit/10935b7b1136accab2a43b308ab380749da0f7ae), [63e796d](https://github.com/morluto/rea/commit/63e796d50ea323ae8dcfef80f86c8154bb106790), [d9e9fb2](https://github.com/morluto/rea/commit/d9e9fb2273543caab4eb21d896c33d462ada6971), [9049dba](https://github.com/morluto/rea/commit/9049dbaf0c3df32357419f9899965df2b611f493), [ed881c6](https://github.com/morluto/rea/commit/ed881c6d2ef6a8adba0c2a241ebc9ab4603b7868)). Thanks @Ashen00001, @charan-rathore, @coygeek, @EDMND-SRC, @JasonBuildAI, @jimpablo, @kaoru0822-kitauji, @N0zoM1z0, @NIU-123370, @Rinkia, @rudycelekli, @sx4im, @xeropresence, @XiaoBinGan, @xthunder0, @hzh666kevin-hue.
-- **Native image identity:** preserve universal Mach-O containers and selected slice/subtype identity, chained fixup locations and library ordinals, exact signing text, PE resource capacity and ELF/header framing. Mach-O summary selection and independent slice commands avoid unnecessary delivery/work. Controlled routing/parser fixtures do not establish every installed-provider path. ([#1703](https://github.com/morluto/rea/pull/1703), [issue morluto/rea#1702](https://github.com/morluto/rea/issues/1702), [#1708](https://github.com/morluto/rea/pull/1708), [#1709](https://github.com/morluto/rea/pull/1709), [#1713](https://github.com/morluto/rea/pull/1713), [#1772](https://github.com/morluto/rea/pull/1772), [issue morluto/rea#1765](https://github.com/morluto/rea/issues/1765), [#1784](https://github.com/morluto/rea/pull/1784), [issue morluto/rea#1775](https://github.com/morluto/rea/issues/1775), [#1982](https://github.com/morluto/rea/pull/1982), [#1995](https://github.com/morluto/rea/pull/1995), [issue morluto/rea#1990](https://github.com/morluto/rea/issues/1990), [#2040](https://github.com/morluto/rea/pull/2040), [#2107](https://github.com/morluto/rea/pull/2107), [#2161](https://github.com/morluto/rea/pull/2161), [issue morluto/rea#2105](https://github.com/morluto/rea/issues/2105), [#2248](https://github.com/morluto/rea/pull/2248), [issue morluto/rea#2176](https://github.com/morluto/rea/issues/2176), [#2281](https://github.com/morluto/rea/pull/2281), [issue morluto/rea#2274](https://github.com/morluto/rea/issues/2274), [#2292](https://github.com/morluto/rea/pull/2292), [#2466](https://github.com/morluto/rea/pull/2466), [#2506](https://github.com/morluto/rea/pull/2506), [#2733](https://github.com/morluto/rea/pull/2733), [issue morluto/rea#2661](https://github.com/morluto/rea/issues/2661), [f598bab](https://github.com/morluto/rea/commit/f598bab488e38c378d69346fa3c106f9e18529ed), [108b5f9](https://github.com/morluto/rea/commit/108b5f94254281639badd25b1f448cca35dc89a2), [f1924cf](https://github.com/morluto/rea/commit/f1924cf9c1910d5d29d11e7bf634b51af8d738cf), [8bd5ba2](https://github.com/morluto/rea/commit/8bd5ba2d234cbd9a5bb9dd5daeaa191c3a1cad24), [b38429c](https://github.com/morluto/rea/commit/b38429cb6a0de8f4bb5ae01633e24abe2d7cde46), [8d4d631](https://github.com/morluto/rea/commit/8d4d631606c701aac150cf009d3b80ae4a7ae7d5), [ac57c88](https://github.com/morluto/rea/commit/ac57c88efe64c3125850b54d3d833227e6b8ec51), [dc038d1](https://github.com/morluto/rea/commit/dc038d16bba9046afd28970de9c47f6259a43524), [34a4bb6](https://github.com/morluto/rea/commit/34a4bb6508006fa113463ef20ed799a2994e9ee8), [ebc22d9](https://github.com/morluto/rea/commit/ebc22d99d62225505c0a84f6e39823ba4ef2f829), [c02fb0e](https://github.com/morluto/rea/commit/c02fb0ea8055f98def2b12ad557aed0faefd3639)). Thanks @1NormalGuy, @Aliciawque, @baron, @coygeek, @dhl84, @hemanthrayuduu, @JasonBuildAI, @kaoru0822-kitauji, @N0zoM1z0, @thangldw, @viniciusdsandrade, @XiaoBinGan, @Zburgers.
-- **Archive and artifact provenance:** keep physical ZIP occurrence identity, exact signatures/names and partial inventory coverage; bound decompression and reject malformed keys/integers. Directory/ASAR/DMG reads retain ownership through cleanup and publication cancellation. Duplicate ZIP names remain explicitly ambiguous where the public projection cannot represent them; synthetic archive/cleanup cases do not prove every real Unblob or DMG failure path. ([#1726](https://github.com/morluto/rea/pull/1726), [issue morluto/rea#1725](https://github.com/morluto/rea/issues/1725), [#1854](https://github.com/morluto/rea/pull/1854), [issue morluto/rea#1844](https://github.com/morluto/rea/issues/1844), [#1865](https://github.com/morluto/rea/pull/1865), [issue morluto/rea#1860](https://github.com/morluto/rea/issues/1860), [#2069](https://github.com/morluto/rea/pull/2069), [#2106](https://github.com/morluto/rea/pull/2106), [#2144](https://github.com/morluto/rea/pull/2144), [#2365](https://github.com/morluto/rea/pull/2365), [#2493](https://github.com/morluto/rea/pull/2493), [918713a](https://github.com/morluto/rea/commit/918713af376e307ecf24d75e6a0dd9d1b544545b), [eb97da3](https://github.com/morluto/rea/commit/eb97da33881e3d1472d97a7d788ee35944fb6b07), [2260887](https://github.com/morluto/rea/commit/2260887f2092be6a3d9c79509e4ae4a3e52fce7f), [74d7da6](https://github.com/morluto/rea/commit/74d7da6ced0f869936ee0316b00616931b088066), [ed485a3](https://github.com/morluto/rea/commit/ed485a3dc8cc3a4baf8cabe01acb7aa0490b73b3), [921bb95](https://github.com/morluto/rea/commit/921bb9575505065f6cfd57b14d97d80d0f238546), [d8ceb3f](https://github.com/morluto/rea/commit/d8ceb3f276a65c181b146f68c0729ff4b6f9fa61), [9435c7a](https://github.com/morluto/rea/commit/9435c7aae279ba184937c0dfeb713fd574ba3f29), [bb54082](https://github.com/morluto/rea/commit/bb540826d65316c164d2de8ba4ef10f81a8ad073), [a73a55f](https://github.com/morluto/rea/commit/a73a55f53cc2b2e5b7618effe6ecb5cee6e0cee2), [3c57e1a](https://github.com/morluto/rea/commit/3c57e1a8b21b379fca55032d177078e1d8426e64), [ec0b081](https://github.com/morluto/rea/commit/ec0b081371f118e6e5e042fbef3479359c672ddb), [e7882b3](https://github.com/morluto/rea/commit/e7882b34f4ac4a26f903c5f49264acc2c19bb562), [b955b82](https://github.com/morluto/rea/commit/b955b825fc002a4bb408f2910b78768c566c2cd1)). Thanks @1052326311, @1NormalGuy, @baron, @Bortlesboat, @Chaoqi31, @DeryFerd, @kaoru0822-kitauji, @N0zoM1z0, @XiaoBinGan.
-- **Setup/uninstall recovery:** preserve unrelated YAML text, caller-selected roots, symlinked data and existing recovery snapshots; explain malformed configuration shapes and retain failed rollback/cleanup owners. Show terminal dry-run plans and each selected skill location. Bunx registration and fault-injected recovery cases remain simulated rather than live-client verification. ([#1731](https://github.com/morluto/rea/pull/1731), [#1754](https://github.com/morluto/rea/pull/1754), [#1821](https://github.com/morluto/rea/pull/1821), [issue morluto/rea#1816](https://github.com/morluto/rea/issues/1816), [#1983](https://github.com/morluto/rea/pull/1983), [#2118](https://github.com/morluto/rea/pull/2118), [issue morluto/rea#2111](https://github.com/morluto/rea/issues/2111), [#2154](https://github.com/morluto/rea/pull/2154), [issue morluto/rea#2152](https://github.com/morluto/rea/issues/2152), [#2157](https://github.com/morluto/rea/pull/2157), [#2182](https://github.com/morluto/rea/pull/2182), [issue morluto/rea#2159](https://github.com/morluto/rea/issues/2159), [#2481](https://github.com/morluto/rea/pull/2481), [bb50813](https://github.com/morluto/rea/commit/bb508134efbba392a404b651d6ec05be8b7eac1e), [c240768](https://github.com/morluto/rea/commit/c2407689cb04df082e8db0b6afa8f8d022f6bcd1), [dcfc5d4](https://github.com/morluto/rea/commit/dcfc5d403ac997c2b08bee4753e57a1a4a8a8538), [21eff3b](https://github.com/morluto/rea/commit/21eff3bae10f58711a35ad44f86e9f96f9bb4790), [94153f1](https://github.com/morluto/rea/commit/94153f1c757e07a6d092e00903aa8b125d4a0afa), [2397137](https://github.com/morluto/rea/commit/23971376158e7815edcbe6c04a8df7c9504650dc), [c339f9e](https://github.com/morluto/rea/commit/c339f9ebe7bd1f30608d6ccb7175da523dd3c485), [f6775a3](https://github.com/morluto/rea/commit/f6775a36694a6a9c620f4248638e8056a6cbcb66)). Thanks @BeqaKs, @Jax367, @kaoru0822-kitauji, @NIU-123370, @shoyann, @viniciusdsandrade, @xeropresence, @zaydiscold.
-- **Bun updates:** locate global installations before changing directories and reuse parsed client activation during maintenance. The update flow is covered with package-manager/filesystem simulations; a real Bun global installation update remains unverified. ([#1735](https://github.com/morluto/rea/pull/1735), [e90acae](https://github.com/morluto/rea/commit/e90acaea674f5f7f9f17ea472104afdc1422ada6), [b045df1](https://github.com/morluto/rea/commit/b045df100e1489e08a36d6ff04cea7feecf1332c)). Thanks @xeropresence.
-- **JavaScript relationships:** preserve loader-specific package/TypeScript/CommonJS boundaries, exact file-URL and source-map identity, Electron intrinsic receivers/IPC guards and chunk metadata. Index repeated lookups and retain completed facts through resource limits and cancellation. Real Electron integration, Bun worker integration and failure-path cleanup remain unverified where the recorded lanes use fixtures. ([#1740](https://github.com/morluto/rea/pull/1740), [#1759](https://github.com/morluto/rea/pull/1759), [issue morluto/rea#1748](https://github.com/morluto/rea/issues/1748), [#1762](https://github.com/morluto/rea/pull/1762), [issue morluto/rea#1761](https://github.com/morluto/rea/issues/1761), [#1767](https://github.com/morluto/rea/pull/1767), [#1788](https://github.com/morluto/rea/pull/1788), [issue morluto/rea#1781](https://github.com/morluto/rea/issues/1781), [issue morluto/rea#1782](https://github.com/morluto/rea/issues/1782), [#1789](https://github.com/morluto/rea/pull/1789), [#1799](https://github.com/morluto/rea/pull/1799), [issue morluto/rea#1793](https://github.com/morluto/rea/issues/1793), [#1827](https://github.com/morluto/rea/pull/1827), [issue morluto/rea#1802](https://github.com/morluto/rea/issues/1802), [#1833](https://github.com/morluto/rea/pull/1833), [issue morluto/rea#1831](https://github.com/morluto/rea/issues/1831), [#1857](https://github.com/morluto/rea/pull/1857), [issue morluto/rea#1842](https://github.com/morluto/rea/issues/1842), [#1871](https://github.com/morluto/rea/pull/1871), [#1874](https://github.com/morluto/rea/pull/1874), [#1905](https://github.com/morluto/rea/pull/1905), [#1912](https://github.com/morluto/rea/pull/1912), [issue morluto/rea#1909](https://github.com/morluto/rea/issues/1909), [#1915](https://github.com/morluto/rea/pull/1915), [issue morluto/rea#1911](https://github.com/morluto/rea/issues/1911), [#1916](https://github.com/morluto/rea/pull/1916), [#1921](https://github.com/morluto/rea/pull/1921), [#1934](https://github.com/morluto/rea/pull/1934), [#1939](https://github.com/morluto/rea/pull/1939), [issue morluto/rea#1881](https://github.com/morluto/rea/issues/1881), [issue morluto/rea#1882](https://github.com/morluto/rea/issues/1882), [issue morluto/rea#1883](https://github.com/morluto/rea/issues/1883), [#1941](https://github.com/morluto/rea/pull/1941), [#2062](https://github.com/morluto/rea/pull/2062), [issue morluto/rea#2058](https://github.com/morluto/rea/issues/2058), [#2104](https://github.com/morluto/rea/pull/2104), [#2422](https://github.com/morluto/rea/pull/2422), [#2475](https://github.com/morluto/rea/pull/2475), [#2737](https://github.com/morluto/rea/pull/2737), [issue morluto/rea#2663](https://github.com/morluto/rea/issues/2663), [d3088c3](https://github.com/morluto/rea/commit/d3088c3795f6c37cb3b6aec0bb0c371dd0640ee8), [1dfb933](https://github.com/morluto/rea/commit/1dfb933e47db0156cf1cb61f28715b81e740c57b), [f8513a4](https://github.com/morluto/rea/commit/f8513a42dc44451a621127f06edde5d38bc93f69), [b8fab74](https://github.com/morluto/rea/commit/b8fab7429771bb17a7ca0297661de3c9935212af), [42b0ed1](https://github.com/morluto/rea/commit/42b0ed126df7d5b908ac369715378d5e519051b7), [c0904b4](https://github.com/morluto/rea/commit/c0904b4c1aabfccf2f0ab12f44960a0a1fbbbfae), [9f67e44](https://github.com/morluto/rea/commit/9f67e44e5d451d705bae9a579ad9802d5c9f097c), [e4532b5](https://github.com/morluto/rea/commit/e4532b537663026c3e5b784380eecd009c959a36), [1c37914](https://github.com/morluto/rea/commit/1c37914306b3ff257d7a0360f11c9bf2a3f2cac7), [5ab0cbb](https://github.com/morluto/rea/commit/5ab0cbb48ea5a4f11542eac44479b9af48f1dabd), [b7169c8](https://github.com/morluto/rea/commit/b7169c8b747cbc032913b31f008a3b81c77b6219), [f43fc02](https://github.com/morluto/rea/commit/f43fc0247527aebb8efc7d9db04276fe2d489323), [3ae826c](https://github.com/morluto/rea/commit/3ae826ceba6f25b08bce50bcb51001209bc16b57), [1b95302](https://github.com/morluto/rea/commit/1b953021eadf4cac09e20be388d79536903633b3), [eaa9616](https://github.com/morluto/rea/commit/eaa961658578522cecfbba7c7be1acf1c64da65a), [c923fb0](https://github.com/morluto/rea/commit/c923fb0dc9462e302b84a15770131ff899f89455), [c7a890d](https://github.com/morluto/rea/commit/c7a890d12987d9b2d496119c1fbf1a88c0fc298e)). Thanks @Aurantium-47, @baron, @chqcjq, @coygeek, @cyanseek, @fengdwx, @flitzrrr, @immanuwell, @kaoru0822-kitauji, @N0zoM1z0, @Nelglor, @ranmori, @rudycelekli, @shoyann, @xu91102.
-- **Browser observations:** preserve effective source-map URLs, empty query/fragment identity, response-body provenance, service-worker policies and explicit uncertainty for malformed events. Bound discovery lifetimes and retain cleanup ownership. Interrupt/retry/failure cases validated with controlled CDP/session fixtures do not establish those paths in real Chromium. ([#1742](https://github.com/morluto/rea/pull/1742), [issue morluto/rea#1729](https://github.com/morluto/rea/issues/1729), [#1829](https://github.com/morluto/rea/pull/1829), [#2074](https://github.com/morluto/rea/pull/2074), [#2099](https://github.com/morluto/rea/pull/2099), [#2239](https://github.com/morluto/rea/pull/2239), [issue morluto/rea#2169](https://github.com/morluto/rea/issues/2169), [#2477](https://github.com/morluto/rea/pull/2477), [486b567](https://github.com/morluto/rea/commit/486b56724c4eaba50719177bcb9eae84d6907297), [a82e37c](https://github.com/morluto/rea/commit/a82e37c8065cc200a0ca3e14e7c4f85e4e468580), [a8d4984](https://github.com/morluto/rea/commit/a8d4984404b611e60b88bc42289c0ba07eee4578), [966f7cc](https://github.com/morluto/rea/commit/966f7cc84b4a8bb0043641cb64d7a7aaf8715e05), [221c856](https://github.com/morluto/rea/commit/221c85648108e9846d9920b0964dafa7f108d581), [951b095](https://github.com/morluto/rea/commit/951b095e11adf9faa9c4a27e212260060aa6b095), [f09bb8a](https://github.com/morluto/rea/commit/f09bb8a99773f79c7306b8799c86f856fe2c0d4b), [6bd2b28](https://github.com/morluto/rea/commit/6bd2b28161411f70ed5dc72e42c2736a1aab758b)). Thanks @1052326311, @chAng-L19, @chqcjq, @coygeek, @evenafterallisaid, @fisforfaheem, @itsF4LCON, @N0zoM1z0, @shayanxcyber.
-- **Managed metadata/CIL:** preserve ExportedType and pointer-table ownership, generic/array/function-pointer/modifier signatures, ReadyToRun host identity, metadata ExtraData and signed zero. Charge retained facts and decoded instruction counts instead of broad decoding bounds; malformed layouts remain caller input errors. ([#1743](https://github.com/morluto/rea/pull/1743), [issue morluto/rea#1736](https://github.com/morluto/rea/issues/1736), [#1768](https://github.com/morluto/rea/pull/1768), [#1822](https://github.com/morluto/rea/pull/1822), [issue morluto/rea#1801](https://github.com/morluto/rea/issues/1801), [#1828](https://github.com/morluto/rea/pull/1828), [issue morluto/rea#1812](https://github.com/morluto/rea/issues/1812), [#1835](https://github.com/morluto/rea/pull/1835), [issue morluto/rea#1832](https://github.com/morluto/rea/issues/1832), [#1886](https://github.com/morluto/rea/pull/1886), [#1893](https://github.com/morluto/rea/pull/1893), [#1897](https://github.com/morluto/rea/pull/1897), [issue morluto/rea#1878](https://github.com/morluto/rea/issues/1878), [#1943](https://github.com/morluto/rea/pull/1943), [issue morluto/rea#1940](https://github.com/morluto/rea/issues/1940), [#1985](https://github.com/morluto/rea/pull/1985), [#2194](https://github.com/morluto/rea/pull/2194), [issue morluto/rea#2191](https://github.com/morluto/rea/issues/2191), [#2437](https://github.com/morluto/rea/pull/2437), [52e76c5](https://github.com/morluto/rea/commit/52e76c5d39b58d1685bb5e22bd40d19524dfa2cb)). Thanks @ac1982, @chqcjq, @fisHarly0, @flitzrrr, @JasonBuildAI, @JayOfTheKeyboard, @jhuang-tw, @kaoru0822-kitauji, @N0zoM1z0, @Nelglor.
-- **Hopper failure ownership:** preserve startup/process outcomes, retain cleanup leases across one-shot failures, wait for late bridges, and stop owned Linux demo children when their REA owner exits. Denied/crashed/late-bridge/queued-request failure paths use simulated process or bridge fixtures; they are not fresh installed-Hopper verification. ([#1763](https://github.com/morluto/rea/pull/1763), [issue morluto/rea#1751](https://github.com/morluto/rea/issues/1751), [#1817](https://github.com/morluto/rea/pull/1817), [#1866](https://github.com/morluto/rea/pull/1866), [#1927](https://github.com/morluto/rea/pull/1927), [#2474](https://github.com/morluto/rea/pull/2474), [#2499](https://github.com/morluto/rea/pull/2499), [issue morluto/rea#2459](https://github.com/morluto/rea/issues/2459)). Thanks @coygeek, @Joshwong1908, @kaoru0822-kitauji, @N0zoM1z0, @rudycelekli.
-- **IDA session boundaries:** retain non-x86 call coverage and unresolved-procedure uncertainty, and bound private universal-Mach-O inputs to the exact selected slice. Transient headless busy recovery was exercised on macOS arm64 IDA Pro 9.1; Linux headless, attached GUI navigation and worker-reaped cleanup paths retain their documented verification gaps. ([#1764](https://github.com/morluto/rea/pull/1764), [issue morluto/rea#1712](https://github.com/morluto/rea/issues/1712), [#1778](https://github.com/morluto/rea/pull/1778), [issue morluto/rea#1766](https://github.com/morluto/rea/issues/1766), [#1785](https://github.com/morluto/rea/pull/1785), [issue morluto/rea#1769](https://github.com/morluto/rea/issues/1769), [#1906](https://github.com/morluto/rea/pull/1906), [issue morluto/rea#1794](https://github.com/morluto/rea/issues/1794), [#2201](https://github.com/morluto/rea/pull/2201), [issue morluto/rea#2139](https://github.com/morluto/rea/issues/2139), [#2291](https://github.com/morluto/rea/pull/2291), [issue morluto/rea#2285](https://github.com/morluto/rea/issues/2285), [#2324](https://github.com/morluto/rea/pull/2324), [12fa8fd](https://github.com/morluto/rea/commit/12fa8fd9f986dbd4ff58165c3ec71a46dc8a8a3b)). Thanks @akushonkamen, @coygeek, @kaoru0822-kitauji, @N0zoM1z0, @nikolay-dementiev, @zecaro.
-- **Input and capability diagnostics:** identify invalid paths, format refusals, missing host tools and non-retryable errors without losing caller selections or retryable capability facts. Foreign execution/device mutation annotations remain destructive, analysis-target text is untrusted, and output ordering follows code points rather than host locale. ([#1770](https://github.com/morluto/rea/pull/1770), [#1867](https://github.com/morluto/rea/pull/1867), [#1869](https://github.com/morluto/rea/pull/1869), [issue morluto/rea#1855](https://github.com/morluto/rea/issues/1855), [#1872](https://github.com/morluto/rea/pull/1872), [#1879](https://github.com/morluto/rea/pull/1879), [issue morluto/rea#1853](https://github.com/morluto/rea/issues/1853), [#1899](https://github.com/morluto/rea/pull/1899), [#1902](https://github.com/morluto/rea/pull/1902), [#1904](https://github.com/morluto/rea/pull/1904), [#1908](https://github.com/morluto/rea/pull/1908), [#1925](https://github.com/morluto/rea/pull/1925), [#1987](https://github.com/morluto/rea/pull/1987), [issue morluto/rea#1979](https://github.com/morluto/rea/issues/1979), [#2004](https://github.com/morluto/rea/pull/2004), [issue morluto/rea#2002](https://github.com/morluto/rea/issues/2002), [#2026](https://github.com/morluto/rea/pull/2026), [#2091](https://github.com/morluto/rea/pull/2091), [#2133](https://github.com/morluto/rea/pull/2133), [issue morluto/rea#2129](https://github.com/morluto/rea/issues/2129), [#2145](https://github.com/morluto/rea/pull/2145), [issue morluto/rea#2143](https://github.com/morluto/rea/issues/2143), [#2472](https://github.com/morluto/rea/pull/2472), [#2478](https://github.com/morluto/rea/pull/2478), [issue morluto/rea#2454](https://github.com/morluto/rea/issues/2454), [#2494](https://github.com/morluto/rea/pull/2494), [#2507](https://github.com/morluto/rea/pull/2507), [#2509](https://github.com/morluto/rea/pull/2509), [#2708](https://github.com/morluto/rea/pull/2708), [3d83135](https://github.com/morluto/rea/commit/3d8313598785359c424d7305f503cb69fc8639a6), [c9fed50](https://github.com/morluto/rea/commit/c9fed50691ae014890e91a72534773d2fb58ce44), [8b18171](https://github.com/morluto/rea/commit/8b181716aca2cb467be499cba226abfb5ae19141), [7a2cd1e](https://github.com/morluto/rea/commit/7a2cd1ea0a63e8c44166860b7ee9c7a1aa43492b)). Thanks @astralyx0129, @CassieFox23, @DeryFerd, @dollarsmoney, @fisforfaheem, @flitzrrr, @Ha1baraA11, @jimpablo, @kaoru0822-kitauji, @larinyo, @N0zoM1z0, @rudycelekli, @SII-YDD, @viniciusdsandrade, @XiaoBinGan.
-- **Android analysis:** retain decoded values, duplicate-class inventories and executable static initializers, reject malformed JADX UTF-8, and keep inline search provenance. Apktool accepts `--no-strings` and explains host requirements. Windows batch-launcher selection also resolves PATH/PATHEXT before choosing its launch mode. Recorded Apktool coverage is Linux/OpenJDK, and changed JADX/batch failure paths do not establish native Windows behavior. ([#1777](https://github.com/morluto/rea/pull/1777), [issue morluto/rea#1774](https://github.com/morluto/rea/issues/1774), [#1876](https://github.com/morluto/rea/pull/1876), [issue morluto/rea#1846](https://github.com/morluto/rea/issues/1846), [#1890](https://github.com/morluto/rea/pull/1890), [issue morluto/rea#1850](https://github.com/morluto/rea/issues/1850), [#1946](https://github.com/morluto/rea/pull/1946), [issue morluto/rea#1945](https://github.com/morluto/rea/issues/1945), [#2707](https://github.com/morluto/rea/pull/2707), [issue morluto/rea#2672](https://github.com/morluto/rea/issues/2672), [0677468](https://github.com/morluto/rea/commit/0677468877465c8dfbe25c72f142a7b5bc8a3212), [fe8d0bd](https://github.com/morluto/rea/commit/fe8d0bdd36fe12bc0836468d1a702a34fbdc219b), [#2802](https://github.com/morluto/rea/pull/2802)). Thanks @akushonkamen, @coygeek, @HeadmasterEggy, @kaoru0822-kitauji, @N0zoM1z0, @psipher.
-- **ADB acquisition:** preserve device paths and directory identity, prevent host destination collisions/overwrites, count UTF-8 logcat bytes and restricted permissions, and evaluate the complete Activity Manager start report. Launch attempts, status, activity and raw failure output remain observations; real-device timeout/mixed-report and Android 8 directory-read paths remain unverified beyond the documented fixtures. ([#1962](https://github.com/morluto/rea/pull/1962), [#2212](https://github.com/morluto/rea/pull/2212), [issue morluto/rea#2175](https://github.com/morluto/rea/issues/2175), [#2221](https://github.com/morluto/rea/pull/2221), [issue morluto/rea#2220](https://github.com/morluto/rea/issues/2220), [#2359](https://github.com/morluto/rea/pull/2359), [c42232f](https://github.com/morluto/rea/commit/c42232f566d55fe7191763649755148c768eef9f), [55b6148](https://github.com/morluto/rea/commit/55b61485e9f7568b69597eef8696ff6abfe53cfd), [3bdc873](https://github.com/morluto/rea/commit/3bdc8730bd98e073522bcb8ba86527be402c0cbe), [c89972c](https://github.com/morluto/rea/commit/c89972c8777d0114566fe76a060849a18bdd2659), [e1cd292](https://github.com/morluto/rea/commit/e1cd292aa6e8f5f13441d408c66126782c8dbb0d)). Thanks @coygeek, @dakjdakd, @DeryFerd, @huiq777, @sx4im.
-- **WASM names and diagnostics:** preserve debug/custom-section names including NUL and leading BOM, accept unpadded WABT section rows, and avoid irrelevant tool-remediation advice on unrelated runtime-root failures. ([#1963](https://github.com/morluto/rea/pull/1963), [issue morluto/rea#1956](https://github.com/morluto/rea/issues/1956), [#1967](https://github.com/morluto/rea/pull/1967), [#1981](https://github.com/morluto/rea/pull/1981), [#2084](https://github.com/morluto/rea/pull/2084), [#2102](https://github.com/morluto/rea/pull/2102)). Thanks @1052326311, @bugstan, @N0zoM1z0, @sathariels, @STiFLeR7, @viniciusdsandrade.
-
-- **Source-map and path handling:** retain source-map entries when embedded-content counts differ or an optional `sourceMappingURL` is used, and keep `file:` URLs out of operator-relative path resolution. ([#2873](https://github.com/morluto/rea/pull/2873), [#2886](https://github.com/morluto/rea/pull/2886), [#2882](https://github.com/morluto/rea/pull/2882), [issue morluto/rea#2821](https://github.com/morluto/rea/issues/2821), [issue morluto/rea#2883](https://github.com/morluto/rea/issues/2883), [issue morluto/rea#2577](https://github.com/morluto/rea/issues/2577)). Thanks @JFSAS, @rileygramlich, @shoyann, @shubhamahuja9999, @coygeek.
-- **Native metadata:** accept declared facts in native dispatch inventories and share native verification input diagnostics. ([#2906](https://github.com/morluto/rea/pull/2906), [#2901](https://github.com/morluto/rea/pull/2901), [issue morluto/rea#2564](https://github.com/morluto/rea/issues/2564), [issue morluto/rea#2621](https://github.com/morluto/rea/issues/2621)). Thanks @ShitK, @coygeek.
-
-### ⚠ BREAKING CHANGES
-
-- **Runtime attachment state:** `attached` may be `null` in JavaScript, browser and Electron discovery/inspection results. Treat null as unknown; do not coerce it to false. ([e55ef72](https://github.com/morluto/rea/commit/e55ef7213515ba204c3d88a4487b4ee6a2773b06)).
-- **Source maps:** original-source and mapping rows preserve a null source name when unavailable. Handle null explicitly instead of expecting an invented unknown-source string; new index fields remain optional when reading older Evidence. ([ee50ed1](https://github.com/morluto/rea/commit/ee50ed121e38cc6e1a2ff0dc8b789f15f71c5402)).
-- **Streamed filtered JSON:** `--filter-output` now emits JSON `null` instead of `{}` when the selected value is null; consumers must distinguish a present null from a missing selection. Use `--full-output` when an object envelope is required. ([#2333](https://github.com/morluto/rea/pull/2333)). Thanks @Jackmeson1.
-- **Call graphs:** `get_call_graph.normalized_result` is now `{ graph, limitations }`; read traversal-depth groups under `graph` and retain relationship-specific caveats. Contract/fixture validation does not establish new Ghidra or IDA engine coverage. ([5dfb9d0](https://github.com/morluto/rea/commit/5dfb9d050c2cc44a61b183dae765bef4d22a53b7)).
-- **MCP discovery:** `binary_session` no longer repeats `server_identity.catalog.tools`. Use the connected server tool list, grouped `tool_availability` and provider capabilities; see [MCP contracts](docs/mcp-contracts.md). Origin: [6395e8d](https://github.com/morluto/rea/commit/6395e8d3007d5ee453477460e7ee1c51cff76be0). ([#1988](https://github.com/morluto/rea/pull/1988)). Thanks @kaoru0822-kitauji, @N0zoM1z0.
-
-- **Provider admission:** MIPS targets with unresolved GNU ABI attributes are refused. Supply supported ABI declarations. Saved Hopper databases on macOS are unavailable because the launcher cannot run the analysis bridge when opening a database; select an executable target instead. Database support requires a script-capable database launch route. ([d4bd65c](https://github.com/morluto/rea/commit/d4bd65c53c0254d0195cc7ab8da163dcadfd3b9b)).
-- **Segment extents:** `binary_overview` segment length may be null when Hopper coordinates cannot establish a finite extent in one address space. Preserve unknown rather than converting it to zero or a saturated value. ([36db19c](https://github.com/morluto/rea/commit/36db19c59)).
-- **Invocation identity:** `server.command_path` may be null, and registration/setup statuses or doctor classifications may be unknown. Preserve these states and establish the actual invocation before treating a registration as aligned. ([187f113](https://github.com/morluto/rea/commit/187f113f7)). Thanks @hemv-857, @qorvr.
-- **ADB installation:** the optional `replace` input is unchanged. Results now require `replace_requested` to record the requested `adb install -r` mode; `replaced` is nullable because prior device package state was not observed. Update result readers to accept null instead of treating reinstall intent as proof of replacement. ([864314a](https://github.com/morluto/rea/commit/864314ac857924a7e6e65bfb37e8dc720fcc21e7)).
-- **Managed/native verification:** unresolved P/Invoke results may retain `matched_native` and candidate facts when module identity is unknown. Interpret `status`, `basis` and `limitations`; `module-identity-unknown` does not verify correspondence, and unresolved no longer implies empty observations. ([3f6b575](https://github.com/morluto/rea/commit/3f6b5755b3e699bd9373641acffe0f2c5d2ab094)).
-
-Full contribution record: [893 commits and 529 merged PRs](https://github.com/morluto/rea/blob/rea-agents-6.5.0/docs/releases/6.5.0.contributions.json).
-
-
 ## [6.4.0](https://github.com/morluto/rea/compare/rea-agents-6.3.0...rea-agents-6.4.0) (2026-10-11)
 
 ### Highlights
@@ -270,7 +69,7 @@ Full contribution record: [336 commits and 163 merged PRs](https://github.com/mo
 
 ### ⚠ BREAKING CHANGES
 
-* **captures:** Historical captures without current producer accounting or transaction identity, and web diffs missing accessibility or storage dimensions, are rejected. Preserve original captures and recapture with the current producer; update comparison consumers to include every dimension rather than synthesizing missing observations. See the [process capture guide](docs/process-capture.md) and [browser scenario contract](docs/browser-scenario-contract.md). ([3283a45](https://github.com/morluto/rea/commit/3283a45d09457c79e3adadb50a48620926d4bc5b))
+* **captures:** Historical captures without current producer accounting or transaction identity, and web diffs missing accessibility or storage dimensions, are rejected. Preserve original captures and recapture with the current producer; update comparison consumers to include every dimension rather than synthesizing missing observations. See the [process capture guide](docs/guides/runtime/process-capture.md) and [browser scenario contract](docs/guides/web/browser-scenario-contract.md). ([3283a45](https://github.com/morluto/rea/commit/3283a45d09457c79e3adadb50a48620926d4bc5b))
 * **browser:** JSON shape paths now contain typed property and array-element segments. WebMCP input_schema_shape is replaced by input_schema and input_schema_sha256, retaining declared examples and defaults.
 * **process:** Filesystem digest omission entries now require system_code; budget and changed-file omissions use null, and unavailable-file omissions preserve the operating-system error code.
 * **contracts:** Provider analysis outputs must explicitly supply metadata previously repaired with defaults; unsupported nullable facets must be reported as null.
@@ -438,7 +237,7 @@ Full contribution record: [336 commits and 163 merged PRs](https://github.com/mo
 
 ### ⚠ BREAKING CHANGES
 
-Read the [6.1 to 6.2 migration guide](docs/migration-6.2.md) before upgrading. REA's `always-bump-minor` policy includes breaking changes; 6.2 is not a backward-compatibility promise. Preserve original saved files and regenerate missing observations rather than fabricating identities or facts.
+Read the [6.1 to 6.2 migration guide](docs/migrations/migration-6.2.md) before upgrading. REA's `always-bump-minor` policy includes breaking changes; 6.2 is not a backward-compatibility promise. Preserve original saved files and regenerate missing observations rather than fabricating identities or facts.
 
 * **MCP / Evidence / snapshots / artifacts:** Success results are direct canonical Evidence; read `normalized_result` rather than the old `result`/`evidence` wrapper. Evidence requires nullable `analysis_profile`, session provider aliases are removed, snapshots require complete profile-bound query records, and artifact roles/permissions belong to occurrences. Recreate incompatible saved data; adding fields without recomputing their semantic identity is invalid. ([63bf914](https://github.com/morluto/rea/commit/63bf91405cf97b114a84f337fb1272d98a267999))
 * **Process captures:** Legacy v3 conversion is removed. Explicit executable identity and `event_journal` are required; retain old captures and recapture when current comparisons are needed instead of inventing launch identity or event order. ([2a77469](https://github.com/morluto/rea/commit/2a7746998d47446c4db6d4f524e0f183d6803f3f))

CONTRIBUTING.md

@@ -11,7 +11,7 @@ incorrect user instructions warrant standalone corrections. Collect other
 cosmetic-only suggestions in an issue rather than separate PRs.
 
 For capability organization and provider composition, use the
-[architecture map](docs/architecture.mermaid). Production factories in
+[architecture map](docs/architecture/architecture.mermaid). Production factories in
 `src/composition/` construct fresh providers without starting engines or acquiring
 targets; optional adapter failures must preserve successful peers. Run
 `npm run verify:test-discovery` after adding or moving tests. Resolved import
@@ -21,87 +21,8 @@ For analysis workflows and agent interfaces, follow the
 [performance priorities](AGENTS.md#performance). Explain the selected output
 scope, reuse/cache decisions, and relevant before/after measurements when these
 costs change.
-Use the [analysis optimization skill](.agents/skills/rea-analysis-optimization/SKILL.md)
-to locate provider and shared-workflow bottlenecks, preserve Evidence, and
-compare equivalent real tasks before claiming an improvement.
 
-When adding or changing an MCP tool, follow the [tool design guide](docs/tool-design.md) and preserve the canonical contracts and generated catalog.
-
-## Reporting issues
-
-Use the issue form that fits the report and keep it concise. For bugs, include
-the actual result, the shortest reproduction you ran, the tested version and
-environment, and the smallest useful output, artifact, screenshot, or source
-reference. Ground expected behavior in documentation, source, or a known-good
-version when available. State observed impact and frequency; keep untested scope
-and suspected causes explicit.
-
-Incomplete reports and intermittent failures are welcome. If a narrative answer
-or supporting evidence is unavailable, write `NOT_ENOUGH_INFO` and explain the
-gap. Clearly label source-only findings and proposed checks; do not claim runtime
-reproduction or results you did not observe. A root-cause analysis or fix is not
-required to report a problem. Documentation reports should identify the relevant
-passage or missing guidance and explain the correction or confusion.
-
-Feature and design proposals can start with a problem and desired outcome.
-Examples, prior art, and measurements help when available; ideas without them
-are welcome. Maintainers can investigate reports and help resolve open questions.
-Human ownership and readiness declarations apply to PRs as described below.
-
-## Pull request ownership and readiness
-
-AI-assisted contributions are welcome. Every PR must have a human owner who
-takes responsibility for the complete change, including code, tests,
-documentation, and claims produced with AI assistance. The PR author is the
-owner unless another human is named in the PR and explicitly accepts ownership.
-These requirements also apply to maintainer-authored PRs.
-
-Before requesting maintainer review, the human owner must:
-
-- Review the final diff and relevant existing code. Be able to explain the
-  problem, the chosen approach, how it fits REA, and meaningful edge cases.
-- Provide evidence that the change works. Summarize what was checked, the
-  observed results, and meaningful gaps in the PR body. Use focused tests,
-  representative CLI/MCP output, CI artifacts, screenshots, or other checks
-  appropriate to the change. For fixes, show the original failure and why the
-  regression coverage catches it when practical. Documentation-only changes
-  can use source, link, or rendered-document checks. Label source-derived
-  conclusions and proposed checks accurately; never report an unrun check as
-  passing. Follow the [verification requirements](#development-feedback-and-pr-verification)
-  for required checks and real-provider coverage.
-- Complete the **Author readiness** declaration in the PR template, explicitly
-  stating that the PR is ready for initial review.
-
-Keep the PR description concise and current. Explain the problem, observable
-outcome, approach, and useful evidence; link long logs or put them in optional
-details. Address actionable automated review findings and explain disagreements.
-Human ownership and review remain required when CI or an automated reviewer
-reports success. Readiness requests maintainer review; it does not grant scope
-approval or permission to merge.
-
-Draft PRs may request early feedback with open questions and incomplete checks.
-Leave the readiness declaration unchecked until the human owner has completed
-it. The declaration records initial readiness; later pushes do not invalidate
-it or require another human sign-off. Keep the PR description and affected
-validation current as work changes. AI agents must leave human declarations to
-the human owner and must not attest to a human review on their behalf.
-
-The `PR readiness` check reports pending for drafts and requires a named human
-owner and all three template declarations for non-drafts. It checks that the
-declaration is filled, not whether the code or evidence is correct. Existing PRs
-can copy the **Author readiness** section from the current template.
-Open PRs must have distinct head commits because GitHub shares commit statuses.
-
-Maintainers enable merge enforcement after the workflow is merged: run
-`gh workflow run pr-readiness.yml -f pull_request_number=NUMBER` for existing
-open PRs, then add `PR readiness` from GitHub Actions to the branch's required
-status checks alongside its existing checks. Deploy the workflow to each
-protected target branch before requiring it there. The workflow reads PR
-metadata using trusted default-branch code and writes only a commit status.
-
-Maintainers may return a PR to the author or close it when the problem is
-unsupported, validation is missing, or the owner cannot explain the change.
-Contributors are responsible for completing this work before requesting review.
+When adding or changing an MCP tool, follow the [tool design guide](docs/development/tool-design.md) and preserve the canonical contracts and generated catalog.
 
 ## Contribution scope
 
@@ -203,7 +124,7 @@ guarantee.
 Use the development toolchain pinned in `.nvmrc` and
 `package.json#packageManager`. Run `nvm use` before installing dependencies;
 installed-package runtime support is documented in
-[installation](docs/installation.md#start-setup).
+[installation](docs/getting-started/installation.md#start-setup).
 
 ```bash
 npm ci
@@ -228,10 +149,7 @@ manifest. A source checkout does not: `native/windows/build/` is ignored by
 Git, and neither `npm ci` nor `npm run build:cached` (or `npm run build`)
 produces `rea-windows-x64.node` or `manifest.json` in that directory.
 Windows workflows and tests that require native controls need these artifacts;
-this includes `run-exclusive` commands, which use the native Job Object to keep
-the artifact lock until every command descendant has exited. Without the
-artifacts, those controls are unavailable even after a successful runtime
-build.
+without them, those controls are unavailable even after a successful runtime build.
 
 Follow the [Windows native build guide](native/windows/README.md#build) before
 running those workflows from source. The artifact build requires Linux,
@@ -241,6 +159,10 @@ verification prerequisites. Keep the generated addon and manifest uncommitted.
 
 ## Documentation website
 
+Use the [documentation directory](docs/README.md) and
+[authoring guide](docs/development/documentation.md) for document ownership,
+domain-based feature specifications and architectural decision records.
+
 The VitePress site uses the Markdown files in `docs/`. Run `npm run docs:dev`
 for live editing, `npm run docs:build` to check the production build and
 links, and `npm run docs:preview` to preview that build at `/rea/`.
@@ -261,23 +183,6 @@ The separate GitHub Pages host uses only the manual
 **Settings → Pages → Build and deployment → Source** must be set to
 **GitHub Actions** before deploying there.
 
-### Translation corrections
-
-README editions and website editions have separate translation sources:
-
-- Find the language's `readme` path in the
-  [language inventory](website/locales/languages.json) and edit that file.
-  Locale codes and README suffixes can differ. Use the
-  [English README](README.md) to check commands, requirements, and analysis claims.
-- Edit `msgstr` values in `website/locales/<language>/messages.po` for website
-  text. Follow the [website translation guide](website/locales/README.md) for
-  the Python environment, catalog validation, and local preview. Preserve source
-  strings, contexts, placeholders, commands, paths, and recorded evidence.
-
-Before submitting a website translation, run the catalog and website checks in
-that guide. Translated HTML in `website/_site/` is generated; edit the PO catalog
-rather than the generated pages.
-
 ## Development feedback and PR verification
 
 For routine merges, wait for the required checks to pass for the current PR
@@ -294,7 +199,7 @@ npm run check:fast
 `test:local` runs source tests without building. `check:changed` combines cached
 static checks with source tests affected since the merge base with `origin/main`.
 Import-graph selection can miss runtime registration, bridges, and generated data;
-select relevant boundary tests explicitly. See [testing](docs/testing.md#developer-commands)
+select relevant boundary tests explicitly. See [testing](docs/development/testing.md#developer-commands)
 for commands, test placement, pruning, and real-provider prerequisites.
 
 Before requesting review, run relevant tests and `npm run check`; add
@@ -361,8 +266,8 @@ Run `npm run verify:hopper` on a supported macOS host or
 `npm run verify:hopper:linux` on the supported Linux demo runner. These build
 native fixtures and verify the installed engine through CLI/MCP; package or
 simulated-provider checks do not establish engine behavior. See
-[real-toolchain verification](docs/testing.md#end-to-end-integration-and-golden-evidence)
-for prerequisites and scope, and [Hopper setup](docs/installation.md#hopper)
+[real-toolchain verification](docs/development/testing.md#end-to-end-integration-and-golden-evidence)
+for prerequisites and scope, and [Hopper setup](docs/getting-started/installation.md#hopper)
 for supported hosts and unattended startup.
 
 Use the default `build/conformance/manifest.json` unless explicitly verifying
@@ -371,7 +276,7 @@ Generated fixtures and manifests remain ignored.
 
 ## Maintainer release checklist
 
-Use the [release guide](docs/releasing.md). Main pushes automatically refresh a
+Use the [release guide](docs/development/releasing.md). Main pushes automatically refresh a
 Release Please PR with the next version and changelog. Review its migration
 notes, wait for the current CI checks to pass, and merge it into main to publish.
 

README.md

@@ -1,7 +1,6 @@
 <div align="center">
 
 **English** · [简体中文](docs/readme/README_zh.md) · [繁體中文](docs/readme/README_zh-TW.md) · [日本語](docs/readme/README_ja.md) · [한국어](docs/readme/README_ko.md) · [Türkçe](docs/readme/README_tr.md) · [Русский](docs/readme/README_ru.md) · [Tiếng Việt](docs/readme/README_vi.md) · [ไทย](docs/readme/README_th.md) · [Deutsch](docs/readme/README_de.md) · [Español](docs/readme/README_es.md) · [Français](docs/readme/README_fr.md) · [Українська](docs/readme/README_uk.md) · [Polski](docs/readme/README_pl.md) · [Português (Brasil)](docs/readme/README_pt-BR.md) · [العربية](docs/readme/README_ar.md) · [فارسی](docs/readme/README_fa.md) · [Bahasa Indonesia](docs/readme/README_id.md) · [Italiano](docs/readme/README_it.md)
-· [Ελληνικά](docs/readme/README_el.md) · [മലയാളം](docs/readme/README_ml.md)
 
 # REA: Reverse Engineer Anything
 
@@ -10,7 +9,7 @@
 **See a feature you like. Understand how it works, down to the binary level.**
 
 [![npm version](https://img.shields.io/npm/v/rea-agents?style=flat-square&color=cb3837)](https://www.npmjs.com/package/rea-agents)
-[![MCP tool catalog](https://img.shields.io/badge/MCP-tool_catalog-5c4ee5?style=flat-square)](docs/mcp-contracts.md#generated-catalog)
+[![MCP tool catalog](https://img.shields.io/badge/MCP-tool_catalog-5c4ee5?style=flat-square)](docs/reference/mcp-contracts.md#generated-catalog)
 [![Node.js requirements](https://img.shields.io/badge/Node.js-requirements-339933?style=flat-square&logo=nodedotjs&logoColor=white)](#what-you-can-analyze)
 [![skills.sh](https://skills.sh/b/morluto/rea?style=flat-square)](https://skills.sh/morluto/rea/reverse-engineer-anything)
 [![MIT license](https://img.shields.io/badge/license-MIT-f4c430?style=flat-square)](LICENSE)
@@ -24,16 +23,6 @@
 
 <code>npx rea-agents setup</code>
 
-</div>
-
-> [!IMPORTANT]
-> Get REA from [morluto/rea](https://github.com/morluto/rea),
-> [rea.tools](https://rea.tools/), or the [rea-agents npm package](https://www.npmjs.com/package/rea-agents).
-> Follow the installation and release links from these official sources. A similar
-> repository name or copied README does not establish that a download is official.
-
-<div align="center">
-
 <br />
 
 <img src="docs/assets/rea-hopper-analysis.png" alt="REA launching its analysis bridge inside Hopper while inspecting a native binary" width="1200" />
@@ -68,11 +57,6 @@ Setup registers REA with your agent and installs matching workflow instructions.
 
 ## Quick start
 
-On Linux, Ghidra, JADX, firmware tool launches and static JavaScript/Electron
-analysis require a procps-compatible `ps` on REA's `PATH` for process ownership
-checks. Recovery steps are in `docs/installation.md` under
-"Linux owned-process prerequisite".
-
 ### Set up your agent
 
 With Node.js and npm installed, run:
@@ -86,8 +70,8 @@ REA's MCP server and matching workflow instructions, with backups of existing
 configuration. Restart your agent afterward.
 
 Setup supports Claude Code, Codex, Cursor, Gemini CLI, Grok Build and
-[other agents](docs/installation.md#supported-agents). See
-[installation and setup](docs/installation.md) for provider configuration and
+[other agents](docs/getting-started/installation.md#supported-agents). See
+[installation and setup](docs/getting-started/installation.md) for provider configuration and
 manual MCP registration.
 
 ### Ask your agent
@@ -118,7 +102,7 @@ rea --help
 ```
 
 For native analysis, configure a provider first. See the
-[CLI and Evidence guide](docs/cli.md) for native commands, provider selection,
+[CLI and Evidence guide](docs/getting-started/cli.md) for native commands, provider selection,
 snapshots and scripting.
 
 ### Update REA
@@ -132,14 +116,6 @@ For a CLI installed with `npm install --global` or `bun add --global`:
 rea update
 ```
 
-`rea --update` is an alias for this verified workflow and accepts the same global
-output flags. Use `rea update` when combining it with other command controls.
-
-Updater commands retain at most 4 MiB of stdout and stderr combined. Oversized
-metadata replies are rejected after the command exits; verbose installs continue
-with bounded diagnostics. Human progress output respects terminal backpressure
-and waits for submitted writes to finish.
-
 Bun global updates require Bun 1.2.17 or later. With an older Bun release,
 upgrade Bun manually before running `rea update`.
 
@@ -174,56 +150,46 @@ CLI commands use the same workflows.
 REA requires Node.js 22.x (>=22.19), 24.x (>=24.11), or 26+, plus npm.
 Additional tools and host support depend on the target:
 
-| Target                 | What REA returns                                                                                  | Requirements and guide                                                                                                                |
-| ---------------------- | ------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------- |
-| Desktop installations  | Runtime candidates, supporting files, component markers and next probes                           | Built-in bounded directory/header inspection; [desktop applications](docs/desktop-applications.md)                                    |
-| Native binaries        | Pseudocode, assembly, strings, symbols, calls and references                                      | Hopper, Ghidra or IDA; [native analysis](docs/native-investigation.md)                                                                |
-| Offline ELF layout     | Sections, segments, original symbols/relocations and static mitigation candidates                 | Caller-supplied pwntools on Linux x64; [binary diagnostics](docs/binary-diagnostics.md)                                               |
-| Go binaries            | Embedded compiler version, modules, replacements and build settings                               | Built-in static ELF/PE/thin Mach-O inspection; no Go installation required                                                            |
-| IL2CPP metadata        | Unity global-metadata.dat assembly images, type and method names and index ranges                 | Built-in static decoding of versions 24, 27, 29, 31 and 39; no Unity required                                                         |
-| Godot PCK              | Archive inventory and extraction, original header/directory facts and selected content identities | Built-in static formats 2, 3 and 4; no Godot required                                                                                 |
-| Rust binaries          | Embedded cargo-auditable crate names, versions, sources and dependency edges                      | Built-in static ELF/PE/thin Mach-O inspection; [Rust binaries](docs/rust-binaries.md)                                                 |
-| WASM artifact          | Validation, sections, exact import/export WAT forms and decoded WAT                               | Caller-supplied WABT 1.0.42; `inspect_wasm_artifact`                                                                                  |
-| EVM bytecode           | Dispatch selectors, byte offsets, inferred arguments and mutability                               | Local raw/hex carrier on Linux x64; [offline EVM guide](docs/evm-bytecode.md)                                                         |
-| SQLite databases       | Tables, columns, indexes, views, triggers and selected ordinary-table rows                        | Local database/WAL snapshot; Node.js 24.x >=24.15 or 26+ with native SQLite limits                                                    |
-| Recorded Linux crashes | Raw notes, every recorded thread's registers/signals and optional mapping candidates              | Caller-supplied pwntools on Linux x64; optional GDB/pwndbg; [recorded crashes](docs/recorded-crashes.md)                              |
-| JavaScript / Electron  | Modules, imports, source maps, routes, IPC and native add-on relationships                        | Node.js and npm; Linux: procps-compatible `ps`; [application analysis](docs/javascript-application-workflows.md)                      |
-| Websites               | Page structure, scripts, network observations and requested screenshots                           | A Chrome-family browser; [browser analysis](docs/browser-observation.md)                                                              |
-| Saved network captures | Requests, responses, exposed payloads and source locations                                        | HAR or Fiddler Everywhere SAZ; mitmdump on Linux for native mitmproxy; [capture guide](docs/web-network-captures.md)                  |
-| .NET assemblies        | Metadata, CIL instructions, declared native dependencies and build comparisons                    | None (static only); [managed-code guide](docs/managed-code-analysis.md)                                                               |
-| Android APKs           | Manifest declarations, classes, decompiled methods and references                                 | Headless JADX and a full JDK on Linux/macOS/Windows x64; [Android guide](docs/android-analysis.md)                                    |
-| Android devices        | Devices, packages, processes, logs, dumps, screen captures, and APK/file transfers                | Caller-supplied adb (emulator or hardware); [ADB guide](docs/adb-device-analysis.md)                                                  |
-| JEB projects           | Engine-backed project units, artifact digests and type/method pseudo-code                         | A caller-started JEB client serving MCP, selected with REA_JEB_MCP_URL; [JEB guide](docs/jeb-analysis.md)                             |
-| Android resources      | Decoded manifest, string tables, locales and version facts                                        | Caller-supplied Apktool launcher; [resource guide](docs/apktool-resource-analysis.md)                                                 |
-| Flutter apps           | Dart snapshot hash, per-ABI library digests and engine build provenance                           | None (static APK parsing); [Flutter guide](docs/flutter-analysis.md)                                                                  |
-| Firmware               | Regions, extraction results and native-analysis handoffs                                          | Binwalk / Unblob on Linux; [firmware guide](docs/firmware-analysis.md)                                                                |
-| Recorded packets       | Selected fields, repeated values, filters and decode-as rules                                     | Linux: TShark 4.x + prlimit; [capture guide](docs/packet-captures.md)                                                                 |
-| Packet summaries       | Endpoints, DNS, TLS SNI, protocol distribution and HTTP requests                                  | Caller-supplied tshark and capinfos (Linux-verified); [pcap guide](docs/pcap-analysis.md)                                             |
-| Recorded logic signals | Decoder annotations, sample ranges and diagnostics                                                | Linux: sigrok-cli 0.7.2 + prlimit; [signal recordings](docs/signal-recordings.md)                                                     |
-| Packages and resources | File inventories, digests, plists, Apple bundle anatomy and extracted resources                   | [Artifact and JavaScript guide](docs/javascript-artifact-reconstruction.md), [Apple applications](docs/apple-application-analysis.md) |
-| Process behavior       | Terminal output, interactions, exit and filesystem observations, and run comparisons              | Linux/macOS with a native PTY; [process capture](docs/process-capture.md)                                                             |
+| Target                 | What REA returns                                                                     | Requirements and guide                                                                                                                                               |
+| ---------------------- | ------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Native binaries        | Pseudocode, assembly, strings, symbols, calls and references                         | Hopper, Ghidra or IDA; [native analysis](https://rea.tools/guides/native/)                                                                                           |
+| Offline ELF layout     | Sections, segments, original symbols/relocations and static mitigation candidates    | Caller-supplied pwntools on Linux x64; [binary diagnostics](docs/guides/native/binary-diagnostics.md)                                                                |
+| Go binaries            | Embedded compiler version, modules, replacements and build settings                  | Built-in static ELF/PE/thin Mach-O inspection; no Go installation required                                                                                           |
+| WASM artifact          | Validation, sections, exact import/export WAT forms and decoded WAT                  | Caller-supplied WABT 1.0.42; `inspect_wasm_artifact`                                                                                                                 |
+| EVM bytecode           | Dispatch selectors, byte offsets, inferred arguments and mutability                  | Local raw/hex carrier on Linux x64; [offline EVM guide](docs/guides/evm/evm-bytecode.md)                                                                             |
+| SQLite databases       | Tables, columns, indexes, views, triggers and selected ordinary-table rows           | Local database/WAL snapshot; Node.js 24.x >=24.15 or 26+ with native SQLite limits                                                                                   |
+| Recorded Linux crashes | Raw notes, every recorded thread's registers/signals and optional mapping candidates | Caller-supplied pwntools on Linux x64; optional GDB/pwndbg; [recorded crashes](docs/guides/native/recorded-crashes.md)                                               |
+| JavaScript / Electron  | Modules, imports, source maps, routes, IPC and native add-on relationships           | Node.js and npm; [application analysis](https://rea.tools/guides/javascript/)                                                                                        |
+| Websites               | Page structure, scripts, network observations and requested screenshots              | A Chrome-family browser; [browser analysis](https://rea.tools/guides/browser/)                                                                                       |
+| Saved network captures | Requests, responses, exposed payloads and source locations                           | HAR or Fiddler Everywhere SAZ; mitmdump on Linux for native mitmproxy; [capture guide](docs/guides/web/web-network-captures.md)                                      |
+| .NET assemblies        | Metadata, CIL instructions, declared native dependencies and build comparisons       | None (static only); [managed-code guide](docs/guides/managed/managed-code-analysis.md)                                                                               |
+| Android APKs           | Manifest declarations, classes, decompiled methods and references                    | Headless JADX and a full JDK on Linux/macOS/Windows x64; [Android guide](docs/guides/android/android-analysis.md)                                                    |
+| Android devices        | Devices, packages, processes, logs, dumps, screen captures, and APK/file transfers   | Caller-supplied adb (emulator or hardware); [ADB guide](docs/guides/android/adb-device-analysis.md)                                                                  |
+| JEB projects           | Engine-backed project units, artifact digests and type/method pseudo-code            | A caller-started JEB client serving MCP, selected with REA_JEB_MCP_URL; [JEB guide](docs/providers/jeb-analysis.md)                                                  |
+| Android resources      | Decoded manifest, string tables, locales and version facts                           | Caller-supplied Apktool launcher; [resource guide](docs/guides/android/apktool-resource-analysis.md)                                                                 |
+| Flutter apps           | Dart snapshot hash, per-ABI library digests and engine build provenance              | None (static APK parsing); [Flutter guide](docs/guides/android/flutter-analysis.md)                                                                                  |
+| Firmware               | Regions, extraction results and native-analysis handoffs                             | Binwalk / Unblob on Linux; [firmware guide](docs/guides/firmware/firmware-analysis.md)                                                                               |
+| Recorded packets       | Selected fields, repeated values, filters and decode-as rules                        | Linux: TShark 4.x + prlimit; [capture guide](docs/guides/data/packet-captures.md)                                                                                    |
+| Packet summaries       | Endpoints, DNS, TLS SNI, protocol distribution and HTTP requests                     | Caller-supplied tshark and capinfos (Linux-verified); [pcap guide](docs/guides/data/pcap-analysis.md)                                                                |
+| Recorded logic signals | Decoder annotations, sample ranges and diagnostics                                   | Linux: sigrok-cli 0.7.2 + prlimit; [signal recordings](docs/guides/signals/signal-recordings.md)                                                                     |
+| Packages and resources | File inventories, digests, plists, Apple bundle anatomy and extracted resources      | [Artifact and JavaScript guide](docs/guides/javascript/javascript-artifact-reconstruction.md), [Apple applications](docs/guides/apple/apple-application-analysis.md) |
+| Process behavior       | Terminal output, interactions, exit and filesystem observations, and run comparisons | Linux/macOS with a native PTY; [process capture](docs/guides/runtime/process-capture.md)                                                                             |
 
 Static JavaScript and .NET inspection read the supplied files without running
 the application. Runtime capture runs or interacts with the selected target
 using your user permissions; each runtime guide describes its effects.
 
-For offline native-binary inspection, REA also supports caller-supplied GNU
-objdump and Rizin. See the [reverse-engineering tools guide](docs/reverse-engineering-tools.md)
-for provider setup, CLI commands, and Evidence limitations. REA does not install
-or update either provider.
-
 <a id="choosing-a-deep-analysis-provider"></a>
 
 Native formats and host support vary by provider. See
-[Hopper and Ghidra setup](docs/installation.md#hopper), the
-[IDA guide](docs/ida-provider.md) (including an optional native MCP bridge), the
-[Kuna decompiler guide](docs/kuna-provider.md), and
-[experimental Windows Ghidra support](docs/windows-ghidra-p0.md).
-Ghidra also supports [16-bit DOS analysis](docs/ghidra-dos.md).
+[Hopper and Ghidra setup](docs/getting-started/installation.md#hopper), the
+[IDA guide](docs/providers/ida-provider.md) (including an optional native MCP bridge), and
+[experimental Windows Ghidra support](docs/providers/windows-ghidra-p0.md).
+Ghidra also supports [16-bit DOS analysis](docs/providers/ghidra-dos.md).
 For large binaries, raise the provider's startup deadline with
 `REA_GHIDRA_STARTUP_TIMEOUT_MS` or `REA_HOPPER_STARTUP_TIMEOUT_MS`.
-For provider selection, see the [CLI guide](docs/cli.md#choose-a-provider).
-Check [release availability](docs/installation.md#released-package-and-main)
+For provider selection, see the [CLI guide](docs/getting-started/cli.md#choose-a-provider).
+Check [release availability](docs/getting-started/installation.md#released-package-and-main)
 for features added since the latest npm release.
 
 ## Showcases
@@ -266,8 +232,8 @@ your question, how REA helped, and what you found.
 <summary><strong>Which agents can use REA?</strong></summary>
 
 Any agent that supports local MCP servers. Setup configures the
-[supported agents](docs/installation.md#supported-agents); other clients can use
-[manual MCP registration](docs/installation.md#mcp-registry).
+[supported agents](docs/getting-started/installation.md#supported-agents); other clients can use
+[manual MCP registration](docs/getting-started/installation.md#mcp-registry).
 
 </details>
 
@@ -276,7 +242,7 @@ Any agent that supports local MCP servers. Setup configures the
 
 Deep native analysis uses one of them. Static JavaScript and .NET inspection
 work without a native analysis engine. Setup can install Hopper after approval;
-Ghidra and IDA use your existing installations. See [provider setup](docs/installation.md#hopper).
+Ghidra and IDA use your existing installations. See [provider setup](docs/getting-started/installation.md#hopper).
 
 </details>
 
@@ -287,7 +253,7 @@ REA starts Hopper when an operation needs it. On macOS, a first-run dialog may
 ask you to choose demo mode or activate your license. Complete that prompt in the
 same user session before your first CLI/MCP operation or unattended job. Open
 Hopper manually if needed. See
-[Hopper startup and troubleshooting](docs/installation.md#launcher-paths-and-troubleshooting).
+[Hopper startup and troubleshooting](docs/getting-started/installation.md#launcher-paths-and-troubleshooting).
 
 </details>
 
@@ -296,7 +262,7 @@ Hopper manually if needed. See
 
 The skill supplies investigation instructions for your agent. Use `npx rea-agents setup`
 to register REA's MCP server and install the matching instructions, then restart
-your agent. See [skill-only installation](docs/installation.md#skill-only-installation).
+your agent. See [skill-only installation](docs/getting-started/installation.md#skill-only-installation).
 
 </details>
 
@@ -345,18 +311,18 @@ with your REA version, target type, steps to reproduce and error output.
 Start with the website's [worked guides](https://rea.tools/guides/).
 For exact options, prerequisites and result contracts:
 
-- [Installation and setup](docs/installation.md): agent registration, provider configuration, updates and uninstall.
-- [Readiness and troubleshooting](docs/installation.md#check-readiness-for-your-task): diagnose one agent or analysis engine.
-- [CLI and Evidence](docs/cli.md): commands, provider selection, snapshots, import/export and exit statuses.
-- [MCP contracts](docs/mcp-contracts.md) and [agent prompts](docs/mcp-prompts.md): tool results, sessions and guided investigations.
-- [Tool catalog](docs/mcp-contracts.md#generated-catalog): generated inventory of tools, providers and CLI commands.
-- [Roadmap](docs/roadmap.md): planned work and capability trackers.
+- [Installation and setup](docs/getting-started/installation.md): agent registration, provider configuration, updates and uninstall.
+- [Readiness and troubleshooting](docs/getting-started/installation.md#check-readiness-for-your-task): diagnose one agent or analysis engine.
+- [CLI and Evidence](docs/getting-started/cli.md): commands, provider selection, snapshots, import/export and exit statuses.
+- [MCP contracts](docs/reference/mcp-contracts.md) and [agent prompts](docs/getting-started/mcp-prompts.md): tool results, sessions and guided investigations.
+- [Tool catalog](docs/reference/mcp-contracts.md#generated-catalog): generated inventory of tools, providers and CLI commands.
+- [Roadmap](docs/development/roadmap.md): planned work and capability trackers.
 
 Report vulnerabilities through [SECURITY.md](SECURITY.md).
 
 ## Star history
 
-🎉 **300,000 GitHub stars — thank you!**
+🎉 **180,000 GitHub stars — thank you!**
 
 Thanks to everyone using REA, reporting bugs, requesting features, testing builds, and contributing fixes.
 
@@ -385,8 +351,8 @@ report a bug or suggest a feature, or [send a pull request](https://github.com/m
 to improve the code or docs.
 
 See [CONTRIBUTING.md](CONTRIBUTING.md) for development setup and checks,
-[testing](docs/testing.md) for verification lanes, and the
-[architecture map](docs/architecture.mermaid) for the project structure.
+[testing](docs/development/testing.md) for verification lanes, and the
+[architecture map](docs/architecture/architecture.mermaid) for the project structure.
 
 ## License
 

SECURITY.md

@@ -27,7 +27,7 @@ provider-dependent behavior to be reproduced safely.
 REA authenticates its Hopper and Ghidra bridges with per-session random
 capability tokens. POSIX uses current-user Unix sockets; Windows Ghidra uses
 authenticated loopback TCP with a private NTFS runtime whose DACL admits only
-the current user and SYSTEM. See [Windows Ghidra P0](docs/windows-ghidra-p0.md#private-runtime-transport-and-lifecycle).
+the current user and SYSTEM. See [Windows Ghidra P0](docs/providers/windows-ghidra-p0.md#private-runtime-transport-and-lifecycle).
 Tokens are transferred through private session descriptors rather than process
 arguments or environment variables.
 This is not a sandbox and does not protect against malicious processes already

THIRD_PARTY_NOTICES.md

@@ -58,7 +58,6 @@ pin inspection sources; they are not included in the npm package.
 | ghidra-nativeaot               | [MIT](https://github.com/Washi1337/ghidra-nativeaot/blob/effeb734fc570c32650f88b159608979dc7b423e/LICENSE.md)                                                                                                                                            | Pinned inspection source; derived parser attribution above.                                                                                                                                                                 |
 | JADX                           | [Apache-2.0](https://github.com/skylot/jadx/blob/v1.5.6/LICENSE)                                                                                                                                                                                         | The audited jadx-headless-mcp source uses JADX 1.5.6 for Android decompilation; the engine JAR is separately supplied.                                                                                                      |
 | jadx-headless-mcp              | [Apache-2.0](https://github.com/1013503897/jadx-headless-mcp/blob/5844800a486d2248fa949b74c9896285f5b54de2/LICENSE)                                                                                                                                      | v0.7.1; pinned submodule and user-supplied JAR.                                                                                                                                                                             |
-| Kuna                           | [Apache-2.0](https://github.com/Noelo-Lab/kuna/blob/v1.833/LICENSE), with its [NOTICE](https://github.com/Noelo-Lab/kuna/blob/v1.833/NOTICE)                                                                                                             | Bring your own `kuna`; REA verified 1.833 and never downloads, installs or bundles it. REA invokes it as a separate process.                                                                                                |
 | Apktool                        | [Apache-2.0](https://github.com/iBotPeaches/Apktool/blob/master/LICENSE.md)                                                                                                                                                                              | User-supplied Android resource decoder.                                                                                                                                                                                     |
 | Binwalk                        | [MIT](https://github.com/ReFirmLabs/binwalk/blob/4fdab3d464d97b68e0af9088df3f9e2e1545b21c/LICENSE)                                                                                                                                                       | v3.1.0; pinned submodule and user-supplied firmware engine.                                                                                                                                                                 |
 | Unblob                         | [MIT](https://github.com/onekey-sec/unblob/blob/1fcc7a0a584a70a96c31f5a276c20944d199a089/LICENSE)                                                                                                                                                        | 26.6.4; pinned submodule and user-supplied firmware engine.                                                                                                                                                                 |

bridge/android/ReaJadxBridge.java

@@ -15,14 +15,11 @@ import java.util.*;
 import java.util.concurrent.CountDownLatch;
 import java.util.stream.Collectors;
 import kotlin.Unit;
-import kotlin.ResultKt;
-import kotlin.coroutines.Continuation;
-import kotlin.coroutines.CoroutineContext;
 import kotlin.coroutines.EmptyCoroutineContext;
-import kotlin.coroutines.intrinsics.IntrinsicsKt;
 import kotlinx.coroutines.BuildersKt;
 import kotlinx.io.CoreKt;
 import kotlinx.io.JvmCoreKt;
+import kotlinx.serialization.json.JsonObject;
 
 /** REA-owned metadata boundary for the unmodified jadx-headless-mcp 0.7.1 JAR. */
 class ReaJadxBridge {
@@ -31,8 +28,7 @@ class ReaJadxBridge {
   private JadxSession indexedSession;
   private Map<String, List<ClassSnapshot>> classes = Map.of();
 
-  private record MethodSnapshot(String name, String rawName, String shortId, List<String> bodyAbsenceMarkers,
-      Map<String, Object> summary) {}
+  private record MethodSnapshot(String name, String shortId, Map<String, Object> summary) {}
   private record ClassSnapshot(JavaClass node, List<MethodSnapshot> methods, Map<String, Object> summary) {}
 
   private static final class InputFailure extends IllegalArgumentException {
@@ -48,93 +44,15 @@ class ReaJadxBridge {
 
   private static CallToolResult json(Object value) { return text(JSON.toJson(value), false); }
 
-  /** Translate the typed load outcome before upstream drops its exception identity. */
-  static Object loadResult(Object result) {
-    try { ResultKt.throwOnFailure(result); }
-    catch (Throwable failure) {
-      if (failure instanceof java.util.concurrent.CancellationException
-          || failure instanceof Error && !(failure instanceof OutOfMemoryError)) return result;
-      if (failure instanceof OutOfMemoryError) {
-        String reason = failure.getMessage();
-        boolean heap = "Java heap space".equals(reason) || "GC overhead limit exceeded".equals(reason);
-        Map<String, Object> reply = new LinkedHashMap<>();
-        reply.put("kind", "jvm-memory-failure");
-        reply.put("memory_area", heap ? "heap" : "unknown");
-        reply.put("exception_type", "java.lang.OutOfMemoryError");
-        if (reason != null) reply.put("message", reason);
-        reply.put("max_heap_bytes", Runtime.getRuntime().maxMemory());
-        return text(JSON.toJson(reply), true);
-      }
-      return text("load failed: " + failure.getMessage(), true);
-    }
-    SessionHolder.LoadResult loaded = (SessionHolder.LoadResult) result;
-    Map<String, Object> reply = new LinkedHashMap<>();
-    reply.put("state", "LOADED");
-    reply.put("apk_path", loaded.getApkPath());
-    reply.put("class_count", loaded.getClassCount());
-    reply.put("raw_class_count", loaded.getRawClassCount());
-    reply.put("resource_count", loaded.getResourceCount());
-    reply.put("load_duration_ms", loaded.getLoadDurationMs());
-    reply.put("decompile_timeout_ms", loaded.getDecompileTimeoutMs());
-    reply.put("threads", loaded.getThreads());
-    reply.put("code_cache_size", loaded.getCodeCacheSize());
-    reply.put("resources", loaded.getResourceMode());
-    if (!loaded.getIncludePackages().isEmpty()) reply.put("include_packages", loaded.getIncludePackages());
-    if (!loaded.getExcludePackages().isEmpty()) reply.put("exclude_packages", loaded.getExcludePackages());
-    return json(reply);
-  }
-
-  private Object load(kotlinx.serialization.json.JsonObject arguments, SessionConfig defaults,
-      Continuation<? super CallToolResult> continuation) {
-    JsonObject args = JsonParser.parseString(arguments.toString()).getAsJsonObject();
-    String path = string(args, "path");
-    SessionConfig options = defaults.withLoadOverrides(
-        optionalString(args, "include_packages"), optionalString(args, "exclude_packages"),
-        args.has("threads") ? integer(args, "threads", 1) : null,
-        args.has("code_cache_size") ? integer(args, "code_cache_size", 64) : null,
-        optionalString(args, "resources"));
-    return loadCall(next -> holder.load(path, options, next), continuation);
-  }
-
-  static Object loadCall(kotlin.jvm.functions.Function1<Continuation<SessionHolder.LoadResult>, Object> load,
-      Continuation<? super CallToolResult> continuation) {
-    var forwarded = new java.util.concurrent.atomic.AtomicBoolean();
-    Continuation<SessionHolder.LoadResult> resumed = new Continuation<>() {
-      public CoroutineContext getContext() { return continuation.getContext(); }
-      public void resumeWith(Object result) {
-        if (!forwarded.compareAndSet(false, true)) throw new IllegalStateException("Load resumed twice");
-        Object translated;
-        try { translated = loadResult(result); }
-        catch (Throwable failure) { translated = ResultKt.createFailure(failure); }
-        // Keep the consumer outside the translation catch, including inline completion.
-        continuation.resumeWith(translated);
-      }
-    };
-    Object result;
-    try { result = load.invoke(resumed); }
-    catch (Throwable failure) {
-      if (forwarded.get()) ResultKt.throwOnFailure(ResultKt.createFailure(failure));
-      result = ResultKt.createFailure(failure);
-    }
-    if (result == IntrinsicsKt.getCOROUTINE_SUSPENDED()) return result;
-    Object translated = loadResult(result);
-    ResultKt.throwOnFailure(translated);
-    return translated;
-  }
-
-  private static String optionalString(JsonObject args, String name) {
-    return args.has(name) ? string(args, name) : null;
-  }
-
   private static String string(JsonObject args, String name) {
-    JsonElement value = args.get(name);
+    JsonElement value = JsonParser.parseString(args.toString()).getAsJsonObject().get(name);
     if (value == null || !value.isJsonPrimitive() || !value.getAsJsonPrimitive().isString())
       throw new IllegalArgumentException(name + " must be a string");
     return value.getAsString();
   }
 
   private static int integer(JsonObject args, String name, int fallback) {
-    JsonElement value = args.get(name);
+    JsonElement value = JsonParser.parseString(args.toString()).getAsJsonObject().get(name);
     if (value == null) return fallback;
     if (!value.isJsonPrimitive() || !value.getAsJsonPrimitive().isNumber())
       throw new IllegalArgumentException(name + " must be a nonnegative integer");
@@ -172,13 +90,10 @@ class ReaJadxBridge {
             if (!shortId.startsWith(rawName + "("))
               throw new IllegalStateException("JADX method ID has no raw-name prefix: " + shortId);
             String descriptor = shortId.substring(rawName.length());
-            List<String> bodyAbsenceMarkers = new ArrayList<>();
-            if (method.getAccessFlags().isNative()) bodyAbsenceMarkers.add("native_method");
-            if (method.getAccessFlags().isAbstract()) bodyAbsenceMarkers.add("abstract_method");
             String signature = name + "(" + method.getArgTypes().stream()
                 .map(Object::toString).collect(Collectors.joining(", "))
                 + "): " + method.getReturnType().toString();
-            return new MethodSnapshot(name, rawName, shortId, List.copyOf(bodyAbsenceMarkers), Map.of(
+            return new MethodSnapshot(name, shortId, Map.of(
                 "name", name, "signature", signature,
                 "dex_descriptor", descriptor,
                 "is_constructor", method.isConstructor(), "def_pos", 0));
@@ -225,52 +140,16 @@ class ReaJadxBridge {
 
   private JadxSession.SmartCode methodBody(JadxSession current, ClassSnapshot cls,
       MethodSnapshot selected, JavaMethod method) {
-    // Access flags belong to the parsed member, before code generation rewrites it.
-    // These methods have no Java body; source slicing can include unrelated members.
-    if (!selected.bodyAbsenceMarkers().isEmpty())
-      return new JadxSession.SmartCode("", "java", false, selected.bodyAbsenceMarkers());
+    if (!selected.shortId().equals("<clinit>()V"))
+      return current.getMethodBodySmart(method, current.getMaxSourceBytes(), true);
     // Java code generation can fold all or part of <clinit> into field declarations.
     // Its method text cannot establish coverage, even when a static block remains.
-    if (selected.shortId().equals("<clinit>()V"))
-      return exactMethodSmali(current, cls, selected, List.of("static_initializer_disassembly"));
-    String java = current.getMethodSource(method);
-    if (java.startsWith("// ERROR:")) throw new IllegalArgumentException(java);
-    // The upstream placeholder means only that Java code was omitted, including
-    // methods merged into synthetic bridges. Access flags established absence above.
-    if (java.isEmpty() || java.equals(
-        "// method exists but has no decompiled body (native/abstract)"))
-      return exactMethodSmali(current, cls, selected, List.of("java_body_unavailable"));
-    List<String> markers = DecompileFailureKt.detectDecompileFailure(java);
-    if (markers.stream().anyMatch(DecompileFailureKt.getSTRONG_FAILURE_MARKERS()::contains))
-      return exactMethodSmali(current, cls, selected, markers);
+    JadxSession.MethodSmali smali = current.getMethodSmali(cls.node(), method.getName());
+    if (!smali.getFound() || smali.getBlocks().size() != 1)
+      throw new IllegalArgumentException("Static initializer disassembly requires one exact method: " + selected.shortId());
     return new JadxSession.SmartCode(
-        TextUtilKt.truncateToBytes(java, current.getMaxSourceBytes()), "java", false, markers);
-  }
-
-  private JadxSession.SmartCode exactMethodSmali(JadxSession current, ClassSnapshot cls,
-      MethodSnapshot selected, List<String> markers) {
-    JadxSession.MethodSmali smali = current.getMethodSmali(cls.node(), selected.rawName());
-    String block = selectMethodSmali(smali, selected.shortId());
-    return new JadxSession.SmartCode(
-        TextUtilKt.truncateToBytes(block, current.getMaxSourceBytes()), "smali", true, markers);
-  }
-
-  private static String selectMethodSmali(JadxSession.MethodSmali smali, String shortId) {
-    if (!smali.getFound())
-      throw new IllegalArgumentException("JADX could not disassemble " + shortId
-          + (smali.getNote() == null ? "" : ": " + smali.getNote()));
-    // Upstream returns every same-name overload, and can return an unterminated
-    // trailing block. Match the full original identity before applying output limits.
-    List<String> matches = smali.getBlocks().stream().filter(block -> {
-      String header = block.lines().findFirst().orElse("").strip();
-      return header.startsWith(".method ") && header.endsWith(" " + shortId);
-    }).toList();
-    if (matches.size() != 1)
-      throw new IllegalArgumentException("Disassembly could not establish one selected method: " + shortId);
-    String block = matches.get(0);
-    if (!block.stripTrailing().endsWith("\n.end method"))
-      throw new IllegalArgumentException("Selected method disassembly is incomplete: " + shortId);
-    return block;
+        TextUtilKt.truncateToBytes(smali.getBlocks().get(0), current.getMaxSourceBytes()),
+        "smali", true, List.of("static_initializer_disassembly"));
   }
 
   // The local transport admits 8 MiB frames. Reserve 1 KiB for the fixed
@@ -324,8 +203,7 @@ class ReaJadxBridge {
     return new DirectInvokes(sites, exhaustive[0]);
   }
 
-  private CallToolResult handle(String name, kotlinx.serialization.json.JsonObject input) {
-    JsonObject args = JsonParser.parseString(input.toString()).getAsJsonObject();
+  private CallToolResult handle(String name, JsonObject args) {
     if (name.equals("rea_jvm_status")) return json(Map.of(
         "engine_reported_version", BuildInfo.VERSION,
         "max_heap_bytes", Runtime.getRuntime().maxMemory(),
@@ -335,25 +213,12 @@ class ReaJadxBridge {
     JadxSession current = session();
     if (name.equals("list_classes")) {
       List<String> names = current.getClassFqns();
-      String query = args.has("query") ? string(args, "query") : "";
       int offset = integer(args, "offset", 0);
       int limit = integer(args, "limit", 200);
       int start = Math.min(offset, names.size());
-      int end = start;
-      List<String> items;
-      if (query.isEmpty()) {
-        end = (int) Math.min((long) start + limit, names.size());
-        items = names.subList(start, end);
-      } else {
-        items = new ArrayList<>();
-        while (end < names.size() && items.size() < limit) {
-          String nameInInventory = names.get(end++);
-          if (nameInInventory.contains(query)) items.add(nameInInventory);
-        }
-      }
-      return json(Map.of("total_classes", names.size(), "next_offset", end,
-          "scope", "top_level", "offset", offset, "limit", limit,
-          "items", items));
+      int end = (int) Math.min((long) start + limit, names.size());
+      return json(Map.of("total", names.size(), "offset", offset, "limit", limit,
+          "items", names.subList(start, end)));
     }
     ClassSnapshot cls = selected(args);
     if (name.equals("get_class_summary")) return json(cls.summary());
@@ -365,7 +230,6 @@ class ReaJadxBridge {
       JadxSession.SmartCode code = methodBody(current, cls, overloads.get(index), method);
       return json(Map.of("class_name", cls.summary().get("full_name"),
           "method_name", overloads.get(index).name(), "full_name", method.getFullName(),
-          "dex_descriptor", overloads.get(index).summary().get("dex_descriptor"),
           "overload_index", index, "overload_count", overloads.size(),
           "mode", code.getKind(), "fell_back", code.getFellBack(),
           "markers", code.getMarkers(), "body", code.getText()));
@@ -377,7 +241,7 @@ class ReaJadxBridge {
     if (name.equals("get_xrefs_to_class")) uses = cls.node().getUseIn();
     else {
       List<MethodSnapshot> overloads = methods(cls, args);
-      if (overloads.size() != 1 && !args.has("overload_index"))
+      if (overloads.size() != 1 && !args.containsKey("overload_index"))
         throw new InputFailure("overload_index", "Select one of " + overloads.size() + " method overloads");
       overloadIndex = integer(args, "overload_index", 0);
       if (overloadIndex >= overloads.size())
@@ -423,12 +287,11 @@ class ReaJadxBridge {
   public static void main(String[] args) throws Exception {
     PrintStream protocolOut = System.out;
     System.setOut(System.err);
-    SessionConfig defaults = new SessionConfig(
-        1048576, 0, 90000L, 1, List.of(), List.of(), 64, ResourceMode.FULL);
-    SessionHolder holder = new SessionHolder(defaults);
+    SessionHolder holder = new SessionHolder(new SessionConfig(
+        1048576, 0, 90000L, 1, List.of(), List.of(), 64, ResourceMode.FULL));
     ServerCapabilities capabilities = new ServerCapabilities(
         new ServerCapabilities.Tools(null), null, null, null, null, null, null, Map.of());
-    Server server = new Server(new Implementation("rea-jadx-bridge", "4", null, null, null),
+    Server server = new Server(new Implementation("rea-jadx-bridge", "1", null, null, null),
         new ServerOptions(capabilities), "", ignored -> Unit.INSTANCE);
     SessionToolsKt.registerSessionTools(server, holder);
     ManifestToolsKt.registerManifestTools(server, holder);
@@ -436,17 +299,13 @@ class ReaJadxBridge {
     MethodToolsKt.registerMethodTools(server, holder);
     XrefToolsKt.registerXrefTools(server, holder);
     ReaJadxBridge bridge = new ReaJadxBridge(holder);
-    Tool loadTool = server.getTools().get("load_apk").getTool();
-    server.removeTool("load_apk");
-    server.addTool(loadTool, (connection, request, continuation) ->
-        bridge.load(request.getArguments(), defaults, continuation));
     Set<String> consumed = Set.of("load_apk", "get_app_info", "get_android_manifest",
         "list_classes", "get_class_summary", "get_method_body",
         "get_xrefs_to_class", "get_xrefs_to_method");
     for (String name : new ArrayList<>(server.getTools().keySet()))
       if (!consumed.contains(name)) server.removeTool(name);
     Tool diagnostics = new Tool("rea_jvm_status",
-        new ToolSchema(null, new kotlinx.serialization.json.JsonObject(Map.of()), List.of(), null),
+        new ToolSchema(null, new JsonObject(Map.of()), List.of(), null),
         "Observed worker JVM and metadata scope", null, null, null, null, null, null);
     server.addTool(diagnostics, (connection, request, continuation) -> bridge.handle("rea_jvm_status", request.getArguments()));
     for (String name : List.of("list_classes", "get_class_summary",
@@ -461,16 +320,13 @@ class ReaJadxBridge {
       };
       Map<String, kotlinx.serialization.json.JsonElement> properties = new LinkedHashMap<>();
       for (String field : fields) properties.put(field, tool.getInputSchema().getProperties().get(field));
-      if (name.equals("list_classes")) properties.put("query",
-          new kotlinx.serialization.json.JsonObject(Map.of(
-              "type", kotlinx.serialization.json.JsonElementKt.JsonPrimitive("string"))));
       String description = switch (name) {
-        case "list_classes" -> "Pages of case-sensitive matching top-level class names; offset and next_offset are inventory positions, limit bounds matching rows. Omitted or empty query inventories all names.";
+        case "list_classes" -> "Indexed pages of all top-level class names, with offset and limit.";
         case "get_class_summary" -> "Parsed member metadata for one exact class name; no source generation.";
         case "get_method_body" -> "Source for an exact class and stable same-name overload index; static initializers use smali to preserve folded field initialization.";
         default -> "Complete static using-node inventory for an exact class or selected method overload; one node may contain multiple invoke instructions, and source lines are unresolved.";
       };
-      Tool narrowed = new Tool(name, new ToolSchema(null, new kotlinx.serialization.json.JsonObject(properties),
+      Tool narrowed = new Tool(name, new ToolSchema(null, new JsonObject(properties),
           tool.getInputSchema().getRequired(), null), description, null, null, null, null, null, null);
       server.addTool(narrowed, (connection, request, continuation) -> {
         try { return bridge.handle(name, request.getArguments()); }

bridge/cutter/rea_bridge.py

@@ -1,825 +0,0 @@
-"""REA's experimental local bridge plugin for Cutter.
-
-Install this file in Cutter's user plugin directory. The bridge is REA-owned
-IPC, not an upstream Cutter transport. It binds to loopback and requires a
-per-process random token stored in a user-only descriptor file.
-"""
-
-from __future__ import annotations
-
-import json
-import hashlib
-import hmac
-import os
-import secrets
-import socket
-import stat
-import tempfile
-import threading
-import time
-import uuid
-from pathlib import Path
-from typing import Any
-
-if os.name == "nt":
-    import ctypes
-    from ctypes import wintypes
-
-import cutter
-
-try:
-    from PySide6.QtCore import QCoreApplication, QObject, Signal
-except ImportError:
-    from PySide2.QtCore import QCoreApplication, QObject, Signal
-
-
-MAX_FRAME_BYTES = 16 * 1024 * 1024
-SOCKET_TIMEOUT_SECONDS = 20
-AUTH_FRAME_TIMEOUT_SECONDS = 1
-MAX_DESCRIPTOR_BYTES = 64 * 1024
-MAX_COMPLETION_RECEIPTS = 64
-
-
-def _windows_api() -> tuple[Any, Any]:
-    kernel32 = ctypes.WinDLL("kernel32", use_last_error=True)
-    advapi32 = ctypes.WinDLL("advapi32", use_last_error=True)
-    kernel32.GetCurrentProcess.restype = wintypes.HANDLE
-    kernel32.LocalFree.argtypes = [wintypes.HLOCAL]
-    kernel32.LocalFree.restype = wintypes.HLOCAL
-    kernel32.CloseHandle.argtypes = [wintypes.HANDLE]
-    kernel32.CloseHandle.restype = wintypes.BOOL
-    kernel32.GetFileAttributesW.argtypes = [wintypes.LPCWSTR]
-    kernel32.GetFileAttributesW.restype = wintypes.DWORD
-    kernel32.CreateDirectoryW.argtypes = [wintypes.LPCWSTR, wintypes.LPVOID]
-    kernel32.CreateDirectoryW.restype = wintypes.BOOL
-    kernel32.CreateFileW.argtypes = [wintypes.LPCWSTR, wintypes.DWORD, wintypes.DWORD,
-                                     wintypes.LPVOID, wintypes.DWORD, wintypes.DWORD, wintypes.HANDLE]
-    kernel32.CreateFileW.restype = wintypes.HANDLE
-    kernel32.WriteFile.argtypes = [wintypes.HANDLE, wintypes.LPVOID, wintypes.DWORD,
-                                   ctypes.POINTER(wintypes.DWORD), wintypes.LPVOID]
-    kernel32.WriteFile.restype = wintypes.BOOL
-    kernel32.FlushFileBuffers.argtypes = [wintypes.HANDLE]
-    kernel32.FlushFileBuffers.restype = wintypes.BOOL
-    kernel32.MoveFileExW.argtypes = [wintypes.LPCWSTR, wintypes.LPCWSTR, wintypes.DWORD]
-    kernel32.MoveFileExW.restype = wintypes.BOOL
-    kernel32.DeleteFileW.argtypes = [wintypes.LPCWSTR]
-    kernel32.DeleteFileW.restype = wintypes.BOOL
-    advapi32.OpenProcessToken.argtypes = [wintypes.HANDLE, wintypes.DWORD, ctypes.POINTER(wintypes.HANDLE)]
-    advapi32.OpenProcessToken.restype = wintypes.BOOL
-    advapi32.GetTokenInformation.argtypes = [wintypes.HANDLE, ctypes.c_int, wintypes.LPVOID,
-                                              wintypes.DWORD, ctypes.POINTER(wintypes.DWORD)]
-    advapi32.GetTokenInformation.restype = wintypes.BOOL
-    advapi32.ConvertSidToStringSidW.argtypes = [wintypes.LPVOID, ctypes.POINTER(wintypes.LPWSTR)]
-    advapi32.ConvertSidToStringSidW.restype = wintypes.BOOL
-    advapi32.GetNamedSecurityInfoW.argtypes = [wintypes.LPWSTR, ctypes.c_int, wintypes.DWORD,
-                                                ctypes.POINTER(wintypes.LPVOID), ctypes.POINTER(wintypes.LPVOID),
-                                                ctypes.POINTER(wintypes.LPVOID), ctypes.POINTER(wintypes.LPVOID),
-                                                ctypes.POINTER(wintypes.LPVOID)]
-    advapi32.GetNamedSecurityInfoW.restype = wintypes.DWORD
-    advapi32.GetSecurityDescriptorControl.argtypes = [wintypes.LPVOID, ctypes.POINTER(wintypes.WORD),
-                                                       ctypes.POINTER(wintypes.DWORD)]
-    advapi32.GetSecurityDescriptorControl.restype = wintypes.BOOL
-    advapi32.EqualSid.argtypes = [wintypes.LPVOID, wintypes.LPVOID]
-    advapi32.EqualSid.restype = wintypes.BOOL
-    advapi32.GetAclInformation.argtypes = [wintypes.LPVOID, wintypes.LPVOID, wintypes.DWORD, ctypes.c_int]
-    advapi32.GetAclInformation.restype = wintypes.BOOL
-    advapi32.GetAce.argtypes = [wintypes.LPVOID, wintypes.DWORD, ctypes.POINTER(wintypes.LPVOID)]
-    advapi32.GetAce.restype = wintypes.BOOL
-    advapi32.IsValidSid.argtypes = [wintypes.LPVOID]
-    advapi32.IsValidSid.restype = wintypes.BOOL
-    advapi32.GetLengthSid.argtypes = [wintypes.LPVOID]
-    advapi32.GetLengthSid.restype = wintypes.DWORD
-    advapi32.ConvertStringSecurityDescriptorToSecurityDescriptorW.argtypes = [
-        wintypes.LPCWSTR, wintypes.DWORD, ctypes.POINTER(wintypes.LPVOID), ctypes.POINTER(wintypes.DWORD),
-    ]
-    advapi32.ConvertStringSecurityDescriptorToSecurityDescriptorW.restype = wintypes.BOOL
-    return kernel32, advapi32
-
-
-def _windows_user_sid_text() -> str:
-    kernel32, advapi32 = _windows_api()
-    token = wintypes.HANDLE()
-    if not advapi32.OpenProcessToken(kernel32.GetCurrentProcess(), 0x0008, ctypes.byref(token)):
-        raise ctypes.WinError(ctypes.get_last_error())
-    try:
-        required = wintypes.DWORD()
-        advapi32.GetTokenInformation(token, 1, None, 0, ctypes.byref(required))
-        if required.value == 0:
-            raise ctypes.WinError(ctypes.get_last_error())
-        buffer = ctypes.create_string_buffer(required.value)
-        if not advapi32.GetTokenInformation(token, 1, buffer, required, ctypes.byref(required)):
-            raise ctypes.WinError(ctypes.get_last_error())
-
-        class SID_AND_ATTRIBUTES(ctypes.Structure):
-            _fields_ = [("Sid", wintypes.LPVOID), ("Attributes", wintypes.DWORD)]
-
-        class TOKEN_USER(ctypes.Structure):
-            _fields_ = [("User", SID_AND_ATTRIBUTES)]
-
-        sid = ctypes.cast(buffer, ctypes.POINTER(TOKEN_USER)).contents.User.Sid
-        text = wintypes.LPWSTR()
-        if not advapi32.ConvertSidToStringSidW(sid, ctypes.byref(text)):
-            raise ctypes.WinError(ctypes.get_last_error())
-        try:
-            return text.value
-        finally:
-            kernel32.LocalFree(text)
-    finally:
-        kernel32.CloseHandle(token)
-
-
-def _verify_windows_private_path(path: Path, directory: bool) -> None:
-    kernel32, advapi32 = _windows_api()
-    attributes = kernel32.GetFileAttributesW(str(path))
-    if attributes == 0xFFFFFFFF:
-        raise ctypes.WinError(ctypes.get_last_error())
-    if attributes & 0x400 or bool(attributes & 0x10) != directory:
-        raise RuntimeError("Cutter bridge path is a reparse point or has the wrong object type")
-
-    class ACL_SIZE_INFORMATION(ctypes.Structure):
-        _fields_ = [("AceCount", wintypes.DWORD), ("AclBytesInUse", wintypes.DWORD), ("AclBytesFree", wintypes.DWORD)]
-
-    class ACE_HEADER(ctypes.Structure):
-        _fields_ = [("AceType", wintypes.BYTE), ("AceFlags", wintypes.BYTE), ("AceSize", wintypes.WORD)]
-
-    class SID_HEADER(ctypes.Structure):
-        _fields_ = [("Revision", wintypes.BYTE), ("SubAuthorityCount", wintypes.BYTE),
-                    ("IdentifierAuthority", wintypes.BYTE * 6)]
-
-    class ACCESS_ALLOWED_ACE(ctypes.Structure):
-        _fields_ = [("Header", ACE_HEADER), ("Mask", wintypes.DWORD), ("SidStart", wintypes.DWORD)]
-
-    owner = wintypes.LPVOID()
-    dacl = wintypes.LPVOID()
-    descriptor = wintypes.LPVOID()
-    result = advapi32.GetNamedSecurityInfoW(
-        str(path), 1, 0x1 | 0x4, ctypes.byref(owner), None, ctypes.byref(dacl), None, ctypes.byref(descriptor),
-    )
-    if result != 0:
-        raise ctypes.WinError(result)
-    try:
-        control = wintypes.WORD()
-        revision = wintypes.DWORD()
-        if not advapi32.GetSecurityDescriptorControl(descriptor, ctypes.byref(control), ctypes.byref(revision)):
-            raise ctypes.WinError(ctypes.get_last_error())
-        if not control.value & 0x1000 or not dacl:
-            raise RuntimeError("Cutter bridge ACL must be present and protected from inheritance")
-
-        token = wintypes.HANDLE()
-        if not advapi32.OpenProcessToken(kernel32.GetCurrentProcess(), 0x0008, ctypes.byref(token)):
-            raise ctypes.WinError(ctypes.get_last_error())
-        try:
-            required = wintypes.DWORD()
-            advapi32.GetTokenInformation(token, 1, None, 0, ctypes.byref(required))
-            token_user = ctypes.create_string_buffer(required.value)
-            if not advapi32.GetTokenInformation(token, 1, token_user, required, ctypes.byref(required)):
-                raise ctypes.WinError(ctypes.get_last_error())
-
-            class SID_AND_ATTRIBUTES(ctypes.Structure):
-                _fields_ = [("Sid", wintypes.LPVOID), ("Attributes", wintypes.DWORD)]
-
-            class TOKEN_USER(ctypes.Structure):
-                _fields_ = [("User", SID_AND_ATTRIBUTES)]
-
-            current_sid = ctypes.cast(token_user, ctypes.POINTER(TOKEN_USER)).contents.User.Sid
-            if not advapi32.EqualSid(owner, current_sid):
-                raise RuntimeError("Cutter bridge path owner does not match the current user")
-        finally:
-            kernel32.CloseHandle(token)
-
-        info = ACL_SIZE_INFORMATION()
-        if not advapi32.GetAclInformation(dacl, ctypes.byref(info), ctypes.sizeof(info), 2) or info.AceCount != 2:
-            raise RuntimeError("Cutter bridge ACL must allow only the current user and SYSTEM")
-        expected_user = _windows_user_sid_text()
-        user_allowed = False
-        system_allowed = False
-        for index in range(info.AceCount):
-            ace_pointer = wintypes.LPVOID()
-            if not advapi32.GetAce(dacl, index, ctypes.byref(ace_pointer)):
-                raise ctypes.WinError(ctypes.get_last_error())
-            header = ctypes.cast(ace_pointer, ctypes.POINTER(ACE_HEADER)).contents
-            if header.AceType != 0 or header.AceSize < ctypes.sizeof(ACE_HEADER) + ctypes.sizeof(wintypes.DWORD) + ctypes.sizeof(SID_HEADER):
-                raise RuntimeError("Cutter bridge ACL contains a malformed or unsupported ACE")
-            ace_address = ctypes.cast(ace_pointer, ctypes.c_void_p).value
-            if ace_address is None:
-                raise RuntimeError("Cutter bridge ACL returned a null ACE")
-            sid_pointer = ctypes.c_void_p(ace_address + ctypes.sizeof(ACE_HEADER) + ctypes.sizeof(wintypes.DWORD))
-            sid_header = ctypes.cast(sid_pointer, ctypes.POINTER(SID_HEADER)).contents
-            sid_size = ctypes.sizeof(SID_HEADER) + sid_header.SubAuthorityCount * ctypes.sizeof(wintypes.DWORD)
-            if sid_size > header.AceSize - ctypes.sizeof(ACE_HEADER) - ctypes.sizeof(wintypes.DWORD) or not advapi32.IsValidSid(sid_pointer) or advapi32.GetLengthSid(sid_pointer) != sid_size:
-                raise RuntimeError("Cutter bridge ACL contains an invalid SID")
-            ace = ctypes.cast(ace_pointer, ctypes.POINTER(ACCESS_ALLOWED_ACE)).contents
-            sid_text = wintypes.LPWSTR()
-            if ace.Mask != 0x001F01FF or ace.Header.AceFlags != 0x03:
-                raise RuntimeError("Cutter bridge ACL contains an unsupported ACE")
-            if not advapi32.ConvertSidToStringSidW(sid_pointer, ctypes.byref(sid_text)):
-                raise ctypes.WinError(ctypes.get_last_error())
-            try:
-                if sid_text.value == expected_user:
-                    user_allowed = True
-                elif sid_text.value == "S-1-5-18":
-                    system_allowed = True
-                else:
-                    raise RuntimeError("Cutter bridge ACL allows an unrelated principal")
-            finally:
-                kernel32.LocalFree(sid_text)
-        if not user_allowed or not system_allowed:
-            raise RuntimeError("Cutter bridge ACL must allow only the current user and SYSTEM")
-    finally:
-        kernel32.LocalFree(descriptor)
-
-
-def _windows_security_attributes() -> tuple[Any, Any]:
-    kernel32, advapi32 = _windows_api()
-    sid = _windows_user_sid_text()
-    sddl = f"O:{sid}G:{sid}D:P(A;OICI;FA;;;{sid})(A;OICI;FA;;;SY)"
-    descriptor = wintypes.LPVOID()
-    if not advapi32.ConvertStringSecurityDescriptorToSecurityDescriptorW(sddl, 1, ctypes.byref(descriptor), None):
-        raise ctypes.WinError(ctypes.get_last_error())
-
-    class SECURITY_ATTRIBUTES(ctypes.Structure):
-        _fields_ = [("nLength", wintypes.DWORD), ("lpSecurityDescriptor", wintypes.LPVOID), ("bInheritHandle", wintypes.BOOL)]
-
-    attributes = SECURITY_ATTRIBUTES(ctypes.sizeof(SECURITY_ATTRIBUTES), descriptor, False)
-    return kernel32, (descriptor, attributes)
-
-
-def _ensure_windows_bridge_directory(directory: Path) -> None:
-    directory.parent.mkdir(parents=True, exist_ok=True)
-    if not directory.exists():
-        kernel32, (descriptor, attributes) = _windows_security_attributes()
-        try:
-            if not kernel32.CreateDirectoryW(str(directory), ctypes.byref(attributes)):
-                error = ctypes.get_last_error()
-                if error != 183:
-                    raise ctypes.WinError(error)
-        finally:
-            kernel32.LocalFree(descriptor)
-    _verify_windows_private_path(directory, True)
-
-
-def _ensure_posix_bridge_directory(directory: Path) -> None:
-    directory.mkdir(mode=0o700, parents=True, exist_ok=True)
-    if not hasattr(os, "O_NOFOLLOW") or not hasattr(os, "O_DIRECTORY"):
-        raise RuntimeError("Cutter bridge directory requires no-follow directory handles")
-    descriptor = os.open(directory, os.O_RDONLY | os.O_DIRECTORY | os.O_NOFOLLOW)
-    try:
-        directory_info = os.fstat(descriptor)
-        if directory_info.st_uid != os.getuid():
-            raise RuntimeError("Cutter bridge directory must be owned by the current user")
-        os.fchmod(descriptor, 0o700)
-        directory_info = os.fstat(descriptor)
-        if stat.S_IMODE(directory_info.st_mode) != 0o700:
-            raise RuntimeError("Cutter bridge directory must have mode 0700")
-    finally:
-        os.close(descriptor)
-
-
-def _write_windows_descriptor(directory: Path, destination: Path, payload: bytes) -> None:
-    if len(payload) > MAX_DESCRIPTOR_BYTES:
-        raise RuntimeError("Cutter bridge descriptor exceeds its byte limit")
-    kernel32, (security_descriptor, attributes) = _windows_security_attributes()
-    temporary = directory / f".{destination.name}.{uuid.uuid4().hex}.tmp"
-    handle = wintypes.HANDLE()
-    try:
-        handle = kernel32.CreateFileW(str(temporary), 0x40000000 | 0x00020000 | 0x00040000,
-                                      0x1 | 0x2 | 0x4, ctypes.byref(attributes), 1, 0x80, None)
-        if handle == wintypes.HANDLE(-1).value:
-            raise ctypes.WinError(ctypes.get_last_error())
-        _verify_windows_private_path(temporary, False)
-        if payload:
-            data = ctypes.create_string_buffer(payload)
-            written = wintypes.DWORD()
-            if not kernel32.WriteFile(handle, data, len(payload), ctypes.byref(written), None) or written.value != len(payload):
-                raise ctypes.WinError(ctypes.get_last_error())
-        if not kernel32.FlushFileBuffers(handle):
-            raise ctypes.WinError(ctypes.get_last_error())
-        kernel32.CloseHandle(handle)
-        handle = wintypes.HANDLE()
-        if not kernel32.MoveFileExW(str(temporary), str(destination), 0x1 | 0x8):
-            raise ctypes.WinError(ctypes.get_last_error())
-    finally:
-        if handle and handle != wintypes.HANDLE(-1).value:
-            kernel32.CloseHandle(handle)
-        kernel32.DeleteFileW(str(temporary))
-        kernel32.LocalFree(security_descriptor)
-
-
-def _bridge_directory() -> Path:
-    configured = os.environ.get("REA_CUTTER_BRIDGE_DIR")
-    if configured:
-        return Path(configured).expanduser()
-    local_app_data = os.environ.get("LOCALAPPDATA")
-    if os.name == "nt" and local_app_data:
-        return Path(local_app_data) / "REA" / "CutterBridge"
-    return Path.home() / ".cache" / "rea" / "cutter-bridge"
-
-
-class _RequestDispatcher(QObject):
-    dispatch = Signal(object, object)
-
-    def __init__(self) -> None:
-        super().__init__()
-        self.dispatch.connect(self._handle)
-        self.generation = 0
-        self.completed_commands: dict[str, str] = {}
-        self._receipt_lock = threading.Lock()
-        self.current_file = self._read_current_file()
-        try:
-            value = QCoreApplication.applicationVersion()
-            self.cutter_version = value if isinstance(value, str) and value else None
-        except Exception:
-            self.cutter_version = None
-
-    @staticmethod
-    def _read_current_file() -> str | None:
-        try:
-            value = cutter.core().getConfig("file.path")
-            return value if isinstance(value, str) and value else None
-        except Exception:
-            return None
-
-    def _handle(self, request: dict[str, Any], reply: dict[str, Any]) -> None:
-        kind = request.get("kind")
-        request_id = request.get("request_id")
-        if kind in ("command", "ack"):
-            try:
-                valid_request_id = (
-                    isinstance(request_id, str)
-                    and str(uuid.UUID(request_id)) == request_id.lower()
-                )
-            except (ValueError, AttributeError):
-                valid_request_id = False
-            if not valid_request_id:
-                reply.update({
-                    "ok": False,
-                    "error": "invalid-command-request-id",
-                    "execution_state": "not_started",
-                })
-                request["_event"].set()
-                return
-        if kind == "ack":
-            with self._receipt_lock:
-                acknowledged = self.completed_commands.pop(request_id, None) is not None
-            reply.update({"ok": True, "acknowledged": acknowledged})
-            request["_event"].set()
-            return
-        if request["_cancelled"].is_set():
-            reply.update({
-                "ok": False,
-                "error": "request-cancelled-before-execution",
-                "execution_state": "not_started",
-            })
-            if kind == "command":
-                self._record_command_completion(request_id, "not_started")
-            request["_event"].set()
-            return
-        self._refresh_document_identity()
-        if kind == "status":
-            with self._receipt_lock:
-                completed_commands = [
-                    {"request_id": receipt_id, "execution_state": state}
-                    for receipt_id, state in self.completed_commands.items()
-                ]
-            reply.update({
-                "ok": True,
-                "session_id": request.get("session_id"),
-                "current_file": self.current_file,
-                "document_generation": self.generation,
-                "cutter_version": self.cutter_version,
-                "identity_status": "partial",
-                "completed_commands": completed_commands,
-            })
-            request["_event"].set()
-            return
-        if kind != "command":
-            reply.update({"ok": False, "error": "unsupported-request-kind"})
-            request["_event"].set()
-            return
-        if request.get("expected_generation") != self.generation:
-            reply.update({
-                "ok": False,
-                "error": "active-document-generation-changed",
-                "execution_state": "not_started",
-            })
-            self._record_command_completion(request_id, "not_started")
-            request["_event"].set()
-            return
-        command = request.get("command")
-        if not isinstance(command, str) or not command.strip():
-            reply.update({
-                "ok": False,
-                "error": "invalid-command",
-                "execution_state": "not_started",
-            })
-            self._record_command_completion(request_id, "not_started")
-            request["_event"].set()
-            return
-        reply["execution_state"] = "running"
-        try:
-            output = cutter.cmdj(command) if request.get("json") is True else cutter.cmd(command)
-            command_error = None
-        except Exception as error:
-            output = None
-            command_error = str(error)
-        self._refresh_document_identity()
-        if command_error is None:
-            reply.update({
-                "ok": True,
-                "output": output,
-                "current_file": self.current_file,
-                "document_generation": self.generation,
-                "cutter_version": self.cutter_version,
-                "identity_status": "partial",
-                "execution_state": "complete",
-            })
-            self._record_command_completion(request_id, "complete")
-        else:
-            reply.update({
-                "ok": False,
-                "error": command_error,
-                "current_file": self.current_file,
-                "document_generation": self.generation,
-                "cutter_version": self.cutter_version,
-                "identity_status": "partial",
-                "execution_state": "unknown",
-                "message": "The command raised an exception; it may have produced partial effects. Do not retry automatically.",
-            })
-            self._record_command_completion(request_id, "failed")
-        request["_event"].set()
-
-    def _record_command_completion(
-        self, request_id: str, execution_state: str
-    ) -> None:
-        with self._receipt_lock:
-            if request_id in self.completed_commands or len(self.completed_commands) < MAX_COMPLETION_RECEIPTS:
-                self.completed_commands[request_id] = execution_state
-
-    def can_accept_command(self) -> bool:
-        with self._receipt_lock:
-            return len(self.completed_commands) < MAX_COMPLETION_RECEIPTS
-
-    def _refresh_document_identity(self) -> None:
-        current_file = self._read_current_file()
-        if current_file != self.current_file:
-            self.current_file = current_file
-            self.generation += 1
-
-
-class _BridgeServer(threading.Thread):
-    def __init__(self, dispatcher: _RequestDispatcher) -> None:
-        super().__init__(name="rea-cutter-bridge", daemon=True)
-        self.dispatcher = dispatcher
-        self.server = socket.socket(socket.AF_INET, socket.SOCK_STREAM)
-        self.server.setsockopt(socket.SOL_SOCKET, socket.SO_REUSEADDR, 1)
-        self.server.bind(("127.0.0.1", 0))
-        self.server.listen(8)
-        self.server.settimeout(0.5)
-        self.port = self.server.getsockname()[1]
-        self.session_id = str(uuid.uuid4())
-        self.token = secrets.token_urlsafe(32)
-        self.poisoned = False
-        self.connection_ordinal = 0
-        self.directory = _bridge_directory()
-        self.descriptor = self.directory / f"cutter-{os.getpid()}-{self.session_id}.json"
-
-    def publish(self) -> None:
-        if os.name == "nt":
-            _ensure_windows_bridge_directory(self.directory)
-        else:
-            _ensure_posix_bridge_directory(self.directory)
-        if os.name == "nt" and (self.directory.is_symlink() or not self.directory.is_dir()):
-            raise RuntimeError("Cutter bridge directory must be a real directory")
-        payload = {
-            "session_id": self.session_id,
-            "pid": os.getpid(),
-            "host": "127.0.0.1",
-            "port": self.port,
-            "token": self.token,
-            "document_generation": self.dispatcher.generation,
-            "current_file": self.dispatcher.current_file,
-            "cutter_version": self.dispatcher.cutter_version,
-            "identity_status": "partial",
-        }
-        if os.name == "nt":
-            _write_windows_descriptor(self.directory, self.descriptor, json.dumps(payload).encode("utf-8"))
-            return
-        descriptor, temporary_path = tempfile.mkstemp(prefix=f".{self.descriptor.name}.", dir=self.directory)
-        try:
-            os.fchmod(descriptor, 0o600)
-            descriptor_info = os.fstat(descriptor)
-            if descriptor_info.st_uid != os.getuid() or stat.S_IMODE(descriptor_info.st_mode) & 0o077:
-                raise RuntimeError("Cutter bridge descriptor must be owned by the current user with mode 0600")
-            with os.fdopen(descriptor, "w", encoding="utf-8") as stream:
-                stream.write(json.dumps(payload))
-                stream.flush()
-                os.fsync(stream.fileno())
-            os.replace(temporary_path, self.descriptor)
-        except Exception:
-            try:
-                os.close(descriptor)
-            except OSError:
-                pass
-            try:
-                os.unlink(temporary_path)
-            except OSError:
-                pass
-            raise
-
-    def run(self) -> None:
-        try:
-            self.publish()
-        except Exception:
-            self.server.close()
-            return
-        while True:
-            try:
-                connection, _ = self.server.accept()
-            except socket.timeout:
-                if getattr(self, "stopping", False):
-                    break
-                continue
-            except OSError:
-                break
-            self.connection_ordinal += 1
-            connection_ordinal = self.connection_ordinal
-            with connection:
-                connection.settimeout(AUTH_FRAME_TIMEOUT_SECONDS)
-                authenticated = False
-                try:
-                    hello = self._receive_frame(connection)
-                    if not isinstance(hello, dict) or hello.get("kind") != "rea-auth-v2" or not isinstance(hello.get("nonce"), str) or len(hello["nonce"]) != 64:
-                        self._send(connection, {"ok": False, "error": "authentication-failed"})
-                        continue
-                    client_nonce = hello["nonce"]
-                    server_nonce = f"{connection_ordinal:016x}{secrets.token_hex(24)}"
-                    server_proof = hmac.new(self.token.encode(), f"rea-cutter-server-v2:{self.session_id}:{client_nonce}:{server_nonce}".encode(), hashlib.sha256).hexdigest()
-                    self._send(connection, {"session_id": self.session_id, "nonce": server_nonce, "proof": server_proof})
-                    authenticated_frame = self._receive_frame(connection)
-                    request_bytes = authenticated_frame.get("request") if isinstance(authenticated_frame, dict) else None
-                    expected_proof = hmac.new(self.token.encode(), f"rea-cutter-client-v2:{self.session_id}:{client_nonce}:{server_nonce}:{request_bytes}".encode(), hashlib.sha256).hexdigest()
-                    if not isinstance(request_bytes, str) or not isinstance(authenticated_frame.get("proof"), str) or not hmac.compare_digest(authenticated_frame["proof"], expected_proof):
-                        self._send(connection, {"ok": False, "error": "authentication-failed"})
-                        continue
-                    request = json.loads(request_bytes)
-                    if not isinstance(request, dict) or request.get("session_id") != self.session_id:
-                        self._send(connection, {"ok": False, "error": "authentication-failed"})
-                        continue
-                    authenticated = True
-                    connection.settimeout(SOCKET_TIMEOUT_SECONDS)
-                    if self.poisoned and request.get("kind") not in ("status", "ack"):
-                        self._send_authenticated(connection, {
-                            "ok": False,
-                            "error": "session-poisoned-after-ui-timeout",
-                            "execution_state": "not_started",
-                        }, client_nonce, server_nonce)
-                        continue
-                    if (
-                        request.get("kind") == "command"
-                        and not self.dispatcher.can_accept_command()
-                    ):
-                        self._send_authenticated(connection, {
-                            "ok": False,
-                            "error": "completion-receipt-capacity-exceeded",
-                            "execution_state": "not_started",
-                        }, client_nonce, server_nonce)
-                        continue
-                    request["session_id"] = self.session_id
-                    event = threading.Event()
-                    cancelled = threading.Event()
-                    reply: dict[str, Any] = {}
-                    request["_event"] = event
-                    request["_cancelled"] = cancelled
-                    self.dispatcher.dispatch.emit(request, reply)
-                    if not event.wait(SOCKET_TIMEOUT_SECONDS):
-                        cancelled.set()
-                        self.poisoned = True
-                        self._send_authenticated(connection, {
-                            "ok": False,
-                            "error": "ui-thread-request-timeout",
-                            "execution_state": "unknown",
-                            "message": "The UI operation may still complete after this timeout; restart Cutter before issuing further commands.",
-                        }, client_nonce, server_nonce)
-                    else:
-                        if request.get("kind") == "status" and reply.get("ok") is True:
-                            reply["completed_connection"] = f"{connection_ordinal - 1:016x}"
-                        self._send_authenticated(connection, reply, client_nonce, server_nonce)
-                except socket.timeout:
-                    if authenticated:
-                        self._send_authenticated(connection, {
-                            "ok": False,
-                            "error": "request-timeout",
-                            "execution_state": "unknown",
-                            "message": "The command may have produced partial or persistent effects. Do not retry automatically.",
-                        }, client_nonce, server_nonce)
-                except Exception as error:
-                    self._send(connection, {"ok": False, "error": str(error)})
-        self.server.close()
-        try:
-            self.descriptor.unlink(missing_ok=True)
-        except OSError:
-            pass
-
-    @staticmethod
-    def _receive_frame(connection: socket.socket) -> dict[str, Any]:
-        data = bytearray()
-        deadline = time.monotonic() + AUTH_FRAME_TIMEOUT_SECONDS
-        while b"\n" not in data:
-            if len(data) >= MAX_FRAME_BYTES:
-                raise ValueError("frame-limit-exceeded")
-            remaining = deadline - time.monotonic()
-            if remaining <= 0:
-                raise socket.timeout("authentication frame timed out")
-            connection.settimeout(remaining)
-            part = connection.recv(min(65536, MAX_FRAME_BYTES + 1 - len(data)))
-            if not part:
-                raise ValueError("incomplete authentication frame")
-            data.extend(part)
-        line, remainder = bytes(data).split(b"\n", 1)
-        if len(line) > MAX_FRAME_BYTES or remainder:
-            raise ValueError("invalid framed request")
-        value = json.loads(line)
-        return value if isinstance(value, dict) else {}
-
-    def _send_authenticated(self, connection: socket.socket, value: dict[str, Any], client_nonce: str, server_nonce: str) -> None:
-        encoded = self._encode_authenticated_response(value, client_nonce, server_nonce)
-        if encoded is None:
-            value = self._truncated_response(value)
-            encoded = self._encode_authenticated_response(value, client_nonce, server_nonce)
-        if encoded is None:
-            # This fixed-size fallback is checked through the same signed framing path.
-            value = {
-                "ok": False,
-                "error": "response-limit-exceeded",
-                "execution_state": value.get("execution_state", "unknown"),
-                "output": None,
-                "output_truncated": True,
-                "message": "The result exceeded the bridge frame limit; command completion state is preserved.",
-            }
-            encoded = self._encode_authenticated_response(value, client_nonce, server_nonce)
-        if encoded is None:
-            return
-        try:
-            connection.sendall(encoded)
-        except OSError:
-            pass
-
-    def _encode_authenticated_response(self, value: dict[str, Any], client_nonce: str, server_nonce: str) -> bytes | None:
-        if not _within_response_limit(value):
-            return None
-        prefix = b'{"response":"'
-        suffix = b'","proof":"' + (b"0" * 64) + b'"}\n'
-        frame_size = len(prefix) + len(suffix)
-        response_parts: list[bytes] = []
-        escaped_parts: list[bytes] = []
-        for fragment in json.JSONEncoder(ensure_ascii=False, separators=(",", ":")).iterencode(value):
-            raw = fragment.encode("utf-8")
-            escaped = json.dumps(fragment, ensure_ascii=False)[1:-1].encode("utf-8")
-            frame_size += len(escaped)
-            if frame_size > MAX_FRAME_BYTES:
-                return None
-            response_parts.append(raw)
-            escaped_parts.append(escaped)
-        proof = hmac.new(self.token.encode(), digestmod=hashlib.sha256)
-        proof.update(f"rea-cutter-response-v2:{self.session_id}:{client_nonce}:{server_nonce}:".encode())
-        for part in response_parts:
-            proof.update(part)
-        return prefix + b"".join(escaped_parts) + b'","proof":"' + proof.hexdigest().encode() + b'"}\n'
-
-    @staticmethod
-    def _truncated_response(value: dict[str, Any]) -> dict[str, Any]:
-        response: dict[str, Any] = {
-            "ok": value.get("ok") is True,
-            "output": None,
-            "execution_state": value.get("execution_state", "unknown"),
-            "output_truncated": True,
-            "message": "The command result exceeded the bridge frame limit; completion state is preserved and output was omitted.",
-        }
-        for key in ("current_file", "document_generation", "cutter_version", "identity_status"):
-            if key in value:
-                response[key] = value[key]
-        if value.get("ok") is not True and isinstance(value.get("error"), str):
-            response["error"] = value["error"]
-        return response
-
-    @staticmethod
-    def _send(connection: socket.socket, value: dict[str, Any]) -> None:
-        if not _within_response_limit(value):
-            value = {
-                "ok": False,
-                "error": "response-limit-exceeded",
-                "execution_state": value.get("execution_state", "unknown"),
-                "output_truncated": True,
-                "message": "The command completed or may have completed, but its result exceeded the bridge response limit. Do not retry automatically.",
-            }
-        parts: list[bytes] = []
-        encoded_size = 0
-        for part in json.JSONEncoder(ensure_ascii=False).iterencode(value):
-            encoded_part = part.encode("utf-8")
-            encoded_size += len(encoded_part)
-            if encoded_size > MAX_FRAME_BYTES:
-                fallback = {
-                    "ok": False,
-                    "error": "response-limit-exceeded",
-                    "execution_state": value.get("execution_state", "unknown"),
-                    "output_truncated": True,
-                    "message": "The command completed or may have completed, but its result exceeded the bridge response limit. Do not retry automatically.",
-                }
-                parts = [json.dumps(fallback, separators=(",", ":")).encode("utf-8")]
-                break
-            parts.append(encoded_part)
-        encoded = b"".join(parts)
-        try:
-            connection.sendall(encoded + b"\n")
-        except OSError:
-            # A disconnected caller must not terminate the bridge thread or
-            # prevent later commands from being served.
-            pass
-
-    def stop(self) -> None:
-        self.stopping = True
-        try:
-            self.server.close()
-        except OSError:
-            pass
-
-
-class ReaCutterPlugin(cutter.CutterPlugin):
-    name = "REA Local Bridge"
-    description = "Local REA analysis bridge for the active Cutter session"
-    version = "1.0"
-    author = "REA"
-
-    def __init__(self) -> None:
-        super().__init__()
-        self._dispatcher: _RequestDispatcher | None = None
-        self._bridge: _BridgeServer | None = None
-
-    def setupPlugin(self) -> None:
-        return
-
-    def setupInterface(self, main: Any) -> None:
-        self._dispatcher = _RequestDispatcher()
-        self._bridge = _BridgeServer(self._dispatcher)
-        self._bridge.start()
-
-    def terminate(self) -> None:
-        if self._bridge is not None:
-            self._bridge.stop()
-            self._bridge.join(timeout=2)
-            self._bridge = None
-        self._dispatcher = None
-
-
-def create_cutter_plugin() -> ReaCutterPlugin:
-    return ReaCutterPlugin()
-
-
-def _within_response_limit(value: Any) -> bool:
-    pending = [value]
-    seen: set[int] = set()
-    size = 0
-    while pending:
-        current = pending.pop()
-        if isinstance(current, str):
-            size += 2
-            if len(current) > MAX_FRAME_BYTES - size:
-                return False
-            if current.isascii():
-                size += len(current)
-            else:
-                # Count UTF-8 bytes without allocating a copy of the whole output.
-                try:
-                    size += sum(
-                        len(current[start:start + 65536].encode("utf-8"))
-                        for start in range(0, len(current), 65536)
-                    )
-                except UnicodeEncodeError:
-                    # Unencodable output also needs the signed omission fallback.
-                    return False
-            size += current.count('"') + current.count("\\")
-            size += sum(5 for character in current if ord(character) < 0x20)
-        elif isinstance(current, dict):
-            identity = id(current)
-            if identity in seen:
-                return False
-            seen.add(identity)
-            size += 2 + 4 * len(current)
-            if size > MAX_FRAME_BYTES:
-                return False
-            pending.extend(current.keys())
-            pending.extend(current.values())
-        elif isinstance(current, (list, tuple)):
-            identity = id(current)
-            if identity in seen:
-                return False
-            seen.add(identity)
-            size += 2 + 2 * len(current)
-            if size > MAX_FRAME_BYTES:
-                return False
-            pending.extend(current)
-        else:
-            size += 16
-        if size > MAX_FRAME_BYTES:
-            return False
-    return True

bridge/ghidra/ReaGhidraBridge.java

@@ -5,11 +5,9 @@ import java.io.BufferedReader;
 import java.io.BufferedWriter;
 import java.io.ByteArrayOutputStream;
 import java.io.IOException;
-import java.io.InputStream;
 import java.math.BigInteger;
 import java.net.InetAddress;
 import java.net.InetSocketAddress;
-import java.net.SocketTimeoutException;
 import java.net.StandardProtocolFamily;
 import java.net.UnixDomainSocketAddress;
 import java.nio.channels.Channels;
@@ -83,7 +81,6 @@ import ghidra.program.model.listing.Function;
 import ghidra.program.model.listing.FunctionIterator;
 import ghidra.program.model.listing.Instruction;
 import ghidra.program.model.listing.InstructionIterator;
-import ghidra.program.model.listing.Listing;
 import ghidra.program.model.listing.Variable;
 import ghidra.program.model.mem.MemoryBlock;
 import ghidra.program.model.mem.MemoryBlockSourceInfo;
@@ -140,7 +137,6 @@ public final class ReaGhidraBridge extends HeadlessScript {
         "params"
     );
     private static final String[] CAPABILITIES = {
-        "read_binary_inventory_summary",
         "annotate_native_function",
         "set_address_name",
         "set_addresses_names",
@@ -301,7 +297,7 @@ public final class ReaGhidraBridge extends HeadlessScript {
                     Files.move(pendingPath, endpointPath);
                 }
             }
-            acceptAuthenticatedLoopbackClient(server, descriptor);
+            acceptClient(server, descriptor);
         }
         finally {
             Files.deleteIfExists(pendingPath);
@@ -313,50 +309,6 @@ public final class ReaGhidraBridge extends HeadlessScript {
         return System.getProperty("os.name", "").startsWith("Windows");
     }
 
-    private static String readLoopbackHandshake(
-            SocketChannel client, int maxBytes, long timeoutMillis) throws IOException {
-        long deadline = System.nanoTime() + timeoutMillis * 1_000_000L;
-        InputStream input = client.socket().getInputStream();
-        ByteArrayOutputStream bytes = new ByteArrayOutputStream();
-        while (true) {
-            long remaining = deadline - System.nanoTime();
-            if (remaining <= 0) throw new SocketTimeoutException("Bridge authentication timed out");
-            client.socket().setSoTimeout((int) Math.max(1,
-                Math.min(Integer.MAX_VALUE, (remaining + 999_999L) / 1_000_000L)));
-            int value = input.read();
-            if (value == -1) return null;
-            if (value == '\n') return bytes.toString(StandardCharsets.UTF_8);
-            if (bytes.size() == maxBytes) throw new IOException("Bridge authentication frame is too large");
-            bytes.write(value);
-        }
-    }
-
-    private void acceptAuthenticatedLoopbackClient(
-            ServerSocketChannel server, SessionDescriptor descriptor) throws Exception {
-        while (true) {
-            try (SocketChannel client = server.accept()) {
-                Request first;
-                try {
-                    String line = readLoopbackHandshake(client, 64 * 1024, 1_000);
-                    if (line == null) continue;
-                    first = parseRequest(line, descriptor.token);
-                }
-                catch (IOException | RuntimeException rejected) {
-                    // A rejected unauthenticated peer cannot consume the bridge session.
-                    continue;
-                }
-                client.socket().setSoTimeout(0);
-                try (BufferedReader reader = new BufferedReader(
-                         Channels.newReader(client, StandardCharsets.UTF_8));
-                     BufferedWriter writer = new BufferedWriter(
-                         Channels.newWriter(client, StandardCharsets.UTF_8))) {
-                    serveClient(descriptor, reader, writer, first);
-                }
-                return;
-            }
-        }
-    }
-
     private void acceptClient(
             ServerSocketChannel server,
             SessionDescriptor descriptor) throws Exception {
@@ -367,28 +319,26 @@ public final class ReaGhidraBridge extends HeadlessScript {
              BufferedWriter writer = new BufferedWriter(
                  Channels.newWriter(client, StandardCharsets.UTF_8)
              )) {
-            serveClient(descriptor, reader, writer, null);
+            serveClient(descriptor, reader, writer);
         }
     }
 
     private void serveClient(
             SessionDescriptor descriptor,
             BufferedReader reader,
-            BufferedWriter writer,
-            Request first) throws Exception {
+            BufferedWriter writer) throws Exception {
         while (true) {
-            Request request = first;
-            first = null;
-            if (request == null) {
-                String line = reader.readLine();
-                if (line == null) return;
-                try {
-                    request = parseRequest(line, descriptor.token);
-                }
-                catch (RuntimeException exception) {
-                    writeFailure(writer, 1, "invalid_request", "Bridge request is invalid");
-                    return;
-                }
+            String line = reader.readLine();
+            if (line == null) {
+                return;
+            }
+            Request request;
+            try {
+                request = parseRequest(line, descriptor.token);
+            }
+            catch (RuntimeException exception) {
+                writeFailure(writer, 1, "invalid_request", "Bridge request is invalid");
+                return;
             }
             try {
                 if (request.method.equals("shutdown")) {
@@ -428,7 +378,6 @@ public final class ReaGhidraBridge extends HeadlessScript {
             );
         }
         return switch (request.method) {
-            case "read_binary_inventory_summary" -> binaryInventorySummary(request.params);
             case "inspect_native_load_image" -> inspectNativeLoadImage(request.params);
             case "read_bytes" -> readMemoryBytes(request.params);
             case "search_bytes" -> searchMemoryBytes(request.params, descriptor);
@@ -456,10 +405,7 @@ public final class ReaGhidraBridge extends HeadlessScript {
             case "xrefs" -> xrefs(request.params);
             case "analyze_function" -> {
                 FunctionAnalysisObservation observation = analyzeFunctionObservation(request.params);
-                JsonObject result = functionObservation(observation.dossier(), observation.limitations());
-                result.add("relationship_coverage", observation.relationshipCoverage());
-                if (observation.decompilerFailed()) result.addProperty("cache_policy", "live");
-                yield result;
+                yield functionObservation(observation.dossier(), observation.limitations());
             }
             case "set_address_name", "set_addresses_names" -> {
                 if (!descriptor.transport.equals("unix-socket"))
@@ -937,8 +883,7 @@ public final class ReaGhidraBridge extends HeadlessScript {
             String value = decompiledText(decompile(function));
             JsonObject result = functionObservation(
                 value == null ? JsonNull.INSTANCE : GSON.toJsonTree(value),
-                functionBoundaryLimitations(
-                    function,
+                noReturnCallLimitations(
                     currentProgram.getListing().getInstructions(function.getBody(), true)
                 )
             );
@@ -1030,7 +975,7 @@ public final class ReaGhidraBridge extends HeadlessScript {
         InstructionScan scan = scanInstructions(function, Integer.MAX_VALUE);
         return functionObservation(
             GSON.toJsonTree(renderAssembly(scan.instructions)),
-            functionBoundaryLimitations(function, scan.instructions)
+            noReturnCallLimitations(scan.instructions)
         );
     }
 
@@ -1049,7 +994,7 @@ public final class ReaGhidraBridge extends HeadlessScript {
         limitations.add(
             "The fast path does not invoke the decompiler or scan whole-program names and strings."
         );
-        List<String> boundaryLimitations = functionBoundaryLimitations(function, scan.instructions);
+        List<String> boundaryLimitations = noReturnCallLimitations(scan.instructions);
         for (String limitation : boundaryLimitations) limitations.add(limitation);
         JsonObject result = new JsonObject();
         result.add("procedure", procedureIdentity(function));
@@ -1071,19 +1016,12 @@ public final class ReaGhidraBridge extends HeadlessScript {
         for (Function item : ordered) {
             result.add(canonicalAddress(item.getEntryPoint()));
         }
-        if (callers) {
-            JsonObject observation = functionObservation(result, functionBoundaryLimitations(function,
+        return functionObservation(
+            result,
+            noReturnCallLimitations(
                 currentProgram.getListing().getInstructions(function.getBody(), true)
-            ));
-            observation.add("relationship_coverage", callRelationshipCoverage(null,
-                unrepresentedIncomingCalls(function, observed)));
-            monitor.checkCancelled();
-            return observation;
-        }
-        CallBoundaryObservation calls = callBoundaryObservation(
-            function, currentProgram.getListing().getInstructions(function.getBody(), true), observed, false, null
+            )
         );
-        return callRelationshipObservation(result, calls);
     }
 
     private JsonObject procedureInfo(JsonObject params) throws Exception {
@@ -1102,8 +1040,7 @@ public final class ReaGhidraBridge extends HeadlessScript {
         result.add("classification", functionClassification(function));
         return functionObservation(
             result,
-            functionBoundaryLimitations(
-                function,
+            noReturnCallLimitations(
                 currentProgram.getListing().getInstructions(function.getBody(), true)
             )
         );
@@ -1134,22 +1071,20 @@ public final class ReaGhidraBridge extends HeadlessScript {
         result.addProperty("direction", direction);
         result.add("references", edges);
         result.addProperty("reference_kinds_available", true);
-        List<String> limitations;
         JsonArray unresolvedCalls = new JsonArray();
-        if (direction.equals("outgoing")) {
-            CallBoundaryObservation calls = callBoundaryObservation(
-                function, currentProgram.getListing().getInstructions(function.getBody(), true), null, true, references
-            );
-            unresolvedCalls = calls.unresolvedCalls();
-            limitations = calls.limitations();
-        } else {
-            limitations = functionBoundaryLimitations(
-                function,
-                currentProgram.getListing().getInstructions(function.getBody(), true)
-            );
+        if (direction.equals("outgoing")) for (Instruction instruction : scanInstructions(function, Integer.MAX_VALUE).instructions) {
+            if (!instruction.getFlowType().isCall()) continue;
+            boolean resolved = false;
+            for (Reference reference : instruction.getReferencesFrom()) if (reference.getReferenceType().isCall()) resolved = true;
+            if (!resolved) {
+                JsonObject site = new JsonObject();
+                site.addProperty("address", canonicalAddress(instruction.getAddress()));
+                site.addProperty("reason", "Instruction decoder identifies a call but ReferenceManager supplies no call destination");
+                unresolvedCalls.add(site);
+            }
         }
         result.add("unresolved_calls", unresolvedCalls);
-        return functionObservation(result, limitations);
+        return result;
     }
 
     private JsonObject inspectNativeDataType(JsonObject params) throws Exception {
@@ -1350,7 +1285,11 @@ public final class ReaGhidraBridge extends HeadlessScript {
         result.add("references", references);
         if (includeIncoming) {
             TreeMap<String, Reference> incoming = new TreeMap<>();
-            visitObservedReferencesTo(address, reference -> addReference(incoming, reference));
+            ReferenceIterator incomingIterator = currentProgram.getReferenceManager().getReferencesTo(address);
+            while (incomingIterator.hasNext()) {
+                monitor.checkCancelled();
+                addReference(incoming, incomingIterator.next());
+            }
             List<Reference> orderedIncoming = new ArrayList<>(incoming.values());
             orderedIncoming.sort(REFERENCE_ORDER);
             JsonArray incomingReferences = new JsonArray();
@@ -1402,8 +1341,16 @@ public final class ReaGhidraBridge extends HeadlessScript {
         requireKeys(params, Set.of("document", "address"));
         requireDocument(params);
         Address address = requireAddress(params, "address");
+        ReferenceIterator references = currentProgram.getReferenceManager().getReferencesTo(address);
         Set<Address> sources = new HashSet<>();
-        visitObservedReferencesTo(address, reference -> sources.add(reference.getFromAddress()));
+        while (references.hasNext()) {
+            monitor.checkCancelled();
+            Reference reference = references.next();
+            if (reference.isEntryPointReference()) {
+                continue;
+            }
+            sources.add(reference.getFromAddress());
+            }
         List<Address> ordered = new ArrayList<>(sources);
         ordered.sort(Address::compareTo);
         JsonArray result = new JsonArray();
@@ -1541,41 +1488,21 @@ public final class ReaGhidraBridge extends HeadlessScript {
         requireKeys(params, Set.of("procedure"));
         Function function = resolveProcedure(requireString(params, "procedure"));
         InstructionScan scan = scanInstructions(function, Integer.MAX_VALUE);
-        DecompileResults decompilation;
-        String decompilerFailure = null;
-        try {
-            decompilation = decompile(function);
-        } catch (RequestFailure failure) {
-            // The listing, reference and CFG facts below do not depend on the
-            // native decompiler. Cancellation still ends the request.
-            if (!failure.code.equals("decompile_failed")) throw failure;
-            decompilation = null;
-            decompilerFailure = failure.getMessage().strip();
-        }
+        DecompileResults decompilation = decompile(function);
         String pseudocode = decompiledText(decompilation);
-        JsonObject availability = new JsonObject();
-        availability.add("pseudocode", facetAvailability(
-            pseudocode != null,
-            decompilerFailure != null ? decompilerFailure
-                : function.isExternal() ? "Ghidra does not decompile external functions."
-                : function.getBody().isEmpty() ? "Ghidra has no function body to decompile."
-                : "Ghidra completed decompilation without returning pseudocode."
-        ));
         if (pseudocode == null) {
             pseudocode = "";
         }
-        List<Reference> bodyIncoming = collectReferences(function, "incoming");
-        List<Reference> incomingReferences = bodyIncoming.stream()
+        List<Reference> incomingReferences = collectReferences(function, "incoming")
+            .stream()
             .filter(reference -> !function.getBody().contains(reference.getFromAddress()))
             .toList();
         List<Reference> outgoingReferences = collectReferences(function, "outgoing");
         JsonArray incoming = referenceEdges(incomingReferences);
         JsonArray outgoing = referenceEdges(outgoingReferences);
-        JsonArray comments = comments(function);
-        Set<Function> callerFunctions = function.getCallingFunctions(monitor);
-        JsonArray callers = procedureIdentities(callerFunctions);
-        Set<Function> calleeFunctions = function.getCalledFunctions(monitor);
-        JsonArray callees = procedureIdentities(calleeFunctions);
+        JsonArray comments = comments(scan.instructions);
+        JsonArray callers = procedureIdentities(function.getCallingFunctions(monitor));
+        JsonArray callees = procedureIdentities(function.getCalledFunctions(monitor));
         JsonArray referencedStrings = referencedStrings(outgoingReferences);
         JsonArray referencedNames = referencedNames(outgoingReferences);
         JsonArray blocks = basicBlockValues(function);
@@ -1606,25 +1533,9 @@ public final class ReaGhidraBridge extends HeadlessScript {
         result.add("basic_blocks", blocks);
         result.add(
             "native_api",
-            decompilerFailure == null
-                ? nativeApiBoundary(function, decompilation)
-                : unavailableNativeApiBoundary(decompilerFailure)
+            nativeApiBoundary(function, decompilation)
         );
-        result.add(
-            "native_value_flow",
-            decompilerFailure == null
-                ? nativeValueFlow(decompilation)
-                : unavailableNativeValueFlow(decompilerFailure)
-        );
-        // Successful full queries distinguish collected empty sets from missing facts.
-        // Availability does not claim that Ghidra resolved every runtime relationship.
-        for (String facet : List.of("comments", "callers", "callees", "references", "strings_names", "cfg")) {
-            availability.add(facet, facetAvailability(true, null));
-        }
-        availability.add("assembly", facetAvailability(
-            !scan.truncated(), "The function instruction scan was truncated."
-        ));
-        result.add("facet_availability", availability);
+        result.add("native_value_flow", nativeValueFlow(decompilation));
         JsonArray limitations = new JsonArray();
         limitations.add(
             "Unresolved computed or indirect flows without target addresses are not represented as reference edges."
@@ -1640,7 +1551,7 @@ public final class ReaGhidraBridge extends HeadlessScript {
         );
         if (swift && aarch64) {
             limitations.add(
-                "Swift String literals are decoded from constant register pairs at calls, returns and paired stores. Literals stored one word at a time, chosen by conditional selects, or built at runtime are not reported; candidate pairs at unresolved jumps are retained as unknown omissions."
+                "Swift String literals are decoded from constant register pairs at calls, returns and paired stores; literals stored one word at a time, chosen by conditional selects, passed through unresolved jumps, or built at runtime are not reported."
             );
             if (swiftLiterals.omissions().size() > 0) {
                 limitations.add(
@@ -1652,40 +1563,34 @@ public final class ReaGhidraBridge extends HeadlessScript {
                 "Swift String literal decoding is implemented for AArch64 register pairs only; no Swift literals were decoded for this architecture."
             );
         }
-        CallBoundaryObservation calls = callBoundaryObservation(
-            function, scan.instructions, calleeFunctions, true, outgoingReferences);
-        result.add("unresolved_calls", calls.unresolvedCalls());
-        for (String limitation : calls.limitations()) {
+        List<String> boundaryLimitations = noReturnCallLimitations(scan.instructions);
+        for (String limitation : boundaryLimitations) {
             limitations.add(limitation);
         }
         if (decompilation != null && decompilation.getErrorMessage() != null &&
             !decompilation.getErrorMessage().isBlank()) {
             limitations.add("Ghidra decompiler diagnostic: " + decompilation.getErrorMessage());
         }
-        if (decompilerFailure != null) {
-            limitations.add(
-                decompilerFailure + (decompilerFailure.endsWith(".") ? " " : ". ") +
-                "Pseudocode, the native API boundary and p-code value flow are unavailable for this procedure; assembly, comments, callers, callees, references, strings, names and basic blocks come from the Ghidra program listing and were still collected."
-            );
-        }
         result.add("limitations", limitations);
-        monitor.checkCancelled();
-        int missingCallers = 0;
-        for (Reference reference : bodyIncoming) {
-            monitor.checkCancelled();
-            if (unrepresentedCaller(reference, callerFunctions)) missingCallers++;
-        }
-        return new FunctionAnalysisObservation(result, calls.limitations(),
-            callRelationshipCoverage(calls, missingCallers), decompilerFailure != null);
+        return new FunctionAnalysisObservation(result, boundaryLimitations);
     }
 
     private JsonObject nativeValueFlow(DecompileResults decompilation) throws Exception {
         HighFunction highFunction =
             decompilation == null ? null : decompilation.getHighFunction();
         if (highFunction == null) {
-            return unavailableNativeValueFlow(
+            JsonObject unavailable = new JsonObject();
+            unavailable.addProperty("available", false);
+            unavailable.addProperty(
+                "reason",
                 "Ghidra has no HighFunction p-code model for this procedure"
             );
+            JsonArray limitations = new JsonArray();
+            limitations.add(
+                "No p-code operations or def-use relationships were recovered for this procedure."
+            );
+            unavailable.add("limitations", limitations);
+            return unavailable;
         }
 
         List<PcodeOpAST> selected = new ArrayList<>();
@@ -1992,18 +1897,6 @@ public final class ReaGhidraBridge extends HeadlessScript {
         return result;
     }
 
-    private JsonObject binaryInventorySummary(JsonObject params) throws Exception {
-        requireKeys(params, Set.of());
-        JsonObject result = new JsonObject();
-        result.addProperty("document", currentProgram.getName());
-        result.add("segments", segments());
-        // Count the owning inventories, preserving their exact discovery rules
-        // without serializing function identities or string values for counts.
-        result.addProperty("procedure_count", procedures().size());
-        result.addProperty("string_count", strings().size());
-        return result;
-    }
-
     private JsonArray listNames(JsonObject params) throws Exception {
         requireKeys(params, Set.of("document", "address"));
         requireDocument(params);
@@ -2030,10 +1923,6 @@ public final class ReaGhidraBridge extends HeadlessScript {
     private JsonArray listSegments(JsonObject params) {
         requireKeys(params, Set.of("document"));
         requireDocument(params);
-        return segments();
-    }
-
-    private JsonArray segments() {
         JsonArray result = new JsonArray();
         String imageBase = canonicalAddress(currentProgram.getImageBase());
         MemoryBlock[] blocks = currentProgram.getMemory().getBlocks();
@@ -2373,18 +2262,6 @@ public final class ReaGhidraBridge extends HeadlessScript {
         return result;
     }
 
-    private static JsonObject unavailableNativeValueFlow(String reason) {
-        JsonObject unavailable = new JsonObject();
-        unavailable.addProperty("available", false);
-        unavailable.addProperty("reason", reason);
-        JsonArray limitations = new JsonArray();
-        limitations.add(
-            "No p-code operations or def-use relationships were recovered for this procedure."
-        );
-        unavailable.add("limitations", limitations);
-        return unavailable;
-    }
-
     private static JsonObject unavailableNativeApiBoundary(String reason) {
         JsonObject unavailable = new JsonObject();
         unavailable.addProperty("available", false);
@@ -3399,278 +3276,52 @@ public final class ReaGhidraBridge extends HeadlessScript {
         return result;
     }
 
-    private static JsonObject facetAvailability(boolean available, String reason) {
-        JsonObject result = new JsonObject();
-        result.addProperty("available", available);
-        if (!available) result.addProperty("reason", reason);
-        return result;
-    }
-
-    private JsonObject callRelationshipObservation(JsonElement value, CallBoundaryObservation calls)
+    private List<String> noReturnCallLimitations(Iterable<Instruction> instructions)
             throws Exception {
-        monitor.checkCancelled();
-        JsonObject result = functionObservation(value, calls.limitations());
-        result.add("relationship_coverage", callRelationshipCoverage(calls, null));
-        return result;
-    }
-
-    private static JsonObject callRelationshipCoverage(
-            CallBoundaryObservation calls, Integer missingCallers) {
-        JsonObject coverage = completeResolvedCallCoverage();
-        Integer omitted = calls == null ? null : calls.unrepresentedCalleeCalls();
-        JsonArray directions = new JsonArray();
-        if (missingCallers != null && missingCallers > 0) directions.add("callers");
-        String callerLimitation = missingCallers != null && missingCallers > 0
-            ? "Ghidra's caller inventory omits sources of " + missingCallers +
-                " call reference(s) into this function's body." : null;
-        if ((calls != null && omitted == null) || (calls == null && missingCallers == null)) {
-            coverage.addProperty("status", "unknown");
-            String reason = calls == null ? "No call inventory was examined."
-                : "The callee inventory was not examined alongside decoded call targets.";
-            coverage.addProperty("reason", reason + (callerLimitation == null ? "" : " " + callerLimitation));
-            if (calls == null && missingCallers == null) directions.add("callers");
-            directions.add("callees");
-            coverage.add("limited_directions", directions);
-            return coverage;
-        }
-        JsonArray limitations = new JsonArray();
-        if (callerLimitation != null) limitations.add(callerLimitation);
-        if (omitted != null && omitted > 0) {
-            limitations.add("Ghidra's callee inventory omits targets of " + omitted +
-                " call reference(s) or decoded call(s) without destinations.");
-            directions.add("callees");
-        }
-        if (!limitations.isEmpty()) {
-            coverage.addProperty("status", "partial");
-            coverage.add("limitations", limitations);
-            coverage.add("limited_directions", directions);
-        }
-        return coverage;
-    }
-
-    private static JsonObject completeResolvedCallCoverage() {
-        JsonObject coverage = new JsonObject();
-        coverage.addProperty("status", "complete");
-        JsonArray diagnostics = new JsonArray();
-        diagnostics.add(
-            "Only resolved Ghidra call references are returned; unresolved computed or indirect calls remain unknown, while function classifications distinguish thunks and externals."
-        );
-        coverage.add("diagnostics", diagnostics);
-        return coverage;
-    }
-
-    private boolean unrepresentedCaller(Reference reference, Set<Function> callers) {
-        if (!reference.getReferenceType().isCall()) return false;
-        Function caller = containingFunction(reference.getFromAddress());
-        return caller == null || !callers.contains(caller);
-    }
-
-    private int unrepresentedIncomingCalls(Function function, Set<Function> callers)
-            throws Exception {
-        int[] omitted = { 0 };
-        visitReferences(function, "incoming", reference -> {
-            if (unrepresentedCaller(reference, callers)) omitted[0]++;
-        });
-        return omitted[0];
-    }
-
-    private List<String> functionBoundaryLimitations(
-            Function function, Iterable<Instruction> instructions)
-            throws Exception {
-        FunctionBoundaryLimitations boundary = new FunctionBoundaryLimitations(function);
-        for (Instruction instruction : instructions) boundary.observe(instruction);
-        return boundary.values();
-    }
-
-    private CallBoundaryObservation callBoundaryObservation(
-            Function function, Iterable<Instruction> instructions, Set<Function> returnedCallees,
-            boolean includeUnresolvedSites, List<Reference> observedReferences)
-            throws Exception {
-        FunctionBoundaryLimitations boundary = new FunctionBoundaryLimitations(function);
-        CallBoundaryReferences calls = new CallBoundaryReferences(returnedCallees, includeUnresolvedSites);
-        if (observedReferences == null) visitReferences(function, "outgoing", calls::observe);
-        else for (Reference reference : observedReferences) {
-            monitor.checkCancelled();
-            calls.observe(reference);
-        }
+        List<String> limitations = new ArrayList<>();
         for (Instruction instruction : instructions) {
-            boundary.observe(instruction);
-            if (!instruction.getFlowType().isCall()) continue;
-            boolean destination = false;
-            for (Reference reference : instruction.getReferencesFrom()) {
-                if (!reference.getReferenceType().isCall()) continue;
-                destination = true;
-                break;
-            }
-            if (!destination) {
-                calls.unrepresented++;
-                calls.unresolved(instruction.getAddress(),
-                    "Instruction decoder identifies a call but ReferenceManager supplies no call destination");
-            }
-        }
-        return new CallBoundaryObservation(boundary.values(),
-            returnedCallees == null ? null : calls.unrepresented, calls.unresolvedCalls());
-    }
-
-    private final class FunctionBoundaryLimitations {
-        private final Function function;
-        private final List<String> limitations = new ArrayList<>();
-        private Instruction beforePrevious;
-        private Instruction previous;
-
-        private FunctionBoundaryLimitations(Function function) {
-            this.function = function;
-        }
-
-        private void observe(Instruction instruction) throws Exception {
             monitor.checkCancelled();
-            String limitation = terminalCallLimitation(instruction);
-            if (limitation != null) limitations.add(limitation);
-            if (beforePrevious != null && previous != null) {
-                String seh = borlandSehHandlerLimitation(
-                    function, beforePrevious, previous, instruction);
-                if (seh != null) limitations.add(seh);
+            if (!instruction.getFlowType().isCall() || !instruction.getFlowType().isTerminal()) {
+                continue;
             }
-            beforePrevious = previous;
-            previous = instruction;
-        }
-
-        private List<String> values() {
-            return List.copyOf(limitations);
-        }
-    }
-
-    private String borlandSehHandlerLimitation(
-            Function function, Instruction handlerPush, Instruction framePush,
-            Instruction frameLink) {
-        if (!immediatelyPrecedes(handlerPush, framePush) ||
-            !immediatelyPrecedes(framePush, frameLink) ||
-            !handlerPush.getMnemonicString().equalsIgnoreCase("PUSH") ||
-            handlerPush.getNumOperands() != 1 ||
-            !framePush.getMnemonicString().equalsIgnoreCase("PUSH") ||
-            framePush.getNumOperands() != 1 ||
-            !frameLink.getMnemonicString().equalsIgnoreCase("MOV") ||
-            frameLink.getNumOperands() != 2 ||
-            !sameFsMemoryOperand(framePush, frameLink) ||
-            !hasRegisterOperand(frameLink, 1, "ESP"))
-            return null;
-        Object[] handlerOperand = handlerPush.getOpObjects(0);
-        if (handlerOperand.length != 1 || !(handlerOperand[0] instanceof Scalar scalar) ||
-            scalar.bitLength() != 32)
-            return null;
-        Address handler = currentProgram.getAddressFactory().getDefaultAddressSpace()
-            .getAddress(scalar.getUnsignedValue());
-        if (function.getBody().contains(handler)) return null;
-        return "Ghidra Listing shows a Borland/Delphi-style SEH frame registration at " +
-            canonicalAddress(frameLink.getAddress()) + " (push " + canonicalAddress(handler) +
-            " followed by fs-segment stack chaining); handler " + canonicalAddress(handler) +
-            " lies outside this procedure's body, so callees, strings, and cross-references may omit the handler region.";
-    }
-
-    private static boolean immediatelyPrecedes(Instruction first, Instruction second) {
-        Address fallThrough = first.getFallThrough();
-        return fallThrough != null && fallThrough.equals(second.getAddress());
-    }
-
-    private static boolean sameFsMemoryOperand(Instruction first, Instruction second) {
-        String firstOperand = normalizedFsMemoryOperand(first);
-        String secondOperand = normalizedFsMemoryOperand(second);
-        return firstOperand != null && firstOperand.equalsIgnoreCase(secondOperand);
-    }
-
-    private static String normalizedFsMemoryOperand(Instruction instruction) {
-        String representation = instruction.getDefaultOperandRepresentation(0);
-        representation = representation.replaceAll("(?i)\\b(?:byte|word|dword|qword)\\s+ptr\\s+", "")
-            .replaceAll("\\s+", "");
-        return representation.regionMatches(true, 0, "fs:", 0, 3) &&
-            representation.indexOf('[') >= 0 ? representation : null;
-    }
-
-    private static boolean hasRegisterOperand(
-            Instruction instruction, int operand, String name) {
-        for (Object object : instruction.getOpObjects(operand)) {
-            if (object instanceof Register register && register.getName().equalsIgnoreCase(name))
-                return true;
-        }
-        return false;
-    }
-
-    private final class CallBoundaryReferences {
-        private final Set<Function> returnedCallees;
-        private final TreeMap<Address, String> unresolved;
-        private int unrepresented;
-
-        CallBoundaryReferences(Set<Function> returnedCallees, boolean includeUnresolvedSites) {
-            this.returnedCallees = returnedCallees;
-            unresolved = includeUnresolvedSites ? new TreeMap<>() : null;
-        }
-
-        void observe(Reference reference) {
-            if (!reference.getReferenceType().isCall()) return;
-            // Reference identity follows the same containing-function owner as referenceEdge.
-            Function target = containingFunction(reference.getToAddress());
-            if (returnedCallees != null && (target == null || !returnedCallees.contains(target)))
-                unrepresented++;
-            if (target == null) unresolved(reference.getFromAddress(),
-                "A call destination has no known containing Ghidra procedure");
-        }
-
-        void unresolved(Address address, String reason) {
-            if (unresolved != null) unresolved.put(address, reason);
-        }
-
-        JsonArray unresolvedCalls() {
-            if (unresolved == null) return null;
-            JsonArray result = new JsonArray();
-            for (var item : unresolved.entrySet()) {
-                JsonObject site = new JsonObject();
-                site.addProperty("address", canonicalAddress(item.getKey()));
-                site.addProperty("reason", item.getValue());
-                result.add(site);
-            }
-            return result;
-        }
-    }
-
-    private String terminalCallLimitation(Instruction instruction) {
-        if (!instruction.getFlowType().isCall() || !instruction.getFlowType().isTerminal())
-            return null;
-        Address[] destinations = instruction.getFlows();
-        StringBuilder limitation = new StringBuilder();
-        limitation.append("Ghidra Listing reports a terminal call at ")
-            .append(canonicalAddress(instruction.getAddress()));
-        if (destinations.length == 0) {
-            limitation.append(" with no resolved callee; its no-return basis is unknown.");
-        }
-        else {
-            limitation.append(" to ");
-            for (int index = 0; index < destinations.length; index++) {
-                if (index > 0) limitation.append(", ");
-                Address destination = destinations[index];
-                limitation.append(canonicalAddress(destination));
-                Function target = currentProgram.getFunctionManager().getFunctionAt(destination);
-                if (target == null) {
-                    limitation.append(" (callee identity unknown)");
-                }
-                else {
-                    limitation.append(" ").append(procedureName(target));
-                    limitation.append(" (external=").append(target.isExternal());
-                    limitation.append(", thunk=").append(target.isThunk());
-                    limitation.append(", hasNoReturn=").append(target.hasNoReturn()).append(")");
-                }
-            }
-            limitation.append("; fallthrough is excluded by Ghidra's flow model.");
-            Function target = destinations.length == 1
-                ? currentProgram.getFunctionManager().getFunctionAt(destinations[0])
-                : null;
-            if (target != null && target.hasNoReturn()) {
-                limitation.append(" This records Ghidra's FunctionManager flag, not an independent verification that the callee cannot return.");
+            Address[] destinations = instruction.getFlows();
+            StringBuilder limitation = new StringBuilder();
+            limitation.append("Ghidra Listing reports a terminal call at ")
+                .append(canonicalAddress(instruction.getAddress()));
+            if (destinations.length == 0) {
+                limitation.append(" with no resolved callee; its no-return basis is unknown.");
             }
             else {
-                limitation.append(" The reason for the terminal flow is not established by this observation.");
+                limitation.append(" to ");
+                for (int index = 0; index < destinations.length; index++) {
+                    if (index > 0) limitation.append(", ");
+                    Address destination = destinations[index];
+                    limitation.append(canonicalAddress(destination));
+                    Function target = currentProgram.getFunctionManager().getFunctionAt(destination);
+                    if (target == null) {
+                        limitation.append(" (callee identity unknown)");
+                    }
+                    else {
+                        limitation.append(" ").append(procedureName(target));
+                        limitation.append(" (external=").append(target.isExternal());
+                        limitation.append(", thunk=").append(target.isThunk());
+                        limitation.append(", hasNoReturn=").append(target.hasNoReturn()).append(")");
+                    }
+                }
+                limitation.append("; fallthrough is excluded by Ghidra's flow model.");
+                Function target = destinations.length == 1
+                    ? currentProgram.getFunctionManager().getFunctionAt(destinations[0])
+                    : null;
+                if (target != null && target.hasNoReturn()) {
+                    limitation.append(" This records Ghidra's FunctionManager flag, not an independent verification that the callee cannot return.");
+                }
+                else {
+                    limitation.append(" The reason for the terminal flow is not established by this observation.");
+                }
             }
+            limitations.add(limitation.toString());
         }
-        return limitation.toString();
+        return limitations;
     }
 
     private static String renderAssembly(List<Instruction> instructions) {
@@ -3696,62 +3347,43 @@ public final class ReaGhidraBridge extends HeadlessScript {
     private List<Reference> collectReferences(
             Function function,
             String direction) throws Exception {
+        // References can target instruction interiors or originate in embedded
+        // data. Use actual body ownership, including an external's exact entry.
+        AddressSet scope = new AddressSet(function.getBody());
+        scope.add(function.getEntryPoint());
+        boolean outgoing = direction.equals("outgoing");
+        AddressIterator addresses = outgoing
+            ? currentProgram.getReferenceManager().getReferenceSourceIterator(scope, true)
+            : currentProgram.getReferenceManager().getReferenceDestinationIterator(scope, true);
         TreeMap<String, Reference> observed = new TreeMap<>();
-        visitReferences(function, direction, reference -> addReference(observed, reference));
+        while (addresses.hasNext()) {
+            monitor.checkCancelled();
+            Address address = addresses.next();
+            if (outgoing) {
+                for (Reference reference : currentProgram.getReferenceManager()
+                        .getReferencesFrom(address)) {
+                    monitor.checkCancelled();
+                    addReference(observed, reference);
+                }
+            }
+            else {
+                ReferenceIterator iterator = currentProgram.getReferenceManager()
+                    .getReferencesTo(address);
+                while (iterator.hasNext()) {
+                    monitor.checkCancelled();
+                    addReference(observed, iterator.next());
+                }
+            }
+        }
         List<Reference> result = new ArrayList<>(observed.values());
         result.sort(REFERENCE_ORDER);
         return result;
     }
 
-    @FunctionalInterface
-    private interface ReferenceVisitor {
-        void accept(Reference reference) throws Exception;
-    }
-
-    private void visitReferences(Function function, String direction, ReferenceVisitor visitor)
-            throws Exception {
-        // References can target instruction interiors or originate in embedded
-        // data. Use actual body ownership, including an external's exact entry.
-        AddressSet scope = functionObservationScope(function);
-        boolean outgoing = direction.equals("outgoing");
-        AddressIterator addresses = outgoing
-            ? currentProgram.getReferenceManager().getReferenceSourceIterator(scope, true)
-            : currentProgram.getReferenceManager().getReferenceDestinationIterator(scope, true);
-        while (addresses.hasNext()) {
-            monitor.checkCancelled();
-            Address address = addresses.next();
-            if (outgoing) {
-                visitObservedReferencesFrom(address, visitor);
-            }
-            else {
-                visitObservedReferencesTo(address, visitor);
-            }
-        }
-    }
-
-    private void visitObservedReferencesFrom(Address address, ReferenceVisitor visitor)
-            throws Exception {
-        for (Reference reference : currentProgram.getReferenceManager().getReferencesFrom(address)) {
-            monitor.checkCancelled();
-            visitObservedReference(reference, visitor);
-        }
-    }
-
-    private void visitObservedReferencesTo(Address address, ReferenceVisitor visitor)
-            throws Exception {
-        ReferenceIterator references = currentProgram.getReferenceManager().getReferencesTo(address);
-        while (references.hasNext()) {
-            monitor.checkCancelled();
-            visitObservedReference(references.next(), visitor);
-        }
-    }
-
-    private static void visitObservedReference(Reference reference, ReferenceVisitor visitor)
-            throws Exception {
-        if (!reference.isEntryPointReference()) visitor.accept(reference);
-    }
-
     private static void addReference(TreeMap<String, Reference> observed, Reference reference) {
+        if (reference.isEntryPointReference()) {
+            return;
+        }
         String key = canonicalAddress(reference.getFromAddress()) + "\u0000" +
             canonicalAddress(reference.getToAddress()) + "\u0000" +
             reference.getReferenceType().getName() + "\u0000" +
@@ -3760,12 +3392,6 @@ public final class ReaGhidraBridge extends HeadlessScript {
         observed.putIfAbsent(key, reference);
     }
 
-    private static AddressSet functionObservationScope(Function function) {
-        AddressSet scope = new AddressSet(function.getBody());
-        scope.add(function.getEntryPoint());
-        return scope;
-    }
-
     private JsonArray referenceEdges(List<Reference> references) {
         JsonArray result = new JsonArray();
         for (Reference reference : references) {
@@ -3919,28 +3545,23 @@ public final class ReaGhidraBridge extends HeadlessScript {
         return result;
     }
 
-    private JsonArray comments(Function function) throws Exception {
-        Listing listing = currentProgram.getListing();
-        AddressSet scope = functionObservationScope(function);
-        AddressIterator addresses = listing.getCommentAddressIterator(scope, true);
+    private static JsonArray comments(List<Instruction> instructions) {
         TreeMap<String, JsonObject> observed = new TreeMap<>();
-        while (addresses.hasNext()) {
-            monitor.checkCancelled();
-            Address address = addresses.next();
+        for (Instruction instruction : instructions) {
             for (CommentType type : CommentType.values()) {
-                String text = listing.getComment(type, address);
+                String text = instruction.getComment(type);
                 if (text == null || text.isEmpty()) {
                     continue;
                 }
                 String kind = type == CommentType.EOL ? "inline" : "comment";
                 JsonObject item = new JsonObject();
-                item.addProperty("address", canonicalAddress(address));
+                item.addProperty("address", canonicalAddress(instruction.getAddress()));
                 item.addProperty("kind", kind);
                 item.addProperty("text", text);
-                String key = canonicalAddress(address) + "\u0000" +
+                String key = canonicalAddress(instruction.getAddress()) + "\u0000" +
                     kind + "\u0000" + type.name() + "\u0000" + text;
                 observed.put(key, item);
-            }
+                    }
         }
         JsonArray result = new JsonArray();
         observed.values().forEach(result::add);
@@ -4011,20 +3632,13 @@ public final class ReaGhidraBridge extends HeadlessScript {
      * The canonical empty string is a small literal with a zero count.
      */
     private SwiftStringLiteralDecode swiftStringLiterals(Function function) throws Exception {
-        return swiftStringLiterals(function, new SwiftLiteralBudget());
-    }
-
-    // An explicit budget makes capacity omissions deterministic in producer tests.
-    private SwiftStringLiteralDecode swiftStringLiterals(
-        Function function,
-        SwiftLiteralBudget budget
-    ) throws Exception {
         Register[] registers = new Register[31];
         for (int index = 0; index < registers.length; index++) {
             registers[index] = currentProgram.getRegister("x" + index);
         }
         TreeMap<String, JsonObject> observed = new TreeMap<>();
         TreeMap<String, JsonObject> omitted = new TreeMap<>();
+        SwiftLiteralBudget budget = new SwiftLiteralBudget();
         Map<String, Boolean> selectedValues = new HashMap<>();
         SymbolicPropogator propagator = new SymbolicPropogator(currentProgram, false);
         propagator.flowConstants(function.getEntryPoint(), function.getBody(), new ContextEvaluatorAdapter() {
@@ -4032,9 +3646,6 @@ public final class ReaGhidraBridge extends HeadlessScript {
             public boolean evaluateContextBefore(VarnodeContext context, Instruction instruction) {
                 // Returning true ends only the current flow, so every queued flow checks the shared stop.
                 if (budget.stopped()) return true;
-                FlowType flow = instruction.getFlowType();
-                Address[] flowTargets = instruction.getFlows();
-                boolean unresolvedJump = flow.isJump() && !flow.isConditional() && flowTargets.length == 0;
                 for (Register[] pair : swiftStringPairs(function, instruction, registers)) {
                     Long word = registerConstant(context, pair[0]);
                     Long object = registerConstant(context, pair[1]);
@@ -4084,14 +3695,12 @@ public final class ReaGhidraBridge extends HeadlessScript {
                     JsonObject item = overCapacity
                         ? swiftStringOmission(layout, word, object)
                         : swiftStringItem(value, layout, word, object);
-                    if (unresolvedJump && !overCapacity)
-                        item = swiftStringOmission(layout, word, object, "unresolved_jump");
                     item.addProperty("source_address", canonicalAddress(instruction.getAddress()));
                     JsonArray pairRegisters = new JsonArray();
                     pairRegisters.add(pair[0].getName());
                     pairRegisters.add(pair[1].getName());
                     item.add("registers", pairRegisters);
-                    (overCapacity || unresolvedJump ? omitted : observed).put(key, item);
+                    (overCapacity ? omitted : observed).put(key, item);
                     if (overCapacity) {
                         budget.stop();
                         return true;
@@ -4127,12 +3736,11 @@ public final class ReaGhidraBridge extends HeadlessScript {
             if (operation.getOpcode() == PcodeOp.RETURN) returns = true;
         }
         // A jump is a proven tail call only when it has resolved targets and all leave the
-        // body. For unresolved targetless jumps, candidate literals remain unknown omissions.
+        // body. A targetless computed jump can still dispatch inside the function.
         Address[] targets = instruction.getFlows();
         boolean tailCall = flow.isJump() && !flow.isConditional() && targets.length > 0 &&
             Arrays.stream(targets).allMatch(target -> !function.getBody().contains(target));
-        boolean unresolvedJump = flow.isJump() && !flow.isConditional() && targets.length == 0;
-        if (!flow.isCall() && !returns && !tailCall && !unresolvedJump) return pairs;
+        if (!flow.isCall() && !returns && !tailCall) return pairs;
         // A String occupies two consecutive registers among x0-x7, or x0 and x1 when returned.
         int lastFirstRegister = returns ? 0 : 6;
         for (int index = 0; index <= lastFirstRegister; index++) {
@@ -4275,11 +3883,6 @@ public final class ReaGhidraBridge extends HeadlessScript {
             remaining = Math.max(0, (runtime.maxMemory() - runtime.totalMemory() + runtime.freeMemory()) / 2);
         }
 
-        SwiftLiteralBudget(long remaining) {
-            if (remaining < 0) throw new IllegalArgumentException("Swift literal budget must be nonnegative");
-            this.remaining = remaining;
-        }
-
         boolean takeState() {
             if (remaining < BYTES_PER_RECORD) return false;
             remaining -= BYTES_PER_RECORD;
@@ -4318,15 +3921,6 @@ public final class ReaGhidraBridge extends HeadlessScript {
     }
 
     private static JsonObject swiftStringOmission(SwiftLiteralLayout layout, long word, long object) {
-        return swiftStringOmission(layout, word, object, "capacity");
-    }
-
-    private static JsonObject swiftStringOmission(
-        SwiftLiteralLayout layout,
-        long word,
-        long object,
-        String reason
-    ) {
         JsonObject item = new JsonObject();
         item.addProperty("representation", layout.representation());
         if (layout.address() == null) {
@@ -4335,7 +3929,7 @@ public final class ReaGhidraBridge extends HeadlessScript {
             item.addProperty("address", canonicalAddress(layout.address()));
         }
         item.addProperty("byte_length", layout.byteLength());
-        item.addProperty("reason", reason);
+        item.addProperty("reason", "capacity");
         item.add("words", swiftStringWords(word, object));
         return item;
     }
@@ -4903,8 +4497,7 @@ public final class ReaGhidraBridge extends HeadlessScript {
     private record InventoryItem(Address address, String value, JsonObject facts) {}
     private record AddressNameRequest(String inputAddress, Address address, String name) {}
     private record FunctionEntry(Function function, InventoryItem item) {}
-    private record FunctionAnalysisObservation(JsonObject dossier, List<String> limitations, JsonObject relationshipCoverage, boolean decompilerFailed) {}
-    private record CallBoundaryObservation(List<String> limitations, Integer unrepresentedCalleeCalls, JsonArray unresolvedCalls) {}
+    private record FunctionAnalysisObservation(JsonObject dossier, List<String> limitations) {}
     private record SwiftStringLiteralDecode(JsonArray literals, JsonArray omissions) {}
     private record SwiftLiteralLayout(
         String representation,

bridge/hopper_bridge.py

@@ -236,15 +236,6 @@ def _name_matches(document, address, name):
     return observed == name or (not name and observed is None)
 
 
-def _bookmark_name(document, address):
-    getter = getattr(document, "getBookmarkName", None)
-    if not callable(getter):
-        raise CapabilityUnavailableError(
-            "Hopper's public Python API does not expose getBookmarkName"
-        )
-    return getter(address)
-
-
 def _address(document, value=None):
     """Keep explicit hexadecimal coordinates distinct from symbol names."""
     if value is None:
@@ -440,6 +431,10 @@ def _procedure_map(document):
     return result
 
 
+def _strings(document):
+    return {address: record["value"] for address, record in _string_inventory(document).items()}
+
+
 def _string_record(segment, address, display):
     """Read one native typed object, retaining its shortened display separately."""
     length = segment.getObjectLength(address)
@@ -526,7 +521,7 @@ def _search_inventory(document, kind):
         if kind == "procedure":
             values = _procedure_map(document)
         elif kind == "string":
-            values = _string_inventory(document)
+            values = _strings(document)
         elif kind == "name":
             values = {_hex(address): value for address, value in _name_map(document).items()}
         else:
@@ -553,17 +548,23 @@ def _search_results(document, kind, params):
     else:
         raise CapabilityUnavailableError("Regex matching requires REA's supervised worker; the native bridge only executes literal searches")
 
+    selected = []
+    for item in _search_inventory(document, kind):
+        if not matches(item[1]):
+            continue
+        selected.append(item)
+    if not selected:
+        return []
     if kind == "string":
-        return [
-            {"address": address, **record}
-            for address, record in _search_inventory(document, kind)
-            if matches(record["value"])
-        ]
+        records = _string_inventory(document)
+        return [{"address": address, **records[address]} for address, _ in selected]
     return [
-        {"address": address, "value": value}
-        for address, value in _search_inventory(document, kind)
-        if matches(value)
-    ]
+            {
+                "address": address,
+                "value": value,
+            }
+            for address, value in selected
+        ]
 
 
 def _unavailable(reason):
@@ -643,7 +644,7 @@ def _analyze_function(document, params):
             "end": _hex(_basic_block_end(procedure, block)),
             "successors": sorted(set(successors), key=lambda value: int(value, 16)),
         })
-    pseudo = _pseudocode(document, procedure)
+    pseudo = _pseudocode(document, procedure) or ""
     assembly_lines = _assembly(procedure).splitlines()
     callers = sorted((_procedure_identity(item) for item in procedure.getAllCallerProcedures()), key=lambda item: int(item["address"], 16))
     callees = sorted((_procedure_identity(item) for item in procedure.getAllCalleeProcedures()), key=lambda item: int(item["address"], 16))
@@ -705,7 +706,7 @@ def _analyze_function(document, params):
             "signature": procedure.signatureString(),
             "locals": _procedure_locals(procedure),
         },
-        "pseudocode": pseudo or "",
+        "pseudocode": pseudo,
         "assembly": assembly_lines,
         "comments": comments,
         "callers": callers, "callees": callees,
@@ -717,12 +718,6 @@ def _analyze_function(document, params):
         "basic_blocks": blocks,
         "native_api": None,
         "native_value_flow": None,
-        "facet_availability": {
-            "pseudocode": {"available": True} if pseudo is not None else _unavailable("Hopper did not supply pseudocode."),
-            **{facet: {"available": True} for facet in (
-                "assembly", "comments", "callers", "callees", "references", "strings_names", "cfg"
-            )},
-        },
         "limitations": [
             "Native CallReference classifications are observed where available; detailed reference flags remain unknown.",
             "Hopper's public Python API does not expose equivalent external or thunk classification in this dossier.",
@@ -735,12 +730,7 @@ def _analyze_function(document, params):
 def _dispatch(method, params):
     """Dispatch only the closed operation set implemented by REA's public tools."""
     if method == "health":
-        return {
-            "name": "REA Hopper bridge",
-            "version": "1.0.0",
-            "run_id": REA_RUN_ID,
-            "process_id": os.getpid(),
-        }
+        return {"name": "REA Hopper bridge", "version": "1.0.0", "run_id": REA_RUN_ID}
     if method in ("shutdown", "shutdown_document"):
         document = _session_document()
         if document is None:
@@ -1003,46 +993,15 @@ def _dispatch(method, params):
         observed = getter(address)
         return observed == comment or (comment == "" and observed is None)
     if method == "list_bookmarks":
-        return [{"address": _hex(item), "name": _bookmark_name(document, item)} for item in document.getBookmarks()]
+        return [{"address": _hex(item), "name": document.getBookmarkName(item)} for item in document.getBookmarks()]
     if method == "set_bookmark":
         address = _address(document, params.get("address"))
         _segment(document, address)
         name = params.get("name")
         if name is not None:
             _api_text(name, "Bookmark name")
-        has_bookmark = getattr(document, "hasBookmarkAtAddress", None)
-        if not callable(has_bookmark):
-            raise CapabilityUnavailableError(
-                "Hopper's public Python API does not expose hasBookmarkAtAddress"
-            )
-        exists = has_bookmark(address)
-        if name is None and exists:
-            # Omission means preserve the existing bookmark and its name.
-            return True
-        if not callable(getattr(document, "getBookmarkName", None)):
-            raise CapabilityUnavailableError(
-                "Hopper's public Python API does not expose getBookmarkName"
-            )
-        if name == "" and exists:
-            rename = getattr(document, "renameBookmarkAtAddress", None)
-            if not callable(rename):
-                raise CapabilityUnavailableError(
-                    "Hopper's public Python API does not expose renameBookmarkAtAddress"
-                )
-            rename(address, name)
-        else:
-            setter = getattr(document, "setBookmarkAtAddress", None)
-            if not callable(setter):
-                raise CapabilityUnavailableError(
-                    "Hopper's public Python API does not expose setBookmarkAtAddress"
-                )
-            setter(address, name)
-        if not has_bookmark(address):
-            return False
-        observed = _bookmark_name(document, address)
-        if name is None:
-            return observed is None or observed == ""
-        return observed == name or (name == "" and observed is None)
+        document.setBookmarkAtAddress(address, name)
+        return document.hasBookmarkAtAddress(address)
     if method == "unset_bookmark":
         address = _address(document, params.get("address"))
         # Permit removing a legacy orphan bookmark, but do not report success
@@ -1087,10 +1046,6 @@ def _serve_connection(connection):
                 ):
                     raise PermissionError("Invalid bridge capability")
                 authenticated = True
-                # The connection grace period only bounds unauthenticated idle
-                # clients. Native analysis and a connected owner's idle time
-                # remain unbounded after capability validation.
-                connection.settimeout(None)
                 _write_message(file, {"id": request_id, "event": {
                     "type": "progress",
                     "phase": "hopper_bridge",
@@ -1182,17 +1137,13 @@ def _run():
     server.bind(REA_SOCKET)
     os.chmod(REA_SOCKET, 0o600)
     server.listen(1)
-    # A bridge can start after its caller's startup/cleanup deadline. Bound
-    # the first accept as well as reconnects so an orphan cannot pin Hopper's
-    # dedicated Python thread and prevent later documents from starting REA.
-    server.settimeout(REA_RECONNECT_TIMEOUT_SECONDS)
     try:
         while True:
             try:
                 connection, _ = server.accept()
             except socket.timeout:
                 break
-            connection.settimeout(REA_RECONNECT_TIMEOUT_SECONDS)
+            connection.settimeout(None)
             if _serve_connection(connection):
                 break
             # Match REA's cleanup handshake budget without pinning Hopper's

bridge/mitmproxy/capture.py

@@ -6,13 +6,11 @@ The containing mitmdump process and its configuration directory are REA-owned.
 
 import base64
 import hashlib
-import ipaddress
 import json
 import math
 import re
 import resource
 from pathlib import Path
-from urllib.parse import unquote_to_bytes
 
 from mitmproxy import ctx, version
 from mitmproxy.io import tnetstring
@@ -43,167 +41,6 @@ class BoundedReader:
         return self.handle.read(count)
 
 
-SPECIAL_SCHEMES = {"ftp", "file", "http", "https", "ws", "wss"}
-SCHEME_PREFIX = r"^[\x00-\x20]*([a-z][a-z0-9+.-]*):"
-NETWORK_PREFIX = r"^[\x00-\x20]*[/\\]{2}"
-URL_IGNORABLE_CONTROLS = "\t\n\r"
-URL_CONTROL_TRANSLATION = {ord(char): None for char in URL_IGNORABLE_CONTROLS}
-C0_CONTROL_OR_SPACE = "".join(chr(code) for code in range(0x21))
-FORBIDDEN_DOMAIN_CODE_POINTS = set(C0_CONTROL_OR_SPACE) | set("#%/:<>?@[\\]^|\x7f")
-
-
-def authority_start(text, base_scheme=None):
-    """Return where an authority begins and whether it is special, or None.
-
-    Follows WHATWG URL parsing as src/domain/recordedTransportUrl.ts does:
-    special schemes (and scheme-relative references) skip every leading "/"
-    or "\\" before the authority, so `https://\\user:pass@host` still has
-    userinfo. File URLs never carry userinfo: an "@" in a file host makes
-    WHATWG reject the whole URL, so there are no credentials to remove.
-    """
-    scheme = re.match(SCHEME_PREFIX, text, flags=re.I)
-    name = scheme.group(1).lower() if scheme is not None else None
-    if name == "file" or (name is None and base_scheme == "file"):
-        return None
-    if name is not None and name in SPECIAL_SCHEMES:
-        # A same-scheme Location without two slash-equivalent separators is
-        # relative to the recorded request, so its @ belongs to the path.
-        following = text[scheme.end():scheme.end() + 2]
-        if name == base_scheme and (len(following) < 2 or any(char not in "/\\" for char in following)):
-            return None
-        start = scheme.end()
-    else:
-        if scheme is not None:
-            if text[scheme.end():scheme.end() + 2] != "//":
-                return None
-            return scheme.end() + 2, False
-        # A non-special base treats backslashes as authority data and only
-        # recognizes two forward slashes as a network reference.
-        if base_scheme is not None and base_scheme not in SPECIAL_SCHEMES:
-            prefix = re.match(r"^[\x00-\x20]*//", text)
-            return None if prefix is None else (prefix.end(), False)
-        prefix = re.match(NETWORK_PREFIX, text)
-        if prefix is None:
-            return None
-        start = prefix.end()
-    while start < len(text) and text[start] in "/\\":
-        start += 1
-    return start, True
-
-
-IPV4_DIGITS = {8: "01234567", 10: "0123456789", 16: "0123456789abcdefABCDEF"}
-
-
-def ipv4_number(part):
-    """WHATWG IPv4 number parser: decimal, 0x hex or 0-prefixed octal, else None."""
-    if part == "":
-        return None
-    radix, digits = 10, part
-    if part[:2] in ("0x", "0X"):
-        radix, digits = 16, part[2:]
-    elif len(part) > 1 and part[0] == "0":
-        radix, digits = 8, part[1:]
-    if digits == "":
-        return 0
-    if any(char not in IPV4_DIGITS[radix] for char in digits):
-        return None
-    # Bound decimal text before int(): Python limits decimal conversions to
-    # 4300 digits, and anything past 10 significant digits exceeds IPv4.
-    significant = digits.lstrip("0")
-    if radix == 10 and len(significant) > 10:
-        return 2**32
-    return int(digits, radix)
-
-
-def domain_parses(domain):
-    """Apply WHATWG's ends-in-a-number check and IPv4 parser to a domain."""
-    parts = domain.split(".")
-    if parts[-1] == "" and len(parts) > 1:
-        parts.pop()
-    last = parts[-1]
-    if not ((last != "" and last.isascii() and last.isdigit()) or ipv4_number(last) is not None):
-        return True
-    numbers = [ipv4_number(part) for part in parts]
-    if len(parts) > 4 or any(number is None for number in numbers):
-        return False
-    return all(number <= 255 for number in numbers[:-1]) and numbers[-1] < 256 ** (5 - len(numbers))
-
-
-def special_host_parses(host_port):
-    """Whether WHATWG could accept a special authority's host and port.
-
-    A rejected host fails the whole URL, so it has no credentials to remove.
-    This mirrors the forbidden-code-point, empty-host, IPv4, IPv6 and port
-    rules for ASCII hosts. UTS #46 mapping is not modeled: a non-ASCII host
-    may map to an accepted one (fullwidth digits, ideographic full stops,
-    ignored code points), so it is treated as accepted and still redacts.
-    """
-    if host_port.startswith("["):
-        host_end = host_port.find("]") + 1
-        literal = host_port[1 : host_end - 1]
-        if host_end == 0 or "%" in literal:
-            return False
-        try:
-            ipaddress.IPv6Address(literal)
-        except ValueError:
-            return False
-    else:
-        colon = host_port.find(":")
-        host_end = len(host_port) if colon < 0 else colon
-        host = unquote_to_bytes(host_port[:host_end]).decode("utf-8", errors="replace")
-        # Mapping never removes ASCII, so these rejections hold either way.
-        if host == "" or any(char in FORBIDDEN_DOMAIN_CODE_POINTS for char in host):
-            return False
-        if host.isascii() and not domain_parses(host.lower()):
-            return False
-    port = host_port[host_end:]
-    if port == "":
-        return True
-    digits = port[1:]
-    if port[0] != ":" or not (digits == "" or (digits.isascii() and digits.isdigit())):
-        return False
-    # Bound the text first: int() refuses decimal strings over 4300 digits.
-    significant = digits.lstrip("0")
-    return len(significant) <= 5 and int(significant or "0") <= 65535
-
-
-def without_userinfo(value, base_scheme=None):
-    """Remove an authority's userinfo using the WHATWG authority boundary.
-
-    Special schemes and scheme-relative references also end the authority
-    at a backslash, so later path text containing "@" is not userinfo.
-    """
-    binary = isinstance(value, bytes)
-    text = value.decode("latin-1") if binary else value
-    # WHATWG removes these controls before interpreting scheme/separators.
-    # Keep that parse view separate from the exact source spelling and bytes.
-    # It also drops trailing C0 controls and spaces; offsets are unchanged.
-    parsed_text = text.translate(URL_CONTROL_TRANSLATION).rstrip(C0_CONTROL_OR_SPACE)
-    located = authority_start(parsed_text, base_scheme)
-    if located is None:
-        return value
-    start, special = located
-    terminators = "/?#\\" if special else "/?#"
-    end = start
-    while end < len(parsed_text) and parsed_text[end] not in terminators:
-        end += 1
-    at = parsed_text.rfind("@", start, end)
-    if at < start or (special and not special_host_parses(parsed_text[at + 1 : end])):
-        return value
-    parsed_offset = 0
-    raw_start = 0
-    for raw_offset, char in enumerate(text):
-        if char in URL_IGNORABLE_CONTROLS:
-            continue
-        if parsed_offset == start:
-            raw_start = raw_offset
-        if parsed_offset == at:
-            safe = text[:raw_start] + text[raw_offset + 1 :]
-            return safe.encode("latin-1") if binary else safe
-        parsed_offset += 1
-    raise CaptureFailure("decoder", "Normalized URL authority could not be bound to its source.")
-
-
 def project_record(state, secrets):
     binaries, numbers, redactions = [], [], []
     byte_secrets = []
@@ -221,23 +58,16 @@ def project_record(state, secrets):
             return None
         return text
 
-    def transport_value(value, path, transport_url, base_scheme):
+    def transport_value(value, path, transport_url):
         if not (transport_url or re.fullmatch(r"/(?:backup/)*request/(?:path|authority)", path)):
             return value, False
         binary = isinstance(value, bytes)
+        pattern = rb"^([\x00-\x20]*(?:[a-z][a-z0-9+.-]*:)?//)[^/?#]*@" if binary else r"^([\x00-\x20]*(?:[a-z][a-z0-9+.-]*:)?//)[^/?#]*@"
+        replacement = rb"\1" if binary else r"\1"
         separator = b"@" if binary else "@"
-        if transport_url:
-            safe_url = without_userinfo(value, base_scheme)
-        elif path.endswith("/authority"):
-            safe_url = value.rsplit(separator, 1)[-1]
-        else:
-            # Native request.path is origin-form unless it explicitly carries
-            # a scheme (absolute-form). Leading separators are path evidence,
-            # not a header URL reference's network authority.
-            text = value.decode("latin-1") if binary else value
-            safe_url = without_userinfo(value) if re.match(
-                SCHEME_PREFIX, text.translate(URL_CONTROL_TRANSLATION), flags=re.I
-            ) else value
+        safe_url = re.sub(pattern, replacement, value, flags=re.I)
+        if path.endswith("/authority") and separator in safe_url:
+            safe_url = safe_url.rsplit(separator, 1)[1]
         changed = safe_url != value
         if changed:
             redactions.append({"pointer": path, "reason": "transport-credential"})
@@ -250,7 +80,7 @@ def project_record(state, secrets):
         del numbers[before[1]:]
         del redactions[before[2]:]
 
-    def visit(value, path, depth=0, credential=False, transport_url=False, base_scheme=None):
+    def visit(value, path, depth=0, credential=False, transport_url=False):
         if depth > 64:
             raise CaptureFailure("input-limit", "Native capture exceeds the 64-level evidence nesting budget.", path)
         if credential:
@@ -260,7 +90,7 @@ def project_record(state, secrets):
                 binaries.append({"pointer": path, "representation": "producer-bytes", "state": "redacted", "content_base64": None, "bytes": None, "sha256": None})
             return None
         if isinstance(value, bytes):
-            safe_bytes, credential_url = transport_value(value, path, transport_url, base_scheme)
+            safe_bytes, credential_url = transport_value(value, path, transport_url)
             content_base64 = base64.b64encode(value).decode("ascii")
             digest = hashlib.sha256(value).hexdigest()
             hidden = any(secret in value or secret in safe_bytes for secret in byte_secrets) or any(secret in content_base64 or secret in digest or secret in str(len(value)) for secret in secrets)
@@ -277,7 +107,7 @@ def project_record(state, secrets):
                 return None
             return safe_text
         if isinstance(value, str):
-            safe_text, _ = transport_value(value, path, transport_url, base_scheme)
+            safe_text, _ = transport_value(value, path, transport_url)
             return redact(safe_text, path, value)
         if isinstance(value, bool) or value is None:
             return value
@@ -295,16 +125,10 @@ def project_record(state, secrets):
                 for index, field in enumerate(value):
                     if not isinstance(field, (list, tuple)) or len(field) != 2 or not isinstance(field[0], bytes):
                         raise CaptureFailure("format", "Native header/trailer is not an ordered byte pair.", pointer(path, index))
-                    result.append([visit(field[0], pointer(pointer(path, index), 0), depth + 2), visit(field[1], pointer(pointer(path, index), 1), depth + 2, field[0].lower() in CREDENTIALS, field[0].lower() in {b"location", b"referer", b"origin"}, base_scheme if field[0].lower() == b"location" else None)])
+                    result.append([visit(field[0], pointer(pointer(path, index), 0), depth + 2), visit(field[1], pointer(pointer(path, index), 1), depth + 2, field[0].lower() in CREDENTIALS, field[0].lower() in {b"location", b"referer", b"origin"})])
                 return result
-            return [visit(item, pointer(path, index), depth + 1, base_scheme=base_scheme) for index, item in enumerate(value)]
+            return [visit(item, pointer(path, index), depth + 1) for index, item in enumerate(value)]
         if isinstance(value, dict):
-            if path == "" or re.fullmatch(r"/backup(?:/backup)*", path):
-                request = value.get("request")
-                scheme = request.get("scheme") if isinstance(request, dict) else None
-                if isinstance(scheme, bytes):
-                    scheme = scheme.decode("latin-1")
-                base_scheme = scheme.lower() if isinstance(scheme, str) and re.fullmatch(r"[a-z][a-z0-9+.-]*", scheme, flags=re.I) else None
             result = {}
             for key, item in value.items():
                 if not isinstance(key, str):
@@ -315,7 +139,7 @@ def project_record(state, secrets):
                     validate_omitted(item, pointer(path, key), depth + 1)
                     redactions.append({"pointer": path, "reason": "explicit-sensitive-value", "scope": "property-name"})
                     continue
-                result[key] = visit(item, pointer(path, key), depth + 1, base_scheme=base_scheme)
+                result[key] = visit(item, pointer(path, key), depth + 1)
             return result
         raise CaptureFailure("decoder", "Native parser returned an unexpected value type: " + type(value).__name__ + ".", path)
 

bridge/mitmproxy/test_capture.py

@@ -1,265 +0,0 @@
-"""Source-owned tests for the mitmproxy adapter's record projection."""
-
-import importlib.util
-import os
-import sys
-import types
-import unittest
-from unittest import mock
-
-
-def load_capture():
-    """Load the adapter with fresh mitmproxy stand-ins scoped to its import."""
-    fake_mitmproxy = types.ModuleType("mitmproxy")
-    fake_mitmproxy.ctx = types.SimpleNamespace()
-    fake_mitmproxy.version = types.SimpleNamespace(VERSION="12.2.3")
-    fake_io = types.ModuleType("mitmproxy.io")
-    fake_io.tnetstring = types.ModuleType("mitmproxy.io.tnetstring")
-    stand_ins = {
-        "mitmproxy": fake_mitmproxy,
-        "mitmproxy.io": fake_io,
-        "mitmproxy.io.tnetstring": fake_io.tnetstring,
-    }
-    spec = importlib.util.spec_from_file_location(
-        "rea_mitmproxy_capture", os.path.join(os.path.dirname(__file__), "capture.py")
-    )
-    module = importlib.util.module_from_spec(spec)
-    with mock.patch.dict(sys.modules, stand_ins):
-        spec.loader.exec_module(module)
-    return module
-
-
-capture = load_capture()
-
-
-def location(value, scheme=None):
-    state = {"response": {"headers": [[b"Location", value]]}}
-    if scheme is not None:
-        state["request"] = {"scheme": scheme}
-    record = capture.project_record(state, [])
-    sidecar = next(
-        field for field in record["binary_fields"] if field["pointer"] == "/response/headers/0/1"
-    )
-    return record["reported"]["response"]["headers"][0][1], sidecar, record["redactions"]
-
-
-class TransportUserinfoTests(unittest.TestCase):
-    def test_ignorable_controls_cannot_hide_authority_credentials(self):
-        for control in [b"\t", b"\n", b"\r"]:
-            for value in [b"https://" + control + b"/user:pass@host/path", b"ht" + control + b"tps://user:" + control + b"pass@host/path"]:
-                with self.subTest(value=value):
-                    text, sidecar, redactions = location(value, b"https")
-                    self.assertNotIn("user", text)
-                    self.assertNotIn("pass", text)
-                    self.assertEqual(sidecar["state"], "redacted")
-                    self.assertEqual(len(redactions), 1)
-
-    def test_mixed_network_separators_remove_credentials(self):
-        for prefix in [b"\\\\", b"/\\", b"\\/"]:
-            with self.subTest(prefix=prefix):
-                text, sidecar, redactions = location(prefix + b"user:pass@host/path", b"https")
-                self.assertEqual(text, prefix.decode("ascii") + "host/path")
-                self.assertEqual(sidecar["state"], "redacted")
-                self.assertEqual(len(redactions), 1)
-
-    def test_non_special_base_keeps_backslashes_inside_network_authorities(self):
-        text, sidecar, redactions = location(b"//user\\name:pass@host/x", b"foo")
-        self.assertEqual(text, "//host/x")
-        self.assertEqual(sidecar["state"], "redacted")
-        self.assertEqual(len(redactions), 1)
-        text, sidecar, redactions = location(b"/\\invoice@customer", b"foo")
-        self.assertEqual(text, "/\\invoice@customer")
-        self.assertEqual(sidecar["state"], "retained")
-        self.assertEqual(redactions, [])
-
-    def test_native_request_paths_preserve_origin_form_and_redact_absolute_form(self):
-        for value in [b"/\\invoice@customer", b"//invoice@customer", b"\\\\invoice@customer"]:
-            with self.subTest(value=value):
-                record = capture.project_record({"request": {"path": value}}, [])
-                self.assertEqual(record["reported"]["request"]["path"], value.decode("ascii"))
-                self.assertEqual(record["binary_fields"][0]["state"], "retained")
-                self.assertEqual(record["redactions"], [])
-        record = capture.project_record({"request": {"path": b"https://user:pass@host/x"}}, [])
-        self.assertEqual(record["reported"]["request"]["path"], "https://host/x")
-        self.assertEqual(record["binary_fields"][0]["state"], "redacted")
-
-    def test_same_scheme_locations_preserve_relative_path_text_and_bytes(self):
-        for value in [b"https:invoice@customer", b"https:/invoice@customer", b"https:\\invoice@customer"]:
-            with self.subTest(value=value):
-                text, sidecar, redactions = location(value, b"https")
-                self.assertEqual(text, value.decode("ascii"))
-                self.assertEqual(sidecar["state"], "retained")
-                self.assertEqual(redactions, [])
-
-    def test_location_authorities_still_remove_credentials_with_a_base_scheme(self):
-        for value, scheme, expected in [
-            (b"https://user:pass@host/path", b"https", "https://host/path"),
-            (b"https:\\\\user:pass@host/path", b"https", "https:\\\\host/path"),
-            (b"https:user:pass@host/path", b"http", "https:host/path"),
-        ]:
-            with self.subTest(value=value, scheme=scheme):
-                text, sidecar, redactions = location(value, scheme)
-                self.assertEqual(text, expected)
-                self.assertEqual(sidecar["state"], "redacted")
-                self.assertEqual(len(redactions), 1)
-
-    def test_backup_location_uses_its_own_request_scheme(self):
-        record = capture.project_record({
-            "request": {"scheme": b"http"},
-            "backup": {
-                "request": {"scheme": b"https"},
-                "response": {"headers": [[b"Location", b"https:invoice@customer"]]},
-            },
-        }, [])
-        self.assertEqual(record["reported"]["backup"]["response"]["headers"][0][1], "https:invoice@customer")
-        self.assertEqual(record["redactions"], [])
-
-    def test_backslash_ends_a_special_scheme_authority(self):
-        text, sidecar, redactions = location(b"https://example.test\\part@tail")
-        self.assertEqual(text, "https://example.test\\part@tail")
-        self.assertEqual(sidecar["state"], "retained")
-        self.assertIsNotNone(sidecar["content_base64"])
-        self.assertEqual(redactions, [])
-
-    def test_userinfo_before_a_backslash_is_still_removed(self):
-        text, sidecar, redactions = location(b"https://user:pw@example.test\\path")
-        self.assertEqual(text, "https://example.test\\path")
-        self.assertEqual(sidecar["state"], "redacted")
-        self.assertEqual(
-            redactions,
-            [{"pointer": "/response/headers/0/1", "reason": "transport-credential"}],
-        )
-
-    def test_ordinary_userinfo_is_removed(self):
-        text, _sidecar, _redactions = location(b"https://user:pw@example.test/a@b")
-        self.assertEqual(text, "https://example.test/a@b")
-
-    def test_empty_userinfo_marker_is_removed(self):
-        self.assertEqual(
-            capture.without_userinfo("https://@host"), "https://host"
-        )
-
-    def test_special_schemes_skip_leading_slashes_before_userinfo(self):
-        for value, expected in [
-            (b"https://\\user:pass@host/path", b"https://\\host/path"),
-            (b"https:\\\\user:pass@host/path", b"https:\\\\host/path"),
-            (b"https:user:pass@host", b"https:host"),
-            (b"//\\user:pass@host", b"//\\host"),
-        ]:
-            with self.subTest(value=value):
-                self.assertEqual(capture.without_userinfo(value), expected)
-        text, sidecar, redactions = location(b"https://\\user:pass@host/path")
-        self.assertEqual(text, "https://\\host/path")
-        self.assertEqual(sidecar["state"], "redacted")
-        self.assertEqual(len(redactions), 1)
-
-    def test_file_base_keeps_paths_after_the_fixed_network_boundary(self):
-        for value in [b"///u@h", b"////u@h"]:
-            with self.subTest(value=value):
-                text, sidecar, redactions = location(value, b"file")
-                self.assertEqual(text, value.decode("ascii"))
-                self.assertEqual(sidecar["state"], "retained")
-                self.assertIsNotNone(sidecar["content_base64"])
-                self.assertEqual(redactions, [])
-
-    def test_file_urls_keep_path_text(self):
-        self.assertEqual(capture.without_userinfo("file:///a@b"), "file:///a@b")
-
-    def test_file_urls_reject_userinfo_and_keep_their_source(self):
-        # WHATWG rejects an "@" in a file host, so nothing parses as credentials.
-        self.assertEqual(
-            capture.without_userinfo("file://user:pass@host/x"), "file://user:pass@host/x"
-        )
-        for value in [b"\\\\user:pass@host/x", b"/\\user:pass@host/x", b"//user:pass@host/x"]:
-            with self.subTest(value=value):
-                text, sidecar, redactions = location(value, b"file")
-                self.assertEqual(text, value.decode("ascii"))
-                self.assertEqual(sidecar["state"], "retained")
-                self.assertEqual(redactions, [])
-
-    def test_rejected_special_hosts_keep_their_source(self):
-        # A rejected host or port fails the whole URL, so it has no userinfo.
-        for value in [
-            "https:user@%",
-            "https://user@",
-            "https://user:pass@h^st/x",
-            "https://user@ho st/x",
-            "https://user@host:99999/x",
-            "https://user@host:12a",
-            "https://user@[::1",
-        ]:
-            with self.subTest(value=value):
-                self.assertEqual(capture.without_userinfo(value), value)
-        text, sidecar, redactions = location(b"https://user:pass@h^st/x", b"https")
-        self.assertEqual(text, "https://user:pass@h^st/x")
-        self.assertEqual(sidecar["state"], "retained")
-        self.assertEqual(redactions, [])
-
-    def test_accepted_special_hosts_still_remove_userinfo(self):
-        for value, expected in [
-            ("https:user@%41", "https:%41"),
-            ("https://user@[::1]:8443/x", "https://[::1]:8443/x"),
-            ("https://user@host:/x", "https://host:/x"),
-            ("wss://user:pass@host:65535", "wss://host:65535"),
-            ("https://user@0x7f.1/", "https://0x7f.1/"),
-            ("https://user@1.2.3.4./", "https://1.2.3.4./"),
-            ("https://user@4294967295/", "https://4294967295/"),
-            ("https://user@1.2.3.08a/", "https://1.2.3.08a/"),
-            ("https://user@[::ffff:1.2.3.4]/", "https://[::ffff:1.2.3.4]/"),
-        ]:
-            with self.subTest(value=value):
-                self.assertEqual(capture.without_userinfo(value), expected)
-
-    def test_unicode_hosts_that_may_map_to_accepted_hosts_remove_userinfo(self):
-        # UTS #46 maps these to 1.2.3.4; mapping is not modeled, so redact.
-        for host in ["%EF%BC%91.2.3.4", "1。2.3.4", "%C2%AD1.2.3.4", "１.2.3.4"]:
-            with self.subTest(host=host):
-                self.assertEqual(
-                    capture.without_userinfo(f"https://user:pw@{host}/"), f"https://{host}/"
-                )
-        text, sidecar, redactions = location(b"https://user:pw@%EF%BC%91.2.3.4/", b"https")
-        self.assertEqual(text, "https://%EF%BC%91.2.3.4/")
-        self.assertEqual(sidecar["state"], "redacted")
-        self.assertEqual(len(redactions), 1)
-        # ASCII rejections still hold for non-ASCII hosts.
-        self.assertEqual(capture.without_userinfo("https://user@１^/"), "https://user@１^/")
-
-    def test_trailing_controls_and_spaces_do_not_hide_userinfo(self):
-        # WHATWG strips trailing C0 controls and spaces before parsing.
-        for suffix in [b" ", b"\x01", b"\x00 \x1f"]:
-            with self.subTest(suffix=suffix):
-                value = b"https://user:pw@example.test" + suffix
-                text, sidecar, redactions = location(value, b"https")
-                self.assertEqual(text, "https://example.test" + suffix.decode("latin-1"))
-                self.assertEqual(sidecar["state"], "redacted")
-                self.assertEqual(len(redactions), 1)
-
-    def test_rejected_ip_literals_keep_their_source(self):
-        for value in [
-            "https://user:pass@256.256.256.256/path",
-            "https://user@1.2.3.4.5/",
-            "https://user@1.2.3.09/",
-            "https://user@4294967296/",
-            "https://user@a.0x/",
-            "https://user@1..2/",
-            "https://user@1." + "9" * 5000 + "/",
-            "https://user@[1::2::3]/",
-            "https://user@[::1%25eth0]/",
-        ]:
-            with self.subTest(value=value[:40]):
-                self.assertEqual(capture.without_userinfo(value), value)
-
-    def test_overlong_ports_are_compared_without_numeric_overflow(self):
-        # Python 3.11+ refuses int() on decimal strings over 4300 digits.
-        accepted = "https://user@host:" + "0" * 5000 + "80/x"
-        self.assertEqual(capture.without_userinfo(accepted), "https://host:" + "0" * 5000 + "80/x")
-        rejected = "https://user@host:" + "9" * 5000 + "/x"
-        self.assertEqual(capture.without_userinfo(rejected), rejected)
-
-    def test_non_special_schemes_keep_backslashes_in_the_authority(self):
-        self.assertEqual(capture.without_userinfo("foo://a\\b@host/x"), "foo://host/x")
-        self.assertEqual(capture.without_userinfo(b"//a\\b@host"), b"//a\\b@host")
-
-
-if __name__ == "__main__":
-    unittest.main()

bridge/native/rea_lldb_tracer.py

@@ -555,38 +555,6 @@ def _failed_launch_description(process):
     return None
 
 
-def _retire_failed_launch(process, config, listener, stdout, stderr):
-    """Reconcile an SBProcess returned alongside a failed Launch error."""
-    if not process.IsValid():
-        stdout.close()
-        stderr.close()
-        return False
-
-    pid = process.GetProcessID()
-    if pid > 0:
-        # Even an already-exited process needs its PID published so the host
-        # can distinguish a completed launch failure from an unknown target.
-        with open(config["pid_path"], "w") as handle:
-            handle.write(str(pid))
-
-    if process.GetState() != lldb.eStateExited:
-        stdout.mark_launched()
-        stderr.mark_launched()
-        if pid > 0:
-            # Hold a surviving target until the host has captured its start
-            # identity. If that proof is unavailable, Kill still addresses
-            # this exact SBProcess created by the current launch request.
-            _wait_for_identity_ack(config)
-        process.Kill()
-        _wait_for_exit(listener, process, 5)
-
-    exit_observed = process.GetState() == lldb.eStateExited
-    expected_exit = exit_observed
-    stdout.close(expected_exit=expected_exit)
-    stderr.close(expected_exit=expected_exit)
-    return exit_observed
-
-
 def trace(debugger, config):
     global _TRACE_CONTEXT
     debugger.SetAsync(True)
@@ -599,27 +567,18 @@ def trace(debugger, config):
         before_digest = _hash_file(config["executable"])
         before_identity = _file_identity(config["executable"])
     except OSError as error:
-        return {
-            "status": "target-integrity-error",
-            "error": str(error),
-            "target_process_created": False,
-        }
+        return {"status": "target-integrity-error", "error": str(error)}
     if before_digest != config["expected_sha256"]:
         return {
             "status": "target-integrity-error",
             "error": "selected executable digest changed before LLDB target creation",
-            "target_process_created": False,
         }
     error = lldb.SBError()
     target = debugger.CreateTarget(
         config["executable"], config["architecture"], None, False, error
     )
     if not target.IsValid():
-        return {
-            "status": "target-error",
-            "error": error.GetCString(),
-            "target_process_created": False,
-        }
+        return {"status": "target-error", "error": error.GetCString()}
     module_path_before, module_file_identity_before, module_uuid_before = (
         _module_identity(target)
     )
@@ -630,7 +589,6 @@ def trace(debugger, config):
         return {
             "status": "target-integrity-error",
             "error": "LLDB executable module resolved to a different pre-launch file identity",
-            "target_process_created": False,
         }
     created = [_create_breakpoints(target, spec) for spec in config["breakpoints"]]
     breakpoint_index = {}
@@ -662,38 +620,14 @@ def trace(debugger, config):
             )
         process = target.Launch(_launch_info(target, config, listener), error)
         if not error.Success() or not process.IsValid():
-            exit_observed = _retire_failed_launch(
-                process, config, listener, stdout, stderr
-            )
-            return {
-                "status": "launch-error",
-                "error": error.GetCString(),
-                **(
-                    {"target_process_created": True}
-                    if process.IsValid()
-                    else {}
-                ),
-                **(
-                    {"target_process_exit_observed": True}
-                    if exit_observed
-                    else {}
-                ),
-            }
+            stdout.close()
+            stderr.close()
+            return {"status": "launch-error", "error": error.GetCString()}
         launch_failure = _failed_launch_description(process)
         if launch_failure is not None:
-            exit_observed = _retire_failed_launch(
-                process, config, listener, stdout, stderr
-            )
-            return {
-                "status": "launch-error",
-                "error": launch_failure,
-                "target_process_created": True,
-                **(
-                    {"target_process_exit_observed": True}
-                    if exit_observed
-                    else {}
-                ),
-            }
+            stdout.close(expected_exit=True)
+            stderr.close(expected_exit=True)
+            return {"status": "launch-error", "error": launch_failure}
         stdout.mark_launched()
         stderr.mark_launched()
         # Publish the PID before any post-launch file or module inspection. The
@@ -710,7 +644,6 @@ def trace(debugger, config):
             return {
                 "status": "target-identity-unavailable",
                 "error": "host could not establish the launched process identity; target was stopped",
-                "target_process_created": True,
             }
         try:
             after_digest = _hash_file(config["executable"])
@@ -719,11 +652,7 @@ def trace(debugger, config):
             process.Kill()
             stdout.close(expected_exit=process.GetState() == lldb.eStateExited)
             stderr.close(expected_exit=process.GetState() == lldb.eStateExited)
-            return {
-                "status": "target-integrity-error",
-                "error": str(identity_error),
-                "target_process_created": True,
-            }
+            return {"status": "target-integrity-error", "error": str(identity_error)}
         if after_digest != config["expected_sha256"] or after_identity != before_identity:
             process.Kill()
             _wait_for_exit(listener, process, 5)
@@ -732,7 +661,6 @@ def trace(debugger, config):
             return {
                 "status": "target-integrity-error",
                 "error": "selected executable digest or file identity changed during LLDB launch",
-                "target_process_created": True,
             }
         module_path_after, module_file_identity_after, module_uuid_after = (
             _module_identity(target)
@@ -748,7 +676,6 @@ def trace(debugger, config):
             return {
                 "status": "target-integrity-error",
                 "error": "LLDB executable module resolved to a different file identity",
-                "target_process_created": True,
             }
         if (
             module_uuid_before is not None
@@ -762,7 +689,6 @@ def trace(debugger, config):
             return {
                 "status": "target-integrity-error",
                 "error": "LLDB executable module identity changed during launch",
-                "target_process_created": True,
             }
         context = {
             "target": target,
@@ -822,11 +748,7 @@ def trace(debugger, config):
         # exit code; preserve the debugger's concrete launch denial.
         launch_failure = _failed_launch_description(process)
         if launch_failure is not None:
-            return {
-                "status": "launch-error",
-                "error": launch_failure,
-                "target_process_created": True,
-            }
+            return {"status": "launch-error", "error": launch_failure}
         launch_identity_stable = (
             module_path_before is not None
             and module_path_after == module_path_before

bridge/native/test_rea_lldb_tracer.py

@@ -8,15 +8,12 @@ import sys
 import tempfile
 import types
 import unittest
-from unittest.mock import patch
 
 
 fake_lldb = sys.modules.setdefault("lldb", types.ModuleType("lldb"))
 fake_lldb.LLDB_INVALID_ADDRESS = -1
 fake_lldb.eLaunchFlagDebug = 2
 fake_lldb.eLaunchFlagStopAtEntry = 4
-fake_lldb.eStateExited = 10
-fake_lldb.SBEvent = lambda: object()
 spec = importlib.util.spec_from_file_location(
     "rea_lldb_tracer", os.path.join(os.path.dirname(__file__), "rea_lldb_tracer.py")
 )
@@ -25,172 +22,6 @@ spec.loader.exec_module(tracer)
 
 
 class NativeTraceBudgetTests(unittest.TestCase):
-    def test_failed_launch_does_not_infer_exit_from_a_failed_kill(self):
-        class Process:
-            def IsValid(self):
-                return True
-
-            def GetProcessID(self):
-                return 12345
-
-            def GetState(self):
-                return 6
-
-            def Kill(self):
-                return None
-
-        class Sink:
-            close_exit = None
-
-            def mark_launched(self):
-                pass
-
-            def close(self, expected_exit=False):
-                self.close_exit = expected_exit
-
-        with tempfile.TemporaryDirectory() as directory:
-            stdout, stderr = Sink(), Sink()
-            with patch.object(tracer, "_wait_for_identity_ack", return_value="unavailable"), patch.object(
-                tracer, "_wait_for_exit", return_value=None
-            ):
-                exited = tracer._retire_failed_launch(
-                    Process(), {"pid_path": os.path.join(directory, "pid")}, object(), stdout, stderr
-                )
-        self.assertFalse(exited)
-        self.assertFalse(stdout.close_exit)
-        self.assertFalse(stderr.close_exit)
-
-    def test_failed_launch_publishes_pid_and_retires_live_process(self):
-        class Process:
-            state = 6
-            killed = False
-
-            def IsValid(self):
-                return True
-
-            def GetProcessID(self):
-                return 12345
-
-            def GetState(self):
-                return self.state
-
-            def Kill(self):
-                self.killed = True
-                self.state = tracer.lldb.eStateExited
-
-        class Sink:
-            launched = False
-            close_exit = None
-
-            def mark_launched(self):
-                self.launched = True
-
-            def close(self, expected_exit=False):
-                self.close_exit = expected_exit
-
-        with tempfile.TemporaryDirectory() as directory:
-            pid_path = os.path.join(directory, "pid")
-            process = Process()
-            stdout, stderr = Sink(), Sink()
-
-            def acknowledge(config):
-                with open(config["pid_path"], "r") as pid_file:
-                    self.assertEqual(pid_file.read(), "12345")
-                return "readable"
-
-            with patch.object(tracer, "_wait_for_identity_ack", acknowledge):
-                exited = tracer._retire_failed_launch(
-                    process,
-                    {"pid_path": pid_path},
-                    object(),
-                    stdout,
-                    stderr,
-                )
-
-        self.assertTrue(exited)
-        self.assertTrue(process.killed)
-        self.assertTrue(stdout.launched)
-        self.assertTrue(stderr.launched)
-        self.assertTrue(stdout.close_exit)
-        self.assertTrue(stderr.close_exit)
-
-    def test_failed_launch_records_when_valid_process_is_already_exited(self):
-        class Process:
-            def IsValid(self):
-                return True
-
-            def GetProcessID(self):
-                return 12345
-
-            def GetState(self):
-                return tracer.lldb.eStateExited
-
-            def Kill(self):
-                raise AssertionError("an exited process must not be killed")
-
-        class Sink:
-            close_exit = None
-
-            def mark_launched(self):
-                raise AssertionError("an exited process has no output to drain")
-
-            def close(self, expected_exit=False):
-                self.close_exit = expected_exit
-
-        with tempfile.TemporaryDirectory() as directory:
-            pid_path = os.path.join(directory, "pid")
-            stdout, stderr = Sink(), Sink()
-            with patch.object(
-                tracer,
-                "_wait_for_identity_ack",
-                side_effect=AssertionError("exit is already observed"),
-            ):
-                exited = tracer._retire_failed_launch(
-                    Process(), {"pid_path": pid_path}, object(), stdout, stderr
-                )
-            with open(pid_path, "r") as pid_file:
-                self.assertEqual(pid_file.read(), "12345")
-
-        self.assertTrue(exited)
-        self.assertTrue(stdout.close_exit)
-        self.assertTrue(stderr.close_exit)
-
-    def test_pre_target_integrity_failure_reports_no_process_created(self):
-        original_debugger = getattr(tracer.lldb, "SBDebugger", None)
-
-        class DebuggerApi:
-            @staticmethod
-            def SetInternalVariable(*_arguments):
-                return None
-
-        class Debugger:
-            def SetAsync(self, _enabled):
-                return None
-
-            def GetInstanceName(self):
-                return "fixture"
-
-            def CreateTarget(self, *_arguments):
-                raise AssertionError("integrity failure precedes target creation")
-
-        tracer.lldb.SBDebugger = DebuggerApi
-        try:
-            with patch.object(tracer, "_hash_file", return_value="changed"), patch.object(
-                tracer, "_file_identity", return_value=(1, 2)
-            ):
-                result = tracer.trace(
-                    Debugger(),
-                    {"executable": "fixture", "expected_sha256": "expected"},
-                )
-        finally:
-            if original_debugger is None:
-                del tracer.lldb.SBDebugger
-            else:
-                tracer.lldb.SBDebugger = original_debugger
-
-        self.assertEqual(result["status"], "target-integrity-error")
-        self.assertIs(result["target_process_created"], False)
-
     def test_journal_checks_exact_byte_budget_before_writing(self):
         record = {"kind": "other-stop", "reason": "signal"}
         encoded_size = len((tracer.json.dumps(record) + "\n").encode("utf-8"))

bridge/process/ProcessRunTokenReader.swift

@@ -12,29 +12,16 @@ struct ProcessIdentityObservation: Encodable {
   let pid: Int32
   let state: String
   let identity: String?
-  let effective_uid: UInt32?
-  let lifecycle: String?
-  let relation: ProcessRelationObservation?
   let reason: String?
 }
 
-struct ProcessRelationObservation: Encodable {
-  let state: String
-  let parent_pid: Int32
-  let process_group_id: Int32
-}
-
-struct ProcessMetadata {
+private struct ProcessMetadata {
   let identity: String
-  let effectiveUid: UInt32
-  let lifecycle: String
-  let parentPid: Int32
-  let processGroupId: Int32
   let pointerSize: Int
 }
 
 struct ProcessSnapshot {
-  let metadata: [Int32: ProcessMetadata]
+  fileprivate let metadata: [Int32: ProcessMetadata]
   let failure: String?
 }
 
@@ -88,10 +75,6 @@ func readProcessSnapshot(
           process.kp_proc.p_pid,
           ProcessMetadata(
             identity: "\(start.tv_sec):\(start.tv_usec)",
-            effectiveUid: process.kp_eproc.e_ucred.cr_uid,
-            lifecycle: process.kp_proc.p_stat == SZOMB ? "zombie" : "non-zombie",
-            parentPid: process.kp_eproc.e_ppid,
-            processGroupId: process.kp_eproc.e_pgid,
             pointerSize: process.kp_proc.p_flag & P_LP64 != 0 ? 8 : 4
           )
         )
@@ -104,61 +87,20 @@ func readProcessSnapshot(
 }
 
 func readProcessIdentities(pids: [Int32]) -> [ProcessIdentityObservation] {
-  readProcessIdentities(pids: pids, snapshot: readProcessSnapshot())
-}
-
-func readProcessIdentities(
-  pids: [Int32],
-  snapshot: ProcessSnapshot
-) -> [ProcessIdentityObservation] {
+  let snapshot = readProcessSnapshot()
   return pids.map { pid in
-    guard pid > 0 else {
-      return unavailableIdentity(pid: pid, reason: "invalid_process_id")
-    }
     guard let metadata = snapshot.metadata[pid] else {
-      if let failure = snapshot.failure {
-        return unavailableIdentity(pid: pid, reason: failure)
-      }
-      // This records absence from this successful KERN_PROC_ALL snapshot only.
-      // Unlike the Linux procfs path, it has no PID-specific kill(0)
-      // corroboration; callers must not treat it as universal or future exit
-      // proof.
-      return ProcessIdentityObservation(
+      return unavailableIdentity(
         pid: pid,
-        state: "absent",
-        identity: nil,
-        effective_uid: nil,
-        lifecycle: nil,
-        relation: nil,
-        reason: "not-in-snapshot"
+        reason: snapshot.failure ?? "process_not_in_snapshot"
       )
     }
-    return ProcessIdentityObservation(
-      pid: pid,
-      state: "readable",
-      identity: metadata.identity,
-      effective_uid: metadata.effectiveUid,
-      lifecycle: metadata.lifecycle,
-      relation: ProcessRelationObservation(
-        state: "observed",
-        parent_pid: metadata.parentPid,
-        process_group_id: metadata.processGroupId
-      ),
-      reason: nil
-    )
+    return ProcessIdentityObservation(pid: pid, state: "readable", identity: metadata.identity, reason: nil)
   }
 }
 
 private func unavailableIdentity(pid: Int32, reason: String) -> ProcessIdentityObservation {
-  ProcessIdentityObservation(
-    pid: pid,
-    state: "unavailable",
-    identity: nil,
-    effective_uid: nil,
-    lifecycle: nil,
-    relation: nil,
-    reason: reason
-  )
+  ProcessIdentityObservation(pid: pid, state: "unavailable", identity: nil, reason: reason)
 }
 
 enum RunTokenReadError: Error {

bridge/pwndbg/core_context.py

@@ -20,9 +20,8 @@ def inspect(request):
     root = Path(os.environ["REA_CORE_CONTEXT_REQUEST"]).parent
     empty = root / "no-libraries"
     empty.mkdir(mode=0o700)
-    for command in ["set auto-load off", "set debuginfod enabled off", "set auto-solib-add off", "set history save off", "set pagination off", "set target-file-system-kind unix",
-                    "set sysroot ./no-libraries", "set solib-search-path ./no-libraries",
-                    "set debug-file-directory ./no-libraries"]:
+    for command in ["set auto-load off", "set debuginfod enabled off", "set auto-solib-add off", "set history save off", "set pagination off",
+                    "set sysroot ./no-libraries", "set solib-search-path ./no-libraries"]:
         gdb.execute(command, to_string=True)
     entry = request["gdbinit"]
     try:
@@ -39,19 +38,7 @@ def inspect(request):
     # relative filename in the owned cwd so no selected path becomes GDB syntax.
     if Path(request["snapshot_path"]) != root.parent / "object.snapshot":
         raise ContextFailure("decoder", "Core context request did not select the shared owned snapshot.")
-    # GDB 16 searches AT_EXECFN/NT_FILE outside sysroot when no executable BFD
-    # is selected. Occupy that slot with the already running, owned debugger;
-    # exec-file loads no symbols and never runs it. Clear it before any query.
-    # /proc/self/exe identifies this process, not the core's historical PID.
-    architecture = {"x86_64-little-endian": "i386:x86-64", "aarch64-little-endian": "aarch64"}.get(request["architecture"])
-    if architecture is None:
-        raise ContextFailure("unsupported", "Unsupported recorded core architecture.")
-    gdb.execute("exec-file /proc/self/exe", to_string=True)
-    # The placeholder must not select the core's architecture. Reuse the
-    # decoder's validated profile, including for cross-architecture GDB builds.
-    gdb.execute("set architecture " + architecture, to_string=True)
     gdb.execute("core-file ../object.snapshot", to_string=True)
-    gdb.execute("file", to_string=True)
     inferior = gdb.selected_inferior()
     if inferior.connection is None or inferior.connection.type != "core" or gdb.current_progspace().filename is not None:
         raise ContextFailure("decoder", "Requested core-only boundary was not established; no mapping query performed.")
@@ -95,7 +82,7 @@ def main():
     try:
         encoded = json.dumps(reply, ensure_ascii=True, allow_nan=False).encode("utf-8")
         if len(encoded) > OUTPUT_BYTES:
-            encoded = json.dumps({"ok": False, "reason": "output-limit", "message": "Complete debugger context exceeds the 64 MiB reply budget."}).encode("utf-8")
+            encoded = json.dumps({"ok": False, "reason": "output-limit", "message": "Complete debugger context exceeds64 MiB reply budget."}).encode("utf-8")
         descriptor = os.open(request["reply_path"], os.O_WRONLY | os.O_CREAT | os.O_EXCL, 0o600)
         with os.fdopen(descriptor, "wb") as handle:
             handle.write(encoded)

bridge/pwndbg/test_core_context.py

@@ -1,126 +0,0 @@
-"""Producer regressions with controlled GDB state, not native debugger qualification."""
-import json
-import os
-from pathlib import Path
-import runpy
-import sys
-import tempfile
-import types
-import unittest
-from unittest.mock import patch
-
-
-BRIDGE = Path(__file__).with_name("core_context.py")
-
-
-class CoreContextTests(unittest.TestCase):
-    def inspect(self, failure=None, connection="core", symbols=None, architecture="x86_64-little-endian", objfile="recorded-executable"):
-        commands, reads, queries = [], [], []
-        state = {"executable": None, "symbols": None, "connection": None}
-        gdb = types.ModuleType("gdb")
-        gdb.VERSION = "16.3"
-        gdb.selected_inferior = lambda: types.SimpleNamespace(
-            connection=state["connection"], pid=123)
-        gdb.current_progspace = lambda: types.SimpleNamespace(filename=state["symbols"])
-
-        def execute(command, to_string):
-            self.assertTrue(to_string)
-            commands.append(command)
-            if command == failure:
-                raise RuntimeError("controlled command failure")
-            if command == "exec-file /proc/self/exe":
-                state["executable"] = "/proc/self/exe"
-            elif command == "core-file ../object.snapshot":
-                if state["executable"] is None:
-                    reads.append("recorded-executable")
-                    state["executable"] = state["symbols"] = "recorded-executable"
-                state["connection"] = types.SimpleNamespace(type=connection)
-            elif command == "file":
-                state["executable"] = None
-                state["symbols"] = symbols
-
-        gdb.execute = execute
-        pwndbg = types.ModuleType("pwndbg")
-        pwndbg.aglib = types.ModuleType("pwndbg.aglib")
-        pwndbg.aglib.vmmap = types.ModuleType("pwndbg.aglib.vmmap")
-        pwndbg.lib = types.ModuleType("pwndbg.lib")
-        pwndbg.lib.version = types.ModuleType("pwndbg.lib.version")
-        pwndbg.lib.version.__version__ = "2026.09.15"
-
-        def maps():
-            self.assertIsNone(state["executable"], "Helper executable must be discarded before mapping queries")
-            queries.append("maps")
-            return [types.SimpleNamespace(start=4096, end=8192, offset=0, flags=5, objfile=objfile)]
-
-        pwndbg.aglib.vmmap.get = maps
-        modules = {module.__name__: module for module in [
-            gdb, pwndbg, pwndbg.aglib, pwndbg.aglib.vmmap, pwndbg.lib, pwndbg.lib.version]}
-        with tempfile.TemporaryDirectory() as directory:
-            root = Path(directory)
-            stage = root / "debugger"
-            stage.mkdir()
-            plugin = root / "gdbinit.py"
-            plugin.write_text("")
-            request = stage / "request.json"
-            reply = stage / "reply.json"
-            request.write_text(json.dumps({"gdbinit": str(plugin), "architecture": architecture, "snapshot_path": str(root / "object.snapshot"), "reply_path": str(reply)}))
-            with patch.dict(sys.modules, modules), patch.dict(os.environ, REA_CORE_CONTEXT_REQUEST=str(request)):
-                runpy.run_path(str(BRIDGE))
-            result = json.loads(reply.read_text())
-        return result, commands, reads, queries
-
-    def test_core_load_never_opens_recorded_executable_and_queries_only_after_discard(self):
-        result, commands, reads, queries = self.inspect()
-        self.assertTrue(result["ok"], result)
-        self.assertEqual(reads, [])
-        self.assertEqual(queries, ["maps"])
-        self.assertEqual(commands[-4:], ["exec-file /proc/self/exe", "set architecture i386:x86-64", "core-file ../object.snapshot", "file"])
-        self.assertLess(commands.index("set debug-file-directory ./no-libraries"), commands.index("core-file ../object.snapshot"))
-        self.assertIsNone(result["value"]["executable"])
-        self.assertEqual(result["value"]["maps"][0]["current_file_identity"], "unknown")
-
-    def test_failed_guard_core_load_or_discard_never_queries_mappings(self):
-        for command in ["exec-file /proc/self/exe", "set architecture i386:x86-64", "core-file ../object.snapshot", "file"]:
-            with self.subTest(command=command):
-                result, commands, reads, queries = self.inspect(failure=command)
-                self.assertFalse(result["ok"])
-                self.assertEqual(reads, [])
-                self.assertEqual(queries, [])
-                if command in ["exec-file /proc/self/exe", "set architecture i386:x86-64"]:
-                    self.assertNotIn("core-file ../object.snapshot", commands)
-
-    def test_cross_architecture_uses_the_validated_decoder_profile(self):
-        result, commands, reads, queries = self.inspect(architecture="aarch64-little-endian")
-        self.assertTrue(result["ok"], result)
-        self.assertEqual(reads, [])
-        self.assertEqual(queries, ["maps"])
-        self.assertLess(commands.index("set architecture aarch64"), commands.index("core-file ../object.snapshot"))
-
-    def test_unknown_architecture_refuses_before_loading_core(self):
-        result, commands, reads, queries = self.inspect(architecture="unknown")
-        self.assertFalse(result["ok"])
-        self.assertEqual(result["reason"], "unsupported")
-        self.assertNotIn("core-file ../object.snapshot", commands)
-        self.assertEqual(reads, [])
-        self.assertEqual(queries, [])
-
-    def test_output_limit_message_separates_the_words_and_names_the_limit(self):
-        result, _, reads, queries = self.inspect(objfile="m" * (64 * 1024 * 1024))
-        self.assertFalse(result["ok"])
-        self.assertEqual(result["reason"], "output-limit")
-        self.assertNotIn("exceeds64", result["message"])
-        self.assertEqual(result["message"], "Complete debugger context exceeds the 64 MiB reply budget.")
-        self.assertEqual(reads, [])
-        self.assertEqual(queries, ["maps"])
-
-    def test_wrong_connection_or_remaining_symbols_never_queries_mappings(self):
-        for options in [{"connection": "native"}, {"symbols": "unexpected-symbols"}]:
-            with self.subTest(options=options):
-                result, _, reads, queries = self.inspect(**options)
-                self.assertFalse(result["ok"])
-                self.assertEqual(reads, [])
-                self.assertEqual(queries, [])
-
-
-if __name__ == "__main__":
-    unittest.main()

docs/.vitepress/config.ts

@@ -1,4 +1,18 @@
 import { defineConfig } from "vitepress";
+import { dirname, relative, resolve, sep } from "node:path";
+import { fileURLToPath } from "node:url";
+import {
+  documentationRewrites,
+  documentationSections,
+} from "./documentation.js";
+
+const documentationRoot = fileURLToPath(new URL("..", import.meta.url));
+const rewrites: Record<string, string> = {
+  ...documentationRewrites,
+  "README.md": "documentation.md",
+  "specs/README.md": "specs/index.md",
+  "adr/README.md": "adr/index.md",
+};
 
 export default defineConfig({
   title: "REA",
@@ -6,87 +20,92 @@ export default defineConfig({
     "Reverse engineer binaries, applications, and runtime behavior with one CLI and MCP server.",
   lang: "en-US",
   base: "/rea/",
+  rewrites,
+  markdown: {
+    config(md) {
+      // Repository links resolve from their physical source. Render them from
+      // the stable public route instead, including links across categories.
+      md.core.ruler.after("inline", "documentation-source-links", (state) => {
+        const physicalPath =
+          state.env.realPath ??
+          (state.env.relativePath
+            ? resolve(documentationRoot, state.env.relativePath)
+            : null);
+        if (physicalPath === null) return;
+        const renderedPath =
+          state.env.path ??
+          resolve(
+            documentationRoot,
+            rewrites[state.env.relativePath] ?? state.env.relativePath,
+          );
+        for (const block of state.tokens) {
+          for (const token of block.children ?? []) {
+            const attribute =
+              token.type === "link_open"
+                ? "href"
+                : token.type === "image"
+                  ? "src"
+                  : null;
+            if (attribute === null) continue;
+            const destination = token.attrGet(attribute);
+            if (
+              !destination ||
+              /^(?:[a-z][a-z\d+.-]*:|[/#])/iu.test(destination)
+            )
+              continue;
+            const separator = destination.search(/[?#]/u);
+            const path =
+              separator === -1 ? destination : destination.slice(0, separator);
+            const suffix = separator === -1 ? "" : destination.slice(separator);
+            const source = relative(
+              documentationRoot,
+              resolve(dirname(physicalPath), path),
+            )
+              .split(sep)
+              .join("/");
+            const rendered = relative(
+              dirname(renderedPath),
+              resolve(
+                documentationRoot,
+                source.startsWith("public/")
+                  ? source.slice("public/".length)
+                  : (rewrites[source] ?? source),
+              ),
+            )
+              .split(sep)
+              .join("/");
+            token.attrSet(attribute, rendered + suffix);
+          }
+        }
+      });
+    },
+  },
   srcExclude: ["readme/**"],
   themeConfig: {
     nav: [
       { text: "Get started", link: "/installation" },
+      { text: "Documentation", link: "/documentation" },
       { text: "Reference", link: "/mcp-contracts" },
       { text: "Roadmap", link: "/roadmap" },
     ],
     sidebar: [
       {
-        text: "Getting started",
+        text: "Documentation directory",
         items: [
-          { text: "Installation and setup", link: "/installation" },
-          { text: "Client configuration", link: "/client-configuration" },
-          { text: "CLI and Evidence", link: "/cli" },
-          { text: "Agent prompts", link: "/mcp-prompts" },
-          { text: "Roadmap", link: "/roadmap" },
-        ],
-      },
-      {
-        text: "Investigation guides",
-        items: [
-          { text: "Native binaries", link: "/native-investigation" },
-          { text: "Go build metadata", link: "/go-binaries" },
-          { text: "IL2CPP metadata", link: "/il2cpp-metadata" },
-          { text: "Rust dependencies", link: "/rust-binaries" },
-          {
-            text: "JavaScript and Electron",
-            link: "/javascript-artifact-reconstruction",
-          },
-          {
-            text: "JavaScript workflows",
-            link: "/javascript-application-workflows",
-          },
-          { text: "Browser observation", link: "/browser-observation" },
-          {
-            text: "Web network captures",
-            link: "/web-network-captures",
-          },
-          { text: "Agent environments", link: "/agent-environments" },
-          { text: "Electron observation", link: "/electron-observation" },
-          { text: "Electron fuses", link: "/electron-fuses" },
-          { text: "Process capture", link: "/process-capture" },
-          { text: ".NET assemblies", link: "/managed-code-analysis" },
-          { text: "Android applications", link: "/android-analysis" },
-          { text: "Apple applications", link: "/apple-application-analysis" },
-          { text: "Desktop installations", link: "/desktop-applications" },
-          { text: "Firmware", link: "/firmware-analysis" },
-          { text: "SQLite databases", link: "/sqlite-databases" },
-          { text: "Packet captures", link: "/packet-captures" },
-          { text: "Signal recordings", link: "/signal-recordings" },
-        ],
-      },
-      {
-        text: "Provider guides",
-        collapsed: true,
-        items: [
-          { text: "IDA", link: "/ida-provider" },
-          { text: "Kuna", link: "/kuna-provider" },
-          { text: "Ghidra on Windows", link: "/windows-ghidra-p0" },
-          { text: "Ghidra DOS analysis", link: "/ghidra-dos" },
-          { text: "Ghidra raw binary", link: "/raw-binary" },
-          { text: "Ghidra NativeAOT", link: "/ghidra-nativeaot" },
-          { text: "Ghidra PowerPC", link: "/ghidra-ppc" },
-          { text: "Ghidra semantics", link: "/ghidra-provider" },
-        ],
-      },
-      {
-        text: "Reference and development",
-        collapsed: true,
-        items: [
-          { text: "MCP contracts", link: "/mcp-contracts" },
-          { text: "Tool design", link: "/tool-design" },
-          { text: "Testing", link: "/testing" },
-          { text: "Client verification", link: "/client-verification" },
-          {
-            text: "Reconstruction readiness",
-            link: "/reconstruction-readiness",
-          },
-          { text: "Releasing", link: "/releasing" },
+          { text: "All guides", link: "/documentation" },
+          { text: "Authoring conventions", link: "/development/documentation" },
+          { text: "Feature specifications", link: "/specs/" },
+          { text: "Architecture decisions", link: "/adr/" },
         ],
       },
+      ...documentationSections.map((section) => ({
+        text: section.text,
+        collapsed: section.text !== "Getting started",
+        items: section.items.map((item) => ({
+          text: item.text,
+          link: item.route,
+        })),
+      })),
     ],
     search: { provider: "local" },
     socialLinks: [

docs/.vitepress/documentation.ts

@@ -0,0 +1,384 @@
+// Authored guide ownership: physical sources and stable public routes.
+export const documentationSections = [
+  {
+    text: "Getting started",
+    items: [
+      {
+        text: "Installation and setup",
+        source: "getting-started/installation.md",
+        route: "/installation",
+      },
+      {
+        text: "Client configuration and troubleshooting",
+        source: "getting-started/client-configuration.md",
+        route: "/client-configuration",
+      },
+      {
+        text: "CLI and Evidence",
+        source: "getting-started/cli.md",
+        route: "/cli",
+      },
+      {
+        text: "Guided MCP prompts and completion",
+        source: "getting-started/mcp-prompts.md",
+        route: "/mcp-prompts",
+      },
+    ],
+  },
+  {
+    text: "Native binaries",
+    items: [
+      {
+        text: "Native binary investigation",
+        source: "guides/native/native-investigation.md",
+        route: "/native-investigation",
+      },
+      {
+        text: "Go binary build metadata",
+        source: "guides/native/go-binaries.md",
+        route: "/go-binaries",
+      },
+      {
+        text: "Offline binary diagnostics",
+        source: "guides/native/binary-diagnostics.md",
+        route: "/binary-diagnostics",
+      },
+      {
+        text: "Recorded crash evidence",
+        source: "guides/native/recorded-crashes.md",
+        route: "/recorded-crashes",
+      },
+    ],
+  },
+  {
+    text: "JavaScript and Electron",
+    items: [
+      {
+        text: "JavaScript Application Graph",
+        source: "guides/javascript/javascript-application-graph.md",
+        route: "/javascript-application-graph",
+      },
+      {
+        text: "Cross-layer JavaScript application workflows",
+        source: "guides/javascript/javascript-application-workflows.md",
+        route: "/javascript-application-workflows",
+      },
+      {
+        text: "JavaScript artifact reconstruction",
+        source: "guides/javascript/javascript-artifact-reconstruction.md",
+        route: "/javascript-artifact-reconstruction",
+      },
+      {
+        text: "JavaScript source recovery",
+        source: "guides/javascript/javascript-recovery.md",
+        route: "/javascript-recovery",
+      },
+      {
+        text: "Passive Node and Electron runtime observation",
+        source: "guides/javascript/javascript-runtime-observation.md",
+        route: "/javascript-runtime-observation",
+      },
+      {
+        text: "JavaScript static/runtime reconciliation",
+        source: "guides/javascript/javascript-runtime-reconciliation.md",
+        route: "/javascript-runtime-reconciliation",
+      },
+      {
+        text: "Electron file-page observation",
+        source: "guides/javascript/electron-observation.md",
+        route: "/electron-observation",
+      },
+    ],
+  },
+  {
+    text: "Browser and captured websites",
+    items: [
+      {
+        text: "Website observation with CDP",
+        source: "guides/web/browser-observation.md",
+        route: "/browser-observation",
+      },
+      {
+        text: "Browser scenario contract",
+        source: "guides/web/browser-scenario-contract.md",
+        route: "/browser-scenario-contract",
+      },
+      {
+        text: "Website runtime source attribution",
+        source: "guides/web/web-runtime.md",
+        route: "/web-runtime",
+      },
+      {
+        text: "Historical web network captures",
+        source: "guides/web/web-network-captures.md",
+        route: "/web-network-captures",
+      },
+      {
+        text: "Captured website source locations",
+        source: "guides/web/web-source-location.md",
+        route: "/web-source-location",
+      },
+      {
+        text: "Captured website module relationships",
+        source: "guides/web/website-module-trace.md",
+        route: "/website-module-trace",
+      },
+      {
+        text: "Captured website scripts and static JavaScript analysis",
+        source: "guides/web/website-script-export.md",
+        route: "/website-script-export",
+      },
+    ],
+  },
+  {
+    text: "Android applications",
+    items: [
+      {
+        text: "Static Android APK analysis",
+        source: "guides/android/android-analysis.md",
+        route: "/android-analysis",
+      },
+      {
+        text: "Apktool resource decoding",
+        source: "guides/android/apktool-resource-analysis.md",
+        route: "/apktool-resource-analysis",
+      },
+      {
+        text: "ADB device inspection and acquisition",
+        source: "guides/android/adb-device-analysis.md",
+        route: "/adb-device-analysis",
+      },
+      {
+        text: "Flutter build identification",
+        source: "guides/android/flutter-analysis.md",
+        route: "/flutter-analysis",
+      },
+    ],
+  },
+  {
+    text: "Apple applications",
+    items: [
+      {
+        text: "Apple Application Inventory Projection",
+        source: "guides/apple/apple-application-analysis.md",
+        route: "/apple-application-analysis",
+      },
+    ],
+  },
+  {
+    text: ".NET assemblies",
+    items: [
+      {
+        text: "Managed-code analysis",
+        source: "guides/managed/managed-code-analysis.md",
+        route: "/managed-code-analysis",
+      },
+    ],
+  },
+  {
+    text: "Firmware",
+    items: [
+      {
+        text: "Firmware analysis",
+        source: "guides/firmware/firmware-analysis.md",
+        route: "/firmware-analysis",
+      },
+    ],
+  },
+  {
+    text: "HarmonyOS packages",
+    items: [
+      {
+        text: "Static HarmonyOS package inventory",
+        source: "guides/harmony/harmony-analysis.md",
+        route: "/harmony-analysis",
+      },
+    ],
+  },
+  {
+    text: "WebAssembly",
+    items: [
+      {
+        text: "Offline WebAssembly artifacts",
+        source: "guides/wasm/wasm-artifacts.md",
+        route: "/wasm-artifacts",
+      },
+    ],
+  },
+  {
+    text: "EVM contracts",
+    items: [
+      {
+        text: "Offline EVM bytecode",
+        source: "guides/evm/evm-bytecode.md",
+        route: "/evm-bytecode",
+      },
+    ],
+  },
+  {
+    text: "Databases and recorded packets",
+    items: [
+      {
+        text: "SQLite database snapshots",
+        source: "guides/data/sqlite-databases.md",
+        route: "/sqlite-databases",
+      },
+      {
+        text: "Recorded packet capture inspection",
+        source: "guides/data/packet-captures.md",
+        route: "/packet-captures",
+      },
+      {
+        text: "Packet capture summaries",
+        source: "guides/data/pcap-analysis.md",
+        route: "/pcap-analysis",
+      },
+    ],
+  },
+  {
+    text: "Process capture and instrumentation",
+    items: [
+      {
+        text: "Process capture",
+        source: "guides/runtime/process-capture.md",
+        route: "/process-capture",
+      },
+      {
+        text: "Frida instrumentation",
+        source: "guides/runtime/frida-instrumentation.md",
+        route: "/frida-instrumentation",
+      },
+    ],
+  },
+  {
+    text: "Provider setup and formats",
+    items: [
+      {
+        text: "Ghidra provider semantics",
+        source: "providers/ghidra-provider.md",
+        route: "/ghidra-provider",
+      },
+      {
+        text: "DOS MZ and COM analysis with Ghidra",
+        source: "providers/ghidra-dos.md",
+        route: "/ghidra-dos",
+      },
+      {
+        text: "Optional NativeAOT metadata recovery",
+        source: "providers/ghidra-nativeaot.md",
+        route: "/ghidra-nativeaot",
+      },
+      {
+        text: "MIPS ELF analysis through Ghidra",
+        source: "providers/ghidra-mips.md",
+        route: "/ghidra-mips",
+      },
+      {
+        text: "PSP static ELF analysis through Ghidra",
+        source: "providers/ghidra-psp.md",
+        route: "/ghidra-psp",
+      },
+      {
+        text: "RISC-V ELF analysis through Ghidra",
+        source: "providers/ghidra-riscv.md",
+        route: "/ghidra-riscv",
+      },
+      {
+        text: "Windows Ghidra P0",
+        source: "providers/windows-ghidra-p0.md",
+        route: "/windows-ghidra-p0",
+      },
+      {
+        text: "Headerless raw-binary analysis with Ghidra",
+        source: "providers/raw-binary.md",
+        route: "/raw-binary",
+      },
+      {
+        text: "IDA provider",
+        source: "providers/ida-provider.md",
+        route: "/ida-provider",
+      },
+      {
+        text: "JEB instrumentation and analysis",
+        source: "providers/jeb-analysis.md",
+        route: "/jeb-analysis",
+      },
+    ],
+  },
+  {
+    text: "Contracts and evidence",
+    items: [
+      {
+        text: "MCP runtime contracts",
+        source: "reference/mcp-contracts.md",
+        route: "/mcp-contracts",
+      },
+      {
+        text: "Reconstruction obligation ledgers",
+        source: "reference/reconstruction-obligation-ledgers.md",
+        route: "/reconstruction-obligation-ledgers",
+      },
+    ],
+  },
+  {
+    text: "Development and verification",
+    items: [
+      {
+        text: "MCP tool design",
+        source: "development/tool-design.md",
+        route: "/tool-design",
+      },
+      {
+        text: "Testing REA",
+        source: "development/testing.md",
+        route: "/testing",
+      },
+      {
+        text: "Client and agent verification",
+        source: "development/client-verification.md",
+        route: "/client-verification",
+      },
+      {
+        text: "Reconstruction readiness conformance",
+        source: "development/reconstruction-readiness.md",
+        route: "/reconstruction-readiness",
+      },
+      {
+        text: "Releasing REA",
+        source: "development/releasing.md",
+        route: "/releasing",
+      },
+      {
+        text: "REA roadmap",
+        source: "development/roadmap.md",
+        route: "/roadmap",
+      },
+    ],
+  },
+  {
+    text: "Release migrations",
+    items: [
+      {
+        text: "Upgrading from REA 6.1 to 6.2",
+        source: "migrations/migration-6.2.md",
+        route: "/migration-6.2",
+      },
+    ],
+  },
+  {
+    text: "Signal recordings",
+    items: [
+      {
+        text: "Recorded signal inspection",
+        source: "guides/signals/signal-recordings.md",
+        route: "/signal-recordings",
+      },
+    ],
+  },
+];
+
+export const documentationRewrites = Object.fromEntries(
+  documentationSections.flatMap((section) =>
+    section.items.map((item) => [item.source, `${item.route.slice(1)}.md`]),
+  ),
+);

docs/README.md

@@ -0,0 +1,138 @@
+# Documentation directory
+
+REA documentation is organized by reader task and document owner. This directory
+links every authored guide; the [site](https://rea.tools/) also serves separate
+product pages. The VitePress documentation source is this `docs/` tree.
+
+## Getting started
+
+- [Installation and setup](getting-started/installation.md)
+- [Client configuration and troubleshooting](getting-started/client-configuration.md)
+- [CLI and Evidence](getting-started/cli.md)
+- [Guided MCP prompts and completion](getting-started/mcp-prompts.md)
+
+## Native binaries
+
+- [Native binary investigation](guides/native/native-investigation.md)
+- [Go binary build metadata](guides/native/go-binaries.md)
+- [Offline binary diagnostics](guides/native/binary-diagnostics.md)
+- [Recorded crash evidence](guides/native/recorded-crashes.md)
+
+## JavaScript and Electron
+
+- [JavaScript Application Graph](guides/javascript/javascript-application-graph.md)
+- [Cross-layer JavaScript application workflows](guides/javascript/javascript-application-workflows.md)
+- [JavaScript artifact reconstruction](guides/javascript/javascript-artifact-reconstruction.md)
+- [JavaScript source recovery](guides/javascript/javascript-recovery.md)
+- [Passive Node and Electron runtime observation](guides/javascript/javascript-runtime-observation.md)
+- [JavaScript static/runtime reconciliation](guides/javascript/javascript-runtime-reconciliation.md)
+- [Electron file-page observation](guides/javascript/electron-observation.md)
+
+## Browser and captured websites
+
+- [Website observation with CDP](guides/web/browser-observation.md)
+- [Browser scenario contract](guides/web/browser-scenario-contract.md)
+- [Website runtime source attribution](guides/web/web-runtime.md)
+- [Historical web network captures](guides/web/web-network-captures.md)
+- [Captured website source locations](guides/web/web-source-location.md)
+- [Captured website module relationships](guides/web/website-module-trace.md)
+- [Captured website scripts and static JavaScript analysis](guides/web/website-script-export.md)
+
+## Android applications
+
+- [Static Android APK analysis](guides/android/android-analysis.md)
+- [Apktool resource decoding](guides/android/apktool-resource-analysis.md)
+- [ADB device inspection and acquisition](guides/android/adb-device-analysis.md)
+- [Flutter build identification](guides/android/flutter-analysis.md)
+
+## Apple applications
+
+- [Apple Application Inventory Projection](guides/apple/apple-application-analysis.md)
+
+## .NET assemblies
+
+- [Managed-code analysis](guides/managed/managed-code-analysis.md)
+
+## Firmware
+
+- [Firmware analysis](guides/firmware/firmware-analysis.md)
+
+## HarmonyOS packages
+
+- [Static HarmonyOS package inventory](guides/harmony/harmony-analysis.md)
+
+## WebAssembly
+
+- [Offline WebAssembly artifacts](guides/wasm/wasm-artifacts.md)
+
+## EVM contracts
+
+- [Offline EVM bytecode](guides/evm/evm-bytecode.md)
+
+## Databases and recorded packets
+
+- [SQLite database snapshots](guides/data/sqlite-databases.md)
+- [Recorded packet capture inspection](guides/data/packet-captures.md)
+- [Packet capture summaries](guides/data/pcap-analysis.md)
+
+## Process capture and instrumentation
+
+- [Process capture](guides/runtime/process-capture.md)
+- [Frida instrumentation](guides/runtime/frida-instrumentation.md)
+
+## Signal recordings
+
+- [Recorded signal inspection](guides/signals/signal-recordings.md)
+
+## Provider setup and formats
+
+- [Ghidra provider semantics](providers/ghidra-provider.md)
+- [DOS MZ and COM analysis with Ghidra](providers/ghidra-dos.md)
+- [Optional NativeAOT metadata recovery](providers/ghidra-nativeaot.md)
+- [MIPS ELF analysis through Ghidra](providers/ghidra-mips.md)
+- [PSP static ELF analysis through Ghidra](providers/ghidra-psp.md)
+- [RISC-V ELF analysis through Ghidra](providers/ghidra-riscv.md)
+- [Windows Ghidra P0](providers/windows-ghidra-p0.md)
+- [Headerless raw-binary analysis with Ghidra](providers/raw-binary.md)
+- [IDA provider](providers/ida-provider.md)
+- [JEB instrumentation and analysis](providers/jeb-analysis.md)
+
+## Contracts and evidence
+
+- [MCP runtime contracts](reference/mcp-contracts.md)
+- [Reconstruction obligation ledgers](reference/reconstruction-obligation-ledgers.md)
+
+## Development and verification
+
+- [MCP tool design](development/tool-design.md)
+- [Testing REA](development/testing.md)
+- [Client and agent verification](development/client-verification.md)
+- [Reconstruction readiness conformance](development/reconstruction-readiness.md)
+- [Releasing REA](development/releasing.md)
+- [REA roadmap](development/roadmap.md)
+
+## Release migrations
+
+- [Upgrading from REA 6.1 to 6.2](migrations/migration-6.2.md)
+
+## Architecture and authoring
+
+- [Architecture map](https://github.com/morluto/rea/blob/main/docs/architecture/architecture.mermaid)
+- [Documentation ownership and contribution model](development/documentation.md)
+- [Feature specifications](specs/README.md)
+- [Architectural decision records](adr/README.md)
+
+## Machine-owned documentation
+
+| Path                                      | Owner and update command                                                                  |
+| ----------------------------------------- | ----------------------------------------------------------------------------------------- |
+| `public/product-catalog.json`             | Ignored contract projection; `npm run docs:generate`                                      |
+| `verification/managed-conformance-*.json` | Ignored managed conformance projections; `npm run evidence:generate`                      |
+| `error-contract.schema.json`              | Tracked schema from contracts; `npm run docs:error-schema`                                |
+| `user-visible-errors.csv`                 | Authored error classification inventory; preserve its schema                              |
+| `releases/<version>.contributions.json`   | Durable release contribution record; follow the [release guide](development/releasing.md) |
+| `assets/`                                 | Shared authored images referenced by guides                                               |
+
+Do not edit generated catalogs or evidence to change product facts. Change their
+canonical contracts or producer and regenerate. Historical release records retain
+the exact commit messages and references from the release they describe.

docs/adr/README.md

@@ -0,0 +1,9 @@
+# Architectural decision records
+
+Store one actual decision per `docs/adr/<domain>/<decision-slug>.md`, without a
+global sequence number. Use meaningful names and the Michael Nygard sections:
+Status, Context, Decision and Consequences. Link each decision from its owning
+feature specification.
+
+See [the authoring guide](../development/documentation.md#feature-lifecycle) for
+the distinction between specifications, roadmaps and isolated decisions.

docs/agent-environments.md

@@ -1,426 +0,0 @@
-# Agent environments from recorded captures
-
-Use `rea environment-serve` to serve an environment manifest as an agent
-environment: an MCP server whose tools answer from the records of one retained
-web network capture, plus the environment card the agentenv framework reads to
-discover it. Nothing is fetched from the recorded application; every answer is
-retained Evidence. `rea environment-export` writes the same pair as a bundle
-folder `agent-env run` builds and runs; see [Export a bundle](#export-a-bundle).
-
-```sh
-rea inspect-web-network-capture /absolute/session.har har --format json > capture.json
-rea inspect-analysis-view view.json --format json > manifest.json
-rea environment-serve manifest.json --evidence capture.json --port 8765
-```
-
-The first command inspects the capture; the second projects the
-[environment manifest](web-network-captures.md#environment-manifest) view from
-it, where `view.json` wraps the capture Evidence as the inline source:
-
-```json
-{
-  "source": { "kind": "inline", "evidence": { "evidence_id": "ev_…" } },
-  "view": {
-    "kind": "environment-manifest",
-    "template_rules": ["after-uid-literal", "opaque-token", "sibling-variance"]
-  }
-}
-```
-
-The third command serves that manifest. Both served files are complete REA
-Evidence JSON as the commands write it with `--format json`; the `evidence`
-member of `view.json` is the whole of `capture.json`.
-
-## From a browser scenario
-
-The capture can also come from REA itself: a
-[browser scenario](browser-scenario-contract.md) records a scripted session
-in a browser REA launches, and its Evidence is a manifest parent like a HAR
-inspection. Select the `network` event family and response bodies. A replayed
-reply carries up to 256 KiB of a recorded body, but the scenario keeps at most
-`max_network_body_bytes` of each body (64 KiB by default), and only within its
-allocation budgets: base64 is charged about 11 bytes per body byte, and
-redaction more the shorter a declared secret is (about 35 bytes per body byte
-for a 12-character `admin_password`). A body over
-`max_network_body_allocation_bytes` (1 MiB by default) is kept as `unavailable`
-with that reason; one over `max_event_allocation_bytes` (4 MiB) or
-`max_total_event_allocation_bytes` (16 MiB) loses its whole content event,
-headers included, which the capture lists among its omissions. Either way its
-tool replays no body. The example raises all four so that 256 KiB bodies are
-kept when the declared secret has at least 12 characters:
-
-```json
-{
-  "browser": { "mode": "launch", "executable_path": "/usr/bin/chromium" },
-  "start_url": { "url": "http://127.0.0.1:5230/auth", "query": [] },
-  "secrets": [
-    { "secret_id": "admin_password", "environment_variable": "APP_PASSWORD" }
-  ],
-  "actions": [
-    {
-      "step_id": "user",
-      "action": "fill",
-      "locator": { "kind": "css", "selector": "input[name=username]" },
-      "value": { "source": "literal", "value": "admin" }
-    },
-    {
-      "step_id": "password",
-      "action": "fill",
-      "locator": { "kind": "css", "selector": "input[type=password]" },
-      "value": { "source": "secret", "secret_id": "admin_password" }
-    },
-    {
-      "step_id": "sign-in",
-      "action": "press",
-      "locator": { "kind": "css", "selector": "input[type=password]" },
-      "key": "Enter"
-    },
-    {
-      "step_id": "first-memo",
-      "action": "goto",
-      "destination": { "url": "http://127.0.0.1:5230/m/1", "query": [] },
-      "wait_until": "load"
-    }
-  ],
-  "capture": {
-    "events": ["network"],
-    "network": {
-      "request_body": true,
-      "response_body": true,
-      "header_values": false
-    },
-    "limits": {
-      "max_network_body_bytes": 262144,
-      "max_network_body_allocation_bytes": 12582912,
-      "max_event_allocation_bytes": 12582912,
-      "max_total_event_allocation_bytes": 67108864
-    }
-  }
-}
-```
-
-```sh
-APP_PASSWORD=… rea capture-browser-scenario scenario.json --format json > capture.json
-rea inspect-analysis-view view.json --format json > manifest.json   # view.json wraps capture.json as before
-rea environment-serve manifest.json --evidence capture.json --port 8765
-```
-
-Each network transaction becomes one record, in request order, and the
-record's ordinal is its zero-based position; a transaction whose URL carried a
-redacted secret is left unrepresented rather than templated, and one the
-capture cannot attribute to a single request and response is left
-unrepresented too. Tools are chosen by response media type, so a scenario that
-selected neither response bodies nor header values is refused. The browser
-scenario redacts credential headers and the secrets it declares; values the
-application returns in response bodies, such as session tokens, are kept, and
-the replayed body is the bytes the browser exposes for each response, with any
-declared secret replaced by its redaction marker (a body that redaction had to
-empty replays no body).
-
-## What a manifest is
-
-An environment manifest is a projection of one application's recorded request
-lines into a tool surface: one tool per method and path template on the
-primary origin, with inferred path parameters, observed query parameter
-names, value-free body shapes and pointers to the parent records each tool
-cites. It carries no bodies and no headers. The manifest's
-`parent_evidence_id` names the capture Evidence it was projected from; the
-serve command refuses a manifest whose parent is not the supplied `--evidence`
-file with an `invalid_request` error naming both identifiers, so a manifest can
-never be served from records it did not cite.
-
-The MCP catalog and environment card use a 1 KiB UTF-8 budget for each
-captured display sample. Observation, body-key and cited-record lists show
-whole values with omission counts; long method, path and query-name displays
-show a marked prefix. Complete values remain in manifest Evidence. Argument
-names longer than 64 characters use collision-safe `path_<n>` or `query_<n>` aliases; replay maps
-those aliases to the complete captured names.
-
-Discovery is admitted as a complete catalog under a 1 MiB serialization
-reservation before the listener binds. Reservation charges up to six bytes per
-UTF-16 code unit for JSON escaping/UTF-8 expansion, plus schema overhead;
-a catalog may therefore be refused even when its compact JSON is smaller.
-This was calibrated with 1500 query fields and eight concurrent SDK discovery
-requests (183,798-byte card, 507.27 MiB sampled process-family RSS). Over-capacity
-catalogs return `resource_constraint`, retain complete input Evidence, and require
-a smaller capture or manifest. Fields and tools are never silently omitted.
-
-## What replay means and does not mean
-
-Each MCP tool call selects one of the records its manifest tool cites and
-returns that record's recorded response. Selection compares the supplied path
-parameters against the record's path segments at the parameter indexes, then
-the supplied query values against the record's query string, and keeps the
-record with the most matches; ties keep manifest order. The result reports
-where the answer came from:
-
-```json
-{
-  "status": 200,
-  "content_type": "application/json",
-  "body": { "id": 2, "login": "probe" },
-  "replay": {
-    "record_ordinal": 5,
-    "evidence_id": "ev_…",
-    "exact_match": true,
-    "recorded_path": "/api/users/2",
-    "recorded_query": null,
-    "recorded_line_truncated": false,
-    "body_recorded": true,
-    "body_encoding": "utf-8",
-    "truncated": false
-  }
-}
-```
-
-`exact_match` is true when every supplied path parameter and query value
-equals the recorded one; it says nothing about parameters the caller omitted.
-Recorded query parsing runs only when supplied query arguments affect selection.
-A path value matches a recorded segment as written or after percent-decoding;
-when both kinds of match are available, the record whose segment equals the
-value as written is chosen. `recorded_query` keeps the `?` of an explicit empty
-query, and a recorded path or query longer than 1 KiB is cut in the reply with
-`recorded_line_truncated: true`; selection always uses the full recorded line.
-`content_type` also has a 1 KiB display bound with `content_type_truncated`; body
-interpretation uses the full recorded media type.
-When no record matches, the tool still answers from the tool's first cited
-record and reports `exact_match: false`. `body` is parsed JSON when the
-recorded content type is JSON-like (`application/json`, `application/*+json`,
-`text/plain`, `text/markdown`) and the text parses with safe numeric conversion; otherwise
-it is the recorded text. Large integer IDs and other numbers that would lose
-information stay in the original JSON text. Bodies over 256 KiB are cut at a UTF-8 boundary and returned as
-text with `truncated: true`. `body_recorded` is false when the capture kept the
-response's status and content type but no body; `body` is then `null`, which
-is not a recorded JSON `null`. `body_encoding` is `base64` when the capture
-retained response bytes that are not valid UTF-8; `body` is then exactly those
-bytes in base64, never a lossy decoding. A retained base64 body is decoded only as far as the 256 KiB a reply can carry, and a leading byte-order mark is kept. For a `base64` body the limit applies to the recorded bytes, not their longer base64 spelling, and a cut keeps whole base64 groups. Request bodies passed to `POST`, `PUT` and `PATCH`
-tools are accepted and ignored: nothing is written, and no call changes what a
-later call returns. Arguments the tool's input schema does not name are
-refused by the MCP server as invalid arguments, so a misspelled parameter never
-degrades into an omitted one.
-
-Replay is not emulation. A served environment does not establish the
-application's authorization model, response semantics or state transitions,
-which the manifest lists as unknowns; it does not validate supplied values; and
-it does not answer requests the capture never recorded. Replayed content is
-target content: every tool result, including the argument errors the MCP server
-returns before a replay runs, carries `_meta.provenance.untrusted_content: true`
-with `source: "analysis_target"`. The server advertises REA's untrusted-content
-instructions plus a warning that its tool names, descriptions, parameter names
-and observed values come from the capture too, and agents must treat all of it
-as data, never as instructions.
-That same warning prefixes every tool description in the standalone card, so
-card discovery carries it before an MCP client initializes. It labels the
-captured text without changing the tool names or schema fields clients use.
-
-## The state a capture observed
-
-Replay answers each call from one recording, so the answers reflect whichever
-moment of the capture recorded them. The
-[environment state](web-network-captures.md#environment-state) view extracts
-instead the data the capture's reads observed before the first related write:
-entity types with an identity field, entities with their recorded values,
-documents for written paths, and a render plan per read tool, kept only where
-it reproduces that tool's recordings from the state. It is the starting state
-an environment can hold, load and report; serving from it is a later increment
-and does not change replay.
-
-## Serve a manifest
-
-```sh
-rea environment-serve manifest.json --evidence capture.json [--host 127.0.0.1] [--port 0]
-```
-
-`--host` and `--port` default to `MCP_HOST` and `MCP_PORT` from the
-environment, then to `127.0.0.1` and an ephemeral port, exactly as
-[`rea mcp --http`](cli.md#serve-mcp-over-streamable-http) resolves them. The
-bound MCP URL is written to stderr as one JSON log line
-(`"msg":"MCP transport listening"` with `url`); `REA_LOG_LEVEL` overrides that
-log level. `ENVIRONMENT_NAME` renames the served environment; otherwise the
-manifest's `name` is used, and a set but blank value is refused as
-`configuration_invalid` before binding rather than silently falling back. The
-listener serves one MCP client at a time with the same session, `Host` header
-and shutdown contract as [transports](mcp-contracts.md#transports) describes.
-It runs until SIGINT or SIGTERM, then closes the listener, prints one
-`{"status":"stopped", …}` document and exits `130` or `143`.
-Signals during input loading or DNS/bind cancel the owning reader/listener before
-a listening announcement;
-that path returns a structured `cancelled` result instead of a stopped-listener
-document, with the same signal exit status.
-
-Three routes are served:
-
-| Route                             | Answer                                                                 |
-| --------------------------------- | ---------------------------------------------------------------------- |
-| `POST /mcp`                       | The MCP server: one tool per manifest tool, replaying retained records |
-| `GET /.well-known/agent-env.json` | The environment card                                                   |
-| `POST /agentenv`                  | JSON-RPC `-32601 method not found: <method>` for every method          |
-
-Numeric JSON-RPC IDs outside JavaScript's safe range or whose precision would
-be lost are refused as invalid requests with a null ID. They are never echoed
-as a different number.
-
-The data plane at `/agentenv` is advertised by the card but carries no
-operations in this release; the error names the requested method so a caller
-can see that the method, not the transport, is unsupported. Its request body is
-read within the same 4 MiB bound the MCP endpoint applies: a larger body is
-answered `413` with a JSON-RPC `-32000` error before any of it is parsed, and a
-body that is not JSON is answered `400` with `-32700`. A notification (no `id`)
-gets `202` and no body, a batch gets one reply per request in it, and an empty
-batch, a batch of more than 100 messages, or a message that is not a JSON-RPC
-request (including an `id` that is not a string, number or null, or `params`
-that are not an object or array) gets `-32600 invalid request`.
-
-## The environment card
-
-The card is the discovery document the agentenv framework reads before
-connecting to `/mcp`:
-
-```json
-{
-  "name": "grafana-example",
-  "protocolVersion": "1.0",
-  "url": "/agentenv",
-  "preferredTransport": "JSONRPC",
-  "additionalInterfaces": [{ "url": "/mcp", "transport": "mcp" }],
-  "capabilities": {
-    "extensions": null,
-    "tools": [
-      {
-        "name": "get_users_by_id",
-        "description": "GET /api/users/{numeric}; replays retained records [5, 6]; evidence ev_…",
-        "inputSchema": {
-          "type": "object",
-          "properties": {
-            "id": {
-              "type": "string",
-              "description": "Path segment 2 (numeric); observed: 2, 3"
-            }
-          },
-          "required": ["id"],
-          "additionalProperties": false
-        }
-      }
-    ],
-    "operations": []
-  },
-  "children_environments": null
-}
-```
-
-`capabilities.tools` lists the same names, descriptions and input schemas that
-`tools/list` advertises over MCP. Path parameters are required strings whose
-description names the segment index, the templating rule and the observed
-values (sampled within the list budget above; the manifest keeps them all);
-query parameter names are optional strings; write methods accept an
-optional `body` object described by the recorded top-level key types. Each
-input keeps its own argument: a query name equal to a path parameter's name is
-advertised as `query_<name>`, a query name longer than 64 characters as
-`query_<n>` (its position) with the captured name sampled in its description,
-and the write body as `request_body` when a query parameter is named `body`. Every
-schema closes with `additionalProperties: false`, a key the echo example's
-schema does not carry.
-`extensions`, `operations` and `children_environments` are fixed to `null`,
-`[]` and `null`: a replay environment declares no extensions, no data-plane
-operations and no children.
-
-## Export a bundle
-
-`rea environment-export` writes the same pair as a bundle folder the agentenv
-framework runs directly, shaped like its own echo example:
-
-```sh
-rea environment-export manifest.json --evidence capture.json ./grafana-example --json
-agent-env run ./grafana-example
-```
-
-```text
-grafana-example/
-  README.md                                 provenance, replay limits, run command, rights note
-  envs/grafana-example/Dockerfile           pinned image: node:24.18.0-bookworm-slim + rea-agents@<this version>
-  envs/grafana-example/env.toml             environment_name = "grafana-example"
-  envs/grafana-example/manifest.json        byte-exact copy of manifest.json
-  envs/grafana-example/evidence.json        byte-exact copy of capture.json
-  artifacts/check_grafana-example/verify.py the replay verifier
-  tasks/smoke.json                          deploy_env (local sandbox), then env_outcome_verifier
-```
-
-The command reads each file once, after checking that reading and parsing the
-whole file, including sealing traversal, fits the process's live heap headroom (a file that does not is
-refused as a `resource_constraint` before it is read), then authenticates and cross-checks the
-pair as `environment-serve` does, so a manifest projected from another capture
-is refused with the same `invalid_request` before anything is written, and the
-bytes it copies are the bytes it authenticated. The bundle directory must be
-absent or empty; an occupied directory is refused and nothing in it changes.
-The complete tool catalog must also fit the server's advertised catalog budget
-before any files are written. Privately parsed JSON is sealed once so authentication
-and replay share immutable response trees rather than copying the capture repeatedly.
-`--name` replaces the manifest's portable kebab-case name as the env folder and env id
-(Windows device names such as `con` and `lpt1` are refused);
-`--package-tarball <path>` copies a packed `rea-agents` tarball into the env
-folder and makes the Dockerfile install it instead of the registry package and
-remove it in the same layer, which is how a checkout rather than a release is
-run. The command prints the
-written files with their sizes and the pinned package source.
-
-Export uses the shared output-tree owner to check directory identities around
-exclusive creates, verify written bytes, and reject unowned entries before
-reporting success. It does not delete an inspectable partial folder on failure.
-Node's portable pathname APIs leave a syscall-boundary race, so the output's
-parent directories must be trusted. On POSIX output files use mode `0600`;
-Windows inherits ACLs and REA does not establish owner-only access there. Choose
-an already private Windows destination when captured content needs it.
-
-The Dockerfile sets `MCP_HOST=0.0.0.0` and `MCP_PORT=18765`, the port the
-framework maps for an MCP server env; the framework's own deploy supplies
-`MCP_HOST`, `MCP_PORT` and `ENVIRONMENT_NAME`, so the served card carries the
-env's name. It installs Debian's `python3` because the framework's local
-sandbox probes a container's readiness with `python3` inside it, which the slim
-Node image lacks. It copies the two inputs owned by the image's non-root `node`
-user, so a private host umask cannot leave them unreadable, runs as that user and starts
-`rea environment-serve /env/manifest.json --evidence /env/evidence.json`. The
-`env.toml` names the environment because the framework otherwise reads the
-name from Python sources the image does not have.
-
-`verify.py` is the framework's `async def verify(mcp_url)` shape over its
-Python MCP client: it lists the tools and checks the count equals the
-manifest's, calls the first `GET` tool without path parameters with no
-arguments and checks the call did not fail and its replayed `status` equals the
-recorded status of that tool's first cited record (an unknown recorded status
-stays unknown; it is not borrowed from another record), and returns one
-`replay` result whose description
-reports both checks. A manifest with no such tool yields a verifier that checks
-the count only and says so. `tasks/smoke.json` deploys the env on the local
-sandbox and runs that verifier against the env's MCP endpoint; the first run
-also builds the framework's own infrastructure, and the run tears everything
-down when it ends.
-
-The README written into the bundle records the capture artifact's SHA-256, the
-capture and manifest Evidence ids, the manifest view digest, the tool count and
-the package source, and states that the recorded content belongs to the
-captured application and must not be published without the rights to it.
-
-## Compatibility verification
-
-`npm run verify:agentenv:environment` is the hosted `real-agentenv` lane
-described in [testing](testing.md#exported-environment-bundles). It projects
-the Grafana-shaped source-owned capture through the built CLI, packs the
-checkout, exports a bundle with `--package-tarball`, runs it with the pinned
-`agentenv-framework` release on the runner's Docker and requires the smoke task
-to pass with no container left behind other than the framework's own
-image-registry helper, which the receipt reports. It proves that one exported bundle runs
-on one framework release; it does not claim any hosted platform or other
-framework versions.
-
-## Resource and lifecycle boundaries
-
-Both Evidence files are read once at startup through the bounded JSON input
-reader and authenticated as Evidence before the listener binds; a file that is
-not Evidence, a manifest of another view kind, a capture of another format, or
-a manifest projected from a different capture is refused before any port is
-opened. Because authentication covers the capture's records, a manifest whose
-parent check passes cites only records the capture retains. The server keeps
-only the cited records' request lines and response text in memory. No outbound
-network request is made, no process is launched and nothing is written to
-disk. A listener that fails after binding is logged and ends the command with
-a `resource_constraint` error and exit `1` instead of serving nothing.

docs/apktool-resource-analysis.md

@@ -1,166 +0,0 @@
-# Apktool resource decoding
-
-REA decodes Android resource tables and the binary manifest through the
-caller's Apktool launcher. This completes the static triad for Android
-targets: Java/Kotlin sources through the JADX family, engine-grade
-decompilation through JEB, and resources through this family. REA never
-installs Apktool or a Java runtime.
-
-## Supply tools
-
-Use Apktool 2.7.0 or newer (verified with 2.7.0 and 3.0.3 on Linux) and a Java runtime the
-launcher can find. Select the launcher through the environment:
-
-```sh
-# Optional: absolute path to the apktool launcher (upstream wrapper or a
-# java -jar script); without it, apktool resolves from PATH.
-export REA_APKTOOL_COMMAND=/absolute/path/apktool
-```
-
-Readiness is `rea inspect-apktool-client`: it runs `apktool --version` and
-reports the resolved launcher, its selection source, and its version. A
-missing launcher reports `capability_unavailable` with the
-`REA_APKTOOL_COMMAND` remediation rather than attempting an installation.
-`binary_session` uses the same host probe for tool availability; it does not
-validate a particular APK or guarantee that the selected input can be decoded.
-
-Client inspection and decode results disclose the following reported-version
-advisory windows without refusing otherwise compatible launchers:
-
-| Advisory                                                                                              | Reported version window                          | Host scope |
-| ----------------------------------------------------------------------------------------------------- | ------------------------------------------------ | ---------- |
-| [CVE-2024-21633](https://github.com/iBotPeaches/Apktool/security/advisories/GHSA-2hqv-2xv4-5h5w)      | Before 2.9.2                                     | All        |
-| [GHSA-vgwr-4w3p-xmjv](https://github.com/iBotPeaches/Apktool/security/advisories/GHSA-vgwr-4w3p-xmjv) | Before 2.9.3                                     | Windows    |
-| [CVE-2026-39973](https://github.com/iBotPeaches/Apktool/security/advisories/GHSA-m8mh-x359-vm8m)      | 3.0.0 release line through versions before 3.0.2 | All        |
-
-The 2026 advisory names 3.0.1 and its 3.0.2 fix. Inclusion of 3.0.0 is
-source-derived: [tagged 3.0.0](https://github.com/iBotPeaches/Apktool/blob/f770b39e425af4fa6ac4ca1e9ea6c4824339c6d3/brut.apktool/apktool-lib/src/main/java/brut/androlib/res/table/ResTypeSpec.java)
-passes type names through unchanged; the [3.0.2 patch](https://github.com/iBotPeaches/Apktool/commit/65dd8480dfcb63068562ffaa527f71bb0a9f772c)
-validates those names at their owner before they reach the output-path producer.
-Prereleases before the fixed release are conservatively disclosed; the exact
-`-dirty` downstream marker is compared as a release while preserving its spelling.
-This is version guidance, not verification of a particular prerelease or decoder.
-
-A launcher version does not prove the decoder's contents, execution platform,
-downstream backports, or overall safety. Windows applicability uses the selected
-local host; an opaque wrapper may run another engine. A missing warning means
-only that none of these version/host windows matched. Verify the selected
-decoder's patches before decoding untrusted APKs; the compatibility floor above
-is not a security recommendation. REA does not fetch advisories at runtime.
-
-On Windows, a `.bat` or `.cmd` launcher (such as Chocolatey's `apktool.bat`)
-runs through an explicit `cmd.exe /d /s /c` call. That call has no AutoRun,
-no delayed expansion, and quotes every argument. A launcher path that
-contains `"`, `%`, `^`, `!`, `&`, `|`, `<` or `>` is reported as
-`not_configured` instead of being passed to `cmd.exe`. If REA's temporary
-decode paths contain those characters, decoding through a batch launcher
-reports `capability_unavailable`.
-
-## Answer an analyst question
-
-```sh
-rea inspect-apktool-client
-rea decode-android-resources /targets/Example.apk
-rea decode-android-resources /targets/Example.apk --locale de
-rea decode-android-resources /targets/Example.apk --locales de --locales pt-BR
-rea decode-android-resources /targets/Example.apk --locales de --locales pt-BR --string-tables-only
-rea decode-android-resources /targets/Example.apk --no-strings
-```
-
-Equivalent MCP methods are `inspect_apktool_client` and
-`decode_android_resources`. The decode request takes `path`, an optional
-primary `locale` (project `res/values-<locale>/strings.xml` instead of the default
-table), `locales` (repeatable array of additional localized string tables to project
-from the same single decode pass), and `include_strings` (default true). Regional locales such as `pt-BR`
-select Android's `values-pt-rBR`. A three-digit region such as `es-419`
-selects `values-b+es+419`; `es-r419` is rejected because Android's legacy
-`-r` form requires a two-letter region. Android qualifiers such as `pt-rBR`
-and `b+zh+Hans+CN` may also be supplied directly.
-
-Set `string_tables_only: true` (CLI `--string-tables-only`) to return string
-entries only inside `string_tables`, including when selecting a single table.
-The top-level `strings` array is then empty by request; it does not establish
-that the primary table is empty. Table status, counts and coverage still describe
-the examined source. This avoids repeating primary entries in multi-locale
-responses and charges the aggregate output budget for one copy per table.
-Omitting the option preserves existing responses. `include_strings: false`
-still suppresses all string projection, including in this mode.
-
-## Interpret the result
-
-- **An owned APK snapshot is digested and decoded.** `target.sha256` and
-  `target.bytes` bind the observation to the exact APK that was decoded.
-  The Evidence subject carries the same snapshot digest and caller-selected
-  path, including when the original file changes during decoding.
-- **Metadata comes from apktool.yml as apktool printed it.** Version codes
-  keep their own spelling (`'7'` versus `7`); `package_name` is read from
-  the decoded manifest, not inferred.
-- **The manifest is the decoded text**, bounded at 512 KiB and reported as
-  truncated when larger.
-- **Strings are projected verbatim.** Escaped entities stay escaped, and
-  entries containing nested markup (`<b>`, `<xliff:g>`) are counted as
-  unparsed rather than flattened — the limitation names the examined count.
-  Malformed XML and a wrong document root are whole-document projection
-  failures: the result is partial, the failure reason is disclosed, and entry
-  counts remain unknown. They are not counted as one unsupported string.
-  The default table is bounded to 2000 entries with partial coverage when more
-  exist. `locales` lists observed regular `strings.xml` tables whose exact
-  `values-<locale>` directory is selectable by the request's locale grammar.
-  Locale suffixes allow up to 23 ASCII characters, derived from Apktool's
-  language, script, region, and variant fields; for example,
-  `b+sr+Latn+RS+REVISED` selects that exact table.
-  Other table directories, including combined qualifiers such as
-  `values-en-rUS-v21` and `values-mcc310-fr`, are named in limitations with
-  their source spelling. They are not advertised as selectable locales;
-  REA does not infer Android's runtime resource matching. Non-regular
-  strings-table paths are disclosed with partial coverage. Discovery uses
-  the same bounded traversal as the file count; filesystem failures remain
-  failures rather than being interpreted as missing tables.
-  When multiple tables are requested with `locales`, `string_tables` records
-  each projected table with its locale, status (`present`, `missing`,
-  `oversized`, `malformed`, or `skipped`), entry counts, and coverage,
-  bounded at an aggregate budget of 10,000 strings and 32 MiB XML. When `locales`
-  is omitted and `string_tables_only` is not true, legacy single-table payloads are preserved
-  without adding `string_tables`.
-- **Smali is skipped by design** (`apktool d --no-src`): Java-source
-  recovery belongs to the JADX family. Resource smali edits and rebuild are
-  a follow-up lane with mutation authority.
-- **Workspaces are owned and short-lived.** Decoding happens in a
-  provider-owned temporary directory that is removed before the result is
-  returned. The APK snapshot and framework cache both live inside this directory.
-  If removal fails, the result names the residual path and the provider retains
-  ownership for a cleanup retry on close, including failed decodes.
-
-## Resource and lifecycle limits
-
-- The decode runs with a 600 s deadline and a 4 MiB output capture budget;
-  a stopped decode reports `provider_timeout` and exceeded budgets report
-  `resource_constraint`.
-- Manifest reads are bounded to 512 KiB before decoding UTF-8. Strings XML
-  reads are bounded to 8 MiB; larger documents are skipped with partial
-  coverage and an explicit limit, rather than reported as missing.
-- `decoded_file_count` is capped at 100,000 files; the cap is reported in
-  the limitations when hit.
-- An ordinary nonzero decode exit surfaces as `unsupported_target` naming
-  the caller-selected APK, with Apktool's diagnostic and captured output.
-  Launcher startup, ownership preparation, signal termination and incomplete
-  output collection remain provider failures; they do not establish that the
-  selected APK is unsupported.
-
-## Real verification
-
-`npm run verify:apktool -- --apk PATH` exercises both operations against a
-real launcher. Record: apktool 2.7.0-dirty (Debian packaging) on Linux with
-OpenJDK 25 against a signed aapt2-built probe APK carrying two resource
-locales — launcher version, on-disk digest agreement, apktool.yml metadata
-(1.2.3, SDK 24–34), manifest package agreement, default and `de` string
-tables projected. Parser goldens in the test suite come from the same
-decode. See `docs/testing.md` for the lane summary.
-
-Multi-locale and table-only projection were also verified through real CLI and
-stdio MCP workflows on Linux with Apktool 3.0.3/JDK 21 against NewPipe 0.29.1,
-ApiDemos 6.0.18 and Appium Settings 8.2.1. Independent XML projection checks,
-exact facts/Evidence parity and bounded task costs are recorded in the
-[shared-decode and table-only checkpoint](../experiments/analysis-efficiency/apktool-string-tables.md).
-This qualifies selected resource facts, not application execution or independent
-binary resource-decoder completeness.

docs/architecture/architecture.mermaid

@@ -1,8 +1,8 @@
 graph TD
     subgraph "Entry Points"
         CLI["src/cli.ts + src/cli/<br/>One-shot CLI adapter<br/>setup, diagnostics, analysis, decompilation"]
-        MAIN["src/main.ts + src/main/<br/>MCP server adapter: stdio default, streamable HTTP opt-in<br/>config, session, process lifetime"]
-        DISPATCH["scripts/rea.mjs<br/>Executable dispatcher<br/>routes mcp / mcp --http / one-shot"]
+        MAIN["src/main.ts + src/main/<br/>MCP stdio server adapter<br/>config, session, process lifetime"]
+        DISPATCH["scripts/rea.mjs<br/>Executable dispatcher<br/>routes mcp / one-shot"]
     end
 
     subgraph "Production Composition"
@@ -10,7 +10,7 @@ graph TD
     end
 
     subgraph "Adapters"
-        SERVER["src/server/<br/>MCP request translation<br/>createServer, tool registration, toolResult<br/>http/: streamable HTTP listener and node:http bridge"]
+        SERVER["src/server/<br/>MCP request translation<br/>createServer, tool registration, toolResult"]
         HOPPER_BRIDGE["bridge/hopper_bridge.py<br/>Runs inside Hopper<br/>adapts operations to Hopper Python API"]
         GHIDRA_BRIDGE["bridge/ghidra/ReaGhidraBridge.java<br/>Packaged HeadlessScript<br/>inventory, decompiler, references, CFG"]
         INSTALL["src/cli/ + src/application/Setup*<br/>Host installation adapters<br/>macOS: verified vendor DMG to ~/Applications<br/>Linux: verified vendor package + apt/dnf/pacman"]
@@ -26,7 +26,6 @@ graph TD
     end
 
     subgraph "Provider Layers"
-        PROVIDER_OWNERS["src/providers/<br/>shared deferred client and inspection owners<br/>exact cleanup retry and attributed failures"]
         PWNTOOLS["src/native/pwntools/ + src/native/pwndbg/<br/>BYO offline ELF/core adapters<br/>owned snapshots/Python and optional core-only GDB<br/>unchanged upstream parsers, ABI structures and mapping API"]
         WASM["src/wasm/<br/>caller-supplied WABT; immutable artifact inspection<br/>owned process supervision and retryable workspace cleanup"]
         EVM["src/evm/<br/>unchanged EVMole/WASM in bounded owned worker<br/>explicit carrier parsing and inferred interface adapter"]
@@ -34,15 +33,11 @@ graph TD
         GHIDRA["src/ghidra/<br/>Ghidra discovery, profile & function analysis<br/>snapshot, Unix/Windows transport, bounded lifecycle"]
         IDA["src/ida/<br/>Upstream MCP contract adaptation<br/>live GUI binding or owned headless database"]
         IDA_MCP["External ida-pro-mcp<br/>GUI proxy or database supervisor<br/>upstream installation and engine lifecycle"]
-        AUX["src/artifacts/ + src/native/<br/>artifact inventory, bounded directory triage and extraction<br/>format readers and native capabilities"]
+        AUX["src/artifacts/ + src/native/<br/>artifact inventory and extraction<br/>format readers and native capabilities"]
         BROWSER["src/browser/<br/>CDP / Playwright capture<br/>captured scripts and native module resolution<br/>execution/: coverage, listener and source attribution"]
         JS_CODEC["src/javascript/sourceMaps/<br/>pinned upstream map codec<br/>owned heap-limited Node process, complete point evidence"]
         INSPECTOR["src/inspector/<br/>passive V8 Inspector discovery and capture<br/>script and target locations"]
         DOTNET["src/dotnet/<br/>Managed static metadata provider<br/>PE/CLI metadata inventory, members, IL"]
-        OBJDUMP["src/objdump/<br/>GNU objdump command profile"]
-        RIZIN["src/rizin/<br/>Static command profile and persistent debugger sessions"]
-        GDB["src/gdb/<br/>Persistent GDB/MI sessions<br/>owned process lifecycle and target state"]
-
         FIRMWARE["src/firmware/<br/>Binwalk / Unblob adapters<br/>owned processes, report normalization, private extraction"]
         ANDROID["src/android/<br/>Static APK adapter<br/>owned SDK stdio, pinned headless JADX, normalization"]
         REFERENCE["src/reference/<br/>Filesystem reference-source reader<br/>bounded traversal, validation, errors"]
@@ -55,7 +50,7 @@ graph TD
     end
 
     subgraph "Contracts Layer"
-        CONTRACTS["src/contracts/<br/>Caller-visible schemas for analysis, reverse engineering, managed, browser, Electron, application, and session tools"]
+        CONTRACTS["src/contracts/<br/>Caller-visible schemas for analysis, managed, browser, Electron, application, and session tools"]
         ERRORS["src/contracts/errorSchemas.ts<br/>Shared analysis error schemas<br/>CLI diagnostics, generated error catalog"]
     end
 
@@ -127,23 +122,10 @@ graph TD
     INSPECTOR --> DOMAIN
     APP --> DOTNET
     DOTNET --> DOMAIN
-    COMPOSITION --> OBJDUMP
-    OBJDUMP --> DOMAIN
-    COMPOSITION --> RIZIN
-    RIZIN --> DOMAIN
-    CLI --> GDB
-    SERVER --> GDB
-    GDB --> PROCESS
-    GDB --> DOMAIN
     HOPPER --> HOPPER_BRIDGE
     GHIDRA --> GHIDRA_BRIDGE
     HOPPER --> PROCESS
     GHIDRA --> PROCESS
-    GHIDRA --> PROVIDER_OWNERS
-    APP --> PROVIDER_OWNERS
-    PROVIDER_OWNERS --> PROCESS
-    PROVIDER_OWNERS --> AUX
-    PROVIDER_OWNERS --> DOMAIN
     GHIDRA --> WINDOWS
     PROCESS --> WINDOWS
     WINDOWS --> WINDOWS_NATIVE

docs/cli.md

@@ -1,531 +0,0 @@
-# CLI and Evidence
-
-Use the CLI for a direct inspection or a script. It uses the same application
-workflows and evidence contracts as REA's MCP server. Each CLI invocation is a
-separate process; save results when you want to use them in a later command.
-
-## Run a command
-
-After [installing REA](installation.md), use `rea`. You can also run a command
-without a global installation:
-
-```bash
-npx -y rea-agents@latest analyze-javascript-application /absolute/path/to/app --json
-```
-
-Use an extracted application directory or an ASAR as the target. Static
-JavaScript analysis returns the application graph and Evidence directly.
-Generic `rea analyze PATH` selects this workflow for directories and `.asar`
-files when neither `--provider` nor `--snapshot` is supplied. See
-[JavaScript artifact reconstruction](javascript-artifact-reconstruction.md)
-for results, integrity checks and coverage.
-
-The complete application Evidence can be hundreds of megabytes for a real
-application. When an agent or a person reads the result, save it to a file and
-project a summary, a module page or one module from the saved Evidence:
-
-```bash
-rea analyze-javascript-application /absolute/path/to/app --json > app-evidence.json
-jq -c '{source: {kind: "inline", evidence: .}, view: {kind: "summary"}}' app-evidence.json > app-view.json
-rea inspect-analysis-view app-view.json
-```
-
-The request can also name the saved file instead of embedding it:
-`{"source": {"kind": "evidence-file", "path": "app-evidence.json"}, "view": {"kind": "summary"}}`.
-The CLI resolves a relative path against the working directory; MCP clients
-pass an absolute path. REA reads and authenticates the file, then projects it
-like retained Evidence, so a large file is bounded by the file reader rather
-than charged as inline input.
-
-For example, a 334 MB Obsidian application Evidence file yields a summary view
-of about 10 KB. Replace the view with
-`{"kind": "page", "collection": "modules", "offset": 0, "limit": 32}` for a
-module page. See
-[JavaScript application workflows](javascript-application-workflows.md) for
-views, feature traces and comparisons that take the same saved Evidence.
-
-## Managed assemblies (.NET)
-
-For a .NET PE/CLI assembly, inspect its identity and deployment form before
-inspecting members. These commands read metadata and Common Intermediate
-Language (CIL) without loading or executing the assembly and require no native
-analysis engine:
-
-```bash
-rea inspect-managed-artifact /absolute/path/Assembly.dll --json
-rea inspect-managed-members /absolute/path/Assembly.dll --json
-rea inspect-managed-members /absolute/path/Assembly.dll --type Example.Parser --json
-```
-
-Replace `Example.Parser` with an exact `full_name` from the member inspection,
-or a declaring type name you already know. Omit `--type` to inspect all members,
-or repeat it to select several types.
-Selection limits decoding to the selected types; member references remain an
-assembly-wide inventory, so the output can still be large.
-
-Choose the workflow from the artifact's contents rather than its `.exe` or
-`.dll` extension. The managed parser requires PE/CLI metadata; it does not
-unpack .NET single-file hosts or decode IL2CPP. For the image, type and method
-names in a Unity `global-metadata.dat`, use
-[IL2CPP metadata](il2cpp-metadata.md). NativeAOT method bodies require native
-analysis. See the [managed-code guide](managed-code-analysis.md)
-for supported deployment forms, selection semantics, and coverage limits.
-
-## SQLite snapshots
-
-For a local database snapshot, use `rea inspect-sqlite-database PATH --json`.
-Add `--table NAME --row-limit 20` to read a bounded sample from an ordinary
-table. This command does not require a native analysis provider. See
-[SQLite database snapshots](sqlite-databases.md) for database/WAL identity,
-source-file handling and row-value semantics.
-
-## Native analysis
-
-Inspect embedded Go build metadata without installing Go or configuring a
-disassembler:
-
-```bash
-rea inspect-go-binary /absolute/path/to/program --json
-```
-
-The shared CLI/MCP workflow reports compiler version, modules, replacements,
-build settings, original bytes and SHA-256. See [Go binaries](go-binaries.md)
-for supported containers and absent or malformed metadata.
-
-Inspect a Godot PCK without running the game:
-
-```sh
-rea inspect-artifact game.pck --detail summary --evidence_output evidence.json --json
-rea extract-artifact game.pck --json
-```
-
-Formats 2, 3 and 4 retain header, directory and integrity facts. Compact delivery
-keeps complete Evidence in the requested bundle. See [Godot PCK](godot-pck.md)
-for embedded packs, batch queries and unknown encrypted coverage.
-
-Inspect Unity IL2CPP metadata names without Unity or a disassembler:
-
-```bash
-rea inspect-il2cpp-metadata /absolute/path/global-metadata.dat --json
-```
-
-The command decodes a version 24, 27, 29, 31 or 39 `global-metadata.dat` and reports assembly
-images, type, method and member names, string literals, index ranges, header
-sections and SHA-256. With `--binary PATH` it also reads the matching
-`GameAssembly.dylib`, `GameAssembly.dll` or `libil2cpp.so` (never runs it) and
-links each method to its code address; `--ghidra-seeds PATH` then writes Ghidra
-function seeds. It does not decrypt metadata. MCP defaults to compact counts
-with retained Evidence; query indexed rows with filters, batch indices and
-selected fields. The CLI defaults to complete Evidence;
-`--detail summary --evidence_output FILE` exports the full result to a new file
-and returns a compact overview. See [IL2CPP metadata](il2cpp-metadata.md).
-
-Inspect an embedded cargo-auditable Rust dependency list without installing
-Rust or configuring a disassembler:
-
-```bash
-rea inspect-rust-binary /absolute/path/to/program --json
-```
-
-The same workflow reports package names, versions, sources, the root package,
-dependency edges, and the section's file range. A missing `.dep-v0` section is
-null metadata, not proof that the binary has no dependencies. See
-[Rust binaries](rust-binaries.md).
-
-Configure [Hopper or Ghidra](installation.md#hopper), the
-[IDA adapter](ida-provider.md), or [Kuna](kuna-provider.md) before analyzing a
-native target. Substitute
-your target, search text and function name or address in these examples:
-
-```bash
-rea analyze /absolute/path/to/program --provider ghidra --json
-rea search /absolute/path/to/program "search" --provider ghidra --json
-rea function /absolute/path/to/program main --provider ghidra --json
-rea decompile /absolute/path/to/program 0x1000 --provider ghidra --json
-rea xrefs /absolute/path/to/program 0x1000 --provider ghidra --json
-rea trace /absolute/path/to/program "search" --provider ghidra --json
-```
-
-`analyze` and `inspect` share the native overview workflow. `function` returns
-a function dossier; `decompile` returns pseudocode. For assembly instructions
-alone, use `rea instructions`. A macOS `.app` bundle can be supplied directly.
-
-Run `rea --help` or a command's `--help` for arguments and output options.
-The [generated catalog](mcp-contracts.md#generated-catalog) lists all CLI commands and MCP
-tools. Provider-specific target support is described in the
-[native guide](native-investigation.md), [DOS guide](ghidra-dos.md),
-[raw binary guide](raw-binary.md), and
-[Windows Ghidra guide](windows-ghidra-p0.md).
-
-## Choose a provider
-
-List the available providers and their supported operations:
-
-```bash
-rea providers --json
-rea capabilities --json
-```
-
-These commands describe binary-session providers and auxiliary capabilities.
-For the complete MCP surface, use the connected server's tool list and the
-session's advertised availability; individual guides describe prerequisites.
-
-With automatic selection, REA uses the single available provider that supports
-the target. When several providers support it, select one explicitly:
-
-```bash
-rea analyze /absolute/path/to/program --provider hopper
-```
-
-Set `REA_ANALYSIS_PROVIDER` for a standing preference. An explicit `--provider`
-overrides it. In MCP, pass `provider_id` to `open_binary`:
-
-```json
-{
-  "path": "/absolute/path/to/program",
-  "provider_id": "hopper"
-}
-```
-
-The selected provider remains bound to the session until an explicit switch
-or close. Provider failures are returned with their original reason. For an
-`ambiguous` selection error, choose from `details.candidate_ids`; for
-`provider_unavailable`, follow `message`, `remediation.action`, and the original
-reasons in `details.rejections`. For Hopper, Ghidra, IDA, and JADX, run
-`rea doctor --provider ID --json` to diagnose the selected engine. Other adapters,
-such as `pwntools-elf`, report their configuration requirements directly and are
-not accepted by `doctor --provider`. See
-[task readiness](installation.md#check-readiness-for-your-task) and
-[provider selection](mcp-contracts.md#identity-and-discovery).
-
-The session reports work still in progress through `analysis_activity`.
-A client timeout can end its wait while the provider continues analyzing.
-`cleanup_incomplete` identifies resources whose shutdown or removal could not
-be verified. See [MCP contracts](mcp-contracts.md) for session lifecycle and
-[Ghidra first-query deadlines](mcp-contracts.md#ghidra-first-query-deadlines-and-recovery)
-for import, client timeouts and recovery.
-
-If one-shot analysis fails and closing its session also fails, the original
-error details remain inline and `details.cleanup_error` describes the later
-close failure. Each diagnostic retains its own reported resources; the later
-failure does not establish whether an earlier resource was released. Captured
-output and partial observations remain in the original details.
-
-## Save and reuse analysis snapshots
-
-A snapshot retains successful analysis results for later queries. REA reuses
-an exact result when the target bytes, operation, parameters, provider and
-settings match. Mutations and cursor-dependent calls are excluded from the
-cache. Snapshot files are local and use owner-only permissions.
-
-Dispatching a metadata write invalidates the active session's snapshot cache,
-even if its reply fails: the provider may already have applied the write.
-Close and reopen the target before importing or saving another snapshot.
-
-Snapshots retain eligible target-scoped question histories in full, including
-mutation Evidence recorded while another target was active. Observations and
-related questions must still belong to the saved target. If those dependencies
-cannot be retained, the entire history is excluded instead of reverting the
-question to an earlier revision or disposition.
-
-```bash
-rea analyze /absolute/path/to/program --provider ghidra --snapshot /absolute/path/to/analysis/program.json
-# Repeat the same query to reuse its saved result.
-rea analyze /absolute/path/to/program --provider ghidra --snapshot /absolute/path/to/analysis/program.json
-```
-
-An exact CLI cache hit is normally read before starting a provider process.
-On Windows, Ghidra first admits the selected source through its native snapshot
-owner, so replay can start that provider.
-In MCP, `open_binary` accepts `snapshot_path` to import a snapshot atomically
-for its matching target; an MCP provider may still start before returning a
-cached result. `close_binary` accepts `snapshot_path` and optional
-`overwrite: true` to save before releasing provider resources. A failed save
-leaves the session open so the caller can resolve the output failure.
-
-The MCP save receipt reports `primitive_entries`, `workflow_entries`, and
-`evidence_records` separately. Zero primitive bindings can still accompany retained workflow
-results and Evidence. These are cached observations, not a saved provider
-database: only eligible exact queries can reuse a result, and new or live
-queries can still require provider startup. The CLI uses the same snapshot
-format and preserves these records when loading and updating it.
-
-## Import, export and compare Evidence
-
-Evidence records retain artifact identity, source locations, observations,
-inferences and unresolved findings. Validate an existing bundle, export its
-canonical form, or compare two supplied bundles:
-
-```bash
-rea evidence-import /absolute/path/to/evidence/bundle.json
-rea evidence-export /absolute/path/to/evidence/bundle.json /absolute/path/to/evidence/canonical.json
-rea compare /absolute/path/to/evidence/left.json /absolute/path/to/evidence/right.json
-```
-
-Exports preserve an existing destination unless `--overwrite` is explicit.
-For application traces and version comparisons, see
-[JavaScript application workflows](javascript-application-workflows.md).
-MCP [retained Evidence references](mcp-contracts.md#retained-application-evidence-inputs)
-belong to one connection. Separate CLI calls consume full saved records.
-
-## Import historical source
-
-Import an older source tree to compare with the current artifact:
-
-```bash
-rea import-reference-source /absolute/path/to/source
-rea import-reference-source /absolute/path/to/source --detail summary --outline-depth 2 --json
-```
-
-The default (`--detail full`) returns the complete `HistoricalSourceGraph`.
-Choose `--detail summary` for a `HistoricalSourceSummary` of that same committed
-inventory: its `HistoricalSourceManifest` contains the full graph and root
-digests, with provenance, VCS facts, languages, manifest paths, entry and
-relationship counts, parse-failure counts, file/directory states, exclusions
-and limitations. The summary is a presentation view, not a graph accepted by
-source-to-bundle comparison; keep the full output for that workflow.
-
-`--outline-depth` requires `--detail summary` and accepts a nonnegative safe
-integer. Depth 1 shows root children, depth 2 (the default) also shows their
-children, and depth 0 omits all outline entries. Paths retain canonical Unicode
-code-point order. `outline.omitted_entry_count` counts only inventoried entries
-hidden by the chosen depth; it does not count unexamined children of excluded or
-unreadable directories, or change `inventory_state`. Exclusions and source
-limitations remain separate from this presentation omission.
-
-`file_sizes.known_bytes` is the exact sum of known inventoried file sizes as
-decimal text, so large sums cannot lose integer precision. Unknown sizes count
-in `file_sizes.unknown_file_count`; excluded or unexamined paths are not included
-in that total. A zero known-byte sum therefore does not establish an empty source
-tree. Full output retains individual file hashes, relationships and parse-failure
-diagnostics. Summary mode performs the same import and cleanup, then projects
-the committed result without rereading source files. It reduces the selected
-output, not the amount of source examined. A shallow tree or many exclusions can
-still produce a large summary; depth 0 removes the outline but preserves the
-other facts. No fixed output-size or runtime improvement is promised.
-
-The import records hashes and metadata for the supplied files, separately
-from observations of the current app. For a directory inside a Git checkout,
-it records the HEAD of the nearest enclosing repository; whether the working
-tree matches that commit remains unknown. It honors the source tree's `.gitignore`
-and applies default exclusions for common generated and dependency paths such
-as `node_modules/`, `dist/`, and `*.log`. Pattern-based exclusions record the
-matched pattern and whether it came from project, default, caller, or sensitive
-path policy. Links into excluded paths retain their internal target metadata;
-the exclusion explains why the target has no inventory entry, and the inventory
-remains partial. Exclusions record `entry_kind` when the importer observed it;
-older saved exclusions without that field have unknown kind. An excluded
-ancestor proves an internal descendant only when its kind is `directory`.
-Set `REA_REFERENCE_SECRET_PATTERNS_JSON` to a JSON array of ignore
-patterns when you want to mark selected paths as sensitive; those patterns are
-reported separately as configured-secret exclusions.
-
-Re-import saved graphs whose pattern-based exclusions lack `pattern` before
-using them in source-to-bundle comparisons.
-
-Entries that change during an import retain an unavailable-entry diagnostic
-alongside readable siblings. If enumeration of an already admitted root fails,
-the graph keeps its observed children and records the root failure as a
-top-level limitation. That partial inventory does not establish absence among
-unexamined children.
-
-JavaScript and TypeScript import parsing requires valid UTF-8. Malformed source
-bytes retain their original hashes and sizes with a decoding diagnostic; REA
-does not infer module targets from replacement characters.
-
-Historical-source import requires safe no-follow file opens on Linux or
-macOS. Native Windows returns `unsupported_host`; use Linux REA inside WSL
-or another supported host. See
-[source-to-bundle comparison](javascript-application-workflows.md#historical-source-to-bundle-comparison)
-for mapping identities, inferences and unknowns.
-
-## Capture runtime behavior
-
-Choose the guide for the target and intended interaction:
-
-- [Browser observation](browser-observation.md): inspect a selected page through CDP.
-- [Browser scenarios](browser-scenario-contract.md): run declared interactions and capture their results.
-- [Electron observation](electron-observation.md): inspect an Electron renderer or capture an application scenario.
-- [Electron fuses](electron-fuses.md): read packaged fuse bytes before expecting `--inspect` to reach an Electron main process.
-- [Node/Electron Inspector](javascript-runtime-observation.md): record script locations and execution contexts.
-- [Process capture](process-capture.md): run an executable and compare terminal, exit and filesystem observations.
-
-Runtime requests name the target and actions. Launched targets run with your
-user permissions; consult the chosen guide for host requirements and effects.
-
-## Serve MCP over streamable HTTP
-
-`rea mcp` speaks stdio to the client that launched it. To serve the same MCP
-catalog over streamable HTTP for one local client, such as an agent environment
-runtime, start the dispatcher entry with `--http`:
-
-```sh
-rea mcp --http --port 8765
-```
-
-`--host` and `--port` default to `MCP_HOST` and `MCP_PORT` from the environment,
-then to `127.0.0.1` and an ephemeral port. The bound URL is written to stderr as
-one JSON log line (`"msg":"MCP transport listening"`) whatever `REA_LOG_LEVEL`
-is set to; nothing is written to stdout. `rea mcp --http --help` lists the accepted options. The listener serves
-one client at a time: a session ends with the client's `DELETE`, and a client
-that connects while another session is open takes it over, so a client that
-exited without ending its session needs no restart. The listener runs until
-SIGINT or SIGTERM and does not stop when stdin closes. See
-[transports](mcp-contracts.md#transports) for the session, `Host` header and
-shutdown contract. Client registrations written by setup and the MCP registry
-entry keep stdio.
-
-## Serve an environment manifest
-
-`rea environment-serve <manifest.json> --evidence <capture.json> [--host H]
-[--port N]` serves an environment manifest projected by `inspect-analysis-view`
-as an agent environment: an MCP server at `/mcp` with one tool per manifest
-tool, each replaying the retained capture records it cites, the environment
-card at `/.well-known/agent-env.json`, and a `/agentenv` data plane that
-answers every method with JSON-RPC `-32601`. The manifest's
-`parent_evidence_id` must equal the evidence file's `evidence_id`; otherwise
-the command refuses with `invalid_request` before binding.
-
-```sh
-rea environment-serve manifest.json --evidence capture.json --port 8765
-```
-
-`--host` and `--port` resolve like `rea mcp --http`: flags, then `MCP_HOST` and
-`MCP_PORT`, then `127.0.0.1` and an ephemeral port. `ENVIRONMENT_NAME` renames
-the served environment; set but blank, it is refused as `configuration_invalid`
-like a blank `MCP_HOST`. The bound URL is written to stderr as one JSON log line
-(`"msg":"MCP transport listening"`). See
-[agent environments](agent-environments.md) for what replay returns and does
-not establish.
-
-## Export an environment bundle
-
-`rea environment-export <manifest.json> --evidence <capture.json> <dir>
-[--package-tarball <path>] [--name <override>]` writes the same manifest and
-capture pair as a bundle folder the agentenv framework runs with
-`agent-env run <dir>`. It reads each file once, authenticates and cross-checks
-the pair with the same checks as `environment-serve`, copies the bytes it
-authenticated, refuses to write into a directory that exists and is not empty,
-and never overwrites a file.
-
-```sh
-rea environment-export manifest.json --evidence capture.json ./grafana-example --json
-```
-
-The folder holds a `README.md` with the bundle's provenance, an env folder
-`envs/<name>/` with a `Dockerfile` that installs this exact `rea-agents`
-version and serves the copied `manifest.json` and `evidence.json` (written
-with mode `0600` on POSIX; Windows retains inherited ACLs) with
-`environment-serve`, a Python verifier under `artifacts/check_<name>/` and the
-smoke task `tasks/smoke.json`. `--package-tarball` copies a packed `rea-agents`
-tarball into the env folder and installs it instead of the registry package,
-which is how the hosted lane proves a checkout rather than a release. `--name`
-replaces the manifest's kebab-case name as the env folder and env id; a device
-name Windows reserves (`con`, `nul`, `com1` and the like) is refused. The
-command prints one JSON document listing the written files with their sizes
-and the pinned package source. See
-[agent environments](agent-environments.md#export-a-bundle) for the folder
-layout and what the smoke task checks.
-
-## Output and exit status
-
-`rea mcp doctor --json` checks production MCP startup and reports child logs in
-`diagnostics`. It drains stderr while retaining at most its first 64 KiB of raw
-bytes as text, omitting a final UTF-8 code point if it crosses that byte limit.
-`stderr_bytes` counts all observed bytes, including omitted output;
-`stderr_truncated` indicates that output exceeded the retention limit. The same
-diagnostics appear inside the report when `--full-output` is selected. Log
-truncation alone does not change the diagnostic health or exit status.
-
-The default terminal format is TOON. Use `--json` when saving results for a
-JSON consumer. Valued output flags (`--format`, `--filter-output`,
-`--token-limit`, `--token-offset`) accept `--flag value` or `--flag=value`; a
-missing value fails with `MISSING_OUTPUT_VALUE` before the command runs. `--json` is indented on a terminal and compact when piped or
-redirected, which keeps large results smaller for agents and scripts; pipe
-through `jq .` for indented files. Output selection and formatting do not change
-operation status.
-
-`--filter-output` selects fields from successful command data. Classified failures
-retain their complete typed diagnostic projection even when the selector matches
-a field such as `code` or `message`, or names a missing field. `--full-output`
-controls whether the outer `{ok, error, meta}` envelope is included.
-
-For `cutter-command`, `--json-output` requests command-specific JSON from
-Cutter when available. This is separate from `--format json`, which selects the
-CLI result representation; the global `--json` flag selects that same CLI
-representation.
-
-Cutter still accepts deprecated `--json=true` and `--json=false` compatibility
-values. When both forms are present, `--json-output` takes precedence in either
-argument order. Bare `--json` retains its global meaning of selecting JSON CLI
-output formatting.
-
-| Status    | Meaning                                                                                                                                                                                                                                                                                                                                                                                |
-| --------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `0`       | The operation completed. Its result may include partial evidence, warnings or unresolved questions.                                                                                                                                                                                                                                                                                    |
-| `1`       | The operation could not complete. Structured output identifies invalid input, permissions, cancellation, timeouts or another failure when available.                                                                                                                                                                                                                                   |
-| `128 + N` | Signal-derived status. An unhandled signal may have ended the process, with the shell or runtime preserving the conventional status; a command may instead have handled the signal, waited for its operation and cleanup to settle, and assigned the same status (`130` for SIGINT, `143` for SIGTERM). In the handled case, it may also have printed a structured `cancelled` result. |
-
-`rea mcp --http` is long-running and prints no structured result. It exits
-`130` on SIGINT or `143` on SIGTERM after closing the listener, the session and
-its providers, and `1` when that cleanup fails.
-
-`rea environment-serve` is also long-running: it serves until SIGINT or
-SIGTERM, closes the listener, then prints one structured
-`{"status":"stopped", …}` document naming the URL, environment and tool count
-and exits `130` or `143` through the shared cancellation handler below.
-Refusals before binding (unreadable files, non-Evidence JSON, capture Evidence
-in a format other than HAR, a manifest whose parent is not the supplied
-evidence, an unbindable port) print a structured
-error and exit `1`, as does a listener that fails after binding.
-`rea environment-export` is one-shot: it prints the written files and exits
-`0`, or prints a structured `invalid_request` error and exits `1` for the same
-pair refusals, a non-empty or file-occupied directory, a missing package
-tarball or a name that is not a kebab-case label or is a Windows device name,
-writing nothing in each case.
-A write that fails after the first file (a permission or disk-space failure
-on a later path) propagates as the host's failure and leaves the partial
-folder in place for inspection; remove it before retrying, since the next
-attempt refuses the non-empty directory.
-
-A `cancelled` result does not by itself determine the exit status; it depends on
-the command's signal handling. Commands routed through the shared
-`withCommandCancellation` handler in the CLI set status `130` for SIGINT or
-`143` for SIGTERM after their operation settles. Current source registrations
-use that handler for process capture and comparison (`capture-process`,
-`compare-process-captures`), JavaScript application analysis (`analyze` when it
-selects the JavaScript lane, and `analyze-javascript-application`), selected
-browser, web and Electron commands (including `analyze-web-bundle`,
-`observe-web-execution`, `capture-browser-scenario` and
-`capture-electron-scenario`), and the platform and provider command families
-for Android/ADB, Apktool/JEB/Flutter, firmware, PCAP and signal analysis,
-WASM/EVM, Go/Rust and binary diagnostics, Frida instrumentation, the Cutter
-command, objdump, Rizin and GDB, and the agent environment server
-(`environment-serve`). In these paths, a returned structured
-`cancelled` result can be printed before the wrapper assigns the
-signal-derived status. This describes the current source routing; it is not a
-claim that every command or provider runtime has been independently exercised.
-
-When the reader of piped output closes early, as `rea ... | head` does, the
-CLI stops writing, prints no error and exits `141` (`128 + 13`, the status of a
-SIGPIPE-terminated writer). The operation itself may have completed; only its
-output was declined.
-
-`inspect-artifact` also returns a structured cancelled result, but its direct
-analysis cancellation path does not set a signal-derived exit status, so it
-exits `1`. Setup has its own contract: cancellation exits `0`. Treat the
-structured result and process status as separate signals when scripting
-cancellation.
-
-`setup --dry-run` returns `planned` and exits `0`; a cancelled setup also exits
-`0`. Setup returns `1` for `needs_confirmation` or `needs_human`.
-`doctor` returns `1` when required checks in its selected readiness scope fail;
-unavailable optional providers remain informational for unrelated tasks.
-
-Enable `pipefail` in a supporting shell so a downstream formatter preserves
-REA's failure status:
-
-```bash
-set -o pipefail
-rea inspect-artifact ./app.asar --json | jq . > inspection.json
-```

docs/desktop-applications.md

@@ -1,147 +0,0 @@
-# Desktop installation directories
-
-Use `inspect_desktop_application` when an installation directory is the target
-and its runtime is unknown. It reads directory entries, selected headers and
-bounded metadata, then reports runtime candidates, supporting files, component
-path markers and concrete follow-up operations. No native provider or active
-binary session is needed. It does not run the application, extract archives,
-follow child symlinks, contact services or change target files.
-
-## MCP
-
-```json
-{ "path": "/artifacts/MyApplication" }
-```
-
-Default `detail: "summary"` retains complete source Evidence in the session and
-returns candidates with representative supporting paths, counts, coverage,
-limitations and grouped next probes. `normalized_result.parent_evidence_id`
-identifies the complete record. A server without Evidence retention refuses
-summary delivery before reading the target; select `detail: "complete"` to
-receive every retained fact inline.
-
-Read exact files in one request:
-
-```json
-{
-  "source": {
-    "kind": "retained-evidence",
-    "evidence_id": "ev_<parent-sha256>"
-  },
-  "view": {
-    "kind": "desktop-application",
-    "collection": "files",
-    "paths": ["Game_Data/Managed/Assembly-CSharp.dll", "GameAssembly.dll"],
-    "fields": ["path", "read_status", "ranges", "facts", "issues"],
-    "offset": 0,
-    "limit": 16
-  }
-}
-```
-
-Collections are `files`, `omissions`, `candidates`, `components` and `next_probes`.
-Files and omissions accept exact `paths` and batched `file_ids` / `omission_ids`.
-Files also accept `has_issues: true` to select probe diagnostics directly, or
-`false` to select rows without reported issues. This filter uses the retained
-issue facts; it does not re-read targets or infer that uninspected files are healthy.
-When both are supplied, all filters apply; an empty selection returns no rows.
-Omission records retain the observed path, kind and stable `omission_id`; their
-payloads are not read, and other special-entry metadata remains unavailable.
-`candidates` accepts exact `families`.
-Omitted selectors match all retained rows; an empty selector matches none.
-Every collection supports `fields`, `offset` and `limit`; its stable row ID is
-always included. Selection changes delivery, not source inspection. Pages keep
-source coverage and parent Evidence links. Page exhaustion does not establish
-absence in a partial source. Complete Evidence remains accessible through
-`get_evidence` and Evidence bundle export.
-
-The summary's `probe_issues` counts files with reported issues and their retained
-issue entries. It previews at most two such files, including stable `file_id`,
-read status and the first issue. Path/reason previews use at most 256 UTF-16 units
-each without splitting surrogate pairs; `text_truncated` marks shortened text,
-and `preview_truncated` marks additional files. These are display prefixes;
-full caller paths and all reasons remain in Evidence. Counts describe retained
-observations, while source coverage still identifies partial inspection.
-
-Use `inspect_analysis_view` with `collection: "files", has_issues: true` and
-`fields: ["path", "read_status", "issues"]` for exact reasons, with the usual
-paging and parent links. It intersects with exact paths and batched file IDs.
-
-An ASAR inventory probe first selects its exact path with `open_binary`; then
-call `inspect_artifact` on that active target. Directory inspection itself does
-not select or replace the session target. The JavaScript application workflow
-accepts its own selected path directly.
-
-## CLI
-
-The one-shot CLI returns complete Evidence by default. For compact output,
-explicitly retain it in a bundle:
-
-```bash
-rea inspect-desktop-application /artifacts/MyApplication \
-  --detail summary --evidence_output /reports/application.evidence.json --json
-```
-
-This returns `summary` Evidence and an `evidence_bundle` publication receipt.
-Existing output files are never overwritten. Summary delivery requires
-`--evidence_output`, checked before analysis. `inspect-evidence-bundle` selects
-saved records; an exact saved record can also feed `inspect-analysis-view`.
-`--detail complete` returns source Evidence inline and can optionally write the
-same bundle. Export writes only the caller-selected output file.
-
-## Facts and uncertainty
-
-| Family       | Evidence used                                                                                                                                                                                    |
-| ------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| .NET         | A PE optional header declares a nonempty CLI directory.                                                                                                                                          |
-| Unity Mono   | A managed assembly below `*_Data/Managed` or `Contents/Resources/Data/Managed` has an exact UnityEngine assembly reference.                                                                      |
-| Unity IL2CPP | An IL2CPP metadata header coexists with a conventionally named native `GameAssembly.dll`, `GameAssembly.so`, `GameAssembly.dylib` or `libil2cpp.so` image. Build correspondence remains unknown. |
-| Godot        | A `GDPC` header at file start or a validated executable trailer offset.                                                                                                                          |
-| GameMaker    | A bounded `FORM` container starts with a `GEN8` chunk.                                                                                                                                           |
-| Unreal       | `Content/Paks` path conventions or an IoStore TOC signature; arbitrary `.pak` filenames are insufficient.                                                                                        |
-| Electron     | A `resources/app.asar` or `resources/default_app.asar` path convention; archive validity is unverified.                                                                                          |
-
-An observed metadata header with supported raw version 29, 31 or 39 offers an
-`inspect_il2cpp_metadata` follow-up at its admitted file path, including when no
-native library was found. This probe does not establish full metadata validity
-or correspondence to a native binary. See [IL2CPP metadata](il2cpp-metadata.md).
-
-Candidates are derived or inferred from these facts and do not prove loading or
-execution. BepInEx, MelonLoader, Easy Anti-Cheat and BattlEye labels identify
-path conventions only; runtime presence stays unknown. No bypass is provided.
-
-`file_id` includes the admitted root namespace, recorded path and available filesystem identity. The caller-selected root path and admitted canonical path/root identity are both retained; `local_path` identifies each observed file for follow-up operations. The selected root may be a symlink; child symlinks are not followed. Exact
-metadata integers remain decimal strings. Read ranges have offsets, byte counts
-and SHA-256 digests; typed facts expose CLI RVAs, metadata/pack versions and
-assembly tokens. Directory and symlink identities unavailable from traversal
-remain null.
-
-The directory's `snapshot_sha256` commits to retained paths, omission kinds,
-available metadata and range digests, composed through the admitted root,
-entry and omission identities. Caller ceilings, coverage counters, diagnostic
-wording and interpretation facts remain in Evidence, outside source identity.
-The same observations under different generous limits share a snapshot digest;
-Evidence IDs still preserve request parameters and reported coverage. Different
-retained entries or read ranges change the source snapshot.
-Omission records share the entry and representation budgets and can be fetched
-independently through their view.
-**It is not a digest of all file contents.** These are sequential stable entry
-observations, not an atomic directory snapshot. Unread bytes remain unknown.
-
-## Resource bounds and reuse
-
-Defaults are 20,000 examined entries and 8 MiB of total probe reads. Callers may
-select up to 100,000 entries and 64 MiB. A separate 32 MiB conservative
-representation budget bounds retained paths and facts before growth. Limits
-and failed probes produce partial coverage. Traversal and reads are serial.
-Each reader admits one inspection at a time; overlapping requests receive a
-retryable capacity refusal without cancelling the admitted caller.
-
-Unity reference decoding stops after a witness in each `Data/Managed` directory;
-other assemblies' references remain unexamined, while their headers are still
-checked. AssemblyRef facts decode names and tokens only; they do not decode or
-hash unrelated key/culture/hash payloads or establish runtime binding. Pack contents, encrypted data, metadata/address correspondence and
-section-embedded PCKs without a trailer are separate capabilities.
-
-Filesystem results are not cached across calls. Retained views reuse validated
-immutable metadata without rescanning files or retaining another inventory.

docs/development/client-verification.md

@@ -6,28 +6,6 @@ and provider lanes. Each record below states its host, client version, model
 fixture, and remaining coverage; a native-client run with a loopback model does
 not establish live model-service acceptance.
 
-## Published Pi code-mode renderer limit
-
-A separate probe of the published `@earendil-works/pi-codemode` 1.1.0 and 1.2.0
-declaration renderers rendered the full `compare_web_captures` input as
-`args: unknown`: its generated TypeScript type exceeds Pi's 16,000-character
-default. REA keeps the full advertisement's fields by inlining references when
-the shared form would exceed Pi's 32-reference expansion limit; retaining that
-shared form would leave later fields unknown instead. The existing
-`REA_MCP_INPUT_SCHEMA_PROFILE=compact` profile lets callers stay below
-its character limit by advertising reduced nested validation structure, while
-REA continues to validate calls against the complete canonical input schema.
-Compact applies to the server's advertised inputs and is not an automatic
-full-profile fallback; see the [compact input schema profile](mcp-contracts.md#compact-input-schema-profile)
-for details of its reduced forms.
-
-Custom renderer hosts can raise `inputMaxChars` through `renderToolSignature` or
-`renderToolSample`; `renderDeclarations` does not expose that override. The
-probe exercised the published renderer code, not a native Pi host or model, and
-does not establish broader Pi compatibility. See the pinned upstream
-[`declarations.ts`](https://github.com/earendil-works/pi/blob/b45e0ebcc5ae2fc42a6f2f23104d10e656e6bedb/packages/codemode/src/declarations.ts)
-and [renderer usage notes](https://github.com/earendil-works/pi/blob/b45e0ebcc5ae2fc42a6f2f23104d10e656e6bedb/packages/codemode/README.md#declarations-for-the-model).
-
 ## End-to-end, integration and golden evidence
 
 The optional `verify:qwen-client`, `verify:pi-client`, and `verify:hermes-client`
@@ -399,11 +377,6 @@ Such a stall leaves the initial page unloaded with empty or placeholder CDP URLs
 it does not establish permission to capture that page. See
 [the keyring diagnosis](https://github.com/morluto/rea/issues/1384#issuecomment-6093781686).
 
-On Windows, browser verifier lanes that launch an owned fixture require a
-standard, non-elevated caller token. They inspect the verifier caller before
-allocating fixture resources and refuse elevated or unobservable tokens; they do
-not change caller authority or claim to inspect the browser process token.
-
 `verify:browser` also captures a source-owned noise canvas as a real PNG above
 8 MiB through the CLI and stdio MCP, with complete byte/digest parity and real PNG
 decoding. Its SDK client explicitly permits the larger inline JSON response;
@@ -433,7 +406,7 @@ existing static JavaScript analysis through CLI and stdio MCP, including
 manifest readback, competing query variants, and resolved relative imports.
 It uses an installed browser and accepts an optional installed REA entrypoint.
 The complete `verify:browser` lane also exercises passive script export through
-both public adapters. See [website script export](website-script-export.md).
+both public adapters. See [website script export](../guides/web/website-script-export.md).
 
 `verify:browser:modules` compares CLI and stdio MCP traces against an independent
 real Chromium module-loading fixture: import-map scopes, package prefixes,
@@ -441,7 +414,7 @@ null/backtracking rejection, query/fragment identities, repeated module instance
 lazy and computed unknowns, exact source/map identities and no implicit refetch.
 Set `REA_BROWSER_EXECUTABLE`; the optional script argument selects an installed
 package entrypoint. The complete `verify:browser` lane and existing conditional
-Chrome CI include this verifier. See [module relationships](website-module-trace.md).
+Chrome CI include this verifier. See [module relationships](../guides/web/website-module-trace.md).
 
 ## Agent evaluation and conformance records
 
@@ -457,9 +430,7 @@ disposable HOME and CODEX_HOME under `~/.cache/rea-agent-evaluations/`. Set
 `REA_AGENT_EVAL_ROOT` to choose another parent directory outside the OS temporary
 directory: current Codex refuses helper aliases under `/tmp`, preventing shell
 commands and skill reads even if MCP works. Each owned run directory is removed
-after verification unless fixture retention is requested. Cleanup attempts the
-remaining run tree even if auth removal fails, and reports unresolved cleanup
-together with the original verification failure. The lane
+after verification unless fixture retention is requested. The lane
 installs the packaged skill and MCP registration through public `rea setup`,
 rather than copying a skill into a project that also inherits the caller's
 skills and configuration. Only authentication is copied, when present, and it

docs/development/documentation.md

@@ -0,0 +1,82 @@
+# Documentation ownership and authoring
+
+Use the [documentation directory](../README.md) to find existing material before
+adding another guide. Preserve one canonical owner for each contract or workflow;
+link to that owner instead of copying its claims into several guides.
+
+## Choose a destination
+
+| Document                                                 | Destination                            |
+| -------------------------------------------------------- | -------------------------------------- |
+| Installation, client setup and first CLI/MCP steps       | `docs/getting-started/`                |
+| Analyst workflows and evidence interpretation            | `docs/guides/<domain>/`                |
+| Analysis-engine configuration and format prerequisites   | `docs/providers/`                      |
+| Shared runtime contracts and evidence semantics          | `docs/reference/`                      |
+| Development, testing, release and authoring instructions | `docs/development/`                    |
+| Composition diagrams                                     | `docs/architecture/`                   |
+| Compatibility changes for a released version             | `docs/migrations/`                     |
+| One feature specification, plan and tasks                | `docs/specs/<domain>/<feature-slug>/`  |
+| One architectural decision                               | `docs/adr/<domain>/<decision-slug>.md` |
+
+Use meaningful, lowercase domain and feature slugs. Global numeric prefixes are
+unnecessary: different domains can add features independently, and branches do
+not compete for the next sequence number. Check the existing domain directory
+and linked issues before creating a feature with the same slug.
+
+Guides describe existing behavior and limitations. Specs define one proposed
+feature or domain change; an existing guide does not become a specification by
+moving it into `specs/`.
+
+## Feature lifecycle
+
+Create the specification before implementation. Each feature directory contains:
+
+- `spec.md`: problem, desired behavior, requirements, acceptance and non-goals.
+- `plan.md`: the single implementation plan, contracts and architectural choices.
+- `tasks.md`: incremental, testable steps linked to requirements and verification.
+
+Split independent domains or separately reviewable features before writing their
+specs. A broad `ROADMAP.md`, when useful, only lists child specifications, order
+and dependencies; requirements and implementation tasks belong to each child.
+Cross-repository contracts have one producer-owned specification. Consumers link
+to that contract instead of maintaining competing copies.
+
+Record an isolated architectural decision separately in
+`docs/adr/<domain>/<decision-slug>.md`, with **Status**, **Context**,
+**Decision** and **Consequences**. Link the ADR from affected specifications.
+Do not create decision records for routine file moves or invent past decisions.
+
+Specs do not replace the contribution-scope decision required for a new provider
+or expanded execution authority. Follow
+[contribution scope](https://github.com/morluto/rea/blob/main/CONTRIBUTING.md#contribution-scope).
+
+## Links and public routes
+
+Use relative links to physical Markdown files so GitHub readers can follow them.
+Link repository files outside `docs/` with their full GitHub URLs. Preserve
+existing heading anchors when moving a guide.
+
+[`documentation.ts`](https://github.com/morluto/rea/blob/main/docs/.vitepress/documentation.ts)
+owns categorized site navigation and the existing guides' stable public routes.
+Update it when adding or moving a guide. VitePress rewrites categorized sources
+to the existing public paths; its Markdown hook resolves repository links from
+the physical source and renders them against those public routes. Keep basenames
+and route assignments unique. Edit links use the physical source file.
+
+For a move, search for both the basename and its old full path. Update README
+translations, authored skills, verification instructions, documentation-fact
+readers and release configuration when they consume that path. Preserve
+historical release records and references bound to earlier commits or tags.
+
+## Generated ownership and checks
+
+The [documentation directory](../README.md#machine-owned-documentation) identifies
+the machine-owned outputs and their producers. Their existing paths are retained
+because scripts, package consumers and release history depend on them. Change
+canonical sources and regenerate; do not fix a generated projection by hand.
+
+Run `npm run docs:check` for documentation facts and generated consistency, and
+`npm run verify:docs:routes` to build the complete production site and check local
+links, anchors and physical edit targets.
+When a physical path moves, also run the tests that read it. Follow
+[development checks](testing.md#developer-commands) before requesting review.

docs/development/releasing.md

@@ -10,64 +10,11 @@ SHA returned by Release Please. Before either registry is published, the release
 run calls full CI qualification at that exact revision, including coverage,
 portable providers, and every native package host. Later main commits cannot
 change or cancel that proof.
-After qualification, a separate runner with read-only repository/actions
-permissions restores the retained tarball and verifier runtime. It installs
-that exact archive into an empty prefix, then exercises CLI help/discovery and
-the real stdio MCP catalog/session contract. Installation finishes before the
-protocol deadline begins, with dependency lifecycle scripts disabled. Only a
-successful rehearsal enables the job with npm publishing authority. Both jobs
-use the same release-input action; neither rebuilds or repacks the archive.
-This rehearsal checks package consumption on the Linux release runner;
-qualification retains its broader native-host and real-provider checks.
-
-Before publishing, npm lookup failures and malformed metadata stop the job.
-An existing version must match the qualified tarball's SHA-512 and intended
-`latest`/`next` dist-tag before it can be reused. Publication never overwrites
-an existing version or silently changes a dist-tag. After publication, only
-confirmed registry absence is retried within the propagation window. Content
-or tag mismatches fail immediately. The post-publication verifier installs
-from npm and repeats the same CLI/MCP checks; it also exercises a real update
-from an older stable release. For a prerelease on `next`, that updater still
-targets stable `latest`, as the public update command does.
-
-The required reverse-tools lane runs fresh coverage and both mutation
-preflights. Complete mutation sweeps run separately on a schedule or manual
-dispatch and do not block publication; see [the testing guide](testing.md).
 Ordinary main pushes and closed, unmerged PRs cannot publish packages. Check
 both publication jobs and the published-package canary; a merged PR or GitHub
 tag alone does not establish that publication finished. Retry failed jobs in
 the original run after a partial publication.
 
-### Recover an already published npm release
-
-Rerunning a job uses its original workflow and source revision. When a verifier
-or publishing workflow needs a code fix, land that fix on main first, then use
-the separate recovery workflow instead of repeating release creation:
-
-```bash
-gh workflow run release-recovery.yml --ref main \
-  -f version=6.5.0 -f release_run_id=38564502044
-```
-
-Select the existing version and its original automatic Release run. Recovery
-requires that run's successful exact-source CI gate and npm publish step. It
-uses the existing release tag, original qualified tarball and verifier runtime;
-expired or missing artifacts stop recovery. The archive's source, version,
-original run/attempt and Node version must match, and its SHA-512 must equal
-npm's published integrity. The corrected controller runs the public CLI, MCP
-catalog/session and previous-version update canary against that released runtime.
-The installation completes before MCP's handshake begins; dependency lifecycle
-scripts are disabled as in the installed-package verifier.
-
-Only after verification succeeds does recovery publish the released
-`server.json` to MCP Registry. It does not create tags or GitHub releases,
-publish npm bytes, or change dist-tags. Both publication paths share the same
-MCP publisher: a paginated registry lookup preserves an identical active
-version, refuses conflicting/inactive metadata, and fails on lookup errors.
-The original failed run remains a historical failure; the recovery run records
-the new verification and remaining registry publication. Manual frozen-branch
-releases are outside this recovery path.
-
 For a release that needs an independently frozen application checkpoint, use
 the optional manual path below. It retains explicit prepare and publish phases.
 
@@ -137,10 +84,8 @@ registry metadata or changelog disagrees with that version before creating a tag
 
 ### Compatibility and version selection
 
-Before publishing a candidate, review its changelog's breaking changes and the
-migration notes for the release being prepared. The
-[6.1 to 6.2 migration guide](migration-6.2.md) records that release's changes;
-it is a historical reference, not the compatibility checklist for later releases.
+For the 6.2 candidate, review the [6.1 to 6.2 migration guide](../migrations/migration-6.2.md)
+alongside the changelog before publication.
 
 REA uses Release Please's `always-bump-minor` strategy: every release increments
 minor and resets patch, including releases with breaking changes. For example,

docs/development/roadmap.md

@@ -5,8 +5,8 @@ The [platform tracker](https://github.com/morluto/rea/issues/32),
 [browser tracker](https://github.com/morluto/rea/issues/39) track capability and
 verification work. Available tools and setup are documented in the
 [investigation guides](https://rea.tools/guides/),
-[installation guide](installation.md), and
-[generated catalog](mcp-contracts.md#generated-catalog).
+[installation guide](../getting-started/installation.md), and
+[generated catalog](../reference/mcp-contracts.md#generated-catalog).
 
 ## Priorities
 
@@ -27,7 +27,7 @@ fixture servers; custom orchestration needs a demonstrated requirement.
 Provider and platform claims require their corresponding
 [real verification lanes](testing.md#real-toolchain-verification-lanes).
 See [tool design](tool-design.md) for choosing a tool boundary and
-[Ghidra semantics](ghidra-provider.md) for the existing deep-provider contract.
+[Ghidra semantics](../providers/ghidra-provider.md) for the existing deep-provider contract.
 
 Setup remains additive, reuses existing tools, and requires approval for disclosed
 configuration and Hopper installation changes. Additional installer choices need

docs/development/testing.md

@@ -19,7 +19,7 @@ behavior, and complete CI evidence before merging.
 | `npm run test:boundary`           | Boundary, CLI boundary, MCP boundary, process boundary, and process-global projects                                     |
 | `npm run test:mcp`                | MCP boundary project                                                                                                    |
 | `npm run test:acceptance`         | Complete compiled CLI and MCP acceptance workflows                                                                      |
-| `npm run test:python`             | LLDB and mitmproxy producer contracts plus analysis-efficiency checks; no real debugger or proxy required               |
+| `npm run test:python`             | LLDB producer retention and launch contracts with a fake LLDB API; no native debugger required                          |
 | `npm run test:watch`              | Dirty source tests in watch mode, without build                                                                         |
 | `npm run test:watch:all`          | Changed tests from every project; builds at startup, so rebuild after production edits before relying on compiled tests |
 | `npm run check:changed`           | Cached typecheck/lint and branch-related source feedback                                                                |
@@ -92,32 +92,15 @@ without serial scheduling. Pure domain/service, composition, conformance,
 evaluation, CLI boundary, and MCP boundary projects share module graphs. Their
 tests avoid process-global state and keep resource cleanup test-scoped. Each
 MCP session still owns its resources, and CLI cases retain fresh command
-instances or subprocesses. CLI and MCP module mocks belong in `tests/process-global/`
+instances or subprocesses. CLI module mocks belong in `tests/process-global/`
 so they keep per-file isolation. Product catalog verification stays with the
 isolated filesystem boundary tests because it loads both source and compiled
 module graphs. Adapter, other boundary, acceptance, and process-global projects
 retain per-file isolation. See `vitest.config.ts` for current settings.
 
-Inject producer faults through scoped dependencies in shared workers: a module
-mock cannot replace a consumer that was imported earlier. Check these tests
-with the consumer preloaded as well as alone. For simulated protocol traces,
-use an acknowledged event barrier before asserting complete observations;
-a zero-duration capture does not guarantee queued events have arrived.
-
-Check advertised schemas after SDK conversion for every supported schema
-profile. Meta-schema validity does not establish client acceptance or useful
-rendered declarations. Keep canonical rejection checks separate from the
-intentionally reduced compact advertisement, and probe actual client renderers
-when changing schema representations.
-
-The reused CLI boundary workers cap V8 old space at 384 MiB for ordinary runs
-and 512 MiB with coverage enabled. Covered ADB fixtures exhaust the ordinary
-384 MiB budget; those fixtures also complete with the shared CLI graph preloaded
-at 512 MiB. This is a measured capacity control, not a suite-wide speedup claim.
-Both profiles keep the
-same bounded worker count, and spawned REA processes retain their own heap
-settings. Explicitly disabling coverage retains the ordinary profile; coverage
-provider options alone do not enable instrumentation.
+The reused CLI boundary workers cap V8 old space at 384 MiB, based on their
+profiled allocation and cleanup behavior. This encourages collection between
+files; spawned REA processes retain their own heap settings.
 
 Vitest worker limits do not bound subprocesses launched within a test. Bound
 those batches separately so repeated CLI validation cannot oversubscribe the
@@ -204,130 +187,6 @@ Measure slow cases before pruning capacity coverage. Retain inputs beyond the
 formerly failing size/depth and distinguish cold runs, warm builds, coverage,
 and toolchain conditions when comparing timings.
 
-## Lifecycle regressions
-
-For changes to resource acquisition, readiness, cancellation, or cleanup, select
-the affected owners and applicable scenarios below. Include temporary snapshots
-and one-shot commands. Use public CLI/MCP workflows where practical and a
-controlled production seam for interleavings that cannot be reproduced reliably.
-
-| Scenario                                                                                | Assertion and control                                                                                                                                                                                                          |
-| --------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| Target admitted; startup still pending                                                  | Status preserves the readiness distinction and observed startup activity; readiness requires the provider's documented proof.                                                                                                  |
-| First handshake is late, absent, invalid, or recovered during close                     | Initial and recovery paths retain the same authenticated identity facts. Foreign run/token controls cannot authorize cleanup; authenticated idle/native work survives the unauthenticated listener deadline.                   |
-| Launch returns an error with a valid process handle                                     | Cover already-exited and still-live owned processes. Verify observed exit separately from creation; failed termination or unavailable identity remains unresolved.                                                             |
-| Cancellation arrives after workload exit, during result reads or temporary-root removal | Return typed cancellation with available partial observations and actual cleanup status. The non-aborted control succeeds; existing primary/cleanup failures keep their precedence.                                            |
-| Children have mixed health or cleanup outcomes                                          | Missing peer health does not erase an observed failure or activity. Idle plus unknown stays unknown. Retry a failed child without closing a successful peer again, including after a close-option change.                      |
-| Cleanup fails after success or primary failure                                          | Public output retains the completed observation or primary diagnostic, remaining resources, and owner recovery action. Restore the denied resource and verify the owning cleanup retry.                                        |
-| Target exits without an acknowledgement, or transport disappears while it stays alive   | Positive owned exit proof resolves target lifetime; other resources still need cleanup. Lost transport alone does not prove exit. Verify unrelated/attached targets survive and same-connection recovery works when supported. |
-
-Shared process-supervision controls separate leader exit from output closure.
-Cover output during held or failed cleanup, bounded retention and drain timeout,
-retry, and borrowed stream authority. The POSIX inherited-stderr control uses a
-separate pipe as a release barrier after leader exit; it does not establish
-native Windows Job Object behavior.
-
-Synchronize cancellation with the finalization boundary being tested; a fixed
-delay after dispatch does not establish that phase. Use markers, barriers, or
-owned cleanup seams while preserving real cleanup where feasible. Check server
-settlement and retained resources even if the MCP SDK rejects the client promise
-before the handler finishes. A cancellation during active execution does not
-cover cancellation during final cleanup.
-Use explicit abort reasons and assert their identity at admission and after
-provider completion, alongside retained observations and cleanup state.
-
-Electron fuse regressions cover actual descriptor close denial and retry through
-the built CLI, same-connection MCP recovery, mixed descriptor outcomes, and
-server shutdown. Controlled seams cover cancellation during final close and
-after reader finalization, plus active-provider shutdown during preflight.
-They preserve real filesystem cleanup where possible; mocked launch boundaries
-do not establish real Electron teardown or naturally occurring OS failures.
-
-Active Electron cleanup controls retain independent transport and process-family
-owners, block replacement captures until recovery, and retry only unresolved
-owners. Cover late close acknowledgement and rejection after a wait deadline,
-opaque rejection reasons, cancellation during failed finalization, and missing
-lineage followed by a confirmed passive family census. Windows controls require
-a fresh lineage observation and do not signal cached descendant PIDs after root
-termination. Simulated Windows controls do not establish native Windows behavior.
-
-Native process-ownership controls distinguish start identity, zombie lifecycle,
-current parent/group relation, and token-read evidence. Retain generation-bound
-candidates through smaller lineage observations, table omissions, reparenting,
-group changes, and failed cleanup retries. A readable token with unavailable
-identity stays unresolved. Native UID facts, rather than an earlier process-table
-row, determine whether a token denial concerns another user. Darwin tests compile
-the helper and exercise snapshot growth, absence, lifecycle, and UID observations;
-controlled Linux procfs tests do not establish real Linux exit or PID-reuse behavior.
-
-For atomic writes, exercise cancellation on both sides of the documented commit
-point and preserve any publication receipt. A late interruption does not prove
-that no output was published.
-
-For successful provider reports, test cancellation immediately before the report
-reaches the application workflow as well as during provider cleanup. Validate
-the report before classifying completion: a valid report must retain its Evidence
-on cancellation, and an invalid report must keep its output error. Exercise both
-the provider boundary and the shared CLI/MCP workflow; a downstream guard does
-not repair the provider's own completion contract. When callers share startup,
-cancel each waiter independently and verify that the last departure awaits owned
-cleanup while interested peers can still reach readiness. Repeat the same
-shutdown event after a cleanup failure to verify that its listener can retry.
-Exercise non-default lifecycle deadlines through queued requests and their
-consumers; default-only controls cannot detect dropped request options.
-
-For descriptor-backed reads, inject a close failure after a successful read and
-after a primary read or cancellation failure. Verify that the exact descriptor
-remains owned, both failures survive, and a later close retries it. Repeat
-admission attempts while close still fails: no additional descriptor or
-native command should start. Restore close and verify that the exact owner
-resolves the originating cleanup marker and allows later work, while the earlier
-failure remains available as a diagnostic. Retain errors returned by multiple
-failed retries, including admission and shutdown aggregates, and assert that
-each becomes complete after recovery. For an aggregate with multiple owners,
-release one owner while another still fails and assert that it remains incomplete.
-Cover recovery before the
-caller-specific error is bound to its retained owner, as
-another request can retry cleanup concurrently. Confirm that an already released
-owner resolves a later binding too. Include
-admission failure after opening the descriptor. If caller cancellation returns
-before an inspection settles, gate its final read or close and verify that
-session shutdown waits for the owned work and reports any retained resources.
-Gate a later read in a multi-read inspection, not only its first read. Overlap
-operations so one retains a failed descriptor while another reaches its next
-read; both the operation and shutdown must settle without nested-admission
-deadlock. Deny child close and verify its containing root survives until retry.
-
-Exercise publication on filesystems without hard links using an unsupported-link
-seam. Check exclusive destination creation, stat/write/close failures, completed
-output receipts, and cancellation at the documented cutoff. A streamed fallback
-has different visibility from an atomic hard-link commit and must report it
-accurately. For Windows command supervision, keep a descendant writing after its
-leader exits, deny cleanup observation, and verify a competing writer remains
-excluded until the exact Job Object closes. Portable doubles cover retry logic;
-the native Windows lane must establish actual process-tree behavior.
-
-Supervisor tests must observe process exit, output-pipe closure, and IPC
-disconnection separately. In the pinned Node runtime, a parent-initiated IPC
-disconnect can omit the aggregate `ChildProcess` close event. Join the actual
-resource observations before reporting completion; process exit alone does not
-establish pipe or process-tree release.
-
-When changing an internal helper contract, check its JavaScript verifier and
-subprocess-script consumers alongside TypeScript references. Source typecheck
-does not check those calls; run their orchestration tests against the built
-modules, including the verifier's failure and cleanup paths.
-
-Representative regressions include
-[process cleanup-time SIGINT](https://github.com/morluto/rea/blob/e78455338fe2d06c4cd03d59cbf33473d754998b/tests/boundary/process/processCaptureCancellationAdapters.test.ts),
-[late authenticated cleanup](https://github.com/morluto/rea/blob/e78455338fe2d06c4cd03d59cbf33473d754998b/tests/boundary/providers/hopper/hopperClient.handshakeRecovery.test.ts),
-[LLDB launch and finalization](https://github.com/morluto/rea/blob/e78455338fe2d06c4cd03d59cbf33473d754998b/tests/boundary/providers/native/lldbCallTracerFailures.test.ts),
-[composed child ownership](https://github.com/morluto/rea/blob/e78455338fe2d06c4cd03d59cbf33473d754998b/src/application/binary/CompositeProvider.test.ts),
-and [public CLI cleanup denial](https://github.com/morluto/rea/blob/e78455338fe2d06c4cd03d59cbf33473d754998b/tests/boundary/cli/wasmCleanupCli.test.ts).
-These controlled probes do not replace the matching real-provider lane. Record
-the base failure, passing control, exact host/provider, verified cleanup, and
-unavailable coverage; a missing engine is not a pass.
-
 ## Behavioral depths
 
 | Depth        | Location                | What it proves                                                                                        |
@@ -364,11 +223,6 @@ The process-global Vitest configuration contract rejects new direct temporary-ro
 creation outside the workspace seam and its narrowly documented boundary/package
 exceptions.
 
-The shared temporary-directory and workspace helpers preserve caller labels
-under an owned `rea-` prefix when needed. `npm run verify:test-temp-hygiene`
-uses the same ownership rule to find retained fixtures under a private temporary
-root. Third-party caches remain outside that ownership rule.
-
 Real Hopper, Ghidra, IDA, browser, package, and managed-code claims belong to their
 explicit `npm run verify:*` lanes. The reconstruction-readiness lane also
 checks deterministic rerun, tamper, and stale-input handling; those checks do
@@ -383,7 +237,7 @@ logic.
 reconstruction, native-boundary relationships and application graphs without
 executing fixture PE files. Operator-local manifests and actual ILSpy oracles
 remain optional, separately reported checks; the real Ghidra NativeAOT lane has
-its own toolchain prerequisites. See [the managed guide](managed-code-analysis.md)
+its own toolchain prerequisites. See [the managed guide](../guides/managed/managed-code-analysis.md)
 for those configurations. Generated completion-ledger checks use the same owning
 entrypoint and include its verifier/fixture files in their cache inputs.
 
@@ -408,60 +262,8 @@ CI owns coverage; aggregate and domain/contract thresholds are maintained in
 `vitest.config.ts`. They are glob-specific and never updated automatically.
 Coverage does not replace named boundary or real-provider scenarios.
 
-The `reverse-tools` commands run the focused tests and report coverage and
-mutation results without an additional percentage requirement. Test failures,
-invalid mutation configuration, and runner failures still fail the check.
-Mutation targets cover reviewed production behavior, including signal-terminated
-commands, Cutter descriptor identity, debugger cleanup ownership, GDB command
-exit and cancellation, and Rizin startup, timeout Evidence, and process exit.
-A second exhaustive pass runs the focused Cutter and Rizin timeout semantics tests against every compilable
-selected mutant to avoid relying on per-test mutation coverage associations;
-Stryker reports compile-error mutants separately because those cannot execute
-tests. Both passes resolve named syntax owners, scoped declarations, guards,
-callbacks, and reviewed expressions from the current TypeScript source; no
-hand-maintained line ranges select mutations. Missing, ambiguous, or malformed
-source targets stop configuration before mutation generation. The selections
-retain their review scope rather than expanding to whole source files. The
-focused suite also exercises affected MCP routes and the Python Cutter bridge.
-Contract, integration, and real-provider lanes complement these focused tests;
-simulated providers do not establish real-provider behavior.
-
-Required CI retains fresh reverse-tools coverage and preflights both canonical
-Stryker configurations with `--dryRunOnly`. These preflights resolve the owned
-targets, instrument the source, and execute the real initial tests. Invalid
-configuration, target resolution, and initial test failures still fail the job.
-Preflights execute no mutants and produce no mutation-outcome report. Both fast
-feedback and full qualification, including exact-revision release qualification,
-require coverage and both preflights. A failed, canceled, skipped or missing
-selected quality job still fails the required gate.
-
-The separate **Mutation sweep** workflow runs both complete configurations daily
-and on manual dispatch, in two isolated jobs. It is a maintenance check outside
-the PR and release publication gates. `ci:full` requests full regression,
-coverage and provider qualification; it does not request a complete mutation
-sweep. Use the Mutation sweep workflow to request that result. Targets,
-checkers, concurrency, deadlines and the existing non-blocking mutation-score
-threshold are unchanged. `npm run test:mutation:reverse-tools` also retains both
-complete passes for local callers.
-
-The two passes write separate JSON and HTML reports under `reports/mutation/`:
-`reverse-tools` and `reverse-tools-semantics`. Required CI retains focused
-coverage; the sweep retains each configuration's JSON/HTML reports separately.
-Both retain available diagnostics for seven days after failure and skip uploads
-on cancellation. Artifact names identify the tier or configuration and run
-attempt. A successful sweep requires both jobs and their nonempty reports;
-partial diagnostics and preflights do not establish complete mutation outcomes
-or qualify the release revision for mutation coverage.
-
-Fast CI starts the source-only projects after classification, independently of
-build and static checks, and runs five built-dependent shards after the build.
-The six test jobs still select every portable test. Full qualification keeps six
-complete Vitest shards with coverage. Neither tier retries tests. Canonical
-project ownership lives in `scripts/lib/test-projects.mjs`, shared by Vitest,
-CI group execution, and development-test preparation. A test importing compiled
-verifier code belongs to the built group even if its directory is conformance.
-Source and built blobs have separate labels to prevent merge collisions.
-Each test job emits a blob report; the merge job produces JUnit and JSON diagnostics, a module timing
+CI runs six native Vitest shards without retries. Each shard emits a blob
+report; the merge job produces JUnit and JSON diagnostics, a module timing
 report, plus aggregate coverage during full qualification. It retains available
 reports even when a shard fails, uploads available diagnostics, and writes the
 slowest files to the workflow summary. Partial reports are marked diagnostic
@@ -496,30 +298,6 @@ portable test shard. These limits leave headroom for cold setup and full coverag
 while preventing a hung job from holding the active main run for hours. They do
 not bound runner queue waiting. Timeouts still fail the required gate.
 
-The separate `CI timings` workflow also diagnoses missing, startup-failed,
-queued/running, approval-required, canceled, and failed PR CI through bounded,
-read-only API scans. Incomplete pagination or changing identity stays unknown.
-It never closes/reopens PRs, reruns workflows, posts comments, or changes gates.
-The timing manifest retains each run's event and head branch, including explicit
-unknowns, so PR runs cannot consume the eligible-main comparison budget.
-Its static failure report compares supported lint/duplication diagnostics with
-failed main runs using exact source, ancestry, task hashes, and toolchain proof.
-A match describes those diagnostics only; it does not establish that every
-failure in a job came from main. Duplication reports retain the actual checker
-exit result, so passing duplication checks preserve lint failures and caller
-thresholds remain owned by the producer. Missing checker outcomes leave
-those duplication diagnostics unclassified. Missing historical receipts remain unknown.
-The reporter executes only trusted default-branch code and parses whitelisted
-JSON artifact members without executing artifact content. Reports and limits
-are retained in `ci-health-diagnostics`; its ten-minute job limit covers the
-existing four-minute timing collection plus the bounded diagnostic stages.
-
-Shard-count reduction remains deferred: the available successful timing sample
-covers an older inventory, and file phase weights are not job wall time. The
-one-source/five-built split retains six test jobs; it makes no hosted speedup
-claim. Current complete timings and completed candidate hosted runs are needed
-before enabling a smaller adaptive matrix.
-
 The separate `CI timings` workflow batches recent completed CI and Release runs
 hourly or on manual dispatch. It uploads `ci-job-timings-batch` with raw API pages and
 a normalized point-in-time report for each collected workflow attempt, plus a
@@ -543,7 +321,7 @@ costs. Its queue, execution, and failures are independent of the required gate
 and publication. CPU time and peak process-family memory are not measured by this API.
 
 The build job saves portable Turbo outputs across runs. Eight Linux real-system
-lanes reuse its current-run artifact; standalone dispatches restore the cross-run cache. The shared action
+lanes restore this cache without waiting for the build job. The shared action
 derives its key from `test:prepare --dry=json` task hashes, runner OS and
 architecture, `.npmrc`, `.nvmrc`, and the lockfile; test-only changes can reuse compiled outputs. Every
 build and verification command still runs, so Turbo checks task inputs and
@@ -553,15 +331,7 @@ that generator's entry. Native outputs are not stored in this cache.
 
 Native package jobs, the Windows curated lane, and the Apple artifact lane reuse
 the same workflow's Turbo cache for portable compiled JavaScript, skills, and
-catalogs. The key parser retains the validated `test:prepare` task identities in
-`.cache/ci-build-plan.json`; staging reads this plan without starting another
-Turbo run that could evict cache entries. The producer stages matching archives,
-metadata, and available manifests into `.cache/ci-build-cache/`.
-`portable-build-cache.json` records availability per task. Evicted or partially
-missing entries are omitted as whole entries, and consumers rebuild cache misses,
-including when every entry is unavailable. Malformed plans, non-file entries,
-and I/O errors other than disappearance still fail publication. Older cross-run entries stay in the
-original cache. The Windows lane relies on the Linux static job for typechecking. They retain the normal build and prepack
+catalogs. The Windows lane relies on the Linux static job for typechecking. They retain the normal build and prepack
 commands, which restore matching outputs or rebuild on a cache miss. Native
 artifacts, dependency installs, package archives, and runtime verification remain
 host-local. Keep platform-dependent outputs out of this shared cache.
@@ -576,17 +346,6 @@ that explicit lane, not the routine iteration requirement.
 
 ## Real-toolchain verification lanes
 
-Linux Rizin debugger ownership changes require a separate real-provider gate on
-Rizin 0.7.4. Run
-`npm run test:focused -- tests/boundary/providers/RizinInferiorTty.test.ts`.
-This test verifies the caller-selected TTY against the actual inferior's file
-descriptors, confirms `dbg.exitkills=false`, detaches through the `olj`/`o-`
-protocol, and checks that the target survives debugger close and writes to the
-selected TTY. The suite is included in the reverse-tools Vitest and mutation
-typecheck selections; its real-provider assertions skip when Rizin 0.7.4 is
-unavailable. Run the focused command above on a host with that provider for the
-explicit real-provider verification gate.
-
 Each real-toolchain command must require only the host tools needed to prove
 its stated claim. Use a host-native fixture for host/provider acceptance, and
 place optional cross-target formats or platform-specific runners in separate
@@ -630,9 +389,8 @@ adds in-place reparse, breakaway, environment, and token observations.
 The separate `scripts/verify-windows-native-inspection.mjs` lane uses the
 `.cache/windows-native-inspection-fixture` artifact built on Linux with
 `node scripts/build-windows-native.mjs --inspection-fixture`. Its controlled
-first deletion failure checks retained NTFS ownership across a same-volume
-rename, later-query handle-based recovery, successful-admission caching, and
-environment-teardown cleanup. It neither
+first deletion failure checks retained NTFS ownership, later-query recovery,
+successful-admission caching, and environment-teardown cleanup. It neither
 establishes the cause of the intermittent #1701 host failure nor replaces
 verification with the shipped production artifact.
 `npm run verify:ghidra:windows:package` additionally packs and installs REA into
@@ -756,16 +514,15 @@ fixed public ApiDemos v6.0.18 fixture. Obtain both with the explicit
 kept under ignored `_reference/`. No Gradle build, Android SDK, emulator or
 application execution is required. The lane compares real CLI/MCP package,
 class search, class inventory, method decompilation and incoming references.
-See [Android analysis](android-analysis.md) for boundaries and resource budgets.
+See [Android analysis](../guides/android/android-analysis.md) for boundaries and resource budgets.
 
 `verify:jeb` requires a caller-started JEB client serving MCP at
 `REA_JEB_MCP_URL` (default `http://127.0.0.1:8425/mcp`) with a project
-already open, and exercises shared application/provider client inspection, unit listing coverage,
+already open, and verifies real CLI client inspection, unit listing coverage,
 and method decompilation. The script records the engine's exact response to
-`open_jeb_project`; the earlier licensed 5.48.0 headless verification did not
-advertise that tool.
-REA does not install or launch JEB; see [JEB analysis](jeb-analysis.md) for
-the bring-your-own boundary. The earlier licensed build was verified against JEB 5.48.0 serving
+`open_jeb_project`; JEB 5.48.0 headless instances do not advertise that tool.
+REA does not install or launch JEB; see [JEB analysis](../providers/jeb-analysis.md) for
+the bring-your-own boundary. Verified against JEB 5.48.0 serving
 `jeb-mcp-server` 1.3.0 at four scales: a compiled Java class fixture, a
 locally built signed probe APK with a launcher activity (manifest, v1/v2/v3
 certificates, dex bytecode, filtered and paginated listing), the published
@@ -776,14 +533,9 @@ decompilation through both CLI and MCP, and the official Flutter Gallery
 analyzed as native code (75k methods on arm64) and decompiled through both
 CLI and MCP with explicit unit selection, plus the thin Java wrapper and
 decoded manifest. The dedicated Dart snapshot processor and `run_script`
-remained GUI-only surfaces in that headless build.
-The separate [Linux CE native audit](../experiments/analysis-efficiency/jeb-linux-native.md)
-uses the official CE `5.48.0.202610071539` direct CLI launcher and real
-CLI/stdio MCP ELF workflows. That audit does not qualify CE Java/Android
-decompilation or GUI project opening, and it does not replace the licensed
-verification above.
+remain GUI-only surfaces in JEB 5.48.0 headless.
 Authenticated IPA and macOS application inventory projection is documented in
-[Apple application analysis](apple-application-analysis.md).
+[Apple application analysis](../guides/apple/apple-application-analysis.md).
 
 `npm run verify:harmony` requires no SDK or engine. It projects the pinned
 harmony-next-pipeline 1.0.1 release HAP from an MIT-licensed source repository,
@@ -793,7 +545,7 @@ The lane exercises `inspect_artifact`, projection determinism, Stage-model
 path hints, exact component sets, signing-entry limitations, and CLI/MCP parity.
 The release artifact has no independently established compiler/SDK or
 reproducible source build; the default lane does not verify an installed package.
-See [HarmonyOS package inventory](harmony-analysis.md) for those proof boundaries.
+See [HarmonyOS package inventory](../guides/harmony/harmony-analysis.md) for those proof boundaries.
 HarmonyOS `.har` libraries are deliberately not suffix-classified because
 `.har` also names HTTP Archive JSON.
 
@@ -814,7 +566,7 @@ with the reported target identity, apktool.yml metadata projection
 (1.2.3, SDK 24–34), manifest package agreement, and both the default and
 `de` string tables projected through the locale option. Parser goldens in
 `src/apktool/ApktoolDecodeOutput.test.ts` come from the same decode. See
-[Apktool resource analysis](apktool-resource-analysis.md) for boundaries and
+[Apktool resource analysis](../guides/android/apktool-resource-analysis.md) for boundaries and
 budgets.
 
 ## Flutter build identification
@@ -844,7 +596,7 @@ documented Gallery APK to assert its pinned digest, hash, exact engine labels
 and per-ABI URI counts. The verifier requires complete structural snapshot
 coverage, reports bounded pool coverage as partial/unverified, and reports
 exact labels/counts on other APKs unverified without an expectations file.
-See [Flutter build identification](flutter-analysis.md) for boundaries and
+See [Flutter build identification](../guides/android/flutter-analysis.md) for boundaries and
 budgets.
 
 ## ADB device acquisition
@@ -875,7 +627,7 @@ removal. System-package pulls whose APKs keep non-`base.apk` names report
 the `unknown` role with the file-name basis, verified with
 `com.android.settings` (single 73.9 MB APK). Parser goldens for
 `adb devices -l`, `getprop`, `pm list packages -f`, and `pm path` come from
-the same device. See [ADB device analysis](adb-device-analysis.md) for
+the same device. See [ADB device analysis](../guides/android/adb-device-analysis.md) for
 boundaries and budgets.
 
 ## Optional NativeAOT Ghidra analysis
@@ -919,7 +671,7 @@ with `REA_NATIVEAOT_PROOF_CAPTURE_DIR` (absolute paths).
 Keep builds/imports sequential on small hosts; scope `GHIDRA_HEADLESS_MAXMEM`
 (e.g. `768M`) to this command and use CPU affinity if needed. REA does not install
 or upgrade Java, Ghidra, .NET or native toolchains. See
-[the supported layout and provenance](ghidra-nativeaot.md).
+[the supported layout and provenance](../providers/ghidra-nativeaot.md).
 
 ## IDA MCP adapter
 
@@ -959,43 +711,11 @@ symbols carry a leading underscore). Before the headless session waited out
 the transient `busy` health a worker can report right after opening, that lane
 failed intermittently on that host. Linux headless, modern attached GUI tools,
 other engine versions and architectures remain unverified; see the
-[provider guide](ida-provider.md).
+[provider guide](../providers/ida-provider.md).
 
 Native IDA MCP verification uses `"protocol": "native"` with an already-running native plugin and requires `--second-procedure other_function --second-marker unique_second_body_text` to exercise GUI function switching and a return to the first function. These options remain optional for other profiles. The literal marker must appear in the second function's pseudocode and be absent from the first. Native cloud/widget failures are reported without hidden retries.
 
-The initial Linux x64 IDA Free 9.4 run used native MCP 1.1.2 with a local navigation correction. Windows x64 verification uses **IDA Pro 9.3**, the two-function public fixture, and the shipped Windows `whoami.exe` application. The native plugin was built from upstream `c9d15d98e8a143fc74f6e14037c48f63889b6d6c`, including the merged navigation fix, with a local loopback-listener change. Production CLI/MCP parity, switching, identity and cleanup passed. Correctness and performance measurements are recorded in the [Windows native verification notes](https://github.com/morluto/rea/blob/main/experiments/analysis-efficiency/ida-native-windows.md). Stock 1.1.2 switching, native macOS, and Windows IDA Free remain unverified. See the [native bridge prerequisites](ida-provider.md#optional-native-ida-mcp-bridge).
-
-## Kuna lane
-
-`npm run verify:kuna` requires a caller-supplied `kuna` in `REA_KUNA_COMMAND`
-and a host C compiler (`REA_CC`, default `cc`) with `strip` and `nm`. It builds a
-source-owned fixture with non-inlined calls, with symbols and stripped, then verifies through MCP that
-callers, callees and exact incoming xrefs agree with those calls, graph/path
-composition reaches the callee, reference-only queries leave project/staging
-entries unchanged, repeated relationships reuse the graph, and
-the first cold pseudocode answer comes from a single-function run or an export
-that already finished, assembly waits for and serves from that export, and
-pseudocode and both dossier facets match their recorded file spans and digests,
-a fresh server reuses the export without rebuilding it, staging is empty after
-a completed export, and no owned process survives. Pass
-`--targets DIR --functions a,b` to add caller-built binaries laid out as
-`DIR/<flavor>/<name>` beside `<name>.stripped`; addresses come from the
-symbol-bearing build. `--compare-ghidra` with `GHIDRA_INSTALL_DIR` runs those
-caller-built functions through Ghidra (it refuses to run without `--targets` and
-`--functions`, an empty matrix, or names missing from every supplied target) and
-reports latency, sampled process-tree CPU and peak memory, UTF-8 response size,
-and goto and warning-marker counts. Those counts are not a correctness judgement,
-and model tokens are not measured. Reference timings and response sizes are
-reported separately; reference caches expire when the server closes. `--report PATH` writes the JSON report.
-
-The first matrix run used Kuna 1.833 and Ghidra 12.1.4 with JDK 21 on macOS
-arm64. It covered zlib 1.3.2 `minigzip`, coreutils 9.9 `sort` and the sqlite
-3.54.0 shell, built at `-O2` for ELF x86-64, ELF AArch64, Mach-O arm64 and
-Mach-O x86-64, each with symbols and stripped. A separate Linux x86-64 run verified
-the fixture and system zlib 1.2.13 / SQLite 3.40.1 libraries through MCP, including
-cached byte spans and a Ghidra comparison. See the [Linux report](https://github.com/morluto/rea/pull/3854#issuecomment-6185870391)
-for measured scope and limitations. Windows, PE and universal Mach-O remain
-unverified by this lane.
+The initial Linux x64 IDA Free 9.4 run used native MCP 1.1.2 with a local navigation correction. Windows x64 verification uses **IDA Pro 9.3**, the two-function public fixture, and the shipped Windows `whoami.exe` application. The native plugin was built from upstream `c9d15d98e8a143fc74f6e14037c48f63889b6d6c`, including the merged navigation fix, with a local loopback-listener change. Production CLI/MCP parity, switching, identity and cleanup passed. Correctness and performance measurements are recorded in the [Windows native verification notes](https://github.com/morluto/rea/blob/main/experiments/analysis-efficiency/ida-native-windows.md). Stock 1.1.2 switching, native macOS, and Windows IDA Free remain unverified. See the [native bridge prerequisites](../providers/ida-provider.md#optional-native-ida-mcp-bridge).
 
 ## DOS Ghidra analysis
 
@@ -1007,7 +727,7 @@ stable CLI/MCP observations, unchanged source bytes, and owned process/project
 cleanup. Raw p-code address-space selector tokens are reported separately from
 the stable observation comparison. Linux x64 and macOS arm64 are verified;
 macOS x64 remains unverified. This lane is separate from host-native and optional cross-format
-verification. See [DOS analysis](ghidra-dos.md).
+verification. See [DOS analysis](../providers/ghidra-dos.md).
 
 `npm run verify:ghidra:com` uses a generated headerless fixture with no compiler,
 DOS emulator or game data. It exercises explicit admission, BinaryLoader entry
@@ -1030,16 +750,6 @@ and runtime cleanup. Windows additionally requires the matching native addon;
 its verifier lineage remains explicitly unavailable outside the provider's
 retained Job Object, as in the other Windows lanes.
 
-`npm run verify:ghidra:m68k` needs no assembler: its 22-byte big-endian 68000
-fixture is source-owned annotated hex in the verifier, loaded at `0x1000`. With
-an installed Ghidra 12.1.4 and full JDK on Linux or macOS, it verifies the
-`68000:BE:32:default` BinaryLoader import, real CLI/stdio MCP load-image parity,
-exact source bytes, both functions, the `bsr.b` call reference, decompilation
-through address and file offset, rejection of a misaligned entry and of a mapping
-past `0xffffffff` without replacing the active session, and runtime cleanup.
-Windows Ghidra P0 does not admit m68k, so this is not a Windows lane. The lane
-has been run on macOS; Linux has not been exercised.
-
 `npm run verify:ghidra:raw` uses a generated ARM little-endian headerless image
 through the compiled CLI and stdio MCP server. With the same Ghidra/JDK
 prerequisites, it checks preparation and bridge startup, verified load mappings,
@@ -1048,7 +758,7 @@ the entry changes without `provider_id`, unchanged source bytes, and owned
 cleanup. Six-byte x86 and x86_64 controls also verify supported compiler
 specifications, independent mappings, unchanged bytes, and decompilation of a
 known return value. AArch64 remains covered by deterministic tests rather than
-this real-provider lane. See [raw binary analysis](raw-binary.md).
+this real-provider lane. See [raw binary analysis](../providers/raw-binary.md).
 
 `npm run verify:ghidra:address-context` runs on Linux with a caller-installed
 Ghidra, full JDK, and an x86-64 ELF GCC toolchain (`CC` selects another compatible
@@ -1147,19 +857,7 @@ the Apple or Windows curated lanes invoke explicitly, which also select that
 lane. Edits to verifier entrypoints run only by manual, licensed or self-hosted
 workflows run static checks and the Linux suite. Website changes run website
 checks. Provider workflow changes validate the workflow and run that provider's
-verifier. Changes under `bridge/ghidra/` also select the `ghidra_bridge` lane,
-which compiles the packaged bridge sources against the pinned Ghidra 12.1.4
-jars with `npm run verify:ghidra:bridge-sources`. It never launches Ghidra or
-imports a target, so a missing import fails the PR instead of every Ghidra
-session. The launcher, compiler and package checks share named required source
-roles. The manifest must match the complete Java cohort, so deleting a helper
-or adding an unregistered dependency cannot silently change the shipped set.
-The preflight reuses the provider's Java Properties parser with the pinned Node
-toolchain's native type stripping, without an npm install or runtime build.
-The shared release policy owns the verified version and JDK major. CI checks
-the archive pin before downloading and verifies the extracted SDK version;
-changes to these source owners also select the compile lane.
-Manual-provider/Android workflow changes run workflow validation only.
+verifier. Manual-provider/Android workflow changes run workflow validation only.
 The four-version SQLite compatibility matrix has its own `sqlite` scope for
 SQLite implementation, contracts, CLI/MCP registration, fixtures, and shared
 runtime boundaries. SQLite and server-lifecycle test edits and the SQLite npm
@@ -1177,16 +875,6 @@ identifiable; unknown or shared script changes select everything. Android
 build-script edits retain the Linux suite and workflow validation; real Android
 verification stays manual. Renames account for both paths.
 
-The `agentenv` scope owns the environment application and server modules, the
-`environment-serve` and `environment-export` command registration, the shared
-streamable HTTP listener, `scripts/verify-agentenv-environment.mjs` and its
-workflow `real-agentenv.yml`. The lane exports a bundle from the source-owned
-Grafana-shaped capture through the built CLI, packs the checkout into the
-bundle's image and runs `agent-env run` on the hosted runner's Docker with the
-pinned `agentenv-framework` release; it passes when the smoke task passes and
-no container remains. It claims nothing about any hosted platform or another
-framework version.
-
 This narrower selection trades PR-time coverage for runner capacity. A change to
 unowned shared runtime code that fails only on arm64, macOS, Windows, the Apple
 artifact lane, or a provider lane that does not own the file is not caught on
@@ -1199,13 +887,8 @@ successful ancestor push run of this CI workflow, rather than the preceding
 push: changes from failed or cancelled intermediate runs remain in scope.
 Missing, untrusted, or non-ancestor history selects every lane. The lookup is
 bounded to the last 100 successful push runs; lookup failures broaden selection.
-Every code change still selects all six portable shards, without coverage
-instrumentation in this fast tier. Ordinary PR matrices cancel remaining
-shards after the first failure; passing PRs execute the complete suite. Main,
-`ci:full`, scheduled, manual, and release qualification retain every shard's
-results after a failure. Available failed-shard reports remain diagnostic only:
-failed, cancelled, skipped, or missing selected shards cannot pass the gate or
-publish successful timing history. This deliberately avoids relying on an
+Every code change still runs all six portable shards, without coverage
+instrumentation in this fast tier. This deliberately avoids relying on an
 import graph for generated files, filesystem inputs, subprocesses, or bridges.
 
 Scheduled qualification is admitted hourly at minute 23. A forced full run at
@@ -1233,11 +916,10 @@ classification job records its selection and broad-fallback reasons in the run
 summary. Representative Git-diff cases live in
 `tests/boundary/filesystem/ciChangeScope.test.ts`.
 
-`CI required` checks classification and every selected lane,
+`CI required` always runs and checks classification and every selected lane,
 rejecting failed, cancelled, or unexpectedly skipped work. It rejects missing or
 unknown tiers and requires every canonical scope to be explicitly `true` or
 `false`; incomplete classification cannot silently omit verification lanes.
-The aggregate remains cancellable so superseded runs release their slots.
 Branch protection
 should require this aggregate, `Static checks`, `Portable tests`, and
 `Conventional PR title`. Title validation runs separately on PR opening,
@@ -1286,7 +968,7 @@ filename cases.
 
 POSIX package verification resolves the runner's configured npm cache before
 creating disposable client homes and passes that location to its child installs.
-This reuses the download cache restored by the shared npm-cache action while keeping client
+This reuses the download cache restored by `setup-node` while keeping client
 configuration isolated. Installs retain their existing registry and integrity
 checks.
 
@@ -1316,28 +998,11 @@ thresholds remain enforced in full qualification.
 Missing or unusable history falls back to Vitest's default assignment. Only
 timing data is reused; live provider results are never cached. Turbo outputs are
 restored by task hash, with trusted default-branch runs as cache writers and PRs
-as restore-only consumers. The static job also restores its Turbo snapshot;
-each task revalidates its own input hash before reusing outputs or diagnostics.
-The Node pin and npm install settings are global hash inputs. Knip includes its ignore rules and VitePress
-entry, so changes to those inputs cannot reuse an older successful check.
+as restore-only consumers. npm caches hold downloads, not `node_modules`.
 
-The shared npm-cache action caches downloads, not `node_modules`, and every
-consumer still runs `npm ci`. Keys cover the runner OS, actual Node architecture,
-root lockfiles, and `.npmrc`. Only push, schedule, and manual events on the
-repository's default branch may save shared npm caches; PRs restore only.
-Static snapshots use the same write authority and are saved only after the
-static job's validation succeeds. Main warms the new cache namespace after
-merge; a cold cache or changed lockfile falls back to the normal install.
-This prevents each PR from saving another branch-scoped copy of the same
-download cache. It does not remove runner assignment waits.
-
-Portable owner-based test selection remains observational. Its reports compare
-proposed omissions with the full run; incomplete or skipped observations do not
-establish that fewer tests would preserve regression detection.
-
-The nine automatic browser, binary-layout, EVM, JavaScript-recovery,
-recorded-crash, web and environment-bundle provider lanes download
-`rea-build-cache` from their own run after the build and static jobs succeed. Their existing build commands still
+The eight automatic browser, binary-layout, EVM, JavaScript-recovery,
+recorded-crash, and web provider lanes download `rea-build-cache` from their own
+run after the build and static jobs succeed. Their existing build commands still
 validate task hashes and rebuild mismatched inputs; provider observations always
 run. Provider-workflow-only edits also admit the build without enabling source
 test shards. Direct provider dispatches retain the cross-run restore-only cache.
@@ -1385,7 +1050,7 @@ status, and Android logcat on success or failure. The emulator is disposable.
 capinfos against a saved capture. Linux verification uses Wireshark 4.6.6
 and captures containing DNS, TLS and HTTP traffic. Native Windows and macOS
 engine behavior remains unverified; process fixtures do not establish it.
-See [Packet capture analysis](pcap-analysis.md) for contracts and budgets.
+See [Packet capture analysis](../guides/data/pcap-analysis.md) for contracts and budgets.
 
 ## Apple native metadata and UI
 
@@ -1405,7 +1070,7 @@ conformance/vtable fixture.
   allows a host-permission-boundary-only result and explicitly reports
   `positive_e2e: false`; it must not be reported as capture/action proof.
   Both commands reject a changed executable digest and clean up the fixture
-  process and helper. These lanes require an interactive macOS desktop. See [native investigation](native-investigation.md)
+  process and helper. These lanes require an interactive macOS desktop. See [native investigation](../guides/native/native-investigation.md)
 
 `npm run verify:native-calls` needs macOS with Command Line Tools (`clang`,
 `lldb`, `codesign`, `nm`) and actual debugger access to the owned fixtures.
@@ -1443,7 +1108,7 @@ unknown chunks, depth limits and extracted child digests. The optional
 `REA_FIRMWARE_VERIFY_EXT4=1` lane requires existing mke2fs/debugfs; the separate
 `REA_FIRMWARE_VERIFY_GHIDRA=1` lane checks a selected host ELF through real Ghidra.
 Neither optional toolchain is a base-lane prerequisite. See
-[firmware analysis](firmware-analysis.md) for limits and unverified formats.
+[firmware analysis](../guides/firmware/firmware-analysis.md) for limits and unverified formats.
 
 ### JavaScript source recovery
 
@@ -1484,7 +1149,7 @@ npm run verify:browser:source-maps
 checks an installed package after building the verifier dependencies. The separate
 conditional `real-web-source-map` CI job supplies Chrome and an isolated pinned
 fixture compiler; static/unit checks do not acquire a browser. See
-[the source location guide](web-source-location.md) for the verified decoder profile.
+[the source location guide](../guides/web/web-source-location.md) for the verified decoder profile.
 
 ### JavaScript large-output lane
 
@@ -1511,7 +1176,7 @@ An optional entrypoint argument to `scripts/verify-browser-runtime.mjs` runs the
 same checks through an isolated installed package. The conditional
 `real-web-runtime` CI job runs only for relevant changes and needs no fixture
 compiler. Ordinary unit/static gates acquire no browser. See
-[website runtime attribution](web-runtime.md) for effects, resource bounds and
+[website runtime attribution](../guides/web/web-runtime.md) for effects, resource bounds and
 coverage limits.
 
 ### Offline binary layout
@@ -1564,58 +1229,6 @@ This is fixture evidence, not a sandbox claim. Inputs remain unchanged and the
 sentinel must stay alive; owned cleanup and empty verifier descendants are required. Pass an
 installed package entrypoint as the script's first argument for package coverage.
 
-### Exported environment bundles
-
-`npm run verify:agentenv:environment` is the `real-agentenv` lane. It requires
-the host's Docker CLI named by absolute `REA_DOCKER_COMMAND`, Python 3.12 with
-`agentenv-framework==0.9.1334` installed in a virtual environment whose
-`agent-env` binary is named by absolute `REA_AGENT_ENV_COMMAND`, and outbound
-network for `pip` on the runner and for `npm` inside the image build. Both
-variables are required; neither upstream executable is resolved from `PATH`,
-and the verifier installs nothing. Packing uses the shared npm helper, honoring
-`npm_execpath` from the caller's selected npm. Direct Node invocations without
-that value use the helper's platform fallback, so configure the pinned toolchain
-on `PATH` for those runs. It checks the supplied runner's `--version` against the pin before
-using Docker and retains the observed version in both passing and failing receipts.
-Its disposable CI runner creates the virtual environment in runner
-storage, exports both paths and uses the runner's own Docker; no developer host
-configuration changes. `agent-env run` attempts share one 22-minute budget
-inside the 30-minute job (the first attempt at most 15 minutes), so a hung or
-retried run ends with the verifier's failed receipt rather than the runner's
-kill. The framework builds its gateway and service-db
-images from `public.ecr.aws` on every fresh runner, and hosted runners share
-that registry's anonymous pull quota, so the lane first pulls the base images
-the pinned framework's Dockerfiles name from `mirror.gcr.io`, which serves the
-same Docker official images under the same digests, and names them as those
-Dockerfiles do (on Docker's containerd image store, so digest-pinned names
-resolve), as the framework's own CI does. The quota handling below covers
-anything still pulled from that registry. The receipt's `agent_env_run` records the
-last run whether it passed or failed, with `public_ecr_quota` set to
-`data_limit` or `rate` when that registry's `429 Too Many Requests` ended it.
-The data-transfer cap (`toomanyrequests: Data limit exceeded`) is counted per
-source IP, so it fails the lane at once: a pause on the same runner cannot lift
-it. When a rate refusal ends the run and at least five minutes of the budget
-would remain after the pause, the verifier waits 90 seconds and runs once more,
-recording `attempts: 2` and `retried_for` in the receipt. Any other failure
-ends the lane at once.
-
-The verifier writes the Grafana-shaped HAR the view tests own, inspects it and
-projects the `environment-manifest` view with all three template rules through
-the built CLI, packs the checkout with `npm pack`, exports the bundle with
-`--package-tarball` so the image installs this checkout rather than the
-registry package, and runs `agent-env run` on the bundle. It checks that the
-export reports the planned file set with the inputs copied byte-exact, that
-the runner exits `0` with `tasks/smoke.json` reported as passed and the
-verifier's description naming the tool count, and that no container exists
-after the run that did not exist before; the container inventory runs even when
-the run fails or times out, so a failed receipt still lists what it left. The one exception is the framework's
-own image-store helper, `agentenv-registry` (or `agentenv-registry-<port>`),
-a `registry:2` container the local provider starts on first use and keeps
-running across runs; a first run on a fresh host creates it, so the receipt
-lists it under `image_store_helpers` instead of counting it as a leak. Images
-built by the run remain and are counted in the receipt. Pass an installed
-package entrypoint as the script's first argument for package coverage.
-
 ## Agent evaluation and conformance records
 
 `npm run verify:agent` evaluates investigation scenarios through a real local
@@ -1652,12 +1265,7 @@ NUL-containing names. It compares exact WAT,
 section output and selected/tool digests through the compiled CLI and real MCP
 SDK, validates advertised schemas, checks identical CLI/MCP Evidence IDs and
 session bundle readback, retains invalid/truncated module diagnostics, preserves
-all inputs and checks workspace cleanup.
-The lane also injects one cleanup denial for exact private runtime roots and
-input descriptors, checks recovered CLI errors, and verifies retry on the same
-MCP connection after repeated runtime-removal denial. These are controlled
-faults, not naturally occurring permission failures; no WASM target is executed.
-Pass an installed package's
+all inputs and checks workspace cleanup. Pass an installed package's
 `scripts/rea.mjs` as the first argument to run the same lane against the package.
 `npm run verify:wasm:package` packs and installs REA into an isolated temporary
 prefix with lifecycle scripts disabled and runs the same required real-tool lane.

docs/development/tool-design.md

@@ -0,0 +1,94 @@
+# MCP tool design
+
+## Decide whether to add a tool
+
+Design around the analyst question. Inspect the current canonical contracts,
+provider capabilities, and nearest existing tool before changing the surface.
+Extend a tool when intent and result contract match; add one for a distinct
+outcome or materially different authority. Public names and semantics remain
+provider-neutral, with exact coverage reported per provider.
+
+Keep the catalog complete; report capability/session availability instead of
+truncating schemas. Serialized bytes alone do not establish agent usability.
+
+## Choose the tool shape
+
+| Shape                 | Use it for                                  | Result                                                                    |
+| --------------------- | ------------------------------------------- | ------------------------------------------------------------------------- |
+| `inspect`             | Facts about one target, object, or resource | Relevant fields, locations, and facet availability                        |
+| `search` / `list`     | Candidate discovery                         | Stable ordering and context; pagination when the query or format needs it |
+| `trace`               | Relationships across evidence               | Typed edges, supporting facts, and unresolved paths                       |
+| `compare`             | Explicitly paired artifacts or observations | Identity, comparable coverage, and supported deltas                       |
+| `workflow`            | A recurring outcome needing composition     | Inline answer, contributing evidence, and partial facets                  |
+| `observe` / `capture` | Runtime behavior                            | Authority, launch/attach effects, lifecycle, and cleanup status           |
+
+These are task shapes, not mandatory prefixes. Name tools for the action and
+object callers reason about. Avoid unrelated discovery/execution/mutation modes
+inside one tool.
+
+## Prefer primitives; compose workflows
+
+A primitive reports a reusable fact about an identified object or relationship.
+A format-specific decoder qualifies; one application's business interpretation
+belongs outside the general contract. Expose provider APIs when they add a
+useful capability that existing tools cannot express.
+
+Compose a workflow when repeated use demonstrates a multi-source outcome REA
+can join without hiding caller choices or uncertainty. Batch homogeneous reads
+when that removes repeated work while preserving per-item outcomes. Keep prompts
+optional and avoid prescribing call sequences that a direct tool can replace.
+
+Agents can compose experiments with ordinary commands, scripts, and local
+fixture servers. Custom orchestration languages, replay engines, or separate
+prepare/execute plans need an observed requirement those primitives cannot
+satisfy. A plan without execution does not establish runtime behavior.
+
+## Define the contract
+
+- Use strict inputs with explicit target identity and required fields. Preserve
+  meaningful target, action, capture, and output choices; remove ignored options
+  and repeated permission declarations.
+- Return the requested facts inline with artifact/provider identity, source
+  locations, Evidence references, coverage, and relevant confidence and
+  limitations. Use supported selection, summaries or views when they answer
+  the question; preserve access to complete source Evidence and honor existing
+  contracts and requested detail. Missing coverage is unknown, not absence.
+  Avoid extra lookups solely to understand the answer or its provenance.
+- Keep observed, derived, and inferred relationships distinct. Preserve
+  unresolved edges and partial provider facts instead of requiring every
+  provider to supply the same metadata.
+- For caller/callee reads, `relationship_coverage` describes only the
+  provider-observed direct relationship set. `complete` means that set was
+  returned without a known read limit; it does not claim every possible runtime
+  edge. Provider and execution caveats stay in `limitations` and do not imply
+  incomplete relationship coverage. Missing coverage remains `unknown`.
+- Declare process, filesystem, network, UI, and mutation effects truthfully;
+  enforce the requested target and lifecycle.
+- Add limits only for real format, protocol, authority, or measured resource
+  constraints. Report pagination, truncation, cancellation, and partial failure.
+  An assumed agent budget is insufficient justification for a limit.
+
+## Implement and evaluate
+
+Put provider protocols/parsing in adapters and shared CLI/MCP workflows in the
+application layer. Share Evidence provenance, unknown projection, and session
+retention semantics; matching payloads alone do not establish parity.
+
+Measure the resource before choosing a budget and enforce it before the costly
+step. Account for value alternatives, trace-frame products, retained records,
+serialization expansion, and temporary-file growth separately. Derive facet
+completeness from examined records and exhaustiveness, rather than diagnostic
+prose or an empty failure list. Preserve observations independently of cleanup
+success.
+
+Update canonical contracts, output schemas, examples, generated artifacts, and
+relevant docs together. Verify converted advertised schemas and success,
+malformed, unavailable, cancellation, and partial outcomes through affected
+consumers. Real-engine claims require the matching provider lane; see
+[testing.md](testing.md).
+
+When discoverability changes, evaluate representative broad, direct, and negative
+tasks on the intended host. Record host/model/catalog, selected tools, arguments,
+errors, retries, and task outcomes. Schema validity and keyword heuristics do not
+establish successful tool selection. See [mcp-contracts.md](../reference/mcp-contracts.md) for
+shipped runtime behavior.

docs/electron-fuses.md

@@ -1,87 +0,0 @@
-# Electron fuse state
-
-`inspect_electron_fuses` / `inspect-electron-fuses` answers whether a packaged
-Electron app will honor `--inspect` and `--inspect-brk`, `ELECTRON_RUN_AS_NODE`,
-embedded ASAR integrity validation, and loading application code only from
-`app.asar`. It reads the fuse wire stored in the Electron binary. It does not
-launch the app, modify fuse bytes, or use the network.
-
-```bash
-rea inspect-electron-fuses /Applications/Example.app --json
-```
-
-The CLI resolves a relative path against the caller's working directory. MCP
-requires an absolute filesystem path and preserves that exact selection:
-
-```json
-{
-  "name": "inspect_electron_fuses",
-  "arguments": { "path": "/Applications/Example.app" }
-}
-```
-
-On POSIX hosts, the CLI preserves path components so symlinks are followed
-before parent (`..`) steps. Bundle selections may end in `.` or parent steps
-through real directories; a terminal parent step through a directory symlink
-is rejected. Windows CLI paths retain native drive and separator resolution.
-
-Check this before `observe_javascript_runtime` with `electron-main`. When
-`EnableNodeCliInspectArguments` is disabled or removed, Electron ignores
-Inspector flags, and a later target listing can simply show no main-process
-target.
-
-## What is read
-
-On macOS, pass the `.app` bundle or the Electron Framework binary. Bundle and
-framework selection first tries the top-level `Electron Framework` binary,
-then `Versions/Current/Electron Framework`, then
-`Versions/A/Electron Framework`. Symlinks are followed only while they stay
-inside that framework.
-On Windows and Linux, pass the main Electron executable. The wire lives in
-that executable rather than in `app.asar`.
-
-The inline Evidence result contains:
-
-- the selected path, the resolved regular file, its SHA-256, size, and container
-  format (`mach-o`, `mach-o-universal`, `pe`, or `elf`);
-- one slice entry for a thin Mach-O, PE, or ELF file, and one entry per slice of
-  a universal Mach-O, with file-absolute `sentinel_offset` values;
-- `wire_version`, `declared_length`, and ordered fuses `{ index, name, state, raw_byte }`;
-- `sentinel_count`, including zero and more than one;
-- `runtime_implications`, each marked `relationship: "derivation"` and tied to
-  the fuse index it came from.
-
-Version 1 names, in index order, are `RunAsNode`, `EnableCookieEncryption`,
-`EnableNodeOptionsEnvironmentVariable`, `EnableNodeCliInspectArguments`,
-`EnableEmbeddedAsarIntegrityValidation`, `OnlyLoadAppFromAsar`,
-`LoadBrowserProcessSpecificV8Snapshot`, `GrantFileProtocolExtraPrivileges`,
-and `WasmTrapHandlers`. An index past that table, or any index on another wire
-version, keeps `name: null` and the raw byte.
-
-Wire bytes are `0x30` disabled, `0x31` enabled, and `0x72` removed. Any other
-byte is `unknown`. A removed fuse is not enabled: Inspector flags and
-`ELECTRON_RUN_AS_NODE` are not honored, and application code is not restricted
-to `app.asar`. On macOS and Windows, a removed or disabled
-`EnableEmbeddedAsarIntegrityValidation` byte means embedded ASAR integrity is
-not enforced, and an enabled byte means it is enforced. Electron compiles that
-validation only on macOS and Windows. On a Linux ELF executable the observed
-byte is preserved and the enforcement outcome is `unknown`.
-
-## Unknown and multiple sentinels
-
-No sentinel means the fuse state is unknown. It does not mean the fuses are
-disabled. A wire that continues past the slice is reported as truncated, with
-only the fuse bytes that were present. Two or more sentinels in one slice are
-all reported. REA does not pick one.
-
-Fuse bytes do not prove that the application enables Inspector some other way,
-for example through `app.commandLine` or a remote-debugging switch in
-application code.
-
-The selected file must be a regular file, or a bundle that resolves to one.
-Symlinks are followed only inside `Electron Framework.framework`. The reader
-admits at most 1 GiB, searches with 256 KiB windows, and keeps at most 32
-sentinels per slice. A real nine-fuse, one-slice result is about 1,200 CLI
-tokens; a two-slice result is about 1,300 tokens. Exact size varies with path
-lengths and limitations. This inspection creates no temporary files and does
-not modify the selected bytes.

docs/electron-observation.md

@@ -1,246 +0,0 @@
-# Electron file-page observation
-
-REA can attach to an Electron/Chromium CDP endpoint and inspect existing `file://` renderer pages without evaluating JavaScript or invoking Electron APIs. The request supplies the endpoint directly; REA accepts only literal-port loopback HTTP endpoints. Selecting an endpoint exposes every Electron target it serves, including local file paths and page metadata.
-
-Disconnecting the inspection's page session can clear caller-owned
-`navigator.platform` emulation inside Chromium. REA cannot restore another
-client's complete user-agent/client-hint configuration. Use a disposable target
-or let the owning client reapply its configuration; see the shared
-[CDP state limitation](browser-observation.md#provider-authorities).
-
-This passive runtime surface is distinct from the target-free static
-[`analyze_javascript_application`](javascript-artifact-reconstruction.md)
-workflow. Static analysis reads a local ASAR or extracted directory without
-executing application code. Passive observation inspects an existing Electron
-page. The results keep static inferences and runtime observations distinct.
-Packaged fuse state is a separate static read:
-[`inspect_electron_fuses`](electron-fuses.md) reports whether this binary will
-honor Inspector flags, `ELECTRON_RUN_AS_NODE`, embedded ASAR integrity, and
-`app.asar`-only loading.
-Use the separate
-[`reconcile_javascript_runtime`](javascript-runtime-reconciliation.md) workflow
-when both Evidence sets already exist.
-
-## Target boundary
-
-The request supplies a literal-port loopback endpoint and, for inspection, a
-target ID. REA accepts local hostless `file://` URLs that resolve to regular
-files, including pages a packaged application serves from inside `app.asar`.
-For those, the first `.asar` path component that is a regular file is the
-archive, the remainder must name a regular file in its header, and the reported
-path is the canonical archive path joined with that member. Remote hosts,
-encoded path separators, ASAR directories or links, and nonexistent paths are
-rejected. The endpoint exposes every eligible target and its local path
-metadata.
-
-Cancellation stops further file authorization after an already-started filesystem
-operation settles. ASAR descriptor-close failures remain typed incomplete cleanup
-with an exact retryable owner; they are not treated as a missing or unauthorized
-page. A later authorization and provider shutdown retry retained descriptors
-before reporting their release.
-
-## Workflow
-
-`list_electron_targets` returns every eligible target served by the supplied endpoint in one inline array.
-
-For the MCP follow-up call, pass the same literal-loopback endpoint and the selected target ID to `inspect_electron_page`. REA rediscovers targets and validates the ID against the live endpoint before inspection.
-
-```bash
-rea list-electron-targets http://127.0.0.1:9223 --json
-rea inspect-electron-page http://127.0.0.1:9223 TARGET_ID \
-  --observation-ms 100 --json
-```
-
-Script content is excluded by default. Setting `include_script_sources` in the
-request returns the selected target's script sources:
-
-```bash
-rea inspect-electron-page http://127.0.0.1:9223 TARGET_ID \
-  --include-script-sources \
-  --json
-```
-
-The normalized result contains canonical local paths, frame and DOM
-structure, resource metadata, stable script/resource identities, explicit
-completeness, and content-addressed script artifacts. Resource sizes are unknown
-when omitted or invalid; supplied invalid sizes also produce an explicit
-completeness diagnostic.
-
-DOM node indices retain their snapshot positions. Invalid rows are omitted with
-completeness diagnostics, so `total_nodes` can exceed the retained node count
-and a parent index can refer to an omitted source node.
-
-Script metadata retains its execution-context frame ID when CDP supplies one. The capture also
-inventories worker, service-worker, and shared-worker targets with
-validated opener-target and parent-frame IDs. Worker discovery uses passive
-target metadata; REA does not attach to or execute code in those targets.
-Script-source collection retains at most 32 MiB of UTF-8 text across scripts
-and shares a 20-second collection deadline. Omitted sources retain their script
-metadata and an explicit reason; later smaller sources may still fit after an
-oversized source is omitted. The separate 64 MiB CDP response limit bounds one
-wire message before retention admission, rather than total transient memory.
-The source budget adds no script-count cap. Like every
-target, frame, script, and resource, a worker URL must resolve to a local
-file before it is retained. Relationship IDs improve
-attribution but do not prove which static module started a worker or that its
-work completed.
-
-Inspection does not retain DOM values, execute renderer code, navigate, click,
-invoke Electron IPC, close a target, or terminate the application.
-
-## Active Electron scenarios
-
-The scenario request supplies the Electron executable and application entry
-point, plus any arguments and actions. The application root defaults to the
-entry point's parent directory and can be supplied when the app uses a different
-root. REA launches that executable through
-the official Playwright Electron API and owns its lifetime. It accepts click/wait actions,
-window-targeted renderer reload/crash actions, and synthetic `open-url` or
-`second-instance` deep-link delivery. It records capture-scoped window and
-WebContents identities, process metrics, and IPC channel and value-shape metadata.
-Payload values are not retained.
-
-Run the real fixture verifier with an operator-provided Electron runtime:
-
-```bash
-REA_ELECTRON_EXECUTABLE=/absolute/path/to/electron npm run verify:electron
-```
-
-This operation actively launches and interacts with the selected target. It is
-not a passive CDP observation. The owned process keeps normal host filesystem
-and network privileges, so lifecycle ownership does not make it a sandbox.
-
-The CLI and MCP surfaces accept the same schema. For a JSON request file:
-
-```bash
-rea capture-electron-scenario scenario.json --json
-```
-
-The result records action status and targets, correlated app/window/WebContents,
-preload, session, navigation, shell, permission, popup, download, protocol,
-native-addon, process, and IPC timeline events. IPC channels and argument-shape
-metadata retain their observed lengths; payload values are never retained.
-Renderer crash/restart and deep-link actions are synthetic
-scenario controls; their attempted and observed outcomes remain in the
-timeline. The active hook blocks and records external shell/navigation,
-permission, download, popup, updater, and OS-integration effects. The timeline
-is explicitly partial when attachment starts after application activity. The
-startup, including the initial state snapshot, has a 60-second deadline.
-Actions wait until completion or request cancellation; a click whose target
-never appears, or a `wait` without `window_index` in an app that opens no
-window, remains pending until cancelled. After cancellation, the final state
-read has 5 seconds before REA keeps the initial snapshot instead; the
-cancellation keeps the caller's reason and records that expiry in its
-diagnostics.
-Blocked synchronous shell APIs keep their return contracts:
-`showItemInFolder` returns `undefined` and `writeShortcutLink` returns `false`.
-Their `shell-attempt` events record the blocked phase and argument shapes;
-neither result means the requested host operation occurred. The existing
-`openExternal` and `openPath` blocks continue to reject their promises.
-CLI SIGINT/SIGTERM requests cancellation and awaits owned-process cleanup.
-Window IDs, URLs, and cached titles come from one main-process Electron snapshot,
-so a crashed renderer does not require a successful renderer-side title query.
-Window instrumentation uses Electron's window-created event, including runtimes
-with a read-only `BrowserWindow` export. Preload configuration comes from the
-window's runtime metadata, including Electron's optional internal preload
-descriptor when web preferences omit it. This descriptor is verified on
-Electron 44.7.0; runtimes that expose neither representation retain an unavailable
-path. A configured path or working IPC handler does not prove preload execution.
-If cleanup cannot be verified, the error retains collected observations in
-`details.partial_observation` and marks their application cleanup `unverified`.
-Cleanup uncertainty does not authorize signaling unrelated processes.
-
-Main-process IPC recording keeps original-function removal for `on` and `once`
-registrations and records a fired `once` callback once. Native Node.js owns
-`once` registration, firing and callable dispatch as well as removal order and
-traversal, including listeners registered by removal observers;
-the hook translates only its own recording wrappers at the removal boundary.
-Wrapper metadata uses weak keys and does not retain removed registrations.
-Wrapper metadata operations, private collection methods and traversal constructors are captured
-before target startup; later replacement of their global bindings does not
-change listener registration or removal.
-
-Native runtimes differ in whether `once` consults callback `.call` or `.apply`.
-The hook observes actual callback entry without imposing another runtime's
-property reads or argument-list representation. Application methods selected by
-native dispatch keep their original receiver and argument-list object; opaque
-methods produce a `custom-call` or `custom-apply` observation gap when callback
-execution cannot be established.
-
-If native wrapper creation or registration-method lookup could expose private
-instrumentation through an application getter, setter or Proxy, registration
-stays native and unwrapped. The `once-metadata` observation gap identifies that
-unobserved registration attempt; it does not prove registration or delivery. The original callback,
-metadata writes and native method receivers are preserved, including when
-registration fails. Later registrations resume normal observation. Non-callable
-`call`/`apply` properties produce failed observation gaps when native dispatch reads
-them; callback entry is not fabricated.
-
-An `on` listener's application-defined `.apply` receives the original argument-list
-object unchanged. Borrowing the exposed method preserves its dynamic receiver.
-Because that method owns argument interpretation and may not
-invoke the callback, the hook records a bounded `ipc-observation-gap` timeline
-entry with the registered channel rather than an IPC invocation. Its empty
-`argument_shapes` means unobserved arguments, not a zero-argument callback;
-callback execution and result remain unknown. Coverage and retention include
-these gaps even when their individual records are dropped. Normal native
-dispatch continues to record actual invocation frames. Evidence snapshots copy
-retained arrays and counters without invoking application iterators or Array
-species.
-
-Listener-chain recognition distinguishes owned, unowned and unknown metadata.
-Data links may be inherited; absence is established only after completing the
-bounded prototype lookup. Exhausting either walk, encountering a getter or seeing a Proxy leaves
-ownership unknown. The hook preserves native registration without adding another
-recording wrapper and retains a `listener-chain` observation gap after successful
-registration. This gap does not prove IPC delivery. An existing inner recording
-wrapper can still report its actual invocation; otherwise callback activity
-remains unobserved. Setter-only properties have a known undefined read.
-Data-descriptor parsing is shared with removal normalization.
-
-This does not establish complete JavaScript function introspection equivalence.
-Caller-defined `.listener` properties can change the identity exposed by
-`listeners()` and meta-events; accessors and Proxy metadata are not followed for
-wrapper recognition. Re-registering a raw recording wrapper on another channel
-retains the original registration's channel attribution.
-Mutating `.listener` on a raw recording wrapper can also prevent removal through
-application decorators that bypass the hook's removal methods. When a removal
-request reaches the hook's methods and its registration order is known, private
-callback ownership preserves removal by the original function and the newest
-matching registration when public metadata is changed or deleted. Native removal
-still determines getter execution, exceptions and removal meta-events.
-
-If registration or removal methods differ from the Node methods captured at hook
-initialization, the hook leaves listener callbacks unwrapped and records a
-`listener-registration` observation gap. The application keeps its original
-callback and receiver; callback execution remains unobserved. This comparison
-assumes Node's EventEmitter prototype has not itself been globally decorated
-before hook initialization. The provider loads the hook before the application
-and excludes `NODE_OPTIONS` from the child environment.
-
-An opaque later listener or unsupported emitter state can prevent proof of
-removal order. The hook then delegates removal
-to the native method and records a `listener-removal` gap rather than claiming
-which registration was removed. These gaps are distinct from dropped records
-and do not establish IPC delivery or successful removal.
-
-### Target fuse prerequisites
-
-Active scenario capture requires that the target Electron executable honors Node CLI inspector flags (`--inspect` or `--remote-debugging-port`) so that Playwright can establish its DevTools protocol session.
-
-When an Electron executable explicitly disables the `EnableNodeCliInspectArguments` fuse (or removes the capability), `capture-electron-scenario` fails immediately before process launch with an `AnalysisUnsupportedTargetError` ("unsupported_target") rather than waiting for the startup deadline. For targets with disabled inspector fuses, use passive CDP inspection via `inspect_electron_page` or run against an unrestricted development binary with the extracted `app.asar`.
-
-The real verifier exercises compiled CLI and stdio MCP discovery, page/script
-inspection, static/runtime reconciliation, active observation, and CLI SIGTERM
-cleanup before checking the IPC, renderer crash/reload, utility/child-process,
-deep-link, and blocked-effect fixture. A cleanup error keeps the full lane failed
-even when the retained capture contains useful observations.
-
-Active Electron Evidence can also be supplied to
-[`reconcile_javascript_runtime`](javascript-runtime-reconciliation.md). That
-projection is intentionally target-only and partial: it binds the selected
-application path and capture outcome to the static graph, while frames, scripts,
-workers, and execution claims remain unavailable until a separate passive runtime
-capture provides them.
-
-ASAR observation reads the header through one open file handle, validates its declared lengths against the archive size, and limits encoded JSON headers to 16 MiB before parsing. The header cache also retains at most 16 MiB of encoded headers across eight archives. Oversized headers produce a scope refusal.

docs/error-contract.schema.json

@@ -28,33 +28,6 @@
           "required": ["action"],
           "additionalProperties": false
         },
-        "recovery": {
-          "oneOf": [
-            {
-              "type": "object",
-              "properties": {
-                "kind": { "type": "string", "const": "inspect_input_contract" },
-                "operation": { "type": "string", "minLength": 1 }
-              },
-              "required": ["kind", "operation"],
-              "additionalProperties": false
-            },
-            {
-              "type": "object",
-              "properties": {
-                "kind": { "type": "string", "const": "inspect_timeout_state" },
-                "operation": { "type": "string", "minLength": 1 },
-                "timeout_ms": {
-                  "type": "integer",
-                  "exclusiveMinimum": 0,
-                  "maximum": 9007199254740991
-                }
-              },
-              "required": ["kind", "operation", "timeout_ms"],
-              "additionalProperties": false
-            }
-          ]
-        },
         "details": {
           "type": "object",
           "propertyNames": { "type": "string" },
@@ -91,33 +64,6 @@
           "required": ["action"],
           "additionalProperties": false
         },
-        "recovery": {
-          "oneOf": [
-            {
-              "type": "object",
-              "properties": {
-                "kind": { "type": "string", "const": "inspect_input_contract" },
-                "operation": { "type": "string", "minLength": 1 }
-              },
-              "required": ["kind", "operation"],
-              "additionalProperties": false
-            },
-            {
-              "type": "object",
-              "properties": {
-                "kind": { "type": "string", "const": "inspect_timeout_state" },
-                "operation": { "type": "string", "minLength": 1 },
-                "timeout_ms": {
-                  "type": "integer",
-                  "exclusiveMinimum": 0,
-                  "maximum": 9007199254740991
-                }
-              },
-              "required": ["kind", "operation", "timeout_ms"],
-              "additionalProperties": false
-            }
-          ]
-        },
         "details": {
           "type": "object",
           "propertyNames": { "type": "string" },
@@ -154,33 +100,6 @@
           "required": ["action"],
           "additionalProperties": false
         },
-        "recovery": {
-          "oneOf": [
-            {
-              "type": "object",
-              "properties": {
-                "kind": { "type": "string", "const": "inspect_input_contract" },
-                "operation": { "type": "string", "minLength": 1 }
-              },
-              "required": ["kind", "operation"],
-              "additionalProperties": false
-            },
-            {
-              "type": "object",
-              "properties": {
-                "kind": { "type": "string", "const": "inspect_timeout_state" },
-                "operation": { "type": "string", "minLength": 1 },
-                "timeout_ms": {
-                  "type": "integer",
-                  "exclusiveMinimum": 0,
-                  "maximum": 9007199254740991
-                }
-              },
-              "required": ["kind", "operation", "timeout_ms"],
-              "additionalProperties": false
-            }
-          ]
-        },
         "details": {
           "type": "object",
           "propertyNames": { "type": "string" },
@@ -217,33 +136,6 @@
           "required": ["action"],
           "additionalProperties": false
         },
-        "recovery": {
-          "oneOf": [
-            {
-              "type": "object",
-              "properties": {
-                "kind": { "type": "string", "const": "inspect_input_contract" },
-                "operation": { "type": "string", "minLength": 1 }
-              },
-              "required": ["kind", "operation"],
-              "additionalProperties": false
-            },
-            {
-              "type": "object",
-              "properties": {
-                "kind": { "type": "string", "const": "inspect_timeout_state" },
-                "operation": { "type": "string", "minLength": 1 },
-                "timeout_ms": {
-                  "type": "integer",
-                  "exclusiveMinimum": 0,
-                  "maximum": 9007199254740991
-                }
-              },
-              "required": ["kind", "operation", "timeout_ms"],
-              "additionalProperties": false
-            }
-          ]
-        },
         "details": {
           "type": "object",
           "propertyNames": { "type": "string" },
@@ -280,33 +172,6 @@
           "required": ["action"],
           "additionalProperties": false
         },
-        "recovery": {
-          "oneOf": [
-            {
-              "type": "object",
-              "properties": {
-                "kind": { "type": "string", "const": "inspect_input_contract" },
-                "operation": { "type": "string", "minLength": 1 }
-              },
-              "required": ["kind", "operation"],
-              "additionalProperties": false
-            },
-            {
-              "type": "object",
-              "properties": {
-                "kind": { "type": "string", "const": "inspect_timeout_state" },
-                "operation": { "type": "string", "minLength": 1 },
-                "timeout_ms": {
-                  "type": "integer",
-                  "exclusiveMinimum": 0,
-                  "maximum": 9007199254740991
-                }
-              },
-              "required": ["kind", "operation", "timeout_ms"],
-              "additionalProperties": false
-            }
-          ]
-        },
         "details": {
           "type": "object",
           "propertyNames": { "type": "string" },
@@ -343,33 +208,6 @@
           "required": ["action"],
           "additionalProperties": false
         },
-        "recovery": {
-          "oneOf": [
-            {
-              "type": "object",
-              "properties": {
-                "kind": { "type": "string", "const": "inspect_input_contract" },
-                "operation": { "type": "string", "minLength": 1 }
-              },
-              "required": ["kind", "operation"],
-              "additionalProperties": false
-            },
-            {
-              "type": "object",
-              "properties": {
-                "kind": { "type": "string", "const": "inspect_timeout_state" },
-                "operation": { "type": "string", "minLength": 1 },
-                "timeout_ms": {
-                  "type": "integer",
-                  "exclusiveMinimum": 0,
-                  "maximum": 9007199254740991
-                }
-              },
-              "required": ["kind", "operation", "timeout_ms"],
-              "additionalProperties": false
-            }
-          ]
-        },
         "details": {
           "type": "object",
           "propertyNames": { "type": "string" },
@@ -406,33 +244,6 @@
           "required": ["action"],
           "additionalProperties": false
         },
-        "recovery": {
-          "oneOf": [
-            {
-              "type": "object",
-              "properties": {
-                "kind": { "type": "string", "const": "inspect_input_contract" },
-                "operation": { "type": "string", "minLength": 1 }
-              },
-              "required": ["kind", "operation"],
-              "additionalProperties": false
-            },
-            {
-              "type": "object",
-              "properties": {
-                "kind": { "type": "string", "const": "inspect_timeout_state" },
-                "operation": { "type": "string", "minLength": 1 },
-                "timeout_ms": {
-                  "type": "integer",
-                  "exclusiveMinimum": 0,
-                  "maximum": 9007199254740991
-                }
-              },
-              "required": ["kind", "operation", "timeout_ms"],
-              "additionalProperties": false
-            }
-          ]
-        },
         "details": {
           "type": "object",
           "propertyNames": { "type": "string" },
@@ -469,33 +280,6 @@
           "required": ["action"],
           "additionalProperties": false
         },
-        "recovery": {
-          "oneOf": [
-            {
-              "type": "object",
-              "properties": {
-                "kind": { "type": "string", "const": "inspect_input_contract" },
-                "operation": { "type": "string", "minLength": 1 }
-              },
-              "required": ["kind", "operation"],
-              "additionalProperties": false
-            },
-            {
-              "type": "object",
-              "properties": {
-                "kind": { "type": "string", "const": "inspect_timeout_state" },
-                "operation": { "type": "string", "minLength": 1 },
-                "timeout_ms": {
-                  "type": "integer",
-                  "exclusiveMinimum": 0,
-                  "maximum": 9007199254740991
-                }
-              },
-              "required": ["kind", "operation", "timeout_ms"],
-              "additionalProperties": false
-            }
-          ]
-        },
         "details": {
           "type": "object",
           "propertyNames": { "type": "string" },
@@ -532,33 +316,6 @@
           "required": ["action"],
           "additionalProperties": false
         },
-        "recovery": {
-          "oneOf": [
-            {
-              "type": "object",
-              "properties": {
-                "kind": { "type": "string", "const": "inspect_input_contract" },
-                "operation": { "type": "string", "minLength": 1 }
-              },
-              "required": ["kind", "operation"],
-              "additionalProperties": false
-            },
-            {
-              "type": "object",
-              "properties": {
-                "kind": { "type": "string", "const": "inspect_timeout_state" },
-                "operation": { "type": "string", "minLength": 1 },
-                "timeout_ms": {
-                  "type": "integer",
-                  "exclusiveMinimum": 0,
-                  "maximum": 9007199254740991
-                }
-              },
-              "required": ["kind", "operation", "timeout_ms"],
-              "additionalProperties": false
-            }
-          ]
-        },
         "details": {
           "type": "object",
           "propertyNames": { "type": "string" },
@@ -595,33 +352,6 @@
           "required": ["action"],
           "additionalProperties": false
         },
-        "recovery": {
-          "oneOf": [
-            {
-              "type": "object",
-              "properties": {
-                "kind": { "type": "string", "const": "inspect_input_contract" },
-                "operation": { "type": "string", "minLength": 1 }
-              },
-              "required": ["kind", "operation"],
-              "additionalProperties": false
-            },
-            {
-              "type": "object",
-              "properties": {
-                "kind": { "type": "string", "const": "inspect_timeout_state" },
-                "operation": { "type": "string", "minLength": 1 },
-                "timeout_ms": {
-                  "type": "integer",
-                  "exclusiveMinimum": 0,
-                  "maximum": 9007199254740991
-                }
-              },
-              "required": ["kind", "operation", "timeout_ms"],
-              "additionalProperties": false
-            }
-          ]
-        },
         "details": {
           "type": "object",
           "propertyNames": { "type": "string" },
@@ -658,82 +388,25 @@
           "required": ["action"],
           "additionalProperties": false
         },
-        "recovery": {
-          "oneOf": [
-            {
-              "type": "object",
-              "properties": {
-                "kind": { "type": "string", "const": "inspect_input_contract" },
-                "operation": { "type": "string", "minLength": 1 }
-              },
-              "required": ["kind", "operation"],
-              "additionalProperties": false
-            },
-            {
-              "type": "object",
-              "properties": {
-                "kind": { "type": "string", "const": "inspect_timeout_state" },
-                "operation": { "type": "string", "minLength": 1 },
-                "timeout_ms": {
-                  "type": "integer",
-                  "exclusiveMinimum": 0,
-                  "maximum": 9007199254740991
-                }
-              },
-              "required": ["kind", "operation", "timeout_ms"],
-              "additionalProperties": false
-            }
-          ]
-        },
         "details": {
-          "anyOf": [
-            {
-              "type": "object",
-              "properties": {
-                "logical_path": { "type": "string" },
-                "declared_sha256": {
-                  "anyOf": [{ "type": "string" }, { "type": "null" }]
-                },
-                "calculated_sha256": {
-                  "anyOf": [{ "type": "string" }, { "type": "null" }]
-                },
-                "unpacked": { "type": "boolean" }
-              },
-              "required": [
-                "logical_path",
-                "declared_sha256",
-                "calculated_sha256",
-                "unpacked"
-              ],
-              "additionalProperties": false
+          "type": "object",
+          "properties": {
+            "logical_path": { "type": "string" },
+            "declared_sha256": {
+              "anyOf": [{ "type": "string" }, { "type": "null" }]
             },
-            {
-              "type": "object",
-              "properties": {
-                "logical_path": { "type": "string" },
-                "algorithm": { "type": "string", "const": "md5" },
-                "declared_md5": {
-                  "type": "string",
-                  "pattern": "^[a-f0-9]{32}$"
-                },
-                "calculated_md5": {
-                  "anyOf": [
-                    { "type": "string", "pattern": "^[a-f0-9]{32}$" },
-                    { "type": "null" }
-                  ]
-                },
-                "unpacked": { "type": "boolean" }
-              },
-              "required": [
-                "logical_path",
-                "algorithm",
-                "declared_md5",
-                "calculated_md5",
-                "unpacked"
-              ],
-              "additionalProperties": false
-            }
-          ]
+            "calculated_sha256": {
+              "anyOf": [{ "type": "string" }, { "type": "null" }]
+            },
+            "unpacked": { "type": "boolean" }
+          },
+          "required": [
+            "logical_path",
+            "declared_sha256",
+            "calculated_sha256",
+            "unpacked"
+          ],
+          "additionalProperties": false
         }
       },
       "required": [
@@ -773,33 +446,6 @@
           "required": ["action"],
           "additionalProperties": false
         },
-        "recovery": {
-          "oneOf": [
-            {
-              "type": "object",
-              "properties": {
-                "kind": { "type": "string", "const": "inspect_input_contract" },
-                "operation": { "type": "string", "minLength": 1 }
-              },
-              "required": ["kind", "operation"],
-              "additionalProperties": false
-            },
-            {
-              "type": "object",
-              "properties": {
-                "kind": { "type": "string", "const": "inspect_timeout_state" },
-                "operation": { "type": "string", "minLength": 1 },
-                "timeout_ms": {
-                  "type": "integer",
-                  "exclusiveMinimum": 0,
-                  "maximum": 9007199254740991
-                }
-              },
-              "required": ["kind", "operation", "timeout_ms"],
-              "additionalProperties": false
-            }
-          ]
-        },
         "details": {
           "type": "object",
           "propertyNames": { "type": "string" },
@@ -836,33 +482,6 @@
           "required": ["action"],
           "additionalProperties": false
         },
-        "recovery": {
-          "oneOf": [
-            {
-              "type": "object",
-              "properties": {
-                "kind": { "type": "string", "const": "inspect_input_contract" },
-                "operation": { "type": "string", "minLength": 1 }
-              },
-              "required": ["kind", "operation"],
-              "additionalProperties": false
-            },
-            {
-              "type": "object",
-              "properties": {
-                "kind": { "type": "string", "const": "inspect_timeout_state" },
-                "operation": { "type": "string", "minLength": 1 },
-                "timeout_ms": {
-                  "type": "integer",
-                  "exclusiveMinimum": 0,
-                  "maximum": 9007199254740991
-                }
-              },
-              "required": ["kind", "operation", "timeout_ms"],
-              "additionalProperties": false
-            }
-          ]
-        },
         "details": {
           "type": "object",
           "propertyNames": { "type": "string" },
@@ -899,33 +518,6 @@
           "required": ["action"],
           "additionalProperties": false
         },
-        "recovery": {
-          "oneOf": [
-            {
-              "type": "object",
-              "properties": {
-                "kind": { "type": "string", "const": "inspect_input_contract" },
-                "operation": { "type": "string", "minLength": 1 }
-              },
-              "required": ["kind", "operation"],
-              "additionalProperties": false
-            },
-            {
-              "type": "object",
-              "properties": {
-                "kind": { "type": "string", "const": "inspect_timeout_state" },
-                "operation": { "type": "string", "minLength": 1 },
-                "timeout_ms": {
-                  "type": "integer",
-                  "exclusiveMinimum": 0,
-                  "maximum": 9007199254740991
-                }
-              },
-              "required": ["kind", "operation", "timeout_ms"],
-              "additionalProperties": false
-            }
-          ]
-        },
         "details": {
           "type": "object",
           "propertyNames": { "type": "string" },
@@ -962,33 +554,6 @@
           "required": ["action"],
           "additionalProperties": false
         },
-        "recovery": {
-          "oneOf": [
-            {
-              "type": "object",
-              "properties": {
-                "kind": { "type": "string", "const": "inspect_input_contract" },
-                "operation": { "type": "string", "minLength": 1 }
-              },
-              "required": ["kind", "operation"],
-              "additionalProperties": false
-            },
-            {
-              "type": "object",
-              "properties": {
-                "kind": { "type": "string", "const": "inspect_timeout_state" },
-                "operation": { "type": "string", "minLength": 1 },
-                "timeout_ms": {
-                  "type": "integer",
-                  "exclusiveMinimum": 0,
-                  "maximum": 9007199254740991
-                }
-              },
-              "required": ["kind", "operation", "timeout_ms"],
-              "additionalProperties": false
-            }
-          ]
-        },
         "details": {
           "type": "object",
           "propertyNames": { "type": "string" },
@@ -1025,33 +590,6 @@
           "required": ["action"],
           "additionalProperties": false
         },
-        "recovery": {
-          "oneOf": [
-            {
-              "type": "object",
-              "properties": {
-                "kind": { "type": "string", "const": "inspect_input_contract" },
-                "operation": { "type": "string", "minLength": 1 }
-              },
-              "required": ["kind", "operation"],
-              "additionalProperties": false
-            },
-            {
-              "type": "object",
-              "properties": {
-                "kind": { "type": "string", "const": "inspect_timeout_state" },
-                "operation": { "type": "string", "minLength": 1 },
-                "timeout_ms": {
-                  "type": "integer",
-                  "exclusiveMinimum": 0,
-                  "maximum": 9007199254740991
-                }
-              },
-              "required": ["kind", "operation", "timeout_ms"],
-              "additionalProperties": false
-            }
-          ]
-        },
         "details": {
           "type": "object",
           "propertyNames": { "type": "string" },
@@ -1088,33 +626,6 @@
           "required": ["action"],
           "additionalProperties": false
         },
-        "recovery": {
-          "oneOf": [
-            {
-              "type": "object",
-              "properties": {
-                "kind": { "type": "string", "const": "inspect_input_contract" },
-                "operation": { "type": "string", "minLength": 1 }
-              },
-              "required": ["kind", "operation"],
-              "additionalProperties": false
-            },
-            {
-              "type": "object",
-              "properties": {
-                "kind": { "type": "string", "const": "inspect_timeout_state" },
-                "operation": { "type": "string", "minLength": 1 },
-                "timeout_ms": {
-                  "type": "integer",
-                  "exclusiveMinimum": 0,
-                  "maximum": 9007199254740991
-                }
-              },
-              "required": ["kind", "operation", "timeout_ms"],
-              "additionalProperties": false
-            }
-          ]
-        },
         "details": {
           "type": "object",
           "propertyNames": { "type": "string" },
@@ -1151,33 +662,6 @@
           "required": ["action"],
           "additionalProperties": false
         },
-        "recovery": {
-          "oneOf": [
-            {
-              "type": "object",
-              "properties": {
-                "kind": { "type": "string", "const": "inspect_input_contract" },
-                "operation": { "type": "string", "minLength": 1 }
-              },
-              "required": ["kind", "operation"],
-              "additionalProperties": false
-            },
-            {
-              "type": "object",
-              "properties": {
-                "kind": { "type": "string", "const": "inspect_timeout_state" },
-                "operation": { "type": "string", "minLength": 1 },
-                "timeout_ms": {
-                  "type": "integer",
-                  "exclusiveMinimum": 0,
-                  "maximum": 9007199254740991
-                }
-              },
-              "required": ["kind", "operation", "timeout_ms"],
-              "additionalProperties": false
-            }
-          ]
-        },
         "details": {
           "type": "object",
           "propertyNames": { "type": "string" },
@@ -1214,33 +698,6 @@
           "required": ["action"],
           "additionalProperties": false
         },
-        "recovery": {
-          "oneOf": [
-            {
-              "type": "object",
-              "properties": {
-                "kind": { "type": "string", "const": "inspect_input_contract" },
-                "operation": { "type": "string", "minLength": 1 }
-              },
-              "required": ["kind", "operation"],
-              "additionalProperties": false
-            },
-            {
-              "type": "object",
-              "properties": {
-                "kind": { "type": "string", "const": "inspect_timeout_state" },
-                "operation": { "type": "string", "minLength": 1 },
-                "timeout_ms": {
-                  "type": "integer",
-                  "exclusiveMinimum": 0,
-                  "maximum": 9007199254740991
-                }
-              },
-              "required": ["kind", "operation", "timeout_ms"],
-              "additionalProperties": false
-            }
-          ]
-        },
         "details": {
           "type": "object",
           "propertyNames": { "type": "string" },
@@ -1277,33 +734,6 @@
           "required": ["action"],
           "additionalProperties": false
         },
-        "recovery": {
-          "oneOf": [
-            {
-              "type": "object",
-              "properties": {
-                "kind": { "type": "string", "const": "inspect_input_contract" },
-                "operation": { "type": "string", "minLength": 1 }
-              },
-              "required": ["kind", "operation"],
-              "additionalProperties": false
-            },
-            {
-              "type": "object",
-              "properties": {
-                "kind": { "type": "string", "const": "inspect_timeout_state" },
-                "operation": { "type": "string", "minLength": 1 },
-                "timeout_ms": {
-                  "type": "integer",
-                  "exclusiveMinimum": 0,
-                  "maximum": 9007199254740991
-                }
-              },
-              "required": ["kind", "operation", "timeout_ms"],
-              "additionalProperties": false
-            }
-          ]
-        },
         "details": {
           "type": "object",
           "propertyNames": { "type": "string" },

docs/frida-instrumentation.md

@@ -1,13 +0,0 @@
-# Frida instrumentation
-
-REA exposes Frida device and process discovery, attach or spawn sessions, and caller-authored JavaScript instrumentation through the CLI and MCP. The Node bindings are an optional package dependency and load only when a Frida operation runs. REA does not install Frida server on a target.
-
-For remote devices, pass a host with an optional port (`host[:port]`; bracket IPv6 addresses) and any token, certificate, origin, or keepalive options on that operation. The keepalive interval is measured in seconds, matching Frida Core 17.23.2. Authentication values are held only for the active call or session and are excluded from Evidence. Do not embed credentials in the endpoint address.
-
-MCP exposes `list_frida_devices`, `list_frida_processes`, `start_frida_session`, `load_frida_script`, `resume_frida_session`, `unload_frida_script`, `frida_session_status`, and `close_frida_session`. A spawned process starts paused so scripts can load first. Closing unloads session scripts and detaches. If a spawn remains paused, REA resumes it only after script cleanup or session detach confirms the instrumentation is released; if both cleanup paths fail, the target stays paused and the cleanup error is retained. REA never kills the target. MCP sessions end with the server process. The one-shot CLI command `instrument-with-frida` accepts one inline script or script file, observes messages for a bounded duration, and returns Evidence with the source hash and captured messages.
-
-Failed startup cleanup retains acquired Frida handles, including a paused spawn that has not attached, for later cleanup retries. Its remote connection stays leased until session detach and target resume complete. CLI commands await provider cleanup before returning; MCP retains these resources for cleanup when its server closes. Server shutdown stops admitting new Frida operations and waits for admitted startup, discovery, and queued work before releasing their resources. A failed cleanup remains reported and can be retried by closing the server again, rather than treating an unregistered session as fully released.
-
-Frida scripts execute inside the selected target with that process's memory, filesystem, and network authority. Message capture is bounded to 16 MiB and reports truncation. Script source is not stored in Evidence; its selected path and SHA-256 digest are. For a file, `source_sha256` identifies the original selected bytes. Invalid UTF-8 continues to use replacement decoding; Evidence then records that limitation and `raw_result.source_representation` with the encoding, decoding mode, and `loaded_source_sha256` of the UTF-8 string passed to Frida. Valid UTF-8 files and inline scripts do not need this additional representation fact. Evidence retains non-authentication target selection such as device or endpoint, mode, program or PID, and spawn arguments. Authentication values remain excluded. Results report the observed session and messages, while unsupported platform metadata remains unknown. A request cancelled before a Frida operation starts has no provider effects. If cancellation arrives during a native Frida call, REA waits for that call to return, then closes any session it created and returns the observed session as a partial observation. A cancelled script load on an existing session releases only its new script before queued operations can run; the session and previously loaded scripts remain available. If cancellation is observed when the native call returns, partial Evidence retains the source identity and captured messages even if that call rejects, including messages emitted during awaited cleanup. The caller's cancellation reason remains primary and a native rejection is retained as a sanitized diagnostic. A failure already observed before cleanup stays primary if cancellation arrives during cleanup. The cancellation cutoff is REA's observation of native completion, rather than a claim about unobservable native event order. `script_id` is REA's load-attempt identity. When creation rejects without returning a handle, `script_cleanup: "no_handle"` means REA acquired no handle to unload; it does not prove that the engine performed no work. Once the provider commits a successful load, later request cancellation does not unload that script; use `unload_frida_script` to release it. If script cleanup fails, the script remains owned and a paused target cannot resume until the pending instrumentation is released. Queued script loads, resumes, and unloads check cancellation before dispatching native effects. Cancellation Evidence separately reports whether a target resume was observed, whether instrumentation cleanup completed, and that final target liveness remains unknown. REA does not kill the target. Remote discovery retains its observations and reports a separate cleanup error if the temporary connection cannot be removed.
-
-The [Frida Core API](https://frida.re/docs/frida-core-api/) documents device management, sessions, and script loading; the [JavaScript API](https://frida.re/docs/javascript-api/) documents target-side instrumentation. [Luma](https://luma.frida.re/) is Frida's standalone GUI; REA does not automate or control it. `npm run verify:frida` requires a Linux host with the optional Frida binding and uses a short-lived local Node.js fixture created by the verifier. Add `-- --address HOST:PORT --pid PID` to run the separate remote attach lane against a caller-selected target. Mock tests do not establish real device/server compatibility.

docs/getting-started/cli.md

@@ -0,0 +1,309 @@
+# CLI and Evidence
+
+Use the CLI for a direct inspection or a script. It uses the same application
+workflows and evidence contracts as REA's MCP server. Each CLI invocation is a
+separate process; save results when you want to use them in a later command.
+
+## Run a command
+
+After [installing REA](installation.md), use `rea`. You can also run a command
+without a global installation:
+
+```bash
+npx -y rea-agents@latest analyze-javascript-application /absolute/path/to/app --json
+```
+
+Use an extracted application directory or an ASAR as the target. Static
+JavaScript analysis returns the application graph and Evidence directly.
+Generic `rea analyze PATH` selects this workflow for directories and `.asar`
+files when neither `--provider` nor `--snapshot` is supplied. See
+[JavaScript artifact reconstruction](../guides/javascript/javascript-artifact-reconstruction.md)
+for results, integrity checks and coverage.
+
+The complete application Evidence can be hundreds of megabytes for a real
+application. When an agent or a person reads the result, save it to a file and
+project a summary, a module page or one module from the saved Evidence:
+
+```bash
+rea analyze-javascript-application /absolute/path/to/app --json > app-evidence.json
+jq -c '{source: {kind: "inline", evidence: .}, view: {kind: "summary"}}' app-evidence.json > app-view.json
+rea inspect-analysis-view app-view.json
+```
+
+For example, a 334 MB Obsidian application Evidence file yields a summary view
+of about 10 KB. Replace the view with
+`{"kind": "page", "collection": "modules", "offset": 0, "limit": 32}` for a
+module page. See
+[JavaScript application workflows](../guides/javascript/javascript-application-workflows.md) for
+views, feature traces and comparisons that take the same saved Evidence.
+
+## Managed assemblies (.NET)
+
+For a .NET PE/CLI assembly, inspect its identity and deployment form before
+inspecting members. These commands read metadata and Common Intermediate
+Language (CIL) without loading or executing the assembly and require no native
+analysis engine:
+
+```bash
+rea inspect-managed-artifact /absolute/path/Assembly.dll --json
+rea inspect-managed-members /absolute/path/Assembly.dll --json
+rea inspect-managed-members /absolute/path/Assembly.dll --type Example.Parser --json
+```
+
+Replace `Example.Parser` with an exact `full_name` from the member inspection,
+or a declaring type name you already know. Omit `--type` to inspect all members,
+or repeat it to select several types.
+Selection limits decoding to the selected types; member references remain an
+assembly-wide inventory, so the output can still be large.
+
+Choose the workflow from the artifact's contents rather than its `.exe` or
+`.dll` extension. The managed parser requires PE/CLI metadata; it does not
+unpack .NET single-file hosts or decode IL2CPP metadata. NativeAOT method bodies
+require native analysis. See the [managed-code guide](../guides/managed/managed-code-analysis.md)
+for supported deployment forms, selection semantics, and coverage limits.
+
+## SQLite snapshots
+
+For a local database snapshot, use `rea inspect-sqlite-database PATH --json`.
+Add `--table NAME --row-limit 20` to read a bounded sample from an ordinary
+table. This command does not require a native analysis provider. See
+[SQLite database snapshots](../guides/data/sqlite-databases.md) for database/WAL identity,
+source-file handling and row-value semantics.
+
+## Native analysis
+
+Inspect embedded Go build metadata without installing Go or configuring a
+disassembler:
+
+```bash
+rea inspect-go-binary /absolute/path/to/program --json
+```
+
+The shared CLI/MCP workflow reports compiler version, modules, replacements,
+build settings, original bytes and SHA-256. See [Go binaries](../guides/native/go-binaries.md)
+for supported containers and absent or malformed metadata.
+
+Configure [Hopper or Ghidra](installation.md#hopper), or the
+[IDA adapter](../providers/ida-provider.md), before analyzing a native target. Substitute
+your target, search text and function name or address in these examples:
+
+```bash
+rea analyze /absolute/path/to/program --provider ghidra --json
+rea search /absolute/path/to/program "search" --provider ghidra --json
+rea function /absolute/path/to/program main --provider ghidra --json
+rea decompile /absolute/path/to/program 0x1000 --provider ghidra --json
+rea xrefs /absolute/path/to/program 0x1000 --provider ghidra --json
+rea trace /absolute/path/to/program "search" --provider ghidra --json
+```
+
+`analyze` and `inspect` share the native overview workflow. `function` returns
+a function dossier; `decompile` returns pseudocode. For assembly instructions
+alone, use `rea instructions`. A macOS `.app` bundle can be supplied directly.
+
+Run `rea --help` or a command's `--help` for arguments and output options.
+The [generated catalog](../reference/mcp-contracts.md#generated-catalog) lists all CLI commands and MCP
+tools. Provider-specific target support is described in the
+[native guide](../guides/native/native-investigation.md), [DOS guide](../providers/ghidra-dos.md),
+[raw binary guide](../providers/raw-binary.md), and
+[Windows Ghidra guide](../providers/windows-ghidra-p0.md).
+
+## Choose a provider
+
+List the available providers and their supported operations:
+
+```bash
+rea providers --json
+rea capabilities --json
+```
+
+These commands describe binary-session providers and auxiliary capabilities.
+For the complete MCP surface, use the connected server's tool list and the
+session's advertised availability; individual guides describe prerequisites.
+
+With automatic selection, REA uses the single available provider that supports
+the target. When several providers support it, select one explicitly:
+
+```bash
+rea analyze /absolute/path/to/program --provider hopper
+```
+
+Set `REA_ANALYSIS_PROVIDER` for a standing preference. An explicit `--provider`
+overrides it. In MCP, pass `provider_id` to `open_binary`:
+
+```json
+{
+  "path": "/absolute/path/to/program",
+  "provider_id": "hopper"
+}
+```
+
+The selected provider remains bound to the session until an explicit switch
+or close. Provider failures are returned with their original reason. For an
+`ambiguous` selection error, choose from `details.candidate_ids`; for
+`provider_unavailable`, run `rea doctor --provider ID --json` to diagnose the
+selected engine. See [task readiness](installation.md#check-readiness-for-your-task)
+and [provider selection](../reference/mcp-contracts.md#identity-and-discovery).
+
+The session reports work still in progress through `analysis_activity`.
+A client timeout can end its wait while the provider continues analyzing.
+`cleanup_incomplete` identifies resources whose shutdown or removal could not
+be verified. See [MCP contracts](../reference/mcp-contracts.md) for session lifecycle and
+[Ghidra first-query deadlines](../reference/mcp-contracts.md#ghidra-first-query-deadlines-and-recovery)
+for import, client timeouts and recovery.
+
+## Save and reuse analysis snapshots
+
+A snapshot retains successful analysis results for later queries. REA reuses
+an exact result when the target bytes, operation, parameters, provider and
+settings match. Mutations and cursor-dependent calls are excluded from the
+cache. Snapshot files are local and use owner-only permissions.
+
+Dispatching a metadata write invalidates the active session's snapshot cache,
+even if its reply fails: the provider may already have applied the write.
+Close and reopen the target before importing or saving another snapshot.
+
+Snapshots retain eligible target-scoped question histories in full, including
+mutation Evidence recorded while another target was active. Observations and
+related questions must still belong to the saved target. If those dependencies
+cannot be retained, the entire history is excluded instead of reverting the
+question to an earlier revision or disposition.
+
+```bash
+rea analyze /absolute/path/to/program --provider ghidra --snapshot /absolute/path/to/analysis/program.json
+# Repeat the same query to reuse its saved result.
+rea analyze /absolute/path/to/program --provider ghidra --snapshot /absolute/path/to/analysis/program.json
+```
+
+An exact CLI cache hit is normally read before starting a provider process.
+On Windows, Ghidra first admits the selected source through its native snapshot
+owner, so replay can start that provider.
+In MCP, `open_binary` accepts `snapshot_path` to import a snapshot atomically
+for its matching target; an MCP provider may still start before returning a
+cached result. `close_binary` accepts `snapshot_path` and optional
+`overwrite: true` to save before releasing provider resources. A failed save
+leaves the session open so the caller can resolve the output failure.
+
+The MCP save receipt reports `primitive_entries`, `workflow_entries`, and
+`evidence_records` separately. Zero primitive bindings can still accompany retained workflow
+results and Evidence. These are cached observations, not a saved provider
+database: only eligible exact queries can reuse a result, and new or live
+queries can still require provider startup. The CLI uses the same snapshot
+format and preserves these records when loading and updating it.
+
+## Import, export and compare Evidence
+
+Evidence records retain artifact identity, source locations, observations,
+inferences and unresolved findings. Validate an existing bundle, export its
+canonical form, or compare two supplied bundles:
+
+```bash
+rea evidence-import /absolute/path/to/evidence/bundle.json
+rea evidence-export /absolute/path/to/evidence/bundle.json /absolute/path/to/evidence/canonical.json
+rea compare /absolute/path/to/evidence/left.json /absolute/path/to/evidence/right.json
+```
+
+Exports preserve an existing destination unless `--overwrite` is explicit.
+For application traces and version comparisons, see
+[JavaScript application workflows](../guides/javascript/javascript-application-workflows.md).
+MCP [retained Evidence references](../reference/mcp-contracts.md#retained-application-evidence-inputs)
+belong to one connection. Separate CLI calls consume full saved records.
+
+## Import historical source
+
+Import an older source tree to compare with the current artifact:
+
+```bash
+rea import-reference-source /absolute/path/to/source
+rea import-reference-source /absolute/path/to/source --detail summary --outline-depth 2 --json
+```
+
+The default (`--detail full`) returns the complete `HistoricalSourceGraph`.
+Choose `--detail summary` for a `HistoricalSourceSummary` of that same committed
+inventory: its `HistoricalSourceManifest` contains the full graph and root
+digests, with provenance, VCS facts, languages, manifest paths, entry and
+relationship counts, parse-failure counts, file/directory states, exclusions
+and limitations. The summary is a presentation view, not a graph accepted by
+source-to-bundle comparison; keep the full output for that workflow.
+
+`--outline-depth` requires `--detail summary` and accepts a nonnegative safe
+integer. Depth 1 shows root children, depth 2 (the default) also shows their
+children, and depth 0 omits all outline entries. Paths retain canonical Unicode
+code-point order. `outline.omitted_entry_count` counts only inventoried entries
+hidden by the chosen depth; it does not count unexamined children of excluded or
+unreadable directories, or change `inventory_state`. Exclusions and source
+limitations remain separate from this presentation omission.
+
+`file_sizes.known_bytes` is the exact sum of known inventoried file sizes as
+decimal text, so large sums cannot lose integer precision. Unknown sizes count
+in `file_sizes.unknown_file_count`; excluded or unexamined paths are not included
+in that total. A zero known-byte sum therefore does not establish an empty source
+tree. Full output retains individual file hashes, relationships and parse-failure
+diagnostics. Summary mode performs the same import and cleanup, then projects
+the committed result without rereading source files. It reduces the selected
+output, not the amount of source examined. A shallow tree or many exclusions can
+still produce a large summary; depth 0 removes the outline but preserves the
+other facts. No fixed output-size or runtime improvement is promised.
+
+The import records hashes and metadata for the supplied files, separately
+from observations of the current app. For a directory inside a Git checkout,
+it records the HEAD of the nearest enclosing repository; whether the working
+tree matches that commit remains unknown. It honors the source tree's `.gitignore`
+and applies default exclusions for common generated and dependency paths such
+as `node_modules/`, `dist/`, and `*.log`. Pattern-based exclusions record the
+matched pattern and whether it came from project, default, caller, or sensitive
+path policy. Set `REA_REFERENCE_SECRET_PATTERNS_JSON` to a JSON array of ignore
+patterns when you want to mark selected paths as sensitive; those patterns are
+reported separately as configured-secret exclusions.
+
+Re-import saved graphs whose pattern-based exclusions lack `pattern` before
+using them in source-to-bundle comparisons.
+
+JavaScript and TypeScript import parsing requires valid UTF-8. Malformed source
+bytes retain their original hashes and sizes with a decoding diagnostic; REA
+does not infer module targets from replacement characters.
+
+Historical-source import requires safe no-follow file opens on Linux or
+macOS. Native Windows returns `unsupported_host`; use Linux REA inside WSL
+or another supported host. See
+[source-to-bundle comparison](../guides/javascript/javascript-application-workflows.md#historical-source-to-bundle-comparison)
+for mapping identities, inferences and unknowns.
+
+## Capture runtime behavior
+
+Choose the guide for the target and intended interaction:
+
+- [Browser observation](../guides/web/browser-observation.md): inspect a selected page through CDP.
+- [Browser scenarios](../guides/web/browser-scenario-contract.md): run declared interactions and capture their results.
+- [Electron observation](../guides/javascript/electron-observation.md): inspect an Electron renderer or capture an application scenario.
+- [Node/Electron Inspector](../guides/javascript/javascript-runtime-observation.md): record script locations and execution contexts.
+- [Process capture](../guides/runtime/process-capture.md): run an executable and compare terminal, exit and filesystem observations.
+
+Runtime requests name the target and actions. Launched targets run with your
+user permissions; consult the chosen guide for host requirements and effects.
+
+## Output and exit status
+
+The default terminal format is TOON. Use `--json` when saving results for a
+JSON consumer. `--json` is indented on a terminal and compact when piped or
+redirected, which keeps large results smaller for agents and scripts; pipe
+through `jq .` for indented files. Output selection and formatting do not change
+operation status.
+
+| Status    | Meaning                                                                                                                                              |
+| --------- | ---------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `0`       | The operation completed. Its result may include partial evidence, warnings or unresolved questions.                                                  |
+| `1`       | The operation could not complete. Structured output identifies invalid input, permissions, cancellation, timeouts or another failure when available. |
+| `128 + N` | Signal `N` ended the process, where the shell or runtime preserves the conventional signal-derived status.                                           |
+
+`setup --dry-run` returns `planned` and exits `0`; a cancelled setup also exits
+`0`. Setup returns `1` for `needs_confirmation` or `needs_human`.
+`doctor` returns `1` when required checks in its selected readiness scope fail;
+unavailable optional providers remain informational for unrelated tasks.
+
+Enable `pipefail` in a supporting shell so a downstream formatter preserves
+REA's failure status:
+
+```bash
+set -o pipefail
+rea inspect-artifact ./app.asar --json | jq . > inspection.json
+```

docs/getting-started/client-configuration.md

@@ -10,7 +10,7 @@ acceptance is verified only where explicitly recorded.
 
 Connect Fiddler Everywhere's MCP server separately for HTTP traffic debugging,
 preserving your REA client entry. See the
-[setup instructions and public skills](web-network-captures.md#fiddler-everywhere-mcp-and-public-skills).
+[setup instructions and public skills](../guides/web/web-network-captures.md#fiddler-everywhere-mcp-and-public-skills).
 
 ## GitHub Copilot CLI
 
@@ -31,7 +31,7 @@ tool inventory on Linux using a loopback model fixture. After setup, add
 settings, then restart the client. Compact advertisements can reduce nested
 schema constraints; REA still validates complete canonical inputs. Full-profile
 `gpt-5.4` metadata is also verified locally. Live model API acceptance and
-Windows remain unverified; see [native client verification](testing.md).
+Windows remain unverified; see [native client verification](../development/testing.md).
 
 ## Claude Desktop
 
@@ -52,16 +52,10 @@ in the file the installed app reads:
   `%APPDATA%` file it still reads; with neither file, setup creates the
   private copy.
 - If `%LOCALAPPDATA%\Packages` holds a `Claude_<publisher ID>` package from
-  another publisher, an `AnthropicPBC.Claude_<publisher ID>` package, or cannot
-  be read, REA cannot establish which file Claude
+  another publisher, or cannot be read, REA cannot establish which file Claude
   Desktop reads. Setup, doctor and uninstall report that instead of falling
   back to `%APPDATA%`. Doctor then reports `claude_desktop` as invalid, and
   uninstall stops before removing anything for any client.
-  The reported `AnthropicPBC.Claude_fnn82j28hfe8t` build can use the `Claude-3p`
-  deployment directory. REA recognizes that package as an unresolved location;
-  it does not assume that it reads the legacy AppData file or automatically
-  register in `Claude-3p`. See [#4432](https://github.com/morluto/rea/issues/4432)
-  for the reported build and manual registration evidence.
 
 Quit Claude Desktop fully before approving setup; closing its window is not
 enough. A running Claude Desktop can rewrite its configuration from memory and
@@ -135,49 +129,13 @@ and Claude Code reports that autocompact is thrashing. To avoid this:
 The sizes above come from REA's own `tools/list`. A live Claude Code session
 against DeepSeek's API is unverified.
 
-For a client whose stdio reader rejects the complete catalog frame, add
-`"REA_MCP_OUTPUT_SCHEMA_PROFILE": "off"` to REA's `env` object and restart the
-client. This omits only advertised output schemas; REA still validates complete
-structured results against its canonical contracts. See [MCP output schema
-profiles](mcp-contracts.md#output-schemas).
-
 ## Kimi Code
 
 Setup registers `rea` in `~/.kimi-code/mcp.json`, or
 `$KIMI_CODE_HOME/mcp.json` when set, while preserving unrelated settings and
 creating a `.rea.backup` before updating an existing file. Kimi Code infers
-stdio from the `command` entry, so setup does not add a `type` field. New
-registrations include `startupTimeoutMs = 30000` and a `toolTimeoutMs` derived
-from REA's known provider allowance plus 120 seconds of operation
-headroom. The default is 450000 ms, covering the default 330-second Ghidra
-startup; an explicit Ghidra startup timeout of 2700000 ms produces a 2820000 ms
-tool timeout. The startup allowance follows an explicitly selected Ghidra or
-Hopper provider, and otherwise uses the larger known Ghidra/Hopper deadline.
-An explicit `REA_JEB_MCP_TIMEOUT_MS` request budget also contributes to that
-maximum. For `ida` or `auto` selection, a valid IDA registration's parsed
-`timeoutMs` also contributes to that maximum; its default is 300000 ms.
-Setup forwards these explicitly selected REA deadlines and the input schema
-profile into the registration; unrelated process values are omitted. An
-explicit `REA_JADX_OPERATION_TIMEOUT_MS` is forwarded with the JADX
-registration but does not contribute to the derived tool timeout; raise
-`toolTimeoutMs` to cover a longer selected JADX deadline.
-This headroom is a practical default, not a guarantee for every analysis
-duration. Setup preserves positive timeout values already in the `rea` entry.
-You can edit `startupTimeoutMs` and `toolTimeoutMs` there; doctor keeps positive
-caller-selected values aligned and reports a non-blocking advisory when a tool
-timeout is shorter than the known provider allowance.
-Setup selects the compact input-schema advertisement for new or refreshed Kimi
-registrations unless their stored configuration or setup environment explicitly
-selects `REA_MCP_INPUT_SCHEMA_PROFILE=full` or `compact`. This keeps REA's
-canonical tool validation unchanged while avoiding a Moonshot Kimi Code 2.2.0
-failure observed with the full catalog: its request was rejected because a
-single tool schema exceeded the provider's size limit. The limit is
-provider-specific and not an MCP protocol limit. `rea doctor --client kimi`
-reports an older registration with no explicit profile as stale. To restore the
-compact profile, run `rea setup --client kimi` or add
-`REA_MCP_INPUT_SCHEMA_PROFILE=compact` to the registration's `env`, then restart
-Kimi Code. An explicit `full` profile remains respected and can still exceed
-Moonshot's limit.
+stdio from the `command` entry, so setup does not add a `type` field. The
+registration includes `startupTimeoutMs = 30000` and `toolTimeoutMs = 120000`.
 Kimi Code also discovers personal skills in `~/.agents/skills` and project-local
 `.agents/skills`, so no separate skill root is required; setup still installs
 and verifies the matching skill files through the normal shared-skill flow.
@@ -243,23 +201,8 @@ standalone CLI check.
 
 ## Codex and Devin
 
-Codex treats an unset or empty `CODEX_HOME` as `~/.codex`. Its MCP server
-registration supports `startup_timeout_sec` for connection initialization and
-`tool_timeout_sec` for each tool call. New REA registrations use a 30-second
-startup timeout and a tool timeout derived from the known provider
-allowance plus 120 seconds of operation headroom. This yields 450 seconds for
-the default Ghidra allowance; an explicit Ghidra startup timeout of 2700
-seconds yields 2820 seconds. Setup preserves positive caller-selected timeout
-values in the REA entry, and doctor reports a non-blocking advisory when a tool
-timeout is shorter than the known provider allowance. An explicitly selected
-JEB request budget also contributes to the allowance. A configured IDA
-registration's parsed `timeoutMs` contributes for `ida` or `auto` selection.
-An explicit `REA_JADX_OPERATION_TIMEOUT_MS` is forwarded with the JADX
-registration but does not contribute; raise `tool_timeout_sec` to cover a
-longer selected JADX deadline.
-These values are client-side deadlines, so increase them in `~/.codex/config.toml` if a
-workload needs more time. Devin honors `XDG_CONFIG_HOME` for its
-`devin/mcp_config.json` on non-Windows systems.
+Codex treats an unset or empty `CODEX_HOME` as `~/.codex`. Devin honors
+`XDG_CONFIG_HOME` for its `devin/mcp_config.json` on non-Windows systems.
 
 ## OMP
 
@@ -322,21 +265,6 @@ The user-level MCP paths follow the editor's VS Code layout. Trae's official
 documentation describes the raw JSON editor without specifying those paths;
 loading this registration in Trae remains unverified.
 
-## WorkBuddy
-
-For [WorkBuddy](https://www.workbuddy.cn/docs/workbuddy/From-Beginner-to-Expert-Guide/Function-Description/MCP-Guide), setup writes `mcpServers.rea` into the
-global `~/.workbuddy/mcp.json` (a standard `mcpServers` JSON file at the user
-home root on every platform). Entries carry `command`, `args`, and `env`;
-stdio is the default transport. WorkBuddy discovers personal skills from
-`~/.workbuddy/skills` (`%userprofile%\.workbuddy\skills` on Windows), so
-setup installs its skill copy there.
-
-The global MCP path is a plain JSON file; setup preserves every other server
-and top-level key when it upserts `rea`. WorkBuddy also reads a project-level
-`<project>/.workbuddy/mcp.json`, which setup does not touch: it registers the
-user-level file only. Loading this registration and real REA tool calls
-through WorkBuddy are verified.
-
 ## ZCode
 
 For [ZCode](https://zcode.z.ai/en/docs/mcp-services), setup registers `rea` in the nested `mcp.servers` table of the
@@ -351,11 +279,7 @@ the first native server into an empty table, it copies the fallback's
 `mcpServers` entries into the native table so they keep loading, and leaves
 the fallback file untouched. Existing REA environment overrides are preserved
 when refreshing its command. A malformed or unreadable fallback file fails setup instead of
-being silently suppressed; repair or remove it and rerun. Uninstall removes an
-REA-owned `rea` entry from both the native table and the fallback, backing up
-each changed file, so an emptied native table cannot load a leftover fallback
-registration; other fallback servers, settings and a foreign `rea` entry are
-kept. ZCode disables a
+being silently suppressed; repair or remove it and rerun. ZCode disables a
 server with `enable: false` on its entry; doctor reports such a registration
 as stale, and rerunning setup removes the flag to repair it. Native configuration
 uses strict JSON; setup refuses comments, trailing commas and a BOM rather than
@@ -404,7 +328,7 @@ in `~/.agents/skills` (`$DSH_AGENTS_HOME/skills` when configured); Harness
 discovers that directory, and its native `skill` tool can load
 `reverse-engineer-anything`.
 
-REA's optional [native client verification](testing.md#end-to-end-integration-and-golden-evidence)
+REA's optional [native client verification](../development/testing.md#end-to-end-integration-and-golden-evidence)
 checks headless chat, skill loading, all tool input schemas and actual analysis
 using the installed Harness and a local model fixture. This establishes the
 Harness integration, with live DeepSeek API compatibility remaining unverified.

docs/getting-started/installation.md

@@ -3,13 +3,13 @@
 Run REA, connect your selected agents, and check the tools needed for your task.
 Setup previews configuration changes and asks for approval before applying them.
 
-| Task                              | Section                                                                                             |
-| --------------------------------- | --------------------------------------------------------------------------------------------------- |
-| Connect an agent                  | [Start setup](#start-setup), then [review changes](#review-setup-changes)                           |
-| Diagnose one task                 | [Scoped readiness checks](#check-readiness-for-your-task)                                           |
-| Configure an analysis engine      | [Hopper](#hopper), [Ghidra](#ghidra), the [IDA guide](ida-provider.md), or [Kuna](kuna-provider.md) |
-| Update or remove REA              | [Maintenance](#diagnose-update-and-remove)                                                          |
-| Resolve a client-specific problem | [Client configuration](client-configuration.md)                                                     |
+| Task                              | Section                                                                                |
+| --------------------------------- | -------------------------------------------------------------------------------------- |
+| Connect an agent                  | [Start setup](#start-setup), then [review changes](#review-setup-changes)              |
+| Diagnose one task                 | [Scoped readiness checks](#check-readiness-for-your-task)                              |
+| Configure an analysis engine      | [Hopper](#hopper), [Ghidra](#ghidra), or the [IDA guide](../providers/ida-provider.md) |
+| Update or remove REA              | [Maintenance](#diagnose-update-and-remove)                                             |
+| Resolve a client-specific problem | [Client configuration](client-configuration.md)                                        |
 
 ## Start setup
 
@@ -57,42 +57,18 @@ Before applying changes, REA checks your current configuration. The plan lists:
 Malformed or unsafe existing configuration blocks the whole transaction before
 Hopper installation or any file write. Declining or pressing Ctrl-C makes no
 changes. Agent configuration writes preserve unrelated entries and comments,
-create backups, stage changes in a private directory, and verify their result.
-Before publication, they refuse detected changes to the selected configuration.
-Replacement uses an explicit destination under the selected canonical parent;
-it does not follow a newly inserted destination symlink. First-run setup uses
-an exclusive hard link and fails without overwriting a newly created destination;
-filesystems without hard-link support cannot publish a first-run configuration.
-Setup and uninstall retain an existing `.rea.backup` rather than replacing the
-first snapshot.
-If that snapshot differs from the current configuration, setup and uninstall
-preserve a verified `.rea.backup.<sha256>.recovery` copy of the current bytes
-before editing; setup also previews it. Both snapshots remain available.
-When an edit made a backup, a failed uninstall update or restore, and a failed
-setup readback or rollback, name the backup path that holds the bytes from just
-before that edit.
-If setup cannot verify a newly created configuration, it retains the file and
-reports manual recovery instead of deleting a pathname that may have changed.
-For an existing configuration, setup and uninstall recovery refuse a detected
-replacement or edit and name the recovery backup. Quit clients before editing their configuration;
-these checks do not lock out another writer modifying the same file in place,
-or exclude pathname changes between the final check and publication.
+create backups, use atomic replacement, and verify their result. Setup and
+uninstall retain an existing `.rea.backup` rather than replacing the first snapshot.
+If that snapshot differs from the current configuration, setup previews and
+preserves a verified `.rea.backup.<sha256>.recovery` copy of the current bytes.
+Both snapshots remain available; a failed rollback reports the current recovery
+copy's path and the restore failure.
 Setup also retains valid environment overrides in REA's existing server entry,
-such as `REA_MCP_INPUT_SCHEMA_PROFILE`, `REA_MCP_OUTPUT_SCHEMA_PROFILE`, and
-`REA_MCP_MAX_RESPONSE_BYTES`.
+such as `REA_MCP_INPUT_SCHEMA_PROFILE` and `REA_MCP_MAX_RESPONSE_BYTES`.
 Detected provider settings replace only matching environment keys.
 Setup and doctor report a malformed REA environment map or invalid runtime
 setting before setup writes files. Repair the named setting in the client
 configuration; setup does not silently discard the rest of the map.
-This includes malformed loader/exclusion JSON arrays and a Ghidra compiler
-specification without its required language identifier. Valid overrides keep
-their original strings, including empty Hopper arguments. DeepSeek Harness
-`!!js` environment expressions remain unevaluated and preserved; registration
-alignment does not verify the runtime values those expressions will produce.
-For layered OpenCode files, each file's values are checked before merging, while
-setting dependencies are checked against the effective merged environment.
-Setup preserves each layer's overrides instead of copying inherited settings
-into the file it updates.
 
 After setup, REA reports which agents, analysis tools, and workflow files passed
 its final checks. Restart any agent named in the completion message, then begin
@@ -136,16 +112,6 @@ See [client configuration](client-configuration.md) for client-specific roots,
 profiles, and environment overrides. A mixed selection plans each distinct
 destination. Selecting the skill without a client uses `~/.agents/skills`.
 Setup leaves existing skill copies in other locations untouched.
-Setup refuses symbolic links at the selected skill directory or its managed
-`references` directory, matching uninstall and update's ownership rules. Use a
-regular skill directory, or select `--skill=false` to configure the client
-registration without installing the bundled skill.
-The final selected directories are checked before approval and again before
-setup changes any client or Hopper installation. Unselected client destinations
-do not block other setup choices. Doctor reports linked or non-directory skill
-paths as `unmanaged`, names the affected paths, and provides those alternatives;
-an unreadable skill identity remains `unknown`. Uninstall retains and reports
-files it cannot safely remove, including their ownership manifest.
 
 `rea setup --skill-client claude_code --yes --json` refreshes and verifies the
 selected skill destination independently of MCP registration selection. The
@@ -161,154 +127,7 @@ identity remains available at `identity.catalog`.
 
 Setup pins package-runner MCP registrations to the exact installed REA version,
 installs the matching skill and on-demand references in the same plan, and adds
-`startup_timeout_sec = 30` for Codex and Grok Build. Codex also receives a
-`tool_timeout_sec` derived from known provider startup plus operation headroom.
-
-## Limit REA to one project or agent profile
-
-Setup registers REA for the whole client. For Claude Code it writes
-`mcpServers.rea` in `~/.claude.json` and installs the bundled skill under
-`~/.claude/skills`, so every project that Claude Code opens can call REA. To
-offer REA's tools only where they're wanted, use one of the routes below.
-
-Both routes control which sessions discover REA's MCP server and skill. They
-leave shell commands, filesystem access and network access available. An agent
-under the same OS account can run `rea` from `PATH` or `npx` and read other
-profiles and REA output. For clean-room separation, use an implementation
-environment with filesystem and network restrictions that prevent reading or
-fetching REA, the target and analysis output, including through shared
-installations and package registries. A separate account or container must
-enforce those restrictions.
-
-For Claude Code, check existing default-profile state before choosing either
-route. Setup is additive: a previous user-level REA registration and personal
-skill remain active in other projects. Back up the default configuration and
-REA skill first, then, with `CLAUDE_CONFIG_DIR` unset, remove the REA user
-registration with `claude mcp remove --scope user rea` and remove the known
-REA-installed `~/.claude/skills/reverse-engineer-anything` directory. Preserve
-unrelated registrations and skills. `rea uninstall` applies to other clients
-as well, so it is broader than this Claude-only migration.
-
-**A separate Claude Code profile.** Claude Code keeps settings, skills and session
-history under `CLAUDE_CONFIG_DIR`. Setup follows the same
-variable: it writes the registration to `$CLAUDE_CONFIG_DIR/.claude.json` and
-the skill to `$CLAUDE_CONFIG_DIR/skills`.
-For REA setup, an empty `CLAUDE_CONFIG_DIR` is treated as unset: registration
-goes to `~/.claude.json` and the skill goes to `~/.claude/skills`.
-
-```bash
-CLAUDE_CONFIG_DIR=~/.claude-rea npx rea-agents setup --client claude_code
-CLAUDE_CONFIG_DIR=~/.claude-rea claude
-```
-
-A new profile may need authentication. Console sign-ins without an API key are
-stored outside `CLAUDE_CONFIG_DIR`; see
-[Claude Code authentication](https://code.claude.com/docs/en/authentication#log-in-with-multiple-accounts).
-Sessions started without the variable use the default profile's registration,
-skill and history.
-
-Inline assignments apply only to that command. Keep the same prefix for every
-profile check, setup rerun, update, or removal; bare commands use the current
-environment and can otherwise inspect or recreate default-profile state:
-
-```bash
-CLAUDE_CONFIG_DIR=~/.claude-rea claude mcp list
-CLAUDE_CONFIG_DIR=~/.claude-rea npx rea-agents doctor --client claude_code --skill --json
-CLAUDE_CONFIG_DIR=~/.claude-rea npx -y rea-agents@latest setup --client claude_code --dry-run
-```
-
-After reviewing an update plan, rerun that same prefixed setup command without
-`--dry-run` and approve its exact changes. Profile removal likewise needs the
-prefix on `claude mcp remove --scope user rea` and any `rea uninstall` command;
-keep the broader client scope of uninstall in mind. Restart the selected
-profile after changing its pinned registration.
-
-`claude mcp remove` removes only the registration. To remove REA from this
-profile without running the broader uninstall flow, first back up the profile's
-REA-managed skill directory, then remove
-`$CLAUDE_CONFIG_DIR/skills/reverse-engineer-anything` as well. Keep other skills
-in the profile intact.
-
-The commands above use POSIX shell assignment syntax. In native Windows
-PowerShell, select the profile for the whole setup/launch/check session and
-restore the previous selection afterward:
-
-```powershell
-$previousClaudeConfigDir = $env:CLAUDE_CONFIG_DIR
-try {
-  $env:CLAUDE_CONFIG_DIR = Join-Path $HOME ".claude-rea"
-  npx rea-agents setup --client claude_code
-  claude mcp list
-  npx rea-agents doctor --client claude_code --skill --json
-  npx -y rea-agents@latest setup --client claude_code --dry-run
-  # After reviewing the plan, repeat setup without --dry-run and approve it.
-  claude
-  # Profile removal, when intended, also belongs inside this selected scope:
-  # claude mcp remove --scope user rea
-} finally {
-  if ($null -eq $previousClaudeConfigDir) {
-    Remove-Item Env:CLAUDE_CONFIG_DIR -ErrorAction SilentlyContinue
-  } else {
-    $env:CLAUDE_CONFIG_DIR = $previousClaudeConfigDir
-  }
-}
-```
-
-Use PowerShell for these Windows examples rather than pasting POSIX assignments
-into cmd.exe. Keep profile updates, readiness checks and removal inside the
-same selected environment; the `finally` block restores the previous profile
-or unsets the variable when it was absent.
-
-**One project.** Install without configuring Claude Code: use the curl
-installer's `--no-setup`, or run setup only for other clients. Then register
-REA from the project directory at Claude Code's local scope.
-
-This route uses the default Claude profile. Keep `CLAUDE_CONFIG_DIR` unset for
-the entire local lifecycle: registration, backup, listing, version replacement
-and removal. In POSIX shells run `unset CLAUDE_CONFIG_DIR`; in PowerShell run
-`Remove-Item Env:CLAUDE_CONFIG_DIR -ErrorAction SilentlyContinue` before these
-commands. Record an existing selection first if you intend to restore it after
-finishing. The configuration path below is the default profile's
-`~/.claude.json`; a different active profile uses its own config root instead.
-
-Register with the variable unset:
-
-<!-- x-release-please-start-version -->
-
-```bash
-claude mcp add --scope local rea -- npx -y rea-agents@6.7.0 mcp
-```
-
-On native Windows, use the same project directory and wrap the package-runner
-shim so the stdio client can launch it:
-
-```powershell
-claude mcp add --scope local rea -- cmd.exe /d /c npx -y rea-agents@6.7.0 mcp
-```
-
-<!-- x-release-please-end -->
-
-Local scope stores the entry under that directory's path in `~/.claude.json`,
-so other projects don't load it. This route doesn't install the bundled skill.
-Avoid `--scope project`, which writes `.mcp.json` into the repository where it
-can be committed or copied. `rea doctor` and `rea uninstall` read only the
-user-level entry, so they don't report or remove a local-scope registration;
-remove it with `claude mcp remove --scope local rea` from the same directory.
-`rea update` doesn't refresh it either, so it stays on the version it names.
-To move it to a newer release, first back up the project entry in
-`~/.claude.json` and record its environment and other metadata. In particular,
-preserve caller-selected overrides such as `REA_MCP_INPUT_SCHEMA_PROFILE` and
-`REA_MCP_MAX_RESPONSE_BYTES`. Run `claude mcp remove --scope local rea` from the
-same directory, then recreate it with the platform-appropriate command above
-and the new version. Reapply every recorded environment value with Claude
-Code's `mcp add --env NAME=value` options and restore any other retained entry
-metadata before restarting the project session. Removal and re-addition do not
-preserve these values automatically. Running setup for Claude Code instead
-would add a user-level entry for every project.
-
-Check the separate profile with the prefixed `claude mcp list` above and compare
-with the default profile with `CLAUDE_CONFIG_DIR` unset. For local scope, run
-`claude mcp list` from the selected project and again from another project.
+`startup_timeout_sec = 30` for Codex and Grok Build.
 
 ## Check readiness for your task
 
@@ -317,15 +136,6 @@ configuration without changing them. Without options, it audits every detected
 registration, the installed skill and optional analysis engines; its overall
 `healthy` value can be false while your chosen workflow works.
 
-Doctor's `providerInspections` are host-level engine and registration checks,
-not a readiness row for every advertised MCP adapter surface. `tools/list`
-remains the complete stable catalog. Call `binary_session` with `{}` before
-choosing an operation; it works before a target is opened, and
-`result.tool_availability` reports per-operation availability, reasons and
-client requirements for the current session state. It does not guarantee that
-a particular caller-supplied input will be valid. See
-[MCP discovery](mcp-contracts.md#identity-and-discovery).
-
 Select the part you want to check:
 
 | Task                                | Readiness check                                                          |
@@ -347,21 +157,6 @@ on `open_binary`. A `capability_unavailable` failure carries
 `details.candidate_ids`, while `provider_unavailable` asks you to repair the
 selected engine. See [provider selection](cli.md#choose-a-provider).
 
-### Linux owned-process prerequisite
-
-On Linux, REA's shared process supervisor requires a procps-compatible `ps`
-on REA's `PATH` for ownership checks before launching a child. Ghidra, JADX,
-firmware tools and static JavaScript/Electron analysis use these checks.
-Install your distribution's `procps` or `procps-ng` package, or put another
-procps-compatible `ps` on `PATH` before
-running those workflows. A missing or incompatible command causes a refusal
-before the supervised child starts.
-
-The public error code varies by caller: `capability_unavailable`,
-`provider_unavailable` or `execution_failure`. Some provider adapters report
-only a generic startup error. Check this prerequisite before following
-provider-specific recovery advice.
-
 ## Diagnose, update, and remove
 
 `rea doctor --json` is strictly read-only. `rea update` updates only the npm or Bun global installation that owns the running CLI. Source checkouts and package-runner copies must be updated through the mechanism that owns them; a fresh package-runner invocation can use `npx rea-agents@latest` or `bunx rea-agents@latest`. `rea uninstall` removes only REA-owned agent registrations and skill files; `--purge-data` additionally removes REA cache and state paths.
@@ -376,17 +171,7 @@ Uninstall preserves Hopper, Node.js, Evidence files, captures, unrelated skills
 and other MCP servers. Purging removes only REA's cache and state under
 `~/.rea`. A client configuration that is malformed, unreadable, or at an unsafe
 path stops the operation before anything is removed, and a client that fails
-while being updated stops the remaining removals. Uninstall reports each
-candidate `configuration_path` with its outcome. A client with multiple files
-keeps their individual `actions` alongside its aggregate status and detail,
-including earlier removals when a later file fails. The paths name
-the discovered configuration candidates, not resolved physical file identities.
-For JSON clients, uninstall removes every repeated `rea` member in the effective
-server table only when each registration is REA-owned. An unowned earlier
-member, or an unowned OpenCode V1 entry that removing V2 would expose, stops
-preflight before any
-removal. Repeats inside an inactive earlier copy of the server table stay
-unchanged. A purge path that is a
+while being updated stops the remaining removals. A purge path that is a
 symbolic link is retained and reported rather than followed. Uninstall checks
 REA's managed shared and Claude Code personal skill locations. See the
 [CLI guide](cli.md#output-and-exit-status) for exit statuses.
@@ -424,11 +209,9 @@ running server or its registration.
 The npm release checked on **2026-10-11** was **6.4.0**, published from
 [`a56f7bb6`](https://github.com/morluto/rea/commit/a56f7bb668ab23fec8d33f7af353ac7ed2fe1895).
 The actual registry package accepted dry-run setup plans for the 17 client IDs
-in that release, including Qwen Code, Pi and Hermes. Seven client IDs are
-included from 6.5.0 and were absent from the checked npm 6.4.0 package: `droid`,
-`dsh`, `kimi`, `qoder`, `trae`, `workbuddy` and `zcode`.
-The 6.4.0 registry check does not establish 6.5.0 publication or live DeepSeek
-API integration.
+in that release, including Qwen Code, Pi and Hermes. DeepSeek Harness (`dsh`)
+is on main and is not in npm 6.4.0; `rea setup --client dsh` against `@latest`
+reports an unsupported client until a release containing it is published.
 OpenCode's plan selected
 `OPENCODE_CONFIG_DIR` even when that directory did not yet exist. These checks
 used an isolated home on macOS with Node 24; they verify planning and argument
@@ -505,12 +288,11 @@ hosted connector; see [its configuration](client-configuration.md#other-client-s
 | Qoder              | `qoder`          |
 | Factory Droid      | `droid`          |
 | Trae               | `trae`           |
-| WorkBuddy          | `workbuddy`      |
 | ZCode              | `zcode`          |
 | DeepSeek Harness   | `dsh`            |
 
-`droid`, `dsh`, `kimi`, `qoder`, `trae`, `workbuddy`, and `zcode` require
-`rea-agents@6.5.0` or later. The 6.4.0 registry check above does not cover them.
+`dsh` and `kimi` require a release containing them. The registry check above does
+not cover them.
 
 See [client configuration and troubleshooting](client-configuration.md) for
 configuration paths, profiles, trust policies, and schema-limit workarounds.
@@ -534,7 +316,7 @@ Nobara 44+, 64-bit Arch Linux, CachyOS, or Omarchy. REA itself runs on any
 Linux distribution with a recognized apt, dnf, or pacman package family, where
 an existing Hopper launcher is selected through `HOPPER_LAUNCHER_PATH`. Ghidra
 and IDA have their own provider-specific host requirements; Windows Ghidra uses
-the [experimental P0 boundary](windows-ghidra-p0.md).
+the [experimental P0 boundary](../providers/windows-ghidra-p0.md).
 
 On macOS, approved setup downloads the official DMG, checks its published size
 and digest, validates the application bundle, and atomically installs it to
@@ -552,53 +334,8 @@ document for the same target. REA does not currently identify, focus, or reuse
 that existing GUI document, and the supported launcher exposes no attach or
 reuse action for it.
 
-REA currently declines saved Hopper database (`.hop`) targets on macOS because
-the native `open database` launch route does not run REA's bridge script. To
-analyze that program with REA, select its original executable as the target and
-open it through Hopper; this starts the supported bridge route. This does not
-recover database-only annotations or analysis changes. Saved-database analysis
-on Linux continues to use its supported demo-launch route.
-
-Hopper lease directories must be readable and owned by the current user.
-REA validates and secures an opened directory before reserving a lease. If
-opening that directory fails with a permission error, the diagnostic identifies
-the path and recovery steps while leaving its permissions unchanged. Check
-ownership and parent-directory access, then restore owner-only read, write, and
-search permissions (`0700`) on a directory you own before retrying.
-
 On supported Linux distributions, approved setup verifies Hopper's official
 `.deb`, `.rpm`, or Arch package before invoking the native package manager.
-The official release feed selects the current public demo without a version
-pin. REA verifies the package's detached PGP signature against Hopper's stable
-primary fingerprint `7C2D73BAFAF5B9A710A69DA1A26DF815099B1BCD`, then checks
-that the signed package and installed launcher agree with `main_exe_hash`.
-Rotating signing subkeys remain bound to that primary identity.
-The feed row itself is not PGP-signed; doctor labels its display version as
-`reported_release_version`, separately from the authenticated launcher identity.
-
-The approval plan includes the caller-selected cache location. Approved setup
-retains the signed archive, public key and release metadata under
-`${XDG_CACHE_HOME:-$HOME/.cache}/rea/hopper-releases/<launcher-sha256>`.
-An empty `XDG_CACHE_HOME` uses `$HOME/.cache`. Approved setup can repair a
-damaged caller-owned entry after authenticating a fresh package; the previous
-entry is preserved beside it as `<launcher-sha256>.backup-<id>`. Ordinary doctor
-and launches reject damaged evidence and never repair it implicitly.
-Approved publications of the same canonical cache entry share a process-backed
-lease. Concurrent setup waits without moving another writer's evidence; a
-failed replacement restores the previous directory when possible and reports
-any retained backup path. Unavailable reads or native inspection tools do not
-authorize replacing existing evidence.
-Doctor and launches authenticate this evidence for offline use; an editable
-digest receipt alone cannot authorize a launcher. Verification reuses at most
-eight immutable package proofs per process, keyed by the complete package,
-key, signature, package format and expected launcher digest. Cached file reads
-still check identity and content. Without retained evidence, inspecting an
-existing install requires the matching current official package and network
-access. Successful live inspection can be reused within that process after
-rehashing the launcher; it does not write a persistent cache or claim that a
-previously observed release is still the latest. Older uncached builds require
-an approved update while the feed exposes only its current release.
-
 REA runs the supported demo build on a private Xvfb display and selects Hopper's
 offered demo mode for each analysis session; it does not require the user's
 desktop display. Unattended package-manager access requires
@@ -609,27 +346,6 @@ host mount and the rest of `/tmp` remain unchanged; this fallback never invokes
 `sudo`. `rea doctor --provider hopper --json` reports the selected
 strategy and both host and effective mount facts.
 
-Hopper also embeds Python; the Python executable and standard library alone
-are insufficient on Ubuntu. Approved setup checks the system interpreter
-at `/usr/bin/python3` and, when necessary, installs its matching
-`libpython3.X` package, then verifies that its shared library can load.
-APT resolves the concrete package (for example, `libpython3.12t64` on Ubuntu
-24.04). Doctor includes these fresh observations in the `embedded_python`
-details of its `hopper-demo-runtime` check, alongside the private-display
-diagnostic. Failed inspections remain unknown rather than proving a library
-absent. Run `rea setup --yes --install-hopper` to repair a supported install.
-This prerequisite check does not launch the bridge or validate a custom Python
-interpreter configured inside Hopper; that interpreter needs its own matching
-shared runtime. Custom installation prefixes or shared-library ABIs require
-manual dependency repair.
-
-When the package-manager step fails, setup reports the failing command and its
-captured output, so a package conflict is distinguishable from an authorization
-failure. On CachyOS, an unversioned compatibility package such as
-`zlib-ng-compat` may conflict with Hopper's versioned `zlib` dependency. Resolve
-the package conflict yourself or install Hopper's official package manually,
-then rerun `rea setup`.
-
 The supported Linux demo forwards additional launches into its existing
 application, even across private displays. REA therefore reserves one Linux
 Hopper application per user across cooperating REA processes. A competing
@@ -651,19 +367,11 @@ sessions before removing that recovery directory and retrying.
 
 ### Launcher paths and troubleshooting
 
-On macOS, REA checks executable Hopper launchers in this order: the canonical
-system application, the canonical application installed by `rea setup` under
-`~/Applications`, then other `Hopper*.app` bundles in `/Applications` and
-`~/Applications`. The Homebrew cask location is an optional `rea doctor`
-diagnostic; to use a Homebrew-installed launcher for CLI/MCP startup, set
-`HOPPER_LAUNCHER_PATH` to the path reported by doctor. REA does not run Homebrew
-while loading runtime configuration.
-Automatic discovery accepts executable regular files, including file symlinks,
-and skips directories.
+On macOS, REA uses
+`/Applications/Hopper Disassembler.app/Contents/MacOS/hopper` by default.
 On Linux, it prefers executable `/opt/hopper/bin/Hopper`, then executable
-`~/.local/share/rea/hopper/bin/Hopper`, followed by `/opt/hopper-v4/bin/hopper`
-and `/usr/bin/hopper`; if none exists, the former remains the diagnostic
-fallback. `HOPPER_LAUNCHER_PATH` overrides those choices:
+`~/.local/share/rea/hopper/bin/Hopper`; if neither exists, the former remains
+the diagnostic fallback. `HOPPER_LAUNCHER_PATH` overrides those choices:
 
 ```bash
 export HOPPER_LAUNCHER_PATH=/absolute/path/to/Hopper
@@ -675,11 +383,6 @@ bridge readiness. For large targets, set `REA_HOPPER_STARTUP_TIMEOUT_MS` to a
 decimal integer from 1 to 2,147,483,647 milliseconds in the environment that
 starts REA. CLI and MCP use the same setting; invalid values fail configuration
 validation. An MCP client's own request timeout must also allow enough time.
-`open_binary` validates and selects a target without waiting for native provider
-readiness. During Hopper startup, `binary_session.provider_operation_health`
-reports `busy` at stage `launch`; `analysis_activity` describes bridge requests
-and can remain idle until the socket is ready. Cleanup work reports `busy` at
-stage `connection`.
 
 If macOS denies Apple Events, allow the application that starts REA under
 **System Settings → Privacy & Security → Automation**, then retry. REA releases
@@ -689,12 +392,9 @@ Arguments containing quotes, backslashes, or line breaks remain unchanged but
 cannot establish that a failed handoff opened no document. Other failed handoffs
 retain ownership until document closure is confirmed. If a timed-out bridge
 becomes ready later, `close_binary` connects to that run, authenticates its
-identity, and requests document shutdown. Once its listener is ready, the bridge
-allows 30 seconds for the first connection and capability validation. After a
-connection drops, it allows the same grace period for an authenticated cleanup
-reconnect, then releases Hopper's Python execution thread. Initial analysis is
-outside this listener grace period, and authenticated native work is not bounded
-by it. Expiry does not establish document closure, so REA
+identity, and requests document shutdown. After a connection drops, the bridge
+allows 30 seconds for an authenticated cleanup reconnect, then releases Hopper's
+Python execution thread. Expiry does not establish document closure, so REA
 retains unconfirmed ownership. Retry close while the bridge remains available.
 
 If a Linux launcher exists but cannot start, inspect its shared libraries:
@@ -715,20 +415,6 @@ If startup reports `Cannot launch Hopper! Connection is invalid.` or waits for
 bridge readiness, check Hopper for a pending demo, license, or loader dialog.
 Complete the dialog and retry. If REA reports `cleanup_incomplete`, follow the
 retained-resource guidance below before reopening the target.
-
-On macOS, Hopper can show an `Executing Python Script...` overlay while the REA
-bridge serves an active MCP connection. Long-lived MCP clients can keep that
-connection open across agent turns, so the overlay may remain visible after the
-analysis calls finish; by itself, it does not establish a stalled startup. REA
-does not automatically idle-close a still-connected target. When the
-investigation is finished, export an Evidence bundle first if you need to keep
-the session ledger, then call `close_binary`; set `snapshot_path` to save a
-provider-neutral analysis snapshot as part of closing. A successful close
-shuts down the REA bridge and clears its overlay; REA does not control the
-macOS Hopper application lifetime.
-The Hopper GUI Cancel button's behavior for this bridge has not been verified;
-`close_binary` is the supported cleanup path.
-
 Hopper serializes analysis requests. Cancelling a wait can leave provider work
 running, which the session reports. Successful decompilation is cached until
 a relevant rename or comment changes it.
@@ -742,18 +428,12 @@ memory has no original file offset. For FAT Mach-O, offsets refer to the origina
 container file. Results retain Hopper's image-relative offset, the observed slice
 base, and the source executable path.
 Loader selection reads the Mach-O container header, including FAT files with a
-single architecture. For FAT32 and FAT64 containers, REA validates the
-architecture table and selected Mach-O header, prepares a private thin image,
-and loads it with Hopper's native Mach-O loader instead of Hopper's implicit
-FAT slice choice. For arm64 targets, REA ranks subtype bases 0 (plain arm64) and
-2 (arm64e), ignoring capability bits for ranking while retaining the raw subtype
-for slice identity. These slices' function-entry encodings decode under
-`--aarch64`, ahead of Apple's arm64e.x1 variant (base subtype 12), which is
-selected only when it is the arm64 family's only candidate. REA checks the
-entire source's SHA-256 while copying the slice; source identity and reported
-offsets still refer to the original container. Any other ambiguous architecture
-subtype requires an explicitly extracted thin image; REA does not guess.
-Configured loader arguments remain explicit overrides.
+single architecture. For FAT64, REA validates the architecture table and selected
+Mach-O header, prepares a private thin image, and loads it with Hopper's native
+Mach-O loader. It checks the entire source's SHA-256 while copying the slice;
+source identity and reported offsets still refer to the original container.
+An ambiguous architecture subtype requires an explicitly extracted thin image;
+REA does not guess. Configured loader arguments remain explicit overrides.
 FAT64 is distinct from the CPU architecture: FAT32 containers can contain 64-bit
 executable images. This preparation avoids the Raw Binary loader dialog observed
 with native FAT64 loading on Hopper 6.1.0-demo.
@@ -769,7 +449,7 @@ output-stream closure; `output_closed: false` keeps that uncertainty explicit.
 Later requests retain the known exit instead of reducing it to socket loss.
 An external GUI's helper exit does not establish that the GUI itself exited.
 For cursor navigation, string decoding, symbol-name limits, and regex matching,
-see [Hopper analysis behavior](native-investigation.md#hopper-analysis-behavior).
+see [Hopper analysis behavior](../guides/native/native-investigation.md#hopper-analysis-behavior).
 
 Closing or switching a target closes its bound Hopper document, shuts down REA's
 bridge and removes its temporary socket directory. The macOS Hopper application
@@ -784,17 +464,9 @@ Once document and process closure are confirmed, the lease can be released even
 if temporary-file cleanup fails. Another client can then launch, but the owning
 client must finish its retained cleanup before starting again.
 An unconfirmed external document can be retried while its authenticated bridge
-remains available. The same authentication and process-identity capture apply
-when the first successful handshake occurs during cleanup after a startup
-timeout. REA can confirm closure if that exact authenticated process exits,
-including while a shutdown request is in flight. A helper exit alone is
-insufficient, and an application that never authenticated has no verified
-process identity. If no matching bridge becomes available, inspect and close
-the reported document in Hopper before ending the owning REA connection.
-Export the Evidence bundle before `close_binary` clears session records.
-`binary_session.cleanup_pending` remains true while provider cleanup is retained,
-and provider health remains visible even with `open: false`; that flag alone
-does not establish successful cleanup.
+remains connected. If that bridge has disconnected, another close cannot confirm
+the document: inspect and close the reported document in Hopper before ending
+the owning REA connection.
 
 ### Hopper in CI
 
@@ -821,13 +493,7 @@ copying license secrets into logs, or killing unrelated Hopper processes.
 REA connects to an existing Ghidra installation on Linux x64/arm64, macOS x64/arm64,
 or experimental Windows x64 P0.
 It accepts Ghidra 12.1.x and the 64-bit full JDK declared by that installation's
-`application.java.min` and `application.java.max`. The JDK's reported platform must also
-map to the same native decompiler directory as the host: a JDK running under
-emulation (for example x86_64 under Rosetta on Apple silicon) or reporting a
-non-host `os.name` fails the doctor
-even when it is an otherwise accepted 64-bit full JDK. Select a matching JDK
-through `JAVA_HOME`; adding another decompiler in the JVM-selected directory
-does not satisfy this host-validated admission rule. Current 12.1 releases require
+`application.java.min` and `application.java.max`. Current 12.1 releases require
 JDK 21 or newer and set no maximum. The bridge is verified with Ghidra 12.1.4
 and JDK 21. Each installation must include the native decompiler for the host
 architecture in `Ghidra/Features/Decompiler/os/<platform>/` or the corresponding
@@ -839,7 +505,7 @@ reported as incompatible instead of being admitted from its directory name, and
 a header that cannot be read or recognized is reported as unknown. REA does not
 build or install native tools, or change Gatekeeper quarantine settings.
 
-The adapter exposes 26 read-only operations: fourteen inventory/name/search
+The adapter exposes 25 read-only operations: thirteen inventory/name/search
 operations and twelve function-analysis operations. These cover metadata,
 decompilation, assembly, resolved calls, typed references, xrefs, function
 dossiers, instructions, recovered data types, measured load mappings, loaded
@@ -853,13 +519,13 @@ and `set_addresses_names` name a function entry or any other mapped address
 session metadata edits leave executable bytes unchanged and are discarded on close. GUI controls
 require Hopper; Windows P0 remains read-only.
 
-Windows P0 admits native x86, x86-64, ARMNT (Thumb-2) and ARM64 PE applications and DLLs, plus explicitly
-selected [raw NMOS 6502 images](raw-binary.md#nmos-6502) with a caller-supplied
+Windows P0 admits native x86 and x86-64 PE applications and DLLs, plus explicitly
+selected [raw NMOS 6502 images](../providers/raw-binary.md#nmos-6502) with a caller-supplied
 entry at file offset 0, on fixed local NTFS volumes. Other raw CPU families remain
 unsupported on Windows.
 The npm package bundles native Job Object ownership, protected private runtime
 DACLs, and handle-based path admission; no separate addon installation is needed.
-See the [Windows Ghidra P0 guide](windows-ghidra-p0.md) for verified scope and
+See the [Windows Ghidra P0 guide](../providers/windows-ghidra-p0.md) for verified scope and
 limitations.
 
 Extract Ghidra and install the JDK outside REA, then export absolute paths:
@@ -871,16 +537,6 @@ rea doctor --json
 rea setup
 ```
 
-On macOS, [Homebrew OpenJDK is keg-only](https://formulae.brew.sh/formula/openjdk)
-and may be unavailable to the system `java` wrapper. Set `JAVA_HOME` to the
-selected formula's `libexec/openjdk.jdk/Contents/Home`, for example
-`/opt/homebrew/opt/openjdk/libexec/openjdk.jdk/Contents/Home` or
-`/usr/local/opt/openjdk/libexec/openjdk.jdk/Contents/Home`. Use a JDK inside the
-Java version bounds declared by your Ghidra installation; REA does not select
-another installed JDK automatically. Doctor distinguishes an absent Java
-command from a command that runs and fails, and retains bounded probe output
-and any parsed properties when the selected runtime cannot be admitted.
-
 On Windows, configure the existing installation in PowerShell:
 
 ```powershell
@@ -895,57 +551,16 @@ REA skill after approval. Direct registrations use Node to launch REA's entry
 script; package-runner registrations use the pinned `npx` or `bunx` command. Hopper
 installation remains unavailable on Windows. Setup never installs Ghidra,
 Java, or Python. It preserves valid detected Ghidra/JDK settings in agent
-registrations. See [Windows Ghidra P0](windows-ghidra-p0.md) for provider diagnostics.
-
-When `GHIDRA_INSTALL_DIR` is unset, doctor and the Ghidra provider also search
-`PATH` for `ghidra` or `ghidraRun`, resolve the selected launcher through its
-real path, and accept it only when that location belongs to a Ghidra tree with
-the application metadata and headless launcher. An explicitly supplied
-`GHIDRA_INSTALL_DIR` always takes precedence, including when it is invalid;
-REA reports that error instead of silently selecting another installation.
-This discovery is read-only and does not execute the Ghidra launcher.
+registrations. See [Windows Ghidra P0](../providers/windows-ghidra-p0.md) for provider diagnostics.
 
 Doctor validates the platform, architecture, Ghidra 12.1.x application version,
 `support/analyzeHeadless` or `support/analyzeHeadless.bat`, the installation's
 Java major range, 64-bit JDK bitness, and the presence of `javac`/`javac.exe`.
-It also checks that the reported JVM `os.arch` and `os.name` map to the same native decompiler
-directory validated for the host; unrecognized reported architectures or a
-non-host operating system are refused. LaunchSupport overrides of either
-property, including through helper-environment JVM option variables, are
-rejected at launch.
 When Java is found through `PATH`, setup records its observed JDK home so GUI
 MCP clients do not depend on an incidental shell path. Setup shows every exact
 environment entry in its plan, writes only after approval, and never downloads,
 installs, upgrades, or modifies Ghidra or Java.
 
-Installation inspection derives the private configuration directory identity from
-`application.version` and `application.release.name` in
-`Ghidra/application.properties`. The directory's version spelling follows Ghidra
-(for example, `12.1.0` becomes
-`12.1`), while the reported provider version preserves the original value.
-The launcher uses that inspected coordinate; it does not reread the properties
-or guess from the extracted folder's name.
-If the identity is missing, malformed, or unsafe as a single path component,
-the launcher fails before preparing its home/cache/config/temp directories or
-starting Java. The client may already have allocated private runtime/endpoint
-resources and a target snapshot; existing startup-failure cleanup still applies.
-Restore the selected release's properties instead of renaming its installation folder.
-Inspection follows selected properties symlinks, admits only a regular file,
-and caps the metadata payload at 1 MiB under REA's resource budget. A final
-one-byte probe checks for growth. This is not a Java
-Properties format limit. Reads preserve Ghidra's Latin-1 byte mapping and check
-the descriptor and selected name for changes. Permission failures and resource
-refusals remain explicit; failed descriptor cleanup must succeed before that
-owner admits another inspection.
-Native decompiler compatibility inspection follows the selected executable symlink
-and reads at most the first 4096 bytes through the same descriptor owner. It
-checks the full extent and selected name for changes without reading the remainder.
-An unreadable or unrecognized header leaves compatibility unknown; diagnostics
-retain read failures. Cancellation and incomplete cleanup propagate as failures,
-and failed cleanup retains the exact descriptor for retry.
-This coordinate selects only REA's session-private configuration directory, not
-the installation or an existing user configuration directory.
-
 Each verified session uses an ephemeral temporary project and isolated
 home/cache/config/temp paths. REA passes `-readOnly`, `-deleteProject`, uses
 Ghidra's default analysis settings, and loads its packaged Java
@@ -961,10 +576,6 @@ ownership inspection, so retaining those wrappers would prevent verified
 process-group cancellation during startup.
 If ownership remains unverifiable, it reports the reason and retains the process
 supervisor and private runtime instead of removing files beneath a live provider.
-Startup preserves an observed launch failure when cancellation arrives during
-rollback. Producer cancellation retains the caller's exact reason separately
-from LaunchSupport warnings and cleanup failures. Failed rollback keeps the
-original process owner for a later cleanup retry.
 The experimental Windows transport uses authenticated IPv4 loopback with a
 private native-owned bearer descriptor and Job Object process ownership.
 
@@ -976,35 +587,14 @@ bridge, and health readiness. Large binaries can need more: set
 `REA_GHIDRA_STARTUP_TIMEOUT_MS` to an integer between 1 and 2,147,483,647
 milliseconds in the server environment. An absent setting uses the default;
 empty, invalid or out-of-range supplied values fail configuration validation.
-When the deadline elapses, the `provider_timeout` error names
-`REA_GHIDRA_STARTUP_TIMEOUT_MS` with the deadline that was applied and suggests
-`REA_GHIDRA_DISABLED_ANALYZERS` for analyzers that dominate the time.
 REA parses the supplied configuration environment and
 passes the deadline to each provider client; a startup failure is returned by the query that triggered it,
 without exposing partial analysis. This deadline is separate from MCP transport
 initialization and the client's deadline for that individual tool call. A client
 can time out earlier even when Ghidra would complete within its startup deadline.
-See [Ghidra first-query deadlines and recovery](mcp-contracts.md#ghidra-first-query-deadlines-and-recovery)
+See [Ghidra first-query deadlines and recovery](../reference/mcp-contracts.md#ghidra-first-query-deadlines-and-recovery)
 for client options and the close/reopen recovery flow.
 
-The 330-second default is configurable. Configuration is read when REA starts:
-changing an environment variable in another shell, or closing and reopening a
-binary in the same MCP server, does not change that server's startup allowance.
-For a CLI retry with an example 30-minute allowance:
-
-```sh
-REA_GHIDRA_STARTUP_TIMEOUT_MS=1800000 rea analyze /absolute/path/to/app.exe --provider ghidra --json
-```
-
-For MCP, export useful Evidence before restarting, close the binary and resolve
-any cleanup failure, update the environment in the client's REA server launch
-configuration, then restart REA and reconnect before reopening the target. Allow
-startup plus the query in the client's own tool-call deadline. Every retry uses
-a fresh ephemeral import; smaller result requests do not reduce the prerequisite
-auto-analysis. A larger time allowance does not raise the JVM heap limit or
-guarantee completion. Keep [heap and host CPU controls](#ghidra-heap-and-cpu-controls)
-appropriate for the machine.
-
 One session contains exactly one imported Program; use `provider_id: "ghidra"`, `--provider ghidra`, or
 `REA_ANALYSIS_PROVIDER=ghidra` when both Hopper and Ghidra support the target.
 One persistent decompiler is owned by the Program, and a serial queue keeps
@@ -1078,8 +668,6 @@ export REA_GHIDRA_COMPILER_SPEC_ID="borlandcpp"   # optional; requires a languag
 
 REA passes `-processor`/`-cspec`, checks both against the installation's `.ldefs`, and records them in the analysis profile. DOS imports reject an override.
 
-Language definitions must be well-formed XML encoded as UTF-8 or BOM-marked UTF-16, with any encoding declaration matching the bytes. Literal Unicode replacement characters (U+FFFD) are accepted; malformed source bytes are rejected.
-
 To seed code that auto-analysis cannot reach (computed jumps, pointers in data):
 
 ```bash
@@ -1107,14 +695,9 @@ and hyphens; at most 32 names are admitted, each at most 120 characters.
 Names must identify analyzers registered for the selected program. Unknown names
 or options that remain enabled abort the headless import before auto-analysis
 and the bridge, so an unsuccessful override cannot produce a session claiming
-that the analyzer was disabled. The setting applies to every import in the REA
-server. A format-specific analyzer may not be registered for another target, so
-the same override can prevent that target from opening. For mixed-target work,
-omit the override or use a separate REA server configured for the affected
-format. Changing the environment requires restarting the server; reopening a
-target alone keeps the current setting. For Windows PE resource analysis, the
-exact name is `WindowsResourceReference`. Disabling an analyzer skips the facts
-it would have produced.
+that the analyzer was disabled. For Windows PE resource analysis, the exact name
+is `WindowsResourceReference`. Disabling an analyzer skips the facts it would
+have produced.
 
 ### Ghidra heap and CPU controls
 
@@ -1170,7 +753,7 @@ contains the launch arguments and `/proc/<jvm-pid>/status` reports
 session and retain the resource flags needed for the measurement rather than
 copying full command lines or environments into reports. Heap and affinity
 settings affect cost and latency; they are not part of REA's semantic analysis
-profile identity. See [real-provider testing](testing.md) for bounded
+profile identity. See [real-provider testing](../development/testing.md) for bounded
 verification workflows.
 
 ### Ghidra diagnostics and verification
@@ -1181,13 +764,6 @@ errors expose Error names, messages, and available codes under
 truncation markers. Darwin ownership-helper compilation failures also retain
 the compiler outcome, exit code or signal, and bounded stderr; a timed-out
 compiler remains distinguishable from a compiler that exited with an error.
-The helper compile deadline defaults to 120,000 ms; set
-`REA_SWIFTC_COMPILE_TIMEOUT_MS` to an integer between 1 and 2,147,483,647 when
-a busy host needs longer.
-On macOS, the Java prerequisite probe waits for this independently bounded
-preparation before starting its five-second command deadline. Caller cancellation
-still interrupts preparation, and failed helper cleanup remains owned for retry.
-Linux process-table preparation remains inside the command deadline.
 Other rejection values retain their primitive value or an explicit type.
 Shutdown warnings include the failure
 kind, message, and diagnostics, while process and temporary-project cleanup
@@ -1209,7 +785,7 @@ On a controlled Windows x64 runner, use
 `npm run verify:ghidra:windows`. The verifier generates a deterministic native
 PE fixture from source bytes and requires the Windows native authority before
 opening the provider. The controls are implemented on main; see the
-[release boundary](#released-package-and-main). The lane verifies all 26 admitted
+[release boundary](#released-package-and-main). The lane verifies all 25 admitted
 read-only operations, digest identity, and runtime cleanup. The separate
 `verify:ghidra:windows:package` lane checks the packed CLI/MCP boundary with an
 ordinary user. It requires the built Windows native bundle and an existing
@@ -1234,7 +810,7 @@ For a client that requires manual configuration, use:
   "mcpServers": {
     "rea": {
       "command": "npx",
-      "args": ["-y", "rea-agents@6.7.0", "mcp"]
+      "args": ["-y", "rea-agents@6.4.0", "mcp"]
     }
   }
 }
@@ -1299,21 +875,6 @@ on the shell `PATH`. Use the setup command above for the guided setup
 journey, `npx -y rea-agents@latest` for unattended one-off commands, or install globally
 with `npm install --global rea-agents` for a shell-visible `rea` command.
 
-For many concurrent agent sessions, run setup directly from a global installation
-to avoid keeping a separate npm launcher process for each MCP connection:
-
-```bash
-npm install --global rea-agents
-rea setup
-```
-
-Review the plan, approve the selected client changes, then restart those clients.
-This registers the installed entrypoint directly; installing the global package
-alone does not replace existing `npx` registrations. Each client still has its own
-REA process and analysis state. Direct registrations follow the installed CLI;
-use `rea update` to update it. Running setup through `npx` again selects the pinned
-package-runner command. Do not register paths inside npm's temporary package cache.
-
 The optional curl wrapper installs only the global npm package:
 
 ```bash

docs/getting-started/mcp-prompts.md

@@ -108,17 +108,11 @@ list does not establish that the target has no procedures.
 | Artifact occurrence | Occurrence IDs present in schema-valid retained artifact inventory pages.                                                                            |
 | Residual unknown    | Current non-resolved unknown heads only.                                                                                                             |
 
-Prefix matching is Unicode-normalized and case-insensitive; suggestions retain
-their original spelling. The server deduplicates them and sorts by code point
-for deterministic results. Procedure completion derives candidates from the
-complete inventory, so a name is offered only when it identifies one address in
-that inventory. Every name at a shared address participates in this check,
-including later rows that establish ambiguity. A completion reply carries at
-most 100 values, the MCP limit. `total` counts every match and
-`hasMore` is `true` when values were omitted. Completion has no paging
-controls. A longer prefix reaches an omitted value only when it excludes other
-matches; matching uses normalized, case-insensitive forms, so a value can stay
-unreachable when more than 100 matches share its normalized prefix.
+Suggestions are Unicode-normalized, case-insensitive prefix matches. The server
+deduplicates them and sorts by code point for deterministic results. Procedure
+completion derives candidates from the complete inventory, so a name is offered
+only when it identifies one address in that inventory. Completion returns all
+matching values; it does not expose paging controls.
 
 ## Lifecycle and safety
 

docs/ghidra-ppc.md

@@ -1,90 +0,0 @@
-# PowerPC ELF analysis through Ghidra
-
-This lane extends native ELF analysis to 32-bit big-endian PowerPC; it does
-not execute PowerPC code. It is the first milestone of
-[#1741](https://github.com/morluto/rea/issues/1741). GameCube/Wii DOL
-executables, PPC64 and other PowerPC variants are separate follow-ups.
-
-## Admission boundary
-
-ELF `EM_PPC` (20) is retained as the provider-neutral `powerpc` family. The
-target also retains class, byte order, `e_type` and raw `e_flags`. Recognition
-does not mean every provider or PowerPC variant is supported. `EM_PPC64` (21)
-is not recognized as this family.
-
-The Ghidra lane admits ELF32 `ET_EXEC`, big endian. ELF64, little-endian,
-relocatable and shared objects are refused with a specific unsupported
-constraint. `EF_PPC_EMB` declares an embedded variant and is refused; the
-remaining `e_flags` bits only declare relocation conventions and do not change
-instruction decoding.
-
-## Bound language
-
-Ghidra's ELF loader selects `PowerPC:BE:32:e500:default` for a plain `EM_PPC`
-header with `e_flags` 0. e500 is the embedded Book-E variant whose SPE unit
-replaces the classic floating-point unit, so it misinterprets ordinary
-750-family code. Nothing in the header distinguishes the two.
-
-The lane therefore imports with `PowerPC:BE:32:default` and compiler spec
-`default`, commits that choice in the analysis profile as
-`language_selection: "provider-pinned-v1"`, and checks the language Ghidra
-reports after import. A different language set through
-`REA_GHIDRA_LANGUAGE_ID` (and optionally `REA_GHIDRA_COMPILER_SPEC_ID`)
-replaces the lane default and is admitted against the installed language
-catalog as usual; for example `PowerPC:BE:32:e500` for genuine e500 code.
-
-PowerPC header facts are committed in the analysis profile so interpretation
-changes invalidate profile-bound snapshots. The support-lane identity is
-versioned independently of file identity. Evidence, lifecycle outputs and saved
-snapshots preserve the `powerpc` family. Hopper and IDA adapters do not
-implicitly gain PowerPC support. Windows Ghidra P0 remains PE x86/x86-64 only.
-
-## Use
-
-With a caller-installed Ghidra and compatible JDK on a supported Linux/macOS host:
-
-```bash
-rea analyze /absolute/path/to/ppc.elf --provider ghidra --json
-rea function /absolute/path/to/ppc.elf function_name --provider ghidra --json
-```
-
-MCP uses the existing tools, including `open_binary` with an absolute path and
-`provider_id: "ghidra"`. No PowerPC-specific tool catalog or emulator is
-introduced.
-
-## Verification
-
-The source-owned freestanding fixture is `tests/conformance/c/ppc.c`. The
-optional cross-target lane requires a caller-supplied Clang with the PowerPC
-target, LLD, GNU `readelf`, Ghidra and its compatible JDK; ordinary host-native
-checks do not acquire these tools. `REA_PPC_CLANG` selects Clang and
-`REA_PPC_READELF` selects GNU readelf (for example
-`/opt/homebrew/opt/binutils/bin/readelf` on macOS). These are test-time
-prerequisites, not REA runtime providers.
-
-```bash
-GHIDRA_INSTALL_DIR=/absolute/path/to/ghidra npm run verify:ghidra:ppc
-```
-
-The lane compiles the fixture for a 750-family core (`-mcpu=750`) and never
-executes it. GNU readelf independently supplies header facts and symbol
-addresses, compared with the production REA target resolver before provider
-startup. Its version, bounded command output and selected tool path are
-retained in the verification report. The parser deliberately recognizes only
-this fixture's GNU output, rejecting missing, ambiguous or unexpected fields
-rather than substituting defaults.
-
-Existing public MCP operations check Ghidra's **observed** language and
-compiler specification and loaded-file hashes; an e500 import fails the lane.
-The source-owned `ppc-probe.S` supplies fixed `addi` and conditional-branch
-encodings: verification checks bytes, length, immediate and direct destination,
-independent of decompiler variable names. Global and string bytes are checked at
-independently reported symbol addresses.
-
-CLI/MCP discovery and decompilation, direct calls, target/profile/Evidence
-identity, snapshot round-trip and final process cleanup remain covered.
-Pseudocode presence is a liveness check, not proof of semantic equivalence.
-Instruction decoding and reader agreement do not establish runtime or complete
-floating-point semantics. Parser/profile tests are narrower checks, not
-substitutes for this real-provider run. Report the actual lanes run and leave
-unexecuted verification pending.

docs/godot-pck.md

@@ -1,108 +0,0 @@
-# Godot PCK archives
-
-`inspect-artifact` and `extract-artifact` read ordinary Godot PCK formats 2, 3
-and 4 without running the game or requiring Godot. Official Godot 4.4.1, 4.6.1
-and 4.7.1 produced these respective formats in verification; other engine
-releases have not been verified. Format 1 is unsupported.
-
-Inspection retains the original header and directory facts, including engine
-version, flags, declared file count, source paths, offsets and declared MD5.
-Observed plaintext bytes receive content-addressed SHA-256 identities. MD5 is a
-container integrity claim, separate from the observed SHA-256. A mismatch fails
-by default; `--integrity-policy record-and-continue` retains the observed bytes
-and an explicit untrusted contradiction. An all-zero MD5 is an unknown claim,
-not a verified digest.
-
-## CLI
-
-Start with a compact summary and keep the complete Evidence bundle:
-
-```sh
-rea inspect-artifact /artifacts/game.pck --detail summary \
-  --evidence_output /evidence/game.json --json
-rea extract-artifact /artifacts/game.pck --json
-```
-
-Summary delivery requires `--evidence_output` and never overwrites that file.
-The response contains `summary` Evidence and an `evidence_bundle` receipt.
-Without `--detail summary`, inspection keeps its complete inline delivery.
-Extraction creates a new temporary directory and returns its path. It rejects
-unsafe paths and verifies container identity before creating output.
-
-The same CLI commands locate a PCK at the beginning of a file or through its
-12-byte EOF trailer in an executable carrier. They do not scan arbitrary
-payloads or discover packs behind additional trailing signatures. The root
-content SHA-256 covers the whole carrier; its content classification remains
-native, while the inventory records the PCK role and exact pack bounds.
-Ordinary native `open_binary` detection remains unchanged.
-
-## MCP and selected facts
-
-For a standalone pack, call `open_binary` with its absolute path, then
-`inspect_artifact` with `{"detail":"summary"}`. The complete inspection and its
-nested inventory stay in the session. Use the summary's
-`normalized_result.parent_evidence_id` as the source of subsequent views:
-
-```json
-{
-  "name": "inspect_analysis_view",
-  "arguments": {
-    "source": {
-      "kind": "retained-evidence",
-      "evidence_id": "<parent_evidence_id>"
-    },
-    "view": {
-      "kind": "inventory",
-      "collection": "occurrences",
-      "logical_paths": ["scripts/main.gd", "project.binary"],
-      "fields": [
-        "logical_path",
-        "declared_integrity",
-        "hash_status",
-        "format_metadata"
-      ],
-      "offset": 0,
-      "limit": 32
-    }
-  }
-}
-```
-
-Occurrences retain `occurrence_id`, `artifact_id` and `parent_occurrence_id`
-even when `fields` is empty. Batch occurrence IDs with `occurrence_ids`, or
-join returned content IDs to `collection: "nodes"`, `artifact_ids: [...]` and
-`fields: ["sha256", "size"]`. Filters intersect; an omitted filter selects all
-available rows and an empty array selects none. Pagination follows the filtered
-canonical order. Multiple occurrences may share one content ID.
-
-Views reuse authenticated immutable inventory facts and lazy lookup indexes;
-they do not reopen the source. These are historical observations, including
-after the source changes or disappears. Close the target with `close_binary`
-when finished. To read an exported bundle through the CLI, select its complete
-inspection record as `source: {kind: "inline", evidence: ...}` in a JSON request
-file for `rea inspect-analysis-view request.json --json`.
-
-## Coverage and limits
-
-PCK summaries expose root format metadata, available graph counts,
-`available_hash_status_counts`, and `source_coverage`. Inventory pages preserve
-producer coverage alongside page coverage. `source_complete` means all declared
-retained graph rows are available; it does not establish that an encrypted or
-otherwise unknown directory was examined. Missing matches in unknown coverage
-are not evidence of absence.
-
-Encrypted directories retain their header and declared file count with unknown
-entry coverage. Individually encrypted members retain directory metadata with
-unknown content identity; REA does not decrypt them. Sparse bundles likewise
-retain header facts with unknown member coverage. Extraction refuses an
-unreadable directory or encrypted member. This capability does not recover
-keys, decode Godot resources, decompile GDScript bytecode, analyze signals,
-apply patch/removal entries or execute targets.
-
-Readable logical member bytes, including repeated physical ranges, share the ZIP
-archive expansion policy: at most the larger of 256 MiB or 500 times the PCK's
-encoded byte span. Embedded carrier bytes do not enlarge that budget. The full
-directory is checked before any member is yielded, hashed or extracted. Encrypted
-members are not read and do not consume this plaintext-work allowance. Small
-bounded aliases remain valid. This is a processing/output resource bound, separate
-from the directory metadata retention budget and format validity.

docs/guides/android/adb-device-analysis.md

@@ -26,9 +26,6 @@ Readiness is `rea inspect-adb-client`: it runs `adb version` and reports the
 resolved binary, its version, and where it was selected from. A missing
 binary reports `capability_unavailable` with the `REA_ADB_PATH` remediation
 rather than attempting an installation.
-The `binary_session` inventory uses the same bounded client-version probe; it
-does not query devices, start the adb server, or establish that a requested
-serial is reachable. Device state is checked by each device operation.
 
 ## Answer an analyst question
 
@@ -76,58 +73,32 @@ existing analysis families directly, for example
 
 ## Operations
 
-| Tool                    | Kind               | What it does                                                                                                                                                                                                                          |
-| ----------------------- | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `inspect_adb_client`    | read               | Resolved binary, version, install path; never contacts the server                                                                                                                                                                     |
-| `list_adb_devices`      | read               | Serial, state, transport, model metadata, inferred emulator/physical kind with basis                                                                                                                                                  |
-| `inspect_adb_device`    | read               | Fixed `getprop` whitelist: build, SDK, patch, fingerprint, product, ABIs, debuggable, `ro.kernel.qemu`                                                                                                                                |
-| `inspect_adb_display`   | read               | `wm size` and `wm density` as declared                                                                                                                                                                                                |
-| `list_adb_features`     | read               | `pm list features` (hardware/software features, hex GL versions)                                                                                                                                                                      |
-| `list_adb_services`     | read               | `service list` binder services and interfaces                                                                                                                                                                                         |
-| `list_adb_processes`    | read               | `ps -A`: user, pid, ppid, rss, state, name                                                                                                                                                                                            |
-| `inspect_adb_window`    | read               | `dumpsys window` focus declarations (what is on screen)                                                                                                                                                                               |
-| `read_adb_setting`      | read               | One `settings get` value; device-side null is reported as such                                                                                                                                                                        |
-| `read_adb_logcat`       | read               | Bounded `logcat -d -t` dump for one buffer, optional pid filter                                                                                                                                                                       |
-| `list_adb_packages`     | read               | `pm list packages -f` with scope; base APK device paths                                                                                                                                                                               |
-| `resolve_adb_packages`  | read               | Case-insensitive package-name substring search with exact-match flag                                                                                                                                                                  |
-| `inspect_adb_package`   | read               | `dumpsys package` projection: versions, install times, installer, flags, permission count                                                                                                                                             |
-| `list_adb_directory`    | read               | NUL-framed immediate children, including hidden entries: kinds, permissions, owner, group, sizes, symlink targets                                                                                                                     |
-| `pull_adb_package`      | read               | Complete split APK set from `pm path`, each file digested                                                                                                                                                                             |
-| `pull_adb_file`         | read               | One absolute device path pulled and digested                                                                                                                                                                                          |
-| `capture_adb_screen`    | read               | One `screencap -p` frame (exec-out, no device-side file) with dimensions                                                                                                                                                              |
-| `collect_adb_bugreport` | read               | Device-generated bugreport zip, digested                                                                                                                                                                                              |
-| `push_adb_file`         | **mutates device** | One local file to a device path (e.g. pushing tools into `/data/local/tmp`); checks for existing targets and refuses them without explicit overwrite (the check is not atomic); compares digests when device `sha256sum` is available |
-| `install_adb_package`   | **mutates device** | Local APK via `adb install [-r]`; preserves its Success/Failure verdict, records `replace_requested`, and leaves actual replacement `null` because prior package state is not observed                                                |
-| `uninstall_adb_package` | **mutates device** | Requests package removal for user 0 via `adb shell pm uninstall --user 0`, without data retention                                                                                                                                     |
-| `start_adb_app`         | **mutates device** | Resolves the package's launcher activity (`cmd package resolve-activity --brief`) and starts it (`am start -n`)                                                                                                                       |
-| `start_adb_activity`    | **mutates device** | Starts an intent (`am start -a` with optional URI, component, and up to 16 typed extras); preserves the activity manager's verdict                                                                                                    |
-| `stop_adb_app`          | **mutates device** | Force-stops every process of a package, ending a dynamic-analysis run                                                                                                                                                                 |
-
-For `inspect_adb_window`, `focus_contexts` retains each display header, its exact
-display ID when recognized, and every focus declaration with its original line.
-Declarations without a display header are explicitly `unscoped`. A missing
-declaration differs from a declaration whose `value` is JSON `null`.
-`source_section` identifies the selected dumpsys section; `observed_lines`
-preserves its focus declarations and display headers in source order.
-
-`focus_summary` is `single_context` only for one context with no repeated focus
-field. The singular `focused_window` and `focused_app` summarize that context;
-they do not establish device-wide focus. Multiple contexts or repeated fields
-produce `ambiguous` with null singular fields and all declarations retained.
-When no focus field was declared, the status is `unavailable`. REA reads the
-displays section only when the windows section declares neither focus field.
-
-For `install_adb_package`, `replace_requested` records whether `-r` was sent.
-The `replaced` result is `null`: the successful install response does not say
-whether the package was installed fresh or replaced, and REA does not query the
-device first. The install verdict and host APK digest remain available.
-
-Push and install consume a private snapshot of the selected local input. The
-reported size and SHA-256 identify those consumed bytes; `local_path` and
-`apk_path` retain the original input path, whose contents may change later.
-Snapshot creation needs temporary disk space proportional to the input size.
-Failed snapshot cleanup remains owned and is retried before later operations
-and during shutdown.
+| Tool                    | Kind               | What it does                                                                                                                                                              |
+| ----------------------- | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `inspect_adb_client`    | read               | Resolved binary, version, install path; never contacts the server                                                                                                         |
+| `list_adb_devices`      | read               | Serial, state, transport, model metadata, inferred emulator/physical kind with basis                                                                                      |
+| `inspect_adb_device`    | read               | Fixed `getprop` whitelist: build, SDK, patch, fingerprint, product, ABIs, debuggable, `ro.kernel.qemu`                                                                    |
+| `inspect_adb_display`   | read               | `wm size` and `wm density` as declared                                                                                                                                    |
+| `list_adb_features`     | read               | `pm list features` (hardware/software features, hex GL versions)                                                                                                          |
+| `list_adb_services`     | read               | `service list` binder services and interfaces                                                                                                                             |
+| `list_adb_processes`    | read               | `ps -A`: user, pid, ppid, rss, state, name                                                                                                                                |
+| `inspect_adb_window`    | read               | `dumpsys window` focus declarations (what is on screen)                                                                                                                   |
+| `read_adb_setting`      | read               | One `settings get` value; device-side null is reported as such                                                                                                            |
+| `read_adb_logcat`       | read               | Bounded `logcat -d -t` dump for one buffer, optional pid filter                                                                                                           |
+| `list_adb_packages`     | read               | `pm list packages -f` with scope; base APK device paths                                                                                                                   |
+| `resolve_adb_packages`  | read               | Case-insensitive package-name substring search with exact-match flag                                                                                                      |
+| `inspect_adb_package`   | read               | `dumpsys package` projection: versions, install times, installer, flags, permission count                                                                                 |
+| `list_adb_directory`    | read               | NUL-framed immediate children, including hidden entries: kinds, permissions, owner, group, sizes, symlink targets                                                         |
+| `pull_adb_package`      | read               | Complete split APK set from `pm path`, each file digested                                                                                                                 |
+| `pull_adb_file`         | read               | One absolute device path pulled and digested                                                                                                                              |
+| `capture_adb_screen`    | read               | One `screencap -p` frame (exec-out, no device-side file) with dimensions                                                                                                  |
+| `collect_adb_bugreport` | read               | Device-generated bugreport zip, digested                                                                                                                                  |
+| `push_adb_file`         | **mutates device** | One local file to a device path (e.g. pushing tools into `/data/local/tmp`); refuses existing targets without explicit overwrite; verifies via the device's own sha256sum |
+| `install_adb_package`   | **mutates device** | Local APK via `adb install [-r]`; preserves the device's Success/Failure verdict                                                                                          |
+| `uninstall_adb_package` | **mutates device** | Removes a package and its data for user 0                                                                                                                                 |
+| `start_adb_app`         | **mutates device** | Resolves the package's launcher activity (`cmd package resolve-activity --brief`) and starts it (`am start -n`)                                                           |
+| `start_adb_activity`    | **mutates device** | Starts an intent (`am start -a` with optional URI, component, and up to 16 typed extras); preserves the activity manager's verdict                                        |
+| `stop_adb_app`          | **mutates device** | Force-stops every process of a package, ending a dynamic-analysis run                                                                                                     |
 
 ## Interpret the result
 
@@ -147,16 +118,6 @@ and during shutdown.
   while POSIX hosts retain valid POSIX filenames such as names with spaces or
   colons. A package pull checks reported names against the destination
   filesystem before pulling, and refuses names that would share a local path.
-- **Package path refusals are diagnosable.** Refusals from `pull_adb_package`
-  return `unreadable_output` with `retryable: false`, keep the `pm path` output
-  in `details.captured_output`, and name the refusal in `details.reason`.
-  `unsafe_device_path` lists refused entries in
-  `details.diagnostics.rejected_paths` as `{device_path, reason}`;
-  `duplicate_local_destination` reports the shared `file_name` and both
-  `device_paths`; `local_destination_unavailable` reports the `device_path`,
-  `file_name`, and filesystem `error_code`. Diagnostics retain raw device
-  strings, while the caller-facing message escapes invisible and bidirectional
-  characters so they cannot hide text or reorder the path.
 - **Splits are part of the answer.** `pm path` enumerates the base APK and
   every installed split; pulls cover the whole set. System packages whose
   APKs keep other names report the `unknown` role rather than guessing.
@@ -166,12 +127,8 @@ and during shutdown.
   partial coverage instead of dropping rows.
 - **Mutations are explicit.** `push_adb_file`, `install_adb_package`, and
   `uninstall_adb_package` declare `mutatesTarget` and never run implicitly:
-  pushes check for existing device files before transfer and refuse them
-  unless `overwrite` is set. A failed or unexpected existence probe stops
-  transfer even with `overwrite`; only a clean `test -e` exit of 1 with no
-  output is interpreted as absence. The check is not atomic, so a different
-  process can create the path before `adb push` writes it. When available, the device's
-  `sha256sum` verifies the transfer; installs preserve the
+  pushes refuse existing device files unless `overwrite` is set and verify
+  the transfer with the device's own `sha256sum`; installs preserve the
   device's `Failure [...]` reason verbatim.
 - **Producer identity stays attached.** Every result embeds the producing
   adb client (`binary_path`, `path_source`, `version`, `installed_path`).
@@ -183,19 +140,14 @@ and during shutdown.
   The app/activity lifecycle tools use `am start -W` and `am force-stop`.
 - Per-invocation budgets: client/devices 10-20 s, shell reads 20-60 s with
   64 KiB-8 MiB capture caps (logcat 4 MiB, screen 32 MiB), transfers and
-  bugreports 600 s. Output capture overflow reports `resource_constraint`;
-  deadline expiration, including the client-version probe, reports
-  `provider_timeout`. Command cancellation preserves the caller's exact reason;
-  a later abort does not replace an already completed command failure.
+  bugreports 600 s. Exceeded budgets report `resource_constraint`; stopped
+  commands report `provider_timeout`.
 - Pull and capture outputs are additive: the destination must not already
   exist. Re-running a completed pull refuses the existing directory instead
   of overwriting evidence.
 - Cancellation during a package pull preserves caller-selected output. The
   error includes partial observations identifying completed artifacts and the
   interrupted local path; remaining APKs were not attempted.
-- Screen capture checks cancellation before publishing its exclusive output.
-  If cancellation arrives after publication, the error retains the committed
-  file's path, digest and dimensions; the file remains available as evidence.
 - Bugreports collect into isolated staging and publish with exclusive creation;
   filename collisions select the next numeric suffix. If publication fails, the
   completed archive remains in staging. The error's partial observation gives
@@ -229,4 +181,4 @@ Record: verified against adb 34.0.5 on Linux against an Android 14
 (API 34) x86_64 emulator — all operations above, a 224-package inventory,
 287 services, 92 features, a real two-APK split set pulled with byte-exact
 digests, a verified push/pull roundtrip, a 1.3 MB screen capture, and the
-complete package lifecycle; see `docs/testing.md` for the lane summary.
+complete package lifecycle; see `docs/development/testing.md` for the lane summary.

docs/guides/android/android-analysis.md

@@ -6,13 +6,9 @@ kept as an unmodified, commit-pinned Git submodule; see
 application workflow and return artifact-bound Evidence inline.
 
 This family is present on repository main and in npm 4.1.0. Check the
-[released package boundary](installation.md#released-package-and-main) and the
+[released package boundary](../../getting-started/installation.md#released-package-and-main) and the
 connected server's tool list before selecting it.
 
-On Linux, JADX launches an REA-owned process and requires a procps-compatible
-`ps` on REA's `PATH`; see the shared
-[Linux process prerequisite](installation.md#linux-owned-process-prerequisite).
-
 ## Optional package delivery
 
 The MCP `inspect_android_package` request keeps complete output when `detail` is
@@ -37,40 +33,10 @@ unverified.
 ## Supply tools
 
 Use a **full JDK 17 or newer** (including its compiler module) and
-[**jadx-headless-mcp 0.7.1**](https://github.com/1013503897/jadx-headless-mcp/releases/download/v0.7.1/jadx-headless-mcp-0.7.1-all.jar).
-Verify the downloaded JAR's SHA-256 against
-[REA's pinned release metadata](https://github.com/morluto/rea/blob/main/src/android/JadxRelease.ts)
-before using it. The following download and verification commands work for npm
-package consumers as well as repository checkouts; the repository-only
-`npm run fixtures:android` helper is not included in the npm package.
-
-On macOS or Linux, choose a destination and verify the pinned digest:
-
-```sh
-mkdir -p "$HOME/.local/share/rea/android" &&
-cd "$HOME/.local/share/rea/android" &&
-curl -fL -o jadx-headless-mcp-0.7.1-all.jar https://github.com/1013503897/jadx-headless-mcp/releases/download/v0.7.1/jadx-headless-mcp-0.7.1-all.jar &&
-if command -v sha256sum >/dev/null; then
-  echo '6e5eacf500b64292bfb73c49797c1958f6ee44646e43e868039ae7feb573ff75  jadx-headless-mcp-0.7.1-all.jar' | sha256sum -c -
-else
-  echo '6e5eacf500b64292bfb73c49797c1958f6ee44646e43e868039ae7feb573ff75  jadx-headless-mcp-0.7.1-all.jar' | shasum -a 256 -c -
-fi &&
-export REA_JADX_MCP_JAR="$PWD/jadx-headless-mcp-0.7.1-all.jar"
-```
-
-On Windows, run the equivalent in PowerShell:
-
-```powershell
-$jar = Join-Path $HOME '.local\share\rea\android\jadx-headless-mcp-0.7.1-all.jar'
-New-Item -ItemType Directory -Force (Split-Path $jar) | Out-Null
-Invoke-WebRequest -Uri 'https://github.com/1013503897/jadx-headless-mcp/releases/download/v0.7.1/jadx-headless-mcp-0.7.1-all.jar' -OutFile $jar
-if ((Get-FileHash -Algorithm SHA256 $jar).Hash.ToLowerInvariant() -ne '6e5eacf500b64292bfb73c49797c1958f6ee44646e43e868039ae7feb573ff75') { throw 'JADX JAR SHA-256 does not match REA pinned metadata' }
-$env:REA_JADX_MCP_JAR = $jar
-```
-
-REA runs its packaged Java metadata bridge in source-file mode against the
-unmodified engine JAR. REA does not install Java, an Android SDK, JADX, a device
-service or an emulator. Set the path in the shell or MCP server environment:
+**jadx-headless-mcp 0.7.1**. REA runs its packaged Java metadata bridge in
+source-file mode against the unmodified engine JAR. REA does not install Java,
+an Android SDK, JADX, a device service or an emulator. Set the path in the shell
+or MCP server environment:
 
 ```sh
 export REA_JADX_MCP_JAR=/absolute/path/jadx-headless-mcp-0.7.1-all.jar
@@ -103,10 +69,9 @@ that every class or engine operation will load successfully. Discovery limits
 each ZIP metadata read to 8 MiB before allocation; a larger directory reports
 the exhausted read budget and the selected JAR path.
 
-The filtered class-page bridge (protocol 2) is verified on Linux x86-64 with
-Temurin 21, public Appium ApiDemos 6.0.18 and NewPipe 0.29.1 APKs. Earlier
-metadata-bridge records covered macOS arm64/OpenJDK 21 and Windows x64/JDK 21;
-this protocol revision has not been rerun on those hosts or Linux/JDK 25.
+The current metadata bridge is verified on macOS arm64 with OpenJDK 21 and the
+public Appium ApiDemos fixture. The POSIX adapter also supports Linux; the new
+bridge has not yet undergone real verification on Linux/JDK 25.
 Windows x64 uses an owned Job Object with bidirectional stdio, atomic job
 assignment and kill-on-owner-close. Real Windows verification uses JDK 21 and
 the pinned JADX 0.7.1 JAR; see the real verification lane below.
@@ -147,20 +112,10 @@ queries accept the same `overload_index`; the bridge resolves the selected
 method node and the result reports its index and displayed signature. These
 indices are tied to the current artifact and engine, not stable across builds.
 
-Smali fallbacks select one complete block using the original method name and DEX
-descriptor, before applying the source byte limit. This preserves the selected
-overload even when Java code generation renames a method. If the selected Java
-body was omitted, including a method merged into a synthetic bridge, REA returns
-its original smali with the `java_body_unavailable` marker. The marker describes
-missing Java; it does not infer why the method was omitted or name a replacement.
-Unresolved or duplicate disassembly identities fail instead of attributing another
-method's instructions to the selection.
-
-Native and abstract methods are identified from access flags
-captured before code generation. They report `body_status: "not_available"`, an
-empty source, and the `native_method` or `abstract_method` marker; their declarations
-are not passed through the engine's source slicer. Other missing decompiled bodies
-do not establish either access flag.
+The engine's smali fallback also joins same-name overloads; REA rejects that
+fallback for an overloaded method instead of attributing all bodies to one
+selected overload. Native/abstract methods with no decompiled body report
+`body_status: "not_available"` without inferring which implementation flag caused it.
 
 Static initializers (`<clinit>`) return smali with the
 `static_initializer_disassembly` marker. Java decompilation can move their
@@ -174,10 +129,7 @@ the same source byte limit and explicit truncation reporting.
   permissions and class/resource counts. Summary fields are extracted by the
   upstream engine and should be checked against the retained XML when needed.
   Signature verification is explicitly `not_performed`.
-- Class search filters the engine's cached top-level names before transferring
-  pages, then follows contiguous inventory positions without rescanning earlier
-  rows. It checks selection, scope, examined ranges and counts before reporting
-  complete coverage. Complete producer replies stay in Evidence; an empty `query`
+- Class search consumes all pages and checks their counts. An empty `query`
   inventories all class-name rows; class names are decompiler representations.
   Repeated names remain repeated in `matches` so the inventory row count and
   producer evidence stay visible. `duplicate_names` identifies matching names
@@ -247,12 +199,8 @@ rea project-android-application-graph '{"inventory_evidence":[<inventory_artifac
 ```
 
 The projection reports exact component paths and hashes, runtime-family hints,
-and path-based bridge hypotheses. File and slice occurrences supply component
-endpoints; directory trees and symlinks retain their identities in the source
-inventory without being classified as code files. It does not decode DEX or
-claim observed runtime calls. DEX/JVM runtime hints summarize the classified
-bytecode component lists. Framework hints match complete native library names,
-such as
+and path-based bridge hypotheses. It does not decode DEX or claim observed
+runtime calls. Framework hints match complete native library names, such as
 `libreactnativejni.so`, `libreactnative.so`, `libhermes.so`,
 `libhermes_executor.so`, `libflutter.so`, and `libunity.so`; unrelated names
 such as `libcommunity.so` and `libreactivity.so` do not identify those families.
@@ -317,34 +265,9 @@ settings. Evidence reports the worker's observed `Runtime.maxMemory()` rounded
 down to MiB and retains exact bytes, Java version and visible processors in its
 raw runtime response. The observed allocatable heap can differ from configured
 `-Xmx`, especially with Serial GC. Heap is not a total RSS cap: the JVM also
-uses native memory. A typed JVM memory allocation failure during APK loading
-reports `resource_constraint` with the observed maximum heap in bytes. Known
-heap failures name `REA_JADX_HEAP_MIB` in remediation; other memory regions
-remain unknown. A healthy doctor configuration check does not establish that
-any particular APK fits. Failures before the bridge can report a typed result
-and upstream errors from other operations retain their existing diagnostics;
-error text alone does not establish memory exhaustion.
-
-Independent REA instances have independent queues. Whole
-operations have a **120-second** execution deadline by default, starting after
-they reach the queue's front. For a known slow cold load, such as a large
-multidex APK, select another finite deadline:
-
-```sh
-export REA_JADX_OPERATION_TIMEOUT_MS=600000
-```
-
-The value must be a decimal millisecond count from 1 to 2147483647; anything
-else is refused before Java starts. The same deadline bounds each upstream
-call, a timeout reports the selected value, and a passing JADX configuration
-check in `rea doctor` reports the effective `operation_timeout_ms`. Explicit
-cancellation still ends the operation immediately, and partial observations
-and owned-process cleanup are unchanged. Raising the deadline does not extend
-the bridge's 30-second startup handshake or the upstream **90-second**
-decompilation limit. MCP clients enforce their own tool-call timeouts, and
-setup's derived [client tool timeout](client-configuration.md) does not include
-this setting, so also raise the client timeout when selecting a longer
-deadline.
+uses native memory. Independent REA instances have independent queues. Whole
+operations have a **120-second** execution deadline after reaching the queue's
+front; upstream decompilation is limited to **90 seconds**.
 
 Decoded manifest and method text have a **1 MiB** upstream byte budget and report
 truncation. Class-name pages use indexed slices of up to 4,096 names without changing the
@@ -363,14 +286,6 @@ export REA_ANDROID_TEST_APK="$PWD/_reference/apk-integration/ApiDemos-debug.apk"
 npm run verify:android
 ```
 
-The main lane and Windows Java-selection checks validate the selected JDK and
-engine archive through `validateVerifierJadxConfiguration`. This shared verifier
-boundary supplies the production validator's resource owner and waits for
-retained cleanup before proceeding. Failed closes retain their exact owners for
-retry; prerequisite failures must not be mistaken for completed bridge tests.
-Recovery checks match the typed Java or archive failure and its applicable
-remediation.
-
 The lane also uses the selected full JDK's `jlink` to create a disposable JRE
 without the compiler module. It checks real Java startup failures, missing
 selectors, recovery after failures, and CLI cancellation with owned cleanup.

docs/guides/android/apktool-resource-analysis.md

@@ -0,0 +1,94 @@
+# Apktool resource decoding
+
+REA decodes Android resource tables and the binary manifest through the
+caller's Apktool launcher. This completes the static triad for Android
+targets: Java/Kotlin sources through the JADX family, engine-grade
+decompilation through JEB, and resources through this family. REA never
+installs Apktool or a Java runtime.
+
+## Supply tools
+
+Use Apktool 2.7.0 or newer (verified with 2.7.0) and a Java runtime the
+launcher can find. Select the launcher through the environment:
+
+```sh
+# Optional: absolute path to the apktool launcher (upstream wrapper or a
+# java -jar script); without it, apktool resolves from PATH.
+export REA_APKTOOL_COMMAND=/absolute/path/apktool
+```
+
+Readiness is `rea inspect-apktool-client`: it runs `apktool --version` and
+reports the resolved launcher, its selection source, and its version. A
+missing launcher reports `capability_unavailable` with the
+`REA_APKTOOL_COMMAND` remediation rather than attempting an installation.
+
+On Windows, a `.bat` or `.cmd` launcher (such as Chocolatey's `apktool.bat`)
+runs through an explicit `cmd.exe /d /s /c` call. That call has no AutoRun,
+no delayed expansion, and quotes every argument. A launcher path that
+contains `"`, `%`, `^`, `!`, `&`, `|`, `<` or `>` is reported as
+`not_configured` instead of being passed to `cmd.exe`. If REA's temporary
+decode paths contain those characters, decoding through a batch launcher
+reports `capability_unavailable`.
+
+## Answer an analyst question
+
+```sh
+rea inspect-apktool-client
+rea decode-android-resources /targets/Example.apk
+rea decode-android-resources /targets/Example.apk --locale de
+rea decode-android-resources /targets/Example.apk --no-strings
+```
+
+Equivalent MCP methods are `inspect_apktool_client` and
+`decode_android_resources`. The decode request takes `path`, an optional
+`locale` (project `res/values-<locale>/strings.xml` instead of the default
+table), and `include_strings` (default true). Regional locales such as `pt-BR`
+select Android's `values-pt-rBR`; Android qualifiers such as `pt-rBR` and
+`b+zh+Hans+CN` may also be supplied directly.
+
+## Interpret the result
+
+- **An owned APK snapshot is digested and decoded.** `target.sha256` and
+  `target.bytes` bind the observation to the exact APK that was decoded.
+- **Metadata comes from apktool.yml as apktool printed it.** Version codes
+  keep their own spelling (`'7'` versus `7`); `package_name` is read from
+  the decoded manifest, not inferred.
+- **The manifest is the decoded text**, bounded at 512 KiB and reported as
+  truncated when larger.
+- **Strings are projected verbatim.** Escaped entities stay escaped, and
+  entries containing nested markup (`<b>`, `<xliff:g>`) are counted as
+  unparsed rather than flattened — the limitation names the count. The
+  default table is bounded to 2000 entries with partial coverage when more
+  exist; `locales` lists every `values-<locale>` that has a strings table.
+- **Smali is skipped by design** (`apktool d --no-src`): Java-source
+  recovery belongs to the JADX family. Resource smali edits and rebuild are
+  a follow-up lane with mutation authority.
+- **Workspaces are owned and short-lived.** Decoding happens in a
+  provider-owned temporary directory that is removed before the result is
+  returned. The APK snapshot and framework cache both live inside this directory.
+  If removal fails, the result names the residual path and the provider retains
+  ownership for a cleanup retry on close, including failed decodes.
+
+## Resource and lifecycle limits
+
+- The decode runs with a 600 s deadline and a 4 MiB output capture budget;
+  a stopped decode reports `provider_timeout` and exceeded budgets report
+  `resource_constraint`.
+- Manifest reads are bounded to 512 KiB before decoding UTF-8. Strings XML
+  reads are bounded to 8 MiB; larger documents are skipped with partial
+  coverage and an explicit limit, rather than reported as missing.
+- `decoded_file_count` is capped at 100,000 files; the cap is reported in
+  the limitations when hit.
+- Apktool's own decode failures (`AndrolibException`, directory traversal
+  refusals) surface as `unsupported_target` with apktool's reason preserved
+  verbatim.
+
+## Real verification
+
+`npm run verify:apktool -- --apk PATH` exercises both operations against a
+real launcher. Record: apktool 2.7.0-dirty (Debian packaging) on Linux with
+OpenJDK 25 against a signed aapt2-built probe APK carrying two resource
+locales — launcher version, on-disk digest agreement, apktool.yml metadata
+(1.2.3, SDK 24–34), manifest package agreement, default and `de` string
+tables projected. Parser goldens in the test suite come from the same
+decode. See `docs/development/testing.md` for the lane summary.

docs/guides/android/flutter-analysis.md

@@ -23,9 +23,7 @@ rea inspect-dart-aot /targets/Example.apk --abi armeabi-v7a
 The equivalent MCP methods are `identify_flutter_build` (with `path`) and
 `inspect_dart_aot` (with `path` and an optional `abi`; the default prefers
 arm64-v8a, then x86_64, then x86, then armeabi-v7a, then the remaining
-ABIs alphabetically). An explicit `abi` is the directory label exactly as
-`identify_flutter_build` reports it, so a payload under a nonstandard label
-stays selectable and keeps that label in the result.
+ABIs alphabetically).
 
 ## Optional retained AOT delivery
 

docs/guides/apple/apple-application-analysis.md

@@ -60,15 +60,6 @@ states that absence is unknown. Component arrays remain complete when candidate
 hypotheses are omitted; component arrays still include every component from
 the supplied inventory pages, and overall coverage is `partial` in that case.
 
-Inventoried files whose bytes were not read, such as encrypted archive members,
-are listed in `unavailable_components` with their original path, format,
-encryption flag, limitations, and null content identity. The same application-root
-and AppleDouble attribution rules apply. These files make overall coverage
-`partial`; component absence is unknown even when `inventory_complete` is true.
-Directories have no file bytes and symlinks remain in `symlinks`, so neither is
-an unavailable file component. The additive field participates in `projection_id`,
-including when empty, so Apple projection identifiers change.
-
 ## Application roots
 
 | Inventory root                         | Application root                                    |
@@ -77,15 +68,6 @@ including when empty, so Apple projection identifiers change.
 | `.app` directory                       | `.`, the inventoried bundle itself                  |
 | Directory, ZIP, or DMG containing apps | Each outermost `<Name>.app` followed by `Contents/` |
 
-File and slice occurrences supply component endpoints. Directory tree identities
-remain in source inventory and bundle anatomy, and links remain in `symlinks`.
-
-Root and layout discovery use known directories and ancestors implied by deeper
-inventory paths. A leaf file or symlink named `*.app`, `Contents`, or `Versions`
-does not establish that directory. Directory and authenticated-file identity are
-selected before applying anatomy case preferences, so a file cannot shadow a
-folded directory name or a directory shadow a metadata/signature file.
-
 ZIP archives made with `ditto -c -k --keepParent` report `<Name>.app`. A DMG
 reports `<image>.dmg/<Volume>/<Name>.app`; DMG child inventory needs the native
 macOS mounting adapter. When a DMG has only its root identity, the projection is

docs/guides/data/packet-captures.md

@@ -54,22 +54,6 @@ resource limit; use selected fields, a display filter or an input-packet limit
 when dissection output is too large. Each call checks the recording's current
 digest, so pages from different source digests must not be combined.
 
-For a question about a known input prefix, select `packet_limit` for that
-prefix, the fields needed for the answer, and a matching output window. For
-example, a question about the first twelve PostgreSQL TCP packets within
-original frames 1–2,000 can use fields `tcp.srcport`, `tcp.dstport`, `tcp.flags`,
-filter `tcp.port == 5432`, `packet_limit: 2000` and `match_limit: 12`.
-The matching count then describes that input prefix. A filter containing
-`frame.number <= 2000` without an input limit still reads the entire capture;
-returning twelve rows does not limit producer output. These controls answer a
-bounded question and must not be used to infer whole-capture absence.
-
-Discover unfamiliar field names with `inspect_packet_fields`, using an exact
-protocol and a narrow query. If the installed names are already established,
-direct field selection avoids an additional glossary probe. Count discovery
-and any retries when comparing investigation cost; a small page alone does
-not establish a faster workflow.
-
 Additional selections:
 
 - `display_filter`: Wireshark display-filter syntax; omitted means no filter.

docs/guides/data/pcap-analysis.md

@@ -58,11 +58,6 @@ tools read that copy, which is hashed again after analysis. Capture metadata and
 literal field values are producer observations; address/protocol counts and DNS
 associations are derivations. Capture Evidence has historical-reference authority.
 
-`capture_start` and `capture_end` are RFC 3339 UTC instants derived from
-`capinfos -S` epoch seconds, retaining all producer fractional digits (up to
-nanoseconds). Empty captures, malformed timestamps and instants outside years
-0000–9999 remain `null`; host-local timestamps without a zone are not inferred.
-
 Addresses count once per packet, including loopback and nested IP occurrences.
 DNS addresses are associated only with one question in the same response packet;
 additional records may be included, so this does not prove final resolution.

docs/guides/data/sqlite-databases.md

@@ -57,10 +57,7 @@ triggers or arbitrary SQL.
 Rows are optional. `table` selects one exact ordinary-table name. `columns`
 (CLI repeated `--column`) selects exact visible column names in the requested
 order; omission selects all visible columns, including generated columns.
-Unselected cells are not evaluated or projected. Malformed column-name bytes
-cause a format refusal when all columns are requested. In inventory scope, an explicit valid subset can
-still be sampled without decoding unrelated malformed column names.
-Column selection requires a
+Unselected cells are not evaluated or projected. Column selection requires a
 table and at least one name; empty-string identifiers are valid. `row_limit`
 requires `table`, defaults to 20 and accepts positive safe integers. Samples
 remain subject to the byte and worker resource limits below, regardless of row count. The result reports
@@ -108,20 +105,6 @@ overall native heap and total resident memory are not capped. Row limits do not
 override these byte and resource limits. Resource-limit failures do not return
 an incomplete schema as successful complete evidence.
 
-If the combined database and WAL exceed the snapshot budget, the refusal is a
-`resource_constraint` and reports both the configured byte limit and the exact
-observed combined size as a decimal string. The remediation directs callers to
-create a smaller consistent offline snapshot containing only relevant data
-through the application's supported export workflow. A generic backup or copy
-does not guarantee a smaller result; REA does not truncate or modify the
-selected source.
-
-On hosts that cannot address the derived WAL or rollback-journal path for a
-long selected database name, REA reports that the SQLite capability is
-unavailable. It does not assume an inaccessible sidecar is absent. Use the
-application's supported consistent offline export or copy workflow to place
-the complete known file set at a shorter path.
-
 MCP also applies its configured response budget to the complete Evidence
 envelope. If delivery exceeds that budget, it reports a transport constraint
 with guidance for exporting retained Evidence, requesting a matching larger