fix(javascript): stop classifying replaced globals as built-in effects

Timer, request, coercion and JSON.parse effects recognized unbound globals
without consulting visible source-local writes, so `setTimeout = f` or
`self.fetch = f` still produced Node timer and fetch operations.

The ambient write owner now classifies a global reference as unmodified,
possibly replaced (a write under an unknown key, such as
`globalThis[k] = v`), or replaced (an exact visible write). Replaced globals
no longer produce built-in effects; possibly replaced ones keep the effect
with partial resolution instead of dropping it. The member-specific
`isUnmodifiedGlobalMember` helper is superseded and removed.

Fixes #3367

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.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/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: "44"
+  version: "42"
 ---
 
 # REA
@@ -30,8 +30,6 @@ unavailable, read [connection and recovery](references/connection-and-recovery.m
 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.
-If the host times out without a REA result, do not repeat the unchanged call or
-assume work stopped. Read the recovery guide's deadline distinction before retrying.
 
 1. Diagnose without changing REA or client configuration. `npx` may download
    the package and write to npm's cache. For Codex, run
@@ -61,7 +59,7 @@ assume work stopped. Read the recovery guide's deadline distinction before retry
    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
+JADX, 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.
@@ -81,7 +79,7 @@ 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
 
@@ -91,19 +89,9 @@ explicit path or endpoint and do not need it.
 
 - ASAR or extracted JavaScript/Electron tree:
   `analyze_javascript_application`.
-- Archive/package member inventory (ZIP/APK/IPA/MSIX/AppX, DMG, or a PyInstaller
-  executable): `open_binary` with the supplied local path; use `inspect_artifact`
-  when its graph and findings help answer the question. A PyInstaller CArchive
-  is the application layer; the bootloader is only the native prefix. Start with
-  `detail: "summary"` for large inventories, then use retained inventory views
-  for selected member fields/pages. A complete small inventory can cost less
-  than extra calls and schemas. Runtime options are metadata, not files.
-  Compact delivery still inventories and hashes members. See the
-  [Python packaged applications guide](https://github.com/morluto/rea/blob/main/docs/python-packaged-applications.md).
-- Apple app plist, Interface Builder, asset catalog, or keyed archive resources:
-  `open_bundle_resources`, then the selected resource tool. This does not
-  require `CFBundleExecutable` or a deep provider. Resource sessions have no
-  executable digest or binary snapshot; use `open_binary` for native code.
+- Archive/package member inventory (ZIP/APK/IPA/MSIX/AppX or DMG):
+  `open_binary` with the supplied local path; use `inspect_artifact` when its
+  graph and findings help answer the question.
 - Android APK code, classes, methods, or incoming references:
   `inspect_android_package`, then focused Android tools when advertised.
   Archive member inventory still uses the archive route above.
@@ -167,9 +155,7 @@ explicit path or endpoint and do not need it.
   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).
 - Explicit local EVM bytecode carrier: `inspect_evm_interface` with caller-selected
-  `raw` or `hex` encoding. The owned worker deadline is `timeout_ms` (default
-  30000 ms, range 1..2147483647, next call). It does not raise the fixed byte,
-  address-space, or CPU allowances. Preserve carrier/decoded digests and treat selectors,
+  `raw` or `hex` encoding. Preserve carrier/decoded digests and treat selectors,
   argument strings and mutability as inferred candidates; this performs no chain
   lookup or target execution. For the complete inferred interface without hex or
   duplicate stdout, discover support and select `detail: "summary"`; complete
@@ -183,40 +169,12 @@ explicit path or endpoint and do not need it.
   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).
-- Embedded CUDA/HIP code objects: `inspect_gpu_code_objects`; inventory targets
-  first, then decode selected payloads and query retained GPU Evidence.
-- Bundled GGUF or safetensors model declarations: `inspect_model_artifact`
-  with the explicit local file. Default header hashing leaves full-file identity
-  unknown; `hash: "full"` additionally reads all weights for SHA-256. MCP returns
-  retained summaries; optional `view` selects one page in the initial call. Use
-  `inspect_analysis_view` kind `model-artifact` for
-  batched metadata keys, tensor names or type totals, selected fields and pages.
-  Preserve header-scoped indices and array preview omissions; do not infer model
-  behavior from declared architecture or tensor types. See the
-  [model file guide](https://github.com/morluto/rea/blob/main/docs/model-artifacts.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.
-  For selected crates, use `view: {collection: "packages", names: [...],
-  fields: ["name", "version", "source"]}` on the first call; explicitly include
-  `dependencies` for direct index references. Use `detail: "summary"` for counts
-  and ranges, or retained `inspect_analysis_view` Rust package/edge pages for
-  subsequent filters. Keep the complete parent Evidence accessible; CLI compact
-  delivery requires `--evidence_output`.
   See the
   [Rust binary guide](https://github.com/morluto/rea/blob/main/docs/rust-binaries.md).
 
@@ -257,20 +215,6 @@ after opening; IDA does not supply `binary_overview`. Consult session availabili
 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
@@ -289,12 +233,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.

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

@@ -24,10 +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 (integer milliseconds from 1 to 2147483647, default
-120000; a change applies on the next process start; 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/connection-and-recovery.md

@@ -34,47 +34,6 @@ answers part of the question, and name the unavailable evidence separately.
 Do not substitute another target. Label observations from ordinary shell tools
 as such; only actual REA output supplies REA Evidence.
 
-## Distinguish client and server deadlines
-
-A host message such as `timed out awaiting tools/call` with no REA result means
-the client's deadline expired before a result arrived. It does not establish
-that REA finished, canceled successfully, or released all resources. Do not
-repeat the unchanged analysis. Inspect available session/provider state and
-retained Evidence only when useful; an idle `binary_session` is not proof that
-every target-free operation stopped. Never invent a missing Evidence reference.
-
-Allow the host tool deadline to cover execution, cancellation/cleanup, and
-response delivery. In Codex, the setting is
-`mcp_servers.<server-id>.tool_timeout_sec` in **seconds**, not
-`startup_timeout_sec`. Select a value for the actual operation budget and
-headroom, not a universal timeout. See the
-[official MCP configuration reference](https://learn.chatgpt.com/docs/extend/mcp?surface=cli).
-Apply configuration changes only within the authorized scope, preserving
-unrelated entries and backups; reconnect/restart as required by the host.
-When configuration is not editable, report the setting needed or use an
-authorized CLI fallback. Do not silently broaden permissions or switch targets.
-
-A returned REA `provider_timeout` instead means the **server/provider** reached
-its deadline. Follow its `remediation.action`, reuse accessible partial Evidence,
-and resolve reported incomplete cleanup before retrying. Raising only the
-client deadline does not change this server budget. For static JavaScript,
-`analysis_timeout_ms` (CLI `rea analyze-javascript-application <path>
---analysis-timeout-ms <milliseconds>`) controls each source's
-startup, analysis and transfer deadline in **milliseconds**. Increase that
-budget or reduce semantic work / select exact inventoried `source_paths` when
-the task permits. Omit `source_paths` for all sources; `[]` is invalid.
-`detail: "summary"` reduces delivery, not analysis work. A per-source budget
-does not bound the elapsed time for an entire multi-source application.
-Partial-Evidence inspection can avoid recomputation; an unavailable reader is
-not itself a reason to block a corrected static-analysis retry.
-The shorthand `rea analyze <path>` does not expose this timeout flag; use the
-explicit JavaScript command when changing that budget.
-
-For invalid arguments, use the connected tool's current input schema, or the
-installed CLI's command help. Refresh the catalog if stale; do not guess fields
-from an older skill or return the entire catalog to repair one field. Correct
-all reported fields before retrying.
-
 ## Repair registration when needed
 
 For Codex:

.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.
@@ -80,23 +69,3 @@ 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.
-`rea environment-serve manifest.json --evidence capture.json` derives that
-state at startup, answers read tools from it and serves `data/reset`,
-`data/add` and `data/get` on `/agentenv`; write tools are not served. It
-replays the capture instead with `--replay-only` or when the state is
-unavailable (not derivable, or a catalog over the discovery budget), and its
-stopped document's `state` says which applied.

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

@@ -18,15 +18,9 @@ only selected files. The result and summary record `source_selection`; files
 outside scope and their relationships remain unknown, so partial application
 coverage does not mean the selected source failed. Use repeated `--source-path`
 on either static application CLI route. Omit the selection when the question
-requires complete application analysis; `source_paths: []` is invalid, not an
-unfiltered request. `detail: "summary"` reduces delivery
+requires complete application analysis. `detail: "summary"` reduces delivery
 and does not by itself reduce analysis work.
 
-ASAR header/index admission is fixed at 16 MiB / 16777216 bytes for this
-release and has no runtime override. `source_paths`, `detail`, and
-`max_heap_mb` do not bypass or raise it. Analyze an extracted directory, or
-supply an archive whose header fits.
-
 Exact `#alias` specifiers resolve through the importer's
 enclosing package `imports` map to package-local files; nested `node_modules`
 packages use their own map. Wildcard, recursive, and external-package import
@@ -41,9 +35,7 @@ the complete application Evidence inline when it fits.
 When the connected schema advertises `max_heap_mb` and `analysis_timeout_ms`,
 these select the isolated source analyzer's old-space heap and per-source
 deadline. Defaults are 1024 MiB and 300000 ms. They do not change the MCP
-process heap or the client's tool deadline. For a host timeout without REA
-output, use the [deadline recovery guide](connection-and-recovery.md#distinguish-client-and-server-deadlines)
-instead of raising the server budget. A Bun-hosted REA does not enforce the heap choice; on Windows it
+process heap. A Bun-hosted REA does not enforce the heap choice; on Windows it
 instead limits the analyzer's committed memory to that choice plus a 512 MiB
 runtime reserve.
 Resource-limited analyses preserve completed static facts and
@@ -102,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
@@ -203,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
@@ -212,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,48 +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.
-
-## Apple app resources
-
-Use `open_bundle_resources` with the selected app path, then `inspect_plist`,
-`decode_interface_builder`, `inspect_asset_catalog`, or `inspect_keyed_archive`.
-The resource session reads the app without resolving `CFBundleExecutable` or
-starting a deep provider. Preserve `resource_root` provenance, per-resource
-hashes where reported, and null executable identity; a directory path is not
-an executable digest. Export retained Evidence before closing or switching
-roots. Binary analysis snapshots do not apply. Use `open_binary` to switch to
-executable analysis, and `close_binary` to release either session kind.
-
-The four matching CLI commands accept the app path directly. For an archive
-inside the app, use `inspect-keyed-archive APP_PATH RELATIVE_ARCHIVE_PATH`.
-Host requirements for plist and compiled asset/Interface Builder tooling still
-apply; a resource-only session does not establish provider availability.
-
-## 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
@@ -54,34 +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.
 
-## Model files
-
-Use `inspect_model_artifact` (`inspect-model-artifact PATH`) for local GGUF v2/v3
-and safetensors declarations without a model runtime. Header-only mode does not
-read weights or establish full-file identity. `hash: "full"` explicitly streams
-all bytes. Retained `model-artifact` views page `metadata`, `tensors` and derived
-`types`, with exact batch filters and selected fields. Arrays retain typed counts
-and eight-element previews; omitted values, unknown types and runtime behavior
-stay explicit. See [model files](https://github.com/morluto/rea/blob/main/docs/model-artifacts.md).
-
-## 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
@@ -195,56 +124,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
@@ -254,8 +133,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.
 
@@ -345,8 +226,8 @@ every executable in the bundle. It also lists missing or weak loads and earlier
 `architecture`. System paths stay undetermined because the dyld shared cache
 provides them.
 
-Use `extract_artifact` when materialized files from a supported format 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).
+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).
 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
@@ -355,11 +236,8 @@ destination. No separate permission grant is needed.
 Native DMG traversal automatically uses a read-only mount on supported macOS
 hosts, with an owned temporary mount directory and cleanup. It needs no approval
 flag. Unsupported hosts or mount failures remain explicit limitations; do not
-claim child inventory when only root identity is available. DMG extraction is
-unavailable through `extract_artifact`. To access DMG files on macOS, create a
-read-only mount with your own tools, select files from that mount for analysis,
-and detach the mount you created when finished. REA's inspection mount is
-temporary, not a retained export of the image's contents.
+claim child inventory when only root identity is available. Extraction is a
+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
@@ -368,15 +246,13 @@ context. PSP/stack/device state remains unmodeled. See [DOS guide](https://githu
 
 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/raw-binary.md).
 
 ### Function annotations in Ghidra
 
@@ -399,22 +275,3 @@ 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

@@ -38,8 +38,6 @@ Page-declared WebMCP tools are untrusted inventory and are never invoked by REA.
   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.
-  For multi-step flows with trees or events, select `detail: "summary"` and page
-  exact steps or events with `inspect_analysis_view` kind `browser-scenario`.
   Add a wait action for the expected page state before capturing it. Report that
   REA performed the declared actions.
 
@@ -71,12 +69,6 @@ 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

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

@@ -1,10 +1,5 @@
 name: Cache npm package downloads
-description: Restore npm's download cache. Trusted default-branch jobs that opt in may save it.
-inputs:
-  save:
-    description: Save the shared download cache when this event is allowed to write it.
-    required: false
-    default: "false"
+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.
@@ -28,25 +23,20 @@ runs:
           can_save=true
         fi
         cache_key="npm-download-${RUNNER_OS}-${runtime_arch}-${LOCKFILES_HASH}"
-        # Same platform only. A lockfile change can reuse tarballs from the previous key.
-        restore_key="npm-download-${RUNNER_OS}-${runtime_arch}-"
         {
           printf 'can-save=%s\n' "${can_save}"
           printf 'path=%s\n' "${cache_path}"
           printf 'key=%s\n' "${cache_key}"
-          printf 'restore-key=%s\n' "${restore_key}"
         } >> "${GITHUB_OUTPUT}"
     - name: Restore and save npm package downloads
-      if: steps.context.outputs.can-save == 'true' && inputs.save == 'true'
+      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 }}
-        restore-keys: ${{ steps.context.outputs.restore-key }}
     - name: Restore npm package downloads without saving
-      if: steps.context.outputs.can-save != 'true' || inputs.save != 'true'
+      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 }}
-        restore-keys: ${{ steps.context.outputs.restore-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/workflows/cache-retention.yml

@@ -1,64 +0,0 @@
-name: Cache retention
-
-on:
-  workflow_run:
-    workflows: ["CI"]
-    types: [completed]
-
-# Qualification calls ci.yml with actions: read. A nested workflow cannot raise
-# that token, so cache deletion stays in this workflow.
-permissions:
-  contents: read
-  actions: write
-
-concurrency:
-  group: cache-retention-${{ github.event.workflow_run.head_sha }}
-  cancel-in-progress: false
-
-jobs:
-  retain:
-    name: Retain Turbo snapshots and npm download caches
-    # Restrict the triggering-source checkout to same-repository default-branch
-    # CI events. The helper runs from this trusted workflow revision; triggering
-    # source is used only for cache identity and is never executed. Static and
-    # build save snapshots before later lanes finish, so failed, timed-out, or
-    # cancelled runs still retain those snapshots.
-    if: >-
-      (github.event.workflow_run.conclusion == 'success' ||
-      github.event.workflow_run.conclusion == 'failure' ||
-      github.event.workflow_run.conclusion == 'timed_out' ||
-      github.event.workflow_run.conclusion == 'cancelled') &&
-      github.event.workflow_run.head_repository.full_name == github.repository &&
-      github.event.workflow_run.head_branch == github.event.repository.default_branch &&
-      (github.event.workflow_run.event == 'push' ||
-      github.event.workflow_run.event == 'schedule' ||
-      github.event.workflow_run.event == 'workflow_dispatch')
-    runs-on: ubuntu-latest
-    timeout-minutes: 10
-    steps:
-      - uses: actions/checkout@11d5960a326750d5838078e36cf38b85af677262 # v4.4.0
-        with:
-          ref: ${{ github.workflow_sha }}
-          path: trusted-retention
-          persist-credentials: false
-      - uses: actions/checkout@11d5960a326750d5838078e36cf38b85af677262 # v4.4.0
-        with:
-          ref: ${{ github.event.workflow_run.head_sha }}
-          path: triggering-source
-          persist-credentials: false
-      - uses: actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020 # v4.4.0
-        with:
-          node-version-file: trusted-retention/.nvmrc
-      - name: Retain current Turbo snapshots and npm download caches
-        env:
-          GH_TOKEN: ${{ github.token }}
-          CI_REPOSITORY: ${{ github.repository }}
-          CACHE_PREFIX: rea-static-v1-${{ runner.os }}-${{ runner.arch }}-
-          CACHE_KEEP_KEY: rea-static-v1-${{ runner.os }}-${{ runner.arch }}-${{ hashFiles('triggering-source/.nvmrc', 'triggering-source/.npmrc', 'triggering-source/package-lock.json') }}-${{ github.event.workflow_run.head_sha }}
-          CACHE_DEEP_PREFIX: rea-static-deep-v1-${{ runner.os }}-${{ runner.arch }}-
-          CACHE_DEEP_KEEP_KEY: rea-static-deep-v1-${{ runner.os }}-${{ runner.arch }}-${{ hashFiles('triggering-source/.nvmrc', 'triggering-source/.npmrc', 'triggering-source/package-lock.json') }}-${{ github.event.workflow_run.head_sha }}
-          CACHE_KNIP_PREFIX: knip-meta-v1-${{ runner.os }}-
-          CACHE_KNIP_KEEP_KEY: knip-meta-v1-${{ runner.os }}-${{ hashFiles('triggering-source/knip.json', 'triggering-source/tsconfig.json', 'triggering-source/package.json', 'triggering-source/package-lock.json') }}-${{ github.event.workflow_run.head_sha }}
-          CACHE_PORTABLE_PREFIX: rea-portable-build-v2-${{ runner.os }}-${{ runner.arch }}-
-          DEDUPE_NPM_DOWNLOADS: "true"
-        run: node trusted-retention/scripts/ci/cache-retention.mjs

.github/workflows/ci.yml

@@ -15,15 +15,6 @@ on:
         description: Exact qualification source; must match the caller revision.
         required: true
         type: string
-      remote_cache_write:
-        description: Trusted release qualification may publish the remote cache.
-        required: false
-        type: boolean
-        default: false
-    secrets:
-      TURBO_TOKEN:
-        description: Remote cache token. Only trusted release qualification passes it.
-        required: false
 
 permissions:
   contents: read
@@ -38,15 +29,6 @@ concurrency:
 
 env:
   HUSKY: "0"
-  # Set Actions secret TURBO_TOKEN and variable TURBO_TEAM. OIDC can mint
-  # TURBO_TOKEN via vercel/setup-turborepo-remote-cache-action; do not commit a token.
-  # A called workflow sees the caller event, so workflow_call is not an event
-  # name here. Release qualification sets remote_cache_write and passes the
-  # token. Open pull requests get an empty token and the local cache only.
-  # Remote reads need a credential, and pull requests do not receive one.
-  TURBO_TOKEN: "${{ (inputs.remote_cache_write == true || (github.ref == format('refs/heads/{0}', github.event.repository.default_branch) && (github.event_name == 'push' || github.event_name == 'schedule' || github.event_name == 'workflow_dispatch'))) && secrets.TURBO_TOKEN || '' }}"
-  TURBO_TEAM: ${{ vars.TURBO_TEAM }}
-  TURBO_CACHE: "${{ (inputs.remote_cache_write == true || (github.ref == format('refs/heads/{0}', github.event.repository.default_branch) && (github.event_name == 'push' || github.event_name == 'schedule' || github.event_name == 'workflow_dispatch'))) && 'local:rw,remote:rw' || 'local:rw' }}"
 
 jobs:
   changes:
@@ -77,9 +59,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 }}
@@ -146,9 +126,6 @@ jobs:
       - name: Cache npm package downloads
         id: npm-cache
         uses: ./.github/actions/npm-cache
-        with:
-          # Linux x64 writer. Parallel Linux jobs restore this key.
-          save: "true"
       - run: npm ci
       - name: Restore static task cache
         if: needs.changes.outputs.code == 'true'
@@ -162,20 +139,19 @@ jobs:
       - 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 }}
-          CI_STATIC_CONTEXT_SCRIPT: check:ci:fast:tasks
         run: npm run ci:static-context
       - if: needs.changes.outputs.code == 'true'
-        run: npm run check:ci:fast
+        run: npm run check:ci
+      - if: needs.changes.outputs.code == 'true'
+        run: npm run verify:test-discovery
+      - name: Check LLDB producer retention and launch contracts
+        if: needs.changes.outputs.code == 'true'
+        run: npm run test:python
       - if: needs.changes.outputs.code != 'true'
         run: npm run format:check
       - name: Save validated static task cache
@@ -197,72 +173,6 @@ jobs:
           if-no-files-found: ignore
           retention-days: 7
 
-  static-deep:
-    name: Deep static checks
-    needs: changes
-    # Full qualification only. Provider lanes wait on fast static, not this job.
-    if: needs.changes.outputs.tier == 'full' && needs.changes.outputs.code == 'true'
-    runs-on: ubuntu-latest
-    timeout-minutes: 15
-    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: Restore deep static task cache
-        id: static-cache
-        uses: actions/cache/restore@0057852bfaa89a56745cba8c7296529d2fc39830 # v4.3.0
-        with:
-          path: .turbo/cache/
-          key: rea-static-deep-v1-${{ runner.os }}-${{ runner.arch }}-${{ hashFiles('.nvmrc', '.npmrc', 'package-lock.json') }}-${{ github.sha }}
-          restore-keys: rea-static-deep-v1-${{ runner.os }}-${{ runner.arch }}-${{ hashFiles('.nvmrc', '.npmrc', 'package-lock.json') }}-
-      - name: Restore Knip analysis cache
-        id: knip-cache
-        uses: actions/cache/restore@0057852bfaa89a56745cba8c7296529d2fc39830 # v4.3.0
-        with:
-          path: node_modules/.cache/knip
-          # Each trusted commit publishes a new entry. Restore still matches the
-          # configuration prefix from the previous successful full run.
-          key: knip-meta-v1-${{ runner.os }}-${{ hashFiles('knip.json', 'tsconfig.json', 'package.json', 'package-lock.json') }}-${{ github.sha }}
-          restore-keys: knip-meta-v1-${{ runner.os }}-${{ hashFiles('knip.json', 'tsconfig.json', 'package.json', 'package-lock.json') }}-
-      - name: Record deep static task source and execution identity
-        continue-on-error: true
-        env:
-          CI_PR_HEAD_SHA: ${{ github.event.pull_request.head.sha }}
-          CI_STATIC_CONTEXT_SCRIPT: check:ci:deep:tasks
-        run: npm run ci:static-context
-      - name: Run deep static checks
-        run: npm run check:ci:deep
-      - name: Save validated deep static task cache
-        if: >-
-          success() && 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: Save Knip analysis cache
-        if: >-
-          success() && steps.npm-cache.outputs.can-save == 'true' &&
-          steps.knip-cache.outputs.cache-hit != 'true'
-        uses: actions/cache/save@0057852bfaa89a56745cba8c7296529d2fc39830 # v4.3.0
-        with:
-          path: node_modules/.cache/knip
-          key: ${{ steps.knip-cache.outputs.cache-primary-key }}
-      - name: Upload complete deep static diagnostics
-        if: always()
-        uses: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02 # v4.6.2
-        with:
-          name: static-deep-check-reports
-          path: .cache/static-checks/
-          include-hidden-files: true
-          if-no-files-found: ignore
-          retention-days: 7
-
   test-source:
     name: Source tests
     needs: changes
@@ -302,11 +212,9 @@ jobs:
       # every shard's diagnostics and coverage. Passing PRs run the full suite.
       fail-fast: ${{ github.event_name == 'pull_request' && needs.changes.outputs.tier == 'fast' }}
       matrix:
-        # Fast feedback uses one source group and eight built groups so the
-        # slowest built shard job stays inside a ten-minute execution budget.
-        # Classification, build, and report merge sit outside that job.
-        # Full qualification retains six complete shards with coverage.
-        shard: ${{ fromJSON(needs.changes.outputs.tier == 'fast' && '["1/8","2/8","3/8","4/8","5/8","6/8","7/8","8/8"]' || '["1/6","2/6","3/6","4/6","5/6","6/6"]') }}
+        # 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"]') }}
     steps:
       - uses: actions/checkout@11d5960a326750d5838078e36cf38b85af677262 # v4.4.0
       - uses: actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020 # v4.4.0
@@ -388,8 +296,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:
@@ -409,9 +316,7 @@ jobs:
         with:
           save: ${{ github.event_name != 'pull_request' && github.ref == format('refs/heads/{0}', github.event.repository.default_branch) }}
       - run: npm run test:prepare
-      # Fast and full shards measure different file costs. Download only the
-      # matching history so one tier cannot pack the other with its weights.
-      - name: Find available trusted timing history
+      - name: Find available trusted full-suite timing history
         id: history
         continue-on-error: true
         env:
@@ -419,14 +324,13 @@ jobs:
           CI_REPOSITORY: ${{ github.repository }}
           CI_REPOSITORY_ID: ${{ github.repository_id }}
           CI_DEFAULT_BRANCH: ${{ github.event.repository.default_branch }}
-          CI_TIMING_TIER: ${{ needs.changes.outputs.tier }}
         run: node scripts/ci/test-history.mjs
       - name: Download previous timing report
         if: steps.history.outputs.run-id != ''
         continue-on-error: true
         uses: actions/download-artifact@d3f86a106a0bac45b974a628896c90dbdf5c8093 # v4.3.0
         with:
-          name: ${{ steps.history.outputs.artifact-name }}
+          name: test-timings
           run-id: ${{ steps.history.outputs.run-id }}
           github-token: ${{ github.token }}
           path: .cache/ci-test-history
@@ -447,23 +351,17 @@ 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
 
   sqlite-runtime:
-    # Admit expensive host/provider work after fast static validation
-    # (typecheck, lint, format). Deep static does not gate these lanes.
-    # Portable tests still provide early feedback.
+    # Preserve all selected coverage, but admit expensive host/provider work
+    # only after static validation. Portable tests still provide early feedback.
     needs: [changes, static, build]
     if: needs.changes.outputs.sqlite == 'true'
     uses: ./.github/workflows/sqlite-runtime.yml
@@ -558,22 +456,11 @@ jobs:
           include-hidden-files: true
           if-no-files-found: error
           retention-days: 30
-      # Default-branch runs only. Pull-request artifacts share this name and
-      # the lookup reads one page, so publishing them would hide main.
       - name: Publish successful timing history
-        if: >-
-          success() &&
-          needs.changes.outputs.code == 'true' &&
-          needs.test-shard.result == 'success' &&
-          (
-            needs.changes.outputs.tier == 'full' ||
-            (needs.changes.outputs.tier == 'fast' && needs.test-source.result == 'success')
-          ) &&
-          github.ref == format('refs/heads/{0}', github.event.repository.default_branch) &&
-          (github.event_name == 'push' || github.event_name == 'schedule' || github.event_name == 'workflow_dispatch')
+        if: needs.changes.outputs.code == 'true' && needs.changes.outputs.tier == 'full' && success() && needs.test-shard.result == 'success'
         uses: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02 # v4.6.2
         with:
-          name: test-timings-${{ needs.changes.outputs.tier }}
+          name: test-timings
           path: .cache/ci-test-history/test-results.json
           include-hidden-files: true
           if-no-files-found: error
@@ -677,9 +564,6 @@ jobs:
       - name: Cache npm package downloads
         id: npm-cache
         uses: ./.github/actions/npm-cache
-        with:
-          # ubuntu-latest is the Linux x64 writer above. Other hosts save their own key.
-          save: ${{ matrix.os != 'ubuntu-latest' }}
       - name: Verify native runtime identity
         env:
           EXPECTED_CI_PLATFORM: ${{ matrix.platform }}
@@ -758,7 +642,6 @@ 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
@@ -816,24 +699,17 @@ jobs:
       - name: Cache npm package downloads
         id: npm-cache
         uses: ./.github/actions/npm-cache
-        with:
-          save: "true"
       - run: npm ci
-      - name: Typecheck with the official Windows compiler
-        env:
-          GOMAXPROCS: "2"
-          GOMEMLIMIT: "3GiB"
-        run: npm run typecheck -- --checkers 2
       - 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
@@ -854,26 +730,17 @@ jobs:
           npx vitest run --coverage.enabled=false
           src/process/capture/FilesystemSnapshot.test.ts
           tests/process-global/filesystemSnapshotFallbackCancellation.test.ts
-          tests/boundary/filesystem/typescriptCompiler.test.ts
           tests/boundary/filesystem/binaryTarget.test.ts
-          src/contracts/sessionPathInputs.test.ts
-          tests/boundary/filesystem/directAnalysisSnapshotReplay.test.ts
-          tests/boundary/mcp/rawBinaryMcp.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
@@ -896,8 +763,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:
@@ -972,107 +837,67 @@ jobs:
             skills/reverse-engineer-anything
           if-no-files-found: error
 
-  # Provider lanes wait for fast static and the portable build, not deep static.
   browser:
     needs: [changes, static, build]
     if: needs.changes.outputs.browser == 'true'
-    secrets:
-      TURBO_TOKEN: ${{ secrets.TURBO_TOKEN }}
     uses: ./.github/workflows/real-browser.yml
     with:
       build_cache_artifact: rea-build-cache
-      remote_cache_write: ${{ inputs.remote_cache_write == true || (github.ref == format('refs/heads/{0}', github.event.repository.default_branch) && (github.event_name == 'push' || github.event_name == 'schedule' || github.event_name == 'workflow_dispatch')) }}
 
   binary_layout:
     needs: [changes, static, build]
     if: needs.changes.outputs.binary_layout == 'true'
-    secrets:
-      TURBO_TOKEN: ${{ secrets.TURBO_TOKEN }}
     uses: ./.github/workflows/real-binary-layout.yml
     with:
       build_cache_artifact: rea-build-cache
-      remote_cache_write: ${{ inputs.remote_cache_write == true || (github.ref == format('refs/heads/{0}', github.event.repository.default_branch) && (github.event_name == 'push' || github.event_name == 'schedule' || github.event_name == 'workflow_dispatch')) }}
 
   evm:
     needs: [changes, static, build]
     if: needs.changes.outputs.evm == 'true'
-    secrets:
-      TURBO_TOKEN: ${{ secrets.TURBO_TOKEN }}
     uses: ./.github/workflows/real-evm-interface.yml
     with:
       build_cache_artifact: rea-build-cache
-      remote_cache_write: ${{ inputs.remote_cache_write == true || (github.ref == format('refs/heads/{0}', github.event.repository.default_branch) && (github.event_name == 'push' || github.event_name == 'schedule' || github.event_name == 'workflow_dispatch')) }}
 
   javascript_recovery:
     needs: [changes, static, build]
     if: needs.changes.outputs.javascript_recovery == 'true'
-    secrets:
-      TURBO_TOKEN: ${{ secrets.TURBO_TOKEN }}
     uses: ./.github/workflows/real-javascript-recovery.yml
     with:
       build_cache_artifact: rea-build-cache
-      remote_cache_write: ${{ inputs.remote_cache_write == true || (github.ref == format('refs/heads/{0}', github.event.repository.default_branch) && (github.event_name == 'push' || github.event_name == 'schedule' || github.event_name == 'workflow_dispatch')) }}
 
   recorded_crash:
     needs: [changes, static, build]
     if: needs.changes.outputs.recorded_crash == 'true'
-    secrets:
-      TURBO_TOKEN: ${{ secrets.TURBO_TOKEN }}
     uses: ./.github/workflows/real-recorded-crash.yml
     with:
       build_cache_artifact: rea-build-cache
-      remote_cache_write: ${{ inputs.remote_cache_write == true || (github.ref == format('refs/heads/{0}', github.event.repository.default_branch) && (github.event_name == 'push' || github.event_name == 'schedule' || github.event_name == 'workflow_dispatch')) }}
 
   web_network:
     needs: [changes, static, build]
     if: needs.changes.outputs.web_network == 'true'
-    secrets:
-      TURBO_TOKEN: ${{ secrets.TURBO_TOKEN }}
     uses: ./.github/workflows/real-web-network-captures.yml
     with:
       build_cache_artifact: rea-build-cache
-      remote_cache_write: ${{ inputs.remote_cache_write == true || (github.ref == format('refs/heads/{0}', github.event.repository.default_branch) && (github.event_name == 'push' || github.event_name == 'schedule' || github.event_name == 'workflow_dispatch')) }}
 
   web_runtime:
     needs: [changes, static, build]
     if: needs.changes.outputs.web_runtime == 'true'
-    secrets:
-      TURBO_TOKEN: ${{ secrets.TURBO_TOKEN }}
     uses: ./.github/workflows/real-web-runtime.yml
     with:
       build_cache_artifact: rea-build-cache
-      remote_cache_write: ${{ inputs.remote_cache_write == true || (github.ref == format('refs/heads/{0}', github.event.repository.default_branch) && (github.event_name == 'push' || github.event_name == 'schedule' || github.event_name == 'workflow_dispatch')) }}
 
   web_source_map:
     needs: [changes, static, build]
     if: needs.changes.outputs.web_source_map == 'true'
-    secrets:
-      TURBO_TOKEN: ${{ secrets.TURBO_TOKEN }}
     uses: ./.github/workflows/real-web-source-map.yml
     with:
       build_cache_artifact: rea-build-cache
-      remote_cache_write: ${{ inputs.remote_cache_write == true || (github.ref == format('refs/heads/{0}', github.event.repository.default_branch) && (github.event_name == 'push' || github.event_name == 'schedule' || github.event_name == 'workflow_dispatch')) }}
-
-  agentenv:
-    needs: [changes, static, build]
-    if: needs.changes.outputs.agentenv == 'true'
-    secrets:
-      TURBO_TOKEN: ${{ secrets.TURBO_TOKEN }}
-    uses: ./.github/workflows/real-agentenv.yml
-    with:
-      build_cache_artifact: rea-build-cache
-      remote_cache_write: ${{ inputs.remote_cache_write == true || (github.ref == format('refs/heads/{0}', github.event.repository.default_branch) && (github.event_name == 'push' || github.event_name == 'schedule' || github.event_name == 'workflow_dispatch')) }}
 
   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'
@@ -1086,7 +911,6 @@ jobs:
       [
         changes,
         static,
-        static-deep,
         build,
         reverse-tools-quality,
         test-shard,
@@ -1108,9 +932,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

@@ -14,11 +14,6 @@ concurrency:
 
 env:
   HUSKY: "0"
-  # Writes only on the default branch for push, schedule, manual dispatch,
-  # and workflow_call. Pull requests get an empty token and remote read-only mode.
-  TURBO_TOKEN: "${{ (github.ref == format('refs/heads/{0}', github.event.repository.default_branch) && (github.event_name == 'push' || github.event_name == 'schedule' || github.event_name == 'workflow_dispatch' || github.event_name == 'workflow_call')) && secrets.TURBO_TOKEN || '' }}"
-  TURBO_TEAM: ${{ vars.TURBO_TEAM }}
-  TURBO_CACHE: "${{ (github.ref == format('refs/heads/{0}', github.event.repository.default_branch) && (github.event_name == 'push' || github.event_name == 'schedule' || github.event_name == 'workflow_dispatch' || github.event_name == 'workflow_call')) && 'local:rw,remote:rw' || 'local:rw,remote:r' }}"
 
 jobs:
   mutation:

.github/workflows/real-agentenv.yml

@@ -1,98 +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: ""
-      remote_cache_write:
-        description: Trusted release qualification may publish the remote cache.
-        required: false
-        type: boolean
-        default: false
-    secrets:
-      TURBO_TOKEN:
-        description: Remote cache token. Only trusted callers pass it.
-        required: false
-
-permissions:
-  contents: read
-
-env:
-  HUSKY: "0"
-  # A called workflow sees the caller event, so workflow_call is not an event
-  # name here. Writes when remote_cache_write is set, or on the default branch
-  # for push, schedule, and manual dispatch. Open pull requests stay empty-token
-  # and use the local cache only.
-  TURBO_TOKEN: "${{ (inputs.remote_cache_write == true || (github.ref == format('refs/heads/{0}', github.event.repository.default_branch) && (github.event_name == 'push' || github.event_name == 'schedule' || github.event_name == 'workflow_dispatch'))) && secrets.TURBO_TOKEN || '' }}"
-  TURBO_TEAM: ${{ vars.TURBO_TEAM }}
-  TURBO_CACHE: "${{ (inputs.remote_cache_write == true || (github.ref == format('refs/heads/{0}', github.event.repository.default_branch) && (github.event_name == 'push' || github.event_name == 'schedule' || github.event_name == 'workflow_dispatch'))) && 'local:rw,remote:rw' || 'local:rw' }}"
-  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

@@ -14,15 +14,6 @@ on:
         required: false
         type: string
         default: ""
-      remote_cache_write:
-        description: Trusted release qualification may publish the remote cache.
-        required: false
-        type: boolean
-        default: false
-    secrets:
-      TURBO_TOKEN:
-        description: Remote cache token. Only trusted callers pass it.
-        required: false
 
 permissions:
   contents: read
@@ -30,13 +21,6 @@ permissions:
 env:
   NODE_OPTIONS: --max-old-space-size=768
   HUSKY: "0"
-  # A called workflow sees the caller event, so workflow_call is not an event
-  # name here. Writes when remote_cache_write is set, or on the default branch
-  # for push, schedule, and manual dispatch. Open pull requests stay empty-token
-  # and use the local cache only.
-  TURBO_TOKEN: "${{ (inputs.remote_cache_write == true || (github.ref == format('refs/heads/{0}', github.event.repository.default_branch) && (github.event_name == 'push' || github.event_name == 'schedule' || github.event_name == 'workflow_dispatch'))) && secrets.TURBO_TOKEN || '' }}"
-  TURBO_TEAM: ${{ vars.TURBO_TEAM }}
-  TURBO_CACHE: "${{ (inputs.remote_cache_write == true || (github.ref == format('refs/heads/{0}', github.event.repository.default_branch) && (github.event_name == 'push' || github.event_name == 'schedule' || github.event_name == 'workflow_dispatch'))) && 'local:rw,remote:rw' || 'local:rw' }}"
   REA_VERIFY_LARGE_ELF_MCP: ${{ inputs.large_mcp && '1' || '0' }}
 
 jobs:

.github/workflows/real-browser.yml

@@ -8,26 +8,10 @@ on:
         required: false
         type: string
         default: ""
-      remote_cache_write:
-        description: Trusted release qualification may publish the remote cache.
-        required: false
-        type: boolean
-        default: false
-    secrets:
-      TURBO_TOKEN:
-        description: Remote cache token. Only trusted callers pass it.
-        required: false
   workflow_dispatch:
 
 env:
   HUSKY: "0"
-  # A called workflow sees the caller event, so workflow_call is not an event
-  # name here. Writes when remote_cache_write is set, or on the default branch
-  # for push, schedule, and manual dispatch. Open pull requests stay empty-token
-  # and use the local cache only.
-  TURBO_TOKEN: "${{ (inputs.remote_cache_write == true || (github.ref == format('refs/heads/{0}', github.event.repository.default_branch) && (github.event_name == 'push' || github.event_name == 'schedule' || github.event_name == 'workflow_dispatch'))) && secrets.TURBO_TOKEN || '' }}"
-  TURBO_TEAM: ${{ vars.TURBO_TEAM }}
-  TURBO_CACHE: "${{ (inputs.remote_cache_write == true || (github.ref == format('refs/heads/{0}', github.event.repository.default_branch) && (github.event_name == 'push' || github.event_name == 'schedule' || github.event_name == 'workflow_dispatch'))) && 'local:rw,remote:rw' || 'local:rw' }}"
 
 permissions:
   contents: read

.github/workflows/real-cutter.yml

@@ -8,14 +8,6 @@ on:
 permissions:
   contents: read
 
-env:
-  HUSKY: "0"
-  # Writes only on the default branch for push, schedule, manual dispatch,
-  # and workflow_call. Pull requests get an empty token and remote read-only mode.
-  TURBO_TOKEN: "${{ (github.ref == format('refs/heads/{0}', github.event.repository.default_branch) && (github.event_name == 'push' || github.event_name == 'schedule' || github.event_name == 'workflow_dispatch' || github.event_name == 'workflow_call')) && secrets.TURBO_TOKEN || '' }}"
-  TURBO_TEAM: ${{ vars.TURBO_TEAM }}
-  TURBO_CACHE: "${{ (github.ref == format('refs/heads/{0}', github.event.repository.default_branch) && (github.event_name == 'push' || github.event_name == 'schedule' || github.event_name == 'workflow_dispatch' || github.event_name == 'workflow_call')) && 'local:rw,remote:rw' || 'local:rw,remote:r' }}"
-
 jobs:
   windows-native-artifact:
     name: Build Windows bridge security boundary
@@ -30,7 +22,7 @@ jobs:
           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
+      - uses: actions/upload-artifact@v4
         with:
           name: cutter-windows-native
           path: native/windows/build/
@@ -61,7 +53,7 @@ jobs:
         uses: ./.github/actions/npm-cache
       - run: npm ci
       - if: matrix.platform == 'Windows'
-        uses: actions/download-artifact@d3f86a106a0bac45b974a628896c90dbdf5c8093 # v4.3.0
+        uses: actions/download-artifact@v4
         with:
           name: cutter-windows-native
           path: native/windows/build/
@@ -75,7 +67,7 @@ jobs:
         env:
           EXPECTED_PLATFORM: ${{ matrix.platform }}
         run: npm run verify:cutter
-      - uses: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02 # v4.6.2
+      - uses: actions/upload-artifact@v4
         if: always()
         with:
           name: cutter-upstream-${{ matrix.platform }}

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

@@ -9,15 +9,6 @@ on:
         required: false
         type: string
         default: ""
-      remote_cache_write:
-        description: Trusted release qualification may publish the remote cache.
-        required: false
-        type: boolean
-        default: false
-    secrets:
-      TURBO_TOKEN:
-        description: Remote cache token. Only trusted callers pass it.
-        required: false
 
 permissions:
   contents: read
@@ -25,13 +16,6 @@ permissions:
 env:
   NODE_OPTIONS: --max-old-space-size=768
   HUSKY: "0"
-  # A called workflow sees the caller event, so workflow_call is not an event
-  # name here. Writes when remote_cache_write is set, or on the default branch
-  # for push, schedule, and manual dispatch. Open pull requests stay empty-token
-  # and use the local cache only.
-  TURBO_TOKEN: "${{ (inputs.remote_cache_write == true || (github.ref == format('refs/heads/{0}', github.event.repository.default_branch) && (github.event_name == 'push' || github.event_name == 'schedule' || github.event_name == 'workflow_dispatch'))) && secrets.TURBO_TOKEN || '' }}"
-  TURBO_TEAM: ${{ vars.TURBO_TEAM }}
-  TURBO_CACHE: "${{ (inputs.remote_cache_write == true || (github.ref == format('refs/heads/{0}', github.event.repository.default_branch) && (github.event_name == 'push' || github.event_name == 'schedule' || github.event_name == 'workflow_dispatch'))) && 'local:rw,remote:rw' || 'local:rw' }}"
 
 jobs:
   real-evm-interface:

.github/workflows/real-ghidra-windows.yml

@@ -6,11 +6,6 @@ on:
 
 env:
   HUSKY: "0"
-  # Writes only on the default branch for push, schedule, manual dispatch,
-  # and workflow_call. Pull requests get an empty token and remote read-only mode.
-  TURBO_TOKEN: "${{ (github.ref == format('refs/heads/{0}', github.event.repository.default_branch) && (github.event_name == 'push' || github.event_name == 'schedule' || github.event_name == 'workflow_dispatch' || github.event_name == 'workflow_call')) && secrets.TURBO_TOKEN || '' }}"
-  TURBO_TEAM: ${{ vars.TURBO_TEAM }}
-  TURBO_CACHE: "${{ (github.ref == format('refs/heads/{0}', github.event.repository.default_branch) && (github.event_name == 'push' || github.event_name == 'schedule' || github.event_name == 'workflow_dispatch' || github.event_name == 'workflow_call')) && 'local:rw,remote:rw' || 'local:rw,remote:r' }}"
 
 permissions:
   contents: read

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

@@ -13,8 +13,20 @@ on:
       - "src/composition/go.ts"
       - "src/cli/goCommands.ts"
       - "src/server/registerGoTools.ts"
+      - "src/server/createServer.ts"
+      - "src/cli.ts"
+      - "src/cliCommandNames.ts"
+      - "src/contracts/toolContracts.ts"
+      - "src/contracts/toolEffects.ts"
+      - "src/artifacts/readStableArtifact*.ts"
+      - "src/artifacts/ArtifactReader.ts"
+      - "src/process/PrivateRuntimeRoot.ts"
       - "scripts/verify-go-binary.mjs"
       - "scripts/lib/mcp-verifier-results.mjs"
+      - "scripts/rea.mjs"
+      - "package.json"
+      - "package-lock.json"
+      - ".nvmrc"
 
 permissions:
   contents: read
@@ -26,11 +38,6 @@ concurrency:
 env:
   NODE_OPTIONS: --max-old-space-size=768
   HUSKY: "0"
-  # Writes only on the default branch for push, schedule, manual dispatch,
-  # and workflow_call. Pull requests get an empty token and remote read-only mode.
-  TURBO_TOKEN: "${{ (github.ref == format('refs/heads/{0}', github.event.repository.default_branch) && (github.event_name == 'push' || github.event_name == 'schedule' || github.event_name == 'workflow_dispatch' || github.event_name == 'workflow_call')) && secrets.TURBO_TOKEN || '' }}"
-  TURBO_TEAM: ${{ vars.TURBO_TEAM }}
-  TURBO_CACHE: "${{ (github.ref == format('refs/heads/{0}', github.event.repository.default_branch) && (github.event_name == 'push' || github.event_name == 'schedule' || github.event_name == 'workflow_dispatch' || github.event_name == 'workflow_call')) && 'local:rw,remote:rw' || 'local:rw,remote:r' }}"
 
 jobs:
   real-go-binary:

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

@@ -5,11 +5,6 @@ on:
 
 env:
   HUSKY: "0"
-  # Writes only on the default branch for push, schedule, manual dispatch,
-  # and workflow_call. Pull requests get an empty token and remote read-only mode.
-  TURBO_TOKEN: "${{ (github.ref == format('refs/heads/{0}', github.event.repository.default_branch) && (github.event_name == 'push' || github.event_name == 'schedule' || github.event_name == 'workflow_dispatch' || github.event_name == 'workflow_call')) && secrets.TURBO_TOKEN || '' }}"
-  TURBO_TEAM: ${{ vars.TURBO_TEAM }}
-  TURBO_CACHE: "${{ (github.ref == format('refs/heads/{0}', github.event.repository.default_branch) && (github.event_name == 'push' || github.event_name == 'schedule' || github.event_name == 'workflow_dispatch' || github.event_name == 'workflow_call')) && 'local:rw,remote:rw' || 'local:rw,remote:r' }}"
 
 permissions:
   contents: read

.github/workflows/real-hopper.yml

@@ -5,11 +5,6 @@ on:
 
 env:
   HUSKY: "0"
-  # Writes only on the default branch for push, schedule, manual dispatch,
-  # and workflow_call. Pull requests get an empty token and remote read-only mode.
-  TURBO_TOKEN: "${{ (github.ref == format('refs/heads/{0}', github.event.repository.default_branch) && (github.event_name == 'push' || github.event_name == 'schedule' || github.event_name == 'workflow_dispatch' || github.event_name == 'workflow_call')) && secrets.TURBO_TOKEN || '' }}"
-  TURBO_TEAM: ${{ vars.TURBO_TEAM }}
-  TURBO_CACHE: "${{ (github.ref == format('refs/heads/{0}', github.event.repository.default_branch) && (github.event_name == 'push' || github.event_name == 'schedule' || github.event_name == 'workflow_dispatch' || github.event_name == 'workflow_call')) && 'local:rw,remote:rw' || 'local:rw,remote:r' }}"
 
 permissions:
   contents: read

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

@@ -8,15 +8,6 @@ on:
         required: false
         type: string
         default: ""
-      remote_cache_write:
-        description: Trusted release qualification may publish the remote cache.
-        required: false
-        type: boolean
-        default: false
-    secrets:
-      TURBO_TOKEN:
-        description: Remote cache token. Only trusted callers pass it.
-        required: false
   workflow_dispatch:
 
 permissions:
@@ -24,13 +15,6 @@ permissions:
 
 env:
   HUSKY: "0"
-  # A called workflow sees the caller event, so workflow_call is not an event
-  # name here. Writes when remote_cache_write is set, or on the default branch
-  # for push, schedule, and manual dispatch. Open pull requests stay empty-token
-  # and use the local cache only.
-  TURBO_TOKEN: "${{ (inputs.remote_cache_write == true || (github.ref == format('refs/heads/{0}', github.event.repository.default_branch) && (github.event_name == 'push' || github.event_name == 'schedule' || github.event_name == 'workflow_dispatch'))) && secrets.TURBO_TOKEN || '' }}"
-  TURBO_TEAM: ${{ vars.TURBO_TEAM }}
-  TURBO_CACHE: "${{ (inputs.remote_cache_write == true || (github.ref == format('refs/heads/{0}', github.event.repository.default_branch) && (github.event_name == 'push' || github.event_name == 'schedule' || github.event_name == 'workflow_dispatch'))) && 'local:rw,remote:rw' || 'local:rw' }}"
   NODE_OPTIONS: "--max-old-space-size=768"
   RAYON_NUM_THREADS: "1"
 

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

@@ -20,17 +20,21 @@ on:
       - "src/composition/captures.ts"
       - "src/cli/captureCommands.ts"
       - "src/server/registerCaptureTools.ts"
+      - "src/server/createServer.ts"
+      - "src/server/sessionAvailabilityPolicy.ts"
+      - "src/application/CapabilityInventory.ts"
+      - "src/contracts/toolContracts.ts"
+      - "src/contracts/toolEffects.ts"
+      - "src/cli.ts"
+      - "src/cliCommandNames.ts"
+      - "src/process/**"
+      - "src/artifacts/readStableArtifact.ts"
       - "scripts/verify-packet-capture.mjs"
       - ".github/workflows/real-packet-capture.yml"
+      - "package*.json"
+      - ".nvmrc"
 permissions:
   contents: read
-env:
-  HUSKY: "0"
-  # Writes only on the default branch for push, schedule, manual dispatch,
-  # and workflow_call. Pull requests get an empty token and remote read-only mode.
-  TURBO_TOKEN: "${{ (github.ref == format('refs/heads/{0}', github.event.repository.default_branch) && (github.event_name == 'push' || github.event_name == 'schedule' || github.event_name == 'workflow_dispatch' || github.event_name == 'workflow_call')) && secrets.TURBO_TOKEN || '' }}"
-  TURBO_TEAM: ${{ vars.TURBO_TEAM }}
-  TURBO_CACHE: "${{ (github.ref == format('refs/heads/{0}', github.event.repository.default_branch) && (github.event_name == 'push' || github.event_name == 'schedule' || github.event_name == 'workflow_dispatch' || github.event_name == 'workflow_call')) && 'local:rw,remote:rw' || 'local:rw,remote:r' }}"
 concurrency:
   group: real-packet-capture-${{ github.event.pull_request.number || github.ref }}
   cancel-in-progress: true
@@ -49,7 +53,7 @@ jobs:
       - 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

@@ -9,15 +9,6 @@ on:
         required: false
         type: string
         default: ""
-      remote_cache_write:
-        description: Trusted release qualification may publish the remote cache.
-        required: false
-        type: boolean
-        default: false
-    secrets:
-      TURBO_TOKEN:
-        description: Remote cache token. Only trusted callers pass it.
-        required: false
 
 permissions:
   contents: read
@@ -25,13 +16,6 @@ permissions:
 env:
   NODE_OPTIONS: --max-old-space-size=768
   HUSKY: "0"
-  # A called workflow sees the caller event, so workflow_call is not an event
-  # name here. Writes when remote_cache_write is set, or on the default branch
-  # for push, schedule, and manual dispatch. Open pull requests stay empty-token
-  # and use the local cache only.
-  TURBO_TOKEN: "${{ (inputs.remote_cache_write == true || (github.ref == format('refs/heads/{0}', github.event.repository.default_branch) && (github.event_name == 'push' || github.event_name == 'schedule' || github.event_name == 'workflow_dispatch'))) && secrets.TURBO_TOKEN || '' }}"
-  TURBO_TEAM: ${{ vars.TURBO_TEAM }}
-  TURBO_CACHE: "${{ (inputs.remote_cache_write == true || (github.ref == format('refs/heads/{0}', github.event.repository.default_branch) && (github.event_name == 'push' || github.event_name == 'schedule' || github.event_name == 'workflow_dispatch'))) && 'local:rw,remote:rw' || 'local:rw' }}"
   UV_CONCURRENT_BUILDS: "1"
   UV_CONCURRENT_INSTALLS: "1"
   UV_PYTHON_DOWNLOADS: never
@@ -40,19 +24,7 @@ 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:
@@ -64,6 +36,11 @@ jobs:
       - 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

@@ -13,17 +13,21 @@ on:
       - "src/composition/signals.ts"
       - "src/cli/signalCommands.ts"
       - "src/server/registerSignalTools.ts"
+      - "src/server/createServer.ts"
+      - "src/server/sessionAvailabilityPolicy.ts"
+      - "src/application/CapabilityInventory.ts"
+      - "src/contracts/toolContracts.ts"
+      - "src/contracts/toolEffects.ts"
+      - "src/cli.ts"
+      - "src/cliCommandNames.ts"
+      - "src/process/**"
+      - "src/artifacts/readStableArtifact.ts"
       - "scripts/verify-signal-recording.mjs"
       - ".github/workflows/real-signal-recording.yml"
+      - "package*.json"
+      - ".nvmrc"
 permissions:
   contents: read
-env:
-  HUSKY: "0"
-  # Writes only on the default branch for push, schedule, manual dispatch,
-  # and workflow_call. Pull requests get an empty token and remote read-only mode.
-  TURBO_TOKEN: "${{ (github.ref == format('refs/heads/{0}', github.event.repository.default_branch) && (github.event_name == 'push' || github.event_name == 'schedule' || github.event_name == 'workflow_dispatch' || github.event_name == 'workflow_call')) && secrets.TURBO_TOKEN || '' }}"
-  TURBO_TEAM: ${{ vars.TURBO_TEAM }}
-  TURBO_CACHE: "${{ (github.ref == format('refs/heads/{0}', github.event.repository.default_branch) && (github.event_name == 'push' || github.event_name == 'schedule' || github.event_name == 'workflow_dispatch' || github.event_name == 'workflow_call')) && 'local:rw,remote:rw' || 'local:rw,remote:r' }}"
 concurrency:
   group: real-signal-recording-${{ github.event.pull_request.number || github.ref }}
   cancel-in-progress: true

.github/workflows/real-termux.yml

@@ -12,11 +12,6 @@ permissions:
 
 env:
   HUSKY: "0"
-  # Writes only on the default branch for push, schedule, manual dispatch,
-  # and workflow_call. Pull requests get an empty token and remote read-only mode.
-  TURBO_TOKEN: "${{ (github.ref == format('refs/heads/{0}', github.event.repository.default_branch) && (github.event_name == 'push' || github.event_name == 'schedule' || github.event_name == 'workflow_dispatch' || github.event_name == 'workflow_call')) && secrets.TURBO_TOKEN || '' }}"
-  TURBO_TEAM: ${{ vars.TURBO_TEAM }}
-  TURBO_CACHE: "${{ (github.ref == format('refs/heads/{0}', github.event.repository.default_branch) && (github.event_name == 'push' || github.event_name == 'schedule' || github.event_name == 'workflow_dispatch' || github.event_name == 'workflow_call')) && 'local:rw,remote:rw' || 'local:rw,remote:r' }}"
 
 jobs:
   real-termux:

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

@@ -9,28 +9,12 @@ on:
         required: false
         type: string
         default: ""
-      remote_cache_write:
-        description: Trusted release qualification may publish the remote cache.
-        required: false
-        type: boolean
-        default: false
-    secrets:
-      TURBO_TOKEN:
-        description: Remote cache token. Only trusted callers pass it.
-        required: false
 
 permissions:
   contents: read
 
 env:
   HUSKY: "0"
-  # A called workflow sees the caller event, so workflow_call is not an event
-  # name here. Writes when remote_cache_write is set, or on the default branch
-  # for push, schedule, and manual dispatch. Open pull requests stay empty-token
-  # and use the local cache only.
-  TURBO_TOKEN: "${{ (inputs.remote_cache_write == true || (github.ref == format('refs/heads/{0}', github.event.repository.default_branch) && (github.event_name == 'push' || github.event_name == 'schedule' || github.event_name == 'workflow_dispatch'))) && secrets.TURBO_TOKEN || '' }}"
-  TURBO_TEAM: ${{ vars.TURBO_TEAM }}
-  TURBO_CACHE: "${{ (inputs.remote_cache_write == true || (github.ref == format('refs/heads/{0}', github.event.repository.default_branch) && (github.event_name == 'push' || github.event_name == 'schedule' || github.event_name == 'workflow_dispatch'))) && 'local:rw,remote:rw' || 'local:rw' }}"
   NODE_OPTIONS: --max-old-space-size=768
 
 jobs:

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

@@ -7,27 +7,11 @@ on:
         required: false
         type: string
         default: ""
-      remote_cache_write:
-        description: Trusted release qualification may publish the remote cache.
-        required: false
-        type: boolean
-        default: false
-    secrets:
-      TURBO_TOKEN:
-        description: Remote cache token. Only trusted callers pass it.
-        required: false
   workflow_dispatch:
 permissions:
   contents: read
 env:
   HUSKY: "0"
-  # A called workflow sees the caller event, so workflow_call is not an event
-  # name here. Writes when remote_cache_write is set, or on the default branch
-  # for push, schedule, and manual dispatch. Open pull requests stay empty-token
-  # and use the local cache only.
-  TURBO_TOKEN: "${{ (inputs.remote_cache_write == true || (github.ref == format('refs/heads/{0}', github.event.repository.default_branch) && (github.event_name == 'push' || github.event_name == 'schedule' || github.event_name == 'workflow_dispatch'))) && secrets.TURBO_TOKEN || '' }}"
-  TURBO_TEAM: ${{ vars.TURBO_TEAM }}
-  TURBO_CACHE: "${{ (inputs.remote_cache_write == true || (github.ref == format('refs/heads/{0}', github.event.repository.default_branch) && (github.event_name == 'push' || github.event_name == 'schedule' || github.event_name == 'workflow_dispatch'))) && 'local:rw,remote:rw' || 'local:rw' }}"
 jobs:
   real-web-runtime:
     runs-on: ubuntu-latest

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

@@ -7,27 +7,11 @@ on:
         required: false
         type: string
         default: ""
-      remote_cache_write:
-        description: Trusted release qualification may publish the remote cache.
-        required: false
-        type: boolean
-        default: false
-    secrets:
-      TURBO_TOKEN:
-        description: Remote cache token. Only trusted callers pass it.
-        required: false
   workflow_dispatch:
 permissions:
   contents: read
 env:
   HUSKY: "0"
-  # A called workflow sees the caller event, so workflow_call is not an event
-  # name here. Writes when remote_cache_write is set, or on the default branch
-  # for push, schedule, and manual dispatch. Open pull requests stay empty-token
-  # and use the local cache only.
-  TURBO_TOKEN: "${{ (inputs.remote_cache_write == true || (github.ref == format('refs/heads/{0}', github.event.repository.default_branch) && (github.event_name == 'push' || github.event_name == 'schedule' || github.event_name == 'workflow_dispatch'))) && secrets.TURBO_TOKEN || '' }}"
-  TURBO_TEAM: ${{ vars.TURBO_TEAM }}
-  TURBO_CACHE: "${{ (inputs.remote_cache_write == true || (github.ref == format('refs/heads/{0}', github.event.repository.default_branch) && (github.event_name == 'push' || github.event_name == 'schedule' || github.event_name == 'workflow_dispatch'))) && 'local:rw,remote:rw' || 'local:rw' }}"
 jobs:
   real-web-source-map:
     runs-on: ubuntu-latest

.github/workflows/release.yml

@@ -21,12 +21,6 @@ on:
 
 env:
   HUSKY: "0"
-  # Remote cache stays local when either value is empty.
-  # Writes only on the default branch for push, schedule, manual dispatch,
-  # and workflow_call. Pull requests get an empty token and remote read-only mode.
-  TURBO_TOKEN: "${{ (github.ref == format('refs/heads/{0}', github.event.repository.default_branch) && (github.event_name == 'push' || github.event_name == 'schedule' || github.event_name == 'workflow_dispatch' || github.event_name == 'workflow_call')) && secrets.TURBO_TOKEN || '' }}"
-  TURBO_TEAM: ${{ vars.TURBO_TEAM }}
-  TURBO_CACHE: "${{ (github.ref == format('refs/heads/{0}', github.event.repository.default_branch) && (github.event_name == 'push' || github.event_name == 'schedule' || github.event_name == 'workflow_dispatch' || github.event_name == 'workflow_call')) && 'local:rw,remote:rw' || 'local:rw,remote:r' }}"
 
 concurrency:
   group: release-${{ inputs.release_branch || github.event.pull_request.merge_commit_sha || github.ref_name }}
@@ -307,11 +301,8 @@ jobs:
       contents: read
       actions: read
     uses: ./.github/workflows/ci.yml
-    secrets:
-      TURBO_TOKEN: ${{ secrets.TURBO_TOKEN }}
     with:
       source_sha: ${{ needs.merged-release.outputs.sha || needs.release-please.outputs.sha }}
-      remote_cache_write: true
 
   rehearsal:
     name: Rehearse qualified release on a clean runner

.release-please-manifest.json

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

AGENTS.md

@@ -20,8 +20,6 @@ Give each interpretation and resource a clear owner. Consumers must use that own
 
 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.

CHANGELOG.md

@@ -1,93 +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).

CONTRIBUTING.md

@@ -21,9 +21,6 @@ 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.
 
@@ -228,10 +225,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,
@@ -261,23 +255,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

README.md

@@ -1,7 +1,7 @@
 <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)
+· [Ελληνικά](docs/readme/README_el.md)
 
 # REA: Reverse Engineer Anything
 
@@ -90,12 +90,6 @@ Setup supports Claude Code, Codex, Cursor, Gemini CLI, Grok Build and
 [installation and setup](docs/installation.md) for provider configuration and
 manual MCP registration.
 
-MCP uses compact input schemas by default to reduce context overhead. Set
-`REA_MCP_INPUT_SCHEMA_PROFILE=full` in your MCP registration when you need the
-complete advertised field guidance and nested validation details. Both profiles
-keep the full tool set and canonical server validation. See
-"Compact input schema profile" in the MCP contracts guide.
-
 ### Ask your agent
 
 ```text
@@ -138,14 +132,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`.
 
@@ -180,37 +166,31 @@ 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                                                            |
-| GPU code objects        | CUDA/HIP targets, selected kernel parameters and resources, retained PTX text                     | Built-in static ELF/PE/fatbin/CUBIN/PTX inspection; [GPU code objects](docs/gpu-code-objects.md)                                      |
-| Model artifacts         | GGUF / safetensors metadata, tensor declarations and derived totals                               | Built-in header inspection; optional full-file hash; [model files](docs/model-artifacts.md)                                           |
-| 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)                                                             |
-| PyInstaller executables | CArchive members, Python version, entry scripts and extracted bytecode                            | None (static only); [Python packaged applications](docs/python-packaged-applications.md)                                              |
+| Target                 | What REA returns                                                                     | Requirements and guide                                                                                                                |
+| ---------------------- | ------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------- |
+| 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                                                            |
+| 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)                                                             |
 
 Static JavaScript and .NET inspection read the supplied files without running
 the application. Runtime capture runs or interacts with the selected target
@@ -225,8 +205,7 @@ or update either provider.
 
 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
+[IDA guide](docs/ida-provider.md) (including an optional native MCP bridge), and
 [experimental Windows Ghidra support](docs/windows-ghidra-p0.md).
 Ghidra also supports [16-bit DOS analysis](docs/ghidra-dos.md).
 For large binaries, raise the provider's startup deadline with
@@ -365,7 +344,7 @@ Report vulnerabilities through [SECURITY.md](SECURITY.md).
 
 ## Star history
 
-🎉 **300,000 GitHub stars — thank you!**
+🎉 **200,000 GitHub stars — thank you!**
 
 Thanks to everyone using REA, reporting bugs, requesting features, testing builds, and contributing fixes.
 

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

@@ -28,9 +28,9 @@ if os.name == "nt":
 import cutter
 
 try:
-    from PySide6.QtCore import QCoreApplication, QObject, Signal
+    from PySide6.QtCore import QObject, Signal
 except ImportError:
-    from PySide2.QtCore import QCoreApplication, QObject, Signal
+    from PySide2.QtCore import QObject, Signal
 
 
 MAX_FRAME_BYTES = 16 * 1024 * 1024
@@ -326,16 +326,15 @@ class _RequestDispatcher(QObject):
         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
+            self.cutter_version = str(cutter.core().getVersionInformation())
         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
+            value = cutter.core().currentlyOpenFile()
+            return str(value) if value else None
         except Exception:
             return None
 
@@ -783,22 +782,14 @@ def _within_response_limit(value: Any) -> bool:
         current = pending.pop()
         if isinstance(current, str):
             size += 2
-            if len(current) > MAX_FRAME_BYTES - size:
-                return False
             if current.isascii():
                 size += len(current)
+                size += current.count('"') + current.count("\\")
+                size += sum(5 for character in current if ord(character) < 0x20)
             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)
+                size += 4 * len(current)
+                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:

bridge/ghidra/ReaGhidraBridge.java

@@ -140,7 +140,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",
@@ -428,7 +427,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);
@@ -458,7 +456,6 @@ public final class ReaGhidraBridge extends HeadlessScript {
                 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;
             }
             case "set_address_name", "set_addresses_names" -> {
@@ -1541,23 +1538,12 @@ 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.isExternal() ? "Ghidra does not decompile external functions."
                 : function.getBody().isEmpty() ? "Ghidra has no function body to decompile."
                 : "Ghidra completed decompilation without returning pseudocode."
         ));
@@ -1606,16 +1592,9 @@ public final class ReaGhidraBridge extends HeadlessScript {
         result.add("basic_blocks", blocks);
         result.add(
             "native_api",
-            decompilerFailure == null
-                ? nativeApiBoundary(function, decompilation)
-                : unavailableNativeApiBoundary(decompilerFailure)
-        );
-        result.add(
-            "native_value_flow",
-            decompilerFailure == null
-                ? nativeValueFlow(decompilation)
-                : unavailableNativeValueFlow(decompilerFailure)
+            nativeApiBoundary(function, decompilation)
         );
+        result.add("native_value_flow", nativeValueFlow(decompilation));
         // 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")) {
@@ -1662,12 +1641,6 @@ public final class ReaGhidraBridge extends HeadlessScript {
             !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;
@@ -1676,16 +1649,25 @@ public final class ReaGhidraBridge extends HeadlessScript {
             if (unrepresentedCaller(reference, callerFunctions)) missingCallers++;
         }
         return new FunctionAnalysisObservation(result, calls.limitations(),
-            callRelationshipCoverage(calls, missingCallers), decompilerFailure != null);
+            callRelationshipCoverage(calls, missingCallers));
     }
 
     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 +1974,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 +2000,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 +2339,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);
@@ -4903,7 +4857,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 FunctionAnalysisObservation(JsonObject dossier, List<String> limitations, JsonObject relationshipCoverage) {}
     private record CallBoundaryObservation(List<String> limitations, Integer unrepresentedCalleeCalls, JsonArray unresolvedCalls) {}
     private record SwiftStringLiteralDecode(JsonArray literals, JsonArray omissions) {}
     private record SwiftLiteralLayout(

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):
@@ -1003,46 +1004,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 +1057,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 +1148,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/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)
@@ -662,9 +630,8 @@ 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
-            )
+            stdout.close()
+            stderr.close()
             return {
                 "status": "launch-error",
                 "error": error.GetCString(),
@@ -673,26 +640,15 @@ def trace(debugger, config):
                     if process.IsValid()
                     else {}
                 ),
-                **(
-                    {"target_process_exit_observed": True}
-                    if exit_observed
-                    else {}
-                ),
             }
         launch_failure = _failed_launch_description(process)
         if launch_failure is not None:
-            exit_observed = _retire_failed_launch(
-                process, config, listener, stdout, stderr
-            )
+            stdout.close(expected_exit=True)
+            stderr.close(expected_exit=True)
             return {
                 "status": "launch-error",
                 "error": launch_failure,
                 "target_process_created": True,
-                **(
-                    {"target_process_exit_observed": True}
-                    if exit_observed
-                    else {}
-                ),
             }
         stdout.mark_launched()
         stderr.mark_launched()

bridge/native/test_rea_lldb_tracer.py

@@ -15,8 +15,6 @@ 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,136 +23,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)
 

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

@@ -29,8 +29,6 @@ export default defineConfig({
         items: [
           { text: "Native binaries", link: "/native-investigation" },
           { text: "Go build metadata", link: "/go-binaries" },
-          { text: "IL2CPP metadata", link: "/il2cpp-metadata" },
-          { text: "Model artifacts", link: "/model-artifacts" },
           { text: "Rust dependencies", link: "/rust-binaries" },
           {
             text: "JavaScript and Electron",
@@ -45,18 +43,12 @@ export default defineConfig({
             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: "Python packaged applications",
-            link: "/python-packaged-applications",
-          },
           { 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" },
@@ -68,7 +60,6 @@ export default defineConfig({
         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" },

docs/adb-device-analysis.md

@@ -98,37 +98,16 @@ existing analysis families directly, for example
 | `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                                                                                                                                     |
+| `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                                                                                                                                                                 |
 
-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.
-
 ## Interpret the result
 
 - **Directory names retain whitespace and newlines.** Symlink targets do too,
@@ -162,19 +141,14 @@ and during shutdown.
   APKs keep other names report the `unknown` role rather than guessing.
 - **Partial results keep facts.** Failed individual pulls return successful
   artifacts with `coverage: "partial"` and per-file `failures`. Listings
-  and package searches that contain unrecognized lines report the first ten
-  as `unparsed_lines`, state the exact total in a limitation when more were
-  seen, and mark partial coverage instead of dropping rows.
+  that contain unrecognized lines report them as `unparsed_lines` and mark
+  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. A missing command or output without a
-  recognizable digest reports `device_digest_source: "unavailable"` with an
-  unverified-transfer limitation; installs preserve the
+  unless `overwrite` is set. 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
   device's `Failure [...]` reason verbatim.
 - **Producer identity stays attached.** Every result embeds the producing
   adb client (`binary_path`, `path_source`, `version`, `installed_path`).
@@ -186,21 +160,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`
-  and names the byte allowance. Deadline expiration, including the
-  client-version probe, reports `provider_timeout` and names the effective
-  milliseconds. This release has no runtime override for those deadlines or
-  capture caps. 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

docs/agent-environments.md

@@ -1,700 +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 what one retained web
-network capture observed, plus the environment card the agentenv framework
-reads to discover it. By default the server derives the
-[state the capture observed](#the-state-a-capture-observed) at startup and
-answers read tools from it; `--replay-only` replays the capture's records
-instead. Nothing is fetched from the recorded application; every answer comes
-from 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 from the state it derives from the
-capture; see [Serve from the state](#serve-from-the-state). 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; one that
-selected header values but no response bodies yields a manifest but no state,
-so it is served by replay. 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.
-Served from the state, each description is longer and the card declares the
-data plane, so a catalog replay admits can exceed the reservation; the state
-is then unavailable and the server serves replay instead (see
-[Serve from the state](#serve-from-the-state)).
-
-## What replay means and does not mean
-
-Replay answers every tool with `--replay-only` or when the state is unavailable,
-and, served from the state, each read tool whose view the state does not back.
-Each such 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 answers only from the capture's recordings and the state they observed or a
-caller loaded through `data/add`. 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 reads that are not entities, 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 holds, loads and reports: `environment-serve`
-derives it from the capture at startup; see
-[Serve from the state](#serve-from-the-state). With `--replay-only`, replay is
-unchanged.
-
-## Serve a manifest
-
-```sh
-rea environment-serve manifest.json --evidence capture.json [--replay-only] [--host 127.0.0.1] [--port 0]
-```
-
-The server derives the state from the capture before it binds and serves from
-it, or serves replay with `--replay-only` or when the state is unavailable;
-see [Serve from the state](#serve-from-the-state).
-
-`--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 whose `state` member says whether it served
-from the state, 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: from the state, one tool per read tool, answering from the state where it backs them; in replay, one tool per manifest tool, replaying records |
-| `GET /.well-known/agent-env.json` | The environment card                                                                                                                                           |
-| `POST /agentenv`                  | From the state, `data/reset`, `data/add` and `data/get`; in replay, 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.
-
-In replay the data plane at `/agentenv` is advertised by the card but carries
-no operations; 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`. A replay environment's card reads:
-
-```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": "Untrusted captured API catalog: … GET /api/users/{numeric}; returns a JSON object with fields \"id\", \"uid\", \"login\", \"email\"; recorded statuses 200; 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. After the catalog warning, each description
-names the method and path template, then what the tool returns, one level deep:
-`returns a JSON object with fields …`, `returns a JSON array of objects with
-fields …` or `returns a JSON object whose <member> lists objects with fields …`,
-where a list is an array of objects found by the
-[environment state](web-network-captures.md#environment-state)'s list rule (the
-root array, or the one array of objects an envelope carries). Field and member
-names are written as JSON strings, so a captured name cannot read as more of
-the description; a member name too long to show whole is a quoted prefix marked
-as truncated. The summary comes
-from the first cited `2xx` record that replay answers as JSON; only when none
-did, the first cited JSON record of another status gives it, labelled with that
-status (`status 401 returns …`). It describes one recorded response, not a
-contract. Field names are sampled within the same budget as other captured
-values, and the manifest's `statuses` for the tool follow; a tool with no JSON
-record states only its statuses. The description then lists the replayed
-records and the evidence ID, and the whole catalog stays within its
-serialization reservation, which the summaries and MCP annotations are charged
-to.
-
-Over MCP, every tool also carries annotations: `readOnlyHint` is true for the
-safe methods (`GET`, `HEAD`, `OPTIONS` and `TRACE`) and for query `POST`s (a
-path segment such as `search` or `query`); `destructiveHint` is true for `DELETE` and left unset for other
-writes, so the MCP default (destructive) applies to them, and read-only tools
-omit it because clients ignore it there; `idempotentHint` is true for the safe
-methods, `PUT` and `DELETE`; and `openWorldHint` is false for every tool,
-because answers come from the capture rather than the captured application. The
-hints describe the captured method; replay itself changes nothing. The card
-keeps the `name`, `description` and `inputSchema` of the echo example's tool
-shape and carries no annotations.
-
-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.
-In replay, `extensions`, `operations` and `children_environments` are fixed to
-`null`, `[]` and `null`: a replay environment declares no extensions, no
-data-plane operations and no children. Served
-[from the state](#serve-from-the-state), the card declares the three data-plane
-operations and one intake extension instead, leaves write tools out and
-describes each tool as answering from the state where the state backs it.
-
-## Serve from the state
-
-```sh
-rea environment-serve manifest.json --evidence capture.json
-```
-
-Before it binds, the server derives the
-[environment state](web-network-captures.md#environment-state) the capture
-observed: it runs the `environment-state` view on the capture in-process with
-the manifest's `template_rules` in the same order, exactly as
-`inspect-analysis-view` projects it from the same capture, so the state
-Evidence id it reports is the one that projection produces. The view's own
-budget and refusals apply, and the result is checked like the view's Evidence
-for this manifest: extracted from the served capture, with the manifest's
-rules, naming only manifest tools. The server keeps one live state, shared by
-every MCP session and the data plane, starting from the derived state.
-
-A state that is unavailable does not stop the server: it logs a warning naming
-the error `code` and message before it binds, then serves replay. The state is
-unavailable when it cannot be derived, such as from a
-`capture_browser_scenario` capture that selected header values but no response
-bodies or over the view's budget, and when its catalog under the served name
-exceeds the [discovery reservation](#what-a-manifest-is). That check runs
-first, so no state is derived for it, and replay is then admitted exactly as
-with `--replay-only`. `--replay-only`
-serves replay without deriving anything; the card, tools and `/agentenv`
-answers are then exactly those of replay. The stopped document's `state`
-member reports which applied:
-
-- `{"served": true, "evidence_id": "ev_…"}`: served from the derived state.
-- `{"served": false, "reason": "replay-only"}`: `--replay-only` was given.
-- `{"served": false, "reason": "unavailable", "code": "unsupported_target", "message": "…"}`:
-  the state is unavailable; `code` and `message` are those of the refusal
-  (`resource_constraint` for a catalog over the reservation), as the warning
-  logged them.
-
-Each read tool answers according to its view in the state:
-
-| View       | Answer                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
-| ---------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `item`     | The entity the path arguments name, rendered into the recorded envelope of `envelope_ordinal`. Arguments match as replay matches them: each collection segment equals the held collection's segment as written or after percent-decoding, and the identity is the last argument percent-decoded, then as written; values are never re-split on `/`. Any entity the state holds answers, including one `data/add` loaded; query arguments only decide `replay.exact_match`. An entity the state does not hold, or one lacking a field every recording carried, is a tool error; a body is never invented. |
-| `list`     | When the arguments name one of the lines the view checked exactly (its latest recordings before the first related write; every path and query value equal to the recording's, and every recorded query parameter supplied), that recorded envelope with its array rendered from the state: every entity of the collection in state order for `membership: "all"`, or the recorded members still held. A member lacking a field every recording carried makes the call a tool error rather than a partial list.                                                                                           |
-| `document` | When the arguments name the document's checked line exactly, the state's value for it; a tool error when the state holds none.                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
-| `recorded` | The recording, as replay answers it.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
-
-A list or document call that names no checked line, including a line recorded
-after a write or with other query values, answers from the recording. Every
-answer has the replay shape plus `state`: `{"source": "state", "view": …}`
-naming the entity, collection or document path, or `{"source": "recording",
-"reason": …}` with the view's reason, `no-view` or `unrecorded-request`. A
-state answer carries the base record's status, content type and `replay`
-provenance with `truncated: false`; one whose JSON would exceed 256 KiB is
-refused as a `resource_constraint` tool error rather than cut. Extraction does
-not state-back a document whose rendered JSON exceeds 256 KiB; that read stays
-recorded (`rendered-oversize`) and replays the captured body. Serving is
-read-only: `POST`, `PUT`, `PATCH` and `DELETE` tools, other than query `POST`s,
-are not served, so nothing a call does changes the state. Query `POST`s stay
-served and answer from their recordings with the reason `query-body`.
-
-The data plane serves three JSON-RPC methods:
-
-| Method       | Result                                                                                                    |
-| ------------ | --------------------------------------------------------------------------------------------------------- |
-| `data/reset` | `{}` after restoring the state the Evidence holds                                                         |
-| `data/add`   | `{}` after replacing the whole state with one valid `rea-state/v1` document                               |
-| `data/get`   | `{"parts": [{"kind": "data", "data": <rea-state/v1 document>}]}` with `state_evidence_id` and the `types` |
-
-Calls run one at a time in arrival order across requests. Every message of a
-batch is queued when the batch arrives, so another request's call never lands
-between them and each message sees the changes of those before it; a reset
-sent while a download is loading applies after that load. `data/add`
-takes exactly one part: a `data` part whose `data` is the document, or a
-`file` part whose `file` carries `bytes` (base64 of UTF-8 JSON) or a `uri`,
-either a `file://` URL of a local regular file, whose host is empty or
-`localhost`, or an `https://` URL fetched without following redirects and
-within 30 seconds, including reading the body; `mimeType`, when given, is
-`application/json`. A `file://` URL naming another host, or a UNC path such as
-`file:////server/share/state.json`, is refused before anything is opened, so a
-load never reaches a network share. A loaded document is at most 32
-MiB, and so is the state as `data/get` writes it back with the members a
-document may omit (`types`, `state_evidence_id`, record citations), so a
-reported state always loads again; an inline part also stays within the 4 MiB
-request body bound, so larger states arrive by `uri`. Anything else, including `{"parts": []}`, is `-32602
-invalid params`; a download that fails or answers a non-2xx status is
-`-32000`. Errors never echo the uri or the content; a file or download failure
-names its category in `error.data.reason`: `not-found`, `permission`,
-`not-regular-file`, `changed` or `read-failed` for files, `timeout`,
-`http-status` or `network` (connection, TLS or a refused redirect) for
-downloads, and `cancelled` for a download the server's stop or its caller's
-departure ended.
-
-Stopping the server cancels every pending call, and a caller that leaves before
-its reply cancels its own: a download in progress ends, and calls not yet run
-are answered `-32000` with `error.data.reason` `cancelled` without running. A
-cancelled call leaves the state unchanged, and shutdown never waits for a
-download.
-
-A `file://` state file whose close fails stays owned by the server, and
-the `data/add` gets `-32000`. The next `file://` load retries that close first
-and, while it still fails, answers `-32000` without reading another file;
-inline and `https://` documents still load. Closing the server retries it once
-more and fails with the unfinished close rather than dropping the descriptor.
-
-One `/agentenv` response carries at most 64 MiB of replies, twice the 32 MiB
-a loaded document may hold: room for a `data/get` of a loaded state, while a
-batch of reads cannot multiply a large state into one body. Replies are
-measured in order as they are produced, in bounded parts and before they are
-assembled, and room is kept for every later reply's budget error and the
-batch's brackets and commas, so one that would take the response past the
-budget is never built whole and is answered instead with `-32000` whose `error.data` gives
-`max_response_bytes` and the `reply_bytes` it would have taken. That call still
-ran, so repeat such a read in another request. A reply no larger than that
-error, such as a write's `{}`, is always kept.
-
-```json
-{
-  "rea_state": {
-    "version": 1,
-    "entities": [
-      {
-        "type": "/api/users",
-        "collection": "/api/users",
-        "id": "2",
-        "fields": { "id": 2, "login": "probe" }
-      }
-    ],
-    "documents": []
-  }
-}
-```
-
-Each entity's `type` is a state type's `collection_template`, its `collection`
-matches that template segment by segment (a template parameter matches any one
-segment), its identity field's value is its `id`, and its type, collection and
-id are unique; `view_fields` is optional and names item or list views of its
-type. Views render their values over the entity's fields, so a view's values
-must not set the type's identity field to a value whose text differs from the
-entity's `id`. Spell a collection as requests spell it, as `data/get` reports it: list
-calls find entities under the checked line's recorded path. Each document
-names a `document` view once, at its initial document's `path`. The `version`,
-and the `state_evidence_id` and `types` that `data/get` reports, must match
-the served state, so a `data/get` result loads back unchanged. A number without
-an exact native value, or whose serialized spelling would not be read as exact
-(an integer from 2^53 below 1e21, such as `1e20`, in any spelling), or a
-`__proto__` member is refused rather than altered.
-An invalid document is `-32602` naming the first problem by JSON pointer, as in
-`/rea_state/entities/3/collection` (also in `error.data.path`); a problem
-inside caller data (`fields`, `value`, `types`) is located at that member, so
-the pointer never names the caller's keys. A refused document changes nothing;
-a valid one replaces the whole state at once. The order of `entities` is the
-state order lists use.
-
-Record citations stay Evidence provenance. An entity's `record_ordinals` may
-be omitted or empty and a document's `record_ordinal` omitted; otherwise they
-must be the served Evidence's citations for that entity or document, or the
-document is refused. After loading, an entity or document whose values equal the Evidence's cites
-the Evidence's records, and one whose values were edited or added cites none
-(`record_ordinals: []`, no `record_ordinal`), so `data/get` never presents a
-loaded value as recorded.
-
-The card declares the operations and what `data/add` accepts:
-
-```json
-{
-  "extensions": [
-    {
-      "uri": "urn:agentenv:intake/v1",
-      "description": "data/add replaces the whole environment state with one rea-state/v1 document; data/get returns the current state in the same format.",
-      "params": {
-        "add": [
-          { "part": "data", "format": "rea-state/v1", "load": "replace" },
-          {
-            "part": "file",
-            "format": "rea-state/v1",
-            "mimeTypes": ["application/json"],
-            "load": "replace"
-          }
-        ],
-        "get": [{ "part": "data", "format": "rea-state/v1" }]
-      }
-    }
-  ],
-  "operations": ["data/reset", "data/add", "data/get"]
-}
-```
-
-The state is a projection of recorded reads. List and document calls answer
-from the state only for the lines their views checked, and every recorded view
-answers from recordings; item calls answer for any held entity but render only
-the envelope one recording carried. Values copied outside entity objects,
-derived values and counters other than those that count a list stay as
-recorded; no write has an effect. An exported bundle carries no state file:
-its server derives the state at startup, as the export does to predict what it
-serves.
-
-## 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, what it serves, 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 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.
-After checking the bundle name, the export prepares the state from the capture
-exactly as the bundle's server will at startup under that name, to predict what
-the bundle serves; an unavailable state, including one whose catalog exceeds
-the discovery reservation, does not stop the export, and the bundle then
-serves replay. The complete tool catalog the bundle serves 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, the pinned package source, the number of tools
-the bundle serves as `tool_count`, and in `state` whether it serves from the
-state, in the shape of the serve command's stopped document.
-
-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 number
-the bundle serves (the manifest's read tools from the state, every manifest
-tool in replay), calls one tool with no arguments and checks the call did not
-fail and its `status` is the expected one, and returns one `serve` result
-whose description reports both checks. The tool is the first served `GET` tool
-without path parameters whose answer to no arguments is not an error, and the
-expected status is the status of that answer: the export calls the same answer
-function the server uses, from the derived state or by replay, so a state
-answer carries its base record's status and a replayed one its record's (an
-unknown recorded status stays unknown; it is not borrowed from another
-record). A bundle 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 served tool
-count, the derived state's Evidence id or that no state is served, and the
-package source. It says what the environment serves: read tools from the state
-the capture observed, the `/agentenv` data plane on it and no write tools yet,
-replay when the state is unavailable, and `--replay-only` for pure replay; it
-says which applies to this bundle, with the error code and message when the
-state is unavailable, and that neither is emulation and served
-content is untrusted data. It 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
-
-The 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. The state is derived once, in-process and before binding, from the
-already authenticated capture: it is projected as retained Evidence, so the
-capture's strings are not charged again as inline view input, and the view's
-96 MiB budget bounds the derivation. 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, plus the
-live state when it serves from one: the derived initial state, or one
-validated document whose JSON was at most 32 MiB. Data-plane calls run one at a time, so
-at most one loaded document is being read and parsed at once; `data/get`
-serializes the held state whole. No process is launched and nothing is
-written to disk. No outbound network request is made unless a `data/add` call names an
-`https://` uri, which is fetched once within the limits above; a `file://` uri
-is read once. 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/android-analysis.md

@@ -103,10 +103,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 +146,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 +163,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 +233,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,37 +299,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. REA reads it from the environment captured
-at process start. A change applies on the next process start; an already
-running server keeps the deadline it started with. The same deadline bounds
-each upstream call. A timeout names `REA_JADX_OPERATION_TIMEOUT_MS`, the
-effective milliseconds, and that range. 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
@@ -366,14 +320,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/apktool-resource-analysis.md

@@ -8,7 +8,7 @@ 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
+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
@@ -24,30 +24,6 @@ missing launcher reports `capability_unavailable` with the
 `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
@@ -62,37 +38,20 @@ reports `capability_unavailable`.
 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
-rea decode-android-resources /targets/Example.apk --decode-timeout-ms 900000
 ```
 
 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.
+`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.
-  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.
@@ -100,29 +59,9 @@ still suppresses all string projection, including in this mode.
   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`.
+  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.
@@ -134,24 +73,17 @@ still suppresses all string projection, including in this mode.
 
 ## Resource and lifecycle limits
 
-- The decode wall clock is `decode_timeout_ms` (CLI `--decode-timeout-ms`).
-  Omitted means 600000 ms. The integer range is 1 to 2147483647. A change
-  applies on the next decode. It does not raise the 4194304-byte (4 MiB)
-  output capture budget. That capture budget has no runtime override. A
-  stopped decode reports `provider_timeout` and names the effective
-  milliseconds; an exceeded capture budget reports `resource_constraint`.
-- The version probe waits 20000 ms and retains 65536 bytes. This release has
-  no runtime override for that probe. `decode_timeout_ms` does not raise it.
+- 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.
+- Apktool's own decode failures (`AndrolibException`, directory traversal
+  refusals) surface as `unsupported_target` with apktool's reason preserved
+  verbatim.
 
 ## Real verification
 
@@ -162,11 +94,3 @@ 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/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
@@ -180,21 +162,8 @@ rea trace-dylib-resolution MyApp.app --root Contents/MacOS/MyApp --architecture
 
 Load commands are parsed in TypeScript from Mach-O and FAT headers, including
 the `dylib_use_command` encoding newer linkers emit for flags such as delayed
-initialization, and `LC_LAZY_LOAD_DYLIB_INFO` (`0x3a`). That command stores its
-install name in a linkedit payload rather than in the load command itself.
-Its flag and chain-start image offsets must lie in the slice VM range, which
-is dyld's one-page floor extended by every segment except `__LINKEDIT`,
-measured from the `__TEXT` vmaddr. Payload strings must start after the 24-byte
-header. The load-path NUL must occur before the payload's final byte, matching
-dyld's scan. Distinct payload bytes and payload-range lookups stay within the 16 MiB
-limit, and a file range already read is reused. String scanning and UTF-8
-checks count every reference, including repeats and overlaps, and stop at that
-same aggregate. A slice retains at most 1024 of these commands; further copies are
-unsupported instead of becoming one traced edge each. Symbol references,
-including repeats, stop at 65536 per slice. A larger table is unsupported
-instead of caching one string per offset.
-Nothing is executed and no Apple tool is required, so the tool also works off
-macOS.
+initialization. Nothing is executed and no Apple tool is required, so the tool
+also works off macOS.
 
 Resolution follows dyld:
 
@@ -213,55 +182,30 @@ Resolution follows dyld:
 Each edge lists every candidate path tried, with its outcome: `resolved`,
 `absent`, `not-mach-o`, `malformed`, `unsupported` (recognized Mach-O outside
 parser coverage, such as big-endian images), `architecture-missing`,
-`not-loadable`, `platform-mismatch`, `outside-target`, `escapes-target`, or
-`undetermined`. `not-loadable` means a
-matching-architecture Mach-O image was found but it is not a dylib and cannot
-satisfy a dylib dependency. `platform-mismatch` means a matching-architecture
-dylib was found but its observed platform is incompatible with the process.
-These outcomes reject that candidate; dyld search may continue and resolve a
-later candidate. Candidate outcomes describe individual search paths, while
-`resolution.status` describes the final edge. Slices follow dyld's graded
-architectures, so an `x86_64h` process also loads `x86_64`. The edge's
-`resolution` is one of:
+`outside-target`, `escapes-target`, or `undetermined`. Slices follow dyld's
+graded architectures, so an `x86_64h` process also loads `x86_64`. The edge's `resolution` is one of:
 
-| Status         | Meaning                                                                                                                                                        |
-| -------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `resolved`     | An image inside the analyzed root loads, and no earlier candidate was undeterminable.                                                                          |
-| `conditional`  | An in-root image may load, but an earlier outside candidate, unmodeled environment input, or unknown platform compatibility can change which image dyld loads. |
-| `unresolved`   | Every candidate is definitively absent or unusable inside the root.                                                                                            |
-| `undetermined` | No candidate resolves inside the root, and some candidate lies outside it or depends on the environment.                                                       |
+| Status         | Meaning                                                                                                                                                   |
+| -------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `resolved`     | An image inside the analyzed root loads, and no earlier candidate was undeterminable.                                                                     |
+| `conditional`  | An image inside the root resolves, but an earlier candidate outside the root (for example `/usr/lib/swift`) would win if it exists on the running system. |
+| `unresolved`   | Every candidate is definitively absent or unusable inside the root.                                                                                       |
+| `undetermined` | No candidate resolves inside the root, and some candidate lies outside it or depends on the environment.                                                  |
 
-A `conditional` image is still traced, because it is an in-root candidate
-that may load. Every edge below it has `loader_conditional: true`, and a
-request that reuses it by install name is `conditional` too. An in-root dylib
-with no platform load command remains unknown unless the root is an executable
-with observed macOS platform and the candidate’s CPU type is x86_64, i386, or arm64. In that macOS context,
-[Apple's dyld](https://github.com/apple-oss-distributions/dyld/blob/fd8d0c4d52320ebf64db34f3cb280310d905c5ae/mach_o/UnsafeHeader.cpp#L1137-L1145) supplies an implicit macOS platform to legacy dylibs on those CPU
-types. The candidate records `platform_basis: "macos-dyld-implicit"`; the
-reported slice fields `platform: null` and `platforms: []` remain the parsed
-facts. For other process contexts the platform remains unknown, coverage is
-partial, and the candidate is not treated as incompatible. If a later known
-candidate resolves, it remains the traced image with conditional resolution;
-the trace does not claim the unknown candidate's dependency graph. Findings on
-conditional edges say that they apply only if the conditional image loads.
+A `conditional` image is still traced, because it is the image the analyzed
+root supplies. Every edge below it has `loader_conditional: true`, and a
+request that reuses it by install name is `conditional` too. Findings on those
+edges say that they apply only if the conditional image loads.
 
-Absolute install names that name a path beneath the analyzed root are checked
-within that root, with symlinks and `..` resolved by the same bounded tree
-resolver. Absolute paths outside the root, such as
-`/usr/lib/libSystem.B.dylib`, are `outside-target`; on macOS 11 and later most
-system libraries live in the dyld shared cache rather than on disk, so REA does
-not check them against the host. Mach-O path strings are not converted from
-`file:` URLs or looked up through unrelated host paths.
+Absolute install names such as `/usr/lib/libSystem.B.dylib` are
+`outside-target`. On macOS 11 and later most of them live in the dyld shared
+cache rather than on disk, so REA does not check them against the host.
 
 `findings` are derived, not observed:
 
 - `required-load-unresolved`, `weak-load-unresolved`, and `lazy-load-unresolved`.
-  `LC_LAZY_LOAD_DYLIB` and `LC_LAZY_LOAD_DYLIB_INFO` dependencies are resolved
-  but not traversed, because dyld loads them on first use; an unresolved one is
-  not a launch failure. `LC_LAZY_LOAD_DYLIB_INFO` has no compatibility version,
-  so those fields are null. Its may-be-missing flag is reported as `weak`, and
-  an unresolved dependency with that flag is not a first-use failure: dyld
-  continues if the image is absent.
+  `LC_LAZY_LOAD_DYLIB` dependencies are resolved but not traversed, because dyld
+  loads them on first use; an unresolved one is not a launch failure.
 - `earlier-rpath-candidate-absent`: a compatible Mach-O placed at an earlier
   modeled search path could take precedence, subject to unmodeled search inputs
   and code-signing library validation. These findings do not establish which

docs/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,7 +33,7 @@ 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"]
@@ -139,11 +138,6 @@ graph TD
     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/binary-diagnostics.md

@@ -147,29 +147,6 @@ received signal alone does not establish its exact cause. Dynamic tags require
 a complete DT_NULL inside PT_DYNAMIC; interpreter names and ranges end at the
 first NUL, with any padding still represented by the original segment range.
 
-## Ghidra process failures
-
-When output from the failing Ghidra startup or operation reports
-`java.lang.OutOfMemoryError`, REA returns `resource_constraint`. Java heap or GC
-overhead exhaustion includes heap-specific recovery advice. Metaspace and array
-size failures do not recommend increasing the heap; native-thread exhaustion is
-reported as a capacity constraint with unknown limits.
-
-`configured_jvm_max_heap` records the explicit `-Xmx` value selected by REA's
-launch builder. It is a configuration fact, not measured memory use or proof of
-the effective JVM limit; JVM environment options may affect that limit.
-When a Windows script wrapper selects the JVM, this value remains unknown.
-Historical stdout and stderr remain available, but classification uses only the
-failing operation's `failure_output`. Retained stdout and stderr share an 8 MiB
-budget, but every drained byte is scanned for `java.lang.OutOfMemoryError`:
-`failure_output.observed_oome` records the latest confirmed token's bounded line per stream from
-the failing operation, with its byte offset, even after the budget is spent. These observations own OOME detection; retained text that ends at a class-name prefix cannot confirm a complete token. `line_complete` distinguishes a known line end from an incomplete trailing context; `invalid_utf8` marks replacement-decoded context.
-Incomplete operation output without an observed OOME keeps the original failure code and explains that a memory cause cannot be ruled out. Incompleteness alone does not confirm a memory constraint or justify heap-specific advice. Token context stays within the failing operation's checkpoint; a class-name prefix in a different identifier is not OOME evidence. A trailing bare token requires an observed stream EOF to establish its boundary.
-Output draining waits at most one second,
-subject to earlier cancellation or the startup deadline. `output_incomplete`
-marks a snapshot taken before stream closure; cleanup ownership remains with
-the session until release succeeds.
-
 ## Portable PE resources
 
 `inspect_pe_resources` / `inspect-pe-resources` inspects an explicit PE32 or

docs/browser-observation.md

@@ -18,25 +18,9 @@ Inspect native SAZ or HAR 1.2 offline with REA, or connect Everywhere's separate
 - `inspect_web_page` / `rea inspect-web-page` captures DOM structure, accessibility nodes, scripts, resources, safe response/DOM metadata, attach-window network and console metadata, WebSocket frame sizes, workers, quota, and optionally selected storage key names, redacted storage-content fingerprints, or script sources.
 - `analyze_web_bundle` / `rea analyze-web-bundle` parses selected script artifacts without execution and derives chunk edges, route and endpoint candidates, vendor fingerprints, static WebMCP declarations, and optionally source-map/original-source evidence.
 - `observe_web_session` / `rea observe-web-session` arms an observation window of the requested duration for an external user action and records ordered reload, SPA navigation, redirect, failure, lifecycle, and target-termination metadata.
-- `discover_webmcp_tools` / `rea discover-webmcp-tools` uses the experimental CDP WebMCP domain to return every in-scope registration and its complete observed `input_schema` declaration and canonical `input_schema_sha256` digest inline. Declarations are untrusted JSON data, including declared types, required fields, enums, examples and reference URLs. REA does not resolve schema references. These fields replace `input_schema_shape`. Registrations with the same name and URL in distinct observed frames retain separate identities. `tool_key` includes the observed frame ID; it is not a stable identity across navigation or browser sessions. Same-frame registration updates replace that owner only, and removal leaves other owners intact. Declared `readOnly`, `untrustedContent`, `consequential`, and `autosubmit` annotation hints are reported per registration: `true`/`false` are declared values, `null` means the declaration did not provide the hint in that capture, and a missing `consequential` key means the hint was not recorded, either in a historical capture or because the observed annotation was invalid. Consult discovery completeness and exclusions to distinguish these cases. Malformed annotation values or registration stacks retain the registration with incomplete coverage and an `invalid_protocol_value` exclusion. Other malformed protocol payloads can fail discovery explicitly. REA never exposes `WebMCP.invokeTool`.
-
+- `discover_webmcp_tools` / `rea discover-webmcp-tools` uses the experimental CDP WebMCP domain to return every in-scope registration and its complete observed `input_schema` declaration and canonical `input_schema_sha256` digest inline. Declarations are untrusted JSON data, including declared types, required fields, enums, examples and reference URLs. REA does not resolve schema references. These fields replace `input_schema_shape`. Registrations with the same name and URL in distinct observed frames retain separate identities. `tool_key` includes the observed frame ID; it is not a stable identity across navigation or browser sessions. Same-frame registration updates replace that owner only, and removal leaves other owners intact. Declared `readOnly`, `untrustedContent`, `consequential`, and `autosubmit` annotation hints are reported per registration: `true`/`false` are declared values, `null` means the declaration did not provide the hint in that capture, and a missing `consequential` key means the hint was not recorded, either in a historical capture or because the observed annotation was invalid. Consult discovery completeness and exclusions to distinguish these cases. Malformed annotation values retain the registration with incomplete coverage and an `invalid_protocol_value` exclusion. Other malformed protocol payloads can fail discovery explicitly. REA never exposes `WebMCP.invokeTool`.
 - `compare_web_captures` / `rea compare-web-captures` compares passive captures or exact-step-aligned browser scenarios. Scenario results commit reproducible literal normalization and expose alignment failures plus artifact-level action, screenshot, DOM, accessibility, URL, history, storage, and event differences. Missing or truncated evidence is never treated as equivalence.
 
-For `analyze_web_bundle`, each `webmcp_declarations` entry's
-`schema_property_names` is a source-derived projection of statically known own
-property keys, not schema validation. `schema_property_names_coverage` reports
-how complete that projection is: `complete` means a literal properties object
-was fully enumerated (including an empty literal); `partial` means a literal
-object was available but some computed or spread membership was unresolved,
-and the name array retains keys that were known; `unknown` means the schema or
-properties owner could not be enumerated as an object literal, including
-explicit non-object values; `not_present` means no effective schema or own
-`properties` member was present after the `inputSchema ?? input_schema` alias
-selection. `not_present` describes this projection only: it does not validate a
-schema or rule out properties expressed through other schema constructs. Older
-observations may omit the coverage field; treat omission as `unknown` rather
-than inferring completeness from the array.
-
 Passive DOM comparison checks complete node inventories and complete frame
 parent/child structure independently. Frame IDs and sibling enumeration order
 are capture-local and do not establish a change; duplicate IDs, missing parents,
@@ -82,25 +66,14 @@ Electron `file://` pages use a separate provider and target boundary; see [elect
 
 ## Provider authorities
 
-CDP page capture and V8 Inspector observation attach to an already-running
-target without launching it, driving actions, or evaluating target code.
-Playwright scenarios drive actions and capture step snapshots in either a
-provider-owned browser or a caller-selected external browser. Separate providers
-preserve these authority and lifecycle differences. They share one exclusion
-vocabulary (`BrowserExclusionReason`): every denial reason maps onto it, even
-where a wire schema keeps a narrower historical bucket.
-
-CDP attachment is not a guarantee that the browser preserves all state.
-Chromium can clear another client's `navigator.platform` emulation when REA's
-page session disconnects, even if that session sent no emulation commands.
-This affects page inspection, bundle capture, session observation, screenshots,
-WebMCP discovery, and Electron page inspection; target listing alone does not
-attach a page session. REA cannot read the other client's complete
-user-agent/client-hint configuration and does not replay guessed settings.
-Use a disposable browser when preserving externally configured emulation is
-required, or have the owning client reapply its complete configuration afterward.
-See [the reproduction and Chromium ownership limitation](https://github.com/morluto/rea/issues/4089).
-
+CDP page capture, V8 Inspector observation, and Playwright scenarios stay
+separate providers because their authorities differ: CDP and V8 attach to an
+already-running target and never launch, drive, evaluate, or mutate it, while
+Playwright providers own and drive the runtime (launch browsers, run actions,
+capture step snapshots). Merging them would mix attach-only and owned-process
+lifecycles in one contract. What they share instead is one exclusion
+vocabulary (`BrowserExclusionReason`): every denial reason in every stack maps
+onto it, even where a wire schema keeps a narrower historical bucket.
 Existing static application Evidence and passive web/Electron captures can be
 combined later through
 [JavaScript static/runtime reconciliation](javascript-runtime-reconciliation.md).
@@ -125,11 +98,14 @@ bundle, for example
 `"/Applications/Brave Browser.app/Contents/MacOS/Brave Browser"`. Fedora installs
 Chromium as `chromium-browser`.
 
-REA attaches through the browser's HTTP discovery endpoint on a loopback port,
-or, for some passive tools, through a
-[browser socket](#browsers-without-http-discovery). Connection failures report
-`endpoint_unreachable`; a reachable HTTP service that returns a non-200 or
-non-JSON discovery response reports `invalid_endpoint_response`.
+REA needs the browser's HTTP discovery endpoint on a loopback port. A browser
+driven over `--remote-debugging-pipe` or a private channel, for example by an
+automation SDK, exposes no such endpoint, so `list_browser_targets` has nothing
+to attach to. Connection failures report `endpoint_unreachable`; a reachable
+HTTP service that returns a non-200 or non-JSON discovery response reports
+`invalid_endpoint_response`.
+Reproduce that flow in a Chromium-family browser started with
+`--remote-debugging-port`.
 
 In a minimal Linux container, headed Chromium under Xvfb can keep running while
 its DevTools port never opens. Install the GLES, EGL, and Mesa DRI libraries
@@ -181,9 +157,7 @@ file for you.
   the origins you are investigating.
 
 A browser driven only through `--remote-debugging-pipe` or a vendor's private
-automation channel has neither endpoint, and REA cannot attach to it. To
-inspect such a page, reproduce it in a Chromium-family browser started with
-`--remote-debugging-port`.
+automation channel has neither endpoint, and REA cannot attach to it.
 
 ## Request boundary
 
@@ -216,11 +190,6 @@ rea inspect-web-page http://127.0.0.1:9222 TARGET_ID \
   --json
 ```
 
-Passive observation honors the requested duration using cancellable waits within
-the runtime's timer range. Long windows stay pending across successive waits;
-caller cancellation, target termination or leaving the allowed origins ends
-collection early. `window_elapsed` identifies completion of the requested wait.
-
 Static bundle analysis and a user-driven observation window are separate operations:
 
 ```bash
@@ -303,30 +272,8 @@ Call `list_browser_targets` first because target IDs are browser-instance-specif
 
 REA establishes a main-frame origin boundary before enabling Runtime, Debugger, or Network observation, rechecks it before document capture, and validates it again afterward. If the main frame navigates during final capture, REA discards the mixed result and returns `target_changed`.
 
-The web-session timeline uses CDP monotonic seconds where the event producer
-provides a comparable timestamp; absent or invalid timestamps are `null` rather
-than a synthetic zero. Events buffered while REA samples the window boundary are
-retained only when their timestamp places them after that boundary; older events
-are excluded. A buffered event without a comparable timestamp may remain as
-contextual evidence with `timestamp: null`, accompanied by a limitation stating
-that it does not establish activity in the selected window. Main-frame scope
-enforcement still applies to contextual navigation events. Network redirect
-events retain their paired prior-hop response context when the timestamped
-next-request event falls inside the window. The pre-arm timeline buffer is bounded
-by original CDP message bytes. If clock sampling completes after that budget is
-exhausted, the operation returns `payload_limit` instead of a partial window.
-Cancellation and clock-request failures retain their own outcomes.
-
 ## Data minimization
 
-The Link projection parses repeated CDP header field lines independently and
-retains their declarations in order, including derived untrusted agent hints.
-Commas inside URI targets or quoted parameters remain part of those values.
-COOP and COEP projections retain the exact declared token after validating the
-complete Structured Field Item, including parameters such as `report-to`.
-These are declarations, not an assessment of the document's effective policy;
-absent, malformed or non-token items project as `null`.
-
 REA retains local observation data and removes only URL userinfo credentials, explicitly declared scenario secrets, and values from structured credential/storage fields:
 
 - URL observations preserve the complete local URL, including query values, fragments, duplicate parameters, and their order. Only username/password userinfo is removed; malformed original URL strings remain available with `origin: null`.
@@ -360,9 +307,9 @@ REA retains local observation data and removes only URL userinfo credentials, ex
   WebSocket stream inventories and connection counts likewise require complete
   WebSocket coverage. Redirect resource types use only shared known metadata:
   an omitted type leaves equality unknown rather than proving a modification.
-- Console observations with a stack source retain call type, argument types, the CDP `Runtime.Timestamp` in milliseconds since Unix epoch, and source location. An absent or invalid timestamp is `null` and makes `console_events` incomplete; an observed zero remains zero. Argument types are listed by CDP argument position. An absent or non-array argument inventory is `null`, and a malformed argument keeps its position as `unknown`; either makes `console_events` incomplete, while an observed empty inventory remains `[]`. A malformed stack or top stack frame is not replaced by its caller: the console event is excluded, and a request initiator location or WebMCP `registration_source` is `null`; each is reported as `invalid_protocol_value`. This epoch-millisecond clock is separate from the monotonic-second timestamps in `observe-web-session`. When console text capture is selected, already-delivered primitive values are retained verbatim with their original `argument_index`; objects, getters, and remote properties are never expanded. Text capture is `unavailable` when the argument inventory is unknown.
-- WebSocket observations retain direction, opcode, and payload byte length. A missing or malformed CDP opcode is returned as `null`, with opcode-dependent payload byte length and shape also `null`, and marks `websocket_frames` incomplete. Missing or wrong-typed payload data is not treated as empty; its byte length is `null`, and a text payload shape is unknown. Numeric opcode `0` and an observed empty payload remain distinct from missing data. Opcode is nullable in the public inspection schema, so clients must handle unknown protocol values. When shape capture is selected, text messages are classified as text or complete value-free JSON shape; binary bytes, hashes, prefixes, and raw payloads are never retained.
-- Storage observations always redact values. Key names, IndexedDB names, and cache names require `include_storage_keys`; stable content fingerprints require the additional `include_storage_fingerprints` selection. Cookie fingerprints cover cookies applicable to the current main-frame URL, including its path, rather than every cookie path on that origin. Other storage remains scoped to the origin. Cache fingerprints hash all decoded response bytes, including bodies above 64 KiB, subject to the [64 MiB per-message CDP limit](#request-boundary). Missing or undecodable cache bodies and partial IndexedDB remote objects make fingerprint coverage incomplete, so identical observations remain `unknown`.
+- Console observations with a stack source retain call type, argument types, timestamp, and source location. When console text capture is selected, already-delivered primitive values are retained verbatim; objects, getters, and remote properties are never expanded.
+- WebSocket observations retain direction, opcode, and payload byte length. When shape capture is selected, text frames are classified as text or complete value-free JSON shape; binary bytes, hashes, prefixes, and raw frames are never retained.
+- Storage observations always redact values. Key names, IndexedDB names, and cache names require `include_storage_keys`; stable content fingerprints require the additional `include_storage_fingerprints` selection. Cookie fingerprints cover cookies applicable to the current main-frame URL, including its path, rather than every cookie path on that origin. Other storage remains scoped to the origin. Cache bodies above 64 KiB and partial IndexedDB remote objects make fingerprint coverage incomplete, so identical observations remain `unknown`.
 - Unavailable or malformed storage inventories mark `storage_keys` unavailable, even without fingerprints. Comparisons suppress inferred key additions and removals while preserving modifications proven by complete fingerprints on both sides. Previously exported captures are not retroactively corrected; recapture them to obtain these coverage markers.
 - Script metadata is included only when CDP supplies a URL on an allowed origin. Stable keys exclude transient CDP script IDs, and exact transient raw URLs are used only during script/resource reconciliation. URL-less scripts are excluded because their origin cannot be established. When CDP supplies an execution-context association, the accepted script retains its authorized frame ID for later attribution. Script metadata admission bounds retained identity and source-map strings to 8 MiB and 50,000 records. When a source-map URL cannot fit, the script identity remains and source-map coverage reports `resource_budget_exhausted`; rejected script observations are counted without retaining their IDs. Source content is omitted unless explicitly requested and is returned inline as a self-verifying artifact with its SHA-256 digest.
 
@@ -384,49 +331,6 @@ validation and resource bounds. Omitted script metadata makes its affected
 section explicitly truncated.
 Disallowed-origin entries are filtered before retention.
 
-Selected script-source collection shares a 32 MiB aggregate UTF-8 retention
-budget and the `command_timeout_ms` deadline (default 20000 ms) across the
-capture. The byte budget has no runtime override. An oversized source is
-omitted while later smaller sources may still fit. When the deadline expires,
-remaining source reads are skipped. Script metadata, per-item omission reasons,
-and `script_sources` completeness remain available. A single CDP response can
-still be materialized up to the separate 64 MiB transport limit before source
-admission; the retention budget does not bound that transient allocation.
-
-Bundle parsing and semantic inspection run sequentially in an owned child,
-without executing captured code. These are separate phases. `max_heap_mb`
-defaults to 1024 MiB V8 old-space (range 128..16384). `analysis_timeout_ms`
-defaults to 30000 per script, including startup and transfer.
-`total_analysis_timeout_ms` defaults to 300000 across script analysis. A
-per-script deadline above the effective total is rejected. A failed or
-timed-out script becomes an explicit unknown while completed findings and later
-scripts remain available. Total-deadline expiry returns a typed timeout with
-partial Evidence and identifies unstarted scripts. `source_map_fetch_timeout_ms`
-defaults to 30000 and is an item limitation, not that analysis timeout. These
-controls are also available as CLI flags with hyphenated names. Worker protocol
-and result byte budgets have no runtime override.
-
-One web-bundle capture/analysis is admitted per REA process at a time. Completed
-script results share an 8 MiB serialized transfer budget, with host heap
-reservation checked before decoding and validating another result.
-When the host reservation is what reaches zero, the failure names that heap
-headroom and the remaining fixed budget. When the 8 MiB allowance itself is
-exhausted, the failure names that fixed budget and says it has no runtime
-override. Either stop ends further script launches and returns a typed
-resource failure with completed facts and explicit unstarted-script unknowns.
-Worker control frames are limited to 64 KiB. Cleanup must confirm child termination
-before releasing its private files; failed cleanup retains its exact owner and
-blocks replacement until retry succeeds. Cancellation retains completed bundle
-facts, including cancellation during final cleanup.
-
-The worker heap setting is not a process-family RSS limit. Node enforces V8
-old-space flags; Bun ignores them. Windows Bun instead uses an owned process
-commit limit with a 512 MiB runtime reserve; other Bun hosts have no enforced
-memory limit. An allocation failure before that Windows limit is reported as
-reached still names the configured limit and says it was not reached. These
-bounds do not establish an aggregate host-memory limit across other REA
-operations or external processes.
-
 Resource-tree inventories distinguish a valid empty `resources` array from a
 missing or malformed collection. Invalid resource entries are omitted with
 incomplete coverage, while valid resources from that frame and other frames
@@ -439,24 +343,10 @@ an invalid supplied size remains unknown with incomplete resource coverage while
 the resource's other facts are retained. Zero and nonnegative fractional sizes
 are preserved.
 
-CDP discovery has a 10-second response deadline. HTTP discovery documents
-use an 8 MiB budget. Browser-socket discovery (`Browser.getVersion`,
-`Target.getTargets`) uses the 64 MiB protocol message budget. Neither budget
-nor the discovery deadline has a runtime override. `list_browser_targets` accepts no
-`command_timeout_ms`: HTTP discovery and browser-socket discovery
-(`Browser.getVersion`, `Target.getTargets`) stay on that fixed deadline, and
-the socket closes without a later command. Other CDP tools use
-`command_timeout_ms` (default 20000) for each WebSocket handshake and command
-response, separate from the caller-selected observation window, discovery, and
-the 5000 ms cleanup grace. A browser-level socket's handshake and the following
-`Target.attachToTarget` each receive that full deadline; they do not share one
-budget. A stalled handshake or command reports
-`provider_timeout` and names `command_timeout_ms` only when that operation
-accepts it; caller cancellation still reports cancellation. WebSocket messages
-remain subject to the [64 MiB limit](#request-boundary), which has no runtime
-override. REA does
-not impose a message-count or pending-command quota. On cancellation, it closes
-only its own WebSocket,
+CDP discovery, connection, and commands wait for the peer or caller cancellation;
+a stalled peer can leave an operation waiting. WebSocket messages remain subject
+to the [64 MiB limit](#request-boundary). REA does not impose a message-count or
+pending-command quota. On cancellation, it closes only its own WebSocket,
 waiting up to one second before terminating it. Malformed unsolicited events
 and malformed replies to pending commands poison the connection so later
 commands fail closed. A correlated reply's session ID must match the command's
@@ -465,7 +355,7 @@ rejects it as unknown; other command rejections retain their reported failure.
 
 Network and console coverage starts only after REA attaches and enables the relevant CDP domains. `prior_activity_available` is always `false`; absence from these arrays is not evidence that an event never occurred. Scripts are different: scripts the page parsed before REA attached are still reported under `scripts`. A page that loaded before attach can therefore list its scripts while `network.requests` lacks the requests that fetched them. If CDP reuses a request ID without supplying redirect metadata, REA retains the predecessor observation and marks network coverage incomplete.
 
-Source maps are not fetched by inspection. Bundle analysis fetches them only when `fetch_source_maps` is selected, with exact-origin redirect checks and no credentials, cookies, or referrer. Each fetch operation uses `source_map_fetch_timeout_ms` (default 30000) and a 64 MiB aggregate streamed-response budget across redirects. The byte budget has no runtime override. A fetch overrun is an item limitation, not a thrown analysis timeout. A deadline or byte-limit failure remains explicitly unavailable and makes bundle completeness partial. Source-map decoding also bounds raw resolved identities to 64 MiB and aggregate inline evidence to 32 MiB. Failed maps preserve their failure context when it fits; if another context cannot fit, collection stops with the full requested count, the returned processed count, and an explicit unknown-results limitation. Retained mappings and original sources are returned inline. See [source-location limits](web-source-location.md) for the structural decoder bounds. Original source artifacts with `.ts`, `.tsx`, `.mts`, or `.cts` suffixes carry `text/typescript`; other source names retain `text/javascript`.
+Source maps are not fetched by inspection. Bundle analysis fetches them only when `fetch_source_maps` is selected, with exact-origin redirect checks and no credentials, cookies, or referrer. Each fetch operation has a 30-second deadline and a 64 MiB aggregate streamed-response budget across redirects. A deadline or byte-limit failure remains explicitly unavailable and makes bundle completeness partial. Source-map decoding also bounds raw resolved identities to 64 MiB and aggregate inline evidence to 32 MiB. Failed maps preserve their failure context when it fits; if another context cannot fit, collection stops with the full requested count, the returned processed count, and an explicit unknown-results limitation. Retained mappings and original sources are returned inline. See [source-location limits](web-source-location.md) for the structural decoder bounds. Original source artifacts with `.ts`, `.tsx`, `.mts`, or `.cts` suffixes carry `text/typescript`; other source names retain `text/javascript`.
 
 source-map items retain the script's `declared_url` separately from the observed
 `effective_url`. successful maps use the latter as their source-resolution base.

docs/browser-scenario-contract.md

@@ -23,21 +23,9 @@ that rejection does not roll back browser effects. REA removes its owned
 future-document scripts, restores live frame methods, then disconnects.
 Add secret declarations, storage seeds, and additional artifact or event
 capture only when needed. Action, secret, and storage counts are not capped.
-Duration, action, and navigation timeouts remain separate from CDP command
-deadlines. `command_timeout_ms` (default 20000; omit it to keep that default
-and leave it out of Evidence) bounds launch startup, the connect-over-CDP
-handshake, target lookup, environment commands, and storage CDP commands,
-including replies from attached child targets. Set it in the scenario JSON.
-`capture-browser-scenario` has no `--command-timeout-ms` option.
-It does not change action `timeout_ms`, `wait_for_timeout.duration_ms`, or
-navigation. Service-worker restoration keeps a fixed 5000 ms grace and does
-not inherit a raised `command_timeout_ms`. CDP discovery stays on its own
-fixed deadline. When service workers are blocked, the registration check
-before discovery has its own fixed 10000 ms deadline; `command_timeout_ms`
-does not apply because discovery has not started. The discovery deadline
-covers endpoint discovery only. The following WebSocket handshake and
-`Target.attachToTarget` each use `command_timeout_ms`. `capture.limits` controls retained event and network-content
-budgets; it does not change those liveness deadlines.
+Duration, action, and navigation timeouts remain fixed provider-owned liveness
+limits. `capture.limits` controls retained event and network-content budgets;
+it does not change those liveness deadlines.
 
 ## Minimal launch example
 
@@ -119,11 +107,6 @@ Through MCP, pass the same object as the `capture_browser_scenario` arguments.
 The final step's DOM and accessibility artifacts retain the page state at that
 capture time inline. REA still launches and cleans up the browser profile.
 
-Action `timeout_ms` and `wait_for_timeout.duration_ms` accept integers from 1
-through 2,147,483,647 milliseconds, matching the underlying timer representation.
-Larger values receive an input error before browser launch. Omit `timeout_ms`
-to keep an action pending until completion or request cancellation.
-
 The click's `timeout_ms` covers the click action. A non-navigating `fetch` or
 delayed render can finish later, so use `wait_for` to observe a page-specific
 ready condition before final capture. A page that updates synchronously can
@@ -161,36 +144,6 @@ distinction: it closes and deletes provider-owned profiles, but only disconnects
 from an external CDP browser. Real-browser verification checks both outcomes and
 confirms that an attached external browser remains alive.
 
-That cleanup requires REA to remain running. Abrupt termination, including
-Windows process-tree termination or POSIX `SIGKILL`, can leave the launch
-profile and Playwright artifacts behind. A profile can retain cookies, history,
-cache and origin storage. Later REA runs currently do not reclaim these paths.
-Playwright 1.58.2 can also leave an artifacts directory when launch preparation
-fails before a browser process exists, such as for a missing executable.
-POSIX wrappers can request awaited cancellation with `SIGINT` or `SIGTERM`;
-Windows process termination is not an equivalent graceful-cancellation channel.
-Do not identify owned artifacts by directory prefix or creation time alone.
-See [#4659](https://github.com/morluto/rea/issues/4659) for the remaining recovery
-and wrapper-cancellation work.
-
-Keeping that browser alive does not guarantee its emulation state survives.
-Chromium can clear caller-owned `navigator.platform` emulation when a page CDP
-session disconnects, including sessions that sent no emulation commands. REA
-cannot snapshot the other client's complete user-agent/client-hint settings and
-does not replay a partial reconstruction. Use launch mode to keep this effect
-inside a provider-owned browser, or have the external owning client reapply its
-complete configuration after capture. Connected captures report this limitation;
-see [issue #4089](https://github.com/morluto/rea/issues/4089).
-
-`environment.locale` sets Intl formatting in both modes. Launch also sets
-`navigator.language`, `navigator.languages`, and the request `Accept-Language`.
-Connect preserves the caller's page and request languages; every attached
-capture identifies this locale limitation, including retained partial
-observations. Use launch mode when the application must select the requested
-language through navigator values or request headers. Artifact completeness
-covers the selected observations, not equivalence of launch and connect
-language environments.
-
 HTTP(S) URLs may include ordinary query values and fragments directly. Use
 ordered structured query entries when a value needs to reference a declared
 environment-backed secret. Form, storage, and cookie values are either literal
@@ -224,9 +177,7 @@ statements remain under the attached debugger client's control.
 The result is Evidence with an initial state followed by one record per
 declared action. Each step reports action status, elapsed time, sanitized URLs,
 event bounds, and independently typed capture states for screenshot, DOM,
-accessibility, URL, history, and storage. Actions after a failed or cancelled
-action are not run and are recorded as `cancelled` with a not-executed error.
-Console, page-error, network,
+accessibility, URL, history, and storage. Console, page-error, network,
 WebSocket, frame, worker, popup, and cancelled-download events are attributed to
 steps. Retained events and requested artifacts are returned inline; omitted
 events are counted by kind and identify affected network transactions.
@@ -293,46 +244,6 @@ external browser without closing it. The request itself defines the operation;
 there is no additional REA grant step. The browser and host still enforce their
 own access and process rules.
 
-## Summary delivery
-
-Multi-step scenarios that select accessibility trees, DOM or network events can
-produce results far larger than an MCP client accepts. Select
-`"detail": "summary"` (CLI: `--detail summary --evidence_output <bundle>`) to
-retain the complete Evidence and receive a compact view instead:
-
-- one row per step with its status, error, elapsed time and `after_url`;
-  `before_url` appears only when it differs from the previous step's
-  `after_url`, and sections are listed as captured, missing or truncated
-  (`not_requested` sections are omitted);
-- `final_accessibility`: the accessibility tree of the first failed or
-  cancelled step, or of the last step, falling back to the nearest earlier step
-  that captured one (`step_index` is `null` when none did);
-- retained event counts by kind, with the budget omissions, and network
-  transaction counts by origin, resource type and final status class.
-
-Page exact records from `normalized_result.parent_evidence_id` with
-`inspect_analysis_view`:
-
-```json
-{
-  "source": { "kind": "retained-evidence", "evidence_id": "ev_..." },
-  "view": {
-    "kind": "browser-scenario",
-    "collection": "steps",
-    "step_indices": [3],
-    "artifacts": ["dom"]
-  }
-}
-```
-
-Steps return only the captured sections named in `artifacts` and list the
-others with their state. Events (`"collection": "events"`) accept
-`step_indices`, `event_kinds` and `transaction_ids` and keep each event's
-original `item_index`. An omitted filter selects all records; `[]` selects
-none. Every page repeats the capture's completeness and dropped-event count:
-exhausting the pages does not make a truncated capture complete. The default
-`"detail": "complete"` keeps returning the whole capture inline.
-
 ## Network evidence
 
 `capture.events: ["network"]` retains request, response, completion, failure,

docs/cli.md

@@ -30,13 +30,6 @@ jq -c '{source: {kind: "inline", evidence: .}, view: {kind: "summary"}}' app-evi
 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
@@ -63,22 +56,10 @@ 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.
 
-Select `--detail summary --evidence-bundle /absolute/path/members.json` to
-receive identity, selection, coverage, limitations and collection counts while
-saving the complete original Evidence in a new bundle. Summary requires that
-explicit destination; existing files are preserved. Later
-`inspect-analysis-view` calls can page the exact parent from the saved bundle
-without reopening the assembly. See
-[CLI summary and saved member rows](managed-code-analysis.md#cli-summary-and-saved-member-rows)
-for the complete command sequence. Omitted or `--detail complete` retains the
-full inline response.
-
 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)
+unpack .NET single-file hosts or decode IL2CPP metadata. 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
@@ -102,47 +83,6 @@ 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 local model declarations without loading weights:
-
-```bash
-rea inspect-model-artifact /absolute/path/model.gguf --json
-rea inspect-model-artifact /absolute/path/model.safetensors --hash full --json
-```
-
-Default hashing reads only headers and leaves full-file identity unknown.
-`--hash full` streams the complete file for SHA-256. Both return typed metadata,
-original tensor declarations and derived totals. MCP summaries retain complete
-Evidence for filtered metadata, tensor and type-total pages; CLI compact delivery
-uses `--detail summary --evidence_output FILE`. See [model files](model-artifacts.md).
-
-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:
 
@@ -155,9 +95,8 @@ 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
+Configure [Hopper or Ghidra](installation.md#hopper), or the
+[IDA adapter](ida-provider.md), before analyzing a native target. Substitute
 your target, search text and function name or address in these examples:
 
 ```bash
@@ -214,7 +153,7 @@ 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, JADX, and Kuna, run
+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
@@ -228,12 +167,6 @@ 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
@@ -289,12 +222,7 @@ 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 can consume full saved records.
-`inspect-analysis-view REQUEST.json --evidence-bundle BUNDLE.json` resolves
-the request's `retained-evidence` source ID from that authenticated bundle,
-including bundles exported from an MCP session. The same view JSON works for
-every supported parent kind; no target is reopened and no record is selected
-by file order. Omit `--evidence-bundle` when the request supplies inline Evidence.
+belong to one connection. Separate CLI calls consume full saved records.
 
 ## Import historical source
 
@@ -351,12 +279,6 @@ 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.
@@ -381,95 +303,6 @@ Choose the guide for the target and intended interaction:
 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>
-[--replay-only] [--host H] [--port N]` serves an environment manifest
-projected by `inspect-analysis-view` as an agent environment: an MCP server at
-`/mcp`, the environment card at `/.well-known/agent-env.json`, and a
-`/agentenv` data plane. The manifest's `parent_evidence_id` must equal the
-evidence file's `evidence_id`; otherwise the command refuses with
-`invalid_request` before binding. Before binding it derives the
-`environment-state` view of the capture with the manifest's `template_rules`,
-as `inspect-analysis-view` would, and serves from it: read tools whose views
-are state-backed answer from a live state, write tools are not served, and
-`/agentenv` serves `data/reset`, `data/add` and `data/get`. When the state
-cannot be derived, or its catalog exceeds the discovery reservation, it logs a
-warning with the error code and message and serves replay; `--replay-only` serves replay without deriving. In replay every
-manifest tool replays the retained capture records it cites and `/agentenv`
-answers every method with JSON-RPC `-32601`. The stopped document's `state`
-member is `{"served": true, "evidence_id": …}`,
-`{"served": false, "reason": "replay-only"}` or
-`{"served": false, "reason": "unavailable", "code": …, "message": …}`; see
-[serve from the state](agent-environments.md#serve-from-the-state).
-
-```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 the state and replay
-return and do 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`, checks the bundle name,
-then prepares the state under that name as the bundle's server will at startup
-to predict what the bundle serves (replay when the state is unavailable),
-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` (from the state by default), a Python verifier under
-`artifacts/check_<name>/` that checks the served tool count and one served
-answer, 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,
-the pinned package source, the served `tool_count`, and `state` in the shape
-of the serve command's stopped document. 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
@@ -488,11 +321,6 @@ 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
@@ -509,30 +337,6 @@ output formatting.
 | `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 or state 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, disk-space or
-pathname-length failure on a later path) propagates as the host's failure,
-naming its cause and, when it failed on one bundle file or the package
-tarball, that file. A failure while syncing the finished folder names only its
-cause. Either way the partial folder stays 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
@@ -545,8 +349,7 @@ browser, web and Electron commands (including `analyze-web-bundle`,
 `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
+command, objdump, Rizin and GDB. 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.

docs/client-configuration.md

@@ -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
@@ -153,14 +147,11 @@ 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` deadline, shared by catalog discovery and
-each tools/call, also contributes to that maximum. For `ida` or `auto` selection, a valid IDA registration's parsed
+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.
+profile into the registration; unrelated process values are omitted.
 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
@@ -254,9 +245,6 @@ 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.

docs/client-verification.md

@@ -17,8 +17,8 @@ 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 is the default for the server's advertised inputs; an explicit `full`
-choice is preserved. See the [compact input schema profile](mcp-contracts.md#compact-input-schema-profile)
+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
@@ -457,22 +457,11 @@ 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. Commands share the
-owned-process supervisor: native ownership preparation has its own bounded
-deadline before each short command budget, and timeouts join bounded process-tree
-and output cleanup before returning. If cleanup remains incomplete, the lane retries its retained
-owner and preserves the run directory (including disposable auth) rather than
-removing files still in use; the error retains ownership and recovery details.
-Command stderr is limited to 32 KiB and combined version output to 8 KiB;
-exceeding these diagnostic budgets fails explicitly. Scenario JSON events stream
-to the evaluator without retaining a second raw stdout copy. 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
-is removed after confirmed process cleanup even with
-`REA_AGENT_EVAL_KEEP_FIXTURES=true`. No user configuration,
+is removed even with `REA_AGENT_EVAL_KEEP_FIXTURES=true`. No user configuration,
 rules, plugins or history is copied; shell snapshots and additional agents are
 disabled. Existing API-key environment authentication remains available.
 The native missing-provider scenario preapproves only `open_binary` and

docs/desktop-applications.md

@@ -1,150 +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 | A recognized IL2CPP metadata magic (with the raw version when complete) 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.                                                                                                                                        |
-
-When the four-byte metadata magic is present but version bytes are incomplete,
-the fact retains `raw_version: null`; it does not offer an IL2CPP metadata
-inspection probe. A complete magic/version prefix 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/electron-observation.md

@@ -2,12 +2,6 @@
 
 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
@@ -33,12 +27,6 @@ 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.
@@ -62,24 +50,12 @@ rea inspect-electron-page http://127.0.0.1:9223 TARGET_ID \
 
 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
+completeness, and content-addressed script artifacts. 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
+Collection counts and aggregate script-source bytes are not capped. 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
@@ -116,9 +92,7 @@ The CLI and MCP surfaces accept the same schema. For a JSON request file:
 rea capture-electron-scenario scenario.json --json
 ```
 
-The result records one status and target per declared action; actions after a
-failed or cancelled action are not run and are recorded as `cancelled` with a
-not-executed error. It also records correlated app/window/WebContents,
+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.
@@ -127,18 +101,8 @@ 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.
+startup has a 60-second deadline. Actions wait until completion or request
+cancellation; a click whose target never appears remains pending until cancelled.
 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.
@@ -152,86 +116,6 @@ 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,
@@ -245,10 +129,4 @@ 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 and validates its
-declared lengths against the archive size. Header/index admission is the same
-fixed 16 MiB / 16777216 byte budget used by static ASAR reads. This release has
-no runtime override. An oversized header is not parsed; selecting a member path
-does not bypass admission, and the page stays unauthorized. The header cache
-separately retains at most 16 MiB of already-admitted encoded headers across
-eight archives. Evicting that cache does not raise admission.
+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/evm-bytecode.md

@@ -106,11 +106,7 @@ CLI keeps its existing complete result.
 
 Inputs are limited to 4 MiB, complete replies to 16 MiB and combined diagnostic
 output to 1 MiB. An owned worker has a 256 MiB JavaScript heap, 3 GiB virtual
-address-space limit and 30 CPU seconds. The worker command deadline is
-`timeout_ms` (default 30000 ms, integer 1 through 2147483647) on the next call,
-or `--timeout-ms` on `rea inspect-evm-interface`. Omission keeps 30000 ms.
-Those byte, address-space, and CPU ceilings have no runtime override, and
-`timeout_ms` does not raise them. Virtual
+address-space limit, 30 CPU seconds and a 30-second command deadline. Virtual
 address space differs from resident memory. The worker retains inherited tighter
 soft/hard limits, reports its configured soft limits inline and leaves hard limits
 unchanged. WASM trap reservations are disabled

docs/firmware-analysis.md

@@ -153,39 +153,13 @@ tree semantics, vulnerability scanning, emulation or hardware runtime capture.
 ## Resource and lifecycle policy
 
 - Nonempty regular firmware inputs: at most **128 MiB**, copied and hashed into
-  a private workspace before analysis. Growth beyond that allowance during
-  copying receives the same typed input refusal as an already oversized file.
-  Supply a stable copy within the allowance. No in-place source modification.
+  a private workspace before analysis. No in-place source modification.
 - One queued heavy operation per provider instance; Binwalk one thread and
   Unblob one worker. No automatic parallel extraction engines.
-- Analysis defaults to **120 seconds**, from tool resolution and input snapshot
-  through inspection and its final private-workspace cleanup, or extraction
-  through report consumption and inventory, excluding queue waiting and retained
-  cleanup admission. Inspection has no publication phase. Select `analysis_timeout_ms` in either MCP operation or
-  `--analysis-timeout-ms` in either CLI command for slower analysis. Current
-  results retain the actual budget; an absent historical value means unknown.
-  Extraction publication and its final
-  cleanup start a separate **120-second** budget; select
-  `publication_timeout_ms` in MCP or `--publication-timeout-ms` in CLI for a slow
-  destination. Valid budgets are integers from 1 through 2,147,483,647 ms (the
-  timer representation limit). Publication timeouts identify their phase and
-  verified file progress; verified writes before atomic commit are not a claim
-  that output remains published after rollback. Caller cancellation applies to
-  both phases and final cleanup. Phase handoff, publication commit and final
-  completion also check monotonic elapsed time, so delayed timer callbacks
-  cannot revive an expired budget.
-- Analysis timeout recovery names the selected budget and the analysis control,
-  not the later publication control. Keep the client call timeout above analysis,
-  publication and cleanup headroom; keep the input/range/question unchanged.
-  Resolve any reported incomplete cleanup before retrying. Raising wall time
-  does not raise fixed CPU, memory, report, diagnostic or input limits.
-- Inherited **1 GiB per-process address-space** limit,
+- **120-second** deadline; inherited **1 GiB per-process address-space** limit,
   120 CPU seconds and zero core-dump allowance through `prlimit`.
 - JSON reports: at most **8 MiB** and valid UTF-8; malformed encoding and
   oversized reports fail without repairing or truncating producer data.
-  Exit status 0 is not an empty result: a missing, empty, malformed or
-  oversized report fails with `unreadable_output`, its `report_state`, the
-  command, exit status and captured output. REA does not retry automatically.
   Diagnostic output is bounded with exact captured byte counts.
 - Default staging budget: **256 MiB** and **10,000 entries**, configurable using
   `max_output_bytes` / `max_output_files` (CLI `--max-output-bytes` /

docs/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/frida-instrumentation.md

@@ -6,24 +6,8 @@ For remote devices, pass a host with an optional port (`host[:port]`; bracket IP
 
 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.
 
-For state and capture-coverage checks, pass `{"session_id":"SESSION_ID","detail":"summary"}` to `frida_session_status`. Each call reads the observed session state and retains the complete observation. The reply is an `inspect_analysis_view` Evidence summary with the session identity, state, scripts, `messages_retained`, and `messages_truncated`; message payloads remain in its `parent_evidence_id`. The count covers retained queued messages, not every target event. Omitted `detail` or `detail=complete` preserves the existing complete reply.
-
-A summary's selected fields look like this (excerpt):
-
-```json
-{
-  "summary": {
-    "state": "running",
-    "messages_retained": 50,
-    "messages_truncated": false
-  }
-}
-```
-
-Use `get_evidence_bundle` with `detail="summary"` and `filters={"evidence_id":"PARENT_ID"}` to discover parent metadata without message payloads. Filters apply only to summary delivery. Use `export_evidence_bundle` for the complete canonical bundle, then select the record whose `evidence_id` matches `normalized_result.parent_evidence_id` from the status summary. To use the existing CLI `inspect-analysis-view`, extract that record into a standalone Evidence JSON file and select it as an Evidence-file source with `view={"kind":"summary"}`. Reading retained Evidence does not refresh a live session or verify a process after exit or PID reuse.
-
 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. Local device lookup waits 1000 ms. This release has no runtime override for that lookup; another REA timeout does not raise it. Remote endpoints do not use that lookup. Message capture is bounded to 16 MiB and reports truncation. Metadata, type, and text field caps, and the JSON node cap, are also fixed. Evidence names a cap when that observation actually dropped data. This release has no runtime override for those capture caps. 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.
+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. 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. 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/ghidra-dos.md

@@ -124,10 +124,6 @@ FileBytes digests, every source mapping and its memory digest, relocation record
 module partitions, relocation fixups and linear coordinates rather than relying
 on the imported executable SHA alone.
 
-Expected DOS relocation records retain each fixup's pre-application bytes and
-applied value. Their memory-byte windows come from the final relocated image,
-including changes made by later overlapping fixups.
-
 The result is `verified`, `mismatch`, or `unsupported`. Every check retains its
 expected and observed values. A memory-digest mismatch identifies the source
 range's file offset and analysis address; it does not locate the first differing
@@ -138,10 +134,6 @@ their contents and DOS runtime semantics are not verified. Independent verificat
 also covers explicit [raw-binary imports](raw-binary.md); other formats return
 `unsupported` with measured observations.
 
-MZ verification retains the initialized image described by the header's page
-count and streams appended overlay bytes into the complete original and modified
-source digests. Overlay size does not increase the retained image allocation.
-
 `read_bytes` returns initialized provider memory, including loader fixups; an
 unmapped or uninitialized byte ends the read with an explicit returned length and
 `complete: false`. `address_to_file_offset` uses the provider's source mapping;

docs/ghidra-nativeaot.md

@@ -69,12 +69,6 @@ Pass a returned MethodTable address to `inspect_native_data_type`. A direct PE
 query also derives the snapshot metadata from the authenticated Ghidra session
 handshake, so it does not require a preceding load-image call. In a persistent
 MCP session, load-image followed by type inspection reuses that same derivation.
-The bridge resolves the caller's address spelling once; metadata lookup uses
-its canonical default-space identity. Bare hexadecimal, prefixed hexadecimal,
-and encoded default-space selectors therefore select the same MethodTable.
-Other address spaces and unresolved identities are not matched by offset alone.
-Metadata already supplied by the engine is retained without reading or deriving
-an additional source snapshot.
 The database result remains `unavailable` when Ghidra has no DataType at that
 address; its `metadata_recovery.source` is `read-only-derived-overlay` and
 carries related type, interface, slot, and target observations. Generated

docs/ghidra-provider.md

@@ -65,14 +65,6 @@ PDB, or change analyzer settings.
 
 ## Loaded addresses and file offsets
 
-Ghidra computes overview procedure and string counts from the same inventories
-used by `list_procedures` and `list_strings`, without transporting those rows
-solely to count them. Counts include external functions and only Ghidra-defined
-strings; they do not establish discovery of unidentified functions or undefined
-string bytes. Complete inventories remain available through the list tools.
-Overview reuse follows the target/profile snapshot lifetime and is invalidated
-by session metadata edits.
-
 `rea analyze <path> --provider ghidra --json` and MCP `binary_overview` report
 the observed loaded `image_base` in `normalized_result`. They retain each
 segment's reported `image_base` and `address_space`. A provider that does not
@@ -147,19 +139,6 @@ overview merely because its source artifact is unchanged.
 
 ## Admitted function-analysis semantics
 
-Concurrent callers share one startup while retaining independent cancellation.
-Only the final departing caller abandons startup and waits for its cleanup.
-New attempts wait for that cleanup; failed cleanup retains its original error
-and owned directories until a successful close. Closing the provider reports a
-provider-state failure to live callers rather than cancelling their signals.
-
-Configured analysis extensions and seeds use owned file reads during profile
-resolution and launch snapshots. A changed read extent or descriptor state
-refuses the commitment. Failed source or snapshot descriptor closes remain
-owned and block new admission until cleanup succeeds; the physical failure
-and exact cancellation reason remain available. Provider shutdown joins all
-profile stages before retrying their retained descriptors.
-
 | Concern                 | Ghidra contract                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
 | ----------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
 | Decompiler lifetime     | One persistent `DecompInterface` is opened for the imported Program and disposed during bridge shutdown. Native decompilation has no fixed per-function deadline. External functions or functions without bodies return `null`; cancellation and native failure remain distinct.                                                                                                                                                                                                                                                                                                                                           |
@@ -214,11 +193,7 @@ these tools before compilation. Keeping this matrix separate lets Linux
 host/provider acceptance run with only the host compiler.
 
 `npm run verify:ghidra:windows` checks source-owned native x86-64 PE applications;
-`-- --x86`, `-- --arm`, or `-- --arm64` selects another target architecture;
-`-- --dll` selects DLLs. Choose one architecture and optionally combine it with
-`--dll`. These static fixtures contain source-owned encoded instructions; they
-are not compiler-produced programs. See the [Windows verification scope](windows-ghidra-p0.md#native-authority-and-target-identity)
-for real-provider coverage and exclusions.
+`-- --x86` selects x86 and `-- --dll` selects DLLs, and the flags can be combined.
 These lanes check all 26 read-only operations, target/snapshot/import SHA-256 linkage,
 and project, endpoint, process, and runtime cleanup. The independent native
 lane checks DACLs, handle admission, cancellation, and Job Object lifecycle.

docs/go-binaries.md

@@ -19,56 +19,6 @@ requires an absolute filesystem path and preserves that exact selection:
 }
 ```
 
-For build identity and counts, select `detail: "summary"`. MCP retains the same
-complete Evidence and returns `normalized_result.parent_evidence_id`. Read
-selected dependency versions without reopening the file:
-
-```json
-{
-  "name": "inspect_analysis_view",
-  "arguments": {
-    "source": {
-      "kind": "retained-evidence",
-      "evidence_id": "ev_<parent digest>"
-    },
-    "view": {
-      "kind": "go",
-      "collection": "dependencies",
-      "paths": ["golang.org/x/crypto"],
-      "fields": ["path", "version", "replacement"],
-      "offset": 0,
-      "limit": 10
-    }
-  }
-}
-```
-
-Go views support `dependencies` (exact `paths`) and `settings` (exact `keys`),
-optional original `indices`, field selection, and pagination. Filters intersect;
-empty filter arrays select no rows and `fields: []` returns only row identity.
-Each row keeps its original `index`, scoped to the parent Evidence and collection;
-duplicate module paths and setting keys keep distinct indices. Page offsets
-count matching records. Exhausting retained rows does not establish complete
-runtime dependencies. Original bytes, unknown lines and all complete metadata
-remain in the parent and can be exported as an Evidence bundle.
-
-One-shot CLI summaries save complete Evidence before returning the projection:
-
-```bash
-rea inspect-go-binary ./application --detail summary --evidence_output ./go-evidence.json --json
-```
-
-`--evidence_output` is required for CLI summary delivery and never overwrites an
-existing file. The default CLI/MCP reply remains complete.
-
-[Measured workflows](../experiments/analysis-efficiency/go-build-views.md) include
-catalog repetition and extra calls. Identity/count questions benefit from a
-single summary. In the tested Codex full-catalog configuration, a compound
-question about identity and one dependency uses fewer tokens in captured request JSON with
-one complete inspection than with a summary followed by a lookup. The complete
-reply remains useful for that initial question; retained views support later
-selected reads. Token figures are serialization estimates, not model usage.
-
 ## Observations
 
 The inline Evidence result contains the artifact path, SHA-256, byte length,
@@ -89,8 +39,8 @@ container format, architecture, word size and byte order. A recognized
 - `module.dependencies`, with the same fields and their original order;
 - `module.settings`, retaining ordered key/value entries and duplicate keys;
 - `module.unparsed_lines`, `module.unparsed_line_bytes_base64` and
-  `module.complete`, which says whether every present module-text line was
-  parsed. It does not establish that the dependency inventory is complete.
+  `module.complete`, so unfamiliar, malformed, conflicting or undecodable records
+  do not disappear behind a complete result.
 
 Missing checksums are `null`; empty fields and development/local replacement
 versions remain unchanged. Build settings such as `GOOS`, `GOARCH` or `vcs.revision`
@@ -100,13 +50,6 @@ base64 while other decodable module records are still reported; the reader does
 not insert replacement characters or reject the entire artifact for those
 strings.
 
-When no main-module (`mod`) record was decoded, `module.main` is `null` and
-dependency coverage is unknown. Successfully decoded dependency records remain
-visible. GOPATH-mode builds may contain only a package `path` and build settings;
-their empty dependency array does not establish the absence of dependencies.
-The result's limitations state this explicitly. A module-mode build with a main
-module record and no dependency records has an observed empty dependency list.
-
 ## Supported boundary
 
 The built-in TypeScript reader supports ELF, PE and thin Mach-O images with Go's
@@ -141,10 +84,6 @@ host permission denial, changed artifacts and cancellation retain distinct
 errors. The selected file is never modified; this inspection creates no
 temporary files, starts no subprocesses and accesses no network endpoint.
 
-An input above 256 MiB returns `resource_constraint` with resource `file-size`
-and `reported_limits.maximum_input_bytes`. Select a suitable input within that
-fixed allowance; changing an output-write or transport budget does not admit it.
-
 Resource guards bound the selected file and cumulative header searches to 256 MiB
 each, aggregate embedded strings
 to 1 MiB, structural table decoding to 16 MiB and the complete normalized metadata

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/gpu-code-objects.md

@@ -1,166 +0,0 @@
-# Static CUDA and HIP code objects
-
-`inspect_gpu_code_objects` answers which GPU targets and kernel declarations a
-local artifact carries. It reads ELF/PE sections, standalone CUDA fatbins,
-CUBIN/PTX and Clang HIP bundles, including CCOB v1/v2/v3. It neither executes the
-artifact nor invokes CUDA/ROCm tools. GPU execution, SASS disassembly and host
-launch correlation remain outside coverage.
-
-Start with a target inventory:
-
-```json
-{ "path": "/artifacts/library.so", "view": { "collection": "targets" } }
-```
-
-Target rows aggregate inventoried payloads and distinguish an unrequested kernel
-analysis from a complete or partial one. `objects` pages expose exact object
-IDs, compression declarations and encoded/header locations. Fields, exact
-filters, batch IDs and stable pagination select the facts delivered to the
-caller. IDs are positional within the recorded artifact SHA-256. Selecting `object_ids`
-in a new inspection requires `expected_sha256` from that inventory; a changed
-file is rejected before parsing selected payloads.
-
-`target` is the inventory declaration used for selection; `payload_target` is
-the independently observed inner declaration when available. Object pages keep
-both values, their kind, `target_consistency` and inspection coverage even with
-selected fields.
-Conflicting base architectures retain both values, mark object/report/target
-coverage partial and annotate the affected kernels. CUBIN flags establish a base
-architecture: `base-only` explicitly leaves feature-profile agreement unknown,
-including `a` variants. A standalone declaration is `single-source`, and
-unexamined payloads remain `unexamined`. An exact AMDGPU target is normalized at
-its note owner for comparison with a Clang bundle declaration; raw values remain
-intact. Unresolved feature comparisons stay `unknown`.
-
-`cuda_target_header` retains the OS ABI, normalized raw `e_flags` and exact
-header location. CUDA OS ABI `0x33` and the observed `0x41` flags layout use
-different architecture fields; they are decoded at one ABI-aware owner.
-Unrecognized layouts keep the header and an unknown target instead of
-inventing an SM label. Header provenance is validated against its CUBIN object.
-
-Target filters select inventory declarations. An unselected payload's inner
-target remains unexamined; an empty filtered result does not establish that
-no enclosed code declares that target. Discovering every inner declaration
-requires decoding those payloads.
-
-HIP IDs with one or two separators before the architecture retain the declared
-target. If a recognized AMDGPU bundle ID does not expose a target, the same
-bounded note-discovery owner used for standalone AMDGPU files establishes it
-before filtering. Those directory/note reads share the inspection work budget;
-successive queries can select the target returned by inventory.
-
-Decode selected targets and return a kernel page in the same call:
-
-```json
-{
-  "path": "/artifacts/library.so",
-  "analysis": "kernels",
-  "targets": ["sm_100"],
-  "view": {
-    "collection": "kernels",
-    "names": ["kernel_name"],
-    "fields": [
-      "name",
-      "parameter_count",
-      "parameter_bytes",
-      "parameters",
-      "registers",
-      "shared_bytes"
-    ]
-  }
-}
-```
-
-Only selected payloads are decoded. Other inventory entries remain present with
-`not-selected` states, and overall payload coverage remains partial. An empty
-kernel page proves no matching retained fact; it does not establish that an
-unexamined payload contains no kernel. Missing fields remain null.
-
-Kernel representations have different meanings:
-
-- PTX reports parameter declarations and virtual registers. Shared bytes cover
-  supported static declarations inside that entry; they do not establish module
-  shared memory, dynamic allocation or physical device resources.
-  Scalar register declarations count each bare or percent-prefixed name and
-  each parameterized range. Unsupported declaration forms or overflowing totals
-  retain an unknown count and partial decoding coverage. Unsupported parameter
-  layouts and unknown shared-memory declarations likewise retain their known
-  facts, explicit limitations and partial coverage through retained pages.
-- CUBIN identifies CUDA entry symbols and reads numeric `nv.info` records and
-  native section declarations. Global register declarations also cover compiler
-  versions that leave the older text-section register field empty.
-- AMDGPU reads v3+ MessagePack notes. Argument counts include hidden ABI arguments
-  when present; SGPR/VGPR counts and fixed group/private segment sizes retain
-  their declared meanings. Legacy YAML metadata remains unsupported.
-
-Each selected PTX payload becomes a retained UTF-8 text artifact with a SHA-256,
-byte length and source coordinates. It is omitted from compact replies. Read it
-with `inspect_analysis_view` and the parent Evidence ID returned by the compact
-receipt:
-
-```json
-{
-  "source": { "kind": "retained-evidence", "evidence_id": "ev_..." },
-  "view": {
-    "kind": "gpu-code-objects",
-    "collection": "ptx",
-    "object_id": "...",
-    "offset": 0,
-    "limit": 4096
-  }
-}
-```
-
-Text offsets use UTF-16 code units and must fall on Unicode scalar boundaries.
-Complete Evidence retains the selected text; `export_evidence_bundle` provides
-its portable source record. Historical pages never reopen the input file.
-
-A location with `container_id: null` uses original file offsets. Other locations
-use that inventoried object's decoded byte coordinates. Follow its parent,
-encoded location and digest to trace decompressed metadata back to a native
-section and the original file. Decoded offsets are never presented as physical
-file offsets.
-
-The CLI uses the same service and contracts:
-
-```sh
-rea inspect-gpu-code-objects /artifacts/library.so --analysis kernels \
-  --targets '["sm_100"]' --detail summary \
-  --view '{"collection":"kernels","names":["kernel_name"]}' \
-  --evidence_output /analysis/library-gpu.evidence.json --json
-```
-
-A full-file SHA-256 always streams every byte. Inventory then reads bounded
-native directories and bundle headers; CCOB requires decompression to discover
-its inner directory. Kernel analysis reads selected payloads. `bytes_read`
-includes hashing and subsequent descriptor reads, so this is not a header-only
-hashing workflow.
-
-CUDA raw LZ4 blocks and Zstd, and CCOB zlib/Zstd are supported. Unknown versions
-or codecs retain declarations with explicit limitations. Lengths are checked
-before decoding, and CCOB's truncated MD5 is verified against decoded bytes.
-Resource limits are one active inspection, 128 MiB per input/output buffer,
-512 MiB of payload input, decoded output and AMD note-read work per inspection,
-and 16 MiB retained facts including selected PTX. Payload work is reserved before
-reading or allocating; a capacity refusal does not reread an aliased payload.
-Native tables and decoded section names each have a 16 MiB structural budget;
-AMDGPU ELF note discovery admits at most 8 MiB of source note bytes, with
-bounded depth and container/string allocations. Standalone AMD targets are read
-from those notes before target selection; selected kernel analysis reuses the
-same parsed declarations. Pages have a
-1 MiB response budget. Resource refusals and interrupted observations preserve
-known facts and explicit uncertainty.
-
-CUDA ELF parsing additionally shares a 262,144 record/symbol visit limit,
-128 MiB of cumulative metadata section reads, and a 16 MiB serialized-size
-accounting budget for temporary index facts. These limits are checked before
-index growth; they are not claims about JavaScript heap size. Equivalent scoped
-metadata byte ranges and repeated equal register declarations are coalesced;
-conflicting values remain unknown. Parameter sections are parsed once per ELF.
-
-Missing CUBIN symbol tables or unresolved section names produce `partial`
-object, report and target coverage even when some kernel facts survive. AMD note
-failures preserve earlier successfully parsed declarations and the original
-failure reason. Standalone PTX recognition tries a small header first, then
-continues within the existing 16 MiB text budget when leading comments or
-whitespace obscure its directives; admitted full-file probe bytes are reused.

docs/harmony-analysis.md

@@ -45,12 +45,6 @@ The MCP tool `project_harmony_application_graph` takes the same
 - path-based N-API bridge hypotheses between bytecode and `libs/<abi>` native
   libraries
 
-File and slice occurrences supply component and child-package paths; directory
-trees and symlinks retain their identities in the source inventory without
-being classified as code files. Ark and JavaScript runtime hints summarize the
-classified bytecode and JavaScript lists; supported source extensions share the
-same classification rule as their component rows.
-
 Every claim is path-presence only. Manifest semantics (module identity,
 abilities, entry points, permissions, dependencies), Ark bytecode contents and
 versions, resource resolution, signing verification, and observed native

docs/ida-provider.md

@@ -8,8 +8,6 @@ Choose one lifecycle mode in an upstream MCP JSON registration. Set `REA_IDA_MCP
 
 Each mode accepts one upstream tool profile, checked against `tools/list` before any analysis runs. The attached profile requires the legacy GUI tool names; upstream 2.0.0 renamed those tools, and REA has not established an equivalent attached-mode lifecycle and ownership contract for that catalog. It therefore fails closed with the missing tool names in the error diagnostics.
 
-Startup failures identify the accepted REA analysis operation. Missing-profile and typed startup transport failures retain the original stage in `details.diagnostics.startup_operation`; existing diagnostics, timeout budgets and resource limits remain available. Startup remains shared within a session; each caller receives its own operation attribution. Cancellation retains live cleanup ownership, so a successful retry releases the originating cancellation outcome as well.
-
 The headless profile is defined by the database-supervisor API, not by an upstream version string. The upstream source snapshot [`c133c385`](https://github.com/mrexodia/ida-pro-mcp/tree/c133c3853faa111a9b00ee615c013b720d0c4acd) includes `idb_close` (introduced by [upstream PR #495](https://github.com/mrexodia/ida-pro-mcp/pull/495)) alongside `idb_open` and `idb_list`. Earlier builds may report the same `2.0.0` version while lacking that tool, so REA checks the live catalog rather than treating a version number or branch name as a compatibility guarantee.
 
 | Mode     | Upstream profile    | Known working                                          |
@@ -41,16 +39,7 @@ rea function /absolute/path/to/program main --json
 rea decompile /absolute/path/to/program main --json
 ```
 
-If the registration cannot be read or validated, provider diagnostics retain its
-selected `registration_path` and the configuration owner's setting/constraint
-facts in `configuration_details.settings`, plus `configuration_remediation`.
-`configured` means a path was selected, not that it is valid or an IDA connection
-was established; failed registrations remain unavailable. Correct
-`REA_IDA_MCP_CONFIG` in the next CLI invocation's environment or the MCP server's
-launch environment. Restart/reconnect that server after changing its environment;
-an export in another shell does not update a running server.
-
-Open the **original input binary** in REA, not an `.idb` or `.i64` database. Its SHA-256 must match IDA's recorded input hash. REA checks the attached identity and image base around each analysis request. A mismatch or target switch fails with recovery guidance. The original input must remain readable by REA; WSL can use its mounted alias while the GUI runs on Windows. Attached profiles, including native mode, refuse universal Mach-O inputs at admission: every slice shares the recorded whole-file hash, so REA cannot verify which slice the GUI loaded. Open a thin file extracted with `lipo -thin` in both IDA and REA, or use headless mode, which analyzes the selected slice.
+Open the **original input binary** in REA, not an `.idb` or `.i64` database. Its SHA-256 must match IDA's recorded input hash. REA checks the attached identity and image base around each analysis request. A mismatch or target switch fails with recovery guidance. The original input must remain readable by REA; WSL can use its mounted alias while the GUI runs on Windows.
 
 REA's close operation releases its MCP connection or proxy. It never saves or closes the existing GUI database. External edits remain visible because results are live and are not replayed from snapshots. These checks do not lock the GUI or prove that the database is unpatched.
 
@@ -142,7 +131,7 @@ Use a package version that actually includes this adapter; repository main can b
 {"name":"close_binary","arguments":{}}
 ```
 
-Opening an MCP target starts its selected provider session; headless opening waits for auto-analysis. Set the agent's MCP request deadline long enough for the target. The registration JSON named by `REA_IDA_MCP_CONFIG` has an optional `timeoutMs` integer from 1 to 2147483647. Omitted means 300000. REA applies an edited value on the next IDA connection after it re-reads that file; an already open session keeps the timeout it connected with. Changing the `REA_IDA_MCP_CONFIG` path itself is read at process start. An upstream SDK request that reaches this limit returns `provider_timeout` naming the effective milliseconds and `timeoutMs`. A shorter inner request is the time remaining inside that ceiling, and the error names both when they differ. A freshly opened headless worker can briefly report `status: "busy"` from `server_health`; REA re-reads health every 100 ms until the worker answers, the caller cancels, or `timeoutMs` has elapsed since the first read. Each health request is capped by the time remaining in that overall wait, so a stalled read cannot extend the readiness deadline by another full request timeout. Expiry while the worker is still busy produces a retryable `provider_timeout`; no further read is started after the deadline. That error names the busy tool from the last observation, or `unknown` when the worker reported none or a value that is not tool-name-shaped. If a health request itself consumes the remaining wait budget, the same last-busy timeout is returned with the stalled request's captured output. Cancellation during the wait produces `cancelled`. Any other unexpected health payload, including a busy payload with an invalid shape, remains `unreadable_output`. Cancellation drains the current upstream request before cleanup; it does not force-stop GUI analysis. An open request that times out without a completed response retains the private workspace because worker inventory alone cannot prove the request has stopped. `binary_session` reports actual tool availability. Repeated doctor/setup calls are unnecessary when the registration already works.
+Opening an MCP target starts its selected provider session; headless opening waits for auto-analysis. Set the agent's MCP request deadline long enough for the target. The registration's optional `timeoutMs` defaults to 300000 for upstream requests. An upstream SDK request that reaches this limit returns `provider_timeout` with its operation and actual request budget. A freshly opened headless worker can briefly report `status: "busy"` from `server_health`; REA re-reads health every 100 ms until the worker answers, the caller cancels, or `timeoutMs` has elapsed since the first read. Each health request is capped by the time remaining in that overall wait, so a stalled read cannot extend the readiness deadline by another full request timeout. Expiry while the worker is still busy produces a retryable `provider_timeout`; no further read is started after the deadline. That error names the busy tool from the last observation, or `unknown` when the worker reported none or a value that is not tool-name-shaped. If a health request itself consumes the remaining wait budget, the same last-busy timeout is returned with the stalled request's captured output. Cancellation during the wait produces `cancelled`. Any other unexpected health payload, including a busy payload with an invalid shape, remains `unreadable_output`. Cancellation drains the current upstream request before cleanup; it does not force-stop GUI analysis. An open request that times out without a completed response retains the private workspace because worker inventory alone cannot prove the request has stopped. `binary_session` reports actual tool availability. Repeated doctor/setup calls are unnecessary when the registration already works.
 
 For guided registration, set `REA_IDA_MCP_CONFIG` before `rea setup --client <client>`. Setup includes that file reference in its reviewed plan and preserves it after approval; it does not copy upstream credentials into the agent configuration. For `ida` or `auto` selection, Codex/Kimi setup and doctor use the effective client registration's parsed `timeoutMs` (default 300000 ms) when recommending the agent's per-tool deadline. Existing positive client deadlines remain caller choices. `rea doctor --provider ida --json` validates the registration without starting IDA and explicitly leaves runtime compatibility and target binding for analysis.
 

docs/il2cpp-metadata.md

@@ -1,419 +0,0 @@
-# IL2CPP metadata
-
-`inspect_il2cpp_metadata` / `inspect-il2cpp-metadata` decodes one selected local
-Unity IL2CPP `global-metadata.dat` file and returns its assembly images, type
-definitions, methods and named members with their owners, plus managed string
-literals, by stable index, namespace, range and count,
-with the header sections and serialized index widths. It reads the file without
-running it and requires no Unity installation, IL2CPP binary, active target,
-Hopper, Ghidra or IDA.
-
-Metadata versions 24, 27, 29, 31 and 39 are supported. For example, Unity 2019.4.41f2
-wrote version 24, 2020.3.49f1 version 27, 2022.3.30f1
-wrote version 29, 2022.3.62f3 wrote 31 and 6000.4.2f1 wrote 39; other Unity
-releases that write these numbers have not been checked. Other versions are
-rejected as unsupported. Version 24 decoding covers the 264-byte header layout
-used by the cited Unity 2019.4 build; earlier 24.x layouts are not inferred from
-the version number and are refused when their header or records differ. The path
-must name a regular file; directories and symbolic links are rejected.
-
-With `binary_path`, the tool also reads the matching native binary and links
-each method to its code address. See [Native method addresses](#native-method-addresses).
-
-## MCP
-
-MCP defaults to a compact summary and retains the complete decoded Evidence in
-the session. MCP requires an absolute filesystem path:
-
-```json
-{
-  "name": "inspect_il2cpp_metadata",
-  "arguments": {
-    "path": "/artifacts/Data/Managed/Metadata/global-metadata.dat"
-  }
-}
-```
-
-The summary retains the complete decoded Evidence in the session and returns a
-linked `inspect_analysis_view` overview: artifact identity, metadata version,
-index widths and `counts` (`sections`, `images`, `types`, `methods`,
-`nested_types`, `fields`, `properties`, `events`, `parameters` and
-`string_literals`) without rows. Use `normalized_result.parent_evidence_id` to page
-the original rows without reopening or decoding the file:
-
-```json
-{
-  "source": {
-    "kind": "retained-evidence",
-    "evidence_id": "<parent_evidence_id>"
-  },
-  "view": {
-    "kind": "il2cpp-metadata",
-    "collection": "types",
-    "offset": 0,
-    "limit": 64
-  }
-}
-```
-
-Collections are `sections`, `images`, `types`, `methods`, `fields`,
-`properties`, `events`, `parameters`, `string_literals`, `method_addresses`,
-`return_types`, `field_types`, `parameter_types` and `code_gen_modules`. Every returned row includes
-its source `index`, scoped by artifact SHA-256 and collection. All collections
-accept batch `indices` and `fields`; collections whose rows have a `name` also
-accept exact `names`. Types also accept `image_indices`, `namespaces` and
-`declaring_types`; methods, fields, properties and events accept
-`declaring_types`. Parameters accept exact `method_indices`, so a batch of
-method indices retrieves their parameters without reading the entire parameter
-table. `parameter_types` accepts the same `method_indices`, resolved through the
-retained `parameters` owners; Evidence without `parameters` refuses that filter. Filters intersect, duplicate indices are returned once, and
-rows retain metadata order. An empty filter selects no rows; `fields: []`
-returns indices only. Omitted fields return the complete selected rows.
-
-For example, after resolving a type index, retrieve selected method facts:
-
-```json
-{
-  "source": {
-    "kind": "retained-evidence",
-    "evidence_id": "<parent_evidence_id>"
-  },
-  "view": {
-    "kind": "il2cpp-metadata",
-    "collection": "methods",
-    "declaring_types": [1555],
-    "names": ["SendMessage"],
-    "fields": ["name", "declaring_type"]
-  }
-}
-```
-
-After finding method indices, parameters can be requested directly:
-
-```json
-{
-  "source": {
-    "kind": "retained-evidence",
-    "evidence_id": "<parent_evidence_id>"
-  },
-  "view": {
-    "kind": "il2cpp-metadata",
-    "collection": "parameters",
-    "method_indices": [9785],
-    "fields": ["name", "method"],
-    "limit": 64
-  }
-}
-```
-
-Historical Evidence that predates these member collections remains queryable.
-A missing collection has an unknown (`null`) summary count, and requesting it
-reports that it was not collected; it is never presented as an empty inventory. The same holds for Evidence that predates binary linking: its summary
-omits `binary`, and `method_addresses`, `method_address_states`,
-`return_types`, `field_types` and `parameter_types` counts are `null`.
-Existing empty collections retain a zero count. Full Evidence is preserved.
-
-`offset` counts matching rows, not source indices. `limit` defaults to 64;
-`coverage.next_offset` continues that filtered page. Coverage describes retained
-metadata facts only; runtime behavior and correspondence to native code remain
-unknown. Each view preserves the parent Evidence link, artifact identity and
-limitations. Queries work after the source file is removed. Select
-`detail: "complete"` to return every row inline within the separate MCP response
-budget.
-
-## CLI
-
-```bash
-rea inspect-il2cpp-metadata /absolute/path/global-metadata.dat --json
-```
-
-The CLI defaults to complete Evidence. For compact delivery, explicitly preserve
-the full Evidence in a new file:
-
-```bash
-rea inspect-il2cpp-metadata /absolute/path/global-metadata.dat \
-  --detail summary --evidence_output /tmp/metadata-evidence.json --json
-jq -c '{source: {kind: "inline", evidence: .records[0]}, view: {kind: "il2cpp-metadata", collection: "methods", indices: [9785], fields: ["name", "declaring_type"]}}' \
-  /tmp/metadata-evidence.json > /tmp/metadata-query.json
-rea inspect-analysis-view /tmp/metadata-query.json --json
-```
-
-Use the exported Evidence with the CLI's inline Evidence source format described
-in [CLI and Evidence](cli.md#run-a-command). Compact delivery requires
-`--evidence_output`; existing files are never overwritten. The full export
-preserves every decoded row for subsequent queries without the original file.
-
-`--binary PATH` links method addresses and `--architecture arm64|amd64` selects
-the slice of a universal Mach-O.
-
-## Observations
-
-The result contains:
-
-- `artifact`: path, SHA-256 and byte length;
-- `magic`: unsigned little-endian header signature (`0xFAB11BAF`, delivered as a JSON number);
-- `metadata_version`: `24`, `27`, `29`, `31` or `39`;
-- `index_widths`: the serialized widths (1, 2 or 4 bytes) of
-  `type_definition`, `generic_container`, `parameter` and `type` indices, and
-  `type_width_source`. Version 39 derives the type index width from the
-  `interface-offsets-record` or the `type-definition-record`; versions 24, 27, 29
-  and 31 always use 4-byte indices (`fixed-width-version`);
-- `sections`: all version-specific header sections in header order, each with `offset`, `size`
-  and `count`. Versions 24 to 31 record no counts, so `count` is `null` and
-  record counts come from the section sizes;
-- `images`: `name`, `type_start` and `type_count`;
-- `types`: `name`, `namespace`, `method_start`, `method_count`,
-  `nested_type_start`, `nested_type_count` and `declaring_type`;
-- `methods`: `name` and `declaring_type`;
-- `fields`, `properties` and `events`: `name` and `declaring_type`, the type
-  whose member range holds the row (`-1` when none does);
-- `parameters`: `name` and `method`, the method whose parameter range holds it;
-- `string_literals`: managed string literals as `value`, or `value_base64` with
-  the exact bytes when they are not valid UTF-8;
-- `limitations`.
-
-A row's position in its collection is its metadata index, so `type_start`,
-`method_start` and `declaring_type` refer to positions in `types` or `methods`.
-`nested_type_start` instead indexes the metadata's `nestedTypes` table, which is
-not returned; each nested type's `declaring_type` carries that relationship.
-A type's `declaring_type` is derived from the `nestedTypes` section and is `-1`
-for top-level types. The start of an empty range can retain the original value
-`-1`.
-
-The complete inventory of a large game is several megabytes and can exceed
-the MCP response budget. Summary delivery and filtered, projected pages keep
-unneeded rows out of agent context without discarding the source Evidence.
-
-## Native method addresses
-
-`binary_path` names the native binary built with the metadata: macOS
-`GameAssembly.dylib` (Mach-O), Windows `GameAssembly.dll` (64-bit PE) or
-Android `libil2cpp.so` (64-bit ELF, AArch64 or x86-64). A
-universal Mach-O needs `binary_architecture` (`arm64` or `amd64`); a thin binary
-rejects it. The file is read, never loaded or executed.
-
-A position-independent `libil2cpp.so` stores zero in most pointer slots and
-keeps the value in `R_AARCH64_RELATIVE` or `R_X86_64_RELATIVE` relocations
-(`DT_RELA`). The reader writes those values into a private copy before
-searching it, so addresses are the link-time addresses and RVAs are relative to
-the first loaded segment. Android packed
-relocations (`DT_ANDROID_RELA`) are refused. No target code is executed.
-
-The binary's `Il2CppCodeRegistration` points to one `Il2CppCodeGenModule` per
-assembly image. Each module record starts with its module name, its method
-pointer count and its method pointer array. The reader finds, for every metadata
-image, the single record whose name pointer reaches that image's name string and
-whose count equals the image's method count. It then requires exactly one
-`codeGenModulesCount`/`codeGenModules` pair that lists exactly those records. No
-symbols are needed, so stripped builds work. A method's token row id selects its
-slot in the module's method pointer array.
-
-Module records establish names through their declared NUL-terminated string pointers. NUL/0xFF padding, spaces, Unicode and suffix-shared storage are supported. A pointer to a longer string does not match just its suffix; a pointer directly into a shared suffix may name it. Exact reversed UTF-8 matching avoids rescanning the file for every name and retains duplicate-name owners until module records resolve them. A contributor investigated a Linux
-`GameAssembly.so` from Unity 2023.2.13f1 whose static registration was not located. When no static pair is resolved on x86-64, the reader searches executable ranges for bytes consistent with RIP-relative LEA/MOV references to module-array candidates. Exactly one referenced array candidate must remain. `code_gen_modules_field` is then `null`, and Evidence is **inferred**: instruction boundaries, the absence of a static registration elsewhere, and runtime use were not verified. The module records and slots themselves remain file observations. Static-table associations are **derived**. Otherwise the result is `code-registration-not-found`.
-
-The binary/metadata pair is caller-selected. Name/count/token agreement is structural evidence, not a cryptographic same-build proof. File-offset locations refer to the primary metadata artifact; linked virtual addresses refer to `binary.artifact`. Both SHA-256 identities remain available in compact native pages as `artifact` and `binary_source`.
-
-Contributor-reported verification (not all rerun by the follow-up): macOS arm64 and x86_64 slices from Unity 2021.3.45f2, 2022.3.30f1, 2022.3.62f3 and
-6000.0.84f1 against dSYM symbols; Android arm64 and x86-64 from 2022.3.62f3
-against `libil2cpp.sym.so`; Windows x64 from 2023.2.13f1 (metadata version 29,
-the MIT-licensed game Between Two Worlds 1.0.5, `GameAssembly.dll` SHA-256
-`a3ae7f6ecd1f671297b7d98d12713ef024062d93cd7a4205298102656c93b67a`) against
-Il2CppDumper, where all 43,198 linked methods share an address with a
-same-named Il2CppDumper method and identical code folding groups 10,448 methods
-into 1,735 addresses. A macOS x86_64 build from Unity 2020.3.49f1 (metadata version 27, which Il2CppDumper reads as 27.1) links 10,555 methods, all at addresses where Il2CppDumper names the same method; its other addresses are generic instances. A build from Unity 2021.1.28f1 (also read as 27.1) gives the same result: 10,345 methods linked, every address named the same by Il2CppDumper, and its other 3,486 addresses generic instances.
-
-These checks compare addresses with symbols or with another static tool. They
-do not establish that a linked address is the code the game runs (a runtime may
-patch, hook or replace it), that builds from other Unity versions, compilers or
-obfuscators link the same way, or that a method without an address has no code:
-generic instances, adjustor thunks and invokers are not linked, and an
-`unknown` row was not looked up at all.
-
-The result adds:
-
-- `binary`: artifact identity, `format`, `architecture`, `image_base`,
-  `code_gen_modules_field` (the address of `codeGenModulesCount`, or `null` as
-  described above), `code_gen_modules_array` (the module pointer array) and
-  `code_gen_modules` (`image`, record `address`, `method_pointer_count`);
-- `method_addresses`: one row per method index with `state`, `address` and
-  `rva` (address minus `image_base`), both hexadecimal strings. `state` is
-  `code` when the module slot holds an unambiguously mapped executable address, `no-body` when an observed slot is zero,
-  as for abstract, extern and most generic methods, and `unknown` when no type
-  range in any image holds the method or a symbol relocation leaves its slot unresolved.
-  `address` and `rva` are `null` unless `state` is `code`. The summary counts
-  each state in `counts.method_address_states`. Ghidra seeds are written only
-  for `code` rows.
-
-- `return_types`, `field_types` and `parameter_types`: one row per method,
-  field and parameter index with `type`, the index into the binary's
-  `Il2CppType` table, and `name`, rendered from that table: C# keywords for
-  primitives (`int`, `string`, `object`), `Namespace.Outer+Inner` for type
-  definitions, `T[]`, `T[,]` and `T*`, generic instances as
-  `System.Collections.Generic.List<string>` and generic parameters by their
-  metadata name (`TKey`). A trailing `&` marks a by-reference type. `name` is
-  `null` only for type index `-1`.
-
-`binary` also records `types_field` and `types_count`: the address of
-`Il2CppMetadataRegistration.typesCount` and its value. That record is found as
-the single place whose `fieldOffsetsCount` and `typeDefinitionsSizesCount` both
-equal the metadata type-definition count and whose type table is file mapped.
-
-Without `binary_path`, `binary` is `null` and the four binary collections are
-empty in the complete producer report to indicate unrequested observations. Their summary counts, including state counts, are `null`, and native page requests report unavailable observations. This does not establish an empty native inventory. Missing native fields in historical Evidence remain unknown too.
-
-For metadata version 27, type names are `null` and only type indices are
-reported: versions 27.0 to 27.2 share that header number but place the
-Il2CppType byref flag in different bits, so a rendered name could gain or lose
-`&` without warning.
-
-The builds checked are listed after the module search rules above.
-
-| Reason                            | Category    | Meaning                                                                                           |
-| --------------------------------- | ----------- | ------------------------------------------------------------------------------------------------- |
-| `unsupported-container`           | unsupported | Not a 64-bit little-endian Mach-O, PE or ELF image (ELF: AArch64 or x86-64 with dynamic section). |
-| `slice-selection-required`        | unsupported | A universal Mach-O was given without `binary_architecture`.                                       |
-| `slice-not-found`                 | unsupported | The requested slice is absent, or a thin binary was given an architecture.                        |
-| `unsupported-pointer-encoding`    | unsupported | Mach-O chained fixups or Android packed (APS2) ELF relocations; pointers not decoded.             |
-| `malformed-container`             | input error | The container headers are damaged.                                                                |
-| `code-gen-modules-not-found`      | input error | An image has no module record; often a binary from a different build.                             |
-| `ambiguous-code-gen-module`       | input error | More than one module record matches an image.                                                     |
-| `code-registration-not-found`     | input error | No unique module table or executable-byte array candidate was resolved.                           |
-| `invalid-method-token`            | input error | A method token is not a method row inside its module's pointer count.                             |
-| `invalid-method-pointer`          | input error | A slot is unavailable or its nonzero address lacks unambiguous executable file coverage.          |
-| `metadata-registration-not-found` | input error | No single MetadataRegistration matches the type-definition count.                                 |
-| `invalid-type`                    | input error | A type index or `Il2CppType` record is out of range, unmapped or malformed.                       |
-| `unsupported-type-kind`           | unsupported | A valid type kind has no implemented rendering.                                                   |
-
-Format and selection failures name `binary_path`; capacity refusals remain typed resource errors. Failed linking preserves the metadata source identity, validated counts, selected binary path/architecture and its SHA-256 when observed, plus prior producer observations. It never publishes an incomplete native table as complete. The binary input is bounded to1GiB.
-
-Scans yield cooperatively in bounded batches. Name-address retention and reverse-trie construction are each limited to65,536 entries/nodes and fallback module-array candidates to64 (`native-index-capacity`); exceeding capacity does not prove absence. Rendered type text has a64MiB UTF-8 cache-workspace guard, separate from the64MiB encoded-report admission, and64 nested rendering frames (`native-type-text-capacity` / `type-nesting-capacity`). Genuine cycles are malformed; unsupported type kinds are explicit coverage failures. Native row/text admission runs before allocation or retention. Unused generic parameter names are read on demand from the same stable metadata snapshot. There is no cross-inspection file cache; validated immutable Evidence is reused for session views.
-
-ELF RELATIVE writes into zero-fill are kept as a private virtual-pointer overlay. Unresolved supported-width symbol relocations, including RELA PLT entries, remain unknown; stored zeros never establish no-body. COPY, TLS descriptor, REL, packed APS2 and other unsupported relocation encodings fail closed. Input bytes are unchanged.
-
-Native address queries batch exact64-bit hexadecimal `addresses` and `states` (`code`, `no-body`, `unknown`), intersecting indices and pagination. Numerically equal address spellings match; original row indices and every shared-body alternative survive:
-
-```json
-{
-  "source": {
-    "kind": "retained-evidence",
-    "evidence_id": "<parent_evidence_id>"
-  },
-  "view": {
-    "kind": "il2cpp-metadata",
-    "collection": "method_addresses",
-    "addresses": ["0x180c56ed0"],
-    "states": ["code"],
-    "fields": ["address", "rva"],
-    "offset": 0,
-    "limit": 64
-  }
-}
-```
-
-## Ghidra function names
-
-The CLI can turn a linked report into a
-[`REA_GHIDRA_SEED_FILE`](installation.md) so Ghidra names every IL2CPP method
-before auto-analysis:
-
-```bash
-rea inspect-il2cpp-metadata global-metadata.dat --binary libil2cpp.so \
-  --ghidra-seeds il2cpp-seeds.tsv --json > /dev/null
-export REA_GHIDRA_SEED_FILE="$PWD/il2cpp-seeds.tsv"
-```
-
-Each linked method becomes one `function` seed named `Namespace.Type$$Method`
-(nested types joined with `.`, whitespace replaced by `_`), the Il2CppDumper
-convention. Seeds are at `seed-base + rva`. The default base is where Ghidra's
-loaders place the binary: `0x100000` for an ELF linked at 0, and the link base
-for Mach-O and PE; `--seed-base 0x...` overrides it for a different import. When
-identical code folding gives several methods one address, the first method names
-the function and a `# folded <address> <kept> also <names>` comment line after
-the seeds lists the others, so the kept name is visibly one of several. Ghidra still names a seeded function that is a thunk after its
-target. The file is atomically published with exclusive creation; an existing destination is never replaced. Failed staging retains its cleanup owner for retry. Source digest and link/seed-base comments make the mapping inspectable. Unknown slots are skipped separately from observed no-body slots. `--seed-base` requires `--ghidra-seeds`; overflowing rebased addresses and names/outputs beyond the existing Ghidra protocol limits (2,000 name characters,32MiB file,1,000,000 entries) are refused before publication. The CLI and reusable service use one formatter and owned output workflow; ordinary MCP inspection remains read-only.
-
-## Failures
-
-A file whose magic is not `0xFAB11BAF` fails as an unsupported target with
-`unrecognized-magic`. The file may be encrypted or may not be IL2CPP metadata.
-A version other than 24, 27, 29, 31 or 39 fails as an unsupported target with
-`unsupported-version`.
-
-Damaged metadata returns an input error (`invalid_format`) whose
-message names one reason:
-
-| Reason                    | Meaning                                                                                                          |
-| ------------------------- | ---------------------------------------------------------------------------------------------------------------- |
-| `truncated-header`        | The file is shorter than the header.                                                                             |
-| `unexpected-header-size`  | `stringLiterals.offset` is not the header size: 264 bytes for version 24, 256 for 27, 29 and 31, 380 for 39.     |
-| `section-out-of-bounds`   | A section extends beyond the file, or a non-empty section starts inside the header.                              |
-| `section-overlap`         | Two sections overlap. Zero-size sections are exempt and gaps are allowed.                                        |
-| `record-size-mismatch`    | A section size does not divide into its records, or the record size differs from the one the index widths imply. |
-| `type-index-width`        | The record used to derive the type index width implies no 1, 2 or 4 byte width.                                  |
-| `index-out-of-range`      | A serialized index or range points outside its target collection.                                                |
-| `nested-type-conflict`    | A type is listed as nested in two types, in itself, or in a cycle of declaring types.                            |
-| `declaring-type-mismatch` | A method inside a type's method range names a different type, or a method lies outside its type's range.         |
-| `image-range-overlap`     | Two images claim the same type definitions.                                                                      |
-| `invalid-string`          | A name index does not start a string, or the name is unterminated or not valid UTF-8.                            |
-
-A version field that disagrees with the file's layout, for example a version
-39 file relabeled as 29, usually surfaces as `unexpected-header-size` or
-`record-size-mismatch`.
-
-Two checks are stricter than the IL2CPP runtime: a name index must start a
-string, and an empty range's start must lie between -1 and the collection size.
-Every Unity-written file checked so far satisfies both; metadata rewritten by
-other tools may be rejected.
-
-An incomplete inventory is never reported as complete. Failures after a verified
-snapshot retain partial source Evidence with its SHA-256, byte length and any
-validated section row counts; these counts do not establish that names and
-relationships were decoded. A file that changes during reading and a cancelled
-request keep distinct errors. Decode checkpoints yield for cancellation, and
-close waits for active work. Each reader admits one inspection at a time.
-Resource guards bound the selected file to 256 MiB and the encoded complete
-report to 64 MiB, checking row counts before allocation and JSON/UTF-8/base64 expansion during
-decoding, before serialization. Names and identical literal spans are decoded
-once within one stable file snapshot; no filesystem results are cached across
-inspections. Ownership assignment also yields to cancellation. MCP also applies its
-[response transport budget](mcp-contracts.md); a complete report within the
-report limit can still require the summary and paging path.
-
-## Outside this tool
-
-- Decrypting or deobfuscating protected metadata.
-- Linking Mach-O binaries that use chained fixups, ELF images with Android
-  packed (APS2) relocations, and 32-bit images; generic method instances,
-  adjustor thunks and invokers.
-- Full method signatures beyond the rendered field, parameter and return type
-  names, generic method instances, and type names for metadata version 27.
-- Running Ghidra or another disassembler. `--ghidra-seeds` only writes a seed
-  file for [`REA_GHIDRA_SEED_FILE`](installation.md); use the
-  [native workflow](native-investigation.md) for native code.
-- Metadata versions other than 24, 27, 29, 31 and 39.
-
-Names come from the metadata file only. They do not establish which methods
-were compiled into the native binary or how they behave at runtime.
-
-## Real producer verification
-
-`npm run verify:il2cpp:metadata -- --metadata PATH` exercises a caller-supplied
-`global-metadata.dat` through the public CLI and MCP. It is opt-in, like
-`verify:pcap`, because no real game metadata ships with the repository. Normal
-inspection does not need it.
-
-The follow-up was checked against the public Cpp2IL
-[`Simple_2022_3_35` sample](https://github.com/SamboyCoding/Cpp2IL/tree/b5ad444b82267cb1e4b88b8b373c008105bdea52/TestFiles/Simple_2022_3_35):
-version 31, 1,892,268 bytes, SHA-256
-`2441635a7c234a1a34deccc6a9906d6f5abcbdab078a38b2bf488a52a4962c48`.
-An independent byte-layout oracle matched all 36 images, 2,468 types and 12,409
-methods. Corresponding managed DLLs independently matched names and ownership
-for 35 images, 2,463 types and 12,406 methods; the generated image has no matching
-DLL. This does not establish real-producer coverage for versions 29 or 39.
-
-Compact native summaries omit the `binary.code_gen_modules` table and keep its
-count in `counts.code_gen_modules`. Query `collection: "code_gen_modules"`
-with batch `image_indices` or source `indices`, selected `fields` and pagination.
-Module row `index` is its retained collection position; `image` joins the
-metadata image collection. Scalar registration facts and both source identities
-remain inline. Complete Evidence retains the original full table.

docs/index.md

@@ -47,19 +47,17 @@ For runtime instrumentation, see the [Frida guide](./frida-instrumentation.md).
 
 ## Choose a guide
 
-| Task                                                | Guides                                                                                                                                                                                                                                                                                                                                                                                                     |
-| --------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| Identify a desktop installation                     | [Runtime candidates, evidence and follow-up files](desktop-applications.md)                                                                                                                                                                                                                                                                                                                                |
-| Inspect native functions, references, or types      | [Native binaries](native-investigation.md), [Go metadata](go-binaries.md), [Rust dependencies](rust-binaries.md), [offline ELF layout](binary-diagnostics.md), [recorded crashes](recorded-crashes.md)                                                                                                                                                                                                     |
-| Select a native provider or import format           | [Ghidra semantics](ghidra-provider.md), [Windows](windows-ghidra-p0.md), [DOS](ghidra-dos.md), [raw bytes](raw-binary.md), [MIPS](ghidra-mips.md), [PSP](ghidra-psp.md), [NativeAOT](ghidra-nativeaot.md), [IDA](ida-provider.md), [Kuna](kuna-provider.md), [JEB](jeb-analysis.md)                                                                                                                        |
-| Analyze JavaScript or Electron artifacts            | [Static analysis](javascript-artifact-reconstruction.md), [tracing and comparisons](javascript-application-workflows.md), [application graph](javascript-application-graph.md), [source recovery](javascript-recovery.md)                                                                                                                                                                                  |
-| Compare static JavaScript with runtime observations | [Runtime attribution](javascript-runtime-observation.md), [reconciliation](javascript-runtime-reconciliation.md), [Electron observation](electron-observation.md), [Electron fuses](electron-fuses.md)                                                                                                                                                                                                     |
-| Inspect assemblies, packages, or firmware           | [Godot PCK](godot-pck.md), [.NET](managed-code-analysis.md), [Python packages](python-packaged-applications.md), [Android](android-analysis.md), [Apktool resources](apktool-resource-analysis.md), [ADB acquisition](adb-device-analysis.md), [Apple](apple-application-analysis.md), [Harmony](harmony-analysis.md), [firmware](firmware-analysis.md), [WASM](wasm-artifacts.md), [EVM](evm-bytecode.md) |
-| Observe or compare a browser scenario               | [CDP observation](browser-observation.md), [scenarios](browser-scenario-contract.md), [runtime evidence](web-runtime.md), [historical captures](web-network-captures.md)                                                                                                                                                                                                                                   |
-| Serve recorded behavior as an agent environment     | [Agent environments](agent-environments.md)                                                                                                                                                                                                                                                                                                                                                                |
-| Trace captured website source                       | [Source locations](web-source-location.md), [module traces](website-module-trace.md), [script export](website-script-export.md)                                                                                                                                                                                                                                                                            |
-| Capture and compare a command                       | [Process capture](process-capture.md)                                                                                                                                                                                                                                                                                                                                                                      |
-| Use CLI/MCP and retain evidence                     | [CLI](cli.md), [MCP contracts](mcp-contracts.md), [agent prompts](mcp-prompts.md), [obligation ledgers](reconstruction-obligation-ledgers.md)                                                                                                                                                                                                                                                              |
+| Task                                                | Guides                                                                                                                                                                                                                                                                                                                      |
+| --------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Inspect native functions, references, or types      | [Native binaries](native-investigation.md), [Go metadata](go-binaries.md), [Rust dependencies](rust-binaries.md), [offline ELF layout](binary-diagnostics.md), [recorded crashes](recorded-crashes.md)                                                                                                                      |
+| Select a native provider or import format           | [Ghidra semantics](ghidra-provider.md), [Windows](windows-ghidra-p0.md), [DOS](ghidra-dos.md), [raw bytes](raw-binary.md), [MIPS](ghidra-mips.md), [PSP](ghidra-psp.md), [NativeAOT](ghidra-nativeaot.md), [IDA](ida-provider.md), [JEB](jeb-analysis.md)                                                                   |
+| Analyze JavaScript or Electron artifacts            | [Static analysis](javascript-artifact-reconstruction.md), [tracing and comparisons](javascript-application-workflows.md), [application graph](javascript-application-graph.md), [source recovery](javascript-recovery.md)                                                                                                   |
+| Compare static JavaScript with runtime observations | [Runtime attribution](javascript-runtime-observation.md), [reconciliation](javascript-runtime-reconciliation.md), [Electron observation](electron-observation.md), [Electron fuses](electron-fuses.md)                                                                                                                      |
+| Inspect assemblies, packages, or firmware           | [.NET](managed-code-analysis.md), [Android](android-analysis.md), [Apktool resources](apktool-resource-analysis.md), [ADB acquisition](adb-device-analysis.md), [Apple](apple-application-analysis.md), [Harmony](harmony-analysis.md), [firmware](firmware-analysis.md), [WASM](wasm-artifacts.md), [EVM](evm-bytecode.md) |
+| Observe or compare a browser scenario               | [CDP observation](browser-observation.md), [scenarios](browser-scenario-contract.md), [runtime evidence](web-runtime.md), [historical captures](web-network-captures.md)                                                                                                                                                    |
+| Trace captured website source                       | [Source locations](web-source-location.md), [module traces](website-module-trace.md), [script export](website-script-export.md)                                                                                                                                                                                             |
+| Capture and compare a command                       | [Process capture](process-capture.md)                                                                                                                                                                                                                                                                                       |
+| Use CLI/MCP and retain evidence                     | [CLI](cli.md), [MCP contracts](mcp-contracts.md), [agent prompts](mcp-prompts.md), [obligation ledgers](reconstruction-obligation-ledgers.md)                                                                                                                                                                               |
 
 For development, use [testing](testing.md), [client verification](client-verification.md),
 [tool design](tool-design.md), and [releasing](releasing.md).

docs/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](ida-provider.md) |
+| Update or remove REA              | [Maintenance](#diagnose-update-and-remove)                                |
+| Resolve a client-specific problem | [Client configuration](client-configuration.md)                           |
 
 ## Start setup
 
@@ -24,10 +24,6 @@ Restart the agents named in the completion message. Quit Claude Desktop fully
 before approving, because a running app can overwrite the registration; on
 Windows, see [where Claude Desktop reads its configuration](client-configuration.md#claude-desktop).
 
-During package resolution, npm may print a deprecation warning for `prebuild-install`
-from transitive native dependencies (such as Frida). This warning originates from
-the upstream dependency tree and does not affect REA or indicate setup failure.
-
 For the latest published release, use `npx rea-agents@latest setup`.
 [Package-runner and global-installation options](#package-runners-and-global-installation)
 cover explicit versions, Bun, runtime requirements, and the curl wrapper.
@@ -61,26 +57,12 @@ 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`.
@@ -197,8 +179,6 @@ as well, so it is broader than this Claude-only migration.
 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
@@ -280,14 +260,14 @@ 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
+claude mcp add --scope local rea -- npx -y rea-agents@6.5.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
+claude mcp add --scope local rea -- cmd.exe /d /c npx -y rea-agents@6.5.0 mcp
 ```
 
 <!-- x-release-please-end -->
@@ -344,13 +324,6 @@ A scoped report has `scope.mode: "explicit"`. Its `scope_checks` determine
 `environment_healthy` summarizes the full audit. `--target` adds a target check,
 but the report remains audit-wide unless a scope option is also supplied.
 
-An invalid `REA_LOG_LEVEL` fails every scope, including one client or the
-installed skill, because the executable rejects it before any command. A
-selected client also fails for every other setting that MCP startup rejects,
-including `REA_GHIDRA_STARTUP_TIMEOUT_MS` and `REA_HOPPER_STARTUP_TIMEOUT_MS`.
-Those settings still fail a selected provider and the audit-wide result. A
-skill-only report leaves them informational.
-
 Follow the remediation for the failed check. If a native target has several
 available providers, choose one with `--provider` on the CLI or `provider_id`
 on `open_binary`. A `capability_unavailable` failure carries
@@ -387,17 +360,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.
@@ -435,9 +398,8 @@ 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`.
+in that release, including Qwen Code, Pi and Hermes. DeepSeek Harness (`dsh`)
+is included from 6.5.0 and was absent from the checked npm 6.4.0 package.
 The 6.4.0 registry check does not establish 6.5.0 publication or live DeepSeek
 API integration.
 OpenCode's plan selected
@@ -520,8 +482,8 @@ hosted connector; see [its configuration](client-configuration.md#other-client-s
 | 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`, `kimi`, and `workbuddy` 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.
@@ -620,20 +582,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
@@ -686,11 +634,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
@@ -700,12 +643,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:
@@ -795,17 +735,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
 
@@ -864,7 +796,7 @@ 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
+Windows P0 admits native x86 and x86-64 PE applications and DLLs, plus explicitly
 selected [raw NMOS 6502 images](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.
@@ -882,16 +814,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
@@ -929,34 +851,6 @@ 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
@@ -972,10 +866,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.
 
@@ -987,9 +877,6 @@ 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
@@ -998,24 +885,6 @@ 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)
 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
@@ -1089,8 +958,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
@@ -1118,14 +985,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
 
@@ -1193,14 +1055,8 @@ 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 in
-the environment that starts REA when a busy host needs longer. Restart REA to
-apply a change; the next ownership-helper compile uses the new value. A
-timeout names that effective deadline.
-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.
+`REA_SWIFTC_COMPILE_TIMEOUT_MS` to an integer between 1 and 2,147,483,647 when
+a busy host needs longer.
 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
@@ -1247,7 +1103,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.5.0", "mcp"]
     }
   }
 }
@@ -1312,21 +1168,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/javascript-application-graph.md

@@ -68,17 +68,6 @@ The node vocabulary covers:
 - runtime script instance;
 - an explicit `unknown` kind when classification is not justified.
 
-Static network endpoints can have `resolution: "partial"` when the analyzer
-recognizes a request call but cannot resolve its target to one exact value.
-The observation's `value` then preserves the source expression, and its
-evidence points to the call site. Partial and exact endpoints have distinct
-identities even when their displayed values match. Partial identities also retain
-the source site: matching expression text at different sites does not establish
-the same runtime target. This records observed source syntax; it does not
-establish that the call ran or contacted that endpoint.
-Graph coverage describes the analyzed artifact scope and resource limits, not
-runtime execution. A partial target alone does not imply omitted source.
-
 The directed relation vocabulary is `contains`, `loads`, `imports`, `maps_to`,
 `exposes`, `sends`, `invokes`, `handles`, `calls`, `persists_to`, `observed_as`,
 and `changed_from`. Provider names are deliberately absent from both

docs/javascript-application-workflows.md

@@ -6,7 +6,7 @@ are `inspect_analysis_view`, `trace_application_feature`,
 `trace_javascript_semantics`, `compare_application_versions`,
 `compare_source_to_bundle`, and `compare_javascript_export_shapes`; their CLI
 equivalents use the same names with hyphens. `inspect_analysis_view` projects a
-summary, module page, typed module references, or one module from already completed application
+summary, module page, or one module from already completed application
 Evidence; it does not walk relationships.
 
 `inspect_analysis_view` also projects retained `inspect_binary_layout`
@@ -40,105 +40,6 @@ combine its fields with the fact's location. Semantic trace results include the
 canonical context subset referenced by their returned facts, so those facts
 remain self-contained in the response.
 
-## Retained module facts
-
-For canonical identities and retained source-range counts, query the existing
-`inspect_analysis_view` tool with a typed module-reference projection:
-
-```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
-  }
-}
-```
-
-Replace the parent ID with the actual analysis summary's `parent_evidence_id`.
-Filters match exact retained paths and kinds. Omission includes all values;
-`path: null` selects an unavailable path and `path: ""` selects a recorded empty
-path. Multiple identities can share a path. The default offset is 0 and limit
-is 64; follow `coverage.next_offset` for later matching rows in retained order.
-
-Each row contains its `node_id`, kind, path, canonical identity, retained
-source-range observation count, and distinct supporting authority/state/confidence
-combinations in `basis`. These counts do not prove unique reference sites or
-runtime loading. Use the existing module item view with the row's `node_id` for
-exact source ranges and complete observations. The result retains parent/query
-Evidence identity, artifact identity, limitations and unknowns. `source_coverage`
-keeps selected/unselected sources, graph coverage and unknown counts separate
-from page exhaustion; an exhausted or empty page cannot prove absence from an
-incompletely analyzed application. CLI `inspect-analysis-view` reads the same
-request from a JSON file; portable input uses `source.kind: "inline"` with the
-complete parent Evidence.
-
-## Retained file and native facts
-
-Read metadata, native inventory and unavailable processing scopes directly from
-retained application observations:
-
-```json
-{
-  "source": {
-    "kind": "retained-evidence",
-    "evidence_id": "ev_ACTUAL_PARENT_ID"
-  },
-  "view": {
-    "kind": "javascript-facts",
-    "where": { "paths": ["package.json", "build/Release/addon.node"] },
-    "property_keys": [
-      "name",
-      "version",
-      "bytes",
-      "availability",
-      "operation",
-      "analysis_status"
-    ],
-    "offset": 0,
-    "limit": 32
-  }
-}
-```
-
-Each row preserves its node identity, observation ID, source-map reference and
-original Evidence, including location, authority, confidence, coverage and
-limitations. `property_keys` selects exact retained property names; absent keys
-stay omitted and retained null values stay null. An empty list requests only
-identity/provenance. Observations are not merged into a single asserted fact.
-When property names are unknown, opt into
-`include_available_property_keys: true`. Each returned row then lists its
-original `available_property_keys`, without unselected values; combine this with
-`property_keys: []` for discovery only. The default is false, so known-field
-reads do not pay for field inventories. Keep node/observation IDs paired when
-combining rows; location-related observations need not belong to the same node.
-
-`where.paths` compares exact Evidence `artifact-path` values or `source-range`
-sources. Empty query strings remain valid selectors, though current location
-contracts require nonempty paths/sources. It does not inspect display labels or a
-property named `path`, normalize URLs, or reopen files. Omission includes unknown
-locations; an empty list matches none. Optional `where.kinds` filters original
-node kinds, with an empty list likewise matching none. Multiple locations of
-shared content remain separate rows with the same canonical node identity.
-
-These rows select application-graph observations. Semantic relationships and
-semantic unknown records remain in complete parent Evidence and trace tools.
-
-Rows follow retained node/observation order. The default offset/limit is 0/64;
-follow `coverage.next_offset`. Page totals count matching retained observations,
-while `source_coverage` preserves caller selection and application/semantic
-partial or unknown states. An empty or exhausted page does not establish absence
-outside examined coverage. Complete source Evidence remains available through
-export. CLI `inspect-analysis-view` and portable Evidence use the same contract
-and application implementation as MCP.
-
 ## Feature tracing
 
 Select one literal seed kind: node ID, route, string, API, IPC channel, module,
@@ -154,14 +55,6 @@ matches exactly. Otherwise the result recommends provider-neutral follow-up
 tools and reports `requires-provider-analysis`; it never starts or switches a
 provider implicitly.
 
-A handoff requires the add-on's exact content identity. Unavailable unpacked
-companions remain visible in the trace graph with their canonical path,
-availability and container-backed Evidence. They yield no actionable handoff
-until their bytes are available and the application is reanalyzed; the archive
-digest does not identify the missing add-on. An empty handoff list does not prove
-that the trace contains no native components. Source partial coverage remains
-visible independently of handoff eligibility.
-
 ## Semantic relation tracing
 
 `trace_javascript_semantics` queries the authenticated companion graph without
@@ -184,28 +77,6 @@ registrations/removals and dispatch, Node timers and cancellation handles, async
 defaults, request construction and response consumers, parse/coercion/
 validation boundaries, and built-in resource acquisition/release.
 
-Local callback candidates do not establish a complete target set when a
-conditional write may leave a parameter, catch binding, or uninitialized
-variable unchanged. These calls retain candidate edges and dynamic uncertainty;
-default traces remain ambiguous with partial coverage. Opt into
-`include_ambiguous_dynamic_edges` to traverse the candidates. Proven preceding
-unconditional assignments, including writes dominating a read in the same
-conditional block, can resolve a target; later writes do not replace an
-earlier read or captured alias. Unproved ordering across branches or function
-activations remains conservative. Returned-reference effects use the same
-read-position facts as call resolution.
-
-Returned-reference effects share one property-projection state per source read.
-When several paths reach that read, differing keys at the same depth become
-wildcards; differing depths become an unknown-depth selection. This retains a
-conservative superset of the represented local targets rather than enumerating
-every alias history or dropping paths at a query cap. It can add possible effects,
-including for finite projection cycles. Static limitations disclose this loss of
-precision; semantic graphs retain `dynamic-property` unknowns at the affected
-callee coordinates, and captured web bundles identify the affected script keys.
-These candidates do not prove runtime calls or mutations. Existing source-worker
-and result-admission limits still apply.
-
 Mutation tracking covers explicit member assignments, updates, deletion, and
 loop assignment targets, including the supported local aliases and shared
 nested references. Calls conservatively invalidate exposed mutable references;
@@ -255,13 +126,8 @@ graph and read literal values from `properties.value`, rather than decoding
 role keys or labels. Previously stored graphs and their original IDs remain
 valid inputs.
 
-Endpoint observations keep their value in `properties.value`. When
-`properties.resolution` is `partial`, that value is the unresolved source
-expression, with an identity distinct from an exact endpoint of the same text.
-Semantic request and response nodes keep their endpoint in `properties.endpoint`. Endpoint
-lookup identities are preserved independently of the primitive-value lattice's
-byte budget. An oversized normalized literal can become unknown while the same
-string remains an exact endpoint for tracing and comparison. Endpoint
+Endpoint nodes keep the exact endpoint in each observation's `properties.value`;
+semantic request and response nodes keep it in `properties.endpoint`. Endpoint
 identity keys use `value-sha256:<digest>` over the canonical JSON string when
 that is shorter, or when the original value starts with the reserved digest
 prefix. Other short endpoint keys remain unchanged. Endpoint labels use the
@@ -299,27 +165,6 @@ and the result includes its basis, candidates, changed dimensions, Evidence
 links, limitations, and a `changed_from` graph containing all compared nodes,
 their observations, and relationships.
 
-A matched pair whose only differing dimension is `location` counts as
-`unchanged` when both input graphs have complete coverage and its neighboring
-relationship identities are resolved. This includes an
-identical module shifted by an earlier bundle edit and a named IPC channel
-observed at a new offset. The item still reports `dimensions: ["location"]`
-and both node IDs; the graph retains both original observations and coordinates.
-Content, property, and complete relationship differences still count as
-`changed`. With incomplete coverage, relocation alone remains `unknown` and
-retains the location and coverage dimensions. Matching confidence is unchanged:
-an inferred pair is not promoted to exact identity by this classification.
-
-Complete inventory does not resolve ambiguous or unmatched relationship targets.
-A matched module with identical bytes can therefore remain `unknown` when a
-neighbor, including its containing chunk, has no cross-version match. The item
-retains its exact content match, coordinates, candidate inventory, and an explicit
-relationship-identity limitation. `coverage` is added to its dimensions only for
-incomplete inventory. Definite content, property, or complete topology differences
-remain `changed` while retaining any separate relationship uncertainty.
-An unknown item with no observed content, property, or relationship difference
-does not emit a `changed_from` edge; its pairing and uncertainty remain in the item.
-
 One-sided absence is `added` or `removed` only when the opposite input graph has
 complete coverage. With partial, unavailable, or truncated input, the same
 condition is `unknown`. The comparison retains every classified item and
@@ -363,13 +208,6 @@ Direct return expressions, including expression-bodied arrows, are evaluated
 through an execution-free value lattice. Literal object fields and direct
 return sites are represented in the result. Calls, dynamic spreads, computed
 keys, and parser recovery remain partial or unknown.
-Rebound values are evaluated at their read position: saving an incoming parameter
-before a later assignment preserves caller-dependent uncertainty, while a proven
-preceding assignment can supply a constant. Unresolved ordering remains unknown.
-Supported reads within object and array literals follow left-to-right evaluation;
-an unproved relative order remains unknown. A later write in a separate conditional
-block can still leave an earlier capture unknown because ordering across those
-blocks is not proven.
 Objects and arrays passed to calls, constructors, or tagged templates, used
 as method receivers, or stored through property targets are not assumed
 unchanged afterward. Property stores conservatively retain reference escape

docs/javascript-artifact-reconstruction.md

@@ -50,12 +50,6 @@ The equivalent MCP input is:
 `input_path` must be absolute. `format` accepts `auto`, `asar`, or `directory`.
 `integrity_policy` accepts `fail` or `record-and-continue`; both CLI routes and
 the MCP tool default to `fail`.
-Evidence parameters retain the caller-selected `input_path`, including a
-symlink alias. Both CLI routes anchor relative inputs to their working
-directory without resolving symlinks. The subject and normalized result use
-the resolved path for artifact identity; the selected path remains a separate
-request fact. Older Evidence can omit this parameter; retained records are
-validated without resolving their paths against the live filesystem.
 The result retains the canonical local path, root artifact digest, artifact
 manifest and graph commitments, JavaScript Application Graph, static
 Electron summary, reconstruction statistics, and explicit limitations. It does
@@ -106,15 +100,6 @@ only reduces delivery; source selection reduces text acquisition and analysis.
 Explicit native provider or snapshot routing rejects `--source-path` rather
 than ignoring it.
 
-ASAR header/index admission is a fixed 16 MiB / 16777216 bytes for this
-release. There is no runtime override. The archive index is read before any
-member can be selected, so `source_paths`, `--source-path`, `detail:
-"summary"`, `max_heap_mb`, and available host memory do not bypass or raise
-it. When the header exceeds that allowance, the failure names this budget.
-Analyze an extracted application directory, which does not admit an ASAR
-header, or supply an archive whose header fits. Repeating the unchanged
-request fails the same way.
-
 ## Read the analysis
 
 `analyze_javascript_application` returns the complete analysis Evidence by
@@ -181,8 +166,7 @@ for the tool-result contract.
 
 Use MCP `detail: "summary"` for a large application, then read selected views of
 the retained analysis. Summary changes delivery only. To reduce source parsing,
-select exact [source paths](#select-sources-before-analysis). Source selection
-does not bypass ASAR header/index admission.
+select exact [source paths](#select-sources-before-analysis).
 
 If a complete response exceeds the transport budget, use its retained Evidence
 ID for a summary, module page, or item, or export the bundle. See
@@ -198,18 +182,6 @@ partial Evidence. Cancellation after source analysis begins can also retain
 completed facts, including when interrupted during cleanup, graph construction,
 or Evidence sealing. Unexamined relationships remain unknown.
 
-Per-file gaps identify the applicable processing phase: JavaScript source analysis
-uses AST authority, while package/JSON, HTML-reference and source-map processing
-use artifact-byte authority. File-analysis interruption gaps carry `analysis_status`:
-`interrupted` means the phase was entered (including source-worker startup),
-and `not-started` means interruption prevented that phase from beginning.
-Neither state establishes that parsing completed. Remaining parsers are not run
-after interruption just to populate a result.
-
-Native add-ons remain metadata-only and acquire no JavaScript parse or analysis
-gap. This also applies when their paths are outside `source_paths`; their inventory
-and caller selection remain available without implying applicable AST work.
-
 MCP returns a `partial_observation` retained reference after recording succeeds;
 open it with `inspect_analysis_view` on the same connection. If the SDK stopped
 waiting before receiving the reply, follow [MCP cancellation recovery](mcp-contracts.md#progress-and-cancellation)
@@ -304,13 +276,8 @@ RPC client syntax also contributes network endpoint candidates, in both
   named operation found at the start of a string or cooked template literal —
   the name must be followed by variable definitions (`($`), a directive, or a
   selection set starting with a field name — or in a precompiled
-  `OperationDefinition` document object. A standalone Source object's `body`
-  remains an operation candidate even when it has `locationOffset` metadata.
-  A graphql-tag `loc.source.body` copy is suppressed only when that source
-  belongs to a recovered document with the same operation and its containing
-  document, location and source have proven private metadata ownership. Writes,
-  escapes and classic-script global bindings retain the source observation.
-  Anonymous operations are not reported.
+  `OperationDefinition` document object. A graphql-tag `loc.source.body` copy is
+  not reported twice. Anonymous operations are not reported.
 
 Literal link options and precompiled document fields follow object property
 order: the final definition owns the key. A later spread, dynamic computed key,
@@ -327,25 +294,13 @@ suffix. Utility calls such as `useUtils().invoice.list.fetch()`, `useQueries`,
 and links whose callee was renamed by a minifier are not recognized.
 
 Each recovered bundle module retains the exact factory-source digest. A complete
-bounded AST also receives a `babel-ast-v3` structural fingerprint. It ignores
-ordinary identifier spellings while retaining literal and directive values,
-operators, fixed property names, and selected syntax flags such as computed
-keys, declaration kind, function async/generator state, update-expression
-prefix, method kind, and class static state. Local names used in computed keys
-remain rename-resistant; private member names are also ignored while their
-method kind and static state remain represented.
-
-This fingerprint is structural evidence for candidate matching, not proof that
-two modules behave equivalently. Its scope follows the AST facts listed above;
-unrepresented syntax can still collide. The exact source digest remains
-available to show byte-level change, and comparison reports content changes even
-when structural matching succeeds.
-
-Version comparison includes the algorithm in its structural matching key.
-Retained `babel-ast-v1` results can still match other v1 results, and v2 results
-can still match v2 results, but v1/v2 results cannot structurally match v3
-results. Other matching tiers remain available across algorithm versions.
-Re-analyze both snapshots to compare using the v3 rules.
+bounded AST also receives a `babel-ast-v2` structural fingerprint that ignores
+ordinary identifier names while retaining syntax, literals, operators, object
+keys, and member properties. Computed member identifiers retain their access
+syntax without treating a local variable's spelling as a fixed property; template
+literal contents remain part of the fingerprint. Version comparison keeps the
+algorithm in its matching key, so retained `babel-ast-v1` fingerprints cannot match
+these new fingerprints. Re-analyze both snapshots to compare their new structure.
 If fingerprint construction reaches its structural
 bound, the fingerprint is unavailable and its status is `truncated`; a bounded
 prefix is never presented as a complete stable fingerprint.
@@ -366,30 +321,11 @@ substitute version-dependent Electron defaults for omitted `webPreferences`.
 Unresolved option objects, bridge keys, API objects, and IPC channel expressions
 remain unknown and make coverage partial.
 
-BrowserWindow options and `webPreferences` can follow local `const` aliases
-whose initialization precedes the use. The shared lexical and mutation index
-checks the selected `webPreferences` path, so an unrelated `options.icon` write
-does not discard these facts. Reassignment, relevant writes, prior escapes,
-ambiguous initialization, and unresolved spreads remain unknown. The binding
-association is an inference: the window observation retains the constructor
-location and `resolution_sources` identifies the original object literals in
-the same artifact. Inline option syntax keeps its observed Evidence. This
-does not execute code or establish runtime configuration; popup overrides from
-`setWindowOpenHandler` are not covered by this constant-options resolution.
-
 Recognized literal module-table bootstraps also support bounded lexical
 substitution through module exports, import helper bodies, local wrapper calls,
 returned closures, object spreads, and callback parameters. Recovered Electron
 paths retain source ranges, module identities, literal channels and branch
-conditions as static candidates. A channel the IPC call site itself
-determines, such as a local constant, resolves that call's observation rather
-than adding a second one. A channel or registration handler supplied through
-a wrapper argument is a candidate beside the call's own unresolved
-observation, because callers outside the traced paths may pass other values.
-A wrapper call that is both its own entry and reached through another entry
-is recorded once when both paths find the same facts; calls that supply
-different handlers or channels stay distinct.
-Unknown spreads, reassigned bindings, accessors,
+conditions as static candidates. Unknown spreads, reassigned bindings, accessors,
 dynamic channels and unsupported syntax do not become exact implementations.
 This pass neither executes the bundle nor proves that runtime guards pass.
 An ambiguous or unresolved handler retains its channel registration but does
@@ -398,29 +334,6 @@ conditions retain both return branches, including fallthrough. Short-circuit
 selection distinguishes truthiness from nullishness; uncertain `??` paths
 retain a nullish guard rather than a falsy guard.
 
-Recognized module factories retain a separate initialization boundary for each
-reachable return and for fallthrough. A conditional early return does not hide
-later exports on the continuing path; exports and captured initializers after a
-definite exit remain unavailable. Fallthrough candidates retain their branch
-predicates. Exports shared by the complete set of proven exits also retain
-unconditional facts. Their shared view excludes later overwrites and bounds
-captured initializers by the earliest completion; branch-dependent facts keep
-their predicates. Incomplete or additionally guarded exit sets cannot use that
-proof. Completed factory control flow is reused within that analysis only.
-Guarded main-process registrations remain candidate paths even with empty
-callbacks; they do not become unconditional IPC summary facts.
-Factory guards read export writes at their source position. Destructured and
-spread snapshots retain their capture position rather than reading later writes.
-An unproven namespace read boundary remains unknown.
-Completed factory environments preserve their `exports` and `module.exports`
-alias identity when a namespace escapes through an export or returned closure.
-Synchronous helper calls retain the caller's factory activation and read point;
-lexical captures and executing callers remain separate facts.
-Async calls retain their truthy Promise identity until an explicit `await`;
-generator calls produce iterators without evaluating their bodies. Iterator
-advancement and Promise/iterator members remain explicitly unresolved. Awaited
-function values retain their source origins and captured initialization bounds.
-
 These paths appear as contextual `javascript-expression` nodes. An exact `api`
 seed such as `desktop.copy` can trace an exposed member through a unique IPC
 pairing to an external API call. `addListener` is normalized to `on`. Semantic
@@ -484,13 +397,10 @@ For `.node` bindings, member names mean “requested by JavaScript syntax.” A
 resolved add-on path does not convert them into verified native exports. Native
 symbol verification remains a separate deep-analysis claim.
 
-Exact endpoint values preserve useful local diagnostics, including query values
-and fragments, while removing URL username/password credentials when the value
-parses as a URL. When a recognized request target cannot be resolved exactly,
-the endpoint's partial resolution retains the original source expression with
-its call-site provenance. This does not establish that the request executed.
-Artifact paths, digests, parse locations, and analysis metadata remain
-actionable because REA is local-only.
+Endpoint observations preserve useful local diagnostics, including query values
+and fragments, while removing only URL username/password credentials. Artifact
+paths, digests, parse locations, and analysis metadata remain actionable
+because REA is local-only.
 
 ## Safety boundary
 
@@ -522,18 +432,7 @@ retained candidate strings and temporary canonical-key serialization. This is
 an in-memory semantic allocation bound independent of CLI or MCP transport
 budgets. Source literal bytes remain in the parsed source and artifact evidence;
 when a normalized semantic value exceeds the bound, its value is unknown and
-coverage is partial. Direct string literals, cooked templates without
-substitutions, and derived strings all use this normalization boundary. A
-single exact primitive is validated without allocating deduplication or sort
-state or serializing a canonical key. Configuration defaults use the same
-normalizer; limited defaults retain `value_resource_limit` and an anchored
-resource-limit unknown. Known null, false, zero, and empty-string defaults stay
-exact. This primitive-value bound does not truncate lookup identities such as
-source paths, field names or request endpoints. Full endpoint properties remain
-available for endpoint queries, tracing and comparison. Each analysis records encountered limit classifications independently of
-later projections: a selected healthy sibling can remain exact while whole-file
-coverage reports the encountered bound. Projection preserves limiting values
-from the shared property-slot owner. Expression
+coverage is partial. Expression
 evaluation and provenance walks stop after 256 nested levels. Union products
 and string lengths are checked before allocating combinations or concatenated
 strings. When a boundary is reached, the value stays unknown, semantic coverage
@@ -607,61 +506,20 @@ The default semantic capacities are 100000 nodes across the application and
 `--max-semantic-nodes-per-file`), each from 1 to 1000000. The per-file offer is
 also bounded by the remaining application capacity. Raising these controls does
 not bypass worker heap, execution deadline or parent result admission. Truncated
-coverage lists both effective ceilings, `max_semantic_nodes` and
-`max_semantic_nodes_per_file`. The limitation names only the ceiling that
-stopped retention. Omitted relationships remain unknown.
-
-Unknown records have independent defaults of 100000 across the application and
-20000 per source. Select `max_semantic_unknowns` and
-`max_semantic_unknowns_per_file` (CLI: `--max-semantic-unknowns` and
-`--max-semantic-unknowns-per-file`), each from 1 to 1000000. The parent offers the
-remaining capacity to the worker, and rejects excess records before adoption.
-Unknown admission happens before canonical identity and provenance construction.
-When capacity is exhausted, coverage is partial and truncated. Coverage lists
-both effective unknown ceilings, `max_semantic_unknowns` and
-`max_semantic_unknowns_per_file`. The limitation names only the ceiling that
-stopped retention. `coverage.omitted_unknown_occurrences` counts examined
-emission occurrences by family and reason, including repeated emissions. It does
-not claim distinct discarded identities or count frontiers in unexamined source.
-Omitted unknown provenance and IDs are not retained. Existing source, node,
-execution and memory limits continue to determine examined coverage. Raising only
-a node capacity does not raise the unknown capacity. Graphs without unknown
-omissions omit this optional coverage field, preserving their existing identities.
+coverage reports both effective node ceilings; omitted relationships remain
+unknown.
 
 While sources remain, the sequential worker reserves one next compact static
 checkpoint at its 8 MiB bound with the same 6x retention expansion used at
 admission. Earlier checkpoints are already charged to retained bytes; the
 remaining inventory does not multiply the reserve. Streamed file transfers keep the default 512 MiB
 allowance, and can grow with the parent's offered retention budget (8x byte
-expansion), up to 2 GiB. Individual records remain bounded to 8 MiB. The 8 MiB
-record ceiling and the 2 GiB file maximum have no runtime override, and raising
-`max_heap_mb` does not raise them. The effective file ceiling follows the
-parent's offered result budget. On Node, a larger CLI/MCP process heap
-(`NODE_OPTIONS`, for example `--max-old-space-size=<MiB>`, after restarting that
-process) can raise it up to 2 GiB. Selecting fewer `source_paths` can also
-raise that effective allowance, because the reserve for remaining sources and
-earlier retained results reduce the offered budget. Neither change raises the
-record ceiling or the 2 GiB maximum. The parent
+expansion), up to 2 GiB. Individual records remain bounded to 8 MiB. The parent
 still independently checks actual bytes, record overhead, digests and source
 identities before adopting results.
 
 A source that exhausts the analyzer heap does not terminate the CLI/MCP
-process. On Node, the failure names `max_heap_mb` (CLI `--max-heap-mb`), the
-effective mebibytes, the inclusive range 128 to 16384, and the 1024 MiB
-default. A changed value applies on the next analysis, which starts a new
-worker. It does not change a worker that is already running and does not
-require restarting the REA server. On Bun, the same heap-exhaustion diagnostic
-is not attributed to that V8 old-space limit, because Bun ignores the flag.
-Raising `max_heap_mb` does not raise the parent result budget,
-the transfer record ceiling, the 2 GiB transfer file maximum, the CLI/MCP
-process heap, or fixed parser limits. The parent result budget follows that
-process heap. On Node, set `NODE_OPTIONS` (for example `--max-old-space-size=<MiB>`)
-in the environment that starts the CLI or MCP server, then restart that
-process, to raise the parent heap and the result budget. A completed static
-checkpoint that does not fit the parent's remaining heap names that parent
-process heap. Increasing `max_heap_mb` does not raise it. On Node, the same
-`NODE_OPTIONS` restart can raise the parent heap and admit the checkpoint.
-Completed static facts are retained, other files can still be analyzed,
+process. Completed static facts are retained, other files can still be analyzed,
 and unexamined semantic relationships remain explicit unknowns. The parent
 also checks transfer expansion and accumulated results against its remaining
 heap before accepting semantic facts. A resource-limited result has partial

docs/javascript-recovery.md

@@ -129,20 +129,12 @@ equivalence remain unknown. No network fetching occurs.
 
 ## Resource policy and verification
 
-Each operation uses one worker, a 1 GiB address-space ceiling and a 120000 ms
-deadline. That deadline has no runtime override: raising `analysis_timeout_ms`
-or `max_heap_mb` does not raise it. An unchanged retry may hit the deadline
-again. The operation accepts up to 64 MiB of total
-input across all selected files and 128 MiB/10000 entries of staged output,
-with 8 MiB per diagnostic/report stream. A `provenance.json` over that report
-allowance names the fixed limit: this release has no runtime override, and
-raising `max_heap_mb` or `analysis_timeout_ms` does not raise it. Malformed
-reports stay distinct from that size refusal. Exceeding a limit is an explicit
-failure with rollback. Selected inputs beyond the total input allowance return a
-non-retryable `resource_constraint` with `resource: "file-size"` and
-`reported_limits.maximum_input_bytes`/`remaining_input_bytes`; input that is not
-valid UTF-8 is an `invalid_format` request issue. These limits apply per
-operation and do not claim aggregate host containment across concurrent callers.
+Each operation uses one worker, a 1 GiB address-space ceiling and a 120-second
+deadline; it accepts up to 64 MiB of total input across all selected files and
+128 MiB/10000 entries of staged
+output, with 8 MiB per diagnostic/report stream. Exceeding a limit is an explicit
+failure with rollback. These limits apply per operation and do not claim aggregate
+host containment across concurrent callers.
 
 See [testing.md](testing.md#javascript-source-recovery) for the focused real
 Wakaru CLI/MCP lane and its source-owned compiler fixtures. Other host platforms

docs/javascript-runtime-observation.md

@@ -95,11 +95,6 @@ pauses or resumes execution, calls `Runtime.runIfWaitingForDebugger`, launches
 the target, instruments JavaScript, or invokes Electron APIs. Closing a call
 closes only REA's WebSocket.
 
-Each WebSocket handshake and command response has its own 20-second deadline,
-separate from the caller-selected observation window. A stalled handshake or
-command reports `provider_timeout` and retains observations already received;
-caller cancellation still reports cancellation.
-
 The direct observations are:
 
 - `Debugger.scriptParsed`, establishing that a bounded script location was
@@ -109,9 +104,7 @@ The direct observations are:
 - `Runtime.executionContextCreated`,
   `Runtime.executionContextDestroyed`, and
   `Runtime.executionContextsCleared`, establishing context lifecycle within
-  the capture window. A created or destroyed event whose context ID is
-  missing or not a safe integer adds no context record; it is retained only
-  as a count reported in `unknowns`.
+  the capture window.
 
 The Inspector protocol does not directly expose require/import caller edges,
 EventEmitter emissions or listener invocation, Electron IPC messages or
@@ -152,15 +145,6 @@ and uncollected scripts, but scripts collected before attachment may be
 missing. Absence from the observation window never proves that a script or
 behavior does not occur.
 
-Cancellation stops new target-file authorization after the current filesystem
-operation settles. Cancellation diagnostics retain the examined target prefix;
-unexamined targets remain unknown. Observation cancellation keeps its original
-reason and any completed Evidence. Finalization waits for REA's bounded socket
-close (up to two seconds for graceful and forced confirmation). A failed close
-retains its exact transport owner and blocks replacement connections until
-cleanup succeeds; CLI finalization and MCP shutdown also retry retained cleanup.
-Closing REA's connection does not stop the caller-owned runtime.
-
 ## Static correlation
 
 Pass the resulting observation Evidence and an

docs/javascript-runtime-reconciliation.md

@@ -91,20 +91,17 @@ nodes. REA evaluates compatible static candidates conservatively:
 
 1. A captured-source SHA-256 plus one matching mapped location yields
    a content-and-location match.
-2. When no static candidate exists at a mapped location, one unique exact
-   content digest can match. Whole-asset digests and reconstructed module-factory source
+2. One unique exact content digest can match even when no location mapping is
+   available. Whole-asset digests and reconstructed module-factory source
    digests remain distinguishable in the reported basis.
 3. Without captured bytes, one unique mapped artifact path can produce a
    medium-confidence location match.
 4. Multiple candidates remain `ambiguous`; no `observed_as` edge is emitted.
-   With captured source and mapped candidates, only mapped content matches
-   qualify; unrelated content matches elsewhere are excluded.
    `candidate_static_count` reports the full qualified layer/node count, and
    `candidate_static_nodes` includes every unique candidate reference.
 5. If captured bytes disagree with the static candidate at the mapped path,
-   the result is an explicit mismatch. An equal digest elsewhere cannot hide
-   that disagreement. If a mapped candidate's digest is unavailable and no
-   mapped content match is known, the comparison remains `unknown`.
+   the result is an explicit mismatch. A path never overrides a digest
+   disagreement.
 6. Missing authorization mappings and incomplete or truncated input coverage
    remain unknown or truncated rather than becoming absence claims.
 

docs/jeb-analysis.md

@@ -8,16 +8,7 @@ Start a JEB client that serves MCP and point REA at it:
 
 - Default endpoint: `http://127.0.0.1:8425/mcp`. Override with `REA_JEB_MCP_URL` (absolute `http`/`https` URL with literal host `127.0.0.1` or `[::1]`; redirects, remote hosts, credentials, query strings, and fragments are rejected rather than silently dropped).
 - In the JEB GUI client, start the MCP server from the _File_ menu (or via the VIBRE assistant).
-- Headless, the official Linux CE build `5.48.0.202610071539` supports `-c --mcp`. From the JEB installation directory, select JDK 21 or newer through `JAVA_HOME`, choose your target and bind explicitly to loopback:
-
-  ```sh
-  "$JAVA_HOME/bin/java" -jar bin/app/jeb.jar -c --mcp --interface=127.0.0.1 \
-    --port=8425 --infile=/absolute/path/to/target
-  ```
-
-  Complete the vendor's first-use EULA and license-key activation when prompted. The Linux audit used an isolated installation, a 1536 MiB Java heap and one active processor inside a separately bounded process family; JVM heap limits alone do not bound the whole family.
-
-- JEB's documented programmatic route (`JebMcpServerInstance` from the JEB API) remains an alternative. The earlier licensed 5.48 headless verification used that route because its CLI did not accept `--mcp`. Check your installed build's `-c --help` and live tool catalog; the version number alone does not establish the launcher options or supported operations.
+- Headless, use JEB's documented programmatic route (`JebMcpServerInstance` from the JEB API) with the JEB client on your classpath; JEB 5.48's `-c` headless mode does not accept `--mcp` directly.
 
 For setup registration, set `REA_JEB_MCP_URL` in the REA process environment
 before running `rea setup`. The approved setup plan preserves the exact selected
@@ -28,21 +19,19 @@ JEB service is reachable or that a project is open; use the existing
 MCP `binary_session` probes the live JEB service and its advertised tool catalog.
 Availability is reported per operation: a reachable headless client can support
 inspection and decompilation while refusing `open_jeb_project`. Catalog discovery
-is one deadline across connection and pagination; a responsive server cannot keep
-discovery running indefinitely by returning more pages.
+uses one 60-second deadline across connection and pagination; a responsive server
+cannot keep discovery running indefinitely by returning more pages.
 
-Catalog discovery and each `tools/call` share `REA_JEB_MCP_TIMEOUT_MS`. Set it
-in REA's launch environment to an integer from 1 to 2147483647 milliseconds,
-for example `REA_JEB_MCP_TIMEOUT_MS=300000` for a five-minute budget. Omitted
-means the pinned MCP client SDK default of 60000 ms (`@modelcontextprotocol/client`
-2.3.1). Restart REA and reconnect to apply a change. Raising the setting raises
-both phases. It does not make one end-to-end deadline across a whole CLI or MCP
-operation: discovery and each `tools/call` each get that budget. A request that
-reaches its budget returns a typed timeout naming the phase and the effective
-milliseconds, while caller cancellation remains a cancellation. Allow execution,
-cleanup, and delivery headroom in the outer MCP client deadline.
+Each upstream tool call has an absolute 60-second request deadline by default.
+Set `REA_JEB_MCP_TIMEOUT_MS` to a positive decimal number of milliseconds to
+select a different per-request budget, for example `REA_JEB_MCP_TIMEOUT_MS=300000`
+for a five-minute decompilation. This budget starts after discovery and applies
+to each individual `tools/call`; it does not extend the separate catalog deadline
+or establish one end-to-end deadline across a whole CLI or MCP operation. A
+request that reaches its budget returns a typed timeout, while caller
+cancellation remains a cancellation.
 
-Earlier verification used JEB 5.48.0 (Linux x64, licensed build) serving `jeb-mcp-server` 1.3.0 over streamable HTTP. The official Linux x64 CE build `5.48.0.202610071539` was also verified through real CLI and production stdio MCP native-code workflows; see the [Linux CE audit](../experiments/analysis-efficiency/jeb-linux-native.md) for measurements and limits. CE verification does not establish licensed/Demo Android decompilation or GUI behavior.
+Verified against JEB 5.48.0 (Linux x64, licensed build) serving `jeb-mcp-server` 1.3.0 over streamable HTTP.
 
 ## Operations
 
@@ -53,18 +42,16 @@ Earlier verification used JEB 5.48.0 (Linux x64, licensed build) serving `jeb-mc
 | `list_jeb_units` / `list-jeb-units`         | Page units by stable path and type (`filter`, `parent-unit-path`, `index`, `count`)                                             |
 | `decompile_jeb_item` / `decompile-jeb-item` | Decompile one type or method to engine pseudo-code                                                                              |
 
-All four preserve target-file bytes. `open_jeb_project` selects or creates an engine-side project; analysis queries can populate computed analysis within it. Evidence records the endpoint, caller-selected parameters, and available engine-reported digests. Mutation workflows the engine also offers (renames, comments, `save_project`, `close_project`) are intentionally not exposed yet.
+All four are read-only with respect to the target file; only `open_jeb_project` changes engine-side project state, and Evidence records the endpoint, the caller-selected parameters, and the engine-reported digests. Mutation workflows the engine also offers (renames, comments, `save_project`, `close_project`) are intentionally not exposed yet.
 
-**Engine coverage note:** The earlier licensed 5.48.0 headless verification did not advertise `open_project`; it selected the target when the engine client started. For that build, use `--infile` on the programmatic launcher or open the file in the GUI. The audited CE headless catalog also omitted `open_project`; the verified CLI route above selects its input at startup. Use `binary_session` to inspect the current engine's advertised operations. REA preserves an unavailable tool's refusal; `open_jeb_project` requires an engine that advertises `open_project`. The CE audit does not establish GUI project-opening support.
+**Engine coverage note (verified):** JEB 5.48.0 headless MCP instances do not advertise `open_project` — the target must be selected when the engine client starts (`--infile` on the programmatic launcher, or the GUI's file opening). REA preserves that refusal with the engine's reason instead of failing silently; `open_jeb_project` completes only against engine builds that advertise the tool, such as GUI clients.
 
 ## Semantics
 
 - Paths in `open_jeb_project` are resolved by the JEB process, not by REA; REA does not require the artifact to exist locally.
 - The engine caps `list_units` pages at 100; a full page is reported as `coverage: "partial"` because more units may exist. An empty remainder is `complete` only when fewer units than requested were returned.
 - When `decompile_jeb_item` omits `unit_path`, the engine implicitly selects the project's first code unit; REA reports `unit_path: null` and a limitation instead of guessing the effective unit.
-- `item_address` is a JEB code-item reference, such as a value returned by the engine's `list_code_items`. Preserve that representation and select its code unit explicitly. For the audited CE SQLite unit, the exported method reference was `sqlite3_libversion_number`; using its raw ELF symbol address did not produce a successful decompilation. File offsets, ELF virtual addresses and engine item references have different semantics. REA currently exposes unit listing, while code-item discovery remains an upstream JEB operation.
 - Engine refusals (`success: false` envelopes) are preserved as unsupported-target errors carrying the engine's own message, for example a nonexistent item address.
-- Successfully parsed client information is reused for the lifetime of the MCP connection, including when the engine omits its version. Explicit client inspection and availability probes refresh it.
 - An unreachable endpoint is a provider-availability failure with recovery guidance; REA does not retry or spawn the engine.
 
 Real-engine verification lives in the JEB lane described in [testing.md](testing.md); mock transport tests do not establish real-engine compatibility.

docs/kuna-provider.md

@@ -1,141 +0,0 @@
-# Kuna provider
-
-[Kuna](https://github.com/Noelo-Lab/kuna) is an Apache-2.0 decompiler distributed as one `kuna` executable. REA uses a `kuna` you supply. It does not download, install, update or bundle Kuna. REA verified this provider with Kuna 1.833; it accepts other releases and reports them as unverified in `rea doctor` and in each analysis profile.
-
-Kuna is static: it reads the selected image and never executes it.
-
-## Configure
-
-```bash
-export REA_KUNA_COMMAND=/absolute/path/to/kuna
-rea doctor --provider kuna
-```
-
-Select it explicitly with `--provider kuna`, MCP's `open_binary.provider_id: "kuna"`, or `REA_ANALYSIS_PROVIDER=kuna`. With Kuna and another provider configured for the same target, `auto` reports `ambiguous` instead of choosing one.
-
-Ordinary readiness cancellation returns `cancelled` (CLI SIGINT/SIGTERM exits
-130/143); an earlier recorded timeout or physical failure keeps its diagnostic.
-Completed version, hash and script observations remain in `kuna_installation`
-with `status: "partial"` and `completed_hash` when available. Typed errors carry
-this in `details.diagnostics`; doctor cleanup checks carry it in their `details`.
-Omitted fields remain unobserved; availability remains unknown until readiness
-completes. Cleanup retries keep both the observations and the exact file owner.
-
-| Setting                       | Default                                                                                                                                 | Meaning                                                                                                                                                                                  |
-| ----------------------------- | --------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `REA_KUNA_COMMAND`            | none (required)                                                                                                                         | Absolute path of the `kuna` executable.                                                                                                                                                  |
-| `REA_KUNA_CACHE_DIR`          | `~/Library/Caches/rea/kuna` (macOS), `$XDG_CACHE_HOME/rea/kuna` (Linux; `~/.cache/rea/kuna` when `XDG_CACHE_HOME` is unset or relative) | Absolute directory REA owns for project exports. Kuna's own spec cache also lives here, not in your Kuna cache.                                                                          |
-| `REA_KUNA_CACHE_MAX_BYTES`    | 4 GiB                                                                                                                                   | Size cap; least recently used exports are evicted above it.                                                                                                                              |
-| `REA_KUNA_PROJECT_TIMEOUT_MS` | 30 minutes                                                                                                                              | Deadline for whole-program inventory/export, reference and string scans.                                                                                                                 |
-| `REA_KUNA_TIMEOUT_MS`         | 120 s                                                                                                                                   | Deadline for one single-function decompile, and for the inventory run REA makes when the export ends without one.                                                                        |
-| `REA_KUNA_JOBS`               | 1                                                                                                                                       | `decompile-project --jobs`. 1 is Kuna's reference answer; more jobs finish sooner but lose callee-first prototypes, and change about 40–60% of function bodies on the measured binaries. |
-
-A single-function decompile, inventory, string, graph or xref run that exceeds its deadline fails as `provider_timeout`, naming the setting that owns the deadline and that raising it takes a restart. A project export that exceeds `REA_KUNA_PROJECT_TIMEOUT_MS` is an export failure instead: requests that need the export report `capability_unavailable` with the export's own retry guidance.
-
-Windows is not supported yet. Supported targets are ELF and thin Mach-O executables for x86-64, AArch64 and ARM; PE and universal Mach-O are rejected with a typed reason.
-
-## What Kuna answers
-
-| Tool                                                        | Source                                                                                                                           |
-| ----------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------- |
-| `list_procedures`, `search_procedures`, `procedure_address` | Kuna's callable inventory (`kuna functions --json`), including import slots it does not decompile                                |
-| `address_name`                                              | Function entries, then the data labels Kuna's export assigns                                                                     |
-| `procedure_pseudo_code`, `batch_decompile`                  | The project export, or a single-function run while the export builds                                                             |
-| `procedure_assembly`                                        | The project export's labeled listing                                                                                             |
-| `procedure_callers`, `procedure_callees`                    | Call-kind edges from a lazy, body-free Kuna graph; synthetic import nodes are accepted by address                                |
-| `list_strings`, `search_strings`                            | Typed string candidates from one cached, reference-free scan; exact-address, literal and ECMAScript regex selection              |
-| `xrefs`                                                     | Exact-address incoming reference sites, with forwarding aliases filtered explicitly                                              |
-| `analyze_function`                                          | Pseudocode and assembly from the export, plus call relationships; typed references, comments, strings and CFG remain unavailable |
-
-Typed procedure references, basic blocks, raw-memory tools, annotations and type recovery are not available from this provider. Use another provider for those operations.
-
-## How answers are produced
-
-The first text or assembly request in a session looks for this target's export in the cache. `list_documents` reads the selected path without initializing analysis. Inventory, function lookup, string queries, call relationships and xrefs do not start a C export. A data-name lookup starts it only when the address is absent from the function inventory. The export is keyed by the target's SHA-256, the Kuna executable's SHA-256, its version and `--jobs`.
-
-- **Warm cache:** analysis reads reuse the verified export. A fresh server verifies its file digests once, even for concurrent first requests; that cost scales with export size.
-- **Cold cache:**
-  - REA starts `kuna decompile-project` in the background on a private copy of the target.
-  - Meanwhile, pseudocode comes from one `kuna decompile --addr` run. Name and address lookups, and listings, use the inventory the export takes with `kuna functions --json` before it decompiles. The session runs `kuna functions` itself, under `REA_KUNA_TIMEOUT_MS`, only when no export is building (an inventory-only request does not start one) or the export ends without an inventory.
-  - Requests for the same function share one run; it stops when its last waiting request is cancelled. Each run analyzes the whole image again in its own process, so one REA process runs at most as many at once as the host has cores beyond `REA_KUNA_JOBS` (at least one). Further requests wait in order, and a waiting request is answered from the export if it finishes first. A run whose stop REA cannot prove keeps its slot until `close_binary` proves it stopped.
-  - The session keeps each completed single-function text, up to 16 MiB in all with the least recently used dropped first, and answers repeats from it until the export can. After a failed export that lasts for the session.
-  - Assembly and data names wait for the export; progress notifications report the wait every ten seconds. A session does not rebuild a failed export: requests that need it fail with `retryable: false`, the export's failure, its captured Kuna output and what to change before reopening the target. A setting such as `REA_KUNA_PROJECT_TIMEOUT_MS` or `REA_KUNA_JOBS` is read when REA starts, so changing it also needs a restart. Pseudocode keeps using single-function runs.
-  - A single-function answer says so in its limitations. It lacks the export's whole-program prototypes, so a later request can return different text for the same function.
-
-Pseudocode, assembly, `analyze_function` and data-name answers record where their text came from in `raw_result.source`: `single-function`, or `project-export` with the cache directory. `procedure_pseudo_code` and `procedure_assembly` answers from the export also name the file, byte span and the file's SHA-256. Combined `analyze_function` answers retain both facet records in `raw_result.source.files`, each with its file, digest and byte span. Both texts come from one export; losing that project retries the complete report. Listings and procedure lookups carry no `raw_result`. Agents can open or search the export's `.c` and `.asm` there directly when that is cheaper than calling a tool per function. Text read that way is target-derived, like any decompiler output, but it bypasses the untrusted-content marker that REA's tool results carry.
-
-The background export belongs to the session. `close_binary`, or the end of a CLI command, cancels it unless another session still waits for it. A one-shot CLI decompile therefore answers from a single-function run; any request that needs the export, such as `procedure_assembly` or `analyze_function`, keeps it.
-
-The assembly label index is scanned once per export reader. Cancelling a request stops its wait without interrupting other readers; closing the session aborts and drains the shared scan before releasing its files.
-
-Regex procedure and string search uses ECMAScript Unicode matching in a cancellable worker with a five-second matching deadline and a worker old-generation heap. Literal matching remains the default. Cancellation or a matching deadline leaves the session available. This release has no runtime override for that deadline. The worker requests 128 MiB. A positive Node.js `--max-old-space-size` on the process that starts REA, including `NODE_OPTIONS`, overrides that request and sets the effective heap. `--max-old-space-size-percentage` takes precedence over that flag in either order. REA does not turn the percentage into a MiB, so the effective heap stays unestablished instead of the 128 MiB request or the absolute flag. The reported `NODE_OPTIONS` value is the process initial environment when that block can be read. A later edit to the environment is not the value Node applied, and an unreadable initial value leaves the effective heap unestablished. The launch Node options are the initial command line on Linux when that buffer still has a program entry, not a later edit to `process.execArgv`. A preload can clear that array after V8 has applied the flags. Setting `process.title` or `--title` overwrites the command line, so a buffer without a program entry leaves the effective heap unestablished. `--env-file` or `--env-file-if-exists` can supply `NODE_OPTIONS` when the initial environment has none. That file is not part of the initial environment block, so the effective heap stays unestablished instead of the 128 MiB request. An initial `NODE_OPTIONS` is still used, because Node does not let the file replace it. A positive `--max-heap-size`, including the underscore form and launch `NODE_OPTIONS` on Node versions that allow it, sets the total heap rather than the old generation and can be lower than the 128 MiB request. The effective old generation stays unestablished while that value is in effect. A zero or empty value clears it. `--experimental-config-file` or `--experimental-default-config-file` can set `nodeOptions`, including a heap percentage, from a file that is not read back. The effective heap stays unestablished when either flag is present, including when an absolute `--max-old-space-size` is also on the command line or in the recovered `NODE_OPTIONS`. Node accepts the config path as `=` or the next argument.
-
-Single-function subprocess output and each cached source facet share a 16 MiB buffered-text capacity. Cached spans are checked before allocation; larger text remains in the local export and the error identifies the file and range. `analyze_function` initially returns the complete dossier, which can still be large; later retained views do not remove that first transfer. Prefer the individual text tools for a focused question.
-
-## Strings
-
-`list_strings` and `search_strings` share one lazy `kuna strings --json --encoding all --min-length 5 --termination any --no-xrefs` scan of the digest-checked private input. Skipping references avoids program lifting, a call graph and a C export. REA validates the input, scan policy, every row and the total before caching any facts. Encoding, character count, byte length and terminator facts must agree; supplementary UTF-8 characters count as Unicode scalars. Malformed output is an error, not an empty search. REA parses the JSON as Kuna writes it instead of buffering it, so the scan has no fixed size: Kuna writes about 290 bytes per row, 31 MB for a 20 MB Ghostty binary and 179 MB (611k rows) for an arm64 Firefox `XUL`. Rows are validated one at a time, and the first contradiction stops Kuna. Text REA does not keep is dropped unassembled; kept text and retained rows are admitted against the REA process's live heap headroom as they arrive; a refusal is a `memory` resource constraint with `retryable: false`, and closing other targets or starting REA with a larger Node.js heap makes room. String scans use the whole-program `REA_KUNA_PROJECT_TIMEOUT_MS` deadline; `REA_KUNA_TIMEOUT_MS` applies to single-function decompilation. The parsed inventory belongs to one selected target/executable profile and expires on session close; Kuna diagnostics beyond their 8 MiB buffer are retained as a failure until close, while other failures are not cached.
-
-Results keep exact u64 virtual addresses, decoded text, native encoding, terminator status and byte length including any terminator. Kuna scans mapped sections or segments for runs of at least five characters; unterminated fragments can include instruction bytes. `all` includes ASCII, UTF-8 and the engine's Latin-range UTF-16LE reading. Other text, including short strings, non-Latin wide text and UTF-16BE, can remain undiscovered. An empty result does not prove absence.
-
-Use `search_strings` for the matching rows or `list_strings` with an exact address for that location. The validated inventory is sorted by numeric address and encoding. Once cached, exact-address reads use binary search and return every encoding at that address without scanning the full inventory or retaining another lookup index. Literal and regex matching run in REA, preserving the existing case and ECMAScript Unicode semantics instead of substituting Kuna's different regex dialect. Procedure and string regex queries share one worker slot per session. Input projections are materialized only after admission, so queued queries retain no per-query inventory arrays. Close cancels and drains matching. Native metadata queries also share one admission slot, including references; a failed stop retains admission until cleanup is proven.
-
-`raw_result.strings` reports the source JSON digest/size, scanned scope, extraction policy, complete inventory count and selected count without copying unrequested text into the answer. Omit the address from `list_strings` to retrieve the complete inventory as Evidence; normal session retention and bundle export apply, including transport-capacity errors for oversized inline replies. These operations preserve their complete-result contracts and do not add paging. Function-referenced string facets in `analyze_function` remain unavailable; call `xrefs` explicitly when references to one returned string are needed.
-
-## Calls and references
-
-The first call query runs `kuna decompile-graph --functions ''`, admitting no C or assembly bodies. One validated graph and forward/reverse indexes serve later call queries and existing `get_call_graph` / `trace_call_path` workflows. Numeric u64 addresses are parsed from their original JSON tokens. Only `call` edges become callers/callees; jumps and data references retain their distinct meaning. Graph counts, edge endpoints and ordering are validated before any relationship is returned. A forwarding address may be an instruction inside a function, so it is retained separately and never promoted to a function node or call edge. Reported indirect calls make affected relationship coverage partial; no target is invented for them.
-
-`xrefs` runs native `xrefs --to ADDRESS --json` on demand. Kuna unifies forwarding aliases and suppresses edges internal to their class; REA filters to the requested address and records the excluded-row count. Duplicate source sites appear once. An empty result cannot establish the absence of references. Addresses are explicit u64 values or exact, unambiguous procedure names; Kuna has no cursor.
-
-REA parses the graph as Kuna writes it, like the string scan, so the graph has no fixed size: a 53 MB Raycast binary produces 157 MB (180k functions, 773k edges), which REA retains in about 93 MB after a whole-program walk of about a minute. Unrequested bodies are refused before any of their text is assembled, and edges are indexed as they arrive, so retained rows and their indexes are admitted against live heap headroom. Xref JSON admits at most 16 MiB before parsing. Output or Kuna diagnostics beyond a buffer are reported as a `memory` resource constraint with `retryable: false`, because the same target and executable produce the same output. The session remembers such a graph failure, so later call queries fail at once instead of repeating the whole-program walk. The graph is cached for the selected target and executable profile within one session. Xref reuse is an LRU charged by source bytes plus metadata, limited to 16 MiB and 128 entries; at most eight distinct native xref queries may be pending. Reference commands run one at a time per session and share the provider's foreground budget with single-function decompiles. An unproven process stop retains its admission slots until cleanup succeeds. Concurrent callers share work, individual cancellation releases only that waiter, and the last departing waiter cancels its producer and receives any unproven cleanup. Session close aborts and drains producers, releases parsed caches and retries any retained process/file cleanup.
-
-Evidence includes only selected addresses or dossier neighbors, the producing JSON's SHA-256/byte count, coverage and relevant function facts; unrequested program-wide JSON and instruction text are omitted. Reference caches are in memory and expire on close: a fresh CLI process or MCP server rebuilds them. A first call query therefore costs a whole-program reference walk even when a C export is warm. These operations do not establish full Ghidra/IDA feature parity.
-
-Failures from shared installation or inventory work identify the operation the
-caller requested. `diagnostics.producer_operation` retains the internal producer
-name when it differs. Caller-specific failures keep the producer's typed outcome,
-captured output, partial facts and live cleanup dependencies; cleanup retry
-updates every projection rather than preserving an independent stale marker.
-Installation acquisition is shared, with independently cancellable caller waits.
-The final departing caller stops the probe and joins its cleanup; session close
-also stops and joins acquisition. A cleanly cancelled acquisition can be retried,
-while a retained cleanup failure blocks replacement until its owner is closed.
-Shared string and reference queries preserve caller cancellation reasons and
-join the final departing caller's command cleanup. A command cleanup error keeps
-its typed primary failure and captured output. Its live resource list follows
-both process and workspace ownership: proving process exit does not prove that
-the private workspace was removed, and retry updates earlier caller errors.
-If workspace setup fails, an unsuccessful rollback retains the original target
-or read failure together with its cleanup owner. Replacement stays blocked until
-that rollback is resolved; a clean rollback permits another setup attempt.
-
-## Provenance and limitations
-
-- Addresses and bytes are Kuna's observations of the image. Procedure entries and extents are its derivations: extents are upper bounds clipped at the next entry, and Kuna can split one function at an entry its own analysis infers. Pseudocode is its reconstruction, never original source.
-- Pseudocode and assembly are exact Kuna text; text from Kuna and from another provider is not comparable as equal or different.
-- Results are re-read rather than replayed from REA's analysis snapshots, because a cold answer can differ from the export's.
-
-## Cache ownership
-
-REA writes Kuna's exports only inside `REA_KUNA_CACHE_DIR`:
-
-- `projects/<key>/` holds published, immutable exports with a manifest of file digests.
-- `staging/` holds builds whose processes may still be live.
-- `trash/` holds retired builds and evicted exports awaiting removal.
-- `home/` is Kuna's HOME.
-
-Builds publish by one rename, so a reader sees a complete export or none. A session keeps the export it uses from eviction only within its own REA process. If another REA process sharing the cache evicts it, the session rebuilds it; meanwhile pseudocode falls back to single-function runs. A damaged or edited export is removed and rebuilt. Staging moves to `trash/` for removal only after REA proves its Kuna process stopped. Staging of a process it cannot prove stopped is never swept; REA keeps it owned, retries the stop on `close_binary`, and reports it until the stop is proven. Failed file removal also stays bound to its export and is retried by `close_binary`; closing does not report success while that cleanup remains. `rea doctor --provider kuna` reports the cache directory without creating it.
-
-## Verify with a real Kuna
-
-```bash
-REA_KUNA_COMMAND=/absolute/path/to/kuna npm run verify:kuna
-# Compare with Ghidra on caller-built binaries
-REA_KUNA_COMMAND=/absolute/path/to/kuna GHIDRA_INSTALL_DIR=/absolute/path/to/ghidra \
-  npm run verify:kuna -- --targets DIR --functions inflate,crc32 --compare-ghidra
-```
-
-The lane compiles a small source-owned fixture with the host C compiler and verifies the MCP workflow end to end. `--targets DIR --functions a,b` adds caller-built binaries. `--compare-ghidra` (with `GHIDRA_INSTALL_DIR`) runs those same functions through Ghidra; it requires `--targets` and `--functions` and refuses empty matrices or requested function names missing from every target. See [testing](testing.md#kuna-lane) for coverage.
-
-Failed runs also report process-lineage evidence and exit unsuccessfully. If provider or transport cleanup is unconfirmed, the report says `cleanup: "incomplete"` and records `retained_workspace`; that directory is preserved for investigation and cleanup retries.

docs/managed-code-analysis.md

@@ -85,7 +85,7 @@ rejects selected summary before analysis; complete delivery remains available.
 
 Complete `inspect_managed_members` delivery always includes the assembly-wide
 `member_refs` and `exported_types`, which `type_names` does not narrow, so even
-one selected or unmatched type can return megabytes. In MCP, select
+one selected or unmatched type can return megabytes. Select
 `{"path":"/absolute/path/Assembly.dll","type_names":["Namespace.Type"],"detail":"summary"}`
 to keep the complete source in the session and receive identity, metadata
 status, the selection with its unmatched names, coverage/issues, the separate
@@ -115,58 +115,13 @@ literal pool's own coverage. Older Evidence that never examined exported types
 or user strings reports a null count and refuses those pages rather than
 returning an empty one.
 
-#### CLI summary and saved member rows
-
-The CLI accepts the same `complete` and `summary` detail choices. Omitted or
-`--detail complete` returns complete Evidence. To receive a summary, choose a
-new Evidence bundle destination so its original complete parent remains
-available after the command exits:
-
-```bash
-rea inspect-managed-members /absolute/path/Assembly.dll --type Namespace.Type \
-  --detail summary --evidence-bundle /absolute/path/evidence/members.json --json
-```
-
-`--evidence-bundle` writes the complete original Evidence in REA's canonical
-bundle format. Its parent directory must exist, and it never replaces an
-existing path. Relative paths resolve against the command's working directory.
-The option also works with complete delivery when a saved bundle is useful.
-Summary without a destination is rejected before analysis. A publication failure
-returns a typed error with the completed Evidence under
-`details.partial_observation`; it does not report successful summary delivery.
-Cancellation before publication prevents the new output. Once atomic
-publication has started, it can complete despite cancellation; a cancelled
-delivery then retains the committed path and byte count under
-`details.diagnostics.evidence_bundle`.
-
-Copy `normalized_result.parent_evidence_id` from the summary into the
-`source.evidence_id` field of the `managed-members` request above, then save that
-small request as `members-page.json` and run:
-
-```bash
-rea inspect-analysis-view /absolute/path/evidence/members-page.json \
-  --evidence-bundle /absolute/path/evidence/members.json --json
-```
-
-The view command authenticates the selected bundle and resolves that exact
-parent ID. It does not reopen the assembly, so the original target may have
-been moved or removed. Subsequent calls can select another collection or use
-the returned `coverage.next_offset` to continue the same collection. An inline
-source already includes its parent and cannot also select `--evidence-bundle`.
-
-Summary changes delivery, while type selection still controls decoding and the
-same inspection resource limits apply. Each separate CLI page reads and
-authenticates the saved bundle; the full source is retained on disk.
-
 ## Shipped scope
 
 The canonical parser admits PE/CLI bytes and their metadata/CIL without loading
 an assembly. It reports observed implementation markers and unavailable facts;
-it does not unpack .NET single-file hosts or infer a NativeAOT identity from an
-ordinary native PE. It does not decode IL2CPP; use
-[IL2CPP metadata](il2cpp-metadata.md) for the image, type and method names in a
-Unity `global-metadata.dat`. Inputs without admitted CLI metadata do not
-become managed assemblies through naming or routing guesses.
+it does not unpack .NET single-file hosts, decode IL2CPP metadata, or infer a
+NativeAOT identity from an ordinary native PE. Inputs without admitted CLI
+metadata do not become managed assemblies through naming or routing guesses.
 Inspect separately obtained components explicitly and preserve their identities.
 
 A valid implementation marker establishes a candidate native boundary, not
@@ -397,7 +352,7 @@ install it or its toolchain. The [NativeAOT guide](ghidra-nativeaot.md) defines
 these routes, their layout/host restrictions, derived-memory provenance, and
 verification coverage.
 
-REA's experimental Windows Ghidra boundary admits native x86, x86-64, ARMNT (Thumb-2) and ARM64 PE
+REA's experimental Windows Ghidra boundary admits native x86 and x86-64 PE
 applications and DLLs for static analysis. For x64 PE NativeAOT, the read-only
 parser also runs there; the [NativeAOT guide](ghidra-nativeaot.md) lists what a
 Windows host covers.
@@ -665,9 +620,6 @@ which managed methods executed or how the CLR resolved them.
 
 Managed member comparisons report a `metadata` dimension when an observed
 MethodDef flags or implementation flags value differs, including accessibility
-or synchronization changes. Observed method-body `init_locals` and `max_stack`
-differences also contribute to `metadata`, even when CIL decoding is incomplete.
-An unavailable header value keeps body coverage unknown rather than establishing
-equality or a difference. These comparisons are separate from the CIL/signature
-matching tiers: identical instructions do not establish unchanged method metadata.
-The reported difference is static metadata evidence, not proof of runtime behavior.
+or synchronization changes. This is separate from the CIL/signature matching
+tiers: identical instructions do not establish unchanged method metadata. The
+reported difference is static metadata evidence, not proof of runtime behavior.

docs/mcp-contracts.md

@@ -1,13 +1,8 @@
 # MCP runtime contracts
 
-For pairing native functions before comparing selected dossiers, see
-[native function matching](native-function-matching.md). It operates on retained
-inventories, preserves aliases/unknowns and exposes selected fact pages.
-
 Use this reference to call REA tools and interpret their replies on one MCP
 connection. Start with [tool results](#tool-results), [retained Evidence](#retained-application-evidence-inputs),
-and [session discovery](#identity-and-discovery). See [transports](#transports)
-for the opt-in HTTP listener, [cancellation](#progress-and-cancellation)
+and [session discovery](#identity-and-discovery). See [cancellation](#progress-and-cancellation)
 for partial-result recovery and [first-query deadlines](#ghidra-first-query-deadlines-and-recovery)
 when a cold provider exceeds the client's wait.
 
@@ -26,14 +21,6 @@ directly to `compare_functions`, and `inspect_artifact` Evidence to
 `compare_artifacts`. Use `get_evidence_bundle` when the task needs broader
 retained session history or an explicit bundle for transfer.
 
-Ghidra inventories and function replies use `raw_result: null` when their facts
-are already preserved in `normalized_result`, limitations, locations and
-relationship coverage. Distinct overview details, measured load-image
-observations, file-offset selection roles and database types supplemented with
-derived metadata keep their upstream representation. Read function results from
-`normalized_result`; older retained Evidence keeps its original representation
-and identity.
-
 Artifact inventories declare `coverage.scope` (`root` or `container-entries`)
 and `coverage.status` (`complete` or `unknown`) independently of diagnostic
 wording. Comparison requires matching scopes, complete graph members and complete
@@ -71,13 +58,7 @@ Call comparison additionally retains the Evidence relationship coverage
 checks. Ghidra and Hopper declare their observed dossier facets and complete
 provider-observed caller/callee sets, including empty sets. Missing decompiler
 output remains unavailable; complete call coverage does not claim every runtime
-target. When Ghidra's decompiler fails on one function, its dossier is still
-returned: `pseudocode`, `native_api` and `native_value_flow` are unavailable
-with the decompiler's failure as the reason, while the listing-backed facets
-are collected as usual. These failed decompiler observations and workflows
-derived from them retain Evidence but skip snapshot reuse, so a later request
-can observe backend recovery; healthy dossiers keep their existing cache policy.
-`procedure_pseudo_code` still fails for that function. Hopper's unavailable reference-kind metadata and reported unresolved
+target. Hopper's unavailable reference-kind metadata and reported unresolved
 calls still prevent equality conclusions for those dimensions. Analysis profiles
 version these declarations so older snapshots are not reused as current results.
 IDA declares the facets its selected adapter cannot provide; an empty
@@ -90,31 +71,13 @@ metadata in the supported JSON payloads (`parameters`, `raw_result`,
 
 Tool execution failures return `isError: true` and the complete canonical
 `{ "error": ... }` diagnostic as JSON in text `content`. Read that diagnostic
-for the error code, target details, partial observations, remediation, and the
-optional bounded `recovery` next step. `recovery.kind=inspect_input_contract`
-names the rejected operation: re-read that operation's advertised input schema
-(call `tools/list` if the catalog may be stale), correct the listed fields, and
-do not repeat the unchanged call. `recovery.kind=inspect_timeout_state` names
-the operation and the REA server/provider deadline; inspect partial Evidence
-and reported cleanup state, then follow producer-specific remediation or reduce
-supported work. Generic errors do not assume adjustable timeout controls. Raising
-only the MCP client's deadline cannot extend this budget. These hints never
-include the complete catalog or caller arguments.
+for the error code, target details, partial observations, and remediation.
 Failures omit `structuredContent`, since each advertised `outputSchema`
 describes successful results. Successful replies retain their schema-validated
 structured data and matching text projection. Oversized errors are retained
 as Evidence before delivery of a bounded diagnostic with an export reference;
 if retention is unavailable or fails, the diagnostic reports that reason.
 
-SDK-generated input validation failures are normalized into the same canonical
-`invalid_request` text when the bounded diagnostic fits the response budget.
-The complete field/type diagnostic is preserved when normalization fits the
-response budget, including request-specific rejected fields and reasons. Oversized
-SDK diagnostics keep the existing retained-Evidence recovery path. An unknown
-tool remains an MCP JSON-RPC `-32602` error, but its message directs the caller
-to `tools/list` and an advertised operation instead of repeating the unknown
-name.
-
 `get_call_graph` returns a `graph` keyed by traversal depth and a top-level
 `limitations` array with deduplicated execution caveats. Each node keeps its
 relationship coverage and read-specific `limitations`, alongside observed
@@ -129,9 +92,8 @@ unresolved relationship reads. Cancellation remains a tool error.
 
 REA prepares complete MCP results within the pinned stdio client's 10 MiB
 receive-buffer budget, including both text and structured representations and
-room for the JSON-RPC envelope. Tool errors omit `structuredContent` from the
-wire; their text, `isError`, provenance marker and negotiated protocol framing
-count toward the wire budget. Response budget settings are captured at startup;
+room for the JSON-RPC envelope. Tool errors carry only their text
+representation and `isError` flag, so only those count against the budget. Response budget settings are captured at startup;
 restart or recreate the server to apply changes. If a result cannot fit, REA returns
 `resource_constraint` with `details.resource: "transport"` before constructing
 a document-sized string. Analysis Evidence remains complete in the current
@@ -141,52 +103,6 @@ that reference for a summary, one section/module, or a stable page, or call
 `export_evidence_bundle` with a destination path. Complete
 bundle exports stream canonical JSON into an atomically published file.
 
-On protocol revision `2026-07-28`, completed replies retain the SDK's
-`resultType: "complete"`, including the replacement for an oversized error.
-This marks completion of the MCP exchange; Evidence coverage, partial facts
-and unknowns retain their separate meaning. Legacy replies keep their existing
-framing.
-
-`list_procedures`, `search_procedures`, `list_strings`, `search_strings` and
-`list_names` accept `detail: "summary"`. Complete inline delivery remains the
-default. Summary retains the original complete Evidence and returns its row
-count, provider identity, analysis-profile digest, original query, parent Evidence
-ID, limitations and explicit unknown discovery coverage. Delivery detail is excluded from provider arguments
-and original Evidence identity.
-
-Read selected rows with `inspect_analysis_view`:
-
-```json
-{
-  "source": {
-    "kind": "retained-evidence",
-    "evidence_id": "ev_<source digest>"
-  },
-  "view": {
-    "kind": "native-inventory",
-    "offset": 0,
-    "limit": 32,
-    "fields": ["value"]
-  }
-}
-```
-
-Each row has `source_index` and `record`; parent Evidence ID plus source index
-identifies same-address alternatives. Order is the original retained order.
-Omit `fields` for complete records; a selected field list always retains
-`record.address`. Selecting `value` also retains available `string` and
-`decoding` qualifications, so native display text and unterminated fragments
-remain distinguishable. Search tools apply their existing filters before retention.
-Follow `coverage.next_offset`; exhaustion describes the retained list, not
-complete discovery of all code or strings. An unbound source keeps
-`artifact: null` and the derived Evidence keeps `subject: null`.
-
-The CLI uses the same projector. For an original complete Evidence JSON file,
-write `{"source":{"kind":"evidence-file","path":"/absolute/source.json"},"view":{"kind":"native-inventory","limit":32}}`
-to `/absolute/view-request.json`, then run
-`rea inspect-analysis-view /absolute/view-request.json --json`. This also reads
-pre-summary source records without changing their identity; no live provider is started.
-
 For oversized native function Evidence, `details.reported_limits.continuation`
 contains a ready-to-call `inspect_analysis_view` request for the retained
 pseudocode's first page. Use its `name` and `arguments` directly, then follow
@@ -195,8 +111,6 @@ limit is the view contract's default, not a guarantee that arbitrary source or
 metadata fits; reduce the limit or export when needed. Continuations are
 offered for completed `analyze_function` results only after session recording is
 acknowledged; the complete result and its retention reference remain intact.
-Oversized native inventories likewise include a ready-to-call first
-`native-inventory` page. Reduce its limit or select fields when a row is large.
 
 A broad follow-up or `get_evidence_bundle` can also exceed the response budget; exporting
 preserves the complete session without sending it through a single MCP frame.
@@ -218,12 +132,6 @@ is null. `total` counts all matching heads; each page preserves complete records
 in stable unknown ID order. Filters apply before paging. Pages reflect current
 session state, so keep the unknown ledger unchanged while traversing it.
 
-Automatically retained workflow questions include their immutable result
-Evidence ID. Distinct results retain independent questions and source links;
-repeating the same result does not create another unknown. Workflow Evidence
-keeps the original residual question text. Explicit `record_unknown` requests
-keep caller-selected identity and reject duplicate creation.
-
 For a portable exported bundle, the CLI shares this projection:
 `rea inspect-evidence-bundle '{"path":"/tmp/evidence.json","detail":"summary","filters":{"operation":"analyze_function"}}' --format json`.
 The CLI validates and materializes that local bundle under its existing memory
@@ -234,31 +142,11 @@ The destination changes only when a complete export is atomically published.
 
 Clients that explicitly configure a larger receive buffer can set the REA
 server's `REA_MCP_MAX_RESPONSE_BYTES` environment variable to the same byte
-count. This setting must be a safe decimal integer at least 10485760 (10 MiB);
-REA reserves 1024 bytes for the envelope. The value is read when the REA
-process starts, so a change requires a restart and a matching client receive
-buffer. Raising it restores complete inline delivery for responses that fit
-that buffer. It does not raise REA's reserved single-string limit, which is
-1024 UTF-16 code units below Node's single-string ceiling, and it does not
-raise that Node ceiling. It does not change analysis coverage or retained
-content. Ordinary responses keep their existing complete result contract.
-
-### Error recovery and deadline ownership
-
-Initialization instructions and the static JavaScript tool description teach
-recovery before a host can discard a tool response. Invalid input calls should be corrected from the connected schema
-(refresh `tools/list` only if stale), not retried unchanged. REA's returned
-`provider_timeout` describes its server/provider deadline; provider-authored
-remediation names the applicable controls and preserves partial Evidence and
-cleanup uncertainty.
-
-A host timeout without a REA result is different: execution and cleanup remain
-unknown. Increasing an advertised `analysis_timeout_ms` cannot fix a shorter
-client deadline. Configure the client's tool timeout with execution, cleanup
-and delivery headroom, or report that change is needed when not authorized.
-Session status does not establish that all target-free work stopped. Detailed
-host settings and bounded retry guidance live in the shipped skill's
-[recovery reference](https://github.com/morluto/rea/blob/main/.agents/skills/reverse-engineer-anything/references/connection-and-recovery.md#distinguish-client-and-server-deadlines).
+count. This setting must be a safe decimal integer at least 10485760; REA
+reserves 1024 bytes for the envelope. Raising it restores complete inline
+delivery for responses that fit that buffer and Node's single-string limit.
+It does not change the client's buffer, analysis coverage, or retained content.
+Ordinary responses keep their existing complete result contract.
 
 ### Untrusted target content
 
@@ -322,21 +210,6 @@ inferred Evidence whenever any group is templated, and derived Evidence only whe
 no group was templated.
 See [derived API surfaces](web-network-captures.md#derived-api-surface).
 
-`inspect_analysis_view` also accepts `environment-manifest` for retained HAR capture
-Evidence and `capture_browser_scenario` Evidence, projecting the primary origin's request lines into named tools with path
-templates, parameters, observed query names, value-free body shapes and record
-pointers, plus excluded groups and three fixed unknowns. Templates, parameters and
-names are inferences; the Evidence is inferred whenever any tool or excluded group
-is templated, and derived otherwise.
-See [environment manifests](web-network-captures.md#environment-manifest).
-
-`inspect_analysis_view` also accepts `environment-state` for the same parents,
-extracting the initial state the recorded reads observed: entity types with an
-identity field, entities, documents for non-entity reads, and a render
-plan per read tool that reproduces its recordings from the state or names why it
-cannot. Types and identity are inferences, so the Evidence is always inferred.
-See [environment state](web-network-captures.md#environment-state).
-
 `inspect_analysis_view` projects a caller-selected view of already completed
 `inspect_binary_layout`, `analyze_javascript_application`, or `analyze_function`
 Evidence. Native views select procedure, pseudocode, assembly, basic blocks,
@@ -355,41 +228,10 @@ application and semantic coverage. The result carries a digest of the selected
 facts. Actual serialized size determines MCP transport admission: reduce the
 page size or export retained Evidence if the view is too large.
 
-`compare_source_to_bundle` accepts the committed historical graph inline or as
-`reference: {"kind":"file","path":"/absolute/reference.json"}`. The shared
-reader checks resource bounds and the graph's root commitment on every read. File-backed
-comparison Evidence records `parameters.reference_source`: the exact
-`requested_path` and the reader's absolute selected `path`, preserving POSIX
-`..`/symlink semantics. Normalized comparison facts and mapping identities agree
-with inline input; Evidence IDs distinguish caller-selected file origins.
-Omitting `view` preserves the complete comparison. For a compact initial reply,
-select `view: {"kind":"summary"}` or a `source-to-bundle` page; the session retains
-the complete comparison before delivery. Later calls use `inspect_analysis_view`
-with the returned `parent_evidence_id`.
-
-A `source-to-bundle` view selects `collection: "mappings"` or `"candidates"` with
-exact `source_paths`, `mapping_ids`, `statuses`, `fields`, `offset` and `limit`.
-Omitted filters select all; empty arrays select none. The default mapping fields
-include status, confidence, source digest/language and candidate/mapped counts.
-Candidate defaults include kind, score and confidence; request `signals` for exact
-supporting values. Mapping identity and `source_index` always remain; candidates
-also retain `current_node_id`, `candidate_index` and whether they were actually
-mapped. Indices refer to the complete comparison's item array and that item's
-candidate array. All classifications are computed before selection. The original
-`source_coverage` remains separate from page `coverage`; exhausting a page never
-turns unknown correspondence into absence or proves behavioral equivalence.
-
-The CLI accepts the same reference-file alternative (relative paths resolve from
-the working directory). Save its complete `--json` Evidence, then use
-`inspect-analysis-view` with an `evidence-file` source and the same view. Neither
-adapter executes the target or repeats analysis for retained queries.
-
 Completed `inspect_artifact` and atomic `inventory_artifact` Evidence also
 support summary and inventory views. A summary reports the manifest's expected
 counts separately from available record counts, observed entry kinds, inventory
-Evidence IDs, the inventory producer's traversal `source_coverage` and
-inspection coverage. Inspection coverage is `partial` when that traversal
-coverage is unknown. An inventory view selects `nodes`,
+Evidence IDs and inspection coverage. An inventory view selects `nodes`,
 `occurrences`, `edges`, or `integrity_contradictions`, with `offset` and `limit`
 defaulting to 0 and 64. For occurrences, optional `logical_paths` matches exact
 recorded strings: omission selects all available records; `[]` selects none.
@@ -513,17 +355,6 @@ checking that a client received the full catalog. An operation absent from all
 groups is missing from the complete inventory; it is not an implicit
 unavailable entry.
 
-`get_call_graph` and `trace_call_path` report `forward` and `backward` modes.
-Each requires `procedure_address` plus `procedure_callees` or `procedure_callers`,
-respectively. The tool is available when either traversal mode is supported;
-`default_mode_available` describes the default forward direction. Read each mode's
-missing operations and remediation before selecting a direction. These facts
-describe traversal prerequisites, not relationship completeness or a guarantee
-for every selector. A trace whose start and goal resolve to the same address can
-finish without reading relationships, even when neither traversal mode is
-available. Discovery does not block that direct invocation or replace its typed
-partial/error outcomes.
-
 The `effects` and `annotations` arrays list the true members of their fixed
 vocabularies. A known member omitted from either array is false. This applies
 only to these closed flag sets; it does not make an omitted tool, provider, mode,
@@ -562,132 +393,15 @@ concrete version, selection source, and complete analysis profile through
 choices return typed selection details. A selected provider is never replaced
 automatically after a runtime failure.
 
-`open_bundle_resources` selects a separate read-only app resource session
-without resolving `CFBundleExecutable`, including when it is absent or
-unresolvable. `binary_session` reports `session_kind: "bundle_resources"` and the
-caller and canonical resource-root paths; it does not report a binary target or
-deep-provider binding. `inspect_plist`, `decode_interface_builder`,
-`inspect_asset_catalog`, and `inspect_keyed_archive` retain resource-root
-provenance and use a null Evidence subject when executable identity is unknown.
-Binary-only operations and binary analysis snapshots do not apply in this
-session. `open_binary` can switch back to executable analysis, and
-`close_binary` retires either session kind.
-
-Each provider client receives `binary_session.analysis_run.run_id` before any
-provider startup, including clients whose startup fails. `process_lineage` is
-`not_observed` until a dynamic provider starts, then becomes `snapshots` with
-every started provider's identity
+Every successful target transition allocates `binary_session.analysis_run.run_id`
+before any provider startup. `process_lineage` is `not_observed` until a dynamic
+provider starts, then becomes `snapshots` with every started provider's identity
 and retained ownership observation. Each observation records `observed_at` and
 is `unavailable` with a reason when ownership could not be revalidated, or
 `verified` with launcher PID, parent PID, process group, and descendants observed
 at that bounded check. These are historical snapshots, not live process
 inventories, and do not claim that no short-lived descendant existed.
 
-`binary_session.cleanup_pending` reports whether the session retains a provider
-client, session file resource, or provider-candidate resource whose cleanup
-has not succeeded. It can be true with
-`open: false`; target retirement does not establish resource release. For a
-retained provider client, health, activity, and lineage remain available under
-its original `analysis_run.run_id` where the provider supplies them.
-Successful provider cleanup clears the retained run;
-a replacement client receives a fresh run ID. Follow the cleanup error's
-reported resources and recovery action before reopening; a missing health
-observation does not establish an idle provider.
-File cleanup can also remain after snapshot publication or after profile
-inspection fails or is cancelled before a provider client exists. If no client
-remains, no provider run or health observation is available; follow the cleanup
-error's reported resources.
-
-## Transports
-
-stdio is the default transport and the only one that client registrations,
-`rea mcp doctor` and the MCP registry entry describe. `rea mcp --http [--host H]
-[--port N]` is an opt-in alternative that serves the same catalog over the
-streamable HTTP transport at `/mcp`; it replaces stdio for that process rather
-than running beside it. Host and port come from the flags, then `MCP_HOST` and
-`MCP_PORT`, then `127.0.0.1` and an ephemeral port. The bound URL is announced
-as one JSON log line on stderr (`"msg":"MCP transport listening"` with `url`)
-at every `REA_LOG_LEVEL`, because an ephemeral port is otherwise unreachable;
-stdout stays unused.
-
-This endpoint uses plain HTTP without TLS or client authentication. Use it only
-within a trusted local or isolated environment; an explicit non-loopback bind
-makes the same tools and active analysis state reachable at that address. It
-does not provide separate users or independent target sessions. Standard client
-registrations continue to use a dedicated stdio process.
-
-The HTTP server is stateful and serves one client at a time on one server
-instance. `initialize` returns an `Mcp-Session-Id`; `notifications/initialized`
-is acknowledged with `202`; responses arrive as JSON or SSE frames; `DELETE
-/mcp` with the session id ends the session with `200`. Ending a session is not
-a server shutdown: the process keeps listening, the instance keeps its providers
-and the shared active target, and the next client opens a fresh session against
-them. A client ending or replacing a session cancels its running tool calls and
-prompt completions, stops request-body reads and fences further message dispatch,
-then waits up to ten seconds for request dispatch, handlers and cleanup to finish before reusing the
-server. A timeout returns `503`; the old calls remain owned, and later requests
-retry the drain rather than starting another session against those resources.
-Requests that finish parsing or SDK dispatch after their session closed are
-refused, and their response streams are cancelled. Tool callbacks whose
-validation finishes after cancellation never start.
-Body forwarding stops when SDK request processing ends, including early header
-and size refusals, rather than remaining active until the session closes.
-HTTP input/route dispatch is limited to eight concurrent requests by default,
-shared by MCP and plain routes. Excess requests receive `503` with a closing
-connection before their bodies are converted, read or cloned. An embedder can
-select `maxConcurrentDispatches`; the SDK's per-body size limit still applies.
-MCP responses with fully read or bodyless requests do not hold admission slots,
-so an idle MCP SSE stream does not prevent later calls. Plain routes retain their
-slots through response delivery and response-source cancellation cleanup. An
-unread upload retains its slot until input finishes or either side closes,
-even with a long response. Sequential keep-alive is supported; a peer pipelining
-behind an unfinished response is disconnected before queued requests dispatch.
-Concurrent MCP requests use separate connections.
-This bounds concurrent input work, not total provider or process memory.
-Provider-backed prompt completions use the same request owner and drain, so a
-cancelled completion cannot keep using providers after handover or shutdown.
-HTTP factories enable `RequestTrackingMcpServer` tracking so completion is tracked
-even when cancellation suppresses the SDK's reply; stdio retains the SDK's
-original callback behavior. Full server shutdown stops the listener and waits
-for MCP work, plain-route handlers and response-source cancellation to settle
-before running provider shutdown hooks or closing providers. Response producers
-must finish provider work before closing their stream and expose asynchronous
-disconnect cleanup through the stream's `cancel()` result. Cancellation does not
-delay delivery of a HEAD reply; a caller retaining a sibling of a teed response
-must consume or cancel that sibling before shutdown can finish. Failed response
-cleanup remains owned, blocks further admission and prevents provider teardown.
-The server continues cleanup
-automatically when they finish, including after a client handover timed out.
-All routes return `503` until the server factory succeeds; startup failure closes
-the listener and joins its pending replies before rejecting the factory.
-The newest client replaces an open session: an `initialize` that arrives
-while a session is open ends that session instead of being refused, because a
-client that exits without `DELETE` must not wedge the listener; the replaced
-client's open streams are closed and its later requests are refused. Only an
-`initialize` that carries the streamable headers (`Content-Type:
-application/json` and an `Accept` naming both `application/json` and
-`text/event-stream`) and passes the Host and Origin checks can replace a
-session; any other sessionless POST goes to the live transport, which refuses
-it without disturbing the session. Requests that carry no valid session id are
-refused with `400` or `404` as the SDK transport defines. A bind is loopback by
-address class, not spelling, and is classified from the address the listener
-actually bound: any `127.0.0.0/8` address, `::1`, or an IPv4-mapped loopback.
-Configured names, including `localhost` and its aliases, do not establish that
-the bound address is local; names are added only after classifying the actual IP.
-On such a bind, requests whose `Host` header is outside the SDK loopback allowlist plus
-the configured name and the bound address are refused with `403`, and a browser
-`Origin` outside that allowlist is refused the same way (a missing `Origin`
-passes); a non-loopback bind relaxes both checks and logs the relaxation. A reply sent before a request body was read (a refused `Host` or `Origin`, an unknown route, the startup `503`) closes the connection after the reply, so an unread upload cannot keep a socket open. Request targets are taken verbatim as origin-form paths (`//host/path` is a path, not another origin); an absolute-form target, a target containing a raw fragment delimiter (`#`), or one whose path URL parsing would rewrite (dot segments such as `/public/../mcp`), is refused with `400`, and a method Fetch does not support with `405`. Percent-encoded `%23` remains valid query data. Only a lone `initialize` can replace an open session; a batch that carries one is left to the transport's refusal. Scoped
-IPv6 literals (`fe80::1%eth0`) are refused before binding, because no URL can
-name them. Listener errors reach the runtime's connection-loss handler only
-after a successful bind; a bind failure prints the listen-failure message alone. Request bodies are bounded by the SDK's
-4 MiB limit, and the response budget keeps its stdio-derived floor. The
-listener ends on SIGINT or SIGTERM only, not on stdin EOF, and exits `130` or
-`143` after cleanup settles. A signal that arrives while startup is still
-running is recorded and acted on as soon as the listener and its providers are
-owned, so startup never ends without cleanup; a second signal during startup
-exits immediately.
-
 ## Progress and cancellation
 
 REA accepts ordinary `tools/call` progress tokens. The numeric `progress` counts
@@ -705,9 +419,6 @@ Provider calls receive the request cancellation signal. Artifact traversal,
 hashing, version comparisons, Hopper requests, and process capture
 check the same signal. Cancellation is distinct from timeout. A cleanup failure
 uses `cleanup_incomplete` and lists only the owned resource kinds that remain.
-Once those owners confirm cleanup, composed failures recover their original
-typed primary outcome and recovery guidance. Historical composition diagnostics
-remain in `details.cleanup_history`, separate from the primary diagnostics.
 An atomic Evidence bundle or snapshot write can publish its complete output
 before staging cleanup fails. In that case, `details.published: true`,
 `details.published_path`, and `details.bytes` retain the publication receipt.
@@ -717,25 +428,12 @@ Native call tracing and process capture retain available observations in
 `details.partial_observation` on failure, including when cleanup succeeds.
 The observation reports its partial coverage; cleanup details describe host
 state separately from the execution failure.
-For these tools, cancellation observed during result finalization or owned
-cleanup also returns typed cancellation with the available observations.
-A normal target exit does not establish request completion. Incomplete cleanup
-still takes precedence and retains its resource diagnostics.
 A process capture that fails during a finalization interval keeps every signal
 attempt and its delivery result in `details.partial_observation`, with
 `elapsed_ms` and `exit_code` null when no exit was observed.
 Derived comparisons and reconstruction verification yield before computation
 and before publication, so cancellation cannot race with successful Evidence.
 
-Bundle recovery requires a recorded Evidence ID. Some provider errors carry
-typed raw observations in `details.partial_observation` instead of Evidence.
-Those raw observations are not recorded in the Evidence bundle. If the SDK
-suppresses the error reply after client cancellation, Evidence tools cannot
-recover them. An empty bundle does not prove that no partial work or side
-effect occurred; output receipts and cleanup observations remain distinct.
-The broader retention decision is tracked in
-[#4276](https://github.com/morluto/rea/issues/4276).
-
 `analyze_javascript_application` also yields between reconstruction phases and
 during graph/result sealing, cross-graph binding checks, Evidence JSON validation,
 and canonical hashing. Its final result validation reuses exact graphs whose
@@ -794,40 +492,12 @@ analysis runtime. These failures are reported at the operation that needs
 them. A configured provider or an endpoint alone does not establish that a
 target is supported.
 
-Composite Hopper regex searches report failures against the accepted
-`search_strings` or `search_procedures` operation. The underlying inventory
-method and request ID remain in `details.diagnostics.provider_request`, with
-the bridge error code and diagnostic type when available. Reattribution
-preserves the failure class, captured output, and live cleanup ownership.
-
 Evidence bundles, snapshots, and extraction use the paths and output behavior
 declared by their tools. Artifact extraction materializes the selected regular
 files into a fresh REA-chosen temporary directory and reports its path.
 
 `analyze_javascript_application` reads the supplied local directory or ASAR path
-and returns its result and Evidence inline. Its owned analysis worker and private
-temporary source files are declared as `launchesProcess` and `writesFilesystem`,
-including for a single JavaScript source. This internal analysis does not execute
-the supplied application code.
-
-## Static Ghidra bytes and source mappings
-
-`read_bytes` returns initialized analysis memory, including loader fixups, rather
-than live process memory. Check `returned_bytes` and `complete` before decoding:
-reads stop at unmapped or uninitialized bytes. Missing bytes are unknown; do not
-pad an incomplete read with zeros and treat the result as an observation.
-
-`list_segments` reports memory-block initialization and address-space facts.
-`address_to_file_offset` maps one address through the provider's source-byte
-mapping. A successful start-address mapping does not establish that an entire
-range is contiguous in the original file, or that its bytes equal analysis
-memory after loader fixups. Uninitialized, missing, and ambiguous mappings fail
-explicitly; preserve the reported failure rather than guessing an offset.
-
-For constructor-populated pointer or resource slots, a static zero is not proof
-of a later null value. Inspect the slot's `xrefs` and the writer's assembly or
-pseudocode, retaining uncertainty about execution order and runtime values.
-These operations inspect static evidence and do not execute the target.
+and returns its result and Evidence inline.
 
 ## Ghidra first-query deadlines and recovery
 
@@ -839,13 +509,13 @@ auto-analysis, bridge connection, and health readiness before returning analysis
 
 These deadlines have different owners:
 
-| Deadline             | Owner and effect                                                                                                                                                                                                                                                                                                    |
-| -------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| MCP initialize       | The client bounds transport/REA connection startup, before any target query.                                                                                                                                                                                                                                        |
-| Hopper startup       | REA allows 120,000 ms by default; `REA_HOPPER_STARTUP_TIMEOUT_MS` accepts decimal integers from 1–2,147,483,647 ms. Invalid values fail configuration validation. Startup failure is reported by the first provider query.                                                                                          |
-| Ghidra startup       | REA allows 330,000 ms by default; `REA_GHIDRA_STARTUP_TIMEOUT_MS` accepts decimal integers from 1–2,147,483,647 ms. Invalid supplied values fail configuration validation. Startup failure is reported by the first provider query.                                                                                 |
-| Darwin swiftc helper | REA allows 120,000 ms by default for ownership-helper compilation; `REA_SWIFTC_COMPILE_TIMEOUT_MS` accepts decimal integers from 1–2,147,483,647 ms. Invalid values fail configuration validation. Set it in the environment that starts REA and restart REA; the next ownership-helper compile uses the new value. |
-| Individual tool call | The client bounds its wait, including cold engine startup. The pinned client SDK 2.3.1 defaults to 60,000 ms and can cancel earlier than REA's startup deadline.                                                                                                                                                    |
+| Deadline             | Owner and effect                                                                                                                                                                                                                    |
+| -------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| MCP initialize       | The client bounds transport/REA connection startup, before any target query.                                                                                                                                                        |
+| Hopper startup       | REA allows 120,000 ms by default; `REA_HOPPER_STARTUP_TIMEOUT_MS` accepts decimal integers from 1–2,147,483,647 ms. Invalid values fail configuration validation. Startup failure is reported by the first provider query.          |
+| Ghidra startup       | REA allows 330,000 ms by default; `REA_GHIDRA_STARTUP_TIMEOUT_MS` accepts decimal integers from 1–2,147,483,647 ms. Invalid supplied values fail configuration validation. Startup failure is reported by the first provider query. |
+| Darwin swiftc helper | REA allows 120,000 ms by default for ownership-helper compilation; `REA_SWIFTC_COMPILE_TIMEOUT_MS` accepts decimal integers from 1–2,147,483,647 ms. Invalid values fail configuration validation.                                  |
+| Individual tool call | The client bounds its wait, including cold engine startup. The pinned client SDK 2.3.1 defaults to 60,000 ms and can cancel earlier than REA's startup deadline.                                                                    |
 
 For [Codex and Kimi registrations](client-configuration.md), setup supplies
 missing tool deadlines from the known provider allowance plus 120 seconds of
@@ -853,8 +523,7 @@ operation headroom: 450 seconds with the default Ghidra allowance, or 2820
 seconds with `REA_GHIDRA_STARTUP_TIMEOUT_MS=2700000`. Positive caller-selected
 deadlines remain unchanged. Doctor reports an informational recommendation
 when a configured deadline is shorter than the known provider allowance. An
-explicit JEB upstream deadline (`REA_JEB_MCP_TIMEOUT_MS`, shared by catalog
-discovery and each tools/call) also contributes to that allowance.
+explicit JEB upstream request budget also contributes to that allowance.
 
 For an already connected client using the pinned SDK, request options are the
 **second** argument of `callTool`:
@@ -923,13 +592,6 @@ the current client, so it is not a fresh-start recovery. On the same connection:
    `provider_id: "ghidra"`, then retry the first query with an appropriate client
    deadline. The connection and selected provider do not need to change.
 
-If REA's provider startup allowance also needs raising, preserve Evidence and
-close as above, then update `REA_GHIDRA_STARTUP_TIMEOUT_MS` in REA's launch
-environment and restart the server. Reconnect the MCP client before reopening
-the target. Configuration is read at process startup; close/reopen on the same
-connection cannot apply a changed environment. See the
-[CLI retry example](installation.md#ghidra).
-
 This close/reopen flow was exercised on one real Linux stdio connection after a
 controlled startup timeout, followed by a successful overview and function
 analysis. A separate Windows x64 stdio run with Ghidra 12.1.4, JDK 21 and Node
@@ -1029,39 +691,18 @@ after SDK conversion and check advertised validation and actual calls.
 Individual model APIs can impose additional nesting limits; complete producer
 captures can exceed ten structural levels.
 
-`search_bytes` advertises its pattern and mask as descriptive strings. Its
-shared canonical validator scans byte pairs, whitespace, wildcards and aligned
-masks without a repeating regular expression or temporary byte arrays. The
-server rejects malformed or unconstrained patterns before provider dispatch;
-the advertised strings alone do not express those rules.
-
-Boolean literal constraints in input schemas are relaxed only in this
-advertisement. For example, a boolean `const` is presented as `type: boolean`;
-an affected `not` is omitted, conditional predicates and their branches are
-omitted together, pure boolean-literal `oneOf` branches collapse to a boolean,
-and other affected `oneOf` branches are presented as `anyOf` to retain branch
-guidance without making overlapping widened branches reject inputs.
-This can make the advertised schema accept inputs the canonical contract
-rejects. The MCP handler still validates every call with the canonical
-contract. The Gemini CLI verifier checks the outgoing
-`parametersJsonSchema` and canonical contract examples against that declaration
-using a loopback model fixture; it does not establish live Google API or
-OpenCode client behavior. Set `REA_VERIFY_GEMINI_SCHEMA_PROFILE=compact` to
-verify the compact advertisement through the same client boundary.
-
 ### Compact input schema profile
 
 Some function-calling providers reject a request while any single tool's
 `parameters` schema exceeds a literal serialized size cap; Moonshot clients
-such as kimi-cli have reported failures with the full catalog attached
+such as kimi-cli fail every request while the default catalog is attached
 ([#1484](https://github.com/morluto/rea/issues/1484)). Setting the server's
-`REA_MCP_INPUT_SCHEMA_PROFILE` environment variable to `compact` (the default)
-renders every advertised input schema within a 13,312-byte budget, measured to sit below
+`REA_MCP_INPUT_SCHEMA_PROFILE` environment variable to `compact` renders every
+advertised input schema within a 13,312-byte budget, measured to sit below
 Moonshot's observed cap (community measurements: a 13.7 KB schema is accepted
 while a ~15 KB one is rejected). The setting is read at startup; restart the
-server to apply changes, as with `REA_MCP_MAX_RESPONSE_BYTES`. Explicitly select
-`full` to retain complete advertised input guidance and nested validation detail.
-Existing explicit profile choices are preserved. Compact presentation
+server to apply changes, as with `REA_MCP_MAX_RESPONSE_BYTES`. The default
+value `full` keeps the complete advertisement unchanged. Compact presentation
 also reduces schemas whose expanded JSON tree exceeds ten levels, the limit
 reported by strict-depth MCP clients in [#2813](https://github.com/morluto/rea/issues/2813).
 WorkBuddy/CodeBuddy gateways have also rejected full REA catalogs with an
@@ -1142,21 +783,6 @@ includes all dimension limitations. Equal CFGs establish only equal observed
 block sizes and successor relationships. Text from different provider
 identities remains unknown.
 
-The `references` dimension preserves each edge's direction, endpoint identity
-and available kind facts. Within one artifact it compares exact raw endpoint
-coordinates, including the address space; hexadecimal case and zero padding
-do not change identity. Resolving an endpoint to a containing procedure does
-not replace the raw coordinate. Unparseable coordinates stay unknown.
-
-Across artifacts, reference endpoints use stable procedure names. Missing or
-address-generated names remain unknown. A name observed at multiple procedure
-entries retains its label constraint but cannot establish equal endpoints.
-Pairing preserves duplicate counts and considers alternative compatible
-pairings; array order never identifies an edge. Compatible records with
-unknown endpoint identity or kind facts remain `unknown`. Independent known
-facts that contradict every possible pairing still establish `changed`.
-Source Evidence retains the original addresses, names and unavailable facts.
-
 ### Comparison input shapes
 
 `compare_web_captures` accepts exactly one of two input shapes:

docs/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/model-artifacts.md

@@ -1,150 +0,0 @@
-# Model file declarations
-
-Use `inspect_model_artifact` (CLI: `inspect-model-artifact`) to inspect a local
-GGUF v2/v3 or safetensors file. Detection uses content, including GGUF byte
-order, rather than its extension. REA does not load a model, interpret weights,
-run inference, import Python, open external-data references or use the network.
-
-Unsupported GGUF versions remain refused. Their diagnostic preserves the four
-version bytes and both UINT32 interpretations with byte order unknown, rather
-than inferring big-endian from an unrecognized little-endian value. Little-endian
-v2/v3 and big-endian v3 remain supported; big-endian v2 remains refused.
-
-```bash
-rea inspect-model-artifact /absolute/path/model.gguf --json
-rea inspect-model-artifact /absolute/path/model.safetensors --hash full --json
-```
-
-The CLI defaults to complete Evidence. For compact delivery with portable access
-to every retained observation:
-
-```bash
-rea inspect-model-artifact /absolute/path/model.gguf \
-  --detail summary --evidence_output /absolute/path/model-evidence.json --json
-```
-
-## Identity and reads
-
-The default `hash: "header"` reads only the metadata and tensor directory. The
-result records the exact selected path, file size, header length, header SHA-256,
-bytes read and read scope. GGUF alignment padding is outside this prefix.
-`artifact.sha256` and the Evidence subject are null: a header digest is not a
-commitment to the weights. Different files can have identical headers and sizes.
-
-`hash: "full"` additionally streams the remaining file bytes through SHA-256.
-It returns a full-file digest and Evidence subject, while retaining the same
-header digest. It uses bounded buffers and does not interpret tensor data, but
-it does read the whole file. Cost therefore grows with file size. Both modes
-check descriptor and selected-path identity and metadata before completion;
-this detects observed replacement or modification, not adversarial modification
-that defeats filesystem metadata checks.
-
-## Facts and selected queries
-
-GGUF reports version, byte order, alignment, typed metadata, and each tensor's
-name, original type ID, dimensions, relative data offset, file offset and derived
-byte length. Alignment accepts every positive UINT32 multiple of eight, including
-non-powers of two. Metadata keys use ASCII lower-snake-case hierarchy components;
-standard numeric components such as `general.base_model.0.name` are preserved.
-Scalar metadata is complete. Arrays have declared element types,
-counts and at most eight preview elements per array, with an explicit
-`preview_complete` flag. This includes tokenizer vocabularies: omitted values
-are not silently represented as a complete array. Strings are UTF-8; 64-bit
-integer metadata and all shape dimensions use decimal strings without rounding.
-Nonfinite floating metadata uses `NaN`, `+Infinity` or `-Infinity` with its
-declared float type; negative zero is `"-0"`. Unknown tensor types retain their numeric IDs and null byte
-lengths; affected totals and storage validation remain unknown.
-
-Safetensors reports the header extent, exact string `__metadata__` values, dtype,
-shape and declared data ranges. JSON duplicate keys, invalid UTF-8, out-of-file
-ranges, overlaps, gaps, trailing unindexed data and known dtype/shape byte-length
-contradictions are rejected with a typed `file_format_rejected` constraint (public code `target_unavailable`, category `unsupported_target`). Empty
-tensors and scalar shapes are supported; packed sub-byte types require whole
-byte storage. Unknown dtypes retain declared ranges and an explicit limitation
-that shape-to-storage validation is unavailable. Each tensor records
-`storage_validation: "consistent" | "unknown"`; `coverage.storage_sizes` remains
-partial when that consistency cannot be checked. Tensor filters accept these
-`storage_validation` states independently of dtype or name.
-
-Parameter counts and per-type totals are **derived from declarations**, not
-measurements of effective parameters or inference behavior. Shared or repeated
-weights are not deduplicated. GGUF dimensions retain their original fastest-first
-order; safetensors shapes retain JSON order. Safetensors tensor rows use name
-order; GGUF rows use directory order. An index identifies a declaration within
-its collection and header digest, not tensor contents or a cross-version match.
-GGUF supports zero extents and scalar shapes, with at most four dimensions;
-known quantized types still require complete blocks in the first dimension.
-
-MCP defaults to a compact summary with counts, selected short headline metadata,
-chat-template presence and derived totals. The full type histogram and all rows
-remain in complete Evidence. Headline metadata uses short keys/types and scalar
-values; long or compound values remain available through explicit metadata
-queries. Use the returned `parent_evidence_id`:
-
-```json
-{
-  "source": {
-    "kind": "retained-evidence",
-    "evidence_id": "<parent_evidence_id>"
-  },
-  "view": {
-    "kind": "model-artifact",
-    "collection": "tensors",
-    "names": ["token_embd.weight", "output.weight"],
-    "fields": ["name", "type", "shape", "file_offset", "byte_length"],
-    "offset": 0,
-    "limit": 32
-  }
-}
-```
-
-To answer a known question in the initial inspection, pass the same selection
-without `kind` as `inspect_model_artifact`'s optional `view`, for example
-`{"path":"/absolute/path/model.gguf","view":{"collection":"tensors","names":["token_embd.weight"],"fields":["type","shape","file_offset"]}}`.
-This returns one selected page with compact model context and retains the full
-source Evidence, avoiding another tool call. `view` requires summary delivery;
-complete detail and a selection are rejected as conflicting choices.
-CLI uses `--view '{"collection":"tensors","names":["token_embd.weight"]}'`
-with `--detail summary --evidence_output FILE`.
-
-Call `inspect_analysis_view` with the historical query object above for further pages. `collection: "metadata"` accepts
-exact `keys`, indices, fields and paging; use it for `tokenizer.chat_template`
-or tokenizer array previews. `collection: "types"` pages derived storage and
-parameter totals and accepts exact `types`. Tensor pages also accept `types`.
-Filters intersect; omitted filters mean all recorded rows and empty arrays mean
-none. Every row retains its source-scoped index. Names, keys and type labels
-follow field selection; `fields: []` returns only indices. Omitted fields return
-all recorded columns. Compact warnings use the shared bounded view budget and
-link to complete parent Evidence when messages are omitted. Page offsets count filtered
-matches, while row indices retain their original scope. Each page carries source
-identity, header coverage, array omissions, unknowns and parent Evidence links.
-
-Pages read historical retained facts without reopening the model. Complete
-Evidence can also be supplied inline or as a single authenticated Evidence JSON
-record through `source: {"kind": "evidence-file", "path": "/absolute/path/model-record.json"}`.
-CLI Evidence bundles contain a `records` array; import the bundle with
-`import_evidence_bundle` before using retained queries, or save one complete
-record as a standalone Evidence file. A bundle is not a single Evidence record.
-The session owns validated indexes until that Evidence is released; there is no
-live-file result cache or automatic freshness claim.
-Imported reports must retain positional indices and unique names, keys and
-type identities; malformed reports return a typed input error before indexing.
-
-## Bounds and unsupported inputs
-
-The reader admits one active inspection per provider. It enforces a 100,000,000
-byte header ceiling (safetensors counts its declared JSON bytes separately from
-the fixed eight-byte length prefix; GGUF counts the complete header) and a separate 32 MiB
-retained representation budget before retaining rows or expanding strings.
-Numeric products use exact integer arithmetic. GGUF follows its four-dimensional
-tensor layout and limits metadata array nesting to 32 frames. Resource refusals
-are typed, rather than returned as complete empty inventories. Cancellation
-joins descriptor finalization; failed cleanup remains owned for retry.
-
-PyTorch pickle and ZIP model deserialization are unsupported; convert using a
-trusted external workflow and supply GGUF or safetensors. ONNX, TFLite, Core ML,
-model execution and conversion are outside this operation.
-
-Format references: [GGUF specification](https://github.com/ggml-org/ggml/blob/da8e2a54b919557b816b1c2beb432ccb766f7ce0/docs/gguf.md),
-[ggml tensor layouts](https://github.com/ggml-org/ggml/blob/da8e2a54b919557b816b1c2beb432ccb766f7ce0/src/ggml-common.h),
-[safetensors format](https://github.com/huggingface/safetensors/tree/e246a2560645b7525f5775669ed816eb57c5bcc8#format).

docs/native-function-matching.md

@@ -1,120 +0,0 @@
-# Match native functions across builds
-
-`match_native_functions` pairs two existing `list_procedures` Evidence inventories. Select `list_procedures` `detail: "summary"` to retain
-complete source rows without transferring the entire inventory. Its
-`parent_evidence_id` is the reference matching consumes.
-Targets may be opened sequentially; matching never opens a target, rereads its
-file, executes it or starts a provider. Preserve each inventory before closing its
-target, or import its Evidence bundle later. `close_binary` clears session
-records. Export each bundle before closing; after collecting both sides and
-closing the last target, import both bundles, then use their references. Keeping
-only an Evidence ID across close is insufficient. Complete inline Evidence and
-CLI `source_bundle` inputs are portable alternatives. Pass Evidence or exact
-session references as `left` and `right`:
-
-```json
-{
-  "left": { "kind": "retained-evidence", "evidence_id": "ev_<left digest>" },
-  "right": { "kind": "retained-evidence", "evidence_id": "ev_<right digest>" }
-}
-```
-
-Unique exact reported names are paired first. Optional `list_names` Evidence
-identifies dynamic/default names to exclude. If origin is unavailable, the
-existing automatic-name exclusion rule applies and each function retains that
-limitation. Exact names establish name correspondence, not unchanged code or
-original-source identity.
-
-For unmatched candidates, optionally supply `left_observations` and
-`right_observations`. `procedure_info` or existing `analyze_function` Evidence
-gives exact inclusive body ranges; `read_bytes` supplies memory bytes. Observations
-must belong to the side's exact target/provider/profile and document context.
-Adjacent, consistent overlapping and partially returned reads compose by their
-observed extent; conflicting intervals remain gaps. A byte match requires every
-body byte, equal total size, equal ordered range lengths, a unique SHA-256
-fingerprint and the same known architecture. Extents are never guessed from the
-next entry, and relocations are not normalized. A larger mapped read can serve
-several observed bodies; only needed ranges need to be captured.
-
-This first slice reuses existing range observations. Stripped builds can require
-many lightweight range queries when those facts are not retained yet. Matching
-does not hide that acquisition cost or silently start those queries. Full
-decompilation is unnecessary.
-
-Repeated candidates stay `unresolved` groups without a Cartesian pair expansion.
-`only_left`/`only_right` mean no exact counterpart in the supplied observations;
-renaming, inlining, stripping, changed bytes or incomplete discovery can explain
-them. They do not prove source addition/removal. `source_coverage` explicitly keeps
-inventory completeness unknown and separately counts known byte fingerprints and
-resolved correspondence. Provider limitations remain accessible.
-
-Default `detail: "summary"` retains complete matching Evidence in MCP and returns
-counts, both identities and coverage. Query its `parent_evidence_id`:
-
-```json
-{
-  "source": {
-    "kind": "retained-evidence",
-    "evidence_id": "ev_<matching digest>"
-  },
-  "view": {
-    "kind": "function-matches",
-    "collection": "functions",
-    "states": ["matched"],
-    "sides": ["left"],
-    "fields": ["name", "body_sha256"],
-    "offset": 0,
-    "limit": 20
-  }
-}
-```
-
-`collection: "matches"` returns relation identities, states, basis and member
-counts. Large member lists are omitted by default; select `left`/`right` columns
-explicitly or page individual `functions`. Batch `match_ids`/`function_ids`, exact function `names`, state
-and side filters intersect. Mandatory identities and provenance survive column
-selection. Page coverage covers selected retained facts. Function identity binds
-inventory Evidence and the owning inventory’s `source_index`, preserving same-address alternatives.
-One validation, lazy member index and bounded recent filter are retained per
-immutable parent; no live target state is cached.
-
-When both functions already have unambiguous `analyze_function` dossiers, a matched
-relation includes `compare_functions_input` with directly usable retained
-references. Otherwise analyze just the selected canonical addresses in their
-respective targets, then compare those dossiers. Matching never claims behavioral
-equivalence. Optional informative CFG/call/string fingerprints from supplied
-dossiers connect unresolved candidate groups only. They require observed CFG,
-callees and strings, complete observed call coverage, no unresolved calls, and
-the same analysis-profile identity. Empty leaf-function buckets are excluded.
-`structural_candidate_sha256` identifies that derived candidate signature; its
-dossier link preserves the full supporting facts. Group membership does not
-assert that every member pair is a candidate or equivalent.
-
-CLI uses the same service and JSON input:
-
-```bash
-rea match-native-functions request.json \
-  --source_bundle left-bundle.json --source_bundle right-bundle.json \
-  --evidence_output matching-bundle.json --json
-```
-
-`source_bundle` resolves exact references from authenticated local bundles.
-Default summary requires `evidence_output`, retaining full matching Evidence and
-its selected source closure, including transitive Evidence links across supplied
-bundles. Missing dependencies fail with an integrity error; unrelated records
-are omitted. Publication never overwrites. Set `detail: "complete"`
-in the JSON for all groups inline. Import the bundle into MCP for views, or
-extract its matching Evidence record to a JSON file for the existing CLI
-`inspect-analysis-view` `evidence-file` source. Input bundles are unchanged.
-
-Representation admission is bounded at 96 MiB before cloning selected observations
-and expanding matching indexes and repeated per-function source links. Work yields to cancellation. No worker/provider
-concurrency is introduced; this budget is not a bound on total process RSS.
-
-The self-owned source fixture is [nativeFunctionMatching.c](https://github.com/morluto/rea/blob/main/tests/fixtures/nativeFunctionMatching.c).
-On Linux x86-64, compile with `cc -O2 -g0 -fno-pie -no-pie -DVERSION=1` and
-`-DVERSION=2`; copy the second binary and run `strip --strip-all` on that copy.
-It includes unchanged/changed code, a byte-identical rename, a removed/added
-observation, an inlined function, identical-code aliases and a renamed changed
-function with an observed call/string signature. Analyze without executing the
-fixture. Full-provider verification still needs caller-supplied Ghidra and Java.

docs/native-investigation.md

@@ -202,38 +202,8 @@ Function dossiers retain this same string evidence. Native call edges retain
 Hopper's partial `CallReference` classification and exact endpoints; detailed
 reference flags remain unavailable rather than being invented.
 Regex searches use ECMAScript Unicode syntax in a cancellable worker with a
-five-second matching deadline and a worker old-generation heap. Deadline or
-cancellation stops matching while leaving the Hopper API available. This
-release has no runtime override for that deadline. The worker requests 128
-MiB. A positive Node.js `--max-old-space-size` on the process that starts
-REA, including `NODE_OPTIONS`, overrides that request and sets the effective
-heap. `--max-old-space-size-percentage` takes precedence over that flag in
-either order. REA does not turn the percentage into a MiB, so the effective
-heap stays unestablished instead of the 128 MiB request or the absolute flag.
-The reported `NODE_OPTIONS` value is the process initial environment when that
-block can be read. A later edit to the environment is not the value Node
-applied, and an unreadable initial value leaves the effective heap
-unestablished. The launch Node options are the initial command line on Linux
-when that buffer still has a program entry, not a later edit to
-`process.execArgv`. A preload can clear that array after V8 has applied the
-flags. Setting `process.title` or `--title` overwrites the command line, so a
-buffer without a program entry leaves the effective heap unestablished.
-`--env-file` or `--env-file-if-exists` can supply `NODE_OPTIONS`
-when the initial environment has none. That file is not part of the initial
-environment block, so the effective heap stays unestablished instead of the
-128 MiB request. An initial `NODE_OPTIONS` is still used, because Node does
-not let the file replace it. A positive `--max-heap-size`, including the
-underscore form and launch `NODE_OPTIONS` on Node versions that allow it,
-sets the total heap rather than the old generation and can be lower than the
-128 MiB request. The effective old generation stays unestablished while that
-value is in effect. A zero or empty value clears it.
-`--experimental-config-file` or `--experimental-default-config-file` can set
-`nodeOptions`, including a heap percentage, from a file that is not read
-back. The effective heap stays unestablished when either flag is present,
-including when an absolute `--max-old-space-size` is also on the command
-line or in the recovered `NODE_OPTIONS`. Node accepts the config path as
-`=` or the next argument.
-Literal mode retains Unicode casefold matching.
+five-second matching deadline. Deadline or cancellation stops matching while
+leaving the Hopper API available. Literal mode retains Unicode casefold matching.
 
 ## Bounded static traces
 
@@ -246,36 +216,6 @@ sites remain distinct. A static route does not establish runtime reachability.
 Swift/closure dispatch requires resolved static references; unavailable ABI
 forms remain unknown.
 
-Incomplete reference kinds do not discard known typed calls or partial
-provider call references. A `provider_call` with `observed` resolution retains
-the provider-reported call site and endpoint without claiming generic direct,
-indirect or Objective-C dispatch semantics. Its `call_reference` evidence
-preserves the original endpoints, classification, raw provider type and
-provenance, even when the target node is a containing procedure. Hopper's
-`none`, `unknown`, `direct` and `objective_c` labels stay provider-scoped;
-unknown numeric types remain available in the raw type field. Target-only
-callee fallback uses `provider_call` with `inferred` resolution.
-
-Callee fallback adds inferred targets while each retained route keeps its
-original provider and call site. If enumeration fails, known routes remain alongside an unresolved
-failure; cancellation still terminates the request. A node-limit omission keeps
-the route's known relation while marking its target unresolved. Distinct call
-sites to the same omitted target retain separate evidence.
-Reports sharing a call site and containing target procedure retain all their
-original endpoint evidence on the shared graph edge. Different reported
-relations retain separate edges, independent of enumeration order.
-
-Session discovery describes two automatic source routes for this trace:
-`authored_ui_dispatch` needs Interface Builder decoding and dispatch metadata;
-`native_seed_call_trace` needs native address resolution, dispatch metadata and
-a call reader. Metadata can come from direct inspection or `list_names`;
-the call reader can supply typed `procedure_references` or inferred
-`procedure_callees`. An authored UI-to-handler edge remains useful without
-call expansion, and native-seed tracing can proceed without UI decoding.
-These routes add no request option or default mode, so discovery omits
-`default_mode_available`. Availability describes source prerequisites;
-the result reports the query's actual matches, coverage and failures.
-
 `trace_native_values` / `rea trace-native-values <binary> <procedure> --provider
  ghidra` composes high-p-code def-use graphs across statically resolved calls.
 Logical CALL arguments bind to recovered parameter ordinals; recovered RETURN
@@ -321,35 +261,6 @@ Mach-O fixtures check each case against source-owned return values.
 
 ## Static inspection
 
-`inspect_plist.format` describes the selected source, not plutil's conversion
-format. Sources explicitly identified as XML, binary or JSON retain those
-labels. For generic text, a bounded source-prefix probe recognizes leading XML
-markup, including UTF-8 and BOM-marked UTF-16 sources. Unidentified text and
-OpenStep plists, including a data-only value such as `<deadbeef>`, report
-`unknown` even when plutil decodes their values through an XML conversion.
-
-Binary plist inspection reads the original bytes through an owned file descriptor,
-so conversion cannot erase control characters, fractional dates, negative zero,
-or the high word of a 128-bit integer. It accepts at most 64 MiB of input and
-reserves an estimated 64 MiB decode budget before parsing; this estimate is not
-a hard process-memory bound. A refused input reports non-retryable
-`resource_constraint` with `reported_limits.maximum_input_bytes`,
-`maximum_decoded_bytes` or, for nesting deeper than 128 levels,
-`maximum_nesting_depth`. These are fixed allowances: worker limits and host
-memory do not raise them, and the unchanged request fails the same way.
-Binary-source provenance records the `file` classification without claiming a
-`plutil` conversion.
-
-A plist explicitly selected through the path input or as the active plist target
-reports an unreadable or malformed selection as `invalid_request`. A missing or
-unreadable default plist of another target reports `capability_unavailable`.
-Permission failures remain `access_denied`; output and cleanup failures retain
-their own error categories.
-
-A conversion refusal includes plutil's diagnostic from either output stream.
-`details.captured_output` retains bounded stdout/stderr excerpts, observed byte
-totals and exit status. `truncated: true` means those excerpts are incomplete.
-
 `inspect_macho.selected_architecture` identifies the exact selected lipo slice
 and its `container_file_offset` in the input file. A thin Mach-O has a known
 offset of zero; an unknown universal-slice offset stays null. The Evidence
@@ -359,9 +270,7 @@ Mach-O image. Architecture
 `file_offset` values are container-relative. Entrypoint, segment and section
 `file_offset` values retain their source meaning and are relative to the
 selected Mach-O slice. Raw load-command fields retain their original values.
-A field otool prints more than once, such as each `LC_BUILD_VERSION` tool, is
-keyed `name #n` in print order. Each `LC_LINKER_OPTION` string is keyed
-`string #n` and checked against the declared `count`. Evidence locations map the LC_MAIN entrypoint and nonempty file-backed segment
+Evidence locations map the LC_MAIN entrypoint and nonempty file-backed segment
 ranges to container offsets by adding the observed slice offset. Zero-fill
 segments do not produce file ranges. When the selected slice's container offset
 is unknown, those mapped locations are omitted with an explicit limitation;
@@ -406,22 +315,12 @@ complete observation.
   shared/cyclic references, class descriptors, raw serialized fields and
   malformed/unresolved/nil references. Missing fields stay absent; unknown
   classes are preserved. Select `root`, `offset` and `limit` explicitly.
-  Object `kind` describes the decoded archive value: data, dates and numbers
-  remain `scalar` when their JSON value uses a `$plist_type` wrapper. An actual
-  dictionary with the same fields remains `dictionary`.
-  XML must be well-formed. Data literals use
-  [CoreFoundation's raw ASCII quartet rules](https://github.com/swiftlang/swift-corelibs-foundation/blob/384ff680be7c7445fee6ce0c55e9ae11a46e07c5/Sources/CoreFoundation/CFPropertyList.c#L1588):
-  non-alphabet ASCII characters are ignored and an incomplete final quartet
-  emits no bytes. Character references retain their source spelling for data
-  decoding. Non-ASCII content, child markup and self-closing `<data/>` are format
-  failures; explicit `<data></data>` represents empty data.
   UID 0 cannot distinguish conditional nil from ordinary nil. Limits are
   64 MiB of input, 200,000 objects/references and 128 nesting levels.
   XML dictionary entries decoded as `__proto__` are omitted with an explicit
   count because REA results cannot represent that key. XML tag whitespace and
-  comments do not change that handling. XML key names combine their text and
-  CDATA segments without trimming or expanding literal CDATA entities. Other
-  values and the original archive digest are preserved.
+  comments do not change that handling. Other values and the original archive
+  digest are preserved; key interpretation follows the pinned plist decoder.
 - `decode_interface_builder` / `rea decode-interface-builder <app>` reads
   compiled storyboard and nib resources into objects, outlets, actions,
   connections and controller/class names. A full app graph is often several
@@ -467,32 +366,10 @@ complete observation.
   vtable descriptors. Records include exact virtual addresses/file offsets and
   artifact evidence. Vtable indexes are metadata word offsets; witness indexes
   start after the conformance header. Names unavailable in metadata remain null.
-  The `swift_class_vtable_descriptors` coverage counters count examined vtable
-  slots and successfully decoded slots, rather than type-section entries.
-  The `objc_class_method_ivar_metadata` counters count admitted class and
-  metaclass objects and successfully decoded objects.
   Pointers are decoded through the image's fixups:
   - `LC_DYLD_CHAINED_FIXUPS` rebases and binds, including the authenticated
     arm64e formats;
-  - legacy `LC_DYLD_INFO` rebase and bind opcodes.
-
-  A Swift conformance whose type or protocol reference is an external bind
-  keeps its name as `null` and carries the raw dyld identity in
-  `type_binding` or `protocol_binding`; that record and its facet coverage are
-  partial. Consumers of this output must handle nullable conformance names
-  and use the typed binding fields instead of substituting a symbol as a
-  display name. Indirect relative-pointer records also retain their binding
-  identity. A decoded rebase to virtual address zero remains an address; only
-  an unfixed zero in a nullable ABI field is treated as null. Incomplete or
-  conflicting fixup streams keep affected pointers unresolved; coverage reports
-  parsing and resource limits while retaining validated prefix facts.
-  Conformance records preserve the raw three-bit `type_reference_kind`. Kinds
-  0 and 1 identify direct and indirect nominal descriptors; kind 2 preserves
-  the inline Objective-C class name and its source location. Kind 3 preserves
-  an imported class binding or the local class-object address when available,
-  but class metadata/name recovery requiring the Objective-C runtime remains
-  partial. Unknown kinds retain the raw kind and reference location without
-  being treated as absent or assigned a guessed type name.
+  - legacy `LC_DYLD_INFO` bind opcodes.
 
   So an external superclass resolves from its `_OBJC_CLASS_$_` bind (for
   example `NSObject`). The `pointer_fixups` coverage facet names the mechanism.
@@ -519,31 +396,6 @@ complete observation.
   coroutine tables, and inherited overrides, have explicit unsupported or
   partial coverage. Other providers retain the
   existing symbol-based inventory with its narrower coverage.
-  Symbols without a reported location remain in that inventory: Swift symbol
-  `address` and Objective-C `implementation_address` are null. An empty provider
-  address is retained as `reported_address` in the symbol's evidence, whose
-  location also remains unknown. Nonempty provider address syntax is preserved.
-
-  Session discovery reports this workflow available when the bound provider
-  offers direct metadata inspection or a `list_names` symbol inventory. The
-  workflow tries direct metadata first and uses the symbol fallback only when
-  that operation is unavailable; runtime failures remain failures rather than
-  being replaced by symbol-only results.
-
-`get_objc_classes` keeps names from the provider inventory. It coalesces rows
-only when their exact selected-image pointer slots decode to the same class
-import, including its binding stream, raw library ordinal, resolved library, weak status, and addend. A literal filter is
-applied to the original names before that join; if the filter selects only an
-alias, the output keeps that exact row. `identity_coverage` distinguishes a
-complete selected-inventory scan from partial, unsupported, and unknown cases.
-Recognized Mach-O formats outside the native metadata reader's support retain
-the provider's class labels with unknown import identity; malformed headers and
-read failures remain errors.
-The join also requires matching whole-artifact digests and matching provider-
-owned selected-image facts: container, byte range, full raw CPU type/subtype,
-and FAT table digest when present. A missing or overridden loader selection
-remains unknown; the result describes agreement on the selected artifact image,
-not an atomic observation of a running process or whole-program class coverage.
 
 ## Native desktop observation
 
@@ -560,17 +412,11 @@ decrement scrolling and text-value entry, or bounded waits. No global event
 injection is used. Unsupported AX actions fail explicitly. The result preserves
 ordered before/after captures and gaps; an action may have occurred before a
 post-action capture fails. Application state is left as-is; REA does not attempt
-to restore it. Failed or cancelled scenarios return a typed error with the
-collected report in `partial_observation`, including ordered step outcomes.
-Cancellation preserves the caller's reason and remains observable through helper
-cleanup. A later abort does not replace an earlier helper or output failure.
-Cleanup failures retain their runtime owner until a confirmed cleanup retry.
+to restore it.
 
 Scenarios accept caller-selected action lists and accessibility node counts.
-One wait step stays capped at 180000 ms. That cap has no runtime override.
-The operation deadline is `native_ui_deadline_ms` (omitted means 180000 ms)
-and does not raise the wait-step cap. The complete scenario result has a
-64 MiB output budget. Screenshots are scaled to
+Individual waits cannot exceed the operation's 180-second deadline, and the
+complete scenario result has a 64 MiB output budget. Screenshots are scaled to
 at most 2,048 pixels and captured only for the selected window. REA compiles one
 owned helper per scenario, removes its temporary compiler cache and stops its
 helper on cancellation. It does not launch or own the selected application. UI
@@ -603,11 +449,6 @@ The run ends when the process exits, `max_events` entries are recorded,
 Bounded termination reports partial coverage. REA checks process termination
 using a launch-time OS start identity; if ownership or cleanup cannot be
 verified, the result or error preserves that uncertainty. The result reports:
-Launch errors keep the fact that LLDB created a process separate from whether
-it remains alive. An exited `SBProcess` is reported as exited only after LLDB
-confirms that state; unresolved ownership remains retained for cleanup retry.
-Cancellation observed while output and Evidence are finalized returns partial
-cancellation Evidence, even if the target has already exited.
 
 - the outcome, exit status and captured stdout/stderr (1 MiB kept per stream
   while excess bytes are drained and counted without growing capture files).
@@ -638,11 +479,6 @@ with partial coverage. Available output prefixes remain inline; their byte
 counts are observed lower bounds when final drain counters are unavailable.
 The original failure classification and cleanup uncertainty remain separate.
 An interrupted journal row is ignored with an explicit limitation.
-If the trace completed before cancellation or runtime-directory cleanup failed,
-the retained observation also keeps its exit status, termination proof, launch
-identity, breakpoint results and final stream counters. Those fields remain
-absent when the interrupted producer did not report them; partial coverage alone
-does not mean that every retained fact is incomplete.
 
 Only entries are observed: return values, floating-point and stack arguments,
 and inlined or `objc_direct` calls are not. The target runs with the current
@@ -659,7 +495,7 @@ is present. A denied trace reports the `debugger-attach-denied` reason.
 Install a Ghidra 12.1.x release and the 64-bit full JDK it declares, then configure REA to
 use them. Ghidra analysis supports Linux x64/arm64 and macOS x64/arm64; each installation requires
 the matching native decompiler. Experimental Windows x64 P0 admits native
-x86, x86-64, ARMNT (Thumb-2) and ARM64 PE applications and DLLs, plus explicitly selected
+x86 and x86-64 PE applications and DLLs, plus explicitly selected
 [raw NMOS 6502 images](raw-binary.md#nmos-6502) with a caller-supplied load address,
 on fixed local NTFS volumes. Other raw CPU families remain unsupported on Windows.
 The boundary uses bundled Job Object ownership, protected runtime DACLs, and
@@ -720,12 +556,6 @@ digests identify the original serialized bytes.
 ## Keyed archive integer precision
 
 The archive reader observes XML number element types and binary number markers.
-XML values and their number facts are interpreted together from the validated
-DOM and its original scalar source spans. Hexadecimal `<integer>` text, including
-an optional sign, retains its value;
-`<real>` text and CDATA segments are combined without inferring text from nested
-elements. Real character references expand outside CDATA; integer and date
-literals use raw source text.
 Integers beyond the exact range of a JSON number are reported with the original
 decimal text as `{ "$plist_type": "integer", "decimal": "<exact digits>" }` when
 that source value can be associated unambiguously. Integral real values remain
@@ -734,9 +564,9 @@ markers remain decoded with an explicit precision limitation. The limitation
 also counts observed unsafe integer literals, including observations outside the
 selected object page. Incomplete supplemental metadata produces an explicit
 precision note without rejecting an archive accepted by the byte decoder.
-Malformed XML scalar content becomes an explicit unknown rather than a prefix
-number, guessed timestamp, or tag-only boolean. These unknowns do not disable
-exact association for unrelated observed numbers. Nonnumeric
+Mixed XML number content (comments, CDATA, processing instructions or child
+elements) and integer text the supplemental reader cannot classify disable exact
+association and retain decoded numbers with that precision note. Nonnumeric
 `UID` and `CF$UID` dictionary values remain ordinary data and are projected
 recursively; numeric reference markers retain their original representation.
 
@@ -745,63 +575,11 @@ Exact and ambiguous value counts describe emitted root/object value instances;
 a root and an object may contain the same value. Archive digests identify the
 original bytes.
 
-Interface Builder's XML and binary plist archives use the same number metadata
-and exact-decimal representation for emitted node attributes. Projection follows
-object and connection classification, so archive IDs, UID links and graph counts
-keep their meaning. Precision limitations name the source document. Unsafe
-integer-literal counts cover the archive, including fields not emitted as node
-attributes; exact and ambiguous projection counts cover emitted attribute values.
-Integral reals stay numbers, and ambiguous or incompletely observed values retain
-explicit precision limitations. Before plist decoding, the existing aggregate
-decode budget reserves estimated room for number metadata and attribute
-projection; these estimates are not a hard process-memory bound. Native
-NIBArchive decoding is unchanged by this plist-specific representation.
-
-Dates are reported as `{ "$plist_type": "date", "iso8601": "<timestamp>" }`.
-XML dates require a complete UTC spelling with fixed two-digit month, day and
-time fields; short, negative and extended years are interpreted as UTC year
-fields within JavaScript's date range. Unsupported calendar fields (including
-leap seconds) and out-of-range dates remain explicit unknowns. REA does not
-emulate CoreFoundation's normalization of overflowing calendar fields. Invalid
-dates returned by other decoders retain `{ "$plist_type": "date", "iso8601": null }`
-with a counted limitation. `inspect_plist` and Interface Builder decoding use
-the same projection. Binary plist decoding refuses a reachable date whose marker
-is not `0x33`; date and numeric payloads must end before the offset table.
-Valid overlapping object records retain their independent source values. A valid `0x33` date is
-reported with an ISO-8601 timestamp only when its float64 seconds are exactly
-the canonical encoding of that millisecond instant. Any other finite binary
-date uses `{ "$plist_type": "date", "iso8601": null }` and the counted
-limitation; the archive bytes remain the source of the instant.
-
-A negative-zero real is reported as `{ "$plist_type": "real", "value": "-0" }`
-because a JSON number cannot carry the sign of zero. `inspect_plist` and
-`inspect_keyed_archive` count these values in a limitation, and Interface
-Builder node attributes use the same value. Positive zero and integer zero,
-including an `<integer>-0</integer>` literal, remain the number `0`.
-
-Known non-finite reals are reported as
-`{ "$plist_type": "real", "value": "nan" | "+infinity" | "-infinity" }`.
-These are canonical numeric labels, not a claim about original source spelling.
-Binary IEEE reals retain NaN versus signed infinity; NaN payload bits and sign
-are not represented in the JSON value, and the original bytes remain the source
-for those details. XML CFPropertyList literals (`nan`, `+infinity`, `-infinity`,
-`infinity`, `inf`, `+inf`, `-inf`, case-insensitively) decode to the same known
-values. Case and aliases normalize; original archive bytes retain source text.
-
-XML scalars whose identity cannot be established use
-`{ "$plist_type": "unknown", "element": "integer" | "real" | "date" | "true" | "false", "literal": "<original content>", "reason": "invalid-literal" | "unsupported-markup" | "unrepresentable" }`.
-A counted limitation accompanies these wrappers. Literal content retains its
-original entity spelling, markup and line endings. Whole XML documents must
-still pass strict well-formedness checks. Empty integer, real and date elements
-are unknown scalars; boolean elements must be empty. Complete decimal/exponent
-reals and signed decimal/hexadecimal integers accept their respective native
-leading whitespace but reject trailing text. Arbitrary-precision integers
-remain an intentional REA extension beyond CoreFoundation's integer range.
-Finite real spellings that overflow the numeric representation remain unknown,
-rather than becoming observed infinities. Known non-finite and unresolved scalar
-values have separate counts. This replaces the former prefix-number and
-incomplete-metadata fallback for malformed XML numeric content. Native
-`inspect_plist` uses the same projection for plutil's XML conversion.
+Dates are reported as `{ "$plist_type": "date", "iso8601": "<timestamp>" }`. A
+date the decoder cannot represent, such as an XML date with a year beyond 9999
+or a negative year, is reported as `{ "$plist_type": "date", "iso8601": null }`
+with a counted limitation; the rest of the plist or archive is still decoded.
+`inspect_plist` and Interface Builder decoding use the same projection.
 
 ## Locate a byte signature
 

docs/pcap-analysis.md

@@ -58,20 +58,11 @@ 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.
 Ambiguous addresses remain in a separate inventory. Protocol distribution counts
-exact nonempty `frame.protocols` stack strings. Frames for which TShark reports
-an empty stack, including zero-length packets, still contribute to the packet
-count without adding a protocol row. An all-empty stack inventory can have
-complete examined coverage; it does not establish the absence of network traffic.
-TLS SNI is recorded handshake metadata,
+exact `frame.protocols` stack strings. TLS SNI is recorded handshake metadata,
 not process identity or proof of the destination's authenticity.
 
 All examined inventories are retained within the resource budget; no fixed

docs/process-capture.md

@@ -38,10 +38,6 @@ supervision on macOS. REA removes that directory when it exits. REA does not
 install Xcode, Command Line Tools, or other software. Capability checks prepare
 this helper before reporting macOS capture as available.
 
-Stopping process sampling or cancelling an ownership query waits for its issued
-inspection command to exit. Closing a macOS ownership reader rejects new queries
-and waits for admitted helper commands before removing their executable directory.
-
 ## Capture a command
 
 For a small first capture, save this as `scenario.json`:
@@ -245,15 +241,6 @@ follow also remain unknown. Partial enumeration of one root does not erase
 known effects in another, and unavailable content hashes do not by themselves
 make path absence unknown.
 
-When a follow-up read fails after an entry's metadata was observed, the
-snapshot keeps unaffected observations and records an `entry_unavailable`
-enumeration omission with the root-aliased path and system error code.
-Successfully observed identity replacements use `identity_changed` with a null
-system code. Unstable symlink targets are omitted; already observed directory
-metadata remains available. The affected root stays incomplete, so omitted
-entries do not prove deletion. A path missing at its initial lookup remains an
-observed absence. Cancellation and unexpected I/O failures still stop capture.
-
 Terminal frame `data` is the comparison text after the selected normalization.
 New captures also preserve `raw_data` when normalization changes a PTY chunk;
 otherwise `data` is already the original text. Older captures may lack the
@@ -432,26 +419,13 @@ Every capture requires `truncation_details`, with separate accounting for:
   imply incomplete path enumeration.
 - `process`: sampling limit and whether sampling ended partially. Coverage
   remains `sampled`, including when that limit was not exhausted.
-  `sampling_failures` counts failed read observations plus at most one
-  unfinished pass interrupted by sampler shutdown. `first_sampling_failure`
-  retains the first attributed read diagnostic, with shutdown context appended
-  when applicable; interruption alone has an explicit shutdown diagnostic.
-  Denied or failed procfs reads mark
-  sampling partial while preserving readable process rows and thread children;
-  a process with unreadable identity is not attributed. Expected process-exit
-  races are separate from failed observations. Shutdown counts only when it
-  interrupts a read or leaves traversal unfinished; a completed pass does not
-  become partial merely because the sampler stops. Completed rows
-  remain available and issued reads settle before final coverage is returned.
 
 The aggregate `truncated` flag summarizes these observations. Comparisons retain
 results for unaffected dimensions and mark affected dimensions unknown; an
 incomplete capture cannot locate the first divergence across all dimensions.
 Trace assertions use coverage for the sources they select, so an assertion
 about complete raw terminal output need not fail because rendered snapshots
-were omitted. A trace difference applies to the dimensions identified by its
-diagnostic; unrelated dimensions retain their own comparison, including unknown
-coverage. Captures missing `truncation_details` are rejected on import;
+were omitted. Captures missing `truncation_details` are rejected on import;
 preserve them as historical files and recapture for current comparisons.
 `limits.file_bytes` is already the cumulative whole-file hashing budget,
 independent of `limits.output_bytes`, which bounds retained terminal content.
@@ -459,62 +433,12 @@ Each filesystem checkpoint starts with a fresh `file_bytes` budget across all
 selected roots; it is not a per-file allowance. File contents are read in
 64 KiB chunks for hashing and are not embedded in capture Evidence.
 
-Ownership inspections bind run-token reads to native start identities and retain
-related generations through reparenting, group changes, omitted rows, and cleanup
-retries. A host without native identity reads still token-checks process-table
-rows that appear only in a launcher-exit refresh before reporting that group
-clean or publishing an empty lineage. A matching token authorizes a signal only
-for a group whose leader carries the same token. A matching token whose leader
-is absent, or an unreadable token for a still-live new row, stays unresolved. A
-readable foreign token is not signaled. An unreadable row that has exited by
-the confirmation read does not hide a new row in that confirmation table, and a
-group proven while revalidating another owned group is signaled in the same
-cleanup. A matched row that changes parent or group on the confirmation read
-is token-checked again. A PID whose token was already read is read again
-on the next confirmation even when its parent and group return to the
-pre-exit values. A PID whose first token was foreign is read again
-on that table, because the PID alone does not identify the process. A PID
-from the pre-exit table is read again when its parent or group changes, and
-an unchanged pre-existing row that was never token-read stays unread. Lineage
-publishes one row for each PID. Confirmation reads are bounded; a table that keeps producing unreadable
-replacements stays unresolved. That refresh does not retain a ledger
-for a later attempt that never observes the launcher. Lineage reads a row again
-when its parent, group, or launcher-tree membership changes, and it reads a
-token again on the next refresh even when those fields are unchanged. The
-launcher is read on every lineage refresh; a missing, unowned, or
-relation-changed launcher PID is not published as a verified lineage. A
-descendant absent from the latest refresh is omitted. An
-ancestor move cannot leave a foreign descendant inside a verified result. A
-group that reappears after cleanup already processed it is revalidated once;
-another appearance stays unresolved. The captured run keeps
-one evidence owner through settlement and cleanup.
-An absent or changed token leaves a previously related generation unresolved;
-current token proof is still required before signaling. Swept cleanup verifies the
-remaining family after its group signals. Coverage is bounded by the native
-snapshots and generations inspected; sampled group IDs select candidates.
-
 When the host withholds an unrelated process’s ownership token, REA leaves that
 process untouched and records its PID and reason in `cleanup.unverified_processes`
 and process residual unknowns. Successful cleanup verifies the owned group;
 it does not attribute those unrelated processes. Related or otherwise unexplained
 unreadable processes still prevent successful cleanup.
 
-Failed cleanup retains its exact resources for the owning session to retry.
-The CLI retries before projecting its error; MCP retries pending cleanup before
-admitting another capture and during session cleanup. Once every attributed
-owner confirms release, the live error status clears `cleanup_incomplete`.
-The original failure, observations and `cleanup_report` retain the facts from
-the earlier attempt, including any cleanup failure recorded then.
-
-Snapshot file handles, directory handles, and the selected executable reader
-follow the same ownership rule. A failed close preserves completed observations
-and any primary read failure; it cannot turn a completed digest into a successful
-capture with unresolved cleanup. Interrupted snapshots retain examined entries
-with incomplete coverage in `partial_observation`, alongside the failure.
-File-handle retry uses the exact retained owner. After a directory close rejects,
-Node does not expose enough handle validity to authorize another native close;
-REA retains that unresolved owner and blocks further captures in the session.
-
 On macOS, changing a Node process's `process.title` can make its run token
 unreadable. Node documents that [setting the title overwrites argv memory](https://nodejs.org/download/release/v24.18.0/docs/api/process.html#processtitle).
 With the pinned toolchain, a live child retained a readable start identity
@@ -545,15 +469,6 @@ missing or relative SDK/compiler path fails with an actionable prerequisite
 error before compilation. An incompatible installation reports the compiler's
 bounded diagnostics; REA does not repair or replace the toolchain.
 
-The compile deadline is `REA_SWIFTC_COMPILE_TIMEOUT_MS`. An omitted value is
-120,000 ms, and accepted values are integers from 1 to 2,147,483,647. REA reads
-the variable from the environment that starts the process and keeps that
-deadline for every helper compile in that process. Restart REA to apply a
-change; the next ownership-helper compile uses the new value. A timeout names
-the effective milliseconds. Invalid values fail configuration validation at
-startup. Embedded compiler diagnostics are cut at 512 bytes, and this release
-has no runtime override for that excerpt.
-
 For example, select paths from your existing Xcode or Command Line Tools
 installation **before** entering an enforced write boundary:
 

docs/python-packaged-applications.md

@@ -1,128 +0,0 @@
-# Python packaged applications
-
-REA statically inventories PyInstaller executables with an appended CArchive.
-`inspect_artifact` and `extract_artifact` share the same reader through CLI and
-MCP. They read archive bytes without launching the application. Bytecode
-source decompilation, encrypted PYZ recovery, zipapp and PEX analysis are outside
-this capability.
-
-## Facts and focused queries
-
-The root occurrence's `format_metadata` records the CArchive layout (2.0 or
-2.1), archive and cookie offsets, table extent, entry count, raw Python version,
-normalized major/minor when known, library name and encryption marker. Member
-metadata retains the original name, table index, type, compression flag,
-relative offset and known directory record extent. Logical paths use archive
-path rules; the source name retains its spelling, including backslashes.
-`relative_offset` is relative to the CArchive start for CArchive rows, or to
-the decoded PYZ image for PYZ rows. A CArchive directory record starts at
-`archive_start + toc_offset + directory_record_offset`; its size is
-`directory_record_size`. PYZ row directory extents remain unknown.
-
-Namespace packages remain directories. Their `relative_offset` and
-`compressed_size` preserve any payload declared by older producers, while
-`declared_size` is zero because no bytecode is materialized for a namespace.
-Every declared span must end before the PYZ table of contents.
-PYZ `compression_flag` is derived from storage: nonempty payloads are compressed,
-including legacy namespaces; an empty namespace has no compressed payload.
-
-CArchive type `o` entries are runtime options. They are metadata occurrences,
-with no content artifact or extractable file. Their query paths are
-`__pyinstaller__/runtime-options/<table index>`; the option text is
-`format_metadata.source_name`. Repeated declarations retain distinct occurrence
-identities. These paths do not claim output filesystem names.
-
-Type `d` entries are multipackage dependencies. They are also metadata, under
-`__pyinstaller__/dependencies/<table index>`, and never materialize an empty file.
-The reader preserves the raw reference and splits its first colon into
-`dependency_archive` and `dependency_member`. `dependency_status` remains
-`unresolved`, or `invalid-reference` with unknown parts for malformed references.
-`external_dependency_count` summarizes these declarations. REA does not open
-another executable or claim its contents are available. A real file with the
-same logical path as metadata remains independently extractable.
-Both declaration types require empty payloads and no compression. Their query
-paths do not participate in filesystem collision checks, directory ancestry or
-source-map target lookup; their parent identifies the declaring container.
-Complete authenticated inventory page sets preserve producer identities in any
-merge order, including metadata/file aliases. Malformed TOC diagnostics name the
-table index; original names remain available in the supplied artifact.
-Path failures use bounded escaped previews and report the original length;
-accepted paths and retained source names are not shortened.
-
-Request `detail: "summary"` for a compact inspection, then query retained
-Evidence with `inspect_analysis_view`. An inventory view can select
-`collection: "occurrences"`, `entry_kinds: ["metadata"]`, exact logical paths or
-occurrence IDs, requested `fields`, and `offset`/`limit`. Filters intersect;
-identities, parent Evidence and coverage survive projection. Full inventory
-Evidence remains available for export. A compact reply reduces returned context;
-it still performs the complete member inventory and hashing work.
-Focused views add calls and tool-schema costs. A complete small inventory can
-cost less overall; prefer compact delivery when the full member graph would
-overwhelm the answer.
-
-```bash
-rea inspect-artifact /absolute/path/hello --detail summary --evidence_output /absolute/new/evidence.json --json
-rea extract-artifact /absolute/path/hello --json
-```
-
-## Decoding and evidence limits
-
-Inventory hashes members individually through bounded streams. Stored PYZ
-images use descriptor ranges; outer-compressed images stream to private files,
-which the reader owns through cleanup and any cleanup retry. Extraction binds
-the selected carrier to its inventoried digest and checks source identity and
-state before and after reading. It does not retain expanded module bodies.
-Opaque outer-compressed images reuse that verified private image when opened,
-instead of inflating the carrier again. Direct source spans describe stored
-CArchive bytes; decompressed content has no direct span even when its encoded
-and decoded sizes coincide. Original offsets and compression remain metadata.
-
-Only the PYZ header and marshal directory are loaded for listing. PYZ tables
-have a 16 MiB budget; CArchive tables have a 32 MiB budget. Parsed facts have a
-32 MiB serialized budget. Projected entries share a 64 MiB retained budget,
-including metadata, bookkeeping and conservative reservations for namespace
-objects and possible case-collision annotations at each path component. These
-reservations happen before normalization or trie allocation.
-Outer-compressed PYZ images have a separate per-reader capacity of 128 private
-files, bounding retained inodes and image identities. The complete image count
-is admitted before any temporary file is created; excess images return a
-capacity failure. This is a resource policy, not a PyInstaller format limit.
-Only a zero-byte read establishes EOF; short successful descriptor reads fill
-the bounded range. Compressed members must consume their complete declared
-input span; trailing junk and concatenated streams are refused.
-Plaintext expansion has an aggregate archive-derived budget. Exceeding a budget
-returns a resource failure.
-
-Supported final Python bytecode magic values cover Python 3.7 through 3.14.
-Supported marshal directory values are lists, tuples, strings, integers and
-bytes. An unsupported magic or directory stays an opaque member with a
-limitation and `pyz_status: "opaque"`; its module contents remain unknown.
-Any opaque PYZ makes producer traversal coverage unknown, including retained
-summaries and exhausted queries. Per-archive reasons remain on the opaque
-occurrences; the coverage observation summarizes their count without repeating
-every limitation. An empty result does not establish module absence.
-Observed `pyz_python_magic` bytes remain available even when their Python version
-is unknown.
-The directory declares compressed module lengths, so uncompressed declared
-sizes and source spans inside decoded data remain unknown.
-
-PYZ modules receive a derived 16-byte `.pyc` header from their own supported
-magic. CArchive bytecode receives that header only when every sibling PYZ magic
-and the cookie's Python version agree. Otherwise it retains its original bytes
-and `bytecode_header: "unknown"`. `bytecode_magic` and graph derivation edges
-identify synthesized headers; member digests cover the resulting derived files.
-These headers do not establish successful execution or decompilation.
-
-The nonempty CArchive Python module `pyimod00_crypto_key` (`m`/`M`) is recorded
-as an encryption marker; a same-named data file or script is not. Affected
-PYZ blobs are reported without decoding; extraction refuses encrypted entries.
-The raw PYZ container remains readable and hashable, including when its module
-table is opaque. Its marker stays in metadata and opaque child coverage stays
-unknown; extracting the container does not decrypt its payloads.
-The marker also applies to nonempty legacy namespace payloads. Empty namespaces
-have no payload to encrypt and retain a null encryption source.
-
-Detection searches the last 16 MiB for a cookie, allowing a trailing macOS code
-signature within that bound. Member offsets are relative to the archive start:
-cookie position plus cookie size minus package length. Native bootloader
-analysis remains available through the native tools.

docs/raw-binary.md

@@ -25,31 +25,27 @@ rea inspect-native-load-image /absolute/path/to/ecu.bin --target-format raw-bina
 }
 ```
 
-`architecture` is one of `x86`, `x86_64`, `arm`, `arm64`, `6502`, or `m68k`. `entry_point` is a
+`architecture` is one of `x86`, `x86_64`, `arm`, `arm64`, or `6502`. `entry_point` is a
 hexadecimal address of the form `0x…`. The complete file is mapped starting at
 that address, and Ghidra seeds an `entry` function there before auto-analysis.
-ARM and AArch64 entries must be 4-byte aligned; m68k entries must be 2-byte
-aligned; x86 and 6502 entries may be byte-aligned.
+ARM and AArch64 entries must be 4-byte aligned; x86 and 6502 entries may be byte-aligned.
 For 6502, the entry and complete mapped file must fit within `0x0000..0xffff`;
 images that cross the 16-bit boundary are rejected before provider startup.
-For m68k, the mapping must fit within `0x0..0xffffffff`.
 `open_binary` and an open `binary_session` return the canonical `entry_point`
 for raw targets so callers can verify the selected mapping directly.
 Omitted `format` keeps header-based detection; architecture and entry without
 `format=raw-binary` are rejected.
 
-Ghidra imports a private snapshot with `BinaryLoader` and these generic
-languages and compiler specifications. Each family has one fixed byte order:
-m68k is big-endian and the others are little-endian.
+Ghidra imports a private snapshot with `BinaryLoader` and these little-endian
+generic languages and compiler specifications:
 
-| architecture | language_id           | compiler_spec_id |
-| ------------ | --------------------- | ---------------- |
-| x86          | `x86:LE:32:default`   | `gcc`            |
-| x86_64       | `x86:LE:64:default`   | `gcc`            |
-| arm          | `ARM:LE:32:v7`        | `default`        |
-| arm64        | `AARCH64:LE:64:v8A`   | `default`        |
-| 6502         | `6502:LE:16:default`  | `default`        |
-| m68k         | `68000:BE:32:default` | `default`        |
+| architecture | language_id          | compiler_spec_id |
+| ------------ | -------------------- | ---------------- |
+| x86          | `x86:LE:32:default`  | `gcc`            |
+| x86_64       | `x86:LE:64:default`  | `gcc`            |
+| arm          | `ARM:LE:32:v7`       | `default`        |
+| arm64        | `AARCH64:LE:64:v8A`  | `default`        |
+| 6502         | `6502:LE:16:default` | `default`        |
 
 Compiler specifications select analysis conventions; they do not identify the
 original compiler or ABI of a headerless target. Ghidra's x86 languages do not
@@ -110,40 +106,12 @@ unchanged source bytes and complete runtime cleanup. Windows requires the
 matching native addon; the POSIX provider path has not been exercised by the
 Windows run.
 
-## Motorola 68000
-
-```bash
-rea function /absolute/path/to/image.bin 0x1000 --target-format raw-binary --architecture m68k --entry-point 0x1000 --provider ghidra --json
-rea inspect-native-load-image /absolute/path/to/image.bin --target-format raw-binary --architecture m68k --entry-point 0x1000 --provider ghidra --json
-```
-
-Select only headerless big-endian 68000-family code with a known, even entry at
-file offset 0. Ghidra's `68000:BE:32:default` language decodes the 68040
-superset in the 32-bit `ram` address space. Instructions that a real MC68000
-would not execute are therefore not rejected, and 68020, 68030, CPU32, and
-ColdFire programs are not admitted as those variants. Addresses are not masked
-to the MC68000 24-bit bus. Evidence preserves `architecture: "m68k"`, the
-selected language, entry, file digest, and verified source mapping. Register and
-calling conventions are analysis conventions, not a recovered source ABI.
-
-This lane does not interpret Amiga hunks, Atari ST, or other container headers,
-cartridge or console memory maps, or bank switching. REA does not read the
-initial stack pointer and reset vector from the first eight bytes; select the
-entry explicitly. Windows Ghidra P0 does not admit m68k.
-
-`npm run verify:ghidra:m68k` uses a source-owned 22-byte fixture written as
-annotated hex in the verifier, so it needs no assembler. The lane checks real
-CLI/MCP load-image parity, mapped bytes, a decoded call, decompilation by address
-and file offset, misaligned and out-of-range mappings, unchanged source bytes and
-runtime cleanup. It has been run with Ghidra 12.1.4 on macOS; Linux has not been
-exercised.
-
 ## Limitations
 
 - Headers are not discovered from file bytes. This increment does not guess
   load addresses, vector tables, or memory maps.
-- Big-endian ARM, Thumb-only, Cortex-M, and other Ghidra processor variants are
-  unsupported. m68k is the only big-endian family.
+- Big-endian, Thumb-only, Cortex-M, and other Ghidra processor variants are
+  unsupported.
 - Reset vectors, memory-mapped I/O, and firmware boot sequences are not
   emulated.
 - Independent load-image verification covers source identity, mapped file

docs/readme/README_ar.md

@@ -1,7 +1,7 @@
 <div align="center">
 
 [English](../../README.md) · [简体中文](README_zh.md) · [繁體中文](README_zh-TW.md) · [日本語](README_ja.md) · [한국어](README_ko.md) · [Türkçe](README_tr.md) · [Русский](README_ru.md) · [Tiếng Việt](README_vi.md) · [ไทย](README_th.md) · [Deutsch](README_de.md) · [Español](README_es.md) · [Français](README_fr.md) · [Українська](README_uk.md) · [Polski](README_pl.md) · [Português (Brasil)](README_pt-BR.md) · **العربية** · [فارسی](README_fa.md) · [Bahasa Indonesia](README_id.md) · [Italiano](README_it.md)
-· [Ελληνικά](README_el.md) · [മലയാളം](README_ml.md)
+· [Ελληνικά](README_el.md)
 
 # REA: هندسة عكسية لأي شيء
 
@@ -146,13 +146,11 @@ npx rea-agents@latest setup
 | شيفرة EVM البايتية              | محددات التوجيه، وإزاحات البايتات، والمعاملات المستنتجة، وقابلية تغيير الحالة                                | مدخل محلي يحمل بايتات خامًا أو تمثيلًا سداسيًا عشريًا على Linux x64؛ [دليل EVM دون تشغيل](../evm-bytecode.md)                      |
 | Rust binaries                   | Embedded cargo-auditable dependency list                                                                   | [Rust binaries](../rust-binaries.md)                                                                                          |
 | أعطال Linux المسجّلة             | سجلات note الخام، ومسجّلات المعالج/الإشارات لكل خيط مسجّل، وترشيحات اختيارية لخرائط الذاكرة                     | pwntools يوفّره المستدعي على Linux x64؛ GDB/pwndbg اختياريان؛ [الأعطال المسجّلة](../recorded-crashes.md)                         |
-| تثبيتات سطح المكتب              | عائلات وقت التشغيل، والملفات الداعمة، وعلامات المكونات، والخطوات التالية                                     | فحص محدود للملفات والترويسات；[تطبيقات سطح المكتب](../desktop-applications.md)                                                |
 | JavaScript / Electron           | الوحدات، وعمليات الاستيراد، وخرائط المصدر، والمسارات، وIPC، وعلاقات إضافات الشيفرة الأصلية                    | Node.js وnpm؛ [تحليل التطبيقات](../javascript-application-workflows.md)                                                       |
 | المواقع                         | بنية الصفحة، والسكربتات، وملاحظات الشبكة، ولقطات الشاشة المطلوبة                                            | متصفح من عائلة Chrome؛ [تحليل المتصفح](../browser-observation.md)                                                             |
 | تسجيلات الشبكة المحفوظة          | الطلبات، والاستجابات، ومحتويات الحمولة المتاحة، ومواضعها في المصدر                                          | HAR؛ وmitmdump على Linux لتسجيلات mitmproxy بصيغتها الأصلية؛ [دليل تسجيلات الشبكة](../web-network-captures.md)                   |
 | التقاط الحزم                    | نقاط النهاية وDNS وTLS SNI وتوزيع البروتوكولات وطلبات HTTP                                                  | tshark وcapinfos يوفّرهما المُستدعي؛ [دليل pcap](../pcap-analysis.md)                                                           |
 | تجميعات .NET                    | البيانات الوصفية، وتعليمات CIL، واعتماديات الشيفرة الأصلية المعلنة، ومقارنات البناء                         | فحص ثابت؛ [دليل الشيفرة المُدارة](../managed-code-analysis.md)                                                                 |
-| PyInstaller                     | CArchive, PYZ, Python bytecode                                                                             | Static inspection; [Python packaged applications](../python-packaged-applications.md)                                         |
 | حزم Android APK                 | تصريحات ملف manifest، والأصناف، والدوال الناتجة عن فك الترجمة، والمراجع                                     | JADX دون واجهة رسومية وJDK كامل على Linux/macOS/Windows x64؛ [دليل Android](../android-analysis.md)                           |
 | أجهزة Android                   | الأجهزة والحزم والعمليات والسجلات والدامبات ولقطات الشاشة ونقل APK/الملفات                                   | adb يوفّره المُستدعي (محاكي أو جهاز)؛ [دليل ADB](../adb-device-analysis.md)                                                     |
 | مشاريع JEB                      | وحدات المشروع من المحرك وبصمات المصنّفات والكود الزائف للأنواع/الدوال                                        | عميل JEB يبدأه المُستدعي ويقدّم MCP، ويُختار عبر REA_JEB_MCP_URL؛ [دليل JEB](../jeb-analysis.md)                                 |
@@ -168,7 +166,7 @@ npx rea-agents@latest setup
 
 <a id="choosing-a-deep-analysis-provider"></a>
 
-تختلف صيغ ملفات الشيفرة الأصلية والأنظمة المضيفة المدعومة باختلاف الموفّر. راجع [إعداد Hopper وGhidra](../installation.md#hopper)، و[دليل IDA](../ida-provider.md)، [Kuna](../kuna-provider.md)، و[دعم Ghidra التجريبي على Windows](../windows-ghidra-p0.md). يدعم Ghidra أيضًا [تحليل DOS ذي 16 بت](../ghidra-dos.md). لاختيار الموفّر، راجع [دليل CLI](../cli.md#choose-a-provider). تحقّق من [توفر الميزات في الإصدارات](../installation.md#released-package-and-main) للميزات المضافة بعد أحدث إصدار على npm.
+تختلف صيغ ملفات الشيفرة الأصلية والأنظمة المضيفة المدعومة باختلاف الموفّر. راجع [إعداد Hopper وGhidra](../installation.md#hopper)، و[دليل IDA](../ida-provider.md)، و[دعم Ghidra التجريبي على Windows](../windows-ghidra-p0.md). يدعم Ghidra أيضًا [تحليل DOS ذي 16 بت](../ghidra-dos.md). لاختيار الموفّر، راجع [دليل CLI](../cli.md#choose-a-provider). تحقّق من [توفر الميزات في الإصدارات](../installation.md#released-package-and-main) للميزات المضافة بعد أحدث إصدار على npm.
 
 ## دراسات الحالة
 
@@ -267,8 +265,6 @@ npx rea-agents@latest setup
 
 - [التثبيت والإعداد](../installation.md): تسجيل الوكلاء، وتهيئة الموفّرين، والتحديثات، وإلغاء التثبيت.
 - [الجاهزية واستكشاف الأخطاء](../installation.md#check-readiness-for-your-task): تشخيص وكيل أو محرك تحليل محدد.
-- [CUDA / HIP](../gpu-code-objects.md)
-- [GGUF / safetensors](../model-artifacts.md)
 - [CLI وEvidence](../cli.md): الأوامر، واختيار الموفّر، واللقطات، والاستيراد/التصدير، وحالات الخروج.
 - [عقود MCP](../mcp-contracts.md) و[تعليمات الوكلاء](../mcp-prompts.md): نتائج الأدوات، والجلسات، والاستقصاءات الموجّهة.
 - [كتالوج الأدوات](../mcp-contracts.md#generated-catalog): قائمة الأدوات والموفّرين وأوامر CLI المولّدة أثناء البناء.
@@ -278,7 +274,7 @@ npx rea-agents@latest setup
 
 ## سجل النجوم
 
-🎉 **300,000 نجمة على GitHub — شكرًا لكم!**
+🎉 **200,000 نجمة على GitHub — شكرًا لكم!**
 
 شكرًا لكل من يستخدم REA، ويبلّغ عن الأخطاء، ويقترح ميزات، ويختبر إصدارات البناء، ويساهم بالإصلاحات.
 

docs/readme/README_de.md

@@ -1,7 +1,7 @@
 <div align="center">
 
 [English](../../README.md) · [简体中文](README_zh.md) · [繁體中文](README_zh-TW.md) · [日本語](README_ja.md) · [한국어](README_ko.md) · [Türkçe](README_tr.md) · [Русский](README_ru.md) · [Tiếng Việt](README_vi.md) · [ไทย](README_th.md) · **Deutsch** · [Español](README_es.md) · [Français](README_fr.md) · [Українська](README_uk.md) · [Polski](README_pl.md) · [Português (Brasil)](README_pt-BR.md) · [العربية](README_ar.md) · [فارسی](README_fa.md) · [Bahasa Indonesia](README_id.md) · [Italiano](README_it.md)
-· [Ελληνικά](README_el.md) · [മലയാളം](README_ml.md)
+· [Ελληνικά](README_el.md)
 
 # REA: Alles reverse-engineeren
 
@@ -146,13 +146,11 @@ REA benötigt Node.js 22.x (>=22.19), 24.x (>=24.11) oder 26+ sowie npm. Zusätz
 | EVM-Bytecode                        | Dispatch-Selektoren, Byte-Offsets, abgeleitete Argumente und Veränderbarkeit des Zustands                       | Lokale Eingabe mit Rohbytes oder Hexdarstellung unter Linux x64; [Offline-EVM-Leitfaden](../evm-bytecode.md)                                |
 | Rust binaries                       | Embedded cargo-auditable dependency list                                                                        | [Rust binaries](../rust-binaries.md)                                                                                                        |
 | Aufgezeichnete Linux-Abstürze       | Unverarbeitete Note-Einträge, Register/Signale aller aufgezeichneten Threads und optionale Zuordnungskandidaten | Vom Aufrufer bereitgestelltes pwntools unter Linux x64; optional GDB/pwndbg; [aufgezeichnete Abstürze](../recorded-crashes.md)              |
-| Desktop-Installationen              | Laufzeitkandidaten, Quelldateien, Komponenten und nächste Schritte                                              | Begrenzte Verzeichnis- und Headerprüfung；[Desktop-Anwendungen](../desktop-applications.md)                                                 |
 | JavaScript / Electron               | Module, Imports, Source Maps, Routen, IPC und Beziehungen zu nativen Add-ons                                    | Node.js und npm; [Anwendungsanalyse](../javascript-application-workflows.md)                                                                |
 | Websites                            | Seitenstruktur, Skripte, Netzwerkbeobachtungen und angeforderte Screenshots                                     | Ein Browser aus der Chrome-Familie; [Browseranalyse](../browser-observation.md)                                                             |
 | Gespeicherte Netzwerkaufzeichnungen | Anfragen, Antworten, zugängliche Nutzdaten und Quellpositionen                                                  | HAR; mitmdump unter Linux für Aufzeichnungen im nativen mitmproxy-Format; [Leitfaden zu Netzwerkaufzeichnungen](../web-network-captures.md) |
 | Paketerfassungen                    | Endpunkte, DNS, TLS SNI, Protokollverteilung und HTTP-Anfragen                                                  | Vom Aufrufer bereitgestellte tshark- und capinfos-Binaries; [pcap-Leitfaden](../pcap-analysis.md)                                           |
 | .NET-Assemblies                     | Metadaten, CIL-Anweisungen, deklarierte native Abhängigkeiten und Build-Vergleiche                              | Statische Untersuchung; [Leitfaden für verwalteten Code](../managed-code-analysis.md)                                                       |
-| PyInstaller                         | CArchive, PYZ, Python bytecode                                                                                  | Static inspection; [Python packaged applications](../python-packaged-applications.md)                                                       |
 | Android-APKs                        | Manifest-Deklarationen, Klassen, dekompilierte Methoden und Verweise                                            | JADX ohne grafische Oberfläche und ein vollständiges JDK unter Linux/macOS/Windows x64; [Android-Leitfaden](../android-analysis.md)         |
 | Android-Geräte                      | Geräte, Pakete, Prozesse, Logs, Dumps, Bildschirmaufnahmen sowie APK- und Dateiübertragungen                    | Vom Aufrufer bereitgestelltes adb (Emulator oder Gerät); [ADB-Leitfaden](../adb-device-analysis.md)                                         |
 | JEB-Projekte                        | Engine-gestützte Projekteinheiten, Artefakt-Prüfsummen und Pseudokode von Typen/Methoden                        | Ein vom Aufrufer gestarteter JEB-Client mit MCP, ausgewählt über REA_JEB_MCP_URL; [JEB-Leitfaden](../jeb-analysis.md)                       |
@@ -168,7 +166,7 @@ Statische JavaScript- und .NET-Untersuchungen lesen die bereitgestellten Dateien
 
 <a id="choosing-a-deep-analysis-provider"></a>
 
-Native Formate und unterstützte Hostsysteme unterscheiden sich je nach Provider. Siehe [Hopper- und Ghidra-Einrichtung](../installation.md#hopper), den [IDA-Leitfaden](../ida-provider.md), [Kuna](../kuna-provider.md) und die [experimentelle Ghidra-Unterstützung unter Windows](../windows-ghidra-p0.md). Ghidra unterstützt auch [16-Bit-DOS-Analyse](../ghidra-dos.md). Die Provider-Auswahl beschreibt der [CLI-Leitfaden](../cli.md#choose-a-provider). Prüfe die [Verfügbarkeit in Releases](../installation.md#released-package-and-main) für Funktionen, die seit der neuesten npm-Version hinzugekommen sind.
+Native Formate und unterstützte Hostsysteme unterscheiden sich je nach Provider. Siehe [Hopper- und Ghidra-Einrichtung](../installation.md#hopper), den [IDA-Leitfaden](../ida-provider.md) und die [experimentelle Ghidra-Unterstützung unter Windows](../windows-ghidra-p0.md). Ghidra unterstützt auch [16-Bit-DOS-Analyse](../ghidra-dos.md). Die Provider-Auswahl beschreibt der [CLI-Leitfaden](../cli.md#choose-a-provider). Prüfe die [Verfügbarkeit in Releases](../installation.md#released-package-and-main) für Funktionen, die seit der neuesten npm-Version hinzugekommen sind.
 
 ## Fallstudien
 
@@ -265,8 +263,6 @@ Beginne mit den [praxisnahen Anleitungen](https://rea.tools/de/guides/) auf der
 
 - [Installation und Einrichtung](../installation.md): Agentenregistrierung, Provider-Konfiguration, Updates und Deinstallation.
 - [Bereitschaft und Fehlerbehebung](../installation.md#check-readiness-for-your-task): Diagnose eines bestimmten Agenten oder einer Analyse-Engine.
-- [CUDA / HIP](../gpu-code-objects.md)
-- [GGUF / safetensors](../model-artifacts.md)
 - [CLI und Evidence](../cli.md): Befehle, Provider-Auswahl, Snapshots, Import/Export und Exit-Status.
 - [MCP-Kontrakte](../mcp-contracts.md) und [Agenten-Prompts](../mcp-prompts.md): Werkzeugergebnisse, Sitzungen und geführte Untersuchungen.
 - [Werkzeugkatalog](../mcp-contracts.md#generated-catalog): Beim Build erzeugtes Inventar von Werkzeugen, Providern und CLI-Befehlen.
@@ -276,7 +272,7 @@ Melde Sicherheitslücken gemäß [SECURITY.md](../../SECURITY.md).
 
 ## Sternverlauf
 
-🎉 **300.000 GitHub-Sterne – vielen Dank!**
+🎉 **200.000 GitHub-Sterne – vielen Dank!**
 
 Danke an alle, die REA nutzen, Fehler melden, Funktionswünsche äußern, Builds testen und Fehlerbehebungen beitragen.