fix(cli): retain correction details across browser commands

Fold the complementary implementation from #2247 into the earlier #2230 proposal, retaining the original contribution history. Co-authored-by: LouisChen <3361008+chqcjq@users.noreply.github.com>
fix(cli): retain browser and Inspector input correction details
2026-10-13 02:11:17 +08:00 · 2026-10-12 08:31:22 -07:00
1064 changed files with 37353 additions and 132933 deletions
@@ -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: "41"
+  version: "40"
 ---

 # REA
@@ -61,47 +61,12 @@ explicit path or endpoint and do not need it.
  consult the NativeAOT workflow in `references/native-and-artifacts.md` for
  optional metadata recovery and its supported host/layout boundary.
 - User-owned browser page already open: `list_browser_targets`.
- Fiddler Everywhere traffic or a native `.saz` capture: read the
-  [Fiddler workflow](references/runtime-observation.md#fiddler-everywhere-traffic-debugging).
-  Inspect saved SAZ with `inspect_web_network_capture` and `format: "saz"`;
-  connect Everywhere's separate MCP server for live traffic.
- Retained HAR/SAZ/native mitmproxy/aioquic qlog capture: `inspect_web_network_capture`. Select
+- Retained HAR/native mitmproxy capture: `inspect_web_network_capture`. Select
  original record ordinals when useful; inspect producer fields and byte/number
  sidecars without fetching recorded URLs or claiming live attribution. See
  [historical captures](https://github.com/morluto/rea/blob/main/docs/web-network-captures.md) for the exact upstream
-  profile and credential exclusions. Qlog support starts with aioquic 1.5.0
-  JSON 0.3; stream coverage and endpoint loss declarations do not recover bodies
-  or establish network loss. Prefer detail summary, then kind qlog trace/stream
-  pages; select one trace, stream ID and direction for contribution/range pages.
-  Facts retain all-recorded-events-before-selection scope. Other qlog layouts
-  and PCAP correlation are unsupported.
+  profile and credential exclusions.
 - User-owned Electron runtime already open: `list_electron_targets`.
- Packet-field discovery: `inspect_packet_fields` searches installed protocols
-  and field names/types before choosing fields for `inspect_packet_capture`.
-  Query/page the relevant records; registrations do not establish observed traffic.
- Recorded packet captures: `inspect_packet_capture` with selected TShark fields,
-  display filters and decode-as rules. Requires Linux, util-linux prlimit and `REA_TSHARK_COMMAND`; see
-  [capture guide](https://github.com/morluto/rea/blob/main/docs/packet-captures.md).
-  Packet limits count input packets before filtering. Output defaults to 50 matching
-  frames; use `match_offset` / `match_limit` for later pages, or explicit null
-  limit for complete matching output. Preserve the source digest across pages.
-  This does not perform live capture.
-  For address/DNS/SNI/protocol summaries use `inspect_pcap_capture` with MCP
-  detail summary, then retained kind pcap pages. Requires Wireshark 4.x tshark
-  and capinfos, with Linux prlimit or Windows Job Objects; see
-  [packet summaries](https://github.com/morluto/rea/blob/main/docs/pcap-analysis.md).
-  Select an exact DNS question for address pages; page exhaustion does not prove
-  network completeness. This reads recordings and does not acquire traffic.
- Decoder discovery: `inspect_signal_decoders` searches installed decoder IDs
-  or selected decoder help, including channels and options. Query and page the
-  relevant details before choosing settings; this does not scan hardware.
- Recorded logic/signal traces: `decode_signal_recording` with explicit decoder,
-  channel and protocol settings. On Linux with util-linux prlimit, supply sigrok-cli 0.7.2 through
-  `REA_SIGROK_COMMAND`; see [recording guide](https://github.com/morluto/rea/blob/main/docs/signal-recordings.md).
-  Output defaults to 50 literal lines; select annotation classes and page with
-  `line_offset` / `line_limit`, or explicit null for all remaining output.
-  Window counts are display lines, not annotations or samples. Preserve source digests across pages.
-  This reads existing files; it does not acquire hardware signals.
 - Explicit local WebAssembly artifact: `inspect_wasm_artifact`. Supply WABT 1.0.42
  through `REA_WABT_BIN_DIRECTORY`; retain exact byte/tool identity and decoded WAT.
  Select JavaScript glue and candidate paths explicitly and preserve URL/path
@@ -110,11 +75,7 @@ explicit path or endpoint and do not need it.
 - Explicit local EVM bytecode carrier: `inspect_evm_interface` with caller-selected
  `raw` or `hex` encoding. Preserve carrier/decoded digests and treat selectors,
  argument strings and mutability as inferred candidates; this performs no chain
-  lookup or target execution. For the complete inferred interface without hex or
-  duplicate stdout, discover support and select `detail: "summary"`; complete
-  Evidence stays retained under its original identity. Use the returned
-  `parent_evidence_id` for exact function or `bytecode_hex`/stdout/stderr pages.
-  Candidate coverage does not establish interface completeness. See the
+  lookup or target execution. See the
  [EVM bytecode guide](https://github.com/morluto/rea/blob/main/docs/evm-bytecode.md).
 - Embedded Go compiler, module or build-setting metadata: `inspect_go_binary`
  with the explicit local file. This built-in target-free inspection requires no
@@ -122,15 +83,6 @@ 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).
-
- Explicit local SQLite database snapshot: `inspect_sqlite_database`. Inspect
-  with Node.js 24.x >=24.15 or 26+ providing native SQLite limits. Read schema
-  first (compact inventory by default), or select an exact ordinary table
-  and `columns` when rows are needed. Defaults are selected-table schema and
-  20 rows; request `schema_scope: "database"` for the complete stored schema. Preserve both database and existing sibling WAL identity; row samples
-  report truncation and have unspecified order. Use a quiescent snapshot rather
-  than assuming a live database/WAL pair was copied atomically. See the
-  [SQLite guide](https://github.com/morluto/rea/blob/main/docs/sqlite-databases.md).
 - Explicit Linux ELF file for offline layout, symbols, relocations or static
  mitigation evidence: `inspect_binary_layout`. This target-free operation uses
  caller-supplied pwntools without opening a disassembler database. Preserve its
@@ -46,7 +46,7 @@ rea setup --client codex --dry-run --json
 Use the current supported client's ID: `claude_code`, `claude_desktop`, `codex`,
 `cursor`, `gemini_cli`, `windsurf`, `devin`, `opencode`, `antigravity`,
 `copilot_cli`, `commandcode`, `qwen_code`, `vscode`, `trae`, `grok_build`, `omp`, `pi`,
-`hermes`, `qoder`, `zcode`, `dsh`, or `grok_bot`. If unknown, inspect `doctor --json` before choosing a
+`hermes`, `zcode`, `dsh`, or `grok_bot`. If unknown, inspect `doctor --json` before choosing a
 scope. `grok_bot` uses a chat registration step rather than local `mcp.json`.
 For unsupported clients, use version-pinned manual stdio registration or CLI.

@@ -11,21 +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.

-## SQLite snapshots
-
-Use `inspect_sqlite_database` with an explicit local database snapshot for its
-schema and optional rows from one exact ordinary table. It requires Node.js
-24.x >=24.15 or 26+ with the native `DatabaseSync.limits` API. It also consumes the
-existing sibling `-wal`; retain both original digests when citing its result.
-Default output is a compact inventory; a selected table expands only its own
-schema and samples 20 rows. Select `columns` to avoid irrelevant or large cells,
-and request `schema_scope: "database"` only for complete schema details.
-Choose `row_limit` when a finite sample is useful and keep truncation and
-unspecified row order explicit. Virtual tables, shadow tables and views are
-schema facts, not row-read targets. REA inspects private copies and leaves
-the source files untouched; obtain a coherent quiescent database/WAL snapshot
-before inspection. See [SQLite snapshots](https://github.com/morluto/rea/blob/main/docs/sqlite-databases.md).
-
 ## Recorded Linux crashes

 Use `inspect_recorded_crash` with an explicit Linux x86-64 ELF core path to
@@ -83,14 +68,6 @@ names, the native API record, and value-flow summaries. Pseudocode offsets and l
 code units; use the returned `next_offset` for continuation. Provider limitations
 and unavailable facts remain explicit; the complete parent Evidence is retained.

-`inspect_macho` on a large framework returns megabytes of imports and exports.
-Select `detail: "summary"` for slice identity, UUID and per-collection counts,
-then page rows with `view: {kind: "macho", facet: "exports", offset: 0, limit: 64}`
-and `normalized_result.parent_evidence_id`. Facets are entrypoints,
-architectures, build_metadata, load_commands, dependencies, imports, exports,
-segments and provenance. `source_exhaustive: false` means unreturned symbols
-may exist.
-
 To see which functions or Objective-C methods a Mach-O actually calls in one
 run, use `observe_native_calls` with explicit breakpoints and a bounded
 `duration_ms`/`max_events`. It launches a new process under LLDB, so the target
@@ -119,8 +96,6 @@ loaded bytes, file mappings, relocations and the entry against the immutable
 snapshot. Keep `mismatch` and `unsupported` explicit. Verified import covers the
 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.
-
 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
@@ -145,18 +120,6 @@ assembly. Keep managed/native boundaries and unavailable reconstruction facts
 explicit. A bring-your-own reconstruction oracle is separate from the canonical
 parser and must not become an implicit setup dependency.

-For identity/classification questions, `inspect_managed_artifact` can explicitly
-select `detail: "summary"` on the first MCP call. It retains complete metadata
-and returns a linked overview with full classification/evidence, nullable
-module/MVID, frameworks, metadata coverage/issues/limitations and returned-row
-counts. Default complete requests remain unchanged. Read original rows with
-`inspect_analysis_view`, source `normalized_result.parent_evidence_id`, and
-`view: {kind: "managed", collection: "attributes", offset: 0, limit: 16}`.
-Collections are `references`, `resources` and `attributes`. Paging does not
-repeat parsing. Returned-row exhaustion
-does not prove complete metadata or absence under partial/unavailable coverage;
-preserve build-local tokens and their artifact/MVID scope.
-
 ### .NET NativeAOT

 NativeAOT binaries contain native machine code, so ordinary CIL decompilers
@@ -204,9 +167,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 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
+Use `extract_artifact` when materialized files are needed. It takes no arguments
+and 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
 destination. No separate permission grant is needed.
@@ -26,18 +26,3 @@ passive browser/Electron Evidence exist. Prefer captured-source digest identity;
 report path/digest disagreement as a mismatch and preserve ambiguity. Explicit
 path mappings are inference inputs and never broaden filesystem or CDP authority.
 A bundle observed at runtime does not prove every contained module executed.
-
-## Fiddler Everywhere traffic debugging
-
-For large saved captures, request `detail: "summary"`, then page retained Evidence
-with `inspect_analysis_view` and `view: {kind: "capture", detail: "preview", offset: 0, limit: 20}`.
-Select complete record pages only for needed headers, metadata or payloads; views
-read the historical parent without repeating capture decoding.
-
-Inspect native `.saz` snapshots with `inspect_web_network_capture` and
-`format: "saz"`; encrypted archives are unsupported. For live
-traffic analysis, connect Everywhere's separate MCP server and use its
-advertised session tools with an explicit `sessionsSource` (`LiveTraffic` or
-`AgentCalls`). Preserve existing sessions and filters when inspecting a
-recorded run. See the [capture and MCP guide](https://github.com/morluto/rea/blob/main/docs/web-network-captures.md)
-for the workflow and Telerik's public setup and traffic-debugging skills.
@@ -3,6 +3,3 @@

 # Windows command fixtures retain their native line endings.
 *.cmd text eol=crlf
-
-# Preserve whitespace in original upstream licensing texts.
-licenses/npm-runtime-notices.txt whitespace=-blank-at-eol
@@ -1,8 +1,5 @@
 blank_issues_enabled: false
 contact_links:
-  - name: Contribution scope and integration requirements
-    url: https://github.com/morluto/rea/blob/main/CONTRIBUTING.md#contribution-scope
-    about: Check supported capabilities, excluded workflows, and the fail-closed integration rule before proposing a feature.
  - name: REA Documentation
    url: https://github.com/morluto/rea#readme
    about: Read the README and AGENTS.md for usage guides and configuration details.
@@ -1,5 +1,5 @@
 name: Design discussion
-description: Discuss an REA architecture, provider, contract, or scope decision
+description: Resolve an REA architecture, provider, or contract question before implementation
 title: "[Design] "
 labels:
  - enhancement
@@ -9,12 +9,7 @@ body:
    attributes:
      value: |
        Use this for a substantial provider, public/persisted contract, or
-        authority-boundary decision. One question and a short explanation are
-        enough to start. Choose "Not sure yet" where needed; maintainers can help
-        with technical details, alternatives, and verification.
-
-        Read the [contribution scope](https://github.com/morluto/rea/blob/main/CONTRIBUTING.md#contribution-scope).
-        Unresolved boundaries block integration, not opening a discussion.
+        authority-boundary decision. Keep one decision per discussion.

  - type: checkboxes
    id: before-submitting
@@ -23,16 +18,14 @@ body:
      options:
        - label: I searched the open and closed issues and pull requests for a related discussion.
          required: true
-        - label: I understand the [contribution scope](https://github.com/morluto/rea/blob/main/CONTRIBUTING.md#contribution-scope) must be reviewed before integration; open questions are welcome here.
-          required: true
-        - label: This discussion does not include credentials, private samples, or sensitive target data.
+        - label: I removed credentials, tokens, private paths, and sensitive target data.
          required: true

  - type: textarea
    id: decision
    attributes:
      label: Decision needed
-      description: What would you like maintainers to help decide? A short question is enough.
+      description: State the exact question maintainers need to resolve.
      placeholder: Should REA ... or ...?
    validations:
      required: true
@@ -41,57 +34,23 @@ body:
    id: context-evidence
    attributes:
      label: Context and evidence
-      description: Explain the problem or motivation. If you have evidence, distinguish observed behavior from ideas or guesses.
-    validations:
-      required: true
-
-  - type: dropdown
-    id: target-interaction
-    attributes:
-      label: Expected interaction with targets
-      description: >-
-        Select all known effects, including upstream tool behavior. Add "Not sure
-        yet" if anything is unclear. Use "No target interaction" only on its own.
-        These selections help discussion and do not establish scope approval.
-      multiple: true
-      options:
-        - Read existing files or captured data
-        - Launch or attach to a process
-        - Inject instrumentation or run scripts/code
-        - Change process memory or registers
-        - Write or change files/configuration
-        - Contact network services
-        - Recover protected code or work around protections
-        - No target interaction (documentation or usability only)
-        - Not sure yet
+      description: Explain why the decision is needed now. Separate observed behavior, derived evidence, and inference.
    validations:
      required: true

  - type: textarea
    id: boundary-invariants
    attributes:
-      label: Boundary details (optional)
-      description: >-
-        If known, clarify target selection, selected effects, provider boundaries,
-        non-goals, or evidence invariants. Leave blank if you need help identifying
-        them. Do not include private samples or proof-of-authorization documents.
+      label: Boundary and invariants
+      description: Identify the owning layer, provider/bridge boundary, artifact or evidence invariants, and any process or authorization constraints.
+    validations:
+      required: true

  - type: textarea
    id: options
    attributes:
      label: Options and tradeoffs
-      description: Optional approaches or tradeoffs. One idea is enough; maintainers can help compare alternatives.
-
-  - type: dropdown
-    id: verification-readiness
-    attributes:
-      label: Verification available so far
-      description: Pick the closest match. An idea without samples or test results is welcome.
-      options:
-        - Idea only; I need help defining checks
-        - I can suggest a sample or manual check
-        - I have a prototype or observed results
-        - Not sure yet
+      description: Compare a small number of viable approaches, including platform, compatibility, safety, evidence, and maintenance costs.
    validations:
      required: true

@@ -99,10 +58,9 @@ body:
    id: success-criteria
    attributes:
      label: Success criteria and open questions
-      description: >-
-        Optional expected output, sample, possible check, or unresolved question.
-        A complete test plan is not required to start; maintainers and implementers
-        will resolve material verification gaps before integration.
+      description: State what outcome would settle the decision and list only unresolved questions that could change the choice.
+    validations:
+      required: true

  - type: textarea
    id: references
@@ -8,13 +8,9 @@ body:
  - type: markdown
    attributes:
      value: |
-        Describe one problem and the outcome you would like. Short answers are
-        welcome. Choose "Not sure yet" wherever needed; you do not need code, a
-        finished design, or a complete test plan to propose an idea.
-
-        Read the [contribution scope](https://github.com/morluto/rea/blob/main/CONTRIBUTING.md#contribution-scope).
-        Maintainers can help resolve scope and technical questions. Unresolved
-        boundaries block integration, not opening a request for discussion.
+        Keep one primary capability or workflow outcome per request. For a
+        substantial provider, public contract, or architecture change, explain
+        the decision maintainers need to make before implementation.

  - type: checkboxes
    id: before-submitting
@@ -23,9 +19,7 @@ body:
      options:
        - label: I searched the open and closed issues and pull requests for a related proposal.
          required: true
-        - label: I understand the [contribution scope](https://github.com/morluto/rea/blob/main/CONTRIBUTING.md#contribution-scope) must be reviewed before integration; open questions are welcome here.
-          required: true
-        - label: This request does not include credentials, private samples, or sensitive target data.
+        - label: I removed credentials, tokens, private paths, and sensitive target data.
          required: true

  - type: dropdown
@@ -42,7 +36,6 @@ body:
        - MCP or agent integration
        - Documentation
        - Other
-        - Not sure yet
    validations:
      required: true

@@ -50,7 +43,7 @@ body:
    id: current-limitation
    attributes:
      label: Current limitation
-      description: What are you trying to understand or do, and what is difficult today? A short example is enough.
+      description: What user or agent workflow is blocked, ambiguous, or unnecessarily difficult today?
    validations:
      required: true

@@ -58,69 +51,23 @@ body:
    id: use-cases
    attributes:
      label: Use cases
-      description: Optional additional examples of applications, targets, or callers. Leave blank if covered above.
+      description: Give concrete applications, targets, callers, or investigation workflows. Explain why current tools are insufficient.
+    validations:
+      required: true

  - type: textarea
    id: desired-outcome
    attributes:
      label: Desired outcome and success criteria
-      description: What would a useful result look like? Describe the output or behavior you want; implementation details are optional.
-      placeholder: For a selected APK, show whether it is packed and include the detection evidence.
-    validations:
-      required: true
-
-  - type: dropdown
-    id: target-interaction
-    attributes:
-      label: Expected interaction with targets
-      description: >-
-        Select all known effects, including upstream tool behavior. Add "Not sure
-        yet" if anything is unclear. Use "No target interaction" only on its own.
-        These selections help discussion and do not establish scope approval.
-      multiple: true
-      options:
-        - Read existing files or captured data
-        - Launch or attach to a process
-        - Inject instrumentation or run scripts/code
-        - Change process memory or registers
-        - Write or change files/configuration
-        - Contact network services
-        - Recover protected code or work around protections
-        - No target interaction (documentation or usability only)
-        - Not sure yet
+      description: Describe observable behavior, inputs, outputs, evidence, and compatibility criteria that would make this useful.
    validations:
      required: true

  - type: textarea
    id: boundaries
    attributes:
-      label: Target and scope details (optional)
-      description: >-
-        If known, name the target/platform, clarify selected effects, or list a
-        non-goal or scope question. You can leave this blank; maintainers can help.
-        Do not include private samples or proof-of-authorization documents.
-
-  - type: dropdown
-    id: verification-readiness
-    attributes:
-      label: Verification available so far
-      description: Pick the closest match. An idea without samples or test results is welcome.
-      options:
-        - Idea only; I need help defining checks
-        - I can suggest a sample or manual check
-        - I have a prototype or observed results
-        - Not sure yet
-    validations:
-      required: true
-
-  - type: textarea
-    id: verification
-    attributes:
-      label: Verification details (optional)
-      description: >-
-        Share an expected output, a possible check, or existing results if you have
-        them. Self-owned or appropriately licensed samples can help, but are not
-        required to open a request. Do not attach private or sensitive data.
+      label: Authority boundaries and non-goals
+      description: Call out process execution, target mutation, provider licensing, evidence provenance, supported platforms, and work that should remain out of scope.

  - type: textarea
    id: alternatives
@@ -1,27 +1,17 @@
 name: Portable build cache
-description: Restore portable Turbo build outputs from the current run or cross-run cache.
+description: Reuse Turbo build outputs without serializing verification jobs.
 inputs:
  save:
    description: Save newly built outputs after the job succeeds.
    default: "false"
-  build_cache_artifact:
-    description: Reuse portable Turbo outputs uploaded by the current workflow run.
-    default: ""
 runs:
  using: composite
  steps:
-    - name: Download portable build outputs from this workflow run
-      if: inputs.build_cache_artifact != ''
-      uses: actions/download-artifact@v4
-      with:
-        name: ${{ inputs.build_cache_artifact }}
-        path: .turbo/cache/
    - name: Resolve portable build task hashes
      id: plan
-      if: inputs.build_cache_artifact == ''
      shell: bash
      env:
-        BUILD_CACHE_PREFIX: rea-portable-build-v2-${{ runner.os }}-${{ runner.arch }}-${{ hashFiles('.npmrc', '.nvmrc', 'package-lock.json') }}
+        BUILD_CACHE_PREFIX: rea-portable-build-v1-${{ runner.os }}-${{ runner.arch }}-${{ hashFiles('.npmrc') }}
      run: |
        npm run --silent test:prepare -- --dry=json |
          node --input-type=module -e '
@@ -35,19 +25,16 @@ runs:
            }).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'
+      if: inputs.save != 'true'
      uses: actions/cache/restore@v4
      with:
        path: .turbo/cache/
        key: ${{ steps.plan.outputs.key }}
-        restore-keys: ${{ steps.plan.outputs.prefix }}
    - name: Restore and save portable build outputs
-      if: inputs.build_cache_artifact == '' && inputs.save == 'true'
+      if: inputs.save == 'true'
      uses: actions/cache@v4
      with:
        path: .turbo/cache/
        key: ${{ steps.plan.outputs.key }}
-        restore-keys: ${{ steps.plan.outputs.prefix }}
@@ -19,39 +19,17 @@ describe the use case and observable outcome. -->
 <!-- Explain the chosen approach, why it fits REA's architecture, and what is
 intentionally not included. -->

-Follow the [contribution scope](https://github.com/morluto/rea/blob/main/CONTRIBUTING.md#contribution-scope).
-Unresolved scope, authority, side effects, or required verification block
-integration. Link the required maintainer scope decision for new providers or
-capabilities involving target execution, injection, mutation, or protection
-recovery; ordinary fixes within existing boundaries may state "not applicable".
-Draft PRs may leave the scope decision pending and the final review checklist
-unchecked. Maintainers can help resolve open questions.
-
 ## Contract and boundary impact

-<!-- Short answers are welcome. Complete applicable lines; mark unresolved facts as "unknown".
-Use "none" or "not applicable" only when established. -->
+<!-- Complete the applicable lines; use "none" or "not applicable" explicitly. -->

 - Semantic owner and earliest changed stage:
- Contribution scope fit and linked maintainer decision:
 - CLI and MCP/tool-catalog contract:
 - Provider, bridge, target-format, or platform compatibility:
 - Evidence, artifact, provenance, or reconstruction contract:
- Target selection, authority, upstream behavior, and cleanup details (if applicable):
+- Process execution, authorization, cleanup, or containment impact:
 - Generated metadata (`docs/public/product-catalog.json`), package, or installation impact (CI generates and validates ignored catalogs and `skills/`; edit authored instructions in `.agents/skills/reverse-engineer-anything/` and never commit build outputs):

-Expected effects (check known effects; use documentation-only on its own).
-Unchecked items do not establish absence; leave uncertainties visible.
-
- [ ] Read existing files or captured data.
- [ ] Launch or attach to a process.
- [ ] Inject instrumentation or run scripts/code.
- [ ] Change process memory, registers, files, or configuration.
- [ ] Contact network services.
- [ ] Recover protected code or work around protections.
- [ ] Documentation or usability only; no target interaction.
- [ ] Not sure yet; investigation or maintainer guidance needed.
-
 ## Evidence and regression coverage

 <!-- State whether evidence is executed, source-derived, or proposed. For fixes,
@@ -90,13 +68,9 @@ limits, security/privacy/containment implications, and meaningful proof gaps. --
 - Package or release metadata impact:
 - Security, privacy, process, or containment review:

-## Before merge
-
-<!-- Draft PRs may leave pending items unchecked. Resolve material scope and
-authority questions before integration. -->
+## Review checklist

 - [ ] This PR addresses a concrete problem or an agreed enhancement.
- [ ] Material scope and authority questions are resolved, and any required maintainer scope decision covers the final diff.
 - [ ] The PR has one focused outcome and the title follows `type(scope): outcome`.
 - [ ] Related issue is linked, or the reason for not linking one is stated above.
 - [ ] Tests cover changed observable behavior and meaningful failure paths.
@@ -1,18 +0,0 @@
-name: Full PR qualification
-
-on:
-  pull_request:
-    branches: [main, "release/*"]
-    types: [labeled]
-
-permissions:
-  contents: read
-  actions: read
-
-jobs:
-  qualification:
-    name: Qualify labeled PR revision
-    if: github.event.label.name == 'ci:full'
-    uses: ./.github/workflows/ci.yml
-    with:
-      source_sha: ${{ github.sha }}
@@ -1,46 +0,0 @@
-name: CI timings
-
-on:
-  schedule:
-    - cron: "17 * * * *"
-  workflow_dispatch:
-
-concurrency:
-  group: ci-timings-${{ github.repository }}
-  cancel-in-progress: false
-
-permissions:
-  contents: read
-  actions: read
-
-jobs:
-  report:
-    name: Collect recent completed workflow attempts
-    runs-on: ubuntu-latest
-    timeout-minutes: 5
-    steps:
-      # Consume only API data and execute batch code from the trusted default branch.
-      - uses: actions/checkout@v4
-        with:
-          ref: ${{ github.event.repository.default_branch }}
-          persist-credentials: false
-      - uses: actions/setup-node@v4
-        with:
-          node-version-file: .nvmrc
-      - name: Record queue, execution, and matched step timing
-        continue-on-error: true
-        env:
-          GH_TOKEN: ${{ github.token }}
-          CI_REPOSITORY: ${{ github.repository }}
-        run: node scripts/ci/job-timings-batch.mjs
-      - name: Upload CI timing artifacts
-        if: always() && hashFiles('.cache/ci-job-timings/*') != ''
-        continue-on-error: true
-        uses: actions/upload-artifact@v4
-        with:
-          name: ci-job-timings-batch
-          path: .cache/ci-job-timings/
-          include-hidden-files: true
-          if-no-files-found: error
-          overwrite: true
-          retention-days: 14
@@ -5,44 +5,42 @@ on:
    branches: [main]
  pull_request:
    branches: [main, "release/*"]
-  schedule:
-    - cron: "23 0-2,4-23 * * *"
-    - cron: "23 3 * * *"
  workflow_dispatch:
-  workflow_call:
-    inputs:
-      source_sha:
-        description: Exact qualification source; must match the caller revision.
-        required: true
-        type: string

 permissions:
  contents: read

 concurrency:
-  # Complete qualification finishes even while main receives more pushes.
-  # Main feedback also finishes, coalescing newer pushes to one pending run.
-  # Scheduled/manual main runs coalesce to one active and the latest pending;
-  # release and label-triggered qualification use exact-revision groups.
-  group: ci-${{ (github.event_name == 'schedule' || github.event_name == 'workflow_dispatch' || inputs.source_sha != '' || contains(github.event.pull_request.labels.*.name, 'ci:full')) && 'qualification' || 'feedback' }}-${{ inputs.source_sha || github.event.pull_request.number || github.ref }}
-  cancel-in-progress: ${{ github.event_name == 'pull_request' && inputs.source_sha == '' && !contains(github.event.pull_request.labels.*.name, 'ci:full') }}
+  group: ci-${{ github.event.pull_request.number || github.ref }}
+  # The latest main push verifies the full tree, including earlier changes.
+  # Publication uses its own release workflow and concurrency group.
+  cancel-in-progress: true

 env:
  HUSKY: "0"

 jobs:
+  pr-title:
+    name: Conventional PR title
+    if: github.event_name == 'pull_request'
+    runs-on: ubuntu-latest
+    steps:
+      - name: Validate title for Release Please
+        env:
+          PR_TITLE: ${{ github.event.pull_request.title }}
+        run: >-
+          node -e 'const title = process.env.PR_TITLE ?? "";
+          const conventional = /^(?:feat|fix|docs|refactor|perf|test|build|ci|chore|revert)(?:\([a-z0-9._/-]+\))?!?: .+/u;
+          if (!conventional.test(title)) {
+            console.error("PR title must use Conventional Commits, for example: feat: add historical source import");
+            process.exit(1);
+          }'
+
  changes:
    name: Classify changes
    runs-on: ubuntu-latest
-    timeout-minutes: 5
-    permissions:
-      contents: read
-      actions: read
    outputs:
-      tier: ${{ steps.plan.outputs.tier }}
-      qualification_run_id: ${{ steps.qualification.outputs.run_id }}
      code: ${{ steps.plan.outputs.code }}
-      sqlite: ${{ steps.plan.outputs.sqlite }}
      runtime: ${{ steps.plan.outputs.runtime }}
      package: ${{ steps.plan.outputs.package }}
      apple: ${{ steps.plan.outputs.apple }}
@@ -61,58 +59,26 @@ jobs:
      nativeaot: ${{ steps.plan.outputs.nativeaot }}
      website: ${{ steps.plan.outputs.website }}
      matrix: ${{ steps.plan.outputs.matrix }}
-      test_selection: ${{ steps.plan.outputs.test_selection }}
    steps:
      - uses: actions/checkout@v4
        with:
-          ref: ${{ inputs.source_sha || github.sha }}
          fetch-depth: 0
      - uses: actions/setup-node@v4
        with:
          node-version-file: .nvmrc
-      - name: Bind qualification to the caller revision
-        if: inputs.source_sha != ''
-        env:
-          SOURCE_SHA: ${{ inputs.source_sha }}
-        run: |
-          test "${SOURCE_SHA}" = "${GITHUB_SHA}"
-          test "${SOURCE_SHA}" = "$(git rev-parse HEAD)"
-      - name: Find a verified ancestor for push selection
-        id: baseline
-        if: github.event_name == 'push' && inputs.source_sha == ''
-        env:
-          GH_TOKEN: ${{ github.token }}
-          HEAD_SHA: ${{ github.sha }}
-          CI_REPOSITORY: ${{ github.repository }}
-          CI_DEFAULT_BRANCH: ${{ github.event.repository.default_branch }}
-        run: node scripts/ci/baseline.mjs
-      - name: Admit scheduled full qualification
-        id: qualification
-        if: github.event_name == 'schedule' && inputs.source_sha == ''
-        env:
-          GH_TOKEN: ${{ github.token }}
-          HEAD_SHA: ${{ github.sha }}
-          CI_REPOSITORY: ${{ github.repository }}
-          CI_REPOSITORY_ID: ${{ github.repository_id }}
-          CI_DEFAULT_BRANCH: ${{ github.event.repository.default_branch }}
-          CI_FORCE_FULL: ${{ github.event.schedule == '23 3 * * *' }}
-        run: node scripts/ci/qualification.mjs
      - name: Select verification lanes
        id: plan
        env:
-          BASE_SHA: ${{ steps.baseline.outputs.base || github.event.pull_request.base.sha }}
-          BASELINE_REASON: ${{ steps.baseline.outputs.reason }}
-          HEAD_SHA: ${{ inputs.source_sha || github.event.pull_request.head.sha || github.sha }}
-          CI_FULL: ${{ inputs.source_sha != '' || contains(github.event.pull_request.labels.*.name, 'ci:full') }}
-          CI_SKIP_FULL: ${{ steps.qualification.outputs.run_full == 'false' }}
+          BASE_SHA: ${{ github.event.pull_request.base.sha }}
+          HEAD_SHA: ${{ github.event.pull_request.head.sha }}
+          CI_FULL: ${{ contains(github.event.pull_request.labels.*.name, 'ci:full') }}
        run: node scripts/ci/plan.mjs

  static:
    name: Static checks
    needs: changes
-    if: ${{ !cancelled() && needs.changes.outputs.tier != 'reused' }}
+    if: ${{ always() }}
    runs-on: ubuntu-latest
-    timeout-minutes: 10
    steps:
      - name: Require successful change classification
        env:
@@ -124,34 +90,18 @@ jobs:
          node-version-file: .nvmrc
          cache: npm
      - run: npm ci
-      - 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=
      - if: needs.changes.outputs.code == 'true'
        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: Upload complete static diagnostics
-        if: always() && needs.changes.outputs.code == 'true'
-        uses: actions/upload-artifact@v4
-        with:
-          name: static-check-reports
-          path: .cache/static-checks/
-          include-hidden-files: true
-          if-no-files-found: ignore
-          retention-days: 7

  test-shard:
    name: Test shard (${{ matrix.shard }})
    needs: [changes, build]
    if: needs.changes.outputs.code == 'true'
    runs-on: ubuntu-latest
-    timeout-minutes: 30
    strategy:
      fail-fast: false
      matrix:
@@ -167,14 +117,7 @@ jobs:
        with:
          name: rea-test-runtime
          path: .
-      - name: Run complete portable suite with coverage
-        if: needs.changes.outputs.tier == 'full'
-        run: npm run test:ci:shard:run -- --shard=${{ matrix.shard }}
-        env:
-          REA_CI_TEST_HISTORY: .cache/ci-test-history/test-results.json
-      - name: Run complete portable suite for fast feedback
-        if: needs.changes.outputs.tier == 'fast'
-        run: npm run test:run -- --reporter=default --reporter=blob --shard=${{ matrix.shard }}
+      - run: npm run test:ci:shard:run -- --shard=${{ matrix.shard }}
        env:
          REA_CI_TEST_HISTORY: .cache/ci-test-history/test-results.json
      - uses: actions/upload-artifact@v4
@@ -190,20 +133,8 @@ jobs:
  build:
    name: Build package
    needs: changes
-    # Reusable provider workflows consume this run's portable build artifact,
-    # even when a workflow-only edit selects the lane without portable tests.
-    if: >-
-      needs.changes.outputs.code == 'true' ||
-      needs.changes.outputs.browser == 'true' ||
-      needs.changes.outputs.binary_layout == 'true' ||
-      needs.changes.outputs.evm == 'true' ||
-      needs.changes.outputs.javascript_recovery == 'true' ||
-      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'
+    if: needs.changes.outputs.code == 'true'
    runs-on: ubuntu-latest
-    timeout-minutes: 10
    permissions:
      contents: read
      actions: read
@@ -217,23 +148,27 @@ jobs:
      - name: Reuse portable build outputs across runs
        uses: ./.github/actions/portable-build-cache
        with:
-          save: ${{ github.event_name != 'pull_request' && github.ref == format('refs/heads/{0}', github.event.repository.default_branch) }}
+          save: "true"
      - run: npm run test:prepare
-      - name: Find available trusted full-suite timing history
+      - name: Find successful default-branch timing history
        id: history
        continue-on-error: true
        env:
          GH_TOKEN: ${{ github.token }}
          CI_REPOSITORY: ${{ github.repository }}
-          CI_REPOSITORY_ID: ${{ github.repository_id }}
          CI_DEFAULT_BRANCH: ${{ github.event.repository.default_branch }}
-        run: node scripts/ci/test-history.mjs
+        run: |
+          run_id="$(gh api --method GET \
+            "repos/${CI_REPOSITORY}/actions/workflows/ci.yml/runs" \
+            -f branch="${CI_DEFAULT_BRANCH}" -f event=push -f status=success -f per_page=1 \
+            --jq '.workflow_runs[0].id // empty')"
+          echo "run-id=${run_id}" >> "${GITHUB_OUTPUT}"
      - name: Download previous timing report
        if: steps.history.outputs.run-id != ''
        continue-on-error: true
        uses: actions/download-artifact@v4
        with:
-          name: test-timings
+          name: test-results
          run-id: ${{ steps.history.outputs.run-id }}
          github-token: ${{ github.token }}
          path: .cache/ci-test-history
@@ -262,24 +197,20 @@ jobs:
          if-no-files-found: error
          retention-days: 7

-  sqlite-runtime:
-    # 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
-
  test:
-    name: Portable tests
+    name: Test (coverage + timing)
    needs: [changes, test-shard]
-    if: ${{ !cancelled() && needs.changes.outputs.tier != 'reused' }}
+    if: ${{ always() }}
    runs-on: ubuntu-latest
-    timeout-minutes: 10
    steps:
-      - name: Require successful change classification
+      - name: Require successful test shards
        env:
          CHANGES_RESULT: ${{ needs.changes.result }}
-        run: test "${CHANGES_RESULT}" = "success"
+          CODE_REQUIRED: ${{ needs.changes.outputs.code }}
+          SHARD_RESULT: ${{ needs.test-shard.result }}
+        run: |
+          test "${CHANGES_RESULT}" = "success"
+          test "${CODE_REQUIRED}" != "true" || test "${SHARD_RESULT}" = "success"
      - uses: actions/checkout@v4
        if: needs.changes.outputs.code == 'true' && success()
      - uses: actions/setup-node@v4
@@ -296,8 +227,7 @@ jobs:
          pattern: vitest-report-*
          merge-multiple: true
      - name: Merge coverage, JUnit, and timing reports
-        id: merge
-        if: needs.changes.outputs.code == 'true' && needs.changes.outputs.tier == 'full' && success()
+        if: needs.changes.outputs.code == 'true' && success()
        run: >-
          npm run test:ci:merge --
          --coverage.reportsDirectory=coverage
@@ -307,61 +237,42 @@ jobs:
          --reporter=default
          --reporter=junit
          --reporter=json
-          --reporter=./scripts/ci/test-timing-reporter.mjs
-          --outputFile.junit=test-results.xml
-          --outputFile.json=test-results.json
-      - name: Merge fast-suite JUnit and timing reports
-        id: merge-fast
-        if: needs.changes.outputs.code == 'true' && needs.changes.outputs.tier == 'fast' && success()
-        run: >-
-          npm exec -- vitest --merge-reports
-          --reporter=default
-          --reporter=junit
-          --reporter=json
-          --reporter=./scripts/ci/test-timing-reporter.mjs
          --outputFile.junit=test-results.xml
          --outputFile.json=test-results.json
      - name: Summarize slowest test files
-        if: needs.changes.outputs.code == 'true' && !cancelled() && hashFiles('test-timings.json') != ''
-        env:
-          SHARD_RESULT: ${{ needs.test-shard.result }}
-          MERGE_RESULT: ${{ needs.changes.outputs.tier == 'full' && steps.merge.outcome || steps.merge-fast.outcome }}
-          CI_VERIFY_TEST_INVENTORY: "true"
-          CI_TEST_SELECTION: ${{ needs.changes.outputs.test_selection }}
-          CI_PR_HEAD_SHA: ${{ github.event.pull_request.head.sha }}
-        run: node scripts/ci/test-report.mjs
+        if: needs.changes.outputs.code == 'true' && success()
+        shell: bash
+        run: |
+          node <<'NODE' >> "${GITHUB_STEP_SUMMARY}"
+          const report = JSON.parse(require("node:fs").readFileSync("test-results.json", "utf8"));
+          const files = (report.testResults ?? [])
+            .map((result) => ({
+              name: result.name,
+              duration: Math.max(0, (result.endTime ?? result.startTime) - result.startTime),
+            }))
+            .sort((left, right) => right.duration - left.duration)
+            .slice(0, 20);
+          console.log("## Slowest deterministic test files\n");
+          console.log("| File | Duration (ms) |");
+          console.log("| --- | ---: |");
+          for (const file of files) {
+            console.log(`| \`${file.name}\` | ${file.duration} |`);
+          }
+          NODE
      - uses: actions/upload-artifact@v4
-        if: needs.changes.outputs.code == 'true' && !cancelled() && hashFiles('test-results.json') != ''
+        if: needs.changes.outputs.code == 'true' && always()
        with:
          name: test-results
          path: |
            test-results.xml
            test-results.json
-            test-timings.json
            coverage/
-            .cache/ci-test-selection/report.json
-          include-hidden-files: true
          if-no-files-found: error
          retention-days: 30
-      - name: Publish successful timing history
-        if: needs.changes.outputs.code == 'true' && needs.changes.outputs.tier == 'full' && success() && needs.test-shard.result == 'success'
-        uses: actions/upload-artifact@v4
-        with:
-          name: test-timings
-          path: .cache/ci-test-history/test-results.json
-          include-hidden-files: true
-          if-no-files-found: error
-          retention-days: 30
-      - name: Require successful test shards
-        if: ${{ !cancelled() }}
-        env:
-          CODE_REQUIRED: ${{ needs.changes.outputs.code }}
-          SHARD_RESULT: ${{ needs.test-shard.result }}
-        run: test "${CODE_REQUIRED}" != "true" || test "${SHARD_RESULT}" = "success"

  conformance-fixtures:
    name: Source-built conformance fixtures
-    needs: [changes, static]
+    needs: changes
    if: needs.changes.outputs.fixtures == 'true'
    runs-on: ubuntu-latest
    timeout-minutes: 10
@@ -372,7 +283,7 @@ jobs:

  windows-native-build:
    name: Build bundled Windows x64 native controls
-    needs: [changes, static]
+    needs: changes
    if: needs.changes.outputs.runtime == 'true'
    runs-on: ubuntu-latest
    timeout-minutes: 10
@@ -408,7 +319,7 @@ jobs:

  package-e2e:
    name: Native package baseline (${{ matrix.platform }} ${{ matrix.architecture }})
-    needs: [changes, static, build, windows-native-build]
+    needs: [changes, build, windows-native-build]
    if: needs.changes.outputs.runtime == 'true'
    strategy:
      fail-fast: false
@@ -447,8 +358,6 @@ jobs:
          name: windows-native-controls
          path: native/windows/build/
      - run: npm run verify:windows-native:artifact
-      - name: Verify NativeAOT diagnostic applicability on this host
-        run: npm run test:focused -- tests/evaluation/package/nativeAotDiagnostics.test.ts
      - name: Resolve npm cache before verifier HOME isolation
        id: npm-cache
        run: |
@@ -457,24 +366,13 @@ jobs:
      - run: npm run verify:package
        env:
          npm_config_cache: ${{ steps.npm-cache.outputs.path }}
-          REA_VERIFIED_PACKAGE_DIRECTORY: ${{ needs.changes.outputs.tier == 'full' && matrix.platform == 'linux' && matrix.architecture == 'x64' && '.cache/verified-package' || '' }}
      - name: Verify real Node Inspector discovery and observation
        timeout-minutes: 10
        run: npm run verify:inspector
-      - name: Retain the exact qualified release package
-        if: needs.changes.outputs.tier == 'full' && matrix.platform == 'linux' && matrix.architecture == 'x64'
-        uses: actions/upload-artifact@v4
-        with:
-          name: verified-release-package
-          path: .cache/verified-package/
-          include-hidden-files: true
-          if-no-files-found: error
-          overwrite: true
-          retention-days: 7

  apple-artifacts:
    name: Real Apple artifact CLI/MCP E2E
-    needs: [changes, static, build]
+    needs: [changes, build]
    if: needs.changes.outputs.apple == 'true'
    runs-on: macos-15
    timeout-minutes: 15
@@ -522,7 +420,7 @@ jobs:

  reconstruction-readiness:
    name: Reconstruction readiness
-    needs: [changes, static]
+    needs: changes
    if: needs.changes.outputs.readiness == 'true'
    runs-on: ubuntu-latest
    timeout-minutes: 15
@@ -551,7 +449,7 @@ jobs:

  windows-curated:
    name: Windows capability and package lane
-    needs: [changes, static, build, windows-native-build]
+    needs: [changes, build, windows-native-build]
    if: needs.changes.outputs.package == 'true'
    runs-on: windows-latest
    timeout-minutes: 25
@@ -596,7 +494,6 @@ jobs:
          tests/boundary/providers/native/artifactProvider.extractionCompleteness.test.ts
          tests/boundary/filesystem/setupUnavailableProvider.test.ts
          tests/boundary/filesystem/windowsNpxRegistration.test.ts
-          tests/acceptance/setup/homeDirectoryFallback.test.ts
          tests/boundary/filesystem/webScriptManifestPaths.test.ts
          tests/boundary/process/ProcessEvidence.host.test.ts
          tests/acceptance/webModuleCli.test.ts
@@ -606,7 +503,6 @@ jobs:
          tests/boundary/filesystem/javascript-applications/javascriptArtifactReconstruction.test.ts
          tests/conformance/providers/ghidra/windowsCapabilities.test.ts
          src/ghidra/GhidraInstallation.test.ts
-          tests/boundary/filesystem/ghidraJavaProbe.test.ts
          tests/boundary/providers/ghidra/ghidraTransport.test.ts
          tests/boundary/providers/ghidra/ghidraTargetSnapshot.test.ts
          tests/boundary/providers/ghidra/ghidraLauncher.test.ts
@@ -663,7 +559,6 @@ jobs:
    needs: changes
    if: needs.changes.outputs.docs == 'true'
    runs-on: ubuntu-latest
-    timeout-minutes: 10
    steps:
      - uses: actions/checkout@v4
      - uses: actions/setup-node@v4
@@ -683,69 +578,63 @@ jobs:
            skills/reverse-engineer-anything
          if-no-files-found: error

+  workflows:
+    name: Validate workflows
+    needs: changes
+    if: needs.changes.outputs.workflows == 'true'
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - name: Validate workflow syntax and expressions
+        run: go run github.com/rhysd/actionlint/cmd/actionlint@v1.7.7 -shellcheck= -pyflakes=
+
  browser:
-    needs: [changes, static, build]
+    needs: changes
    if: needs.changes.outputs.browser == 'true'
    uses: ./.github/workflows/real-browser.yml
-    with:
-      build_cache_artifact: rea-build-cache

  binary_layout:
-    needs: [changes, static, build]
+    needs: changes
    if: needs.changes.outputs.binary_layout == 'true'
    uses: ./.github/workflows/real-binary-layout.yml
-    with:
-      build_cache_artifact: rea-build-cache

  evm:
-    needs: [changes, static, build]
+    needs: changes
    if: needs.changes.outputs.evm == 'true'
    uses: ./.github/workflows/real-evm-interface.yml
-    with:
-      build_cache_artifact: rea-build-cache

  javascript_recovery:
-    needs: [changes, static, build]
+    needs: changes
    if: needs.changes.outputs.javascript_recovery == 'true'
    uses: ./.github/workflows/real-javascript-recovery.yml
-    with:
-      build_cache_artifact: rea-build-cache

  recorded_crash:
-    needs: [changes, static, build]
+    needs: changes
    if: needs.changes.outputs.recorded_crash == 'true'
    uses: ./.github/workflows/real-recorded-crash.yml
-    with:
-      build_cache_artifact: rea-build-cache

  web_network:
-    needs: [changes, static, build]
+    needs: changes
    if: needs.changes.outputs.web_network == 'true'
    uses: ./.github/workflows/real-web-network-captures.yml
-    with:
-      build_cache_artifact: rea-build-cache

  web_runtime:
-    needs: [changes, static, build]
+    needs: changes
    if: needs.changes.outputs.web_runtime == 'true'
    uses: ./.github/workflows/real-web-runtime.yml
-    with:
-      build_cache_artifact: rea-build-cache

  web_source_map:
-    needs: [changes, static, build]
+    needs: changes
    if: needs.changes.outputs.web_source_map == 'true'
    uses: ./.github/workflows/real-web-source-map.yml
-    with:
-      build_cache_artifact: rea-build-cache

  nativeaot:
-    needs: [changes, static]
+    needs: changes
    if: needs.changes.outputs.nativeaot == 'true'
    uses: ./.github/workflows/nativeaot-fixtures.yml

  website:
-    needs: [changes, static]
+    needs: changes
    if: needs.changes.outputs.website == 'true'
    uses: ./.github/workflows/website-check.yml

@@ -755,10 +644,10 @@ jobs:
    needs:
      [
        changes,
+        pr-title,
        static,
        build,
        test-shard,
-        sqlite-runtime,
        test,
        conformance-fixtures,
        windows-native-build,
@@ -767,6 +656,7 @@ jobs:
        reconstruction-readiness,
        windows-curated,
        docs,
+        workflows,
        browser,
        binary_layout,
        evm,
@@ -779,24 +669,12 @@ jobs:
        website,
      ]
    runs-on: ubuntu-latest
-    timeout-minutes: 5
    steps:
      - uses: actions/checkout@v4
      - uses: actions/setup-node@v4
        with:
          node-version-file: .nvmrc
      - name: Require every selected lane to pass
-        id: gate
        env:
          CI_JOBS: ${{ toJSON(needs) }}
-          CI_QUALIFICATION_DIRECTORY: .cache/ci-qualification
        run: node scripts/ci/required.mjs
-      - name: Upload full qualification receipt artifact
-        if: needs.changes.outputs.tier == 'full' && success()
-        uses: actions/upload-artifact@v4
-        with:
-          name: ${{ steps.gate.outputs.receipt_name }}
-          path: ${{ steps.gate.outputs.receipt_path }}
-          if-no-files-found: error
-          overwrite: true
-          retention-days: 7
@@ -12,8 +12,7 @@ jobs:
    name: Build Windows x64 NativeAOT fixture
    # .NET 8.0.22's bundled linker discovery supports VS 2019/2022.
    runs-on: windows-2022
-    # Two bounded restore attempts and one compile can each take five minutes.
-    timeout-minutes: 20
+    timeout-minutes: 15
    env:
      DOTNET_CLI_TELEMETRY_OPTOUT: "1"
      DOTNET_PROCESSOR_COUNT: "1"
@@ -1,29 +0,0 @@
-name: PR title
-
-on:
-  pull_request:
-    branches: [main, "release/*"]
-    types: [opened, synchronize, reopened, edited]
-
-permissions: {}
-
-concurrency:
-  group: pr-title-${{ github.event.pull_request.number }}
-  cancel-in-progress: true
-
-jobs:
-  pr-title:
-    name: Conventional PR title
-    runs-on: ubuntu-latest
-    timeout-minutes: 2
-    steps:
-      - name: Validate title for Release Please
-        env:
-          PR_TITLE: ${{ github.event.pull_request.title }}
-        run: >-
-          node -e 'const title = process.env.PR_TITLE ?? "";
-          const conventional = /^(?:feat|fix|docs|refactor|perf|test|build|ci|chore|revert)(?:\([a-z0-9._/-]+\))?!?: .+/u;
-          if (!conventional.test(title)) {
-            console.error("PR title must use Conventional Commits, for example: feat: add historical source import");
-            process.exit(1);
-          }'
@@ -8,16 +8,14 @@ on:
        type: boolean
        default: false
  workflow_call:
-    inputs:
-      build_cache_artifact:
-        description: Portable build cache artifact from the calling CI run.
-        required: false
-        type: string
-        default: ""

 permissions:
  contents: read

+concurrency:
+  group: real-binary-layout-${{ github.event.pull_request.number || github.ref }}
+  cancel-in-progress: true
+
 env:
  NODE_OPTIONS: --max-old-space-size=768
  HUSKY: "0"
@@ -35,8 +33,6 @@ jobs:
          cache: npm
      - run: npm ci
      - uses: ./.github/actions/portable-build-cache
-        with:
-          build_cache_artifact: ${{ inputs.build_cache_artifact }}
      - name: Acquire exact upstream libraries in an isolated runner environment
        shell: bash
        run: |
@@ -2,14 +2,12 @@ name: Real browser verification

 on:
  workflow_call:
-    inputs:
-      build_cache_artifact:
-        description: Portable build cache artifact from the calling CI run.
-        required: false
-        type: string
-        default: ""
  workflow_dispatch:

+concurrency:
+  group: real-browser-${{ github.event.pull_request.number || github.ref }}
+  cancel-in-progress: ${{ github.event_name == 'pull_request' }}
+
 env:
  HUSKY: "0"

@@ -28,8 +26,6 @@ jobs:
          cache: npm
      - run: npm ci
      - uses: ./.github/actions/portable-build-cache
-        with:
-          build_cache_artifact: ${{ inputs.build_cache_artifact }}
      - run: npm run verify:browser
        env:
          REA_BROWSER_EXECUTABLE: /usr/bin/google-chrome
@@ -3,16 +3,14 @@ name: Real offline EVM interface
 on:
  workflow_dispatch:
  workflow_call:
-    inputs:
-      build_cache_artifact:
-        description: Portable build cache artifact from the calling CI run.
-        required: false
-        type: string
-        default: ""

 permissions:
  contents: read

+concurrency:
+  group: real-evm-interface-${{ github.event.pull_request.number || github.ref }}
+  cancel-in-progress: true
+
 env:
  NODE_OPTIONS: --max-old-space-size=768
  HUSKY: "0"
@@ -29,8 +27,6 @@ jobs:
          cache: npm
      - run: npm ci
      - uses: ./.github/actions/portable-build-cache
-        with:
-          build_cache_artifact: ${{ inputs.build_cache_artifact }}
      - name: Acquire unchanged fixture compiler in isolated runner storage
        shell: bash
        run: |
@@ -2,17 +2,15 @@ name: Real JavaScript recovery

 on:
  workflow_call:
-    inputs:
-      build_cache_artifact:
-        description: Portable build cache artifact from the calling CI run.
-        required: false
-        type: string
-        default: ""
  workflow_dispatch:

 permissions:
  contents: read

+concurrency:
+  group: javascript-recovery-${{ github.event.pull_request.number || github.ref }}
+  cancel-in-progress: ${{ github.event_name == 'pull_request' }}
+
 env:
  HUSKY: "0"
  NODE_OPTIONS: "--max-old-space-size=768"
@@ -30,8 +28,6 @@ jobs:
          cache: npm
      - run: npm ci
      - uses: ./.github/actions/portable-build-cache
-        with:
-          build_cache_artifact: ${{ inputs.build_cache_artifact }}
      - name: Fetch pinned Wakaru release into the job workspace
        shell: bash
        run: |
@@ -1,58 +0,0 @@
-name: Real packet capture
-on:
-  workflow_dispatch:
-  pull_request:
-    paths:
-      - "tests/boundary/captures/**"
-      - "tests/boundary/cli/captureCleanup.test.ts"
-      - "tests/boundary/mcp/packetCaptureMcp.test.ts"
-      - "src/captures/**"
-      - "src/pcap/**"
-      - "src/domain/pcap/**"
-      - "src/domain/analysisView/pcapCaptureView.ts"
-      - "src/application/pcap/**"
-      - "src/contracts/pcap/**"
-      - "src/server/registerPcapTools.ts"
-      - "tests/boundary/pcap/**"
-      - "src/domain/captures/**"
-      - "src/application/captures/**"
-      - "src/contracts/captures/**"
-      - "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
-concurrency:
-  group: real-packet-capture-${{ github.event.pull_request.number || github.ref }}
-  cancel-in-progress: true
-jobs:
-  tshark:
-    runs-on: ubuntu-24.04
-    timeout-minutes: 15
-    steps:
-      - uses: actions/checkout@v4
-      - uses: actions/setup-node@v4
-        with:
-          node-version-file: .nvmrc
-          cache: npm
-      - run: sudo apt-get update && sudo DEBIAN_FRONTEND=noninteractive apt-get install -y tshark util-linux python3
-      - run: npm ci
-      - run: npm run build:cached
-      - run: npm run test:focused -- tests/boundary/captures/fieldDiscovery.test.ts src/process/LinuxResourceLimits.test.ts tests/boundary/captures/captureProvider.test.ts tests/boundary/captures/captureDescriptorCleanup.test.ts tests/boundary/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
-          REA_CAPINFOS_COMMAND: /usr/bin/capinfos
@@ -3,16 +3,14 @@ name: Real recorded crash evidence
 on:
  workflow_dispatch:
  workflow_call:
-    inputs:
-      build_cache_artifact:
-        description: Portable build cache artifact from the calling CI run.
-        required: false
-        type: string
-        default: ""

 permissions:
  contents: read

+concurrency:
+  group: real-recorded-crash-${{ github.event.pull_request.number || github.ref }}
+  cancel-in-progress: true
+
 env:
  NODE_OPTIONS: --max-old-space-size=768
  HUSKY: "0"
@@ -32,8 +30,6 @@ jobs:
          cache: npm
      - run: npm ci
      - uses: ./.github/actions/portable-build-cache
-        with:
-          build_cache_artifact: ${{ inputs.build_cache_artifact }}
      - name: Install GDB on the disposable CI runner
        shell: bash
        run: |
@@ -1,50 +0,0 @@
-name: Real signal recording
-on:
-  workflow_dispatch:
-  pull_request:
-    paths:
-      - "tests/boundary/signals/**"
-      - "tests/boundary/cli/signalCleanup.test.ts"
-      - "tests/boundary/mcp/signalRecordingMcp.test.ts"
-      - "src/signals/**"
-      - "src/domain/signals/**"
-      - "src/application/signals/**"
-      - "src/contracts/signals/**"
-      - "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
-concurrency:
-  group: real-signal-recording-${{ github.event.pull_request.number || github.ref }}
-  cancel-in-progress: true
-jobs:
-  sigrok:
-    runs-on: ubuntu-24.04
-    timeout-minutes: 15
-    steps:
-      - uses: actions/checkout@v4
-      - uses: actions/setup-node@v4
-        with:
-          node-version-file: .nvmrc
-          cache: npm
-      - run: sudo apt-get update && sudo apt-get install -y sigrok-cli util-linux python3
-      - run: npm ci
-      - run: npm run build:cached
-      - run: npm run test:focused -- tests/boundary/signals/decoderDiscovery.test.ts src/process/LinuxResourceLimits.test.ts src/domain/signals/annotationTextWindow.test.ts tests/boundary/signals/recordingProvider.test.ts tests/boundary/signals/recordingDescriptorCleanup.test.ts tests/boundary/signals/resourceLimits.test.ts tests/boundary/mcp/signalRecordingMcp.test.ts tests/boundary/cli/signalCleanup.test.ts
-      - run: node scripts/verify-signal-recording.mjs
-        env:
-          REA_SIGROK_COMMAND: /usr/bin/sigrok-cli
@@ -3,16 +3,14 @@ name: Real historical web network captures
 on:
  workflow_dispatch:
  workflow_call:
-    inputs:
-      build_cache_artifact:
-        description: Portable build cache artifact from the calling CI run.
-        required: false
-        type: string
-        default: ""

 permissions:
  contents: read

+concurrency:
+  group: real-web-network-captures-${{ github.event.pull_request.number || github.ref }}
+  cancel-in-progress: true
+
 env:
  HUSKY: "0"
  NODE_OPTIONS: --max-old-space-size=768
@@ -31,8 +29,6 @@ jobs:
        run: npm install --global npm@11.16.0
      - run: npm ci
      - uses: ./.github/actions/portable-build-cache
-        with:
-          build_cache_artifact: ${{ inputs.build_cache_artifact }}
      - name: Acquire fixed upstream native profile in runner temporary storage
        shell: bash
        run: |
@@ -1,15 +1,12 @@
 name: Real website runtime attribution
 on:
  workflow_call:
-    inputs:
-      build_cache_artifact:
-        description: Portable build cache artifact from the calling CI run.
-        required: false
-        type: string
-        default: ""
  workflow_dispatch:
 permissions:
  contents: read
+concurrency:
+  group: real-web-runtime-${{ github.event.pull_request.number || github.ref }}
+  cancel-in-progress: ${{ github.event_name == 'pull_request' }}
 env:
  HUSKY: "0"
 jobs:
@@ -24,8 +21,6 @@ jobs:
          cache: npm
      - run: npm ci
      - uses: ./.github/actions/portable-build-cache
-        with:
-          build_cache_artifact: ${{ inputs.build_cache_artifact }}
      - run: npm run verify:browser:runtime
        env:
          REA_BROWSER_EXECUTABLE: /usr/bin/google-chrome
@@ -1,15 +1,12 @@
 name: Real website source-map verification
 on:
  workflow_call:
-    inputs:
-      build_cache_artifact:
-        description: Portable build cache artifact from the calling CI run.
-        required: false
-        type: string
-        default: ""
  workflow_dispatch:
 permissions:
  contents: read
+concurrency:
+  group: real-web-source-map-${{ github.event.pull_request.number || github.ref }}
+  cancel-in-progress: ${{ github.event_name == 'pull_request' }}
 env:
  HUSKY: "0"
 jobs:
@@ -24,8 +21,6 @@ jobs:
          cache: npm
      - run: npm ci
      - uses: ./.github/actions/portable-build-cache
-        with:
-          build_cache_artifact: ${{ inputs.build_cache_artifact }}
      - name: Install the pinned compiler into an isolated fixture directory
        run: npm install --prefix "$RUNNER_TEMP/rea-web-source-map-compiler" --no-audit --no-fund --package-lock=false esbuild@0.25.10
      - run: npm run verify:browser:source-maps
@@ -290,25 +290,13 @@ jobs:
        if: inputs.phase == 'prepare' && steps.release.outputs.prs_created == 'true'
        run: npm run docs:check && git diff --exit-code

-  qualification:
-    name: Qualify exact release revision
+  publish:
+    name: Publish to npm
    needs: [merged-release, release-please]
    if: >-
      always() && !cancelled() &&
      ((needs.merged-release.result == 'success' && needs.merged-release.outputs.release_created == 'true') ||
      (needs.release-please.result == 'success' && inputs.phase == 'publish' && needs.release-please.outputs.release_created == 'true'))
-    permissions:
-      contents: read
-      actions: read
-    uses: ./.github/workflows/ci.yml
-    with:
-      source_sha: ${{ needs.merged-release.outputs.sha || needs.release-please.outputs.sha }}
-
-  publish:
-    name: Publish to npm
-    needs: [merged-release, release-please, qualification]
-    if: >-
-      always() && !cancelled() && needs.qualification.result == 'success'
    runs-on: ubuntu-latest
    permissions:
      contents: read
@@ -327,20 +315,17 @@ jobs:

      - run: npm ci

-      - name: Download the exact qualified package
-        uses: actions/download-artifact@v4
-        with:
-          name: verified-release-package
-          path: .cache/verified-package/
+      - name: Prepare Windows native build toolchain
+        run: sudo apt-get update && sudo apt-get install --no-install-recommends -y g++-mingw-w64-x86-64

-      - name: Verify qualified package provenance and digest
-        id: package
-        run: node scripts/ci/verified-package.mjs validate .cache/verified-package
+      - name: Build and verify bundled Windows native controls
+        run: npm run build:windows-native && npm run verify:windows-native:artifact
+
+      - name: Verify packaged release before publishing
+        run: npm run verify:package

      - name: Publish
        shell: bash
-        env:
-          VERIFIED_PACKAGE_TARBALL: ${{ steps.package.outputs.tarball }}
        run: |
          version="$(node --input-type=module -e 'import packageJson from "./package.json" with { type: "json" }; process.stdout.write(packageJson.version)')"
          published_version="$(npm view "rea-agents@${version}" version --json 2>/dev/null || true)"
@@ -348,7 +333,7 @@ jobs:
            echo "rea-agents@${version} is already published; verifying the existing package."
          else
            tag="$(node scripts/release-npm-tag.mjs "${version}")"
-            npm publish "${VERIFIED_PACKAGE_TARBALL}" --access public --tag "${tag}"
+            npm publish --access public --tag "${tag}"
          fi

      - name: Verify published CLI from npm
@@ -1,37 +0,0 @@
-name: SQLite runtime compatibility
-
-on:
-  workflow_call:
-
-permissions:
-  contents: read
-
-env:
-  HUSKY: "0"
-
-jobs:
-  sqlite:
-    name: SQLite runtime compatibility (Node ${{ matrix.node }})
-    runs-on: ubuntu-latest
-    timeout-minutes: 15
-    strategy:
-      fail-fast: false
-      matrix:
-        # Exercise unavailable-runtime diagnostics, the first supported release,
-        # and new patches on both supported lines without hand-editing versions.
-        # The repository-pinned Node 24 version also runs the complete test suite.
-        node: ["22.x", "24.15.0", "24.x", "26.x"]
-    steps:
-      - uses: actions/checkout@v4
-      - uses: actions/setup-node@v4
-        with:
-          node-version: ${{ matrix.node }}
-          check-latest: true
-          cache: npm
-      - run: npm ci
-      - uses: actions/download-artifact@v4
-        with:
-          name: rea-test-runtime
-          path: .
-      - name: Verify SQLite discovery, inspection and cleanup
-        run: npm run test:sqlite:run
@@ -7,6 +7,10 @@ on:
 permissions:
  contents: read

+concurrency:
+  group: website-check-${{ github.event.pull_request.number || github.ref }}
+  cancel-in-progress: true
+
 jobs:
  check:
    name: Website checks
@@ -36,7 +36,6 @@ coverage/
 .vitest/
 .vitest-reports/
 test-results.xml
-test-timings.json
 .turbo/
 .cache/
 docs/.vitepress/cache/
@@ -73,5 +72,3 @@ Thumbs.db

 # Complete static website output, including generated language editions.
 website/_site/
-# Temporary translation output prepared before replacing the complete site.
-website/.i18n-*/
@@ -1,5 +1,6 @@
 {
-  "threshold": 3.5,
+  "_comment": "Test files remain included so the gate measures duplication across both src/ and tests/. The 3.0% limit leaves headroom for ordinary changes while keeping duplication visible.",
+  "threshold": 3.0,
  "reporters": ["consoleFull"],
  "ignore": [
    "node_modules/**",
@@ -4,8 +4,6 @@

 REA is a local-only reverse-engineering tool with shared CLI/MCP workflows. Distinguish observations, derivations, inferences, and unknowns; preserve Evidence provenance and session semantics through both adapters. Provider support and setup live in [README.md](README.md#choosing-a-deep-analysis-provider) and its linked guides.

-Follow the [contribution scope and fail-closed integration rule](CONTRIBUTING.md#contribution-scope). Do not integrate capabilities while material scope, authority, side-effect, or required verification questions remain unresolved. For new providers or capabilities involving target execution, injection, mutation, or protection recovery, seek the required maintainer scope decision before substantial implementation for integration. Welcome early proposals, small exploratory prototypes, and draft PRs that help resolve questions; they do not authorize integration.
-
 Ghidra uses ephemeral databases without modifying executable bytes or controlling a GUI; Windows Ghidra P0 has no mutation authority. IDA analysis is read-only; never save or close an attached GUI database.

 Configuration changes must be additive and idempotent, with backups. Installers must not install or upgrade unrelated software, including Homebrew, Node.js, npm, Java, or Ghidra. Ghidra and IDA are bring-your-own. `rea setup` must show its planned changes and require approval before writing files or installing Hopper.
@@ -24,37 +22,10 @@ Assess brittleness in touched code during implementation, debugging, review, and

 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.

-When addressing a review thread, inspect the producing boundary and affected consumers for brittleness. Complete directly related refactoring in the same change. Before resolving the thread, explain the root cause, structural fix, validation, and any remaining cleanup.
-
 Parse unknown boundary values and model expected failures with the tagged error algebra and `Result`. Preserve partial facts and meaningful failure reasons. Keep identity and lookup values separate from display formatting; preserve source values and explicit unknowns when normalization loses information. Absolute paths, file URLs, and HTTP paths have different semantics.

 Validate advertised JSON Schemas after SDK conversion against their declared dialect and actual clients. Bind handlers to named contracts with exact types; catalog ordering must never select an operation or schema.

-## Performance
-
-Design analysis workflows and agent interfaces for efficiency from the first
-implementation. Correctness, useful answers, Evidence provenance, caller choices,
-compatibility and safe resource bounds remain required.
-
-Optimize in this order:
-
-1. Agent tokens and context. Return the smallest sufficient answer with
-   necessary provenance, coverage and limitations. Use task selection,
-   summaries, paging and retained Evidence where supported; honor requested
-   detail and keep complete Evidence accessible. Count the whole task,
-   including schemas, extra calls and retries.
-2. Analysis time. Reuse validated results and shared work. Cache keys must
-   cover result-affecting inputs; define invalidation and lifetime. Validate
-   freshness before reporting cached live state as current.
-3. CPU and memory. Avoid unnecessary work and copies; bound concurrency,
-   retained state and serialization growth.
-
-For changes affecting these costs, measure representative completed tasks and
-compare equivalent workflows before and after where available. Report token
-usage, elapsed time, CPU time and peak process-family memory. Separate cold
-and warm runs, label estimates, and state unmeasured costs. Fewer bytes alone
-do not establish fewer tokens or faster analysis.
-
 ## Development

 Use [.nvmrc](.nvmrc) and `package.json#packageManager` for the pinned toolchain. Cursor Cloud may place older Node.js first on `PATH`; environment setup installs the pinned toolchain under `/usr/local/bin`.
@@ -17,108 +17,8 @@ targets; optional adapter failures must preserve successful peers. Run
 `npm run verify:test-discovery` after adding or moving tests. Resolved import
 boundaries are checked by `npm run verify:module-boundaries`, included in lint.

-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.
-
 When adding or changing an MCP tool, follow the [tool design guide](docs/tool-design.md) and preserve the canonical contracts and generated catalog.

-## Contribution scope
-
-REA focuses on software structure, runtime behavior, and evidence through
-general-purpose reverse-engineering workflows. Evaluate a proposal by its actual
-capabilities, side effects, defaults, and complete workflow. A tool name or a
-reference to vulnerability research, malware analysis, or CTFs does not determine
-whether it belongs in REA.
-
-Supported contributions include format inspection, ordinary archive and standard
-compression extraction, disassembly, decompilation, cross-references, general
-static deobfuscation, vulnerability analysis, and evidence reporting. Static
-protection detection is distinct from defeating that protection. Security fixes
-and isolated regression tests remain in scope.
-
-Runtime investigation needs explicit boundaries. Launching or attaching to a
-process, injecting instrumentation, running scripts, and changing memory or
-registers require review of target selection, execution and mutation authority,
-provenance, resource limits, cancellation, and cleanup. General Frida or debugger
-support is not inherently read-only, and existing support does not authorize
-every workflow built on it. General-purpose interfaces are not classified as
-dedicated bypass workflows solely because caller-provided code could be misused;
-their execution and mutation authority must still be reviewed.
-
-REA does not integrate or officially distribute:
-
- Purpose-built workflows to defeat commercial packing or code-virtualization
-  protections and automatically recover protected code.
- Anti-debugging or anti-instrumentation evasion, or DRM, license, anti-cheat, or
-  access-control bypass workflows.
- Exploit or attack-payload automation, credential theft, covert persistence,
-  unauthorized access, or bulk attack workflows.
-
-These boundaries apply to first-party providers, adapters, plugins, bundled
-scripts, defaults, examples, and documentation. Moving a capability into an
-optional dependency or plugin does not exempt it. Review what the integration
-exposes, including upstream defaults and raw-command or script execution paths.
-Ordinary extraction and general static deobfuscation are not excluded merely
-because the input is packed or obfuscated; assess added bypass or execution
-behavior separately.
-
-This is a product and maintenance boundary, not a judgment about a contributor's
-intentions or a declaration that all excluded research is unlawful. Contributors
-must have the rights and authorization needed for their work. A local-only design
-or an "authorized use only" disclaimer does not establish containment or settle
-legal and scope questions.
-
-### Fail-closed integration
-
-If scope fit, target or authorization boundaries, side effects, or the verification
-needed to establish those boundaries remain materially unresolved, **do not merge,
-enable, or include the capability in official packages or distributions**. Keep
-the proposal pending, narrow it, or decline it. Record unknowns explicitly; do not
-turn them into "none" or assumed safety. Passing CI, completed implementation,
-upstream popularity, or silence from maintainers is not scope approval.
-
-For a new provider or a capability involving target execution, injection,
-mutation, or protection recovery, seek an explicit maintainer scope decision in
-the linked issue or design discussion before substantial implementation intended
-for integration. Small exploratory prototypes and draft PRs may help inform that
-decision; they do not authorize integration. The decision must cover the final
-proposed behavior; a scope expansion needs a new decision. Routine fixes and
-documentation changes within existing boundaries do not need a separate advance
-decision, but must not silently expand those boundaries.
-
-### Starting a proposal
-
-To open a feature request or design discussion, describe the problem and desired
-outcome or decision. Short answers and the forms' "Not sure yet" options are
-welcome. You do not need code, a complete design or test plan, legal analysis, or
-private proof-of-authorization documents to start a discussion. Share what you
-know and leave optional details blank when you need help.
-
-Form selections guide triage; they are not proof of authorization or scope
-approval. Unselected effects must not be treated as established absence.
-Maintainers and implementers work together to resolve the following before
-integration:
-
- The concrete analyst question, requested inputs and outputs, and why existing
-  REA operations are insufficient.
- Why the workflow fits this scope, its non-goals, and any protection recovery,
-  bypass, or attack automation it would expose.
- The selected targets and every execution, injection, mutation, network, or
-  persistence effect, including behavior inherited from upstream tools.
- How the boundaries and outcome will be verified with self-owned or appropriately
-  licensed samples; identify real CLI/MCP and provider coverage, cleanup and
-  resource checks, and remaining unknowns. Do not publish private binaries,
-  credentials, or sensitive target data; follow [SECURITY.md](SECURITY.md) for
-  private vulnerability reports.
-
-Mixed proposals should separate acceptable analysis capabilities from excluded
-workflows so each can be decided independently. An issue may discuss unresolved
-questions; opening an issue or PR does not authorize integration. This is a
-maintainer integration gate, not a per-call confirmation requirement or a sandbox
-guarantee.
-
 ## Development setup

 Use the development toolchain pinned in `.nvmrc` and
@@ -187,10 +87,6 @@ CI diagnosis. Packaging/setup/distribution changes additionally require
 `npm run verify:package` and `npm pack --dry-run`; provider changes require the
 matching real-provider lane. State which host/provider workflows ran.

-`check:pr` reuses build and static-check outputs while executing the test suite
-fresh, including the fast Python producer checks. `docs:check` also runs the
-onboarding example consistency suite for README-only changes.
-
 Pre-commit formats and lints staged files; pre-push runs `check:fast`.

 ### Generated files and command ownership
@@ -157,11 +157,10 @@ Additional tools and host support depend on the target:
 | Go binaries            | Embedded compiler version, modules, replacements and build settings                  | Built-in static ELF/PE/thin Mach-O inspection; no Go installation required                                                            |
 | WASM artifact          | Validation, sections, exact import/export WAT forms and decoded WAT                  | Caller-supplied WABT 1.0.42; `inspect_wasm_artifact`                                                                                  |
 | EVM bytecode           | Dispatch selectors, byte offsets, inferred arguments and mutability                  | Local raw/hex carrier on Linux x64; [offline EVM guide](docs/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; [application analysis](https://rea.tools/guides/javascript/)                                                         |
 | Websites               | Page structure, scripts, network observations and requested screenshots              | A Chrome-family browser; [browser analysis](https://rea.tools/guides/browser/)                                                        |
-| Saved network captures | Requests, responses, exposed payloads and source locations                           | HAR or Fiddler Everywhere SAZ; mitmdump on Linux for native mitmproxy; [capture guide](docs/web-network-captures.md)                  |
+| Saved network captures | Requests, responses, exposed payloads and source locations                           | HAR; mitmdump on Linux for native mitmproxy captures; [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)                                                  |
@@ -169,9 +168,6 @@ Additional tools and host support depend on the target:
 | 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)                                                             |

@@ -183,7 +179,7 @@ using your user permissions; each runtime guide describes its effects.

 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), and
+[IDA guide](docs/ida-provider.md), 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
@@ -322,7 +318,7 @@ Report vulnerabilities through [SECURITY.md](SECURITY.md).

 ## Star history

-🎉 **170,000 GitHub stars — thank you!**
+🎉 **110,000 GitHub stars — thank you!**

 Thanks to everyone using REA, reporting bugs, requesting features, testing builds, and contributing fixes.

@@ -139,7 +139,6 @@ npx rea-agents@latest setup
 | JavaScript / Electron           | الوحدات، وعمليات الاستيراد، وخرائط المصدر، والمسارات، وIPC، وعلاقات إضافات الشيفرة الأصلية                    | Node.js وnpm؛ [تحليل التطبيقات](https://rea.tools/ar/guides/javascript/)                                                          |
 | المواقع                         | بنية الصفحة، والسكربتات، وملاحظات الشبكة، ولقطات الشاشة المطلوبة                                            | متصفح من عائلة Chrome؛ [تحليل المتصفح](https://rea.tools/ar/guides/browser/)                                                      |
 | تسجيلات الشبكة المحفوظة          | الطلبات، والاستجابات، ومحتويات الحمولة المتاحة، ومواضعها في المصدر                                          | HAR؛ وmitmdump على Linux لتسجيلات mitmproxy بصيغتها الأصلية؛ [دليل تسجيلات الشبكة](docs/web-network-captures.md)                     |
-| التقاط الحزم                    | نقاط النهاية وDNS وTLS SNI وتوزيع البروتوكولات وطلبات HTTP                                                  | tshark وcapinfos يوفّرهما المُستدعي؛ [دليل pcap](docs/pcap-analysis.md)                                                             |
 | تجميعات .NET                    | البيانات الوصفية، وتعليمات CIL، واعتماديات الشيفرة الأصلية المعلنة، ومقارنات البناء                         | فحص ثابت؛ [دليل الشيفرة المُدارة](docs/managed-code-analysis.md)                                                                   |
 | حزم Android APK                 | تصريحات ملف manifest، والأصناف، والدوال الناتجة عن فك الترجمة، والمراجع                                     | JADX دون واجهة رسومية وJDK كامل على Linux/macOS/Windows x64؛ [دليل Android](docs/android-analysis.md)                             |
 | أجهزة Android                   | الأجهزة والحزم والعمليات والسجلات والدامبات ولقطات الشاشة ونقل APK/الملفات                                   | adb يوفّره المُستدعي (محاكي أو جهاز)؛ [دليل ADB](docs/adb-device-analysis.md)                                                       |
@@ -147,8 +146,6 @@ npx rea-agents@latest setup
 | موارد Android                   | البيان المفكوك الترميز وجداول السلاسل واللغات وحقائق الإصدار                                                 | مُشغّل Apktool يوفّره المُستدعي؛ [دليل الموارد](docs/apktool-resource-analysis.md)                                                    |
 | تطبيقات Flutter                 | بصمة لقطة Dart وهشوش المكتبات لكل ABI وأصل بناء المحرك                                                     | لا شيء (تحليل APK ساكن)؛ [دليل Flutter](docs/flutter-analysis.md)                                                                  |
 | البرامج الثابتة                 | المناطق، ونتائج الاستخراج، وما يُمرّر إلى تحليل الشيفرة الأصلية                                                | Binwalk / Unblob على Linux؛ [دليل البرامج الثابتة](docs/firmware-analysis.md)                                                     |
-| الحزم المسجلة                   | حقول مختارة وقيم متكررة ومرشحات وقواعد فك الترميز                                                          | Linux: TShark 4.x + prlimit; [دليل التقاط الحزم](docs/packet-captures.md)                                                         |
-| الإشارات المنطقية المسجلة        | تعليقات مفكك الترميز ونطاقات العينات ومعلومات التشخيص                                                      | Linux: sigrok-cli 0.7.2 + prlimit; [دليل الإشارات](docs/signal-recordings.md)                                                      |
 | الحزم والموارد                  | قوائم الملفات، والبصمات، وملفات plist، وبنية حزم Apple، والموارد المستخرجة                                 | [دليل تحليل الملفات وJavaScript](docs/javascript-artifact-reconstruction.md)، [تطبيقات Apple](docs/apple-application-analysis.md) |
 | سلوك العمليات                   | مخرجات الطرفية، والتفاعلات، وملاحظات الخروج ونظام الملفات، ومقارنات التشغيل                                  | Linux/macOS مع PTY أصلي؛ [تسجيل سلوك العمليات](docs/process-capture.md)                                                           |

@@ -264,7 +261,7 @@ npx rea-agents@latest setup

 ## سجل النجوم

-🎉 **170,000 نجمة على GitHub — شكرًا لكم!**
+🎉 **110,000 نجمة على GitHub — شكرًا لكم!**

 شكرًا لكل من يستخدم REA، ويبلّغ عن الأخطاء، ويقترح ميزات، ويختبر إصدارات البناء، ويساهم بالإصلاحات.

@@ -139,7 +139,6 @@ REA benötigt Node.js 22.x (>=22.19), 24.x (>=24.11) oder 26+ sowie npm. Zusätz
 | JavaScript / Electron               | Module, Imports, Source Maps, Routen, IPC und Beziehungen zu nativen Add-ons                                    | Node.js und npm; [Anwendungsanalyse](https://rea.tools/de/guides/javascript/)                                                                 |
 | Websites                            | Seitenstruktur, Skripte, Netzwerkbeobachtungen und angeforderte Screenshots                                     | Ein Browser aus der Chrome-Familie; [Browseranalyse](https://rea.tools/de/guides/browser/)                                                    |
 | Gespeicherte Netzwerkaufzeichnungen | Anfragen, Antworten, zugängliche Nutzdaten und Quellpositionen                                                  | HAR; mitmdump unter Linux für Aufzeichnungen im nativen mitmproxy-Format; [Leitfaden zu Netzwerkaufzeichnungen](docs/web-network-captures.md) |
-| Paketerfassungen                    | Endpunkte, DNS, TLS SNI, Protokollverteilung und HTTP-Anfragen                                                  | Vom Aufrufer bereitgestellte tshark- und capinfos-Binaries; [pcap-Leitfaden](docs/pcap-analysis.md)                                           |
 | .NET-Assemblies                     | Metadaten, CIL-Anweisungen, deklarierte native Abhängigkeiten und Build-Vergleiche                              | Statische Untersuchung; [Leitfaden für verwalteten Code](docs/managed-code-analysis.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](docs/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](docs/adb-device-analysis.md)                                         |
@@ -147,8 +146,6 @@ REA benötigt Node.js 22.x (>=22.19), 24.x (>=24.11) oder 26+ sowie npm. Zusätz
 | Android-Ressourcen                  | Dekodiertes Manifest, String-Tabellen, Sprachen und Versionsfakten                                              | Vom Aufrufer bereitgestellter Apktool-Starter; [Ressourcen-Leitfaden](docs/apktool-resource-analysis.md)                                      |
 | Flutter-Apps                        | Dart-Snapshot-Hash, Per-ABI-Bibliotheksprüfsummen und Engine-Build-Provenienz                                   | Keine (statische APK-Analyse); [Flutter-Leitfaden](docs/flutter-analysis.md)                                                                  |
 | Firmware                            | Bereiche, Extraktionsergebnisse und Übergaben an die native Analyse                                             | Binwalk / Unblob unter Linux; [Firmware-Leitfaden](docs/firmware-analysis.md)                                                                 |
-| Aufgezeichnete Pakete               | Ausgewählte Felder, wiederholte Werte, Filter und Decode-as-Regeln                                              | Linux: TShark 4.x + prlimit; [Mitschnitt-Anleitung](docs/packet-captures.md)                                                                  |
-| Aufgezeichnete Logiksignale         | Decoder-Anmerkungen, Sample-Bereiche und Diagnosen                                                              | Linux: sigrok-cli 0.7.2 + prlimit; [Signalaufzeichnungen](docs/signal-recordings.md)                                                          |
 | Pakete und Ressourcen               | Dateiinventare, Hashwerte, plists, Aufbau von Apple-Bundles und extrahierte Ressourcen                          | [Artefakt- und JavaScript-Leitfaden](docs/javascript-artifact-reconstruction.md), [Apple-Anwendungen](docs/apple-application-analysis.md)     |
 | Prozessverhalten                    | Terminalausgabe, Interaktionen, Beobachtungen zu Prozessende und Dateisystem sowie Laufvergleiche               | Linux/macOS mit nativer PTY; [Prozessaufzeichnung](docs/process-capture.md)                                                                   |

@@ -262,7 +259,7 @@ Melde Sicherheitslücken gemäß [SECURITY.md](SECURITY.md).

 ## Sternverlauf

-🎉 **170.000 GitHub-Sterne – vielen Dank!**
+🎉 **110.000 GitHub-Sterne – vielen Dank!**

 Danke an alle, die REA nutzen, Fehler melden, Funktionswünsche äußern, Builds testen und Fehlerbehebungen beitragen.

@@ -139,7 +139,6 @@ REA requiere Node.js 22.x (>=22.19), 24.x (>=24.11) o 26+, además de npm. Las h
 | JavaScript / Electron       | Módulos, importaciones, mapas de código fuente, rutas, IPC y relaciones con complementos nativos                               | Node.js y npm; [análisis de aplicaciones](https://rea.tools/es/guides/javascript/)                                                         |
 | Sitios web                  | Estructura de la página, scripts, observaciones de red y capturas de pantalla solicitadas                                      | Un navegador de la familia Chrome; [análisis del navegador](https://rea.tools/es/guides/browser/)                                          |
 | Capturas de red guardadas   | Solicitudes, respuestas, contenido accesible de las cargas útiles y ubicaciones de origen                                      | HAR; mitmdump en Linux para capturas en formato nativo de mitmproxy; [guía de capturas](docs/web-network-captures.md)                      |
-| Capturas de paquetes        | Endpoints, DNS, TLS SNI, distribución de protocolos y solicitudes HTTP                                                         | tshark y capinfos suministrados por el autor de la llamada; [guía pcap](docs/pcap-analysis.md)                                             |
 | Ensamblados .NET            | Metadatos, instrucciones CIL, dependencias nativas declaradas y comparaciones de compilaciones                                 | Inspección estática; [guía de código administrado](docs/managed-code-analysis.md)                                                          |
 | APK de Android              | Declaraciones del manifiesto, clases, métodos descompilados y referencias                                                      | JADX sin interfaz gráfica y un JDK completo en Linux/macOS/Windows x64; [guía de Android](docs/android-analysis.md)                        |
 | Dispositivos Android        | Dispositivos, paquetes, procesos, registros, volcados, capturas de pantalla y transferencias de APK/archivos                   | adb suministrado por el autor de la llamada (emulador o dispositivo); [guía de ADB](docs/adb-device-analysis.md)                           |
@@ -147,8 +146,6 @@ REA requiere Node.js 22.x (>=22.19), 24.x (>=24.11) o 26+, además de npm. Las h
 | Recursos de Android         | Manifiesto decodificado, tablas de cadenas, idiomas y datos de versión                                                         | Lanzador de Apktool suministrado por el autor de la llamada; [guía de recursos](docs/apktool-resource-analysis.md)                         |
 | Aplicaciones Flutter        | Hash de snapshot de Dart, resúmenes de bibliotecas por ABI y procedencia de compilación del motor                              | Ninguna (análisis APK estático); [guía de Flutter](docs/flutter-analysis.md)                                                               |
 | Firmware                    | Regiones, resultados de extracción y derivaciones al análisis nativo                                                           | Binwalk / Unblob en Linux; [guía de firmware](docs/firmware-analysis.md)                                                                   |
-| Paquetes grabados           | Campos seleccionados, valores repetidos, filtros y reglas de decodificación                                                    | Linux: TShark 4.x + prlimit; [guía de capturas](docs/packet-captures.md)                                                                   |
-| Señales lógicas grabadas    | Anotaciones del decodificador, rangos de muestras y diagnósticos                                                               | Linux: sigrok-cli 0.7.2 + prlimit; [guía de señales](docs/signal-recordings.md)                                                            |
 | Paquetes y recursos         | Inventarios de archivos, resúmenes criptográficos, plists, estructura de paquetes de Apple y recursos extraídos                | [Guía de artefactos y JavaScript](docs/javascript-artifact-reconstruction.md), [aplicaciones de Apple](docs/apple-application-analysis.md) |
 | Comportamiento de procesos  | Salida de la terminal, interacciones, observaciones de salida y del sistema de archivos, y comparaciones entre ejecuciones     | Linux/macOS con una PTY nativa; [captura de procesos](docs/process-capture.md)                                                             |

@@ -262,7 +259,7 @@ Informa de vulnerabilidades siguiendo [SECURITY.md](SECURITY.md).

 ## Historial de estrellas

-🎉 **170.000 estrellas en GitHub: ¡gracias!**
+🎉 **110.000 estrellas en GitHub: ¡gracias!**

 Gracias a quienes usan REA, informan de errores, solicitan funciones, prueban compilaciones y contribuyen con correcciones.

@@ -122,27 +122,24 @@ npx rea-agents@latest setup

 REA به Node.js 22.x (>=22.19)، 24.x (>=24.11) یا 26+، به‌همراه npm نیاز دارد. ابزارهای اضافی و پشتیبانی سیستم میزبان به نوع هدف بستگی دارند:

-| هدف                    | خروجی REA                                                                           | پیش‌نیازها و راهنما                                                                                                                  |
-| ---------------------- | ----------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------- |
-| باینری‌های بومی         | شبه‌کد، اسمبلی، رشته‌ها، نمادها، فراخوانی‌ها و ارجاعات                                 | Hopper، Ghidra یا IDA؛ [تحلیل بومی](https://rea.tools/fa/guides/native/)                                                            |
-| ساختار ELF آفلاین       | بخش‌ها، سگمنت‌ها، نمادها و relocationهای اصلی و گزینه‌های احتمالی کاهش آسیب‌پذیری ایستا | pwntools تأمین‌شده توسط فراخواننده روی Linux x64؛ [تشخیص باینری](docs/binary-diagnostics.md)                                         |
-| بایت‌کد EVM             | selectorهای dispatch، offsetهای بایتی، آرگومان‌های استنباط‌شده و قابلیت تغییر وضعیت   | دادهٔ خام/hex محلی روی Linux x64؛ [راهنمای EVM آفلاین](docs/evm-bytecode.md)                                                          |
-| کرش‌های ثبت‌شدهٔ لینوکس   | یادداشت‌های خام، رجیسترها/سیگنال‌های تمام threadهای ثبت‌شده و گزینه‌های احتمالی نگاشت   | pwntools تأمین‌شده توسط فراخواننده روی Linux x64؛ GDB/pwndbg اختیاری؛ [کرش‌های ثبت‌شده](docs/recorded-crashes.md)                      |
-| JavaScript / Electron  | ماژول‌ها، importها، source mapها، مسیرها، IPC و ارتباط افزونه‌های بومی                | Node.js و npm؛ [تحلیل برنامه](https://rea.tools/fa/guides/javascript/)                                                              |
-| وب‌سایت‌ها               | ساختار صفحه، اسکریپت‌ها، مشاهدات شبکه و اسکرین‌شات‌های درخواستی                        | مرورگر مبتنی بر Chrome؛ [تحلیل مرورگر](https://rea.tools/fa/guides/browser/)                                                        |
-| داده‌های ضبط‌شدهٔ شبکه    | درخواست‌ها، پاسخ‌ها، payloadهای آشکارشده و مکان آن‌ها در منبع                          | HAR؛ ابزار mitmdump در لینوکس برای ضبط‌های بومی mitmproxy؛ [راهنمای ضبط شبکه](docs/web-network-captures.md)                          |
-| اسمبلی‌های .NET         | فراداده، دستورالعمل‌های CIL، وابستگی‌های بومی اعلام‌شده و مقایسهٔ buildها                | بررسی ایستا؛ [راهنمای کد مدیریت‌شده](docs/managed-code-analysis.md)                                                                  |
-| فایل‌های APK اندروید    | تعاریف Manifest، کلاس‌ها، متدهای دیکامپایل‌شده و ارجاعات                               | JADX بدون رابط گرافیکی و JDK کامل در Linux/macOS/Windows x64؛ [راهنمای اندروید](docs/android-analysis.md)                           |
-| دستگاه‌های اندروید      | دستگاه‌ها، بسته‌ها، فرایندها، لاگ‌ها، دامپ‌ها، اسکرین‌شات‌ها و انتقال APK/فایل             | adb تأمین‌شده توسط فراخوان‌کننده (شبیه‌ساز یا دستگاه)؛ [راهنمای ADB](docs/adb-device-analysis.md)                                      |
-| پروژه‌های JEB           | واحدهای پروژه از موتور، هش‌های مصنوع و شبه‌کدِ نوع/متد                                 | یک کلاینت JEB که توسط فراخوان‌کننده اجرا شده و MCP ارائه می‌دهد و با REA_JEB_MCP_URL انتخاب می‌شود؛ [راهنمای JEB](docs/jeb-analysis.md) |
-| منابع اندروید          | مانیفست رمزگشایی‌شده، جداول رشته‌ها، زبان‌ها و اطلاعات نسخه                             | راه‌انداز Apktool تأمین‌شده توسط فراخوان‌کننده؛ [راهنمای منابع](docs/apktool-resource-analysis.md)                                     |
-| برنامه‌های فلاتر         | هش اسنپ‌شات دارت، هش کتابخانه‌ها به تفکیک ABI و اصالت بیلد موتور                      | هیچ (تحلیل ایستا APK)؛ [راهنمای فلاتر](docs/flutter-analysis.md)                                                                     |
-| Firmware               | ناحیه‌ها، نتایج استخراج و تحویل به ابزارهای تحلیل بومی                               | Binwalk / Unblob در لینوکس؛ [راهنمای Firmware](docs/firmware-analysis.md)                                                           |
-| بسته‌های ضبط‌شده         | فیلدهای منتخب، مقادیر تکراری، فیلترها و قواعد رمزگشایی                              | Linux: TShark 4.x + prlimit; [راهنمای ضبط بسته](docs/packet-captures.md)                                                            |
-| ضبط بسته‌ها             | نقاط پایانی، DNS، TLS SNI، توزیع پروتکل و درخواست‌های HTTP                           | tshark و capinfos تأمین‌شده توسط فراخوان‌کننده؛ [راهنمای pcap](docs/pcap-analysis.md)                                                 |
-| سیگنال‌های منطقی ضبط‌شده | توضیحات رمزگشا، بازه‌های نمونه و اطلاعات عیب‌یابی                                      | Linux: sigrok-cli 0.7.2 + prlimit; [راهنمای سیگنال‌ها](docs/signal-recordings.md)                                                    |
-| بسته‌ها و منابع         | فهرست فایل‌ها، digestها، فایل‌های plist، ساختار bundle اپل و منابع استخراج‌شده         | [راهنمای آرتیفکت و JavaScript](docs/javascript-artifact-reconstruction.md)، [برنامه‌های اپل](docs/apple-application-analysis.md)     |
-| رفتار فرایند           | خروجی ترمینال، تعاملات، وضعیت خروج، مشاهدات سیستم فایل و مقایسهٔ اجراها               | Linux/macOS با PTY بومی؛ [ضبط فرایند](docs/process-capture.md)                                                                      |
+| هدف                   | خروجی REA                                                                           | پیش‌نیازها و راهنما                                                                                                                  |
+| --------------------- | ----------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------- |
+| باینری‌های بومی        | شبه‌کد، اسمبلی، رشته‌ها، نمادها، فراخوانی‌ها و ارجاعات                                 | Hopper، Ghidra یا IDA؛ [تحلیل بومی](https://rea.tools/fa/guides/native/)                                                            |
+| ساختار ELF آفلاین      | بخش‌ها، سگمنت‌ها، نمادها و relocationهای اصلی و گزینه‌های احتمالی کاهش آسیب‌پذیری ایستا | pwntools تأمین‌شده توسط فراخواننده روی Linux x64؛ [تشخیص باینری](docs/binary-diagnostics.md)                                         |
+| بایت‌کد EVM            | selectorهای dispatch، offsetهای بایتی، آرگومان‌های استنباط‌شده و قابلیت تغییر وضعیت   | دادهٔ خام/hex محلی روی Linux x64؛ [راهنمای EVM آفلاین](docs/evm-bytecode.md)                                                          |
+| کرش‌های ثبت‌شدهٔ لینوکس  | یادداشت‌های خام، رجیسترها/سیگنال‌های تمام threadهای ثبت‌شده و گزینه‌های احتمالی نگاشت   | pwntools تأمین‌شده توسط فراخواننده روی Linux x64؛ GDB/pwndbg اختیاری؛ [کرش‌های ثبت‌شده](docs/recorded-crashes.md)                      |
+| JavaScript / Electron | ماژول‌ها، importها، source mapها، مسیرها، IPC و ارتباط افزونه‌های بومی                | Node.js و npm؛ [تحلیل برنامه](https://rea.tools/fa/guides/javascript/)                                                              |
+| وب‌سایت‌ها              | ساختار صفحه، اسکریپت‌ها، مشاهدات شبکه و اسکرین‌شات‌های درخواستی                        | مرورگر مبتنی بر Chrome؛ [تحلیل مرورگر](https://rea.tools/fa/guides/browser/)                                                        |
+| داده‌های ضبط‌شدهٔ شبکه   | درخواست‌ها، پاسخ‌ها، payloadهای آشکارشده و مکان آن‌ها در منبع                          | HAR؛ ابزار mitmdump در لینوکس برای ضبط‌های بومی mitmproxy؛ [راهنمای ضبط شبکه](docs/web-network-captures.md)                          |
+| اسمبلی‌های .NET        | فراداده، دستورالعمل‌های CIL، وابستگی‌های بومی اعلام‌شده و مقایسهٔ buildها                | بررسی ایستا؛ [راهنمای کد مدیریت‌شده](docs/managed-code-analysis.md)                                                                  |
+| فایل‌های APK اندروید   | تعاریف Manifest، کلاس‌ها، متدهای دیکامپایل‌شده و ارجاعات                               | JADX بدون رابط گرافیکی و JDK کامل در Linux/macOS/Windows x64؛ [راهنمای اندروید](docs/android-analysis.md)                           |
+| دستگاه‌های اندروید     | دستگاه‌ها، بسته‌ها، فرایندها، لاگ‌ها، دامپ‌ها، اسکرین‌شات‌ها و انتقال APK/فایل             | adb تأمین‌شده توسط فراخوان‌کننده (شبیه‌ساز یا دستگاه)؛ [راهنمای ADB](docs/adb-device-analysis.md)                                      |
+| پروژه‌های JEB          | واحدهای پروژه از موتور، هش‌های مصنوع و شبه‌کدِ نوع/متد                                 | یک کلاینت JEB که توسط فراخوان‌کننده اجرا شده و MCP ارائه می‌دهد و با REA_JEB_MCP_URL انتخاب می‌شود؛ [راهنمای JEB](docs/jeb-analysis.md) |
+| منابع اندروید         | مانیفست رمزگشایی‌شده، جداول رشته‌ها، زبان‌ها و اطلاعات نسخه                             | راه‌انداز Apktool تأمین‌شده توسط فراخوان‌کننده؛ [راهنمای منابع](docs/apktool-resource-analysis.md)                                     |
+| برنامه‌های فلاتر        | هش اسنپ‌شات دارت، هش کتابخانه‌ها به تفکیک ABI و اصالت بیلد موتور                      | هیچ (تحلیل ایستا APK)؛ [راهنمای فلاتر](docs/flutter-analysis.md)                                                                     |
+| Firmware              | ناحیه‌ها، نتایج استخراج و تحویل به ابزارهای تحلیل بومی                               | Binwalk / Unblob در لینوکس؛ [راهنمای Firmware](docs/firmware-analysis.md)                                                           |
+| بسته‌ها و منابع        | فهرست فایل‌ها، digestها، فایل‌های plist، ساختار bundle اپل و منابع استخراج‌شده         | [راهنمای آرتیفکت و JavaScript](docs/javascript-artifact-reconstruction.md)، [برنامه‌های اپل](docs/apple-application-analysis.md)     |
+| رفتار فرایند          | خروجی ترمینال، تعاملات، وضعیت خروج، مشاهدات سیستم فایل و مقایسهٔ اجراها               | Linux/macOS با PTY بومی؛ [ضبط فرایند](docs/process-capture.md)                                                                      |

 بررسی ایستای JavaScript و .NET فایل‌های ارائه‌شده را بدون اجرای برنامه می‌خواند. ضبط زمان اجرا، هدف انتخاب‌شده را با مجوزهای کاربری شما اجرا می‌کند یا با آن تعامل دارد؛ آثار این عملیات در راهنمای مربوط به هر نوع ضبط توضیح داده شده‌اند.

@@ -247,7 +244,7 @@ npx rea-agents@latest setup

 ## تاریخچهٔ ستاره‌ها

-🎉 **۱۷۰٬۰۰۰ ستارهٔ GitHub — سپاسگزاریم!**
+🎉 **۱۱۰٬۰۰۰ ستارهٔ GitHub — سپاسگزاریم!**

 از همهٔ کسانی که از REA استفاده می‌کنند، خطاها را گزارش می‌دهند، قابلیت‌های جدید پیشنهاد می‌کنند، buildها را آزمایش می‌کنند و در بهبود پروژه مشارکت دارند سپاسگزاریم.

@@ -143,7 +143,6 @@ REA nécessite Node.js 22.x (>=22.19), 24.x (>=24.11) ou 26+, ainsi que npm. Les
 | JavaScript / Electron        | Modules, imports, source maps, routes, IPC et relations avec les modules natifs                             | Node.js et npm ; [analyse d'applications](https://rea.tools/fr/guides/javascript/)                                                    |
 | Sites web                    | Structure des pages, scripts, observations réseau et captures d'écran demandées                             | Un navigateur de la famille Chrome ; [analyse du navigateur](https://rea.tools/fr/guides/browser/)                                    |
 | Captures réseau enregistrées | Requêtes, réponses, payloads exposés et emplacements dans le code source                                    | HAR ; mitmdump sous Linux pour les captures mitmproxy natives ; [guide des captures](docs/web-network-captures.md)                    |
-| Captures de paquets          | Points de terminaison, DNS, TLS SNI, distribution des protocoles et requêtes HTTP                           | tshark et capinfos fournis par l'appelant ; [guide pcap](docs/pcap-analysis.md)                                                       |
 | Assemblys .NET               | Métadonnées, instructions CIL, dépendances natives déclarées et comparaisons de builds                      | Inspection statique ; [guide du code managé](docs/managed-code-analysis.md)                                                           |
 | APK Android                  | Déclarations du manifeste, classes, méthodes décompilées et références                                      | JADX headless et un JDK complet sous Linux/macOS/Windows x64 ; [guide Android](docs/android-analysis.md)                              |
 | Appareils Android            | Appareils, paquets, processus, journaux, dumps, captures d'écran et transferts d'APK/fichiers               | adb fourni par l'appelant (émulateur ou appareil) ; [guide ADB](docs/adb-device-analysis.md)                                          |
@@ -151,8 +150,6 @@ REA nécessite Node.js 22.x (>=22.19), 24.x (>=24.11) ou 26+, ainsi que npm. Les
 | Ressources Android           | Manifeste décodé, tables de chaînes, langues et faits de version                                            | Lanceur Apktool fourni par l'appelant ; [guide des ressources](docs/apktool-resource-analysis.md)                                     |
 | Applications Flutter         | Empreinte de snapshot Dart, condensés de bibliothèques par ABI et provenance de build du moteur             | Aucune (analyse APK statique) ; [guide Flutter](docs/flutter-analysis.md)                                                             |
 | Firmware                     | Régions, résultats d'extraction et passage de relais vers l'analyse native                                  | Binwalk / Unblob sous Linux ; [guide firmware](docs/firmware-analysis.md)                                                             |
-| Paquets enregistrés          | Champs sélectionnés, valeurs répétées, filtres et règles de décodage                                        | Linux: TShark 4.x + prlimit; [guide des captures](docs/packet-captures.md)                                                            |
-| Signaux logiques enregistrés | Annotations du décodeur, plages d’échantillons et diagnostics                                               | Linux: sigrok-cli 0.7.2 + prlimit; [guide des signaux](docs/signal-recordings.md)                                                     |
 | Paquets et ressources        | Inventaires de fichiers, empreintes, plists, anatomie des bundles Apple et ressources extraites             | [Guide artefacts et JavaScript](docs/javascript-artifact-reconstruction.md), [applications Apple](docs/apple-application-analysis.md) |
 | Comportement des processus   | Sortie du terminal, interactions, code de sortie, observations du système de fichiers et comparaisons       | Linux/macOS avec un PTY natif ; [capture de processus](docs/process-capture.md)                                                       |

@@ -266,7 +263,7 @@ Signalez les vulnérabilités via [SECURITY.md](SECURITY.md).

 ## Historique des étoiles

-🎉 **170 000 étoiles GitHub — merci !**
+🎉 **110 000 étoiles GitHub — merci !**

 Merci à toutes les personnes qui utilisent REA, signalent des bugs, proposent des fonctionnalités, testent les builds et contribuent des correctifs.

@@ -146,7 +146,6 @@ Alat tambahan dan dukungan sistem host bergantung pada target yang dianalisis:
 | JavaScript / Electron      | Modul, impor, source map, rute, IPC, dan hubungan add-on native                                       | Node.js dan npm; [analisis aplikasi](https://rea.tools/id/guides/javascript/)                                                      |
 | Situs web                  | Struktur halaman, skrip, pengamatan jaringan, dan tangkapan layar yang diminta                        | Peramban berbasis Chrome; [analisis peramban](https://rea.tools/id/guides/browser/)                                                |
 | Rekaman jaringan tersimpan | Permintaan, respons, payload yang terekspos, dan lokasi sumber                                        | HAR; mitmdump di Linux untuk rekaman native mitmproxy; [panduan rekaman](docs/web-network-captures.md)                             |
-| Capturan paket             | Endpoint, DNS, TLS SNI, distribusi protokol, dan permintaan HTTP                                      | tshark dan capinfos buatan pemanggil; [panduan pcap](docs/pcap-analysis.md)                                                        |
 | Assembly .NET              | Metadata, instruksi CIL, dependensi native yang dideklarasikan, dan perbandingan build                | Tidak ada (hanya analisis statis); [panduan kode terkelola](docs/managed-code-analysis.md)                                         |
 | APK Android                | Deklarasi manifest, kelas, metode hasil dekompilasi, dan referensi                                    | JADX mode headless dan JDK lengkap di Linux/macOS/Windows x64; [panduan Android](docs/android-analysis.md)                         |
 | Perangkat Android          | Perangkat, paket, proses, log, dump, tangkapan layar, serta transfer APK/berkas                       | adb buatan pemanggil (emulator atau perangkat); [panduan ADB](docs/adb-device-analysis.md)                                         |
@@ -154,8 +153,6 @@ Alat tambahan dan dukungan sistem host bergantung pada target yang dianalisis:
 | Resource Android           | Manifest terdekode, tabel string, lokal, dan fakta versi                                              | Peluncur Apktool buatan pemanggil; [panduan resource](docs/apktool-resource-analysis.md)                                           |
 | Aplikasi Flutter           | Hash snapshot Dart, hash pustaka per ABI, dan asal build engine                                       | Tidak ada (parsing APK statis); [panduan Flutter](docs/flutter-analysis.md)                                                        |
 | Firmware                   | Wilayah, hasil ekstraksi, dan pengalihan ke analisis native                                           | Binwalk / Unblob di Linux; [panduan firmware](docs/firmware-analysis.md)                                                           |
-| Paket rekaman              | Kolom terpilih, nilai berulang, filter, dan aturan decode-as                                          | Linux: TShark 4.x + prlimit; [panduan tangkapan](docs/packet-captures.md)                                                          |
-| Sinyal logika terekam      | Anotasi dekoder, rentang sampel, dan diagnostik                                                       | Linux: sigrok-cli 0.7.2 + prlimit; [panduan sinyal](docs/signal-recordings.md)                                                     |
 | Paket dan sumber daya      | Inventaris berkas, digest, plist, struktur paket Apple, dan sumber daya yang diekstrak                | [Panduan artefak dan JavaScript](docs/javascript-artifact-reconstruction.md), [aplikasi Apple](docs/apple-application-analysis.md) |
 | Perilaku proses            | Keluaran terminal, interaksi, pengamatan proses keluar dan sistem berkas, serta perbandingan eksekusi | Linux/macOS dengan PTY native; [perekaman proses](docs/process-capture.md)                                                         |

@@ -287,7 +284,7 @@ Laporkan kerentanan melalui [SECURITY.md](SECURITY.md).

 ## Riwayat Bintang

-🎉 **170.000 bintang GitHub, terima kasih!**
+🎉 **110.000 bintang GitHub, terima kasih!**

 Terima kasih kepada semua orang yang menggunakan REA, melaporkan bug, meminta fitur, menguji build, dan berkontribusi dalam perbaikan.

@@ -143,7 +143,6 @@ REA richiede Node.js 22.x (>=22.19), 24.x (>=24.11) o 26+, oltre a npm. Strument
 | JavaScript / Electron        | Moduli, import, source map, route, IPC e relazioni con add-on nativi                              | Node.js e npm; [analisi delle applicazioni](https://rea.tools/it/guides/javascript/)                                                |
 | Siti web                     | Struttura della pagina, script, osservazioni di rete e screenshot richiesti                       | Un browser della famiglia Chrome; [analisi browser](https://rea.tools/it/guides/browser/)                                           |
 | Acquisizioni di rete salvate | Richieste, risposte, payload esposti e posizioni sorgente                                         | HAR; mitmdump su Linux per acquisizioni mitmproxy native; [guida alle acquisizioni](docs/web-network-captures.md)                   |
-| Captured di pacchetti        | Endpoint, DNS, TLS SNI, distribuzione dei protocolli e richieste HTTP                             | tshark e capinfos forniti dal chiamante; [guida pcap](docs/pcap-analysis.md)                                                        |
 | Assembly .NET                | Metadati, istruzioni CIL, dipendenze native dichiarate e confronti di build                       | Nessuno (solo statico); [guida managed-code](docs/managed-code-analysis.md)                                                         |
 | APK Android                  | Dichiarazioni manifest, classi, metodi decompilati e riferimenti                                  | JADX headless e un JDK completo su Linux/macOS/Windows x64; [guida Android](docs/android-analysis.md)                               |
 | Dispositivi Android          | Dispositivi, pacchetti, processi, log, dump, screenshot e trasferimenti APK/file                  | adb fornito dal chiamante (emulatore o hardware); [guida ADB](docs/adb-device-analysis.md)                                          |
@@ -151,8 +150,6 @@ REA richiede Node.js 22.x (>=22.19), 24.x (>=24.11) o 26+, oltre a npm. Strument
 | Risorse Android              | Manifest decodificato, tabelle stringhe, lingue e dati di versione                                | Launcher Apktool fornito dal chiamante; [guida alle risorse](docs/apktool-resource-analysis.md)                                     |
 | App Flutter                  | Hash dello snapshot Dart, digest delle librerie per ABI e provenienza della build del motore      | Nessuno (analisi APK statica); [guida Flutter](docs/flutter-analysis.md)                                                            |
 | Firmware                     | Regioni, risultati di estrazione e passaggi all'analisi nativa                                    | Binwalk / Unblob su Linux; [guida firmware](docs/firmware-analysis.md)                                                              |
-| Pacchetti registrati         | Campi selezionati, valori ripetuti, filtri e regole di decodifica                                 | Linux: TShark 4.x + prlimit; [guida alle catture](docs/packet-captures.md)                                                          |
-| Segnali logici registrati    | Annotazioni del decoder, intervalli di campioni e diagnostica                                     | Linux: sigrok-cli 0.7.2 + prlimit; [guida ai segnali](docs/signal-recordings.md)                                                    |
 | Pacchetti e risorse          | Inventari file, digest, plist, anatomia dei bundle Apple e risorse estratte                       | [Guida artifact e JavaScript](docs/javascript-artifact-reconstruction.md), [Applicazioni Apple](docs/apple-application-analysis.md) |
 | Comportamento dei processi   | Output del terminale, interazioni, osservazioni su uscita e filesystem ed confronti di esecuzione | Linux/macOS con un PTY nativo; [cattura dei processi](docs/process-capture.md)                                                      |

@@ -266,7 +263,7 @@ Segnala vulnerabilità tramite [SECURITY.md](SECURITY.md).

 ## Cronologia delle stelle

-🎉 **170.000 stelle su GitHub — grazie!**
+🎉 **110.000 stelle su GitHub — grazie!**

 Grazie a tutti coloro che usano REA, segnalano bug, propongono funzionalità, testano le build e contribuiscono con correzioni.

@@ -139,7 +139,6 @@ REA には Node.js 22.x（>=22.19）、24.x（>=24.11）、または 26+ と npm
 | JavaScript / Electron            | モジュール、インポート、ソースマップ、ルート、IPC、ネイティブアドオンの関係                 | Node.js と npm；[アプリケーション分析](https://rea.tools/ja/guides/javascript/)                                                                    |
 | ウェブサイト                     | ページ構造、スクリプト、ネットワークの観測結果、依頼されたスクリーンショット                | Chrome 系ブラウザー；[ブラウザー分析](https://rea.tools/ja/guides/browser/)                                                                        |
 | 保存済みのネットワークキャプチャ | リクエスト、レスポンス、取得可能なペイロード、ソース内の位置                                | HAR；mitmproxy ネイティブ形式のキャプチャには Linux 上の mitmdump；[キャプチャガイド](docs/web-network-captures.md)                                |
-| パケットキャプチャ               | エンドポイント、DNS、TLS SNI、プロトコル分布、HTTPリクエスト                                | 呼び出し側が用意した tshark と capinfos；[pcapガイド](docs/pcap-analysis.md)                                                                       |
 | .NET アセンブリ                  | メタデータ、CIL 命令、宣言されたネイティブ依存関係、ビルドの比較                            | 静的な検査；[マネージドコードのガイド](docs/managed-code-analysis.md)                                                                              |
 | Android APK                      | マニフェストの宣言、クラス、逆コンパイルされたメソッド、参照                                | Linux/macOS/Windows x64 上のヘッドレス JADX と完全な JDK；[Android ガイド](docs/android-analysis.md)                                               |
 | Android デバイス                 | デバイス、パッケージ、プロセス、ログ、ダンプ、スクリーンキャプチャ、APK/ファイル転送        | 呼び出し側が用意した adb（エミュレーターまたは実機）；[ADB ガイド](docs/adb-device-analysis.md)                                                    |
@@ -147,8 +146,6 @@ REA には Node.js 22.x（>=22.19）、24.x（>=24.11）、または 26+ と npm
 | Android リソース                 | デコードされたマニフェスト、文字列テーブル、ロケール、バージョン情報                        | 呼び出し側が用意した Apktool ランチャー；[リソースガイド](docs/apktool-resource-analysis.md)                                                       |
 | Flutter アプリ                   | Dart スナップショットハッシュ、ABI ごとのライブラリダイジェスト、エンジンビルドの来歴       | 不要（静的 APK 解析）；[Flutter ガイド](docs/flutter-analysis.md)                                                                                  |
 | ファームウェア                   | 領域、抽出結果、ネイティブ分析への引き継ぎ                                                  | Linux 上の Binwalk / Unblob；[ファームウェアガイド](docs/firmware-analysis.md)                                                                     |
-| 記録済みパケット                 | 選択フィールド、繰り返し値、フィルター、デコード指定                                        | Linux: TShark 4.x + prlimit; [キャプチャガイド](docs/packet-captures.md)                                                                           |
-| 記録済みロジック信号             | デコーダ注釈、サンプル範囲、診断情報                                                        | Linux: sigrok-cli 0.7.2 + prlimit; [信号記録ガイド](docs/signal-recordings.md)                                                                     |
 | パッケージとリソース             | ファイル一覧、ダイジェスト、plist、Apple バンドルの構造、抽出されたリソース                 | [アーティファクトと JavaScript のガイド](docs/javascript-artifact-reconstruction.md)、[Apple アプリケーション](docs/apple-application-analysis.md) |
 | プロセスの動作                   | ターミナル出力、対話、終了とファイルシステムの観測結果、実行の比較                          | ネイティブ PTY を備えた Linux/macOS；[プロセスキャプチャ](docs/process-capture.md)                                                                 |

@@ -264,7 +261,7 @@ npx rea-agents@latest setup

 ## スター履歴

-🎉 **GitHub スター 170,000 件、ありがとうございます！**
+🎉 **GitHub スター 110,000 件、ありがとうございます！**

 REA の利用、バグ報告、機能の要望、ビルドのテスト、修正への貢献に感謝します。

@@ -139,7 +139,6 @@ REA에는 Node.js 22.x(>=22.19), 24.x(>=24.11) 또는 26+와 npm이 필요합니
 | JavaScript / Electron | 모듈, 임포트, 소스 맵, 라우트, IPC, 네이티브 애드온 관계                      | Node.js와 npm; [애플리케이션 분석](https://rea.tools/ko/guides/javascript/)                                                           |
 | 웹사이트              | 페이지 구조, 스크립트, 네트워크 관찰 결과, 요청한 스크린샷                    | Chrome 계열 브라우저; [브라우저 분석](https://rea.tools/ko/guides/browser/)                                                           |
 | 저장된 네트워크 캡처  | 요청, 응답, 접근 가능한 페이로드, 소스 위치                                   | HAR; mitmproxy 네이티브 캡처에는 Linux의 mitmdump; [캡처 가이드](docs/web-network-captures.md)                                        |
-| 패킷 캡처             | 엔드포인트, DNS, TLS SNI, 프로토콜 분포, HTTP 요청                            | 호출자 제공 tshark 및 capinfos; [pcap 가이드](docs/pcap-analysis.md)                                                                  |
 | .NET 어셈블리         | 메타데이터, CIL 명령, 선언된 네이티브 의존성, 빌드 비교                       | 정적 검사; [관리 코드 가이드](docs/managed-code-analysis.md)                                                                          |
 | Android APK           | 매니페스트 선언, 클래스, 디컴파일된 메서드, 참조                              | Linux/macOS/Windows x64의 헤드리스 JADX와 전체 JDK; [Android 가이드](docs/android-analysis.md)                                        |
 | Android 기기          | 기기, 패키지, 프로세스, 로그, 덤프, 화면 캡처, APK/파일 전송                  | 호출자 제공 adb(에뮬레이터 또는 실제 기기); [ADB 가이드](docs/adb-device-analysis.md)                                                 |
@@ -147,8 +146,6 @@ REA에는 Node.js 22.x(>=22.19), 24.x(>=24.11) 또는 26+와 npm이 필요합니
 | Android 리소스        | 디코딩된 매니페스트, 문자열 테이블, 로캘, 버전 정보                           | 호출자 제공 Apktool 런처; [리소스 가이드](docs/apktool-resource-analysis.md)                                                          |
 | Flutter 앱            | Dart 스냅샷 해시, ABI별 라이브러리 해시, 엔진 빌드 출처                       | 없음 (정적 APK 파싱); [Flutter 가이드](docs/flutter-analysis.md)                                                                      |
 | 펌웨어                | 영역, 추출 결과, 네이티브 분석으로 전달할 정보                                | Linux의 Binwalk / Unblob; [펌웨어 가이드](docs/firmware-analysis.md)                                                                  |
-| 기록된 패킷           | 선택 필드, 반복 값, 필터 및 디코딩 규칙                                       | Linux: TShark 4.x + prlimit; [캡처 가이드](docs/packet-captures.md)                                                                   |
-| 기록된 논리 신호      | 디코더 주석, 샘플 범위, 진단 정보                                             | Linux: sigrok-cli 0.7.2 + prlimit; [신호 기록 가이드](docs/signal-recordings.md)                                                      |
 | 패키지 및 리소스      | 파일 목록, 다이제스트, plist, Apple 번들 구조, 추출한 리소스                  | [아티팩트 및 JavaScript 가이드](docs/javascript-artifact-reconstruction.md), [Apple 애플리케이션](docs/apple-application-analysis.md) |
 | 프로세스 동작         | 터미널 출력, 상호작용, 종료 및 파일 시스템 관찰 결과, 실행 비교               | 네이티브 PTY를 지원하는 Linux/macOS; [프로세스 캡처](docs/process-capture.md)                                                         |

@@ -264,7 +261,7 @@ npx rea-agents@latest setup

 ## 스타 기록

-🎉 **GitHub 스타 170,000개, 감사합니다!**
+🎉 **GitHub 스타 110,000개, 감사합니다!**

 REA를 사용하고, 버그를 보고하고, 기능을 요청하고, 빌드를 테스트하고, 수정에 기여해 주신 모든 분께 감사드립니다.

@@ -139,7 +139,6 @@ REA wymaga Node.js 22.x (>=22.19), 24.x (>=24.11) lub 26+ oraz npm. Dodatkowe na
 | JavaScript / Electron                   | Moduły, importy, mapy źródeł, trasy, IPC i powiązania z natywnymi dodatkami                                           | Node.js i npm; [analiza aplikacji](https://rea.tools/pl/guides/javascript/)                                                             |
 | Strony internetowe                      | Struktura strony, skrypty, obserwacje sieciowe i zamówione zrzuty ekranu                                              | Przeglądarka z rodziny Chrome; [analiza w przeglądarce](https://rea.tools/pl/guides/browser/)                                           |
 | Zapisane przechwycenia ruchu sieciowego | Żądania, odpowiedzi, dostępne dane przesyłane i lokalizacje źródłowe                                                  | HAR; mitmdump w systemie Linux dla natywnych przechwyceń mitmproxy; [przewodnik przechwytywania](docs/web-network-captures.md)          |
-| Przechwytywanie pakietów                | Punkty końcowe, DNS, TLS SNI, dystrybucja protokołów i żądania HTTP                                                   | Dostarczone przez wywołującego tshark i capinfos; [przewodnik pcap](docs/pcap-analysis.md)                                              |
 | Zestawy .NET                            | Metadane, instrukcje CIL, zadeklarowane zależności natywne i porównania kompilacji                                    | Analiza statyczna; [przewodnik kodu zarządzanego](docs/managed-code-analysis.md)                                                        |
 | Pakiety APK dla Androida                | Deklaracje manifestu, klasy, zdekompilowane metody i odwołania                                                        | JADX bez interfejsu graficznego i pełny JDK w systemach Linux/macOS/Windows x64; [przewodnik Androida](docs/android-analysis.md)        |
 | Urządzenia z Androidem                  | Urządzenia, pakiety, procesy, logi, zrzuty, zrzuty ekranu oraz transfery APK/plików                                   | adb dostarczony przez wywołującego (emulator lub urządzenie); [przewodnik ADB](docs/adb-device-analysis.md)                             |
@@ -147,8 +146,6 @@ REA wymaga Node.js 22.x (>=22.19), 24.x (>=24.11) lub 26+ oraz npm. Dodatkowe na
 | Zasoby Androida                         | Zdekodowany manifest, tablice ciągów, języki i informacje o wersji                                                    | Należący do wywołującego launcher Apktool; [przewodnik zasobów](docs/apktool-resource-analysis.md)                                      |
 | Aplikacje Flutter                       | Hash migawki Dart, sumy bibliotek per ABI i pochodzenie kompilacji silnika                                            | Brak (statyczna analiza APK); [przewodnik Flutter](docs/flutter-analysis.md)                                                            |
 | Oprogramowanie układowe                 | Regiony, wyniki wyodrębniania i przekazanie do analizy kodu natywnego                                                 | Binwalk / Unblob w systemie Linux; [przewodnik oprogramowania układowego](docs/firmware-analysis.md)                                    |
-| Zapisane pakiety                        | Wybrane pola, powtarzane wartości, filtry i reguły dekodowania                                                        | Linux: TShark 4.x + prlimit; [przewodnik po przechwyconych pakietach](docs/packet-captures.md)                                          |
-| Zapisane sygnały logiczne               | Adnotacje dekodera, zakresy próbek i diagnostyka                                                                      | Linux: sigrok-cli 0.7.2 + prlimit; [przewodnik po sygnałach](docs/signal-recordings.md)                                                 |
 | Pakiety i zasoby                        | Spisy plików, skróty, pliki plist, struktura pakietów Apple i wyodrębnione zasoby                                     | [Przewodnik artefaktów i JavaScript](docs/javascript-artifact-reconstruction.md), [aplikacje Apple](docs/apple-application-analysis.md) |
 | Zachowanie procesów                     | Wyjście terminala, interakcje, obserwacje zakończenia i systemu plików oraz porównania uruchomień                     | Linux/macOS z natywnym PTY; [przechwytywanie procesów](docs/process-capture.md)                                                         |

@@ -262,7 +259,7 @@ Zgłaszaj podatności zgodnie z [SECURITY.md](SECURITY.md).

 ## Historia gwiazdek

-🎉 **170 000 gwiazdek na GitHubie — dziękujemy!**
+🎉 **110 000 gwiazdek na GitHubie — dziękujemy!**

 Dziękujemy wszystkim, którzy używają REA, zgłaszają błędy, proponują nowe funkcje, testują kompilacje i przesyłają poprawki.

@@ -139,7 +139,6 @@ O REA requer Node.js 22.x (>=22.19), 24.x (>=24.11) ou 26+, além do npm. As fer
 | JavaScript / Electron       | Módulos, importações, source maps, rotas, IPC e relações com complementos nativos                                       | Node.js e npm; [análise de aplicativos](https://rea.tools/pt-BR/guides/javascript/)                                                   |
 | Sites                       | Estrutura da página, scripts, observações de rede e capturas de tela solicitadas                                        | Um navegador da família Chrome; [análise do navegador](https://rea.tools/pt-BR/guides/browser/)                                       |
 | Capturas de rede salvas     | Requisições, respostas, payloads acessíveis e localizações de origem                                                    | HAR; mitmdump no Linux para capturas no formato nativo do mitmproxy; [guia de capturas](docs/web-network-captures.md)                 |
-| Capturas de pacotes         | Endpoints, DNS, TLS SNI, distribuição de protocolos e requisições HTTP                                                  | tshark e capinfos fornecidos pelo chamador; [guia pcap](docs/pcap-analysis.md)                                                        |
 | Assemblies .NET             | Metadados, instruções CIL, dependências nativas declaradas e comparações de builds                                      | Inspeção estática; [guia de código gerenciado](docs/managed-code-analysis.md)                                                         |
 | APKs Android                | Declarações do manifesto, classes, métodos descompilados e referências                                                  | JADX sem interface gráfica e um JDK completo no Linux/macOS/Windows x64; [guia de Android](docs/android-analysis.md)                  |
 | Dispositivos Android        | Dispositivos, pacotes, processos, logs, despejos, capturas de tela e transferências de APK/arquivos                     | adb fornecido pelo chamador (emulador ou aparelho); [guia de ADB](docs/adb-device-analysis.md)                                        |
@@ -147,8 +146,6 @@ O REA requer Node.js 22.x (>=22.19), 24.x (>=24.11) ou 26+, além do npm. As fer
 | Recursos do Android         | Manifesto decodificado, tabelas de strings, idiomas e fatos de versão                                                   | Lançador do Apktool fornecido pelo chamador; [guia de recursos](docs/apktool-resource-analysis.md)                                    |
 | Aplicativos Flutter         | Hash de snapshot Dart, hashes de bibliotecas por ABI e procedência de build do motor                                    | Nenhuma (análise estática de APK); [guia Flutter](docs/flutter-analysis.md)                                                           |
 | Firmware                    | Regiões, resultados de extração e encaminhamentos à análise nativa                                                      | Binwalk / Unblob no Linux; [guia de firmware](docs/firmware-analysis.md)                                                              |
-| Pacotes gravados            | Campos selecionados, valores repetidos, filtros e regras de decodificação                                               | Linux: TShark 4.x + prlimit; [guia de capturas](docs/packet-captures.md)                                                              |
-| Sinais lógicos gravados     | Anotações do decodificador, intervalos de amostras e diagnósticos                                                       | Linux: sigrok-cli 0.7.2 + prlimit; [guia de sinais](docs/signal-recordings.md)                                                        |
 | Pacotes e recursos          | Inventários de arquivos, digests, plists, estrutura de bundles Apple e recursos extraídos                               | [Guia de artefatos e JavaScript](docs/javascript-artifact-reconstruction.md), [aplicativos Apple](docs/apple-application-analysis.md) |
 | Comportamento de processos  | Saída do terminal, interações, observações de encerramento e do sistema de arquivos, e comparações entre execuções      | Linux/macOS com PTY nativo; [captura de processos](docs/process-capture.md)                                                           |

@@ -262,7 +259,7 @@ Relate vulnerabilidades conforme [SECURITY.md](SECURITY.md).

 ## Histórico de estrelas

-🎉 **170.000 estrelas no GitHub — muito obrigado!**
+🎉 **110.000 estrelas no GitHub — muito obrigado!**

 Obrigado a todos que usam o REA, relatam bugs, sugerem funcionalidades, testam builds e contribuem com correções.

@@ -130,27 +130,24 @@ npx rea-agents@latest setup

 REA требует Node.js 22.x (>=22.19), 24.x (>=24.11) или 26+, а также npm. Дополнительные инструменты и поддерживаемые системы зависят от цели:

-| Цель                          | Что возвращает REA                                                                                                         | Требования и руководство                                                                                                                     |
-| ----------------------------- | -------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------- |
-| Нативные бинарные файлы       | Псевдокод, ассемблер, строки, символы, вызовы и ссылки                                                                     | Hopper, Ghidra или IDA; [нативный анализ](https://rea.tools/ru/guides/native/)                                                               |
-| Структура ELF без запуска     | Секции, сегменты, исходные символы/релокации и возможные механизмы защиты по данным статического анализа                   | pwntools, предоставленный вызывающей стороной, в Linux x64; [диагностика бинарных файлов](docs/binary-diagnostics.md)                        |
-| Байт-код EVM                  | Селекторы диспетчеризации, смещения байтов, предполагаемые аргументы и изменяемость состояния                              | Локальные необработанные байты или шестнадцатеричное представление в Linux x64; [руководство по EVM без запуска](docs/evm-bytecode.md)       |
-| Записанные сбои Linux         | Необработанные записи note, регистры/сигналы каждого записанного потока и необязательные кандидаты сопоставления с памятью | pwntools, предоставленный вызывающей стороной, в Linux x64; необязательные GDB/pwndbg; [записанные сбои](docs/recorded-crashes.md)           |
-| JavaScript / Electron         | Модули, импорты, карты исходного кода, маршруты, IPC и связи с нативными дополнениями                                      | Node.js и npm; [анализ приложений](https://rea.tools/ru/guides/javascript/)                                                                  |
-| Сайты                         | Структура страницы, скрипты, наблюдения за сетью и запрошенные снимки экрана                                               | Браузер семейства Chrome; [анализ браузера](https://rea.tools/ru/guides/browser/)                                                            |
-| Сохранённые сетевые захваты   | Запросы, ответы, доступные полезные данные и позиции в источнике                                                           | HAR; mitmdump в Linux для захватов в собственном формате mitmproxy; [руководство по сетевым захватам](docs/web-network-captures.md)          |
-| Сборки .NET                   | Метаданные, инструкции CIL, объявленные нативные зависимости и сравнения сборок                                            | Статическое исследование; [руководство по управляемому коду](docs/managed-code-analysis.md)                                                  |
-| Android APK                   | Объявления манифеста, классы, декомпилированные методы и ссылки                                                            | JADX без графического интерфейса и полный JDK в Linux/macOS/Windows x64; [руководство по Android](docs/android-analysis.md)                  |
-| Устройства Android            | Устройства, пакеты, процессы, журналы, дампы, снимки экрана и передача APK/файлов                                          | adb, предоставленный вызывающей стороной (эмулятор или устройство); [руководство по ADB](docs/adb-device-analysis.md)                        |
-| Проекты JEB                   | Единицы проекта от движка, дайджесты артефактов и псевдокод типов/методов                                                  | Запущенный вызывающей стороной клиент JEB с интерфейсом MCP, выбирается через REA_JEB_MCP_URL; [руководство по JEB](docs/jeb-analysis.md)    |
-| Ресурсы Android               | Декодированный манифест, таблицы строк, языки и сведения о версии                                                          | Запуск Apktool, предоставленный вызывающей стороной; [руководство по ресурсам](docs/apktool-resource-analysis.md)                            |
-| Приложения Flutter            | Хеш снапшота Dart, дайджесты библиотек по ABI и происхождение сборки движка                                                | Не требуется (статический разбор APK); [руководство по Flutter](docs/flutter-analysis.md)                                                    |
-| Прошивки                      | Области, результаты извлечения и передача в нативный анализ                                                                | Binwalk / Unblob в Linux; [руководство по прошивкам](docs/firmware-analysis.md)                                                              |
-| Записанные пакеты             | Выбранные поля, повторяющиеся значения, фильтры и правила декодирования                                                    | Linux: TShark 4.x + prlimit; [руководство по захватам](docs/packet-captures.md)                                                              |
-| Захват пакетов                | Конечные точки, DNS, TLS SNI, распределение протоколов и HTTP-запросы                                                      | Предоставленные вызывающей стороной tshark и capinfos; [руководство по pcap](docs/pcap-analysis.md)                                          |
-| Записанные логические сигналы | Аннотации декодера, диапазоны отсчётов и диагностика                                                                       | Linux: sigrok-cli 0.7.2 + prlimit; [руководство по сигналам](docs/signal-recordings.md)                                                      |
-| Пакеты и ресурсы              | Списки файлов, хеши, plist, структура пакетов Apple и извлечённые ресурсы                                                  | [Руководство по артефактам и JavaScript](docs/javascript-artifact-reconstruction.md), [приложения Apple](docs/apple-application-analysis.md) |
-| Поведение процессов           | Вывод терминала, взаимодействия, наблюдения за завершением и файловой системой, сравнения запусков                         | Linux/macOS с нативным PTY; [захват процессов](docs/process-capture.md)                                                                      |
+| Цель                        | Что возвращает REA                                                                                                         | Требования и руководство                                                                                                                     |
+| --------------------------- | -------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------- |
+| Нативные бинарные файлы     | Псевдокод, ассемблер, строки, символы, вызовы и ссылки                                                                     | Hopper, Ghidra или IDA; [нативный анализ](https://rea.tools/ru/guides/native/)                                                               |
+| Структура ELF без запуска   | Секции, сегменты, исходные символы/релокации и возможные механизмы защиты по данным статического анализа                   | pwntools, предоставленный вызывающей стороной, в Linux x64; [диагностика бинарных файлов](docs/binary-diagnostics.md)                        |
+| Байт-код EVM                | Селекторы диспетчеризации, смещения байтов, предполагаемые аргументы и изменяемость состояния                              | Локальные необработанные байты или шестнадцатеричное представление в Linux x64; [руководство по EVM без запуска](docs/evm-bytecode.md)       |
+| Записанные сбои Linux       | Необработанные записи note, регистры/сигналы каждого записанного потока и необязательные кандидаты сопоставления с памятью | pwntools, предоставленный вызывающей стороной, в Linux x64; необязательные GDB/pwndbg; [записанные сбои](docs/recorded-crashes.md)           |
+| JavaScript / Electron       | Модули, импорты, карты исходного кода, маршруты, IPC и связи с нативными дополнениями                                      | Node.js и npm; [анализ приложений](https://rea.tools/ru/guides/javascript/)                                                                  |
+| Сайты                       | Структура страницы, скрипты, наблюдения за сетью и запрошенные снимки экрана                                               | Браузер семейства Chrome; [анализ браузера](https://rea.tools/ru/guides/browser/)                                                            |
+| Сохранённые сетевые захваты | Запросы, ответы, доступные полезные данные и позиции в источнике                                                           | HAR; mitmdump в Linux для захватов в собственном формате mitmproxy; [руководство по сетевым захватам](docs/web-network-captures.md)          |
+| Сборки .NET                 | Метаданные, инструкции CIL, объявленные нативные зависимости и сравнения сборок                                            | Статическое исследование; [руководство по управляемому коду](docs/managed-code-analysis.md)                                                  |
+| Android APK                 | Объявления манифеста, классы, декомпилированные методы и ссылки                                                            | JADX без графического интерфейса и полный JDK в Linux/macOS/Windows x64; [руководство по Android](docs/android-analysis.md)                  |
+| Устройства Android          | Устройства, пакеты, процессы, журналы, дампы, снимки экрана и передача APK/файлов                                          | adb, предоставленный вызывающей стороной (эмулятор или устройство); [руководство по ADB](docs/adb-device-analysis.md)                        |
+| Проекты JEB                 | Единицы проекта от движка, дайджесты артефактов и псевдокод типов/методов                                                  | Запущенный вызывающей стороной клиент JEB с интерфейсом MCP, выбирается через REA_JEB_MCP_URL; [руководство по JEB](docs/jeb-analysis.md)    |
+| Ресурсы Android             | Декодированный манифест, таблицы строк, языки и сведения о версии                                                          | Запуск Apktool, предоставленный вызывающей стороной; [руководство по ресурсам](docs/apktool-resource-analysis.md)                            |
+| Приложения Flutter          | Хеш снапшота Dart, дайджесты библиотек по ABI и происхождение сборки движка                                                | Не требуется (статический разбор APK); [руководство по Flutter](docs/flutter-analysis.md)                                                    |
+| Прошивки                    | Области, результаты извлечения и передача в нативный анализ                                                                | Binwalk / Unblob в Linux; [руководство по прошивкам](docs/firmware-analysis.md)                                                              |
+| Пакеты и ресурсы            | Списки файлов, хеши, plist, структура пакетов Apple и извлечённые ресурсы                                                  | [Руководство по артефактам и JavaScript](docs/javascript-artifact-reconstruction.md), [приложения Apple](docs/apple-application-analysis.md) |
+| Поведение процессов         | Вывод терминала, взаимодействия, наблюдения за завершением и файловой системой, сравнения запусков                         | Linux/macOS с нативным PTY; [захват процессов](docs/process-capture.md)                                                                      |

 Статическое исследование JavaScript и .NET читает предоставленные файлы, не запуская приложение. Захват во время выполнения запускает выбранную цель или взаимодействует с ней с правами вашего пользователя; соответствующие руководства описывают последствия.

@@ -262,7 +259,7 @@ npx rea-agents@latest setup

 ## История звёзд

-🎉 **170 000 звёзд на GitHub — спасибо!**
+🎉 **110 000 звёзд на GitHub — спасибо!**

 Спасибо всем, кто использует REA, сообщает об ошибках, предлагает новые функции, тестирует сборки и помогает с исправлениями.

@@ -139,7 +139,6 @@ REA ต้องใช้ Node.js 22.x (>=22.19), 24.x (>=24.11) หรือ 26
 | JavaScript / Electron        | โมดูล การนำเข้า ซอร์สแมป เส้นทาง IPC และความสัมพันธ์กับส่วนเสริมเนทีฟ                      | Node.js และ npm; [การวิเคราะห์แอปพลิเคชัน](https://rea.tools/th/guides/javascript/)                                                |
 | เว็บไซต์                       | โครงสร้างหน้า สคริปต์ ข้อมูลเครือข่ายที่สังเกตได้ และภาพหน้าจอที่ร้องขอ                         | เบราว์เซอร์ในตระกูล Chrome; [การวิเคราะห์ผ่านเบราว์เซอร์](https://rea.tools/th/guides/browser/)                                        |
 | ข้อมูลเครือข่ายที่บันทึกไว้           | คำขอ คำตอบ เพย์โหลดที่ปรากฏ และตำแหน่งต้นทาง                                         | HAR; mitmdump บน Linux สำหรับข้อมูลที่บันทึกในรูปแบบเนทีฟของ mitmproxy; [คู่มือการบันทึกข้อมูล](docs/web-network-captures.md)                  |
-| การจับแพ็กเก็ต                  | จุดเชื่อมต่อ, DNS, TLS SNI, การกระจายโปรโตคอล และคำขอ HTTP                          | tshark และ capinfos ที่ผู้เรียกจัดเตรียม; [คู่มือ pcap](docs/pcap-analysis.md)                                                           |
 | แอสเซมบลี .NET                | เมทาดาทา คำสั่ง CIL การพึ่งพาเนทีฟที่ประกาศไว้ และการเปรียบเทียบผลการบิลด์                  | การตรวจสอบแบบสถิต; [คู่มือโค้ดแบบจัดการ](docs/managed-code-analysis.md)                                                              |
 | APK ของ Android              | การประกาศใน manifest คลาส เมธอดที่ดีคอมไพล์ และการอ้างอิง                             | JADX แบบไม่มี GUI และ JDK แบบเต็มบน Linux/macOS/Windows x64; [คู่มือ Android](docs/android-analysis.md)                              |
 | อุปกรณ์ Android                | อุปกรณ์ แพ็กเกจ โพรเซส บันทึก ดัมพ์ ภาพหน้าจอ และการถ่ายโอน APK/ไฟล์                      | adb ที่ผู้เรียกจัดเตรียม (โปรแกรมจำลองหรืออุปกรณ์จริง); [คู่มือ ADB](docs/adb-device-analysis.md)                                            |
@@ -147,8 +146,6 @@ REA ต้องใช้ Node.js 22.x (>=22.19), 24.x (>=24.11) หรือ 26
 | ทรัพยากร Android              | ไฟล์ manifest ที่ถอดรหัสแล้ว ตารางสตริง ภาษา และข้อมูลเวอร์ชัน                            | ตัวเรียก Apktool ที่ผู้เรียกจัดเตรียม; [คู่มือทรัพยากร](docs/apktool-resource-analysis.md)                                                  |
 | แอป Flutter                  | แฮชสแนปชอต Dart, แฮชไลบรารีราย ABI และที่มาของบิลด์เอนจิน                             | ไม่ต้อง (วิเคราะห์ APK แบบ static); [คู่มือ Flutter](docs/flutter-analysis.md)                                                        |
 | เฟิร์มแวร์                      | พื้นที่ข้อมูล ผลการแตกไฟล์ และการส่งต่อไปวิเคราะห์เนทีฟ                                     | Binwalk / Unblob บน Linux; [คู่มือเฟิร์มแวร์](docs/firmware-analysis.md)                                                             |
-| แพ็กเก็ตที่บันทึกไว้                | ฟิลด์ที่เลือก ค่าซ้ำ ตัวกรอง และกฎการถอดรหัส                                             | Linux: TShark 4.x + prlimit; [คู่มือไฟล์แคปเจอร์](docs/packet-captures.md)                                                          |
-| สัญญาณลอจิกที่บันทึกไว้             | คำอธิบายจากตัวถอดรหัส ช่วงตัวอย่าง และข้อมูลวินิจฉัย                                       | Linux: sigrok-cli 0.7.2 + prlimit; [คู่มือสัญญาณ](docs/signal-recordings.md)                                                       |
 | แพ็กเกจและทรัพยากร             | รายการไฟล์ ค่าแฮช plist โครงสร้างบันเดิลของ Apple และทรัพยากรที่แตกออกมา                | [คู่มืออาร์ติแฟกต์และ JavaScript](docs/javascript-artifact-reconstruction.md), [แอปพลิเคชัน Apple](docs/apple-application-analysis.md) |
 | พฤติกรรมของโปรเซส             | เอาต์พุตเทอร์มินัล การโต้ตอบ ข้อมูลการสิ้นสุดและระบบไฟล์ที่สังเกตได้ และการเปรียบเทียบการรัน       | Linux/macOS ที่มี PTY เนทีฟ; [การบันทึกโปรเซส](docs/process-capture.md)                                                              |

@@ -262,7 +259,7 @@ npx rea-agents@latest setup

 ## ประวัติดาว

-🎉 **170,000 ดาวบน GitHub — ขอบคุณทุกคน!**
+🎉 **110,000 ดาวบน GitHub — ขอบคุณทุกคน!**

 ขอบคุณทุกคนที่ใช้ REA รายงานบั๊ก เสนอฟีเจอร์ ทดสอบบิลด์ และช่วยแก้ไข

@@ -139,7 +139,6 @@ REA; Node.js 22.x (>=22.19), 24.x (>=24.11) veya 26+ ve npm gerektirir. Ek araç
 | JavaScript / Electron                   | Modüller, içe aktarmalar, kaynak haritaları, rotalar, IPC ve yerel eklenti ilişkileri                       | Node.js ve npm; [uygulama analizi](https://rea.tools/tr/guides/javascript/)                                                            |
 | Web siteleri                            | Sayfa yapısı, betikler, ağ gözlemleri ve istenen ekran görüntüleri                                          | Chrome ailesinden bir tarayıcı; [tarayıcı analizi](https://rea.tools/tr/guides/browser/)                                               |
 | Kaydedilmiş ağ yakalamaları             | İstekler, yanıtlar, erişilebilir yük içerikleri ve kaynak konumları                                         | HAR; mitmproxy'nin kendi biçimindeki yakalamalar için Linux üzerinde mitmdump; [ağ yakalama rehberi](docs/web-network-captures.md)     |
-| Paket yakalamaları                      | Uç noktalar, DNS, TLS SNI, protokol dağılımı ve HTTP istekleri                                              | Çağıranın sağladığı tshark ve capinfos; [pcap rehberi](docs/pcap-analysis.md)                                                          |
 | .NET derlemeleri                        | Meta veriler, CIL talimatları, bildirilmiş yerel bağımlılıklar ve derleme karşılaştırmaları                 | Statik inceleme; [yönetilen kod rehberi](docs/managed-code-analysis.md)                                                                |
 | Android APK'leri                        | Manifest bildirimleri, sınıflar, tersine derlenmiş metotlar ve referanslar                                  | Linux/macOS/Windows x64 üzerinde arayüzsüz JADX ve tam bir JDK; [Android rehberi](docs/android-analysis.md)                            |
 | Android cihazları                       | Cihazlar, paketler, süreçler, günlükler, dökümler, ekran görüntüleri ve APK/dosya aktarımları               | Çağıranın sağladığı adb (emülatör veya cihaz); [ADB rehberi](docs/adb-device-analysis.md)                                              |
@@ -147,8 +146,6 @@ REA; Node.js 22.x (>=22.19), 24.x (>=24.11) veya 26+ ve npm gerektirir. Ek araç
 | Android kaynakları                      | Çözülmüş manifest, dize tabloları, diller ve sürüm bilgileri                                                | Çağıranın sağladığı Apktool başlatıcısı; [kaynak rehberi](docs/apktool-resource-analysis.md)                                           |
 | Flutter uygulamaları                    | Dart anlık görüntü karması, ABI başına kitaplık özetleri ve motor derleme kökeni                            | Yok (statik APK çözümleme); [Flutter rehberi](docs/flutter-analysis.md)                                                                |
 | Donanım yazılımı                        | Bölgeler, çıkarma sonuçları ve yerel kod analizine devirler                                                 | Linux üzerinde Binwalk / Unblob; [donanım yazılımı rehberi](docs/firmware-analysis.md)                                                 |
-| Kaydedilmiş paketler                    | Seçilen alanlar, yinelenen değerler, filtreler ve çözümleme kuralları                                       | Linux: TShark 4.x + prlimit; [yakalama kılavuzu](docs/packet-captures.md)                                                              |
-| Kaydedilmiş mantık sinyalleri           | Kod çözücü açıklamaları, örnek aralıkları ve tanılama                                                       | Linux: sigrok-cli 0.7.2 + prlimit; [sinyal kılavuzu](docs/signal-recordings.md)                                                        |
 | Paketler ve kaynaklar                   | Dosya envanterleri, özet değerleri, plist'ler, Apple paket yapısı ve çıkarılmış kaynaklar                   | [Artefakt ve JavaScript rehberi](docs/javascript-artifact-reconstruction.md), [Apple uygulamaları](docs/apple-application-analysis.md) |
 | Süreç davranışı                         | Terminal çıktısı, etkileşimler, sonlanma ve dosya sistemi gözlemleri, çalıştırma karşılaştırmaları          | Yerel PTY ile Linux/macOS; [süreç yakalama](docs/process-capture.md)                                                                   |

@@ -262,7 +259,7 @@ Güvenlik açıklarını [SECURITY.md](SECURITY.md) üzerinden bildirin.

 ## Yıldız geçmişi

-🎉 **GitHub'da 170.000 yıldız — teşekkürler!**
+🎉 **GitHub'da 110.000 yıldız — teşekkürler!**

 REA'yı kullanan, hata bildiren, özellik talep eden, derlemeleri test eden ve düzeltmelere katkıda bulunan herkese teşekkürler.

@@ -139,7 +139,6 @@ REA потребує Node.js 22.x (>=22.19), 24.x (>=24.11) або 26+, а та
 | JavaScript / Electron                | Модулі, імпорти, карти вихідного коду, маршрути, IPC і зв'язки з нативними доповненнями                           | Node.js і npm; [аналіз застосунків](https://rea.tools/uk/guides/javascript/)                                                                        |
 | Сайти                                | Структура сторінки, скрипти, мережеві спостереження й запитані знімки екрана                                      | Браузер сімейства Chrome; [аналіз браузера](https://rea.tools/uk/guides/browser/)                                                                   |
 | Збережені мережеві захоплення        | Запити, відповіді, доступні корисні дані та місця в джерелі                                                       | HAR; mitmdump у Linux для захоплень у власному форматі mitmproxy; [посібник мережевих захоплень](docs/web-network-captures.md)                      |
-| Захоплення пакетів                   | Кінцеві точки, DNS, TLS SNI, розподіл протоколів та HTTP-запити                                                   | Надані викликаючою стороною tshark та capinfos; [підручник pcap](docs/pcap-analysis.md)                                                             |
 | Збірки .NET                          | Метадані, інструкції CIL, оголошені нативні залежності й порівняння збірок                                        | Статична перевірка; [посібник керованого коду](docs/managed-code-analysis.md)                                                                       |
 | Android APK                          | Оголошення маніфесту, класи, декомпільовані методи й посилання                                                    | JADX без графічного інтерфейсу й повний JDK у Linux/macOS/Windows x64; [посібник Android](docs/android-analysis.md)                                 |
 | Пристрої Android                     | Пристрої, пакети, процеси, журнали, дампи, знімки екрана та передавання APK/файлів                                | adb, наданий викликаючою стороною (емулятор або пристрій); [підручник ADB](docs/adb-device-analysis.md)                                             |
@@ -147,8 +146,6 @@ REA потребує Node.js 22.x (>=22.19), 24.x (>=24.11) або 26+, а та
 | Ресурси Android                      | Декодований маніфест, таблиці рядків, мови та відомості про версію                                                | Засіб запуску Apktool, наданий викликаючою стороною; [підручник ресурсів](docs/apktool-resource-analysis.md)                                        |
 | Додатки Flutter                      | Хеш знімка Dart, дайджести бібліотек за ABI та походження збірки рушія                                            | Не потрібні (статичний розбір APK); [підручник Flutter](docs/flutter-analysis.md)                                                                   |
 | Прошивки                             | Області, результати видобування й передавання до нативного аналізу                                                | Binwalk / Unblob у Linux; [посібник прошивок](docs/firmware-analysis.md)                                                                            |
-| Записані пакети                      | Вибрані поля, повторювані значення, фільтри та правила декодування                                                | Linux: TShark 4.x + prlimit; [посібник із записів пакетів](docs/packet-captures.md)                                                                 |
-| Записані логічні сигнали             | Анотації декодера, діапазони відліків і діагностика                                                               | Linux: sigrok-cli 0.7.2 + prlimit; [посібник із сигналів](docs/signal-recordings.md)                                                                |
 | Пакети й ресурси                     | Переліки файлів, хеші, plist, структура пакетів Apple та видобуті ресурси                                         | [Посібник артефактів і JavaScript](docs/javascript-artifact-reconstruction.md), [застосунки Apple](docs/apple-application-analysis.md)              |
 | Поведінка процесів                   | Вивід термінала, взаємодії, спостереження за завершенням і файловою системою та порівняння запусків               | Linux/macOS із нативним PTY; [захоплення процесів](docs/process-capture.md)                                                                         |

@@ -262,7 +259,7 @@ npx rea-agents@latest setup

 ## Історія зірок

-🎉 **170 000 зірок на GitHub — дякуємо!**
+🎉 **110 000 зірок на GitHub — дякуємо!**

 Дякуємо всім, хто використовує REA, повідомляє про помилки, пропонує нові функції, тестує збірки й допомагає з виправленнями.

@@ -139,7 +139,6 @@ REA yêu cầu Node.js 22.x (>=22.19), 24.x (>=24.11) hoặc 26+, cùng với np
 | JavaScript / Electron         | Mô-đun, các khai báo import, source map, tuyến, IPC và quan hệ với tiện ích mở rộng mã máy                      | Node.js và npm; [phân tích ứng dụng](https://rea.tools/vi/guides/javascript/)                                                                 |
 | Trang web                     | Cấu trúc trang, script, quan sát mạng và ảnh chụp màn hình được yêu cầu                                         | Trình duyệt thuộc họ Chrome; [phân tích trình duyệt](https://rea.tools/vi/guides/browser/)                                                    |
 | Bản ghi lưu lượng mạng đã lưu | Yêu cầu, phản hồi, payload có thể truy cập và vị trí nguồn                                                      | HAR; mitmdump trên Linux cho bản ghi định dạng gốc của mitmproxy; [hướng dẫn bản ghi mạng](docs/web-network-captures.md)                      |
-| Bắt gói tin                   | Điểm cuối, DNS, TLS SNI, phân bố giao thức và yêu cầu HTTP                                                      | tshark và capinfos do nơi gọi cung cấp; [hướng dẫn pcap](docs/pcap-analysis.md)                                                               |
 | Assembly .NET                 | Siêu dữ liệu, lệnh CIL, các phụ thuộc mã máy được khai báo và so sánh bản dựng                                  | Kiểm tra tĩnh; [hướng dẫn mã được quản lý](docs/managed-code-analysis.md)                                                                     |
 | APK Android                   | Khai báo manifest, lớp, phương thức được dịch ngược và tham chiếu                                               | JADX không giao diện đồ họa và JDK đầy đủ trên Linux/macOS/Windows x64; [hướng dẫn Android](docs/android-analysis.md)                         |
 | Thiết bị Android              | Thiết bị, gói, tiến trình, nhật ký, dump, ảnh chụp màn hình và truyền APK/tệp                                   | adb do nơi gọi cung cấp (trình giả lập hoặc thiết bị); [hướng dẫn ADB](docs/adb-device-analysis.md)                                           |
@@ -147,8 +146,6 @@ REA yêu cầu Node.js 22.x (>=22.19), 24.x (>=24.11) hoặc 26+, cùng với np
 | Tài nguyên Android            | Manifest đã giải mã, bảng chuỗi, ngôn ngữ và thông tin phiên bản                                                | Trình khởi chạy Apktool do nơi gọi cung cấp; [hướng dẫn tài nguyên](docs/apktool-resource-analysis.md)                                        |
 | Ứng dụng Flutter              | Băm snapshot Dart, hash thư viện theo ABI và nguồn gốc build engine                                             | Không cần (phân tích APK tĩnh); [hướng dẫn Flutter](docs/flutter-analysis.md)                                                                 |
 | Phần sụn                      | Các vùng, kết quả trích xuất và dữ liệu chuyển sang phân tích mã máy                                            | Binwalk / Unblob trên Linux; [hướng dẫn phần sụn](docs/firmware-analysis.md)                                                                  |
-| Gói tin đã ghi                | Trường được chọn, giá trị lặp, bộ lọc và quy tắc giải mã                                                        | Linux: TShark 4.x + prlimit; [hướng dẫn bản ghi gói tin](docs/packet-captures.md)                                                             |
-| Tín hiệu logic đã ghi         | Chú thích bộ giải mã, phạm vi mẫu và chẩn đoán                                                                  | Linux: sigrok-cli 0.7.2 + prlimit; [hướng dẫn tín hiệu](docs/signal-recordings.md)                                                            |
 | Gói và tài nguyên             | Danh sách tệp, giá trị băm, plist, cấu trúc bundle Apple và tài nguyên được trích xuất                          | [Hướng dẫn hiện vật phần mềm và JavaScript](docs/javascript-artifact-reconstruction.md), [ứng dụng Apple](docs/apple-application-analysis.md) |
 | Hành vi tiến trình            | Đầu ra terminal, tương tác, quan sát khi thoát và hệ thống tệp, cùng so sánh các lần chạy                       | Linux/macOS có PTY gốc; [ghi lại tiến trình](docs/process-capture.md)                                                                         |

@@ -262,7 +259,7 @@ Báo cáo lỗ hổng theo [SECURITY.md](SECURITY.md).

 ## Lịch sử sao

-🎉 **170.000 sao trên GitHub — xin cảm ơn!**
+🎉 **110.000 sao trên GitHub — xin cảm ơn!**

 Cảm ơn mọi người đã sử dụng REA, báo lỗi, đề xuất tính năng, kiểm thử bản dựng và đóng góp bản sửa lỗi.

@@ -139,7 +139,6 @@ REA 需要 Node.js 22.x（>=22.19）、24.x（>=24.11）或 26+，以及 npm。
 | JavaScript / Electron | 模組、匯入、source map、路由、IPC 和原生附加元件關係            | Node.js 和 npm；[應用分析](https://rea.tools/zh-TW/guides/javascript/)                                                 |
 | 網站                  | 頁面結構、腳本、網路觀察結果和按請求獲取的螢幕擷取畫面          | Chrome 系瀏覽器；[瀏覽器分析](https://rea.tools/zh-TW/guides/browser/)                                                 |
 | 已保存的網路擷取      | 請求、回應、可訪問的酬載和來源位置                              | HAR；原生 mitmproxy 擷取需要 Linux 上的 mitmdump；[擷取指南](docs/web-network-captures.md)                             |
-| 封包擷取              | 端點、DNS、TLS SNI、通訊協定分佈和 HTTP 請求                    | 呼叫端提供的 tshark 和 capinfos；[pcap 指南](docs/pcap-analysis.md)                                                    |
 | .NET 程式集           | 中繼資料、CIL 指令、聲明的原生依賴和建置對比                    | 靜態檢查；[托管程式碼指南](docs/managed-code-analysis.md)                                                              |
 | Android APK           | 清單聲明、類別、反編譯的方法和引用                              | Linux/macOS/Windows x64 上的無界面 JADX 和完整 JDK；[Android 指南](docs/android-analysis.md)                           |
 | Android 裝置          | 裝置、套件、程序、日誌、傾印、螢幕擷取以及 APK/檔案傳輸         | 呼叫端提供的 adb（模擬器或實體裝置）；[ADB 指南](docs/adb-device-analysis.md)                                          |
@@ -147,8 +146,6 @@ REA 需要 Node.js 22.x（>=22.19）、24.x（>=24.11）或 26+，以及 npm。
 | Android 資源          | 解碼後的清單、字串表、語系和版本資訊                            | 呼叫端提供的 Apktool 啟動器；[資源指南](docs/apktool-resource-analysis.md)                                             |
 | Flutter 應用          | Dart 快照雜湊、依 ABI 的程式庫雜湊及引擎建置來源                | 無（靜態 APK 解析）；[Flutter 指南](docs/flutter-analysis.md)                                                          |
 | 韌體                  | 區域、提取結果和轉交原生分析的內容                              | Linux 上的 Binwalk / Unblob；[韌體指南](docs/firmware-analysis.md)                                                     |
-| 封包記錄              | 指定欄位、重複值、篩選條件與解碼規則                            | Linux: TShark 4.x + prlimit; [封包分析指南](docs/packet-captures.md)                                                   |
-| 錄製的邏輯訊號        | 解碼註解、樣本範圍與診斷資訊                                    | Linux: sigrok-cli 0.7.2 + prlimit; [訊號記錄指南](docs/signal-recordings.md)                                           |
 | 軟體包與資源          | 檔案清單、摘要、plist、Apple bundle 結構和提取的資源            | [製品與 JavaScript 指南](docs/javascript-artifact-reconstruction.md)、[Apple 應用](docs/apple-application-analysis.md) |
 | 處理程序行為          | 終端輸出、互動、退出和檔案系統觀察結果，以及執行對比            | 支援原生 PTY 的 Linux/macOS；[處理程序擷取](docs/process-capture.md)                                                   |

@@ -264,7 +261,7 @@ npx rea-agents@latest setup

 ## Star 歷史

-🎉 **GitHub Star 達到 170,000 個，感謝大家！**
+🎉 **GitHub Star 達到 110,000 個，感謝大家！**

 感謝每一位使用 REA、報告錯誤、提出功能需求、測試建置和貢獻修復的朋友。

@@ -139,7 +139,6 @@ REA 需要 Node.js 22.x（>=22.19）、24.x（>=24.11）或 26+，以及 npm。
 | JavaScript / Electron | 模块、导入、source map、路由、IPC 和原生扩展关系              | Node.js 和 npm；[应用分析](https://rea.tools/zh-CN/guides/javascript/)                                                 |
 | 网站                  | 页面结构、脚本、网络观察结果和按请求获取的截图                | Chrome 系浏览器；[浏览器分析](https://rea.tools/zh-CN/guides/browser/)                                                 |
 | 已保存的网络捕获      | 请求、响应、可访问的载荷和来源位置                            | HAR；原生 mitmproxy 捕获需要 Linux 上的 mitmdump；[捕获指南](docs/web-network-captures.md)                             |
-| 数据包捕获            | 端点、DNS、TLS SNI、协议分布和 HTTP 请求                      | 调用方提供的 tshark 和 capinfos；[pcap 指南](docs/pcap-analysis.md)                                                    |
 | .NET 程序集           | 元数据、CIL 指令、声明的原生依赖和构建对比                    | 静态检查；[托管代码指南](docs/managed-code-analysis.md)                                                                |
 | Android APK           | 清单声明、类、反编译的方法和引用                              | Linux/macOS/Windows x64 上的无界面 JADX 和完整 JDK；[Android 指南](docs/android-analysis.md)                           |
 | Android 设备          | 设备、软件包、进程、日志、转储、屏幕截图以及 APK/文件传输     | 调用方提供的 adb（模拟器或实体设备）；[ADB 指南](docs/adb-device-analysis.md)                                          |
@@ -147,8 +146,6 @@ REA 需要 Node.js 22.x（>=22.19）、24.x（>=24.11）或 26+，以及 npm。
 | Android 资源          | 解码后的清单、字符串表、语言区域和版本信息                    | 调用方提供的 Apktool 启动器；[资源指南](docs/apktool-resource-analysis.md)                                             |
 | Flutter 应用          | Dart 快照哈希、按 ABI 的库摘要及引擎构建溯源                  | 无（静态 APK 解析）；[Flutter 指南](docs/flutter-analysis.md)                                                          |
 | 固件                  | 区域、提取结果和转交原生分析的内容                            | Linux 上的 Binwalk / Unblob；[固件指南](docs/firmware-analysis.md)                                                     |
-| 抓包文件              | 指定字段、重复值、过滤条件与解码规则                          | Linux: TShark 4.x + prlimit; [抓包分析指南](docs/packet-captures.md)                                                   |
-| 录制的逻辑信号        | 解码注释、样本范围和诊断信息                                  | Linux: sigrok-cli 0.7.2 + prlimit; [信号记录指南](docs/signal-recordings.md)                                           |
 | 软件包与资源          | 文件清单、摘要、plist、Apple bundle 结构和提取的资源          | [制品与 JavaScript 指南](docs/javascript-artifact-reconstruction.md)、[Apple 应用](docs/apple-application-analysis.md) |
 | 进程行为              | 终端输出、交互、退出和文件系统观察结果，以及运行对比          | 支持原生 PTY 的 Linux/macOS；[进程捕获](docs/process-capture.md)                                                       |

@@ -264,7 +261,7 @@ npx rea-agents@latest setup

 ## Star 历史

-🎉 **GitHub Star 达到 170,000 个，感谢大家！**
+🎉 **GitHub Star 达到 110,000 个，感谢大家！**

 感谢每一位使用 REA、报告错误、提出功能需求、测试构建和贡献修复的朋友。

@@ -24,12 +24,9 @@ provider-dependent behavior to be reproduced safely.

 ## Security boundary

-REA authenticates its Hopper and Ghidra bridges with per-session random
-capability tokens. POSIX uses current-user Unix sockets; Windows Ghidra uses
-authenticated loopback TCP with a private NTFS runtime whose DACL admits only
-the current user and SYSTEM. See [Windows Ghidra P0](docs/windows-ghidra-p0.md#private-runtime-transport-and-lifecycle).
-Tokens are transferred through private session descriptors rather than process
-arguments or environment variables.
+REA authenticates each local provider bridge session with a random capability
+token and a current-user Unix socket. Tokens are transferred through private
+session descriptors rather than process arguments or environment variables.
 This is not a sandbox and does not protect against malicious processes already
 running as the same operating-system user. Opening an untrusted binary
 delegates parsing and analysis to the selected local provider with that user's
@@ -28,13 +28,6 @@ entries preserve the declared license and author metadata and include a clearly
 labeled standard license text. These are documented upstream notice gaps, not
 recovered copyright notices or a claim that attribution has been fully verified.

-The optional `frida@17.23.2` npm archive and tagged Node binding source also
-omit a standalone license/copyright document. Its declared
-`LGPL-2.0 WITH WxWindows-exception-3.1` license is recorded with unchanged
-[Frida licensing text](licenses/frida-17.23.2-COPYING.txt) and the
-[GNU Library GPL v2](licenses/LGPL-2.0.txt). These are licensing supplements,
-not recovered Node binding or prebuild-component copyright notices.
-
 ## Open-source engine credits and licenses

 We thank the maintainers and contributors of the projects below. Their
@@ -106,8 +106,6 @@ public final class ReaGhidraBridge extends HeadlessScript {
    private static final int MAX_HIGH_PCODE_INPUTS_PER_OP = 64;
    private static final int MAX_HIGH_PCODE_DEF_USE_EDGES = 12000;
    private static final Gson GSON = new GsonBuilder().serializeNulls().create();
-    private final Map<FileBytes, Boolean> targetSourceIdentity = new IdentityHashMap<>();
-    private String admittedTargetSha256;
    private static final Set<String> DESCRIPTOR_KEYS = Set.of(
        "transport",
        "endpoint_path",
@@ -209,7 +207,6 @@ public final class ReaGhidraBridge extends HeadlessScript {
                "Ghidra imported-byte digest does not match the admitted target"
            );
        }
-        admittedTargetSha256 = descriptor.targetSha256;
        // GhidraScript wraps run() in a transaction. End it before serving so
        // each edit owns a real outer transaction and can roll back immediately.
        end(true);
@@ -636,7 +633,7 @@ public final class ReaGhidraBridge extends HeadlessScript {
        return result;
    }

-    private JsonObject addressToFileOffset(JsonObject params) throws Exception {
+    private JsonObject addressToFileOffset(JsonObject params) {
        requireKeys(params, Set.of("document", "address"));
        requireDocument(params);
        Address address = requireAddress(params, "address");
@@ -646,15 +643,14 @@ public final class ReaGhidraBridge extends HeadlessScript {
        Long fileOffset = null;
        int mappings = 0;
        for (MemoryBlockSourceInfo source : block.getSourceInfos()) {
-            if (!source.contains(address) || source.getFileBytes().isEmpty() ||
-                !isTargetSource(source.getFileBytes().get())) continue;
+            if (!source.contains(address) || source.getFileBytes().isEmpty()) continue;
            long offset = source.getFileBytesOffset(address);
            if (offset < 0) continue;
            fileOffset = offset;
            mappings++;
        }
        if (mappings != 1)
-            throw new RequestFailure("invalid_request", "Address has " + mappings + " authoritative target-file mappings: " + canonicalAddress(address));
+            throw new RequestFailure("invalid_request", "Address has " + mappings + " authoritative source mappings: " + canonicalAddress(address));
        JsonObject result = new JsonObject();
        result.addProperty("address", canonicalAddress(address));
        result.addProperty("file_offset", fileOffset);
@@ -677,96 +673,14 @@ public final class ReaGhidraBridge extends HeadlessScript {
    private JsonElement procedurePseudocode(JsonObject params) throws Exception {
        requireKeys(params, Set.of("document", "procedure"));
        requireDocument(params);
-        String selector = requireString(params, "procedure");
-        JsonObject selection = new JsonObject();
-        Function function = resolveDecompileProcedure(selector, selection);
-        try {
-            String value = decompiledText(decompile(function));
-            JsonObject result = functionObservation(
-                value == null ? JsonNull.INSTANCE : GSON.toJsonTree(value),
-                noReturnCallLimitations(
-                    currentProgram.getListing().getInstructions(function.getBody(), true)
-                )
-            );
-            if (selection.size() > 0) result.add("selection", selection);
-            return result;
-        } catch (RequestFailure failure) {
-            if (selection.size() == 0) throw failure;
-            // Preserve completed resolution facts without changing the backend's
-            // failure code or suggesting that the successful mapping was invalid.
-            throw new RequestFailure(failure.code, "Selector " + selector +
-                " mapped to analysis address " + selection.get("mapped_address").getAsString() +
-                " and procedure " + canonicalAddress(function.getEntryPoint()) +
-                "; " + failure.getMessage());
-        }
-    }
-
-    private Function resolveDecompileProcedure(String selector, JsonObject selection) throws Exception {
-        String prefix = "file-offset:";
-        boolean explicitOffset = selector.startsWith(prefix);
-        if (!explicitOffset) {
-            try {
-                return resolveProcedure(selector);
-            } catch (RequestFailure failure) {
-                // Existing names/addresses win. Only an unresolved numeric input
-                // can fall back to source coordinates; ambiguity never falls back.
-                if (!failure.code.equals("not_found") || !selector.matches("0x[0-9a-fA-F]+"))
-                    throw failure;
-            }
-        }
-        String coordinate = explicitOffset ? selector.substring(prefix.length()) : selector;
-        if (!coordinate.matches("0x[0-9a-fA-F]+"))
-            throw new RequestFailure("invalid_request", "File offsets require hexadecimal file-offset:0x... syntax");
-        BigInteger parsed = new BigInteger(coordinate.substring(2), 16);
-        if (parsed.compareTo(BigInteger.valueOf(9007199254740991L)) > 0)
-            throw new RequestFailure("invalid_request", "File offset exceeds the exact JSON integer range");
-        long offset = parsed.longValueExact();
-        monitor.checkCancelled();
-        // Ghidra's convenience lookup spans every FileBytes and uses coordinates
-        // local to each object. Only a complete, digest-matched target source
-        // establishes that the caller's offset belongs to the admitted file.
-        Set<Address> mappedAddresses = new java.util.LinkedHashSet<>();
-        for (MemoryBlock block : currentProgram.getMemory().getBlocks()) {
-            for (MemoryBlockSourceInfo source : block.getSourceInfos()) {
-                monitor.checkCancelled();
-                FileBytes backing = source.getFileBytes().orElse(null);
-                if (backing == null || !isTargetSource(backing)) continue;
-                Address mapped = source.locateAddressForFileOffset(offset);
-                if (mapped != null) mappedAddresses.add(mapped);
-            }
-        }
-        List<Address> candidates = new ArrayList<>(mappedAddresses);
-        if (candidates.size() > 1)
-            throw new RequestFailure("ambiguous", "File offset " + coordinate +
-                " has multiple loaded mappings: " + candidates.stream().map(ReaGhidraBridge::canonicalAddress).toList() +
-                "; select an explicit analysis address");
-        if (candidates.isEmpty())
-            throw new RequestFailure("not_found", "File offset " + coordinate +
-                " has no loaded source mapping for the admitted target file; Ghidra image base: " + canonicalAddress(currentProgram.getImageBase()) +
-                ". Inspect mappings with rea inspect-native-load-image <path> --provider ghidra --json or MCP inspect_native_load_image.");
-        Address mapped = candidates.get(0);
-        Function function = functionAtOrContaining(mapped);
-        if (function == null)
-            throw new RequestFailure("not_found", "File offset " + coordinate +
-                " maps to analysis address " + canonicalAddress(mapped) +
-                ", but no procedure starts at or contains that address in the current Ghidra analysis. " +
-                "Choose an observed procedure with CLI rea search <path> . --kind procedures --mode regex --provider ghidra --json or MCP list_procedures.");
-        selection.addProperty("file_offset", offset);
-        selection.addProperty("mapped_address", canonicalAddress(mapped));
-        selection.addProperty("procedure_address", canonicalAddress(function.getEntryPoint()));
-        return function;
-    }
-
-    private boolean isTargetSource(FileBytes source) throws Exception {
-        Boolean observed = targetSourceIdentity.get(source);
-        if (observed != null) return observed;
-        // Original FileBytes are immutable even when analysis memory is edited.
-        // Partial/auxiliary sources remain inspectable but cannot establish an
-        // original-target offset from their object-local coordinates alone.
-        boolean matched = source.getFileOffset() == 0 &&
-            constantTimeEquals(hashFileBytes(source, false), admittedTargetSha256);
-        targetSourceIdentity.put(source, matched);
-        return matched;
+        Function function = resolveProcedure(requireString(params, "procedure"));
+        String value = decompiledText(decompile(function));
+        return functionObservation(
+            value == null ? JsonNull.INSTANCE : GSON.toJsonTree(value),
+            noReturnCallLimitations(
+                currentProgram.getListing().getInstructions(function.getBody(), true)
+            )
+        );
    }

    private JsonElement procedureAssembly(JsonObject params) throws Exception {
@@ -1919,23 +1833,12 @@ public final class ReaGhidraBridge extends HeadlessScript {
        Address address = explicitAddress ? parseReaAddress(value) : tryParseAddress(value);
        if (address == null)
            throw new RequestFailure("not_found", "Unknown Ghidra procedure name or address: " + value);
-        Function function = functionAtOrContaining(address);
-        if (function == null)
-            // Other procedure operations retain their analysis-address semantics.
-            throw new RequestFailure("not_found", "No procedure exists at the requested address: " + value +
-                "; Ghidra image base: " + canonicalAddress(currentProgram.getImageBase()) +
-                ". Choose an observed analysis address. CLI: rea search <path> . --kind procedures --mode regex --provider ghidra --json; " +
-                "MCP: list_procedures. Inspect the loaded base and source mappings with CLI rea analyze <path> --provider ghidra --json " +
-                "and rea inspect-native-load-image <path> --provider ghidra --json, or MCP binary_overview and inspect_native_load_image. " +
-                "Repeat the original target options. For decompile, select source coordinates explicitly with --file-offset=0x... or MCP procedure file-offset:0x....");
-        return function;
-    }
-
-    private Function functionAtOrContaining(Address address) {
        Function function = currentProgram.getFunctionManager().getFunctionAt(address);
-        return function == null && address.isMemoryAddress()
-            ? currentProgram.getFunctionManager().getFunctionContaining(address)
-            : function;
+        if (function == null && address.isMemoryAddress())
+            function = currentProgram.getFunctionManager().getFunctionContaining(address);
+        if (function == null)
+            throw new RequestFailure("not_found", "No procedure exists at the requested address: " + value);
+        return function;
    }

    private JsonObject nativeApiBoundary(
@@ -93,7 +93,7 @@ def project_record(state, secrets):
            safe_bytes, credential_url = transport_value(value, path, transport_url)
            content_base64 = base64.b64encode(value).decode("ascii")
            digest = hashlib.sha256(value).hexdigest()
-            hidden = any(secret in value or secret in safe_bytes for secret in byte_secrets) or any(secret in content_base64 or secret in digest or secret in str(len(value)) for secret in secrets)
+            hidden = any(secret in value or secret in safe_bytes for secret in byte_secrets) or any(secret in content_base64 or secret in digest for secret in secrets)
            safe_text = None
            try:
                safe_text = safe_bytes.decode("utf-8", errors="strict")
@@ -37,19 +37,12 @@ export default defineConfig({
            link: "/javascript-application-workflows",
          },
          { text: "Browser observation", link: "/browser-observation" },
-          {
-            text: "Web network captures",
-            link: "/web-network-captures",
-          },
          { text: "Electron observation", link: "/electron-observation" },
          { text: "Process capture", link: "/process-capture" },
          { text: ".NET assemblies", link: "/managed-code-analysis" },
          { text: "Android applications", link: "/android-analysis" },
          { text: "Apple applications", link: "/apple-application-analysis" },
          { text: "Firmware", link: "/firmware-analysis" },
-          { text: "SQLite databases", link: "/sqlite-databases" },
-          { text: "Packet captures", link: "/packet-captures" },
-          { text: "Signal recordings", link: "/signal-recordings" },
        ],
      },
      {
@@ -136,8 +136,8 @@ existing analysis families directly, for example
 ## Resource and lifecycle limits

 - Caller values reach adb only as positional arguments in fixed vectors;
-  no tool accepts an arbitrary shell command line, `input`, or `monkey`.
-  The app/activity lifecycle tools use `am start -W` and `am force-stop`.
+  no tool accepts an arbitrary shell command line, and UI interaction
+  (`input`, `am`, `monkey`) is deliberately not exposed.
 - 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. Exceeded budgets report `resource_constraint`; stopped
@@ -148,11 +148,6 @@ existing analysis families directly, for example
 - 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.
- 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
-  its recoverable `local_path`, the original `adb_reported_path`, and an unknown
-  digest status. Later operations and shutdown preserve this retained evidence.
 - Failed package acquisition rollback retains its directory identity and retries
  cleanup before later work and during shutdown. Cleanup refuses a replacement
  directory. Terminal shutdown stops admission and drains active operations.
@@ -9,27 +9,6 @@ This family is present on repository main and in npm 4.1.0. Check the
 [released package boundary](installation.md#released-package-and-main) and the
 connected server's tool list before selecting it.

-## Optional package delivery
-
-The MCP `inspect_android_package` request keeps complete output when `detail` is
-omitted or `"complete"`. Select `detail: "summary"` explicitly to receive all
-package, SDK and permission declarations, engine identity and class/resource
-counts without decoded manifest text or duplicate raw provider replies. A
-retaining session keeps the complete original Evidence and returns a distinct
-linked `inspect_analysis_view` summary. This changes delivery, not JADX analysis.
-
-Use the returned `normalized_result.parent_evidence_id` with
-`inspect_analysis_view`, source kind `retained-evidence`, and
-`view: {kind: "android", facet: "manifest", offset: 0, limit: 4096}` to read the
-exact decoded manifest without reopening the APK. Offsets and limits count UTF-16
-code units; follow `coverage.next_offset`. The page preserves `source_status` and
-`reported_total_bytes`: exhausting retained text does not make a partial decoded
-manifest complete. Complete source Evidence remains exportable under the existing
-session lifetime. Servers without retention reject summary before starting JADX.
-One-shot CLI output remains complete. Older servers require the existing complete
-request after schema discovery. APK authenticity and runtime behavior remain
-unverified.
-
 ## Supply tools

 Use a **full JDK 17 or newer** (including its compiler module) and
@@ -174,7 +174,7 @@ Resolution follows dyld:
 - `@rpath` tries each `LC_RPATH` of the loading image first, then those of the
  image that loaded it, up to the process root.
 - Dependencies load dependents-first in load-command order, and each image
-  loads once per process. A later @rpath request whose install name matches an
+  loads once per process. A later request whose install name matches an
  already loaded image reuses it.
 - Symlinks such as `Versions/Current` are followed inside the analyzed root.
  An escape through `..` or an absolute link is `escapes-target`.
@@ -6,7 +6,7 @@ graph TD
    end

    subgraph "Production Composition"
-        COMPOSITION["src/composition/<br/>fresh typed provider and session factories<br/>one-shot binding and independent optional loading<br/>static WASM/EVM descriptors: named contracts, factories, retryable lifetimes"]
+        COMPOSITION["src/composition/<br/>fresh typed provider and session factories<br/>one-shot binding and independent optional loading<br/>static WASM descriptor: named contract, factory, retryable lifetime"]
    end

    subgraph "Adapters"
@@ -8,10 +8,6 @@ exported script's native imports under an explicit URL/import-map context.

 REA can attach to a user-owned Chrome-family browser through the Chrome DevTools Protocol (CDP) and produce bounded Evidence about an existing page. This is a passive reverse-engineering capability, not a general browser automation or remote-control surface.

-For request/response bodies and traffic debugging, see
-[Fiddler Everywhere captures and MCP](web-network-captures.md#reading-fiddler-captures-saz).
-Inspect native SAZ or HAR 1.2 offline with REA, or connect Everywhere's separate MCP server.
-
 ## Shipped surfaces

 - `list_browser_targets` / `rea list-browser-targets` discovers all eligible page targets at the endpoint by default, with an optional exact-origin filter.
@@ -312,9 +312,3 @@ artifacts carry their normalized before/after digests and capture states.
 Every changed or unknown artifact record is returned inline for each aligned
 step. Missing, truncated, or mismatched capture coverage remains unknown
 instead of being treated as equality.
-
-`scenario.event_families` records the sorted, de-duplicated `capture.events`
-selection. Captures with different selections report event evidence as unknown
-with a recovery instruction, even when no selected family emitted an event.
-Captures written before this field existed omit it, so their event evidence is
-also unknown.
@@ -62,14 +62,6 @@ 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
-
-For a local database snapshot, use `rea inspect-sqlite-database PATH --json`.
-Add `--table NAME --row-limit 20` to read a bounded sample from an ordinary
-table. This command does not require a native analysis provider. See
-[SQLite database snapshots](sqlite-databases.md) for database/WAL identity,
-source-file handling and row-value semantics.
-
 ## Native analysis

 Inspect embedded Go build metadata without installing Go or configuring a
@@ -215,9 +207,7 @@ rea import-reference-source /absolute/path/to/source
 ```

 The import records hashes and metadata for the supplied files, separately
-from observations of the current app. For a directory inside a Git checkout,
-it records the HEAD of the nearest enclosing repository; whether the working
-tree matches that commit remains unknown. It honors the source tree's `.gitignore`
+from observations of the current app. It honors the source tree's `.gitignore`
 and applies default exclusions for common generated and dependency paths such
 as `node_modules/`, `dist/`, and `*.log`. Pattern-based exclusions record the
 matched pattern and whether it came from project, default, caller, or sensitive
@@ -6,12 +6,6 @@ for the reviewed setup transaction and [client IDs](installation.md#supported-ag
 The versioned verification notes below describe their stated runs; live service
 acceptance is verified only where explicitly recorded.

-## Fiddler Everywhere alongside REA
-
-Connect Fiddler Everywhere's MCP server separately for HTTP traffic debugging,
-preserving your REA client entry. See the
-[setup instructions and public skills](web-network-captures.md#fiddler-everywhere-mcp-and-public-skills).
-
 ## GitHub Copilot CLI

 For GitHub Copilot CLI 1.0.95, `gpt-4.1` model metadata can block ordinary
@@ -101,11 +95,6 @@ Setup and doctor follow Qwen Code's tilde and working-directory-relative home
 overrides. Qwen Code also discovers personal skills in `~/.agents/skills`,
 where setup installs the bundled workflow.

-## Antigravity
-
-Antigravity 2.0 discovers personal skills in `~/.gemini/config/skills`.
-Setup installs its selected skill copy there.
-
 ## Gemini CLI

 Gemini CLI uses `$GEMINI_CLI_HOME/.gemini/settings.json` when that home override
@@ -156,15 +145,6 @@ REA follows `HERMES_HOME` whitespace trimming, environment-variable expansion,
 and home expansion before resolving that profile. Setup previews the resolved
 configuration and skill destinations; doctor and uninstall use those same paths.

-## Qoder CLI
-
-For [Qoder](https://docs.qoder.com/cli/mcp-reference), setup writes
-`mcpServers.rea` into the user-level `~/.qoder/settings.json` (the
-`QODER_CONFIG_DIR` override is honored). Entries carry `command`, `args`, and
-`env`; stdio is the default transport. Qoder CLI discovers personal skills
-from `~/.qoder/skills` (following `QODER_CONFIG_DIR` when set), so setup
-installs its skill copy there.
-
 ## Trae

 For [Trae](https://docs.trae.ai/ide/add-mcp-servers), setup writes
@@ -298,42 +298,13 @@ subsequent wire recovery and clean shutdown. Caller timeout does not interrupt
 Hopper's synchronous native operation. Socket boundary tests deterministically
 cover active and queued expiry, late replies and timer cleanup.

-The Linux demo lane remains a separate `verify:hopper:linux` command. Hopper
-6.4.2's ELF loader did not recognize the original 4,119-byte literal or three
-non-ASCII byte strings in the measured fixtures. The lane retains complete raw
-byte checks for those literals through source-owned symbols. Recognition of the
-original full-length literal is bound to its exact source address; its decoded
-object coverage remains explicitly unverified on Linux even when recognized.
-Absent non-ASCII recognition also reports decoded-object coverage as unverified.
-Recognized non-ASCII and control-text objects must still match their source
-bytes, encoding, filters and searches.
-A separate 548-byte ASCII literal requires native fragmentation, shortened
-provider display, complete decoded fragments and dossier provenance on Linux;
-the macOS lane retains the original full-length recognition requirement. These
-are observed fixture/build capabilities, not universal Hopper length limits.
-Its lifecycle checks attempt competing CLI launches for the active target and a
+The Linux demo lane remains a separate `verify:hopper:linux` command. Its
+lifecycle checks attempt competing CLI launches for the active target and a
 different target, requiring rejection before either can change the owning
 MCP session's documents or procedures. Lease boundary tests also preserve
 unresponsive or malformed live endpoints while allowing confirmed stale
 sockets to recover.

-`verify:setup:linux` exercises installation on a clean supported Linux runner as
-root. Use a disposable VM: this lane installs Hopper and its Linux runtime
-dependencies through the system package manager. Set `REA_VERIFY_SERVER_COMMAND`
-to the CLI entrypoint being verified. The command builds and checks source-owned
-ELF fixtures before testing the read-only Hopper setup plan, approved
-installation, scoped doctor, real CLI/MCP analysis, rejection of a modified
-launcher, idempotent setup without requesting a reinstall, and owned child
-cleanup. Before installation and after teardown, a clean-runner process scan
-also rejects surviving Hopper demo helpers or Xvfb groups, including orphans
-whose launcher exited. This scan observes processes without signaling them.
-Hopper detection compares executable file identity through `/proc`, covering
-alternate or configured launcher paths even after an invoked symlink is removed.
-The dedicated runner must have no unrelated Hopper/Xvfb sessions. It requires
-the repository's pinned development toolchain and an
-existing host C compiler, `file`, `nm`, and `strings`. Use `verify:hopper:linux`
-instead when Hopper is already installed.
-
 `verify:hopper:fat` is a separate macOS lane requiring installed Hopper and the
 existing Xcode clang/lipo toolchain. It compiles arm64/x86-64 thin executables and
 one- and two-slice FAT32 containers, verifies exact/interior address mappings
@@ -35,7 +35,7 @@ license](https://github.com/morluto/rea/blob/main/third_party/evmole/README.md)
  and whitespace. Decoded-byte SHA-256 identifies actual selected EVM bytes.
  Neither digest is the Ethereum Keccak code hash.
 - Full bytecode, upstream function offsets and original producer representation
-  are returned inline by default. Offsets are byte positions in decoded bytecode.
+  are returned inline. Offsets are byte positions in decoded bytecode.
 - Upstream also returns terminal metadata during selector recovery. Its reported
  values remain in `raw_result`; integer precision and non-text-key coverage are
  unknown in the JS binding. Full bytecode retains the original encoded metadata.
@@ -47,49 +47,6 @@ license](https://github.com/morluto/rea/blob/main/third_party/evmole/README.md)
 - Analysis is offline: no target runtime execution, implicit chain/RPC/explorer
  lookup, wallet action, transaction broadcast or network request.

-## Selected interface delivery and retained views
-
-Existing CLI calls and MCP calls with omitted or `complete` detail keep the
-complete inline result. On a retaining MCP server, select `detail: "summary"`
-when the question needs every inferred function and its identity/uncertainty,
-without bytecode text or duplicated raw stdout:
-
-```json
-{
-  "name": "inspect_evm_interface",
-  "arguments": {
-    "path": "/artifacts/runtime.hex",
-    "encoding": "hex",
-    "detail": "summary"
-  }
-}
-```
-
-The result is distinct derived Evidence linked to its complete parent. Its
-`normalized_result.summary` preserves every producer-returned selector, decoded
-byte offset, dispatch, argument/mutability string including null, carrier/decoded
-identities, original limitations and explicit unknowns. Payload `evidence_kind`
-remains `inferred`. It preserves stderr/truncation and records stdout text length.
-Complete-within-view coverage covers returned candidates; discovery completeness
-remains unknown even for an empty or exhausted collection. Analysis still runs;
-delivery selection does not save interpreter work or change source parameters.
-
-Use `normalized_result.parent_evidence_id` with `inspect_analysis_view` source
-kind `retained-evidence`. EVM view kind `evm` pages `functions` by original row
-order, or `bytecode_hex`, `stdout`, `stderr` by UTF-16 code units. Hex pages preserve
-the original lowercase text without a prefix; two characters represent one decoded
-byte. A text-page offset differs from a function's decoded-byte offset. Complete
-parent Evidence remains accessible through the normal ledger/export workflow;
-reading views does not rerun analysis or change its identity. Existing record
-retention and close semantics are unchanged.
-
-Portable historical complete EVM Evidence can use source kind `inline` without
-a provider. A fixed server without Evidence retention rejects selected summary
-delivery before starting analysis and continues to support complete delivery.
-Discover the actual advertised schema before sending `detail` to an older server;
-use its complete operation when an equivalent workflow is required. The one-shot
-CLI keeps its existing complete result.
-
 ## Resource and lifecycle limits

 Inputs are limited to 4 MiB, complete replies to 16 MiB and combined diagnostic
@@ -123,10 +123,8 @@ Select a verified native child for the existing tools:
 ```

 Then use `analyze_function`, `inspect_native_api` or the other native primitives.
-Native architecture and executable validation still apply. Generic
-[MIPS ELF](ghidra-mips.md) and [RISC-V ELF](ghidra-riscv.md) lanes are separate
-documents with their own admission boundaries. This milestone does
-not add PPC decompilation, raw flash load profiles, bootloader/device
+Native architecture and executable validation still apply. This milestone does
+not add MIPS/PPC/RISC-V decompilation, raw flash load profiles, bootloader/device
 tree semantics, vulnerability scanning, emulation or hardware runtime capture.

 ## Resource and lifecycle policy
@@ -25,26 +25,6 @@ The equivalent MCP methods are `identify_flutter_build` (with `path`) and
 arm64-v8a, then x86_64, then x86, then armeabi-v7a, then the remaining
 ABIs alphabetically).

-## Optional retained AOT delivery
-
-MCP `inspect_dart_aot` keeps complete output when `detail` is omitted or
-`"complete"`. Explicit `detail: "summary"` returns the selected target/ABI/library
-identity, all snapshot headers, structural coverage, string-pool coverage and
-original lower-bound counts without the string lists. It retains complete source
-Evidence and returns a distinct linked `inspect_analysis_view` summary. Analysis
-and the caller's ABI choice are unchanged; one-shot CLI output stays complete.
-
-Use `normalized_result.parent_evidence_id` as the retained source for
-`inspect_analysis_view`, with `view: {kind: "dart-aot", collection: "package_uris",
-offset: 0, limit: 64}`. Collections are `package_uris`, `dart_uris` and
-`class_like_tokens`. Pages preserve the original strings and order, selected ABI,
-library identity and source coverage. `returned_counts` describe producer-returned
-rows; counts ending in `_at_least` remain lower bounds. Exhausting a page sequence
-does not make a partial pool complete or turn byte-pattern tokens into typed
-classes/functions. Views do not reopen the APK. Original Evidence remains
-exportable under its existing session lifetime. Summary requires a retaining
-server; older servers keep the complete request after schema discovery.
-
 ## What the AOT inspection returns

 `inspect_dart_aot` reads one ABI's `libapp.so` in full and reports:
@@ -41,80 +41,6 @@ does not prove text is absent. Both list and search Evidence carry this
 limitation. When an address is known, use `read_bytes` and `xrefs` to inspect
 bytes and references.

-## Loaded addresses and file offsets
-
-`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
-report a base, or whose segments disagree, omits the overview field, following
-the existing contract on main. REA does not substitute zero or the first
-segment's address. All reported bases and address spaces remain visible in the
-complete segment inventory, including conflicting observations.
-
-`function` and most MCP procedure selectors use procedure names or
-provider analysis addresses. Ghidra `decompile` / MCP `procedure_pseudo_code`
-also accept source-file byte offsets. Existing symbols and analysis addresses
-take precedence; a `0x`-prefixed number that resolves to no procedure falls back
-to its observed source mapping. Use `--file-offset=0x...` on the CLI or
-`procedure: "file-offset:0x..."` through MCP to select file coordinates explicitly.
-Multiple mapping candidates fail as ambiguous rather than selecting a bank or
-address space. A successful conversion retains the file offset, mapped address
-and procedure entry in raw Evidence and `locations`.
-
-If an offset maps to loaded target bytes but no procedure starts at or contains
-the mapped address, the failure preserves both the original file offset and
-analysis address. This differs from an unmapped offset and does not recommend
-retrying the same offset syntax.
-If the function resolves but the backend fails or cancels decompilation, the
-failure retains the selector, mapped address and procedure entry without
-changing the backend failure code.
-
-Both mapping directions require a complete original `FileBytes` source whose
-SHA-256 matches the admitted target. Auxiliary files and partial source objects
-remain visible in the load-image inventory but do not establish offsets in the
-original target. Ghidra's object-local offsets are not silently treated as
-original-file coordinates. Original-source identity is checked once per source
-object per session; analysis-memory edits do not change the original bytes.
-
-ELF virtual addresses and file offsets are
-different coordinates. Ghidra can rebase a PIE ELF during import: in the
-source-owned verification fixture, ELF entry `0x1013` becomes Ghidra procedure
-`0x101013` with image base `0x100000`. That example is not a general conversion
-rule.
-
-Use `list_procedures` to select an observed procedure address. To relate file
-bytes to loaded memory, call MCP `inspect_native_load_image` or:
-
-```sh
-rea search <path> . --kind procedures --mode regex --provider ghidra --json
-rea inspect-native-load-image <path> --provider ghidra --json
-rea decompile <path> <observed-procedure-address> --provider ghidra --json
-rea decompile <path> --file-offset=0x1013 --provider ghidra --json
-rea address-to-file-offset <path> <observed-procedure-address> --provider ghidra --json
-```
-
-The load-image result preserves source-file indexes, file offsets, address
-spaces, and inclusive mapping ranges. Follow the mapping for the selected
-source file and region; adding `image_base` to an arbitrary file offset is not
-valid. For a linear byte-addressed, file-backed mapping, a file offset `F` in
-`[mapping.file_offset, mapping.file_offset + mapping.length)` maps to
-`mapping.start + (F - mapping.file_offset)` in the reported `address_space`.
-If several mappings cover the same file offset, keep those candidates distinct
-and select the procedure from the observed inventory. Uninitialized regions may
-have no file backing. ELF mappings are observed
-without independent format-specific load-image verification, as the result's
-status and limitations state.
-
-An unsuccessful numeric procedure lookup reports the current Ghidra image base
-and gives the CLI commands above alongside the corresponding MCP operations.
-Repeat any target-format, architecture, and entry-point options used to open the
-target. Other procedure operations keep their analysis-address semantics;
-file-offset fallback applies only to decompilation.
-
-Overview workflow revision 3 binds this output to snapshot identity. Older
-serialized overview Evidence remains readable; it is not replayed as a current
-overview merely because its source artifact is unchanged.
-
 ## Admitted function-analysis semantics

 | Concern                 | Ghidra contract                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
@@ -1,105 +0,0 @@
-# RISC-V ELF analysis through Ghidra
-
-This lane extends native ELF analysis for `EM_RISCV` targets. It does not
-execute RISC-V code, emulate a boot sequence, or rehost firmware. It addresses
-[#2063](https://github.com/morluto/rea/issues/2063) and follows the same
-lane shape as [generic MIPS support](ghidra-mips.md).
-
-## Admission boundary
-
-ELF `EM_RISCV` (243) is retained as the provider-neutral `riscv` family. The
-target also retains the raw ELF declarations that decide a lane: class, byte
-order, `e_type`, and `e_flags`. Recognition does not mean every provider or
-RISC-V variant is supported. Existing PE, managed and Mach-O architecture sets
-are unchanged, and caller-supplied headerless raw-binary entry still accepts only
-its existing four families.
-
-The Ghidra lane admits little-endian ELF32 and ELF64 `ET_EXEC` images that
-declare `EF_RISCV_FLOAT_ABI_DOUBLE` in `e_flags`, with no `EF_RISCV_RVE`,
-`EF_RISCV_TSO`, or any bit outside `EF_RISCV_RVC | EF_RISCV_FLOAT_ABI`. These are
-header declarations, not proof that every instruction conforms to that ISA.
-
-Provider selection returns the specific unsupported constraint rather than
-guessing a compatible profile:
-
-| Declaration                                     | Outcome                                                                                  |
-| ----------------------------------------------- | ---------------------------------------------------------------------------------------- |
-| Little-endian ELF64 `ET_EXEC`, double-float ABI | admitted, `RISCV:LE:64:default` + `gcc`                                                  |
-| Little-endian ELF32 `ET_EXEC`, double-float ABI | admitted, `RISCV:LE:32:default` + `gcc`                                                  |
-| Big-endian                                      | refused; Ghidra 12.1.4 ships no big-endian RISC-V language                               |
-| `ET_REL`, `ET_DYN`, other `e_type`              | refused with the declared value                                                          |
-| `EF_RISCV_RVE`                                  | refused; the embedded 16-register profile (x0–x15) needs its own processor specification |
-| `EF_RISCV_TSO`                                  | refused; the total-store-order memory model is unverified here                           |
-| Soft, single, or quad float ABI                 | refused; the pinned generic compiler specification models double-float                   |
-| Reserved or newer `e_flags` bits                | refused with the offending bits named                                                    |
-
-`e_type` is the only load-shape declaration this lane reads. A fixed-address
-`ET_EXEC` declaration does **not** establish static linkage: `PT_INTERP` and
-dynamic dependencies are not inspected, and the session records that boundary as
-a limitation rather than inferring a load model.
-
-## Why the language is pinned
-
-Ghidra's header-based selection is not reliable for RV32. The 12.1.4
-`riscv.opinion` pins `variant="default"` for the 64-bit constraint and leaves the
-32-bit constraint unpinned with the comment that the loader "must choose between
-'default' and 'AndeStar' variants". Measured against the installed release tree:
-
-| Fixture                                         | Ghidra auto-selection         |
-| ----------------------------------------------- | ----------------------------- |
-| RV64 ELF, `e_flags 0x5` (RVC, double-float ABI) | `RISCV:LE:64:default:gcc`     |
-| RV32 ELF, `e_flags 0x5`, no Andes declaration   | `RISCV:LE:32:AndeStar_v5:gcc` |
-
-So an ordinary RV32 image lands on an Andes processor model unless the language
-is stated. REA therefore pins `RISCV:LE:32:default` or `RISCV:LE:64:default`
-with the `gcc` compiler specification per class, records
-`language_selection: provider-pinned-v1`, and refuses a caller-selected
-`REA_GHIDRA_LANGUAGE_ID` or `REA_GHIDRA_COMPILER_SPEC_ID` that disagrees with the
-pin without changing the requested override. An override that matches the pin is
-accepted and recorded as `configured-v1`.
-
-## Evidence
-
-The lane identity is `elf32-exec-le-double-float-generic-v1` or
-`elf64-exec-le-double-float-generic-v1`, and `riscv_elf` retains `elf_class`,
-`byte_order`, `type`, and the raw `flags` alongside the read-only booleans
-`float_abi_double`, `rvc_declared`, `rve_declared`, and `tso_declared`. Those
-fields report declarations the header makes; none of them is evidence of the
-original compiler, of instruction conformance, or of a floating-point calling
-convention beyond the ABI the pinned language models.
-
-## Verification and limits
-
-Ghidra 12.1.4 PUBLIC with a 64-bit JDK 21+ is required, and on macOS the release
-tree ships no host decompiler binary, so `Decompiler/os/<platform>/decompile` and
-`sleigh` must come from your own build; see
-[installation](installation.md#ghidra).
-
-Run `npm run verify:ghidra:riscv` with an existing Ghidra 12.1.4 installation,
-JDK 21+, and a RISC-V-capable Clang, LLD and LLVM readelf. The verifier acquires
-no tools and never executes target code. Select installed tools explicitly when
-they are not on `PATH`:
-
-```sh
-GHIDRA_INSTALL_DIR=/path/to/ghidra_12.1.4_PUBLIC \
-JAVA_HOME=/path/to/jdk-21 \
-REA_RISCV_CLANG=/path/to/llvm/bin/clang \
-REA_RISCV_LLD=/path/to/lld/bin/ld.lld \
-REA_RISCV_READELF=/path/to/llvm/bin/llvm-readelf \
-npm run verify:ghidra:riscv
-```
-
-The lane builds the committed freestanding C and assembly sources into RV32 and
-RV64 `ET_EXEC` fixtures. Independent LLVM readelf observations establish ELF
-declarations and symbol addresses. Public CLI and stdio MCP workflows verify
-function enumeration, decompilation, pinned language/compiler identity, decoded
-probe bytes, global data, and direct calls. It validates advertised MCP output
-schemas and both JSON representations, saves and reopens snapshots, rejects
-header-mutated soft-float and unsupported high-bit declarations, and checks
-unchanged source bytes and owned cleanup. Failures retain the diagnostic
-workspace; successful runs remove it and report the observed process lineage.
-
-Module tests cover admission and malformed headers. Call-graph completeness,
-string inventories, dynamic linkage, Andes or RVE/TSO images, and big-endian
-targets are **not** established by this lane. `.riscv.attributes` ISA extensions
-are not inspected; the generic language pin remains an analysis convention.
@@ -1,6 +1,6 @@
-# IDA provider
+# IDA Pro provider

-REA adapts an existing IDA MCP server into its native analysis tools. Existing IDA Pro profiles use [mrexodia/ida-pro-mcp](https://github.com/mrexodia/ida-pro-mcp); an optional native bridge for IDA Pro and IDA Free is described below. Install and configure your selected engine and upstream MCP using their instructions. REA does not install, upgrade, activate, or license them, and does not bundle another IDA server.
+REA adapts an existing [mrexodia/ida-pro-mcp](https://github.com/mrexodia/ida-pro-mcp) server into its native analysis tools. Install and configure IDA, Hex-Rays, Python, and upstream MCP using that repository's instructions. REA does not install, upgrade, activate, or license them, and does not bundle another IDA server.

 Choose one lifecycle mode in an upstream MCP JSON registration. Set `REA_IDA_MCP_CONFIG` to that file, then select `ida` once through `REA_ANALYSIS_PROVIDER`, the CLI's `--provider ida`, or MCP's `open_binary.provider_id`. No provider startup occurs during discovery.

@@ -32,33 +32,7 @@ Open the **original input binary** in REA, not an `.idb` or `.i64` database. Its

 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.

-## Optional native IDA MCP bridge
-
-IDA Pro and IDA Free can use the separate [ida-free-mcp native plugin](https://github.com/0xshlomil/ida-free-mcp) through an explicit attached registration. Install and start that plugin using its upstream instructions, open the original binary in the IDA GUI, and wait for analysis. The native MCP 1.1.2 release binds `0.0.0.0` without a listen-address setting. Restrict inbound access with the host firewall or use an upstream build that binds only to loopback before starting it. REA's loopback URL restriction does not change the plugin's listener. REA does not install IDA, build the plugin, activate a license, or launch the GUI.
-
-```json
-{
-  "mode": "attached",
-  "protocol": "native",
-  "url": "http://127.0.0.1:13337/mcp"
-}
-```
-
-Set `REA_IDA_MCP_CONFIG` to this file and select `ida` using the same CLI/MCP commands above. Omitting `protocol` preserves existing IDA Pro registrations. Native mode requires `resources/read` for `ida://idb/metadata` and its recorded input SHA-256; it never substitutes a digest of an unrelated local file. The native resource's `path` describes the IDB in the upstream protocol, not the original input path. REA retains it and checks database identity and image base before and after requests.
-
-This experimental profile provides function/string inventory and search, function lookup, assembly, GUI pseudocode, callees, address xrefs, instruction windows, and function dossiers. Direct callers remain unavailable: native code/data xref labels do not prove call edges. It requires neither IDAPython nor idalib. Native headless registrations are rejected.
-
-Native string observations use upstream C-string rendering; other representations remain unknown. Literal searches request conservative candidates and apply REA's original case and Unicode matching rules. Regex searches retain the full scan because native byte-oriented regex semantics cannot replace REA's Unicode regex semantics. All candidate pages are examined, and upstream search errors remain failures.
-
-Native callee resolution batches unique queries and checks each reply's query identity. Results remain live: a recorded input hash does not establish database revision, so cross-request analysis caches cannot prove freshness. For focused questions, use pseudocode, callees, or instruction-window tools; a function dossier requests additional facets and returns more Evidence.
-
-IDA Free's cloud decompiler needs network access and may request consent. Follow its licensing and supported architecture limits; see [IDA Free](https://hex-rays.com/ida-free). Decompilation moves GUI focus and the upstream plugin closes existing pseudocode tabs before requesting fresh output. REA advertises UI/network effects and closes only its MCP connection, preserving the open database. Rendered pseudocode has upstream traversal limits and does not prove complete source recovery. Cloud/widget failures remain explicit failures; retry after the GUI finishes or dismiss its prompt.
-
-Native MCP 1.1.2 can navigate in the previously focused pseudocode tab when switching functions. Use upstream 1.1.3 or a source build including [the navigation correction](https://github.com/0xshlomil/ida-free-mcp/commit/6adf2c615a2a03661059673e9c136ef28d0dc778), which focuses the disassembly view **before** jumping to the requested entry. This REA profile does not repair stale GUI output. Verification must include two different functions before claiming reliable function switching. The initial Linux verification used a locally corrected 1.1.2 plugin; upstream 1.1.3 has not been verified by that run.
-
-Native tool observations retain actual tool names and complete JSON text. Upstream `structuredContent` can be a shortened preview even while text contains the full result. REA reads the full native representation and rejects missing/malformed text instead of treating previews as complete observations.
-
-The legacy producer moves the active GUI as a side effect: assembly and raw function instructions jump to the function, and successful pseudocode opens or reuses a pseudocode view. A function dossier does both. Native GUI decompilation also changes the active view. `binary_session` reports these operations with `effects.may_show_ui: true`; headless operations and the other attached operations report `false`.
+The legacy producer moves the active GUI as a side effect: assembly and raw function instructions jump to the function, and successful pseudocode opens or reuses a pseudocode view. A function dossier does both. `binary_session` reports these operations with `effects.may_show_ui: true` in attached mode; headless operations and the other attached operations report `false`.

 ## Give REA a target for headless analysis

@@ -124,9 +98,9 @@ For guided registration, set `REA_IDA_MCP_CONFIG` before `rea setup --client <cl

 ## Coverage and evidence

-All profiles support procedure/string inventory and literal or regex search, procedure resolution, pseudocode, assembly, raw function instructions, resolved callees, incoming address references, and a function dossier. Inventories and modern pseudocode/assembly follow upstream pagination. Upstream limits on modern xrefs and callees are retained as explicit truncation limitations. In the modern headless profile, targets that are not proven x86-only use processor-neutral `callgraph` edges instead of the x86 instruction checks in upstream `callees` (mrexodia/ida-pro-mcp#549). REA requests depth zero: the pinned upstream emits the root's outgoing edges without scanning child functions, then REA batches function-name lookup for those addresses. The graph covers recognized function destinations only; imports and other non-function targets remain unknown. A server without `callgraph` returns an empty relationship list with an explicit coverage limitation. Graph and path workflows retain those limitations alongside observed edges. A failed or inconsistent graph reply remains an error. A transport-level truncated preview is rejected rather than reported as complete evidence; the error preserves upstream retrieval guidance.
+Both profiles support procedure/string inventory and literal or regex search, procedure resolution, pseudocode, assembly, raw function instructions, resolved callees, incoming address references, and a function dossier. Inventories and modern pseudocode/assembly follow upstream pagination. Upstream limits on modern xrefs and callees are retained as explicit truncation limitations. In the modern headless profile, targets that are not proven x86-only use processor-neutral `callgraph` edges instead of the x86 instruction checks in upstream `callees` (mrexodia/ida-pro-mcp#549). REA requests depth zero: the pinned upstream emits the root's outgoing edges without scanning child functions, then REA batches function-name lookup for those addresses. The graph covers recognized function destinations only; imports and other non-function targets remain unknown. A server without `callgraph` returns an empty relationship list with an explicit coverage limitation. Graph and path workflows retain those limitations alongside observed edges. A failed or inconsistent graph reply remains an error. A transport-level truncated preview is rejected rather than reported as complete evidence; the error preserves upstream retrieval guidance.

-The legacy profile additionally supports direct callers. Its producer may report call-site or interior addresses; REA resolves the reported function symbol to its canonical entry. The modern and native profiles do not prove direct callers from its code/data xref labels, so that capability is unavailable and the dossier marks it unknown.
+The legacy profile additionally supports direct callers. Its producer may report call-site or interior addresses; REA resolves the reported function symbol to its canonical entry. The modern profile does not prove direct callers from its code/data xref labels, so that capability is unavailable and the dossier marks it unknown.

 Complete body ranges, typed reference edges, CFG, referenced data, source locals, comment kinds, and database revision are unavailable. Empty unsupported dossier facets mean **unknown**, not observed absence. `binary_overview`, whole-symbol inventory, mutation, debugging, arbitrary Python forwarding, and requested GUI navigation are outside this adapter's coverage. Check session availability before composing a workflow that needs those facets.

@@ -136,10 +110,4 @@ Complete body ranges, typed reference edges, CFG, referenced data, source locals

 Run `npm run verify:ida -- --target /absolute/path/to/program --procedure main` with a configured upstream server. It exercises production CLI and MCP tools, validates their output contracts and Evidence, checks original-input preservation and session cleanup, and keeps local target data out of its console summary. Supply `--package-root` to verify an extracted or installed package. See [testing](testing.md) for the distinction between adapter tests and real-provider evidence.

-Native verification requires `--second-procedure other_function --second-marker unique_second_body_text`; these options remain optional for the other profiles. The marker must occur in the second function's pseudocode and be absent from the first; the verifier also checks that returning to the first restores its text.
-
-The verifier requires the resolved procedure in both inventory and procedure search, then compares address, assembly, pseudocode, instruction windows and relationship results with the CLI/MCP dossier. Supply `--expected-string known_literal` to check a known positive string inventory/search result and `--expected-xref 0xSOURCE` to check a known reference source address. Choose those oracles independently from the operation under test. Without them, string and xref correctness are listed in `unverified`; valid output shapes alone do not establish those behaviors. Callee parity does not independently establish semantic completeness. Native callee successes must report an explicit truncation marker; missing markers remain protocol failures.
-
 The initial real workflows use stdio registrations for the legacy Windows GUI profile and a Windows x64 headless supervisor with IDA 9.3. The headless workflow has also passed on macOS arm64 with IDA Professional 9.1 (build 9.1.250226) against the same upstream commit `c133c3853faa111a9b00ee615c013b720d0c4acd`, using a source-built arm64 Mach-O fixture; Mach-O C symbols carry a leading underscore, so the procedure name is `_rea_fixture_add`. Streamable HTTP is tested against a loopback MCP fixture with the pinned client SDK; a real IDA HTTP-supervisor workflow remains unverified. Linux headless engine operation, other IDA releases, architectures, and modern attached GUI tools require their corresponding real workflows before support is claimed.
-
-Native Windows verification uses IDA Pro 9.3 with the public two-function fixture and Windows `whoami.exe`, using upstream `c9d15d98e8a143fc74f6e14037c48f63889b6d6c` with a loopback-listener change. It covers production CLI/MCP parity, distinct-function switching, identity and connection cleanup. See the [correctness and performance measurements](https://github.com/morluto/rea/blob/main/experiments/analysis-efficiency/ida-native-windows.md). This follow-up did not run Windows IDA Free or native macOS.
@@ -57,10 +57,6 @@ Hopper installation or any file write. Declining or pressing Ctrl-C makes no
 changes. Agent configuration writes preserve unrelated entries and comments,
 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` and `REA_MCP_MAX_RESPONSE_BYTES`.
 Detected provider settings replace only matching environment keys.
@@ -105,11 +101,13 @@ rea setup --yes --all-detected --install-hopper --json

 ### Skill destinations

-The bundled skill is installed in each selected client's personal skill directory.
-See [client configuration](client-configuration.md) for client-specific roots,
-profiles, and environment overrides. A mixed selection plans each distinct
-destination. Selecting the skill without a client uses `~/.agents/skills`.
-Setup leaves existing skill copies in other locations untouched.
+The bundled skill is installed where each selected client discovers personal
+skills: Claude Code uses `~/.claude/skills` (or
+`$CLAUDE_CONFIG_DIR/skills` when configured). Gemini CLI uses `.agents/skills`
+under its selected home; Antigravity 2.0 uses `~/.gemini/config/skills`.
+Other integrations, including Qwen Code, use `~/.agents/skills`.
+A mixed selection plans each distinct destination. Selecting the skill without a client uses the shared
+directory. Setup leaves existing skill copies in other locations untouched.

 `rea setup --skill-client claude_code --yes --json` refreshes and verifies the
 selected skill destination independently of MCP registration selection. The
@@ -282,7 +280,6 @@ hosted connector; see [its configuration](client-configuration.md#other-client-s
 | OMP                | `omp`            |
 | Pi                 | `pi`             |
 | Hermes             | `hermes`         |
-| Qoder              | `qoder`          |
 | Trae               | `trae`           |
 | ZCode              | `zcode`          |
 | DeepSeek Harness   | `dsh`            |
@@ -321,8 +318,8 @@ The Hopper launcher action used by REA creates a document from an executable;
 its supported command-line interface does not attach to an already-open
 document. While another live REA session owns the same target and loader
 profile, a second session reports the owning run ID instead of opening a
-duplicate document. On macOS, closing the owning REA session releases this guard;
-Hopper keeps its document open. A later REA session can therefore open another
+duplicate document. Closing the owning REA session releases this guard; Hopper
+keeps its document open. A later REA session can therefore open another
 document for the same target. REA does not currently identify, focus, or reuse
 that existing GUI document, and the supported launcher exposes no attach or
 reuse action for it.
@@ -345,14 +342,8 @@ Hopper application per user across cooperating REA processes. A competing
 CLI or MCP session receives the owning session ID before Hopper is launched,
 for both the same target and a different target. Switch targets through that
 MCP session, or close it before starting another session. Closing the owner
-releases the reservation and stops REA's owned demo application and private
-display; the headless Linux demo does not retain documents after MCP shutdown.
-Its helper watches a private lifetime pipe, so an owner crash or SIGKILL also
-stops those children, without relying on a reusable PID or a process-name scan.
-A later session recovers the dead owner's stale lease after child cleanup;
-private runtime files can remain when REA itself was killed. This does not attach to
-or claim ownership of manually opened Hopper applications. An application left
-running by an older REA version must still be closed before starting a new session.
+releases the reservation. This does not attach to or claim ownership of
+manually opened Hopper applications.

 Stale lease recovery is serialized. If an interrupted recovery leaves its
 reservation directory, the diagnostic identifies that exact path. Stop REA
@@ -445,9 +436,8 @@ For cursor navigation, string decoding, symbol-name limits, and regex matching,
 see [Hopper analysis behavior](native-investigation.md#hopper-analysis-behavior).

 Closing or switching a target closes its bound Hopper document, shuts down REA's
-bridge and removes its temporary socket directory. The macOS Hopper application
-and unrelated documents remain open; the owned Linux demo application stops.
-A `cleanup_incomplete`
+bridge and removes its temporary socket directory while preserving the Hopper
+application and unrelated documents. A `cleanup_incomplete`
 result identifies resources whose cleanup could not be verified.
 REA retains unresolved cleanup ownership and any confirmed shutdown phases.
 After addressing the reported failure, retry `close_binary` on the same
@@ -614,39 +604,12 @@ rea doctor --json
 The copy step requires the destination to be absent and preserves an existing
 decompiler. This recipe is specific to macOS x64: the
 [Ghidra 12.1.4 Makefile](https://github.com/NationalSecurityAgency/ghidra/blob/Ghidra_12.1.4_build/Ghidra/Features/Decompiler/src/decompile/cpp/Makefile)
-explicitly selects `-arch x86_64` on Darwin. For a Gradle
+explicitly selects `-arch x86_64` on Darwin. For other architectures or a Gradle
 build, follow the matching release's
 [native component instructions](https://github.com/NationalSecurityAgency/ghidra/blob/Ghidra_12.1.4_build/GhidraDocs/GettingStarted.md#building-native-components).
 REA accepts the matching executable under either `os/<platform>/` or
 `build/os/<platform>/`; it does not build the component during setup or diagnosis.

-### macOS arm64 native decompiler
-
-On Apple Silicon the same source build works with explicit overrides; no
-Makefile edits and no Rosetta are needed. The Darwin block in the
-[Ghidra 12.1.4 Makefile](https://github.com/NationalSecurityAgency/ghidra/blob/Ghidra_12.1.4_build/Ghidra/Features/Decompiler/src/decompile/cpp/Makefile)
-pins `-arch x86_64`, but `ARCH_TYPE` and `OSDIR` are ordinary make variables,
-and command-line assignments replace them for every compile and link rule:
-
-```bash
-cd "$GHIDRA_INSTALL_DIR/Ghidra/Features/Decompiler/src/decompile/cpp"
-make ghidra_opt ARCH_TYPE="-arch arm64" OSDIR=mac_arm_64
-decompiler_dir="$GHIDRA_INSTALL_DIR/Ghidra/Features/Decompiler/os/mac_arm_64"
-mkdir -p "$decompiler_dir"
-test ! -e "$decompiler_dir/decompile" && test ! -L "$decompiler_dir/decompile" &&
-  install -m 755 ghidra_opt "$decompiler_dir/decompile"
-rea doctor --json
-```
-
-Verified end to end on macOS 15.6 arm64 with Apple clang 17 and the stock
-bison 2.3, against Ghidra 12.1.4: the build produces a Mach-O arm64
-`ghidra_opt`, the doctor check `ghidra-native_decompiler` turns healthy with
-"reports mach-o arm64, which matches darwin/arm64", and `rea decompile` on an
-arm64 Mach-O returns decompiled C through the headless provider. The JDK is
-not needed for the make step, only for the Ghidra provider. If your toolchain
-rejects the inherited `-mmacosx-version-min=10.6` flag, retry the make with
-`ADDITIONAL_FLAGS="-w"`.
-
 ### Ghidra import language and analysis seeds

 Ghidra detects the language from the executable header. To set it (for example, Borland C++ PE images):
@@ -104,15 +104,6 @@ static inferences. Dynamic or ambiguous IPC is retained without a pairing edge.
 Runtime entities retain passive-CDP authority, while a successful static/runtime
 correspondence is a separately identified cross-layer inference.

-Source module links retain their resolution mode. Static imports in `.ts` and
-`.tsx` are `compiler-dependent` when compiler options have not been retained.
-REA compares Node import and require resolution: a shared outcome remains
-available with a limitation; divergent outcomes remain unavailable with both
-conditional branches and their limitations. This models source relationships,
-not verified emitted code or execution. A declaration file found only through
-an emitted-extension fallback is retained as a candidate, not a runtime target;
-an explicitly selected path keeps its original identity.
-
 ## Evidence and authority

 Every observation and edge carries all of the following:
@@ -23,14 +23,6 @@ artifact digest and structural graph ID. Semantic tracing requires the semantic
 relation graph and reports when it is unavailable rather than treating missing
 data as an empty graph.

-Explicit TypeScript `import type` and `export type` declarations remain source
-facts and do not create runtime import or export relationships. Type export names
-are reported separately from value export names. Inline `type` specifiers can
-leave an empty import or re-export with side effects under
-[`verbatimModuleSyntax`](https://www.typescriptlang.org/tsconfig/verbatimModuleSyntax.html);
-REA retains those dependency candidates and reports the unavailable compiler
-options rather than assuming the dependency is erased.
-
 The semantic graph wire format stores shared non-location provenance once in
 its required `evidence_contexts` table. Each node, relation, fingerprint, and
 unknown retains its exact `evidence.location` and names the owning context with
@@ -164,12 +156,9 @@ to the comparison Evidence in a live session.
 `compare_source_to_bundle` compares one cryptographically committed
 `HistoricalSourceGraph` with authenticated application-graph Evidence. The
 stable scoring model reports every admitted signal and weight: exact source
-digest, source-map original path, exact current path, path suffix, Unicode-
-equivalent path, basename, and language extension. Exact digest wins over
-location inference; weak basename, extension, and Unicode-equivalence evidence
-never forces a mapping. Unicode-equivalent spellings are candidate evidence
-only because distinct filesystem paths can preserve those spellings as separate
-files; multiple canonical-equivalent candidates remain unknown.
+digest, source-map original path, exact current path, path suffix, basename, and
+language extension. Exact digest wins over location inference; weak basename
+or extension evidence never forces a mapping.

 Each historical source file is classified as `unchanged`, `modified`,
 `removed`, `split`, `merged`, `duplicated`, or `unknown`. Multiple equally
@@ -352,14 +352,10 @@ creation. Arguments follow each actual callable invocation rather than property
 chain depth; rebinding retains the original bound receiver.
 Visibly replaced invocation intrinsics produce unknown effects instead
 of using their former call semantics; captured function aliases retain their
-earlier identity. Invocation member reads are checked separately from the earlier
-function capture. Comma-expression callees use their final value while all
-preceding expressions remain in the effect traversal. Call effects are
-classified after callee and argument effects have been collected. Unexamined
-targets remain unresolved. `Reflect.set` examines its explicit receiver as well
-as its target, retaining unknown receiver effects. Creating an unused binding
-does not itself mutate an intrinsic. Variable redeclarations retain a single
-unconditional initializer
+earlier identity. Unexamined targets remain unresolved. `Reflect.set` examines
+its explicit receiver as well as its target, retaining unknown receiver effects.
+Creating an unused binding does not itself mutate an intrinsic. Variable
+redeclarations retain a single unconditional initializer
 when they introduce no assignment or second initializer.
 Stable identifier chains to fresh object, array, function,
 undecorated class or RegExp syntax keep those targets separate from intrinsic
@@ -1,31 +1,28 @@
 # JavaScript static/runtime reconciliation

 REA can combine an existing static JavaScript Application Graph with one or
-more browser, Electron, or Node/Electron V8 Inspector observations while
-preserving their different authorities. The `reconcile_javascript_runtime` MCP tool and
+more passive browser, Electron page, or Node/Electron V8 Inspector captures without collapsing their different
+authorities. The `reconcile_javascript_runtime` MCP tool and
 `rea reconcile-javascript-runtime` CLI command accept Evidence records and
 return derived Evidence containing a combined JavaScript Application Graph
 and explicit match, ambiguity, mismatch, and unknown classifications.

 The operation performs no filesystem, browser, or Electron I/O. It accepts only
 semantically verified Evidence produced by `analyze_javascript_application`,
-`inspect_web_page`, `inspect_electron_page`, `observe_javascript_runtime`, or
-`capture_electron_scenario`; matching operation names alone
+`inspect_web_page`, `inspect_electron_page`, or
+`observe_javascript_runtime`; matching operation names alone
 is insufficient. Provider identity, predicate type, subject digest, target
 parameters, and normalized-result schemas are checked before reconciliation.

-`capture_electron_scenario` supplies target-only partial observations. It does
-not establish loaded-script coverage; see [Electron observation](electron-observation.md).
-
 ## Workflow

 1. Run `analyze_javascript_application` against exactly one application layer.
   Optional cache or assets directories can be analyzed independently and
   supplied as additional layers.
 2. Run `inspect_web_page`, `inspect_electron_page`, or the attach-only
-   `observe_javascript_runtime`, or supply existing `capture_electron_scenario`
-   Evidence with the partial scope above. Capturing script sources is optional,
-   but a source capture provides the strongest byte identity.
+   `observe_javascript_runtime`. Capturing script sources
+   is optional, but a source capture provides the strongest byte
+   identity.
 3. Pass the resulting Evidence records to `reconcile_javascript_runtime`.
   Browser URLs normally need an explicit URL-prefix mapping. Extracted
   Electron and V8 Inspector file locations are mapped automatically when runtime files remain
@@ -107,7 +104,7 @@ nodes. REA evaluates compatible static candidates conservatively:

 Every successful cross-layer `observed_as` edge has
 `authority: cross-layer-reconciliation` and `state: inferred`. The underlying
-artifact/AST observations and runtime observations remain unchanged and
+artifact/AST observations and passive-CDP observations remain unchanged and
 retain their own Evidence links.

 ## Loaded, resident, and not observed
@@ -40,47 +40,6 @@ inspection is needed; see [selected member inspection](#selected-member-inspecti
 Compare separate builds with [member comparison](#member-comparison), preserving
 their paths, digests, and selection scope.

-### Metadata overview and retained rows
-
-The existing CLI and omitted/complete MCP detail return complete metadata
-inventories. For identity and classification questions, select
-`inspect_managed_artifact` with
-`{"path":"/absolute/path/Assembly.dll","detail":"summary"}` on the first call.
-This keeps the complete source in the session and returns a distinct linked
-`inspect_analysis_view` overview with complete PE/CLI, classification and its
-evidence, metadata status, module/MVID, assembly, frameworks, returned-row counts,
-coverage/issues and limitations. No assembly is loaded or executed.
-
-Use `normalized_result.parent_evidence_id` to page original rows:
-
-```json
-{
-  "source": {
-    "kind": "retained-evidence",
-    "evidence_id": "<parent_evidence_id>"
-  },
-  "view": {
-    "kind": "managed",
-    "collection": "attributes",
-    "offset": 0,
-    "limit": 16
-  }
-}
-```
-
-Collections are `references`, `resources` and `attributes`; rows retain their
-original values, nulls, order, metadata tokens and offsets. Pages retain source
-metadata status and coverage. Exhaustion covers the returned parent collection,
-not all possible metadata, and empty rows under partial/unavailable metadata do
-not establish absence. Tokens are build-local and require the recorded artifact
-SHA-256 and known module MVID for cross-observation matching.
-
-Retained views do not repeat the parser or require the source file to remain
-available. Portable views use the authenticated original Evidence inline,
-including the existing `inspect-analysis-view` CLI. Session record lifetime and
-export/import semantics remain unchanged. A server without Evidence retention
-rejects selected summary before analysis; complete delivery remains available.
-
 ## Shipped scope

 The canonical parser admits PE/CLI bytes and their metadata/CIL without loading
@@ -151,7 +110,7 @@ assembly. Older member Evidence without `selection` remains readable.

 Start by identifying the artifact with `inspect_managed_artifact`, then inspect
 its types and CIL with `inspect_managed_members`. Use [member comparison](#member-comparison)
-for another build, and [managed/native boundary rules](#managed-native-boundaries)
+for another build, and [managed/native boundary rules](#managednative-boundary-rules)
 when matching declared native calls to supplied native Evidence. Static inspection
 does not load or execute the assembly. Reconstructed structure and unresolved
 native/runtime questions retain their own authority and coverage.
@@ -220,8 +179,6 @@ to native function addresses requires verified
 provider evidence; names or vtable similarity alone do not prove that a native
 function implements a specific managed method.

-<div id="managed-native-boundaries"></div>
-
 ## Managed/native boundary rules

 `verify_managed_native_boundaries` compares declared P/Invoke module and entry
@@ -21,12 +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.

-Evidence and bundle imports reject unsupported fields in their envelopes,
-identities, manifests and other fixed metadata before authentication. Imports
-leave retained session state unchanged when validation fails. Keep application
-metadata in the supported JSON payloads (`parameters`, `raw_result`,
-`normalized_result`, or analysis-profile parameters), where keys are preserved.
-
 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, and remediation.
@@ -84,12 +78,6 @@ unknown metadata. Missing omission counts remain null. Summary output carries
 every matching record; actual transport admission still applies. Omitted
 `detail` preserves complete canonical bundle delivery; filters require summary.

-`list_unknowns` returns every matching current head by default. For a smaller
-inline response, supply `offset` and `limit`, then follow `next_offset` until it
-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.
-
 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
@@ -106,49 +94,10 @@ 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
-
-Strings, symbols, decompiled code and pseudocode, page text, script bodies,
-network captures, logs, and file listings come from the analysis target. A
-target can embed text written to look like instructions to the agent, for
-example a string asking it to run a command or download a "required" helper.
-REA treats that text as data, and its server instructions tell the agent to do
-the same: never follow directives found in tool results, and report any request
-to run, install, download, or send something as a prompt-injection attempt.
-
-Results from tools that can return such content carry a stable marker in the
-result's `_meta`, whether the call succeeded or failed:
-
-```json
-{ "provenance": { "untrusted_content": true, "source": "analysis_target" } }
-```
-
-The marker is declared once per tool contract (`returnsTargetContent`) and is
-on by default: only `export_evidence_bundle` and `record_unknown`, whose
-results and errors contain only REA session state or caller-supplied values,
-omit it. Tools whose results or errors can include provider, launcher, or
-device output stay marked, including `binary_session` (provider failure
-reasons and availability diagnostics), `close_binary` (provider cleanup
-diagnostics with captured launcher output), `inspect_adb_client` and
-`inspect_apktool_client` (version output and stderr excerpts), and
-`update_unknown` (it echoes the stored question and domain, which an imported
-bundle can supply). A new tool is marked until it is audited into
-that exception list. Error results (`isError: true`) from a marked tool carry
-the marker too, because a failure can include target-derived text: an error
-message, captured output, or a `partial_observation` such as terminal data
-retained by a cancelled `capture_process_scenario`. That covers provider and
-admission failures, the response-budget error that replaces an oversized
-result, its oversized-error replacement, and errors the MCP SDK builds itself,
-such as input validation failures. The marker adds a fixed number of bytes
-that the response budget accounts for. It does not alter `content` or
-`structuredContent`. Hosts and hooks can use it to apply stricter handling,
-such as requiring approval for process-launching or device-mutating tools
-after target content was read.
-
 ## Retained application Evidence inputs

-`analyze_javascript_application`, `inspect_binary_layout`, `inspect_artifact`,
-`inspect_wasm_artifact`, and `inspect_macho` accept `detail`:
+`analyze_javascript_application`, `inspect_binary_layout`, `inspect_artifact`, and
+`inspect_wasm_artifact` accept `detail`:
 `complete` (default) returns the complete analysis Evidence; `summary` records
 that complete Evidence in the session and returns the derived
 `inspect_analysis_view` summary Evidence instead. Its
@@ -218,19 +167,6 @@ attempting oversized delivery, and returns the same summary with an exact
 `parent_evidence_id` for later export or facet reads. Delivery detail does not
 reach WABT or change the original source Evidence ID.

-Completed `inspect_macho` Evidence supports a summary and
-`view: {kind: "macho", facet: "exports", offset: 0, limit: 64}`. Facets are
-`entrypoints`, `architectures`, `build_metadata`, `load_commands`,
-`dependencies`, `imports`, `exports`, `segments`, and `provenance`; pages return
-the original rows. The summary keeps the selected slice, header fields and UUID,
-and replaces each collection with its returned count, reported total and
-`exhaustive` flag. Each page repeats the paged collection's `source_total` and
-`source_exhaustive`; exhausting a non-exhaustive collection does not establish
-that unreturned symbols are absent. Large frameworks return megabytes of
-symbols (Electron Framework: 2.5 MB of imports and exports, 3.3 KB as a
-summary), so select `detail: "summary"` on the first call. Delivery detail
-never reaches the native tools or changes the source Evidence ID.
-
 `trace_application_feature`, `trace_javascript_semantics`,
 `compare_application_versions`, `compare_source_to_bundle`, and
 `compare_javascript_export_shapes` accept complete inline application Evidence
@@ -1,5 +1,3 @@
-<div id="native-ui-and-dispatch-investigation"></div>
-
 # Native binary investigation

 Use a native provider to discover functions, inspect instructions and pseudocode,
@@ -1,176 +0,0 @@
-# Recorded packet capture inspection
-
-`inspect_packet_capture` answers which selected protocol fields TShark observes
-in an existing capture. Network, USB or Bluetooth recordings can use the same
-field/filter interface when the installed TShark supports their encapsulation
-and dissectors. This tool does not acquire traffic, open an interface or control
-a device. HAR/SAZ/mitmproxy web-capture workflows remain separate.
-
-Supply an existing TShark 4.x installation **on Linux**, with util-linux
-`prlimit` available at `/usr/bin/prlimit`. Override its absolute path with
-`REA_TSHARK_PRLIMIT_COMMAND` if required. Unsupported hosts, including macOS
-and Windows, are refused before inspection because this integration requires
-an enforced address-space limit:
-
-```sh
-export REA_TSHARK_COMMAND=/absolute/path/to/tshark
-rea inspect-packet-capture /artifacts/device.pcapng \
-  --fields ip.addr --fields udp.port --fields data.data \
-  --display_filter 'udp' --format json
-```
-
-The corresponding MCP call is:
-
-```json
-{
-  "name": "inspect_packet_capture",
-  "arguments": {
-    "path": "/artifacts/device.pcapng",
-    "fields": ["ip.addr", "udp.port", "data.data"],
-    "display_filter": "udp"
-  }
-}
-```
-
-`frame.number` is always included. Repeated values are ordered string arrays,
-for example `"ip.addr": ["192.0.2.1", "192.0.2.2"]`. Missing fields remain
-absent; they are not converted to zero or empty arrays. Export-only index/score
-metadata is discarded. No payload bytes are automatically added; select a
-supported byte field such as `data.data` or `@data` when needed.
-
-Selectors are limited before argv expansion: at most 1,024 fields and 1,024
-`decode_as` rules, 8,192 UTF-16 code units per selector, and 32 KiB total encoded
-selector arguments (UTF-8 text, terminators, option names and argv pointers).
-This leaves headroom below Linux's [execve argument/environment limits](https://man7.org/linux/man-pages/man2/execve.2.html);
-an unusually large inherited environment can still prevent launching.
-
-Output is paged after filtering: `match_limit` defaults to 50 and `match_offset`
-to 0. The result retains original frame numbers and reports `output_window`
-with the matching count within the input read scope, returned count and
-`has_more`. Request later pages with the offset, or explicit `match_limit: null`
-(CLI `--all_matches`) for all remaining matches. Paging does not shorten
-input reading or change two-pass reassembly. Producer output must still fit its
-resource limit; use selected fields, a display filter or an input-packet limit
-when dissection output is too large. Each call checks the recording's current
-digest, so pages from different source digests must not be combined.
-
-Additional selections:
-
- `display_filter`: Wireshark display-filter syntax; omitted means no filter.
- `decode_as`: explicit dissector overrides, such as `["udp.port==5555,dns"]`.
-  Repeat `--decode_as` in the CLI for multiple overrides.
- `packet_limit`: optional maximum **input packets read before filtering**.
-  A limit of 1 can therefore yield zero matching packets even when later frames
-  match. Omitted means read to EOF within resource limits. The report records
-  `to-eof` or `up-to-input-packet-limit`, never inferring total capture size from
-  the returned packet count.
- `two_pass`: defaults to true for fields that need later packets and reassembly
-  dependencies. MCP may set false; CLI uses `--no-two_pass` for a single pass.
-
-See the [TShark manual](https://www.wireshark.org/docs/man-pages/tshark.html)
-for field names, display filters, decode-as syntax and pass semantics. Invalid
-fields or filters return producer diagnostics. An empty result does not prove
-absence of traffic outside the selected recording, filter or read range.
-Dissector results are observations, not independently verified device behavior.
-
-Evidence includes source path/digest/size, exact selections, typed packet fields,
-configured and resolved executable paths/digests/full version banner, arguments and stderr. Warnings remain
-visible even on exit zero. `tool.version_diagnostics` also retains warnings from
-the separate version probe. Post-run identity failures identify the affected
-private copy, executable or limiter; resource-signal errors retain the signal
-and effective ceilings. Two-pass mode cannot recover missing capture bytes.
-
-Each call uses a private read-only capture copy and an empty personal
-configuration directory (`WIRESHARK_CONFIG_DIR`), with name resolution disabled.
-The executable, resource limiter and private input copy are rechecked after execution. Owned
-processes, file descriptors and private files are cleaned up; failed cleanup retains ownership and
-completed observations for retry. The one-shot CLI awaits a cleanup retry while
-preserving the original failure and completed Evidence. Completed observations
-remain in the MCP session after cancellation or cleanup failure; bounded
-post-run integrity checks finish before honoring a late abort. Source files
-are never passed to TShark.
-Installed libraries, global configuration and plugins remain trusted, are not
-fully fingerprinted, and can influence dissection. This is not an OS sandbox.
-
-Input is limited to 32 MiB before reading, each command to 30 seconds, and
-combined stdout/stderr to 4 MiB during collection. Output overflow fails instead
-of returning truncated success. Before execution, `prlimit` enforces **1 GiB
-address space per process**, **64 MiB per file**, **30 CPU seconds** and no core
-dumps. Stricter inherited soft/hard limits are preserved; Evidence records the effective
-ceilings. Both limits are set before execution, so dissector allocations and
-compressed-capture expansion cannot exceed the per-process address-space cap.
-These are not aggregate process-memory or filesystem quotas. The selected
-limiter is trusted; its path, digest and arguments are retained in Evidence.
-No arbitrary process flags are accepted.
-
-## Verification
-
-```sh
-npm run build:cached
-REA_TSHARK_COMMAND=/absolute/path/to/tshark node scripts/verify-packet-capture.mjs
-```
-
-The verifier generates its own Ethernet/IPv4/UDP/DNS and Bluetooth HCI PCAPs.
-It exercises real compiled CLI/MCP parity, advertised schemas, repeated/missing
-fields, filtering, decode-as, both pass modes, a packet limit before matching
-frames, Evidence persistence, failure diagnostics, source identity and cleanup.
-An optional positional REA entrypoint verifies an installed package.
-
-The real-tool lane requires Linux and TShark 4.x. A separate kernel-limit
-regression checks the inherited soft/hard limits and verifies an oversized
-allocation is refused before it can consume memory. The Ubuntu workflow uses
-its distribution package; check its outcome before claiming that build verified.
-The earlier macOS check does not establish the current bounded integration,
-which deliberately refuses unsupported hosts. Other formats (including PCAPNG),
-USB, BLE ATT and actual physical capture are not established by these fixtures.
-
-Each provider admits one inspection at a time, including acquisition and cleanup.
-An occupied provider returns a retryable capacity error before acquiring another
-file or worker. Closing the provider stops new admission and drains accepted work;
-failed cleanup remains owned and can be retried.
-
-## Discover protocols and field names
-
-`inspect_packet_fields` / `inspect-packet-fields` queries the installed TShark
-registration glossary before selecting fields for capture inspection:
-
-```sh
-rea inspect-packet-fields --query usb
-rea inspect-packet-fields --kind fields --protocol usb --query idVendor
-rea inspect-packet-fields --kind fields --protocol udp --all
-```
-
-`kind` defaults to `protocols`; `fields` selects field definitions. `protocol`
-selects an exact protocol abbreviation (the protocol itself or its child fields).
-`query` is a case-insensitive literal substring in name, abbreviation or field
-description. `offset` skips matching records; `limit` defaults to 50. MCP
-`limit: null` or CLI `--all` requests all remaining matches within the resource
-budget. `--all` and `--limit` conflict. The window reports examined records of
-the selected kind before filters, matching records, returned records and
-`has_more`; it never counts capture packets.
-
-Returned records preserve field type, parent protocol, display base, bitmask,
-description and original glossary line number. Empty producer strings remain
-empty; protocol records have null field-only properties. Repeated abbreviations
-remain separate registrations. A listed field is an installation capability, not
-proof that the field appears in a selected recording.
-
-The adapter uses the documented `tshark -G fields` grammar under its existing
-private empty profile and Linux process limits. TShark 4.6.9's full glossary was
-measured at 22,303,197 bytes; discovery admits at most **32 MiB** combined command
-output (capture inspection remains at **4 MiB**). Parsing walks lines once and
-constructs objects only for the selected page. Returned strings are copied so
-retained pages do not retain the complete glossary string. Before constructing a selected
-record it charges six times the source UTF-8 bytes plus 512 bytes against an
-**8 MiB** representation budget, covering JSON escaping and record bookkeeping.
-If that budget would be exceeded, narrow the query or page size; results are not
-silently truncated. This is a conservative admission budget, not measured heap
-usage. Parent pipe buffers and producer per-process limits remain distinct.
-
-Tool/limiter identity, version, stderr and selected arguments are retained in
-Evidence. No capture, interface or device is opened. Discovery shares capture
-analysis's admission slot and cleanup owner. Each call rereads the glossary;
-installed plugins, libraries and global configuration remain trusted and are not
-fully fingerprinted. There is no cache or snapshot-consistent pagination claim.
-The real Linux lane checks public CLI/MCP queries against the direct glossary,
-including USB vendor-ID typing, negative queries and paging.
@@ -1,118 +0,0 @@
-# Packet capture summaries
-
-REA summarizes already saved pcap/pcapng files through caller-selected Wireshark
-4.x `tshark` and `capinfos`. Use `inspect_packet_capture` for selected fields,
-filters and decode-as rules; use this family for address, DNS, SNI, protocol-stack
-and URI inventories. It does not acquire traffic or fetch recorded targets.
-
-## Supply tools
-
-```sh
-export REA_TSHARK_COMMAND=/absolute/path/tshark
-export REA_CAPINFOS_COMMAND=/absolute/path/capinfos
-# Linux only; default /usr/bin/prlimit
-export REA_TSHARK_PRLIMIT_COMMAND=/absolute/path/prlimit
-rea inspect-pcap-client
-rea inspect-pcap-capture /captures/session.pcapng --json
-```
-
-Without explicit tool commands, this family resolves them through PATH and
-records that selection source. Client inspection reads no capture file. Capture
-inspection requires Linux with util-linux prlimit or Windows with owned Job
-Objects. macOS capture inspection returns a capability gap because the new
-native memory boundary is unverified; its version probes remain available.
-Tools and installed libraries/plugins are caller-trusted. An empty private
-personal Wireshark configuration is used; this is not an OS sandbox.
-
-## Inspect only the needed facts
-
-MCP `inspect_pcap_capture` accepts `path` and optional `detail: "summary"`.
-Complete delivery remains the default. Summary commits and retains the same
-complete Evidence, returning identity, capture metadata, observed counts,
-retained counts, source coverage and diagnostic lengths without large lists.
-Then use its `normalized_result.parent_evidence_id` with
-`inspect_analysis_view` source kind `retained-evidence`:
-
-```json
-{"kind":"pcap","facet":"endpoints","offset":0,"limit":20}
-{"kind":"pcap","facet":"dns-queries","offset":0,"limit":20}
-{"kind":"pcap","facet":"dns-addresses","query":"example.com","offset":0,"limit":20}
-{"kind":"pcap","facet":"tls-sni","offset":0,"limit":20}
-{"kind":"pcap","facet":"diagnostics","stream":"tshark","offset":0,"limit":4096}
-```
-
-Other row facets are `protocols`, `http-uris` and `unattributed-addresses`.
-Defaults are offset 0 and limit 64. DNS question pages give address counts;
-select one exact retained question to page its addresses. Diagnostic windows
-count UTF-16 code units; other windows count rows. Missing/ambiguous selectors
-fail. Unknown legacy diagnostics remain unknown, not an observed empty stream.
-Portable CLI views use the existing `inspect-analysis-view` workflow with inline
-complete Evidence. Views never reread the source or launch Wireshark and work
-after the original file is deleted. Page exhaustion covers the retained facet;
-it does not establish network completeness or recover missing traffic.
-
-## Interpret provenance and coverage
-
-`target.sha256` binds observations to an admitted stable capture snapshot. Both
-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.
-
-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 `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
-200/100/50-item truncation is applied. HTTP transport credentials are excluded
-without rewriting other URI bytes; ambiguous credential spans cause omission.
-Counts preserve distinct observed source URIs before omission or coalescing.
-`coverage: "partial"` records unresolved DNS attribution or URI item loss;
-component credential exclusion is also counted explicitly. Diagnostics retain
-both tool stderr streams. Recorded fields do not establish decrypted payloads,
-causality, process identity, absence of unrecorded traffic or current deployments.
-
-## Resources and lifecycle
-
-One inspection is admitted at a time per provider. Concurrent calls return a
-capacity error; close drains active work before releasing resources. Captures
-are streamed into a read-only owned snapshot with a 2 GiB disk budget. Native
-capture commands enforce Linux address-space ceilings of at most 1 GiB,
-300 CPU seconds, 64 MiB per file and no core dumps, preserving stricter inherited
-limits. Windows uses a 1 GiB committed-memory limit for each owned tool tree.
-These are not aggregate machine or filesystem quotas.
-
-TShark output is bounded at 8 MiB; its known five-level selected-field shape and
-128 MiB graph-expansion estimate are checked before allocation. Retained facts
-have a separate 16 MiB estimate. Capinfos output is limited to 64 KiB. Command
-wall deadlines are 300 s for dissection, 60 s for metadata and 20 s for probes.
-Native ownership preparation has its own bounded lifecycle.
-
-Malformed/oversized output returns no partial success. Unvalidated partial JSON
-is not returned as facts. Cancellation reaches probes, acquisition, commands and
-projection. Cleanup failure returns a typed error, retains completed Evidence
-when available, and retains owned resources for retry on close.
-
-## Verification scope
-
-Current follow-up verification uses Linux/Node 24.18.0 and Wireshark 4.0.17.
-Private real recorded corpora are checked against independent raw-frame/IP
-parsing and Python aggregation, public CLI/stdio MCP parity, SDK schemas, source
-hashes and retained views. Synthetic native tools separately test malformed
-output, cancellation, source/snapshot mutation, capacity and cleanup; they do
-not establish real Wireshark or other-platform behavior.
-
-The original proposal reported Linux 4.6.6, macOS/Windows 4.6.9 verification on
-its earlier implementation. Those reports do not verify the new final memory
-boundary. Actual Windows/Bun Wireshark execution is unverified here; macOS
-capture support needs a separate enforceable-bound decision.
-
-```sh
-npm run verify:pcap -- --pcap /absolute/saved-capture.pcapng
-```
-
-This verifier exercises built CLI/stdio MCP, schemas, artifact identity and
-cleanup. Without `--pcap`, capture inspection is reported as unverified. Private
-captures, keys and provider runtime files are not committed.
@@ -416,52 +416,3 @@ while its token became unavailable after this change; npm changes its title
 as well. A newly started unreadable process can prevent verified cleanup even
 after the selected command exits. REA preserves this uncertainty and leaves
 that process untouched.
-
-Reading those tokens requires compiling a small Swift helper with `xcrun swiftc`.
-By default that compilation reuses Swift's shared module cache, while the
-compiler's intermediate objects stay inside the per-run temporary root that REA
-removes afterwards. Set `REA_DARWIN_MODULE_CACHE_PATH` to a writable directory
-when a shared cache is unavailable, for example under an enforced write
-boundary. REA creates the directory, passes it to the compiler as
-`-module-cache-path`, and exports it as `CLANG_MODULE_CACHE_PATH` so the
-Objective-C header modules the helper builds land there too. REA never removes
-that directory: it outlives each run, so the first compilation into a new
-directory pays a cold-cache build and later runs reuse it. An absent or empty
-value keeps the shared default.
-
-`xcrun` also maintains a separate tool-lookup cache. Its `--no-cache` option
-refreshes entries and does not guarantee a write-free lookup. To avoid that
-lookup while compiling REA's helper, set `REA_DARWIN_SWIFTC_PATH` to the absolute
-path of an installed `swiftc` and `SDKROOT` to the absolute path of a compatible
-macOS SDK. REA invokes that compiler directly with `-sdk` and the selected SDK;
-an unset or empty compiler setting keeps the normal `xcrun swiftc` path. A
-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.
-
-For example, select paths from your existing Xcode or Command Line Tools
-installation **before** entering an enforced write boundary:
-
-```sh
-export REA_DARWIN_SWIFTC_PATH="$(xcrun --find swiftc)"
-export SDKROOT="$(xcrun --show-sdk-path)"
-export REA_DARWIN_MODULE_CACHE_PATH="$PWD/rea-cache/modules"
-export TMPDIR="$PWD/rea-cache/tmp"
-mkdir -p "$TMPDIR"
-rea analyze-javascript-application ./fixture --artifact-format directory
-```
-
-Keep the selected compiler and SDK paired. Permit REA's evidence/output paths
-and its temporary directory as well as the caller-owned module cache. REA does
-not create a sandbox or claim that these settings contain every write made by
-arbitrary toolchains or analysis providers. They bypass REA's `xcrun` lookup
-and select the helper's Swift/Clang cache without disabling ownership checks.
-The caller-owned cache survives cancellation and cleanup; per-run compiler
-intermediates and the compiled helper remain REA-owned temporary files.
-
-The boundary must also permit process-table inspection. On macOS, `/bin/ps`
-is setuid and a blanket sandbox may reject its launch with `spawn EPERM`.
-REA then preserves ownership uncertainty and can report `cleanup_incomplete`;
-it does not disable verification to continue. A sandbox that explicitly allows
-this read-only process inspector is a separate prerequisite from the compiler
-and cache settings.
@@ -61,7 +61,7 @@ Independent raw verification streams the complete private snapshot digest and
 extent with bounded memory and supports cancellation during the read.

 Hopper and IDA refuse raw-binary targets. Windows Ghidra P0 continues to admit
-native PE applications and DLLs only; raw-binary targets are unsupported.
+PE applications only.

 ## Limitations

@@ -36,7 +36,7 @@ check project-owned conformance fixtures and fail-closed report behavior.
 | ------------------------------- | --------------------------------------------------------------------------------------------------------------------- |
 | `discover-classify`             | target-free startup, artifact inventory, compatible workflow selection, and exact visible limits                      |
 | `diagnose-environment`          | broken runtime separated from analysis failure, version skew detected, and revision changed after recovery            |
-| `acquire-authority`             | missing scope reported, narrow grant resumed, expansion reprompted, and denial launched nothing                       |
+| `declare-request`               | exact target, operation, and lifecycle are carried by the request before launch                                       |
 | `static-analysis`               | native and JavaScript routing plus preserved ambiguity, truncation, unsupported syntax, and residual unknowns         |
 | `reactive-scenarios`            | predicate-driven interaction, descendant settlement, Electron correlation, and cancellation cleanup Evidence          |
 | `compare-authority-candidate`   | explicit partial-order/finite-trace semantics, primary divergence localization, and unknown for incomplete comparison |
@@ -6,10 +6,7 @@ checks to pass. Merging that PR into main starts publication automatically.

 The Release workflow validates the merged release metadata and ancestry before
 creating a tag. npm and MCP Registry publication use the exact reviewed merge
-SHA returned by Release Please. Before either registry is published, the release
-run calls full CI qualification at that exact revision, including coverage,
-portable providers, and every native package host. Later main commits cannot
-change or cancel that proof.
+SHA returned by Release Please. Later main commits cannot change that source.
 Ordinary main pushes and closed, unmerged PRs cannot publish packages. Check
 both publication jobs and the published-package canary; a merged PR or GitHub
 tag alone does not establish that publication finished. Retry failed jobs in
@@ -199,14 +196,8 @@ both registry publishes.
 See [npm's provenance implementation](https://github.com/npm/cli/blob/v11.16.0/workspaces/libnpmpublish/lib/provenance.js)
 for the use of GitHub's workflow ref and commit SHA.

-Full qualification builds the bundled Windows controls and verifies the packaged
-artifact on its native hosts. The Linux x64 verifier retains the exact tarball
-it installed and tested, after its workspace cleanup completes. The npm job
-downloads that archive from the same workflow run and checks its source SHA,
-run identity/attempt, package and Node versions, host identity, and SHA-256.
-It publishes that archive without rebuilding or repacking it. Re-running failed
-publisher jobs can reuse a prior successful attempt from the same run.
-The workflow then verifies the published CLI, the
+The workflow builds the bundled Windows controls and verifies the packaged
+artifact before npm publication. It then verifies the published CLI, the
 capability-scoped MCP catalog, and the isolated package update path before
 publishing MCP Registry metadata.

@@ -227,15 +218,6 @@ release baseline and can propose an already-published version again.
 After publication, open a PR from the release branch back to main. Preserve
 main's later implementation changes and regenerate ignored build outputs from
 the combined contracts with the released package version.
-Before merging, check whether GitHub permits merge commits:
-
-```bash
-gh api repos/morluto/rea --jq .allow_merge_commit
-```
-
-If disabled, a maintainer must arrange an approved ancestry-preserving merge
-path before synchronization can finish. Squash and rebase merges do not put the
-released tag in main's ancestry. Do not substitute them for this step.
 Review and test this synchronization PR, then use a merge commit so the release
 tag remains in main's ancestry. Keep the released tag unchanged.

@@ -1,142 +0,0 @@
-# Recorded signal decoding
-
-`decode_signal_recording` answers what a selected protocol decoder observes in
-an existing recording. It uses caller-supplied **sigrok-cli 0.7.2** with
-libsigrokdecode on **Linux**. util-linux `prlimit` is required (default
-`/usr/bin/prlimit`, overridable with absolute `REA_SIGROK_PRLIMIT_COMMAND`).
-The limiter sets soft and hard address-space limits before the decoder starts.
-macOS and Windows are refused because this adapter cannot enforce that limit on
-those hosts. It does not acquire samples or communicate with hardware.
-
-```sh
-export REA_SIGROK_COMMAND=/absolute/path/to/sigrok-cli
-rea decode-signal-recording /artifacts/uart.vcd \
-  --decoders uart:rx=RX:baudrate=9600 --input_format vcd \
-  --annotations uart=rx-data --format json
-```
-
-The corresponding MCP request is:
-
-```json
-{
-  "name": "decode_signal_recording",
-  "arguments": {
-    "path": "/artifacts/uart.vcd",
-    "decoders": "uart:rx=RX:baudrate=9600",
-    "input_format": "vcd",
-    "annotations": "uart=rx-data"
-  }
-}
-```
-
-`decoders` uses sigrok's decoder stack and option/channel syntax. Channel names
-must match the recording; REA does not guess wiring, baud rate or protocol.
-Omitting `input_format` requests sigrok's autodetection. Omitting `annotations`
-retains every annotation class. Both omitted selections are recorded as null.
-See the [upstream manual](https://sigrok.org/wiki/Sigrok-cli) for formats,
-decoder stacking and annotation selectors. No arbitrary command flags are accepted.
-
-Output defaults to 50 literal LF-separated lines. Use `line_offset` and
-`line_limit` for later pages, or MCP `line_limit: null` / CLI `--all_lines`
-for all remaining output. `output_window` reports `total_lines`, `returned_lines`
-and `has_more`; these count display lines, **not annotations or samples**.
-Line endings, blank lines and text within the selected window stay unchanged.
-REA does not parse display text into protocol facts, as explained by
-[upstream's annotation output guidance](https://sigrok.org/wiki/Protocol_decoder_output).
-Paging does not shorten decoding and producer output must still fit its limit.
-Use annotation-class selection to reduce producer output. Calls independently
-check the source digest; do not combine pages from different digests.
-
-Each selector is limited to 8,192 UTF-16 code units, and total encoded selector
-arguments (UTF-8, option prefixes, terminators and 64-bit argv pointers) to
-32 KiB before launching. This reserves headroom below Linux execve's minimum
-argument/environment budget; a large inherited environment may still exhaust it.
-
-The returned Evidence includes the input path/digest, exact selections, tool
-configured and resolved paths/digests, full version banner (including library versions), annotation text
-with sample-number ranges, and stderr. For example, `1104-1938 uart-1: 52`
-is producer display text over a sample range, not a timestamp or an independently
-verified protocol fact. Text is retained verbatim; it is not parsed as a lossless
-binary payload. Empty output does not establish absence of traffic. Warnings
-remain visible even when sigrok exits zero, including `tool.version_diagnostics`
-from the separate version probe. Post-run identity failures name the tool, limiter
-or private copy involved, rather than blaming the admitted source. Resource-signal
-failures retain the signal and effective limits without inferring its exact cause.
-
-REA decodes a private, read-only copy of the recording, verifies that copy and
-the selected executable and resource limiter after decoding, and removes the workspace after owned
-process cleanup. Failed descriptor, process or workspace cleanup retains ownership for retry, and the one-shot
-CLI awaits a retry without replacing the original failure or completed Evidence.
-Completed observations remain in the MCP session after cancellation or cleanup
-failure; bounded post-run integrity checks finish before honoring a late abort. The source file is
-never passed to sigrok. Caller-supplied tools and their libraries/decoder modules
-are trusted, and hashes identify bytes rather than publisher authenticity.
-
-The input copy is bounded at 32 MiB before reading, each command has a 30-second
-deadline, and combined stdout/stderr is bounded at 4 MiB during collection.
-Oversized output fails rather than becoming truncated success. These limits do
-not form an OS sandbox. Before execution, `prlimit` enforces **1 GiB address
-space per process**, **64 MiB per file**, **30 CPU seconds** and no core dumps.
-Stricter inherited soft/hard limits are preserved; Evidence records the effective
-ceilings. Both limits are set before execution, so decoder allocations and compressed
-recording expansion cannot exceed the per-process address-space cap. These are
-not aggregate process-memory or filesystem quotas. The selected limiter is
-trusted and its path, digest and arguments are retained in Evidence.
-
-## Verification
-
-```sh
-npm run build:cached
-REA_SIGROK_COMMAND=/absolute/path/to/sigrok-cli node scripts/verify-signal-recording.mjs
-```
-
-The verifier synthesizes a 9600-baud 8N1 UART VCD carrying `REA`, then checks
-actual CLI/MCP parity, advertised schemas, stored Evidence, source hashes,
-annotation filtering/autodetection, invalid decoder/input failures and cleanup.
-An optional positional REA entrypoint verifies an installed package.
-The real-tool lane requires Linux, sigrok-cli 0.7.2 and libsigrokdecode. A separate
-kernel-limit regression checks the inherited soft/hard limits and verifies an
-oversized allocation is refused before it can consume memory. Other formats,
-decoders and physical acquisition are not established by the UART fixture.
-The workflow result must be checked before claiming a specific Linux build
-verified. The earlier macOS tool check does not establish the current bounded
-integration, which deliberately refuses unsupported hosts.
-
-One decode is admitted at a time, including acquisition and cleanup. Excess
-requests receive a retryable capacity error before acquiring another file or
-worker. Shutdown closes admission and drains accepted work; failed cleanup
-remains owned and retryable.
-
-## Discover decoders before choosing settings
-
-`inspect_signal_decoders` / `inspect-signal-decoders` queries the **installed**
-sigrok catalog without opening a recording or scanning devices:
-
-```sh
-rea inspect-signal-decoders --query uart
-rea inspect-signal-decoders --decoder uart --query baud
-rea inspect-signal-decoders --decoder i2c --offset 0 --limit 50
-```
-
-Omit `decoder` to search decoder IDs and names. Supply one exact decoder ID to
-read its literal help, including required/optional channels, options, annotation
-classes and documentation. `query` is a case-insensitive literal substring;
-matching help retains original one-based line numbers. Empty query selects all.
-`offset` skips matches; `limit` defaults to 50. MCP `limit: null` or CLI `--all`
-returns all remaining matches; CLI `--all` and `--limit` conflict.
-The window reports examined, matching and returned records and `has_more`.
-A filtered empty page is not evidence that the installation has no decoders.
-
-Discovery refuses more than 65,535 line separators before constructing record
-objects (65,536-line representation budget), in addition to the 4 MiB output cap.
-Exceeding that budget is a resource failure with captured output. Returned text
-is copied so a retained page does not keep the complete producer output alive.
-
-Discovery shares decoding's owned process, admission slot, resource limits,
-cleanup retries and Evidence delivery. It records the executable and limiter
-identities, version banner and warnings. Failed version checks and malformed
-producer output preserve diagnostics. Help is producer text, not an independently
-validated parameter schema. Each request probes again; it does not cache or claim
-stable pages across installation changes. Libraries/decoder modules remain
-trusted and are not fully fingerprinted. Catalog output includes a SHA-256 of
-its executable, not a digest of the complete installation.
@@ -1,144 +0,0 @@
-# SQLite database snapshots
-
-`inspect_sqlite_database` / `inspect-sqlite-database` inspects one explicitly
-selected local SQLite database snapshot without an active native analysis
-target. Use it to understand application storage, configuration or retained
-database evidence. No separate SQLite installation is required.
-
-This operation requires Node.js 24.x >=24.15 or 26+ with the native
-`DatabaseSync.limits` API. The worker verifies that capability before querying
-the copied database. Other REA features retain their published Node.js 22.x,
-24.x or 26+ requirements.
-
-`rea capabilities` reports `inspect_sqlite_database` availability and the
-runtime requirement without opening a database. Unsupported runtimes show
-`available: false`, `availability_code: "unsupported_version"`, and an upgrade
-note while the inventory command still succeeds.
-
-```sh
-rea capabilities --json
-rea inspect-sqlite-database ./application.sqlite --json
-rea inspect-sqlite-database ./application.sqlite --table settings --column key --column value --row-limit 20 --json
-```
-
-```json
-{
-  "name": "inspect_sqlite_database",
-  "arguments": {
-    "path": "/artifacts/application.sqlite",
-    "table": "settings",
-    "columns": ["key", "value"],
-    "row_limit": 20
-  }
-}
-```
-
-MCP paths must be absolute filesystem paths on the current host. CLI paths
-resolve against the operator's working directory. Select a quiescent snapshot:
-stop the writer or obtain a consistent database/WAL pair using the application's
-backup workflow before inspection. A file copy of a live pair does not establish
-an atomic SQLite snapshot, even if no change is detected during inspection.
-
-## Returned evidence
-
-Without a table selection, the default `schema_scope` is `inventory`: compact
-table metadata and index, view and trigger names, without SQL declarations or
-column details. Selecting a table defaults to `selected_table`, which expands
-that table and its indexes and triggers. Explicit `schema_scope: "database"`
-(or CLI `--schema-scope database`) expands all stored declarations and supported
-columns. `schema.completeness` refers to the reported scope; omitted column
-details are marked `not_requested`. SQL declarations retain the original text. Virtual and
-shadow tables are identified as such; their supported metadata coverage is
-reported. If a virtual table cannot be resolved, possible backing tables have
-`kind: "unknown"` and an explicit limitation; their rows are refused. Unrelated
-ordinary tables remain selectable. Schema inventory does not execute views,
-triggers or arbitrary SQL.
-
-Rows are optional. `table` selects one exact ordinary-table name. `columns`
-(CLI repeated `--column`) selects exact visible column names in the requested
-order; omission selects all visible columns, including generated columns.
-Unselected cells are not evaluated or projected. Column selection requires a
-table and at least one name; empty-string identifiers are valid. `row_limit`
-requires `table`, defaults to 20 and accepts positive safe integers. Samples
-remain subject to the byte and worker resource limits below, regardless of row count. The result reports
-the selected limit, returned count and whether more rows were observed. Row
-order is unspecified; a truncated sample does not prove anything about omitted
-records. View, virtual-table and shadow-table row reads are unsupported.
-
-SQLite integers are decimal strings so every signed 64-bit value survives JSON
-serialization. Real values retain their numbers; `"Infinity"`, `"-Infinity"`
-and `"-0"` explicitly preserve infinities and negative zero through JSON.
-Text returns the decoded string together with its bytes as hex and the database
-encoding, preserving malformed text that the SQLite binding may replace for
-display. Blobs are hex, and SQL NULL is a distinct tagged value.
-
-Database and existing sibling `-wal` files have separate original SHA-256 and
-byte counts. The Evidence subject identifies the original database file;
-the WAL identity is also necessary to interpret pending committed data. The
-SQLite engine version is reported with the observed result. Neither digest is
-a claim that the database is healthy, complete or trusted.
-
-## Source files and failures
-
-REA copies the selected database and existing sibling WAL to an owned private
-temporary directory before SQLite opens them. Source files are not opened by
-SQLite, so its locks or shared-memory sidecars cannot modify the original
-snapshot. Temporary copies and the owned worker are cleaned up on success,
-failure and cancellation. Extension loading and schema trust are disabled.
-Empty rollback journals and fully zeroed journal headers left by successful
-`TRUNCATE` and `PERSIST` commits are accepted after stable identity checks.
-Journal headers are checked both before and after acquisition; unchanged file
-metadata alone does not establish that a journal remains inactive.
-Other retained rollback journals are refused because recovery is outside this
-profile. Journal files are never modified or copied into the worker snapshot.
-
-A provider admits at most two inspections through acquisition, worker execution
-and cleanup. Additional requests receive a typed capacity error before reading
-files or creating workers; retry after an active inspection finishes. This
-bounds simultaneous input buffering and private snapshot/worker counts.
-
-The database and WAL together are limited to 256 MiB. SQLite values/records,
-SQL statements and the complete worker JSON reply each have a 16 MiB limit.
-The owned worker has a 256 MiB JavaScript heap limit and a 30-second inspection
-deadline. SQLite native allocations are separate from the JavaScript heap;
-overall native heap and total resident memory are not capped. Row limits do not
-override these byte and resource limits. Resource-limit failures do not return
-an incomplete schema as successful complete evidence.
-
-MCP also applies its configured response budget to the complete Evidence
-envelope. If delivery exceeds that budget, it reports a transport constraint
-with guidance for exporting retained Evidence, requesting a matching larger
-client/server response budget or using complete CLI JSON output.
-
-A cancellation received after the worker has completed does not erase the
-completed observation. If subsequent private-root cleanup fails, the error
-retains the completed Evidence and the resource owner for cleanup retry. MCP
-records that Evidence before delivering the error, which carries its retained
-evidence ID for later retrieval or export.
-
-Changed input identities, special files, malformed databases, unsupported
-formats and resource failures are reported as errors with the selected path and
-meaningful reason. Encrypted databases, database repair, arbitrary SQL,
-cross-database queries and live capture are outside this inspection's coverage.
-
-## Compatibility verification
-
-Run `npm run test:sqlite` after changing the SQLite adapter or its shared
-process, filesystem, CLI or MCP boundaries. It prepares the compiled runtime
-and runs SQLite service, snapshot, inspection, cleanup and public CLI/MCP
-tests. Directory-based selection includes new SQLite service and boundary
-tests automatically. `npm run test:sqlite:run` runs the same cases when the
-compiled runtime and generated test artifacts are already current.
-
-The reusable SQLite CI workflow consumes the shared build artifact and tests
-the latest Node 22.x unavailable-runtime diagnostics, the minimum supported
-24.15.0 release, and the latest 24.x and 26.x releases. The repository-pinned
-runtime also runs the full suite. CI's required gate waits for every selected
-SQLite matrix job; a failed, cancelled, skipped or missing selected lane blocks
-the gate. Workflow changes themselves select the build and compatibility lane.
-
-PR checks run against GitHub's merge with the current base branch. A later
-change to `main` can introduce failures outside SQLite; inspect the failing
-job and recheck the updated merge before treating an earlier green run as
-current verification. Compatibility checks detect regressions, but cannot
-guarantee that an arbitrary future upstream change remains compatible.
@@ -19,12 +19,11 @@ behavior, and complete CI evidence before merging.
 | `npm run test:boundary`           | Boundary, CLI boundary, MCP boundary, process boundary, and process-global projects                                     |
 | `npm run test:mcp`                | MCP boundary project                                                                                                    |
 | `npm run test:acceptance`         | Complete compiled CLI and MCP acceptance workflows                                                                      |
-| `npm run test:python`             | LLDB producer retention and launch contracts with a fake LLDB API; no native debugger required                          |
 | `npm run test:watch`              | Dirty source tests in watch mode, without build                                                                         |
 | `npm run test:watch:all`          | Changed tests from every project; builds at startup, so rebuild after production edits before relying on compiled tests |
 | `npm run check:changed`           | Cached typecheck/lint and branch-related source feedback                                                                |
 | `npm run check:pr`                | Opt-in complete local deterministic gate and generated-file checks                                                      |
-| `npm run docs:check`              | Generated-document validation and fresh onboarding example consistency checks                                           |
+| `npm run docs:check`              | Generated-document validation from current source and build outputs                                                     |

 For example:

@@ -68,16 +67,6 @@ correctness. Select relevant boundary files and real-provider lanes explicitly.
 Source projects also contain large capacity regressions; `test:fast` promises
 no compiled-runtime prerequisite, not a fixed time budget.

-`npm run lint` prints errors and a warning summary; `npm run jscpd` prints
-duplication statistics. Complete reports remain in `.cache/static-checks/` and
-CI uploads them as `static-check-reports`, including after a failed static gate.
-Use `npm run lint:details` or `npm run jscpd:details` for all console diagnostics.
-Both duplicate commands scan production and test code with the same 3% limit;
-the summary commands preserve checker failures and restore reports from cached
-static tasks. Both lint caches include the website, documentation configuration,
-and experiment code scanned by the checker; a regression compares the actual
-lint inventory with Turbo's resolved inputs.
-
 Routine iterations and rebases need focused regressions and relevant checks.
 Before handing off a PR, run `npm run check` and generated-document checks when
 applicable; CI owns the full suite and coverage. Use the full local gate for
@@ -108,12 +97,6 @@ runner. Preserve simultaneous launches where concurrency is itself under test.

 Build/documentation writers hold checkout-local output locks. Tests do not
 hold a broad command lock; `check:pr` finishes tests before document validation.
-Turbo caches deterministic preparation and static checks, but `test:run` always
-executes. Repository files do not fully describe installed tool contents or host
-state. A previous test pass therefore cannot replace current validation, even
-when the source tree is unchanged. `check:pr` also runs the fast Python producer
-suite; CI runs it in the static job for code changes. These producer tests do not
-establish real LLDB engine coverage.

 Vitest's persistent compile cache remains disabled. The `cliTest` fixture shares
 a temporary Node compile cache among its fresh CLI subprocesses. The worker
@@ -263,71 +246,18 @@ CI owns coverage; aggregate and domain/contract thresholds are maintained in
 Coverage does not replace named boundary or real-provider scenarios.

 CI runs six native Vitest shards without retries. Each shard emits a blob
-report; the merge job produces JUnit and JSON diagnostics, a module timing
-report, plus aggregate coverage during full qualification. It retains available
-reports even when a shard fails, uploads available diagnostics, and writes the
-slowest files to the workflow summary. Partial reports are marked diagnostic
-only. Failed, cancelled, or missing selected shards still fail the required gate,
-and aggregate coverage thresholds remain enforced in full qualification.
-Only successful complete full-tier merges publish the small `test-timings` artifact, with
-checkout-relative paths; the build job downloads that artifact for the sequencer
-instead of the coverage/JUnit bundle. Timing weights come from Vitest module
-diagnostics and include tests and hooks, worker preparation, environment,
-imports, and setup. Import timings already include transform waits, which are
-not added again. The weights describe file costs under the measured worker and
-coverage settings; their sum is not workflow elapsed time. The diagnostic
-artifact retains the phase breakdown, while shard history keeps only each
-file's total. Legacy test-body-only history and missing history fall back to native
-sharding. Static checks, documentation, build, package verification, and
+report; the merge job produces aggregate coverage plus JUnit and JSON timing
+reports, uploads them together, and writes the slowest files to the workflow
+summary. Static checks, documentation, build, package verification, and
 real-system lanes remain separate jobs so one kind of evidence cannot stand in
-for another. Workflow syntax and expression validation runs inside the required
-static-check job when workflow changes select it, avoiding a separate runner.
-Native, provider, fixture, SQLite compatibility, and website lanes wait for
-static checks to succeed before allocating their runners. This avoids spending
-those runner slots on revisions that already fail static validation. Portable
-test shards and documentation checks remain independent of static results, so
-they can still provide diagnostic feedback. The required gate rejects skipped
-selected lanes when static checks fail; passing revisions retain all selected
-coverage. This ordering reduces peak demand on invalid revisions but can add
-static-check waiting to otherwise passing runs; it is not a measured reduction
-in end-to-end latency.
-
-Core jobs have execution limits of five minutes for classification, ten minutes
-for static checks, builds, docs, and report merging, and thirty minutes per
-portable test shard. These limits leave headroom for cold setup and full coverage
-while preventing a hung job from holding the active main run for hours. They do
-not bound runner queue waiting. Timeouts still fail the required gate.
-
-The separate `CI timings` workflow batches recent completed CI and Release runs
-hourly or on manual dispatch. It uploads `ci-job-timings-batch` with raw API pages and
-a normalized point-in-time report for each collected workflow attempt, plus a
-batch manifest describing examined coverage, failures, and limits. Overlapping
-lookback windows may collect an attempt again; identify records by run ID and
-attempt. Each batch examines at most 100 completed runs per workflow created in
-the preceding 24 hours, with a four-minute API collection budget. It collects the
-latest attempt of each selected run and does not claim an exhaustive archive.
-It runs the reporter from the trusted default branch with read-only permissions,
-treating workflow runs as API data. It does not allocate a new reporter job for
-every completed, cancelled, or skipped workflow. Reports separate queue
-waiting (`created_at` to `started_at`) from completed execution and report
-percentiles plus matched `npm ci` and artifact-step durations.
-Queue excludes dependency waiting before job creation and does not establish
-whether account concurrency or runner availability caused the wait. Queued jobs with
-placeholder start times, skipped jobs, and missing or invalid timestamps remain
-unknown. The reporter targets each selected run and attempt explicitly.
-Summed job elapsed time is parallel work, not workflow wall time, CPU time,
-memory usage, or billing. Step names identify samples, not complete transfer
-costs. Its queue, execution, and failures are independent of the required gate
-and publication. CPU time and peak process-family memory are not measured by this API.
+for another.

 The build job saves portable Turbo outputs across runs. Eight Linux real-system
 lanes restore this cache without waiting for the build job. The shared action
 derives its key from `test:prepare --dry=json` task hashes, runner OS and
-architecture, `.npmrc`, `.nvmrc`, and the lockfile; test-only changes can reuse compiled outputs. Every
+architecture, and `.npmrc`; test-only changes can reuse compiled outputs. Every
 build and verification command still runs, so Turbo checks task inputs and
-rebuilds misses. A restore prefix with the same platform and toolchain permits
-partial task reuse when one generator's inputs change; Turbo still invalidates
-that generator's entry. Native outputs are not stored in this cache.
+rebuilds misses. There is no prefix fallback to accumulate older build outputs.

 Native package jobs, the Windows curated lane, and the Apple artifact lane reuse
 the same workflow's Turbo cache for portable compiled JavaScript, skills, and
@@ -336,10 +266,9 @@ commands, which restore matching outputs or rebuild on a cache miss. Native
 artifacts, dependency installs, package archives, and runtime verification remain
 host-local. Keep platform-dependent outputs out of this shared cache.

-Record cold and warm preparation separately from fresh test execution when
-benchmarking the optional `npm run check:pr` gate. Compare multiple runs on the
-same host, including subprocess and queue costs; a cached pass is not a test
-runtime measurement. A PR that touches packaging or real-system
+The PR acceptance target is a median `npm run check:pr` wall time below three
+minutes across three warm-build runs on the benchmark host. Keep Vitest caches
+cold unless separately identified. A PR that touches packaging or real-system
 behavior requires the applicable `verify:*` lanes; packaging and installation
 changes also require `npm run verify:package`. The full-gate benchmark measures
 that explicit lane, not the routine iteration requirement.
@@ -363,7 +292,6 @@ prove behavior on the verified Ghidra 12.1.4 and JDK 21 build.
 | `npm run verify:ghidra`                    | Linux x64/arm64 ELF or macOS x64/arm64 Mach-O                                                   | Host C compiler, Ghidra 12.1.4, and full JDK 21                     |
 | `npm run verify:ghidra:seeds`              | POSIX; raw x86 fixture; seed ordering, BSS labels, analyzer readback and unknown-name rejection | Ghidra 12.1.4 and full JDK 21                                       |
 | `npm run verify:ghidra:swift`              | macOS x64/arm64 Mach-O                                                                          | Host Swift compiler, Ghidra 12.1.4, and full JDK 21                 |
-| `npm run verify:ghidra:riscv`              | Linux/macOS x64/arm64 host; source-owned RV32/RV64 ELF through CLI and MCP                      | RISC-V Clang, LLD, LLVM readelf, Ghidra 12.1.4, and full JDK 21     |
 | `npm run verify:ghidra:switch`             | Linux x64 ELF; GCC/Clang optimized and stripped switch fixtures                                 | GCC, Clang, GNU nm/objdump/strip, Ghidra 12.1.4, and full JDK 21    |
 | `npm run verify:ghidra:aarch64-jump-table` | Any supported Ghidra host; AArch64 ELF; signed/unsigned byte/halfword tables; host ARM64 Mach-O | Clang with AArch64 target support, Ghidra 12.1.4, and full JDK 21   |
 | `npm run verify:ghidra:cross-format`       | Any supported Ghidra host; also analyzes AArch64 ELF, x86-64 PE, and x86-64 Mach-O              | `clang`, LLD, and `lld-link` in addition to host-lane prerequisites |
@@ -672,12 +600,11 @@ or upgrade Java, Ghidra, .NET or native toolchains. See
 `npm run verify:ida -- --target /absolute/path/to/program --procedure main`
 uses the existing `REA_IDA_MCP_CONFIG` registration. It installs no engine,
 Python package, or compiler. The target must already be open in the GUI for
-the legacy or native attached profile; the database-supervisor headless profile opens
+the legacy attached profile; the database-supervisor headless profile opens
 a digest-verified private copy. A caller-supplied fixture keeps prerequisites
 limited to the selected engine and host. `tests/conformance/ida/inventory.c`
-provides an optional small native fixture source with exported
-`rea_fixture_add` and `rea_fixture_subtract` functions. For their switching check,
-use `--second-procedure rea_fixture_subtract --second-marker='- 13'`.
+provides an optional small native fixture source with an exported
+`rea_fixture_add` function.

 The lane invokes the production CLI dispatcher and connects the pinned MCP
 client SDK to the production REA server. It verifies function Evidence and
@@ -705,10 +632,6 @@ failed intermittently on that host. Linux headless, modern attached GUI tools,
 other engine versions and architectures remain unverified; see the
 [provider guide](ida-provider.md).

-Native IDA MCP verification uses `"protocol": "native"` with an already-running native plugin and requires `--second-procedure other_function --second-marker unique_second_body_text` to exercise GUI function switching and a return to the first function. These options remain optional for other profiles. The literal marker must appear in the second function's pseudocode and be absent from the first. Native cloud/widget failures are reported without hidden retries.
-
-The initial Linux x64 IDA Free 9.4 run used native MCP 1.1.2 with a local navigation correction. Windows x64 verification uses **IDA Pro 9.3**, the two-function public fixture, and the shipped Windows `whoami.exe` application. The native plugin was built from upstream `c9d15d98e8a143fc74f6e14037c48f63889b6d6c`, including the merged navigation fix, with a local loopback-listener change. Production CLI/MCP parity, switching, identity and cleanup passed. Correctness and performance measurements are recorded in the [Windows native verification notes](https://github.com/morluto/rea/blob/main/experiments/analysis-efficiency/ida-native-windows.md). Stock 1.1.2 switching, native macOS, and Windows IDA Free remain unverified. See the [native bridge prerequisites](ida-provider.md#optional-native-ida-mcp-bridge).
-
 ## DOS Ghidra analysis

 `npm run verify:ghidra:dos` requires the supported Ghidra and JDK installation
@@ -742,44 +665,6 @@ specifications, independent mappings, unchanged bytes, and decompilation of a
 known return value. AArch64 remains covered by deterministic tests rather than
 this real-provider lane. See [raw binary analysis](raw-binary.md).

-`npm run verify:ghidra:address-context` runs on Linux with a caller-installed
-Ghidra, full JDK, and an x86-64 ELF GCC toolchain (`CC` selects another compatible
-compiler). It builds
-`tests/conformance/c/pie-address-context.c` as a PIE ELF without executing it.
-The compiled CLI and real stdio MCP workflow must expose the measured image
-base, retain segment address spaces, agree on the overview, resolve explicit and
-numeric file offsets, and reject unmapped analysis addresses with actionable
-guidance. It checks the reverse `address-to-file-offset` mapping, file-coordinate
-Evidence locations, and the suggested CLI search and load-image commands.
-The verifier compares mapped bytes with the source file and checks source
-identity, session preservation after failed lookup, owned runtime cleanup, and
-verified empty process lineage. This lane does not establish Windows or macOS
-real-provider coverage.
-
-For source-identity boundaries that a normal single-file import cannot create,
-`tests/conformance/ghidra/ReaFileOffsetSourceProbe.java` exercises the production
-bridge against real Ghidra `FileBytes`. It rejects auxiliary and partial sources,
-checks the original target's round trip, and retains ambiguity when duplicate
-target bytes have distinct loaded mappings. Injected decompiler failures and
-cancellation verify that completed source/function resolution facts and backend
-failure codes survive; these injections do not establish natural engine failures.
-On Windows, after creating the
-source-owned PE fixture, run from the repository root:
-
-```powershell
-node scripts/create-ghidra-windows-fixture.mjs
-$proofRoot = Join-Path $env:TEMP 'rea-file-offset-source-proof'
-New-Item -ItemType Directory -Path $proofRoot -Force | Out-Null
-Copy-Item bridge/ghidra/ReaGhidraBridge.java, bridge/ghidra/ReaGhidraExtensions.java, tests/conformance/ghidra/ReaFileOffsetSourceProbe.java -Destination $proofRoot
-& "$env:GHIDRA_INSTALL_DIR/support/analyzeHeadless.bat" $proofRoot source-proof -import "$PWD/build/fixtures/rea-ghidra-windows.exe" -scriptPath $proofRoot -postScript ReaFileOffsetSourceProbe.java -deleteProject
-```
-
-Require the `REA_FILE_OFFSET_SOURCE_OK` marker and no script errors; Ghidra may
-exit successfully even when a post-script fails. The probe edits only its
-temporary analysis database and does not execute the fixture. This producer
-regression supplements public CLI/MCP coverage and does not establish Linux
-host behavior or native process-supervision controls.
-
 ## Apple Interface Builder archives

 `npm run verify:interface-builder` compiles the source-owned AppKit XIB into a
@@ -797,35 +682,13 @@ not make native host acceptance unavailable.
 Pull requests that change only root `README*.md` files, `docs/`, `AGENTS.md`,
 `CONTRIBUTING.md`, `CHANGELOG.md`, `SECURITY.md`, `native/windows/README.md`,
 or the GitHub issue and pull-request templates run formatting and
-generated-document validation, including the small onboarding example consistency
-suite, without the source-test shards or native package
+generated-document validation without the source-test shards or native package
 lanes. Classification compares the PR head with its merge base, so later
-base-branch changes do not expand that scope. Static and portable-test aggregate jobs
+base-branch changes do not expand that scope. Static and coverage aggregate jobs
 remain present and fail if classification fails. Every code change retains the
 complete six-shard Linux suite; individual test files are not selected by
 imports or filenames.

-Ordinary PRs also produce an **observational** test-selection plan. The candidate
-leaf-adapter ownership table lives in `scripts/ci/test-selection.mjs`, separately
-from provider-job scopes. It proposes keeping affected owners plus every unowned
-test, including all CLI/MCP, acceptance, composition, conformance, and process
-tests. Shared inputs, unknown paths, missing owner tests, and removed tests fall
-back to the complete inventory. Renames account for both paths. Main, scheduled,
-manual, and `ci:full` runs always propose the full suite.
-
-All six shards still execute the complete suite. The existing report merge
-compares the proposal with actual module outcomes and retains
-`.cache/ci-test-selection/report.json` in `test-results`, including selected and
-omitted paths, changed input paths, missed failures, unobserved files, scheduling weights, PR head and
-executed merge SHA. This adds no test reruns or runner jobs. Missing, duplicate,
-skipped, interrupted, or unhandled results cannot establish a complete comparison;
-even a complete passing comparison is not proof of ownership completeness.
-Before enabling omissions, review representative full-run comparisons and
-cross-owner consumers, including failures, and measure completed CI feedback and
-runner demand. There is no automatic promotion or switch to skip tests. The
-initial proposal measures only leaf producer-test omissions; it does not promise
-the savings of a broader affected-test planner.
-
 `scripts/ci/plan.mjs` selects lanes using the ownership table in
 `scripts/ci/scopes.mjs`. Provider implementation changes run their real-provider
 verifiers and the Linux x64 installed-package/Inspector baseline. The `apple`
@@ -840,19 +703,9 @@ lane. Edits to verifier entrypoints run only by manual, licensed or self-hosted
 workflows run static checks and the Linux suite. Website changes run website
 checks. Provider workflow changes validate the workflow and run that provider's
 verifier. Manual-provider/Android workflow changes run workflow validation only.
-The four-version SQLite compatibility matrix has its own `sqlite` scope for
-SQLite implementation, contracts, CLI/MCP registration, fixtures, and shared
-runtime boundaries. SQLite and server-lifecycle test edits and the SQLite npm
-scripts also select it. Unrelated code edits retain the complete portable suite
-on the pinned Node version without starting four additional compatibility jobs.
-Full qualification retains every SQLite version.
 Shared process/contract/CLI boundaries, dependencies, other packaging inputs,
-unknown paths, and changes to the planner select the full baseline.
-CI timing collection, timing history, and test-report helper edits retain static
-checks and the complete portable suite without selecting unrelated host/provider
-lanes. Classification, qualification, gate, release receipt, and unknown CI
-scripts keep the broad fallback.
-Package script-only edits select their owning verifier when its entrypoint is
+unknown paths, and changes to the planner select the full baseline. Package
+script-only edits select their owning verifier when its entrypoint is
 identifiable; unknown or shared script changes select everything. Android
 build-script edits retain the Linux suite and workflow validation; real Android
 verification stays manual. Renames account for both paths.
@@ -860,84 +713,38 @@ verification stays manual. Renames account for both paths.
 This narrower selection trades PR-time coverage for runner capacity. A change to
 unowned shared runtime code that fails only on arm64, macOS, Windows, the Apple
 artifact lane, or a provider lane that does not own the file is not caught on
-the PR; scheduled full qualification reports it after merge. Ownership globs do
+the PR; the main-push full baseline reports it after merge. Ownership globs do
 not follow imports. Use the `ci:full` label when a change may have native-host
 or provider effects outside its owners.

-Ordinary main pushes use the same owner scopes as PRs. Their diff starts at a
-successful ancestor push run of this CI workflow, rather than the preceding
-push: changes from failed or cancelled intermediate runs remain in scope.
-Missing, untrusted, or non-ancestor history selects every lane. The lookup is
-bounded to the last 100 successful push runs; lookup failures broaden selection.
-Every code change still runs all six portable shards, without coverage
-instrumentation in this fast tier. This deliberately avoids relying on an
-import graph for generated files, filesystem inputs, subprocesses, or bridges.
-
-Scheduled qualification is admitted hourly at minute 23. A forced full run at
-03:23 UTC refreshes runner and dependency drift every day. Other hourly runs
-can reuse a successful full-qualification receipt for the exact source SHA
-from the same repository's trusted CI workflow on its default branch. Both the
-receipt and original workflow run must be less than 24 hours old, so retrying an
-old gate cannot renew stale proof. Missing, expired, failed, foreign, or uncertain proof runs full
-validation; API lookup failure also runs full. Lookups examine at most 100 named
-receipts and three candidate runs within a 20-second budget. Reused runs select
-no validation lanes, identify the original run, and produce no new receipt, so
-reuse cannot indefinitely extend proof freshness. They make no fresh provider
-observation. Manual dispatch, `ci:full`, and exact release qualification always
-run full validation.
-
-Full qualification includes aggregate coverage,
-every portable provider lane, and all native hosts below. Adding `ci:full`
-immediately starts the separate `Full PR qualification` workflow against the
-label event's merge revision; subsequent PR revisions also select the full tier
-in normal CI while that label remains. Unrelated labels do not start validation
-jobs or replace the main CI checks. Manual dispatch also requests full validation.
-Fast-tier broad fallbacks retain all owner lanes and the three-host
-package matrix; Intel macOS and coverage remain full-tier obligations. Each
+Main pushes and manual dispatch retain the full baseline, including all portable
+provider lanes and the native matrix below. A `ci:full` PR label selects the full
+baseline on the next PR run; manual dispatch can request it immediately. Each
 classification job records its selection and broad-fallback reasons in the run
 summary. Representative Git-diff cases live in
 `tests/boundary/filesystem/ciChangeScope.test.ts`.

-`CI required` always runs and checks classification and every selected lane,
-rejecting failed, cancelled, or unexpectedly skipped work. It rejects missing or
-unknown tiers and requires every canonical scope to be explicitly `true` or
-`false`; incomplete classification cannot silently omit verification lanes.
-Branch protection
-should require this aggregate, `Static checks`, `Portable tests`, and
-`Conventional PR title`. Title validation runs separately on PR opening,
-reopening, commits, and edits; correcting a title refreshes only this lightweight
-check. It reads title text through an environment variable, executes no PR code,
-and has no token permissions. Its separate concurrency group cannot cancel
-test runs. Fast PR runs cancel superseded feedback for the same PR. Main push
-runs keep one active run and the latest pending run for that branch.
-Scheduled/manual qualification has a separate concurrency group: active work
-finishes and only the latest pending run is retained. Release qualification uses
-its exact source SHA and cannot be cancelled by newer main pushes. Provider and
-website lanes inherit their caller's scheduling; reusable
-workflows have no independent cancellation group. Direct manual lane dispatches
-run independently on disposable hosted runners. Publication
-requires that qualification to succeed and consumes its exact verified tarball,
-checking source SHA, workflow run, run attempt, package/Node version and SHA-256
-before npm publication. Earlier attempts from the same workflow run are accepted
-when rerunning failed publisher jobs; future attempts and other runs are rejected.
-The public-registry canary still verifies the published package. Licensed/self-hosted
+`CI required` checks classification and every selected lane, rejecting failed,
+cancelled, or unexpectedly skipped work. Existing required check names are
+preserved; changing branch protection to require the new aggregate is a separate
+repository-settings operation. Newer commits cancel superseded CI for the same
+PR or main branch. Release publication has its own concurrency group and retains
+its package verification and public-registry canary. Licensed/self-hosted
 provider workflows and the Android smoke test retain their explicit triggers.

 CI exercises the pinned Node.js runtime on native hosted runners:

-| Host                  | Runner             | Baseline checks                                                                             |
-| --------------------- | ------------------ | ------------------------------------------------------------------------------------------- |
-| Linux x64             | `ubuntu-latest`    | Installed package and real Node Inspector CLI/MCP                                           |
-| Linux arm64 (aarch64) | `ubuntu-24.04-arm` | Installed package and real Node Inspector CLI/MCP                                           |
-| macOS 15 arm64        | `macos-15`         | Installed package and real Node Inspector CLI/MCP                                           |
-| macOS 15 x64          | `macos-15-intel`   | Installed package and real Node Inspector CLI/MCP (hourly, dispatch, release and `ci:full`) |
-| Windows x64           | `windows-latest`   | Curated capabilities, native controls, installed package and real Node Inspector CLI/MCP    |
+| Host                  | Runner             | Baseline checks                                                                          |
+| --------------------- | ------------------ | ---------------------------------------------------------------------------------------- |
+| Linux x64             | `ubuntu-latest`    | Installed package and real Node Inspector CLI/MCP                                        |
+| Linux arm64 (aarch64) | `ubuntu-24.04-arm` | Installed package and real Node Inspector CLI/MCP                                        |
+| macOS 15 arm64        | `macos-15`         | Installed package and real Node Inspector CLI/MCP                                        |
+| macOS 15 x64          | `macos-15-intel`   | Installed package and real Node Inspector CLI/MCP (main, dispatch and `ci:full` only)    |
+| Windows x64           | `windows-latest`   | Curated capabilities, native controls, installed package and real Node Inspector CLI/MCP |

-macOS x64 is the slowest package host. Ordinary PRs and main pushes omit it,
-so darwin x64 installed-package and Inspector regressions surface in full
-qualification. Schedule admission can be delayed by GitHub; the hourly trigger
-does not guarantee an hourly completed result. Release publication waits for
-its own complete result at the exact released revision.
+macOS x64 is the slowest package host. Pull requests without the `ci:full` label
+omit it, so darwin x64 installed-package and Inspector regressions surface on
+the main-push full baseline rather than on the PR.

 Package lanes assert the actual Node platform/architecture before verification
 and record those values with the Node version. The package matrix runs up to
@@ -963,34 +770,17 @@ The Linux source-test shards download a shared runtime and generated test
 metadata snapshot produced by the build job with `npm run test:prepare`. The
 snapshot includes `dist/`, generated skills, the MCP tool catalog, product
 catalog, and managed-conformance metadata. Each shard still installs the locked
-dependencies and runs its assigned tests; full qualification enables coverage. It no longer
+dependencies and runs its assigned coverage-enabled tests; it no longer
 regenerates the same metadata independently.

-The build job also finds an available `test-timings` artifact from a successful
-trusted default-branch scheduled or manual qualification and includes that same
-report in each shard's snapshot. The bounded lookup verifies the artifact's
-producer; newer schedules that reuse qualification without producing timings do
-not hide the last full run's artifact.
+The build job also retrieves the merged timing report from the last successful
+default-branch push and includes that same report in each shard's snapshot.
 CI assigns discovered files by historical duration, with a deterministic
 fallback weight for new files, rather than dividing only by file count. Every
-discovered file still belongs to exactly one shard; worker limits and project
-ordering remain unchanged. The merge job rejects successful reports with missing,
-unexpected, or duplicate portable files. Coverage instrumentation and aggregate
-thresholds remain enforced in full qualification.
+discovered file still belongs to exactly one shard; worker limits, project
+ordering, coverage instrumentation, and aggregate thresholds remain unchanged.
 Missing or unusable history falls back to Vitest's default assignment. Only
-timing data is reused; live provider results are never cached. Turbo outputs are
-restored by task hash, with trusted default-branch runs as cache writers and PRs
-as restore-only consumers. npm caches hold downloads, not `node_modules`.
-
-The eight automatic browser, binary-layout, EVM, JavaScript-recovery,
-recorded-crash, and web provider lanes download `rea-build-cache` from their own
-run after the build and static jobs succeed. Their existing build commands still
-validate task hashes and rebuild mismatched inputs; provider observations always
-run. Provider-workflow-only edits also admit the build without enabling source
-test shards. Direct provider dispatches retain the cross-run restore-only cache.
-This removes repeated compilation on fresh source revisions, but adds the build
-as a prerequisite: a delayed build can delay provider admission. Compare queue
-and execution times before claiming an end-to-end speedup.
+timing data is reused; persistent compile caches remain disabled.

 These native baseline checks complement the Linux source-test shards and the
 separate Apple-artifact and real-provider lanes. Actual Hopper, Ghidra, IDA,
@@ -1026,14 +816,6 @@ establish passing Android coverage; inspect its execution receipt.
 The `termux-browser-diagnostics` artifact retains the Termux command log, exit
 status, and Android logcat on success or failure. The emulator is disposable.

-## Packet capture analysis
-
-`npm run verify:pcap -- --pcap PATH` exercises caller-supplied tshark and
-capinfos against a saved capture. Linux verification uses Wireshark 4.6.6
-and captures containing DNS, TLS and HTTP traffic. Native Windows and macOS
-engine behavior remains unverified; process fixtures do not establish it.
-See [Packet capture analysis](pcap-analysis.md) for contracts and budgets.
-
 ## Apple native metadata and UI

 `npm run verify:apple-dispatch` compiles the Objective-C fixture (classes,
@@ -48,12 +48,10 @@ satisfy. A plan without execution does not establish runtime behavior.
 - Use strict inputs with explicit target identity and required fields. Preserve
  meaningful target, action, capture, and output choices; remove ignored options
  and repeated permission declarations.
- Return the requested facts inline with artifact/provider identity, source
-  locations, Evidence references, coverage, and relevant confidence and
-  limitations. Use supported selection, summaries or views when they answer
-  the question; preserve access to complete source Evidence and honor existing
-  contracts and requested detail. Missing coverage is unknown, not absence.
-  Avoid extra lookups solely to understand the answer or its provenance.
+- Return complete evidence inline, with artifact/provider identity, source
+  locations, Evidence references, and relevant confidence and limitations.
+  Missing coverage is unknown, not absence. Avoid extra lookups solely to
+  understand the answer or its provenance.
 - Keep observed, derived, and inferred relationships distinct. Preserve
  unresolved edges and partial provider facts instead of requiring every
  provider to supply the same metadata.
@@ -25,36 +25,6 @@ and original zero-based producer ordinals; duplicate or out-of-range selections
 are input errors. Every record is validated before selection, so selecting one
 entry does not hide a malformed entry elsewhere.

-For agent discovery over MCP, request `detail: "summary"`. REA retains the
-complete selected Evidence in the session and returns identity and counts.
-Use `normalized_result.parent_evidence_id` with `inspect_analysis_view`:
-
-```json
-{
-  "source": {
-    "kind": "retained-evidence",
-    "evidence_id": "<parent_evidence_id>"
-  },
-  "view": { "kind": "capture", "detail": "preview", "offset": 0, "limit": 20 }
-}
-```
-
-Preview pages select recorded HTTP headline fields, event names/times when
-present, original locations and byte descriptors; they omit headers, XML and
-payload content. Choose `detail: "complete"` in that view for exact record
-pages, including all sidecars. Offsets follow the parent's selected record
-order; producer ordinals remain unchanged. `total_records` counts the original
-capture while `retained_records` and page coverage count records in the parent.
-An exhausted page does not establish absence from unselected records.
-
-Views do not reopen the file or rerun its decoder. They remain historical
-Evidence if the source changes or disappears; inspect the capture again to
-observe new bytes. The inspection tool's default `detail: "complete"` preserves
-existing inline delivery. For CLI use, save complete inspection JSON and pass
-it as inline Evidence to `inspect-analysis-view`; the same summary and capture
-page contracts apply. Large complete records can still exceed MCP's response
-budget; export the retained Evidence when a single record cannot fit.
-
 ## Formats and upstream profiles

 HAR uses unchanged `har-schema@2.0.0` draft-06 schemas, `ajv@8.20.0`,
@@ -87,80 +57,11 @@ tested upstream source is tag `v12.2.3`, commit
 an explicit unsupported-profile diagnostic. Non-Linux native decoding is not
 supported by this adapter.

-## Reading Fiddler captures (`.saz`)
-
-Fiddler Everywhere saves traffic in **Session Archive Zip (`.saz`)** files.
-Inspect native SAZ directly, without installing Fiddler or converting to HAR:
-
-```sh
-rea inspect-web-network-capture /absolute/session.saz saz --json
-rea inspect-web-network-capture /absolute/session.saz saz --record 0 --json
-```
-
-MCP uses the same `capture_path`, `format: "saz"`, and optional
-`record_ordinals` fields as the examples above. REA pairs `raw/<id>_c.txt`
-requests, `_s.txt` responses, and `_m.xml` metadata by filename stem. Archive
-member names identify the source; zero-based ordinals follow each session's
-first member in ZIP directory order, not its numeric ID or capture time.
-
-HTTP fields and ordered duplicate headers are retained, with stored body bytes
-in binary sidecars. Bodies are not dechunked or decompressed. Metadata is an
-XML node tree; optional `_w.txt` and `_g.txt` files retain opaque WebSocket and
-gRPC message bytes. Missing members remain null, distinct from empty bodies.
-See Telerik's [SAZ format reference](https://www.telerik.com/fiddler/fiddler-everywhere/documentation/knowledge-base/fiddler-archives).
-
-The existing ZIP reader verifies read members; expanded archive contents are
-limited to 32 MiB in addition to the input/output budgets below. Encrypted
-archives and unrecognized raw session members are unsupported. SAZ requires an
-enforced decoder memory bound: Node's fixed heap, or the Windows Job Object
-commit limit. Bun on hosts without that Job Object limit returns capability
-unavailable before starting the SAZ decoder. Non-session
-members are inventoried without decoding their content. Original files remain
-unchanged. Linux verification includes independently checked public recorded
-Mattermost captures from [FOREST](https://github.com/dfrc-korea/FOREST/tree/405c9154658a128ea203a6c10040cec55111ed03/api-results/dataset)
-and the Fiddler author's [encoding corpus](https://github.com/ericlaw1979/Clearinet/blob/b6faf78cde1e72042980364f180ceb34b77d1434/Test/data/Encodings.saz),
-plus synthetic malformed/limit fixtures. Their exporting product versions are
-not authenticated. An interactive export from a current Fiddler Everywhere
-installation and its live MCP server remain unverified. Support here is the
-bounded documented raw HTTP/XML SAZ layout, not every product/version profile.
-
-For visual inspection, use Everywhere's **Import Snapshot**, then **Inspectors**
-and **Overview**. HAR remains an alternative: select sessions, choose
-**Export > HTTPArchive**, and confirm `log.version` is `"1.2"`. Preserve the
-original SAZ when exporting. See the [import/export instructions](https://www.telerik.com/fiddler/fiddler-everywhere/documentation/collaboration/exporting-and-importing).
-
-## Fiddler Everywhere MCP and public skills
-
-For agent-driven traffic debugging, connect Everywhere's MCP server separately
-from REA. Run a current Everywhere release with MCP access (Trial, Pro, or
-higher), internet access, and a compatible MCP client. Use
-**Settings > MCP Server > Coding agent**, or **Manual setup** with the generated
-API key. The default endpoint is `http://localhost:8868/mcp`. See Telerik's
-[MCP setup guide](https://www.telerik.com/fiddler/fiddler-everywhere/documentation/agent-tools/fiddler-mcp-server)
-and [agent-skills prerequisites](https://www.telerik.com/fiddler/fiddler-everywhere/documentation/agent-tools/agent-skills).
-
-Telerik's [public skills](https://github.com/telerik/fiddler-agent-tools) cover
-installation (`fiddler-download-setup`), connection setup, and traffic analysis:
-
-```sh
-npx skills add telerik/fiddler-agent-tools --skill fiddler-mcp-setup
-npx skills add telerik/fiddler-agent-tools --skill fiddler-traffic-debugging
-```
-
-After setup, reload the agent client and use the connected server's advertised
-tool names and schemas. Check status, list sessions, then inspect relevant
-session IDs. Set `sessionsSource` to `LiveTraffic` for HTTP(S) traffic or
-`AgentCalls` for enriched LLM calls; active filters affect the session list.
-For an existing run, skip the skill's pre-capture steps that replace process
-filters and clear sessions. The documented MCP session sources do not provide
-a saved-snapshot selector; use the SAZ workflow above for saved files. REA does
-not register or wrap the Fiddler MCP server.
-
 ## Reading the evidence

 - `artifact` identifies the caller-selected file and stable snapshot digest.
- `records` preserve producer order/ordinals and original JSON pointers, byte
-  ranges, or SAZ member names. No live browser transaction or scenario IDs are invented.
+- `records` preserve producer order/ordinals and original JSON pointers or byte
+  ranges. No live browser transaction or scenario IDs are invented.
 - `reported` retains the producer's fields. HAR container metadata is returned
  separately, with `log.entries` replaced by `null` and `records_pointer`
  identifying the record collection. This is an inspection representation,
@@ -255,7 +156,7 @@ response fields, including HAR's `status: 0` and an empty `mimeType`, remain
 unknown, not invented statuses or MIME types.

 The view makes no handler-identity, schema or causality claim. It performs no
-network activity. Native mitmproxy, SAZ and qlog captures return a typed unsupported error.
+network activity. Native mitmproxy captures return a typed unsupported error.
 Parents inspected with `sensitive_values`, or whose Evidence does not record
 `sensitive_value_count`, return a typed unsupported error whose reason is the
 canonical token `sensitive_values_unretained`. The view would write path
@@ -291,15 +192,14 @@ Complete evidence has a 32 MiB input, 96 MiB decoder reply and 64-level nesting
 budget. Exceeding a budget returns no partial success.
 Oversized selected captures return an input error identifying `capture_path`
 and the byte budget; owned reply/output failures remain output or provider errors.
-HAR, SAZ and qlog run in an owned
-192 MiB Node old-generation heap with one V8 worker. Mitmproxy decoding applies
+HAR runs in an owned
+192 MiB Node old-generation heap with one V8 worker. Native decoding applies
 Linux limits of 768 MiB address space, 30 seconds CPU and 96 MiB file output;
 both commands have a 30-second wall deadline and independently supervised
 process cleanup. Owned decoder diagnostics retain at most 1 MiB across stdout
 and stderr; the collector drops overflow as it arrives, reports the limit
 failure and verifies cleanup. Heap limits alone do not establish aggregate RSS limits.
-SAZ and qlog refuse decoding when neither a Node heap limit nor a Windows Job Object bound can be enforced. Existing HAR availability is preserved.
-When REA runs on Bun, the HAR/SAZ/qlog decoder runs on Bun, which ignores these V8 heap
+When REA runs on Bun, the HAR decoder runs on Bun, which ignores these V8 heap
 flags; its limitations and resource failures then omit the heap sizes. On
 Windows, the decoder's owned Job Object instead limits its committed memory to
 704 MiB, the 192 MiB budget plus a 512 MiB reserve for Bun itself. The
@@ -307,7 +207,7 @@ limitations state that limit, and reaching it returns `resource_constraint`
 with `process_memory_limit_bytes`, whatever exit status Bun reports.

 Observed decoder memory exhaustion returns `resource_constraint`, with the
-selected capture, applicable limits and retained process diagnostics. HAR/SAZ/qlog's
+selected capture, applicable limits and retained process diagnostics. HAR's
 old-generation heap is fixed; inherited `NODE_OPTIONS` cannot raise it.
 Record selection happens after complete decoding and does not reduce that
 workload. Use a smaller capture exported by its producer or another decoder
@@ -334,108 +234,3 @@ Command cleanup failures retain the original status and both diagnostic streams;
 the decoder's ownership preparation receives the same cancellation signal.

 MCP advertises the same strict named input contract used by the application. Historical inspection delegates argument validation to that shared application boundary so accepted explicit-sensitive declarations also cover invalid argument names and other correction details. The SDK receives raw arguments through its Standard Schema interface; malformed inputs still fail before decoder or filesystem effects and return the normal structured REA error. Protocol-envelope validation remains owned by MCP.
-
-## Retained aioquic qlog
-
-Select `format: "qlog"` through `inspect_web_network_capture`, or:
-
-```bash
-rea inspect-web-network-capture /absolute/origin.qlog qlog --json
-rea inspect-web-network-capture /absolute/origin.qlog qlog --record 95 --record 0 --json
-```
-
-The initial profile is **aioquic 1.5.0, JSON qlog 0.3**: one JSON object with
-`qlog_format: "JSON"`, `qlog_version: "0.3"`, `traces` containing object events
-with `name`, finite numeric `time` and object `data`. JSON-SEQ, JSONL, columnar
-array events and other versions are unsupported. Duplicate JSON members,
-malformed UTF-8, invalid interpreted QUIC integers and excessive nesting fail
-without partial success, including in events outside the selected ordinals.
-Well-formed event subsets and missing frame metadata remain inspectable.
-Unknown extensions are retained; this is not validation of every qlog schema.
-
-Choosing the format selects the interpretation profile; the file does not
-necessarily report or authenticate an aioquic version. The profile's clock
-uses Unix-epoch milliseconds, verified in aioquic 1.5.0's `QuicLoggerTrace`
-`log_event`/`encode_time`. The `qlog.clock.basis` and Evidence analysis profile
-state that assumption explicitly. Numeric lexemes survive independently of
-safe JSON-number projections; decimal spelling does not establish physical
-clock precision or monotonicity.
-
-Every event has a global ordinal from trace/event source traversal and its
-original `/traces/T/events/E` pointer. This order is not a global time sort.
-Trace index and the selected artifact identify a connection observation;
-reported ODCID is preserved without claiming global uniqueness. Streams are
-scoped by trace, stream ID and sent/received direction. Control/QPACK streams
-are retained, so counting streams does not count HTTP requests.
-
-`qlog` is a typed facet required exactly for this format. Its scope is
-`all-recorded-events-before-selection`: selection changes returned event
-records while facts cite the original ordinals across the entire recorded
-file. The container retains trace metadata with each events array replaced
-by null; there is no single events pointer shared by all traces.
-
-| Fact                                | Basis and limits                                                                                                                                                                                                                                                              |
-| ----------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| Original event and loss declaration | Observed endpoint report; `recovery:packet_lost` does not prove actual network loss. Missing packet number/type remains unknown.                                                                                                                                              |
-| STREAM ranges and byte totals       | Derived per trace and direction from reported offsets and lengths using exact integer arithmetic. `unique_bytes` unions intervals; `frame_length_sum` includes overlaps; `repeated_bytes` is their difference. Overlap alone does not prove retransmission or equal contents. |
-| FIN final sizes                     | Reported offset plus length where FIN is true; multiple conflicting sizes remain visible. A final size does not establish complete coverage or a received body.                                                                                                               |
-| Incomplete fact records             | Ordinals with omitted/redacted interpretable frame metadata; usable fields in other records survive. An empty list does not establish complete logging or capture.                                                                                                            |
-| HTTP bodies and causality           | `body_bytes: "not-reported"`; lengths and headers are metadata, with no reconstructed body, hash, timing causality or live process attribution.                                                                                                                               |
-
-QUIC integer fields interpreted here accept exact nonnegative JSON integer
-values through `2^62 - 1`, including equivalent exponent notation. Offsets plus
-lengths must fit that range. Derived sums are decimal strings and are not
-rounded to JavaScript numbers. A missing offset is unknown, never defaulted to
-zero. Ranges can start above zero or contain gaps. Packet headers, HTTP events,
-raw lengths and unknown extensions remain producer evidence rather than being
-normalized into invented HAR requests.
-
-The adapter excludes authorization/proxy authorization/cookie/set-cookie
-values in known HTTP frame events, reset tokens in transport parameters and
-NEW_CONNECTION_ID frames, and NEW_TOKEN frame tokens. Known URL header userinfo
-and explicit sensitive values follow the shared exclusions. Ordinary extension
-fields and token-looking query text remain retained. Explicit declarations also
-cover normalized numeric projections, derived totals and trace pointers; facts
-that cannot be safely shown are omitted with incomplete-record coordinates.
-No keylog, PCAP, live URL or recorded target is opened by the qlog decoder.
-
-To repeat the real-provider lane with **local caller-supplied evidence** from
-the educational aioquic 1.5.0 experiment (one origin trace, known 32,803-byte
-stream coverage and one 1,169-byte repeated range in the loss case):
-
-```bash
-npm run verify:web:qlog -- /absolute/control/origin.qlog /absolute/loss/origin.qlog /absolute/new-report.json
-```
-
-This lane checks built CLI/stdio MCP parity, SDK-converted JSON Schemas,
-artifact digests, original event count, selection scope, retained parent lookup,
-credential exclusions and the known control/loss facts. The report is created
-exclusively and contains no keys or captured credential values. It is a
-fixture-specific verification, not a general loss detector. CI uses synthetic
-format inputs for malformed cases and limits; those tests do not establish
-producer provenance. PCAP parsing and correlation remain outside this stage.
-
-### Focused qlog views
-
-Use MCP `inspect_web_network_capture` with `format: "qlog", detail: "summary"`
-for identity, profile, scope and retained-fact counts. Then pass its
-`normalized_result.parent_evidence_id` to `inspect_analysis_view` as a
-`retained-evidence` source.
-
-```json
-{"kind":"qlog","facet":"traces","offset":0,"limit":10}
-{"kind":"qlog","facet":"streams","trace_index":0,"offset":0,"limit":10}
-{"kind":"qlog","facet":"contributions","trace_index":0,"stream_id":"0","direction":"sent","offset":0,"limit":20}
-```
-
-Trace pages omit nested lists and give their counts. Stream pages preserve
-exact byte totals but omit contributions, ranges and final-size lists. For
-those lists select `contributions`, `ranges` or `final-sizes` with all three
-stream selectors. `loss-declarations` and `incomplete-records` need only
-`trace_index`. Offsets count rows in that retained facet; defaults are 0 and 64. Missing or ambiguous selectors fail rather than choosing a connection.
-
-These views page already interpreted facts without decoding again or opening
-the source, and work after its deletion. Facts still cover all recorded events
-before parent record selection. Their exhaustion does not prove logging or
-network completeness. Event preview/complete pages remain available through
-kind `capture`, with original numeric lexemes and producer ordinals preserved.
@@ -153,12 +153,8 @@ the private runtime, isolating Ghidra preferences, logs, and caches.
 Process creation assigns a suspended child atomically to an owned Job Object.
 Membership and kill-on-owner-close policy are verified before resume.
 Breakaway is disabled. Only the child's default file owner is normalized;
-the caller token stays unchanged. Caller priority is preserved, and caller CPU
-affinity whenever the caller and the child share a processor group. A child that
-Windows places in another group keeps that group's default when the caller asked
-for no bound of its own; a caller pinned to fewer processors than its group
-holds is refused there rather than widened.
-Close, cancellation, timeout, startup failure, and provider failure
+the caller token stays unchanged. Caller CPU affinity and priority are
+preserved. Close, cancellation, timeout, startup failure, and provider failure
 terminate the job and verify all members have settled before runtime cleanup.
 Cleanup removes admitted objects by handle and unlinks reparse entries without
 following their targets. Abrupt owner death kills the job but can leave
@@ -7,57 +7,6 @@ JSON measurements belong outside the checkout. This document keeps the measured
 findings, verification scope and revision references; the scripts and `corpus.json`
 keep the reproduction inputs. Generated `results/` is ignored.

-Follow-up: [latest-main capability audit](latest-main-audit.md) records the
-Flutter, SQLite, TShark and sigrok priorities and the first shipped Dart AOT
-baseline, preserving existing controls before introducing another selector.
-
-Follow-up: [Dart AOT summary and retained string pools](flutter-aot-summary.md)
-records real LocalSend delivery pairs and old Evidence continuation, preserving
-ABI selection, snapshot identity, original lower bounds and partial coverage.
-
-Follow-up: [SQLite existing-control measurements](sqlite-existing-controls.md)
-tests QGIS's shipped GeoPackage through the existing column selection, preserving
-full selected-table schema and typed cells before considering another API.
-
-Follow-up: [native PE/DOS entry views and real model verification](native-entry-views.md)
-records the post-merge native continuation, including a small-function case where
-four selected replies cost more bytes than the complete dossier.
-
-Follow-up: [EVM descriptor and real-template controls](evm-descriptor.md) extends
-the offline corpus with digest-pinned Uniswap runtime templates and an independent
-published ABI selector oracle, preserving unknown deployment/immutable metadata.
-
-Follow-up: [EVM interface summary delivery](evm-interface-summary.md) records
-the opt-in retained view, old-client/Evidence migration checks and repeated SDK
-and real-model pairs, including mixed token/time results and strict-answer limits.
-
-Follow-up: [task-scoped preset lifecycle verification](preset-lifecycle.md) checks
-real Ghidra profile/snapshot boundaries, startup cancellation and retained cleanup
-retry while preserving defaults and distinguishing verification from performance.
-
-Follow-up: [EVM descriptor lifecycle acceptance](evm-lifecycle.md) verifies actual
-worker replies, late SDK cancellation, permission-induced cleanup failures,
-healthy WASM peers and old CLI parity with explicit runtime and platform scope.
-
-Follow-up: [managed artifact delivery and retained views](managed-artifact-summary.md)
-records two shipped assembly checks, previous-runtime portable Evidence, and four
-actual Codex trials. Selected replies shrink substantially; observed model input
-tokens increase and latency is mixed, so model-token savings are not claimed.
-
-Follow-up: [model tool context and per-response usage](model-context.md) separates
-raw MCP replies from observed client execution/discovery and usage. Optional
-trial capture retains tool/usage items while excluding account and ambient state;
-existing ephemeral trials keep their default behavior.
-
-Follow-up: [Android package delivery and retained manifest](android-package-summary.md)
-records real NewPipe SDK pairs, unchanged old requests/Evidence, exact retained
-text, and actual Codex outcomes including client errors and a failed discovery.
-Reply bytes fall; model-token/time gains are not established.
-
-Follow-up: [resource counters at payload completion](resource-counters.md) adds
-optional owned counter observations while preserving unknown whole-scope final
-counters, default receipt shape and the unchanged CPU/memory safeguards.
-
 The 12 detailed checkpoint receipts were archived byte-for-byte before removal
 from the final PR tree. The archive `review-receipts-00d51e0fc-20261012` is in the
 private experiment lab outside the checkout; its `archive-index.json` records
@@ -87,9 +36,8 @@ acceptance conditions for every optimization.
  experiment control; it does not itself establish reduced CPU consumption.

 Migrate domain by domain with focused real-artifact checks and relevant shared
-contract checks. The native follow-up verifies selected PE and DOS MZ entry facts;
-DOS COM and complete native application behavior remain unverified. The domain
-matrix is a growing roadmap. A passed lane does not imply all
+contract checks. The domain matrix is a growing roadmap; native PE and DOS, for
+example, remain unverified in this study. A passed lane does not imply all
 advertised platforms/providers have passed. Newly discovered REA bugs remain
 in the separate local handoff document for later team repair.

@@ -11,8 +11,6 @@ import subprocess
 import tempfile
 import time

-from codex_context import capture_tool_context
-

 def file_digest(path):
    digest = hashlib.sha256()
@@ -50,20 +48,7 @@ def main():
    parser.add_argument('--providers', type=Path)
    parser.add_argument('--enabled-tools', type=Path)
    parser.add_argument('--authority', choices=['static', 'browser'], default='static')
-    parser.add_argument('--capture-tool-context', action='store_true',
-                        help='Retain owned tool/usage items; excludes account/ambient state')
-    parser.add_argument('--guide-enabled-tools', action='store_true',
-                        help='Opt-in exact-name discovery guidance for selected REA tools')
    args = parser.parse_args()
-    if args.guide_enabled_tools and args.enabled_tools is None:
-        parser.error('--guide-enabled-tools requires --enabled-tools')
-    enabled_tools = None
-    if args.enabled_tools:
-        enabled_tools = json.loads(args.enabled_tools.read_text())
-        if not isinstance(enabled_tools, list) or not all(isinstance(name, str) and name for name in enabled_tools) or len(enabled_tools) != len(set(enabled_tools)):
-            raise ValueError('enabled-tools must be a unique list of exact tool names')
-    if args.guide_enabled_tools and not enabled_tools:
-        parser.error('--guide-enabled-tools requires a nonempty selected tool list')
    def terminate(signum, _frame):
        # The outer resource scope terminates descendants together. Ensure the
        # runner's copied credentials are also removed on a resource abort.
@@ -145,14 +130,11 @@ def main():
            'possible and select the requested normalized_result fields before returning '
            'intermediate output to model context. Keep real Evidence IDs and limitations.'
        )
-    if args.guide_enabled_tools:
-        instruction += (
-            ' Configured REA tool function names for this trial: '
-            + json.dumps(['mcp__rea__' + name for name in enabled_tools])
-            + '. For discovery select only these exact names from ALL_TOOLS and '
-            'return only their metadata. Preserve the original analyst question, '
-            'dependency order and source Evidence.'
-        )
+    enabled_tools = None
+    if args.enabled_tools:
+        enabled_tools = json.loads(args.enabled_tools.read_text())
+        if not isinstance(enabled_tools, list) or not all(isinstance(name, str) and name for name in enabled_tools) or len(enabled_tools) != len(set(enabled_tools)):
+            raise ValueError('enabled-tools must be a unique list of exact tool names')
    quote = json.dumps
    config = '\n'.join([
        'approval_policy = "never"', 'sandbox_mode = "read-only"',
@@ -178,7 +160,6 @@ def main():
                 'inspect_android_package', 'search_android_classes',
                 'inspect_android_class', 'inspect_android_method',
                 'inspect_firmware_regions', 'inspect_managed_artifact',
-                 'inspect_sqlite_database',
                 'inspect_managed_members', 'inspect_managed_native_boundaries',
                 'inspect_artifact', 'inspect_wasm_artifact',
                 'inspect_evm_interface', 'get_evidence_bundle', 'export_evidence_bundle',
@@ -202,8 +183,6 @@ def main():
        (args.output / 'prompt.txt').write_text(prompt)
        (args.output / 'trial-settings.json').write_text(json.dumps({
            'mode': args.mode, 'model': args.model, 'reasoning': args.reasoning,
-            'capture_tool_context': args.capture_tool_context,
-            'guide_enabled_tools': args.guide_enabled_tools,
            'driver_commit': subprocess.check_output(
                ['git', 'rev-parse', 'HEAD'], cwd=driver_repository, text=True).strip(),
            'runtime_revision': args.revision,
@@ -217,7 +196,7 @@ def main():
            'package_lock_sha256': file_digest(repository / 'package-lock.json'),
            'experiment_sources_sha256': {
                name: hashlib.sha256((experiment / name).read_bytes()).hexdigest()
-                for name in ['agent-trial.py', 'codex_context.py', 'provider-environment.json']
+                for name in ['agent-trial.py', 'provider-environment.json']
            },
            'developer_instructions': instruction,
            'developer_instructions_sha256': hashlib.sha256(instruction.encode()).hexdigest(),
@@ -233,8 +212,7 @@ def main():
                         'multi_agent': False, 'code_mode': args.mode == 'client-code',
                         'code_mode_only': args.mode == 'client-code'},
        }, indent=2) + '\n')
-        invocation = [args.codex, '--no-daemon', 'exec', '--strict-config',
-                      *([] if args.capture_tool_context else ['--ephemeral']),
+        invocation = [args.codex, '--no-daemon', 'exec', '--strict-config', '--ephemeral',
                      '--skip-git-repo-check', '--ignore-rules', '--json',
                      '--color', 'never', '-C', str(workspace),
                      '--output-last-message', str(args.output.resolve() / 'answer.txt'), '-']
@@ -256,28 +234,26 @@ def main():
        usage = []
        tools = []
        event_types = {}
-        with (args.output / 'events.jsonl').open() as event_file:
-            for line in event_file:
-                if not line.strip():
-                    continue
-                event = json.loads(line)
-                kind = event.get('type', 'unknown')
-                event_types[kind] = event_types.get(kind, 0) + 1
-                if 'usage' in event:
-                    usage.append(event['usage'])
-                item = event.get('item', {})
-                if item.get('type') == 'mcp_tool_call' and kind == 'item.completed':
-                    tools.append({
-                        **{k: item.get(k) for k in ['server', 'tool', 'arguments', 'status', 'error']},
-                        'codex_event_result_json_utf8_bytes': len(json.dumps(
-                            item.get('result'), separators=(',', ':'), ensure_ascii=False
-                        ).encode()),
-                    })
+        for line in (args.output / 'events.jsonl').open():
+            if not line.strip():
+                continue
+            event = json.loads(line)
+            kind = event.get('type', 'unknown')
+            event_types[kind] = event_types.get(kind, 0) + 1
+            if 'usage' in event:
+                usage.append(event['usage'])
+            item = event.get('item', {})
+            if item.get('type') == 'mcp_tool_call' and kind == 'item.completed':
+                tools.append({
+                    **{k: item.get(k) for k in ['server', 'tool', 'arguments', 'status', 'error']},
+                    'codex_event_result_json_utf8_bytes': len(json.dumps(
+                        item.get('result'), separators=(',', ':'), ensure_ascii=False
+                    ).encode()),
+                })
        final_target_digest = file_digest(Path(args.artifact_path)) if args.artifact_path else None
        summary = {
            'mode': args.mode, 'requested_model': args.model, 'reasoning': args.reasoning,
            'runtime_revision': args.revision,
-            'capture_tool_context_requested': args.capture_tool_context,
            'selected_artifact_sha256_before': target_digest,
            'selected_artifact_sha256_after': final_target_digest,
            'selected_artifact_bytes_unchanged': target_digest == final_target_digest if target_digest else None,
@@ -292,13 +268,9 @@ def main():
        (args.output / 'summary.json').write_text(json.dumps(summary, indent=2) + '\n')
        print(json.dumps(summary))
    finally:
-        try:
-            if args.capture_tool_context:
-                capture_tool_context(trial_codex_home, args.output)
-        finally:
-            # Capture failure must never prevent copied-credential cleanup.
-            shutil.rmtree(profile)
-            (args.output / 'cleanup.json').write_text(json.dumps({'profile_removed': not profile.exists()}) + '\n')
+        # Always remove copied credentials, config, caches and profile state.
+        shutil.rmtree(profile)
+        (args.output / 'cleanup.json').write_text(json.dumps({'profile_removed': not profile.exists()}) + '\n')
    raise SystemExit(124 if timeout else exit_code)


@@ -1,166 +0,0 @@
-# Android package summary and exact retained manifest
-
-Continues [#2016](https://github.com/morluto/rea/issues/2016) and
-[#2438](https://github.com/morluto/rea/pull/2438). The recurring NewPipe question
-asks for APK/package/version identity, all case-sensitive MainActivity matches
-and all reported onCreate entries, including explicit null DEX descriptors.
-Complete package replies delivered decoded manifest text and duplicate upstream
-calls unrelated to those selected facts.
-
-## Compatibility and ownership
-
-MCP `inspect_android_package` accepts explicit `detail: "summary"`; omitted and
-`"complete"` requests preserve the complete output and provider request. The
-one-shot CLI stays complete. Summary selection happens in the application
-workflow, independently of the engine protocol, using the existing retained
-analysis-view machinery. No third-party plugin API or persistent analysis cache
-is introduced. Servers lacking retention reject summary before provider work.
-
-The complete original Evidence stays under its original ID and session lifetime.
-A distinct linked derived view returns all package/SDK/permission declarations,
-engine identity, class/resource counts and signature-verification status.
-Manifest metadata retains the producer's partial/complete status, nullable
-reported byte total, and observed UTF-16 length. Text and duplicate raw calls
-remain in the original record, rather than being rewritten under its ID.
-
-Use `inspect_analysis_view` with the parent's ID and
-`view: {kind: "android", facet: "manifest", offset: 0, limit: 4096}` to read exact
-retained decoded text. Follow `coverage.next_offset`; surrogate boundaries use
-the existing text-page implementation. Exhaustion describes the retained text,
-not global completeness when the producer says partial. APK signatures and
-runtime behavior remain unverified. Engine artifact SHA-256 identifies the JAR;
-views require the authenticated APK subject and never substitute the engine
-hash for a missing target identity. Older servers require schema discovery and
-the original complete request; automatic fallback is not introduced.
-
-## Frozen runtime and real SDK pairs
-
-Source runtime: `28c84e78cf2fbfde4aceed345b773c59eb889f68`; later test-only schema
-typing corrections do not relabel these receipts. Compiled dist/bridge file-table
-SHA-256: `5332dda13981f043e146b3601ebec1f380d9f698280ca53d75786b638a912e11`.
-The frozen old runtime is `8bc1601ca51e417ca472d90ea0367e9418a1a0f2`, digest
-`9e7380f537301bf0cfe2926f5619011af848af7c220750e75189498e65d825e1`.
-
-Real NewPipe 0.29.1 bytes, acquisition and digest are pinned in `corpus.json`.
-Actual configured JADX headless MCP 0.7.1/Java runs use the same selected
-provider settings and search-path digests, one worker and 768 MiB Java heap.
-Node is 24.18.0; actual SDK client/server are 2.3.1. Processes and engines are
-fresh per trial; host page caches are not flushed. SDK schema mode is selected
-in both treatments. Heavy runs are serial, with one CPU, unchanged 3 GiB early
-stop/4 GiB hard memory, no swap, and 192 tasks.
-
-All four candidate workflows use three successful public MCP calls. Only the
-first package delivery changes. Both pairs pass settings and selected-fact
-comparison, including all declarations, manifest status/length, engine identity,
-original limitations, matching class rows and onCreate entries. Original replies
-and IDs remain separate. A fresh old-runtime complete workflow also passes
-comparison against the candidate complete request; both complete package replies
-are exactly 119,527 compact client-result JSON bytes. This is scoped compatibility
-evidence, not a guarantee for every historical release/client/host.
-
-| Trial          | Package reply bytes | SDK workflow seconds | Payload CPU seconds | Kernel peak bytes |
-| -------------- | ------------------: | -------------------: | ------------------: | ----------------: |
-| sdk-complete-1 |             119,527 |               24.059 |              25.259 |     1,225,076,736 |
-| sdk-summary-1  |               8,659 |               23.694 |              24.894 |     1,226,870,784 |
-| sdk-summary-2  |               8,659 |               24.407 |              25.611 |     1,228,296,192 |
-| sdk-complete-2 |             119,527 |               24.509 |              25.740 |     1,229,844,480 |
-
-Summary replies are 8,659 bytes, about 92.8% smaller; all three replies together
-fall from 149,577 to 38,709 bytes. This is a delivery result, not a model-token
-or engine-work saving. The SDK timing differences are small. CPU and memory do
-not establish a reduction. No provider setting or analysis scope changes.
-Transport roundtrip includes server/client work and is not an engine-only timer.
-
-The complete catalog is 2,506,213 compact JSON bytes versus 2,497,635 on the old
-runtime: about 0.34% growth, including intervening main changes. Discovery cost
-remains visible alongside selected-delivery savings.
-
-## Authentic old Evidence continuation
-
-A real package record from old runtime 8bc160 imports into the candidate and
-supports retained summary, exact manifest pages, inline portable summary and
-export through actual public SDK tools. The new session explicitly selects an
-absent JADX JAR; this workflow performs no package analysis. Eleven successful
-calls preserve the original record, original ID, all declarations and all 25,222
-manifest UTF-16 units. Manifest UTF-8 SHA-256:
-`fee192fe2a6d7892c22cba115184c74c7e2c42ce464e8bb37be6289f2c16881d`.
-The exported original record is deeply equal to the imported record.
-
-## Actual Codex task outcomes
-
-Four serial trials run in complete/summary/summary/complete order on the same
-frozen candidate. Requested configuration: Codex CLI 0.161.0, `gpt-5.6-terra` high,
-three exact selected tool names and the same optional context/discovery capture
-settings. The requested alias does not certify the server-resolved model. The
-original analyst question is unchanged; equal treatment instructions explicitly
-choose package detail and explain the summary carrier. Temporary configuration
-points to the frozen modified REA MCP; no global configuration is edited.
-
-| Trial            |   Input | Cached | Uncached | Output | Seconds | MCP calls | Usage records | Facts |
-| ---------------- | ------: | -----: | -------: | -----: | ------: | --------: | ------------: | ----- |
-| model-complete-1 |  39,267 | 23,040 |   16,227 |  1,690 |  94.053 |         3 |             3 | Pass  |
-| model-summary-1  | 128,417 | 93,440 |   34,977 |  3,633 | 150.401 |         8 |             9 | Pass  |
-| model-summary-2  |  54,437 | 37,120 |   17,317 |  2,185 | 123.677 |         3 |             4 | Pass  |
-| model-complete-2 |  21,332 |  9,984 |   11,348 |    667 |  20.774 |         0 |             2 | Fail  |
-
-Three answers pass the original selected-fact gate against the actual SDK
-producer. Each trial preserves APK bytes and removes its isolated profile.
-The first summary trial makes five successful calls and three rejected requests:
-an invented `case_sensitive` argument, empty class-search input and empty
-class-inspection input. It then repeats successful package/search work. These
-errors and correction turns remain part of measured task cost; strict existing
-schemas correctly reject them. The second summary trial uses the intended three
-successful calls, but still does not establish improved total/uncached input or
-latency against the factually acceptable first complete control.
-
-The final complete control's first client executor filters `ALL_TOOLS` for the
-same three exact names and receives an empty array. It makes zero MCP calls,
-reports all requested facts unknown and fails the factual gate. Identical name
-filters worked in the other trials. Stderr contains no explanatory error; the
-client visibility failure remains unexplained and is not attributed to REA or
-summary delivery. Its short duration is not comparable completed work. The
-original failed receipt is retained rather than replaced by a successful trial.
-
-These measurements demonstrate no real-model token or speed gain. Smaller raw
-MCP envelopes do not establish smaller model context; observed usage also
-includes discovery, execution context, corrections and extra responses. Usage
-records count captured usage items rather than asserting exact remote request
-contents or equating MCP calls with model rounds. The complete default and
-opt-in choice remain unchanged; this is useful delivery/retention capability,
-not a general performance recommendation.
-
-All model runs have verified payload-completion witnesses with only the observer
-remaining and zero memory/task limit events at that phase. Kernel peaks are
-602,472,448–1,444,945,920 bytes; the failed no-analysis control is included in that
-range and is not evidence of lower analysis memory. Whole-scope final counters
-remain unknown and the existing full resource grader stays false. No broader
-CPU, memory, OS/provider or model claim is made.
-
-## Resource interpretation
-
-Every SDK run and portable continuation has a verified owned
-payload-exited-observer-alive witness, with only the observer remaining and no
-memory/task limit events at that phase. Kernel peak and CPU include that opt-in
-observer. Whole-scope terminal counters remain unknown; the existing complete
-physical resource grader is not changed or called successful. No OOM stress or
-resource-limit increase is used.
-
-## Verification and scope
-
-Twenty-seven relevant converted-schema, SDK, domain and existing Android
-failure/cancellation/cleanup checks pass. A three-case focused rerun passes after
-a test-only schema typing correction. The 1 MiB manifest protocol fixture verifies
-original default/full output, reconstruction after source removal, unchanged
-exported Evidence and one engine launch. Other cases preserve nulls and partial
-status, Unicode boundaries and tagged malformed/missing-identity failures, and
-reject unavailable retention or cancelled requests before provider work. These
-fixtures verify production boundaries; actual JADX claims use the real NewPipe
-runs above. Full supported single-thread compiler and unchanged lint pass under
-the same memory safeguards. No other Android OS/device/provider lane is inferred.
-
-Raw SDK/model replies, private profiles and resource receipts stay outside Git.
-Reproduce SDK pairs using the existing `measure.mjs` with `--artifact newpipe.apk`,
-`--schemas selected`, identical explicit provider configuration and frozen runtime,
-and alternating `--delivery complete` / `--delivery summary`. Preserve failed
-attempts and run `compare.mjs` on both pair orders. Model findings require their
-own identical analyst facts and explicit delivery controls.
@@ -1,117 +0,0 @@
-"""Retain owned Codex tool/usage observations without account or ambient state."""
-
-import hashlib
-import json
-import os
-
-
-def token_counts(value):
-    if not isinstance(value, dict):
-        raise ValueError('Expected a token-count object')
-    result = {}
-    for key in ['input_tokens', 'cached_input_tokens', 'cache_write_input_tokens',
-                'output_tokens', 'reasoning_output_tokens', 'total_tokens']:
-        if key in value:
-            count = value[key]
-            if not isinstance(count, int) or isinstance(count, bool) or count < 0:
-                raise ValueError('Expected nonnegative integer token counts')
-            result[key] = count
-    return result
-
-
-def selected_event(event):
-    """Select observed items; these are not the exact submitted model request."""
-    if not isinstance(event, dict) or not isinstance(event.get('payload'), dict):
-        raise ValueError('Expected an event object with an object payload')
-    if not isinstance(event.get('type'), str):
-        raise ValueError('Expected an event type string')
-    if event.get('timestamp') is not None and not isinstance(event['timestamp'], str):
-        raise ValueError('Expected a timestamp string or omission')
-    payload = event['payload']
-    kind = event.get('type')
-    if kind == 'response_item' and payload.get('type') in [
-        'custom_tool_call', 'custom_tool_call_output',
-        'function_call', 'function_call_output',
-    ]:
-        keys = ['type', 'call_id', 'name', 'input', 'arguments', 'output']
-    elif kind == 'token_usage_record':
-        keys = ['response_id', 'usage', 'turn_token_usage', 'thread_token_usage']
-        payload = {key: token_counts(payload[key]) if key != 'response_id'
-                   else payload[key] for key in keys if key in payload}
-    elif kind == 'event_msg' and payload.get('type') == 'token_count':
-        keys = ['type', 'info']
-        info = payload.get('info')
-        if info is not None:
-            if not isinstance(info, dict):
-                raise ValueError('Expected token-count info')
-            selected_info = {key: token_counts(info[key]) for key in
-                             ['total_token_usage', 'last_token_usage'] if key in info}
-            window = info.get('model_context_window')
-            if 'model_context_window' in info:
-                if window is not None and (not isinstance(window, int) or isinstance(window, bool) or window <= 0):
-                    raise ValueError('Expected a positive model context window')
-                selected_info['model_context_window'] = window
-            payload = {'type': 'token_count', 'info': selected_info}
-        else:
-            payload = {'type': 'token_count', 'info': None}
-    else:
-        return None
-    return {
-        'timestamp': event.get('timestamp'),
-        'type': kind,
-        'payload': {key: payload[key] for key in keys if key in payload},
-    }
-
-
-def capture_tool_context(codex_home, output):
-    """Capture only an explicitly selected trial's rollouts; never its auth/config."""
-    sessions = codex_home / 'sessions'
-    blocked = sessions.is_symlink()
-    sources = [] if blocked else sorted(sessions.rglob('*.jsonl'))
-    target = output / 'codex-tool-context.jsonl'
-    source_receipts = []
-    errors = [{'source': 'sessions', 'reason': 'not_an_owned_directory'}] if blocked else []
-    retained = 0
-    with os.fdopen(os.open(target, os.O_WRONLY | os.O_CREAT | os.O_EXCL, 0o600),
-                   'w', encoding='utf-8') as result:
-        for source in sources:
-            name = source.relative_to(codex_home).as_posix()
-            if source.is_symlink() or not source.is_file():
-                errors.append({'source': name, 'reason': 'not_an_owned_regular_file'})
-                continue
-            digest = hashlib.sha256()
-            counts = {}
-            with source.open('rb') as lines:
-                for ordinal, line in enumerate(lines, 1):
-                    digest.update(line)
-                    try:
-                        event = json.loads(line)
-                        selected = selected_event(event)
-                    except ValueError as error:
-                        errors.append({'source': name, 'line': ordinal,
-                                       'reason': type(error).__name__})
-                        continue
-                    kind = event.get('type')
-                    counts[str(kind)] = counts.get(str(kind), 0) + 1
-                    if selected is not None:
-                        result.write(json.dumps(selected, ensure_ascii=False) + '\n')
-                        retained += 1
-            source_receipts.append({'source': name, 'sha256': digest.hexdigest(),
-                                    'event_counts': counts})
-    retained_digest = hashlib.sha256()
-    with target.open('rb') as captured:
-        for chunk in iter(lambda: captured.read(1024 * 1024), b''):
-            retained_digest.update(chunk)
-    receipt = {
-        'status': 'partial' if errors else 'captured' if source_receipts else 'unavailable',
-        'retained_file': target.name,
-        'retained_sha256': retained_digest.hexdigest(),
-        'retained_events': retained, 'sources': source_receipts, 'errors': errors,
-        'scope': 'Owned client tool-call/reply and per-response usage items, not '
-                 'the exact submitted model request. Session/account metadata, '
-                 'world state, user/developer messages, encrypted reasoning and '
-                 'internal passthrough are omitted. Authentication, configuration '
-                 'and ambient environment are never copied by this capture.',
-    }
-    (output / 'context-receipt.json').write_text(json.dumps(receipt, indent=2) + '\n')
-    return receipt
@@ -24,15 +24,12 @@ const sameSettings = [
  "artifact",
  "artifact_sha256",
  "artifact_sha256_after",
-  "retained_verification",
  "native_question",
  "javascript_question",
-  "managed_question",
  "provider_settings_sha256",
  "provider_search_path_sha256",
  "provider_environment_policy_sha256",
  "measure_source_sha256",
-  "native_workflow_source_sha256",
  "package_lock_sha256",
  "node_version",
  "sdk_client_version",
@@ -43,9 +40,7 @@ const sameSettings = [
 const settingDifferences = sameSettings.filter(
  (key) =>
    !isDeepStrictEqual(left[key], right[key]) ||
-    ((key === "provider_search_path_sha256" ||
-      (key === "native_workflow_source_sha256" &&
-        typeof left.native_question === "string")) &&
+    (key === "provider_search_path_sha256" &&
      !/^[a-f0-9]{64}$/.test(left[key] ?? "")),
 );
 // Producer/view IDs identify different delivery observations; a named recovery
@@ -59,17 +54,6 @@ const facts = (answer) =>
 const a = facts(leftAnswer);
 const b = facts(rightAnswer);
 const runSpecific = [];
-for (const [side, answer] of [
-  ["left", leftAnswer],
-  ["right", rightAnswer],
-]) {
-  if (Object.hasOwn(answer, "evidence_ids"))
-    runSpecific.push({
-      side,
-      path: ["evidence_ids"],
-      value: answer.evidence_ids,
-    });
-}
 // Binwalk assigns a new opaque region UUID in each invocation. Preserve both
 // original lookup values in this report; compare the observed region facts
 // separately. The product and original replies retain those IDs unchanged.
@@ -116,36 +116,6 @@
        "derivation": "selected regular ZIP member ShareX.HelpersLib.dll; no target execution"
      }
    },
-    {
-      "id": "sharex.exe",
-      "file": "ShareX.exe",
-      "bytes": 198656,
-      "sha256": "46af1ccc514b395cb703633abb5a505a771942b7db9b1915f31aeea541b3685f",
-      "provenance": {
-        "project": "ShareX native executable component",
-        "version": "19.0.2",
-        "upstreamFile": "ShareX-19.0.2-portable.zip",
-        "url": "https://github.com/ShareX/ShareX/releases/download/v19.0.2/ShareX-19.0.2-portable.zip",
-        "transport_sha256": "967b5d838df5ce25fb5fd7cbd16f1bd797427e2df16907b022b74a4bc0fb9d54",
-        "transport_bytes": 168796487,
-        "derivation": "selected regular ZIP member ShareX.exe; PE32+ x86-64 with no CLR directory; no target execution"
-      }
-    },
-    {
-      "id": "freedos.edlin.exe",
-      "file": "EDLIN.EXE",
-      "bytes": 31492,
-      "sha256": "96b2b6d543e2d8bdc83e313756444e103339eb5ee2c1229abe3607539b31ad6e",
-      "provenance": {
-        "project": "FreeDOS EDLIN",
-        "version": "2.24",
-        "upstreamFile": "edlin.zip",
-        "url": "https://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/repositories/1.4/base/edlin.zip",
-        "transport_sha256": "9db8a0b50bc4be5c2358cd0fa1fb6fc77342c6d5175a6b1084547c370e428f8a",
-        "transport_bytes": 377009,
-        "derivation": "selected regular ZIP member BIN/EDLIN.EXE; original UPX-compressed DOS MZ; APPINFO/EDLIN.LSM reports version; no execution or unpacking"
-      }
-    },
    {
      "id": "vscode.tree-sitter.wasm",
      "file": "tree-sitter.wasm",
@@ -179,90 +149,6 @@
        "transport_integrity": "sha512-RJFoomET6FajjG511fmQxeBQfU6M24a0aFZPqpid+ttIxanWf1VGytBG0UmsGjt07qmIPJS8U31D+aecuCucsQ==",
        "derivation": "selected regular tar member package/wasm/tree-sitter-css.wasm; no target execution"
      }
-    },
-    {
-      "id": "uniswap-v3.factory.hex",
-      "file": "UniswapV3Factory.runtime.hex",
-      "bytes": 49073,
-      "sha256": "fb152cc9b597ef4e54e9d72e81dd72c202050aae5e98c63df139864274504276",
-      "decoded_bytes": 24535,
-      "decoded_sha256": "95c34fe1e6b26c79ae42800041a3e2bdb6a978d19297cd74001ac6b316a48d8d",
-      "provenance": {
-        "project": "Uniswap v3-core UniswapV3Factory",
-        "version": "1.0.1",
-        "url": "https://registry.npmjs.org/@uniswap/v3-core/-/v3-core-1.0.1.tgz",
-        "transport_bytes": 86371,
-        "transport_sha256": "141b001e2a376fff867cb24e0713b2834095cb1250c13aae263d9a646446d329",
-        "transport_integrity": "sha512-7pVk4hEm00j9tc71Y9+ssYpO6ytkeI0y7WE9P6UcmNzhxPePwyAxImuhVsTqWK9YFvzgtvzJHi64pBl4jUzKMQ==",
-        "archive_member": "package/artifacts/contracts/UniswapV3Factory.sol/UniswapV3Factory.json",
-        "compiler_artifact_bytes": 104076,
-        "compiler_artifact_sha256": "599479f60ebb056804aff7b2d05bdd0830ddbb1fdfaa0b6c62c02294ca7188b0",
-        "derivation": "Parse the exact published Hardhat deployedBytecode field and preserve its original hex carrier with one trailing LF; preserve template placeholders",
-        "authority": "Published compiler runtime template, not a live deployed instance; original placeholders/immutables preserved; no execution or chain lookup",
-        "published_abi_function_count": 7,
-        "deployed_link_references": {},
-        "immutable_references": {
-          "recorded": false,
-          "value": null
-        },
-        "immutable_scope": "Published Hardhat artifact does not record an immutable-reference map; absence is unknown, not proof of no immutables. Runtime template bytes remain exact."
-      }
-    },
-    {
-      "id": "uniswap-v3.pool.hex",
-      "file": "UniswapV3Pool.runtime.hex",
-      "bytes": 44287,
-      "sha256": "84d90218eb125074383287877cdc564eca3765241e3bf6f6afdd64a922fbed2b",
-      "decoded_bytes": 22142,
-      "decoded_sha256": "3ef71385c2a22b945bead7904f24b25db877de9db51d1401f2f9daea07ea5c0c",
-      "provenance": {
-        "project": "Uniswap v3-core UniswapV3Pool",
-        "version": "1.0.1",
-        "url": "https://registry.npmjs.org/@uniswap/v3-core/-/v3-core-1.0.1.tgz",
-        "transport_bytes": 86371,
-        "transport_sha256": "141b001e2a376fff867cb24e0713b2834095cb1250c13aae263d9a646446d329",
-        "transport_integrity": "sha512-7pVk4hEm00j9tc71Y9+ssYpO6ytkeI0y7WE9P6UcmNzhxPePwyAxImuhVsTqWK9YFvzgtvzJHi64pBl4jUzKMQ==",
-        "archive_member": "package/artifacts/contracts/UniswapV3Pool.sol/UniswapV3Pool.json",
-        "compiler_artifact_bytes": 111557,
-        "compiler_artifact_sha256": "204fb2fa7ad1a639b1df5601f035f9924b064b721b97adf60c7d5d4712643e34",
-        "derivation": "Parse the exact published Hardhat deployedBytecode field and preserve its original hex carrier with one trailing LF; preserve template placeholders",
-        "authority": "Published compiler runtime template, not a live deployed instance; original placeholders/immutables preserved; no execution or chain lookup",
-        "published_abi_function_count": 26,
-        "deployed_link_references": {},
-        "immutable_references": {
-          "recorded": false,
-          "value": null
-        },
-        "immutable_scope": "Published Hardhat artifact does not record an immutable-reference map; absence is unknown, not proof of no immutables. Runtime template bytes remain exact."
-      }
-    },
-    {
-      "id": "localsend-arm64.apk",
-      "file": "LocalSend-1.18.2-android-arm64v8.apk",
-      "bytes": 46558706,
-      "sha256": "82ec3568fba2aa5295b9aae8b76f701d7a4703d86b9f8bad749472038fbaeab3",
-      "provenance": {
-        "project": "LocalSend",
-        "version": "1.18.2",
-        "upstreamFile": "LocalSend-1.18.2-android-arm64v8.apk",
-        "url": "https://github.com/localsend/localsend/releases/download/v1.18.2/LocalSend-1.18.2-android-arm64v8.apk",
-        "transport_sha256": "82ec3568fba2aa5295b9aae8b76f701d7a4703d86b9f8bad749472038fbaeab3",
-        "transport_bytes": 46558706,
-        "derivation": "Official arm64 release APK, compared with GitHub release asset digest; byte-only analysis without execution"
-      }
-    },
-    {
-      "id": "qgis-world-map.gpkg",
-      "file": "qgis-world-map.gpkg",
-      "bytes": 12914688,
-      "sha256": "01d293159d1b77bd9212b5252587853f61aa9e25b2387135f34afaba8d057190",
-      "provenance": {
-        "project": "QGIS bundled world map",
-        "source_commit": "e1223b8e9e71fc50ee995ed556f711c54ccc101b",
-        "git_blob_sha1": "c9ff80228dff0de93c9acdef16a97545ba360244",
-        "url": "https://raw.githubusercontent.com/qgis/QGIS/e1223b8e9e71fc50ee995ed556f711c54ccc101b/resources/data/world_map.gpkg",
-        "derivation": "unmodified official resource file; streaming Git blob and SHA-256 verification"
-      }
    }
  ]
 }
@@ -1,218 +0,0 @@
-# EVM descriptor and real-template checkpoint
-
-Continues [#2016](https://github.com/morluto/rea/issues/2016) after the native
-checkpoint merged. The internal descriptor binds the existing exact EVM
-contract, CLI name and typed service lifetime. Existing complete inputs, output,
-provider selection and cleanup remain the baseline. Wiring alone does not establish
-token or latency savings.
-
-The descriptor contains only the named contract, existing CLI name and existing
-factory. The legacy `createEvmInterfaceService` export remains usable. The MCP
-host selects one complete service instance, preserves injection identity, passes
-that same instance to registration and retains it for cleanup/retry. No bound
-service wrapper, generic registry, automatic dependency acquisition or new pack
-selection is introduced.
-
-Five actual in-memory SDK boundary scenarios verify converted schemas, duplicate
-registration rejection before use, malformed inputs, explicit unavailable or
-incompatible-output failures with a healthy WASM peer, cleanup retry, and request
-cancellation followed by recovery. Their injected ports are recording seams, not
-real EVMole/WABT claims. Nine service and 26 provider-boundary cases also pass;
-two unsupported-host scenarios are skipped on this Linux host. The existing seven
-WASM MCP scenarios pass. Full `npm run check` passes; its approximately 3 GiB
-sampled peak and `memory.high` events are excluded from performance claims.
-Candidate real-artifact/catalog and model observations are recorded below.
-
-## Public inputs and independent checks
-
-[corpus.json](corpus.json) retains the original WETH historical example and adds
-Uniswap v3-core 1.0.1 Factory/Pool compiler runtime templates from the official npm
-package. Archive integrity, exact regular member, compiler JSON, original carrier
-and decoded-byte digests are pinned. The carrier is the original `deployedBytecode`
-field plus one trailing LF. No placeholder is rewritten and no contract is executed.
-
-These are compiler templates, not live deployed instances. Their published Hardhat
-artifacts omit immutable-reference maps; that metadata remains explicitly unknown.
-The recorded empty link-reference maps do not establish absence of immutables.
-WETH remains a published historical RPC example, with unknown live authenticity.
-
-Actual control CLI observations infer 7 Factory and 26 Pool functions. The
-[independent verifier](verify-evm-template.mjs) hashes each canonical published ABI
-signature with caller-supplied Ethereum Keccak and checks the complete ABI-dispatch
-selector multiset against the original REA response. Both sets match. This does not
-establish inferred argument/mutability equivalence, deployment authenticity or
-runtime semantics; all producer unknowns remain visible.
-
-## Latest-main control
-
-Production control: `1770f38cfc6cbe87491d0de8b8730c305c5cf8ea`, Node 24.18.0,
-npm 11.16.0, matching locked dependencies and unchanged EVMole 0.9.3.
-The frozen `dist/`/`bridge/` file-table SHA-256 is
-`7fd6c2c37b4e166df158ec29d48d31f3712b9b087d9807ee019ee997d06ea144`.
-Measurement driver SHA-256 is
-`f767c0c0232be1e11918e70e3197a6919680d16688076bef28d4320662f712f7`.
-Each public SDK run validates the selected named advertised schema and verifies
-original carrier and decoded identities, inference/unknown scope and unchanged
-input bytes. All three runs return the same complete 2,420,709-byte catalog.
-
-| Question                 | Inferred functions | SDK tool-result JSON bytes | First workflow seconds |
-| ------------------------ | -----------------: | -------------------------: | ---------------------: |
-| WETH historical carrier  |                 11 |                     26,760 |                 11.432 |
-| Uniswap Factory template |                  7 |                    110,424 |                  3.628 |
-| Uniswap Pool template    |                 26 |                    110,998 |                 11.211 |
-
-These are initial observations, not paired performance conclusions or model-token
-counts. Each workflow includes connection, complete catalog discovery and one
-interface query. Full bytecode remains inline. Candidate/control repetitions must
-use the same source driver, inputs, provider settings and Node/worker limits.
-
-Preparation against earlier frozen main `b1bf4a70d44191348ca20a91a52fb663da4daed0`
-also passed all 59 cases of the existing real CLI/MCP EVM verifier with privately
-supplied solc 0.8.30 and strace 6.1. Those cases cover compiler configurations,
-raw/hex identity, malformed/unsupported carriers, missing limiter and resource
-constraints. Its measured scope took 233.1 seconds, sampled peak 1,192,730,624
-bytes and last-observed CPU 181.018 seconds. This is a control, not candidate proof.
-
-All heavy runs are serial under one CPU, 4 GiB hard memory/3 GiB early-stop, no swap
-and bounded tasks. Final cgroup counters disappear at scope teardown and remain
-unverified; last-observed zero limit events are not substituted for final counters.
-Raw replies, tools, compiler artifacts and detailed receipts remain outside Git.
-
-## Reproduction
-
-Build and freeze each pinned runtime using the repository toolchain, then run
-`measure.mjs --artifact uniswap-v3.factory.hex` or `uniswap-v3.pool.hex` with the
-exact derived carrier, `--schemas selected`, explicit runtime/revision and a fresh
-private output directory. Existing `weth.hex` answer fields and invocation remain
-unchanged. The same common workflow verifies all three offline carriers.
-
-Run `verify-evm-template.mjs` with `--artifact` selecting the corpus ID,
-`--artifact-json` selecting its original published compiler JSON, `--evidence`
-selecting the recorded CLI Evidence or SDK structured reply, `--keccak-module`
-selecting the absolute `js-sha3/src/sha3.js` module from the private solc toolchain,
-and `--output` selecting a new private receipt. It acquires no dependencies and
-does not overwrite an existing receipt.
-
-The [template model question](questions/evm-uniswap.txt) requires the same complete
-inferred interface facts and explicit unknowns. An ABI-count match is not used as
-a model grade.
-
-## Candidate compatibility and real-provider verification
-
-Candidate: `152984da771450048ee9d60db8a410994a125878`, frozen runtime file-table
-SHA-256 `725563640c27eb50ddb6f977d2dfbe1bdaddf7e05c02897318bceaa36fa602d7`.
-Two repetitions for each EVM input produce six passing paired fact/settings
-comparisons with the same driver and explicit limits. Each report preserves both
-original Evidence reference maps. The complete actual SDK catalog is byte-identical
-on every pair, including order, names, descriptions, schemas and annotations;
-catalog SHA-256 is
-`8664e42fd5225645cfd910f440f731c67ac198d3d53aa85b5c485374c74cf603`.
-Result byte counts remain unchanged. Candidate Factory/Pool selectors also match
-the independent published ABI oracle.
-
-| Question | Control seconds, repetitions 1 / 2 | Candidate seconds, repetitions 1 / 2 |
-| -------- | ---------------------------------: | -----------------------------------: |
-| Factory  |                      3.628 / 3.650 |                        3.708 / 3.605 |
-| Pool     |                     11.211 / 3.591 |                        3.749 / 3.581 |
-| WETH     |                     11.432 / 3.694 |                        3.572 / 3.677 |
-
-First controls preceded wiring; each second pair ran candidate then control.
-Every measurement starts a new MCP process; host cache/page state is not fully
-controlled. Slower initial controls do not establish a descriptor speedup.
-Second-pair latency and last-observed CPU are similar. Sampled EVM SDK family peaks
-range from 510,255,104 to 527,622,144 bytes. No scope abort occurred; final counters
-remain unknown, so these measurements are descriptive.
-
-The candidate passes all 59 existing real CLI/MCP verifier cases with solc 0.8.30
-and unchanged EVMole 0.9.3. Actual syscall traces report target execution and network
-sockets absent for those scenarios, and the verifier reports no remaining
-descendants. The scope took 177.456 seconds, sampled peak 1,237,020,672 bytes and
-last-observed CPU 144.913 seconds. Different totals from the earlier control are
-not attributed to unchanged provider algorithms.
-
-Post-descriptor public MCP regression uses the original pinned shipped corpus:
-
-| Domain / selected question                  | Actual provider / scope                            | Calls | Seconds |
-| ------------------------------------------- | -------------------------------------------------- | ----: | ------: |
-| SQLite WASM counts / exports                | WABT 1.0.42; selected summary and retained read    |     2 |   5.516 |
-| ShareX managed metadata / native boundaries | Static PE/CLI, no assembly execution               |     2 |   3.710 |
-| Obsidian manifest / inventory               | Complete inventory retained, no AST claim          |     4 |   5.376 |
-| NewPipe package / MainActivity methods      | Real headless JADX 0.7.1                           |     3 |  21.669 |
-| OpenWrt regions                             | Real firmware signature scan, no device execution  |     1 |   3.581 |
-| jq native entry                             | Ghidra 12.1.4, default analysis, ephemeral Program |     4 | 270.986 |
-
-All six workflows pass named SDK output validation and original digest checks;
-input bytes remain unchanged. Maximum sampled family peak is 1,284,648,960 bytes.
-They establish those available Linux workflows, not paired performance or
-Windows/macOS, IDA/Hopper, Android-device, DOS COM, browser or JavaScript AST
-behavior. Browser/AST were not repeated for this narrow migration.
-
-## Real model complete-output calibration
-
-Six serial Codex CLI 0.161.0 trials request `gpt-5.6-terra`, high reasoning, with
-isolated temporary profiles pointing to the frozen candidate. Resolved server-side
-model identity is not inferred. Only the EVM inspection tool is enabled, matching
-the earlier WETH calibration; this is not full-catalog tool selection verification.
-Every trial makes one successful call and no failed call.
-
-| Trial     | Total input | Uncached input | Output | Seconds |
-| --------- | ----------: | -------------: | -----: | ------: |
-| Factory 1 |      66,158 |         36,974 |  1,329 |  43.483 |
-| Pool 1    |      65,600 |         36,416 |  2,307 |  69.546 |
-| WETH 1    |      54,700 |         25,516 |  1,144 |  56.372 |
-| Factory 2 |      65,964 |         36,780 |  1,453 |  26.412 |
-| Pool 2    |      65,753 |         36,569 |  1,939 |  74.706 |
-| WETH 2    |      54,502 |         25,318 |  1,208 |  35.137 |
-
-Every trial reports 29,184 cached input tokens. Selected fact/reference/lifecycle
-grades all pass: original/decoded identities, every inferred selector, offset,
-dispatch, argument/mutability string including null, explicit unknowns, no runtime
-execution, observed Evidence references, unchanged bytes and removed profiles.
-Raw transcripts and grades remain private. Sampled peaks are
-594,853,888–776,335,360 bytes; last-observed CPU is 6.181–7.034 seconds. Strict
-overall grades remain unverified because final resource counters are unknown;
-they are not relabeled as wholly passing resource-qualified runs.
-
-This calibrates the current complete path after compatible wiring, not a paired
-model performance experiment. The next token experiment should answer the same
-interface question through an explicitly selected precise view, retain full
-bytecode/original Evidence under the existing lifetime, and preserve complete
-defaults. Discover support before sending new options to an older server. Include
-discovery, follow-up, failures and retries in the complete task cost.
-
-## Static contract admission verification
-
-The follow-up from main `c462a4ebd3a10e59253bcf38353a0914b176738b` tests the
-pilot's actual static boundary, without adding a dynamic module registry or
-changing production code. Complete-project TypeScript checking now verifies
-that the inferred descriptor type rejects a WASM operation contract, a WASM
-CLI command, a WASM service factory, an unrelated input schema and an unrelated
-output schema. These are negative assignability assertions: their guarantee
-comes from the compiler, not from executing an incompatible descriptor.
-The existing named contract and CLI identity are also checked at runtime;
-separate factory calls produce distinct service/provider owners. Invalid target
-input remains an application error without launching a worker.
-
-The actual public in-memory MCP SDK test additionally spies on the provider:
-duplicate EVM registration throws the named `already registered` error before
-any provider call. Converted input/output JSON Schemas validate before the
-first valid operation. Invalid client arguments are rejected before execution;
-incompatible provider reply data is validated **after** execution and is not
-presented as a pre-use contract guarantee. Existing healthy-peer, cancellation,
-retained summary/default and cleanup-retry scenarios remain covered.
-
-Full project typecheck passes with the installed compiler's supported single
-thread scheduling; it includes all source/test files. The two exact focused
-files pass 12 runtime cases. The resource scopes sample 2,057,961,472 bytes for
-typecheck and 2,426,290,176 bytes for required build plus focused tests, below the
-unchanged 3 GiB early-stop/4 GiB hard ceiling. Final transient-cgroup counters
-remain unknown. No new real-provider or performance improvement is claimed by
-these compile/SDK checks; the earlier pinned real EVMole/WABT/lifecycle evidence
-retains its original scope and source identity.
-
-This proves the one statically composed descriptor's named/schema/factory
-compatibility and duplicate-registration guard. It does not implement runtime
-admission of arbitrary JavaScript descriptors, third-party plugin ABI/version
-negotiation or a general plugin SDK. Those remain deferred by the original plan.
-Existing callers, full defaults, provider inputs, owned lifetimes and output
-identities are unchanged.
@@ -1,208 +0,0 @@
-# EVM interface delivery and migration checkpoint
-
-Continues [#2016](https://github.com/morluto/rea/issues/2016) after the static
-descriptor merged in [#2261](https://github.com/morluto/rea/pull/2261). Opt-in
-`inspect_evm_interface` MCP `detail: "summary"` returns every inferred interface
-candidate without bytecode hex or duplicate stdout. Complete Evidence remains
-retained under its original identity. Delivery bytes fall; the measured model
-cohort does **not** establish a stable token or task-time improvement.
-
-## Frozen scope
-
-Control production is `ad08510a113d7a9b8d92fb1e385757880e469869`; candidate
-production is `32c7548b9ae5c8cda348653d177b1747127c74ba`. Their compiled file-table
-SHA-256 values are respectively
-`f68e85030cb05082520ea9f0d7650298ae316ce7bba59a8942e0cc1318ae9850` and
-`978b3a014e3b2a1e1c6620364dcd793fa7cb40f19892d44cfb0312739a8c14a3`.
-The SDK driver SHA-256 is
-`a95d8d8e9f72c0b2b885c61907ed13054ebf7d1642f6f13b0126163840b1221a`.
-Driver commit `03bff83e70e09a917341c1fe3ebffbfdc67785c5` fixes only reading the
-public `get_evidence_bundle.result.records` envelope; production is unchanged.
-Both runtimes use Node 24.18.0, matching locked dependencies, SDK client/server
-2.3.1 and unchanged bundled EVMole 0.9.3.
-
-Inputs are the digest-pinned WETH historical hex carrier and Uniswap v3-core
-1.0.1 Factory/Pool compiler runtime templates in [corpus.json](corpus.json).
-Original carrier and decoded-byte identities remain distinct. Templates are
-not authenticated deployed instances; constructor-dependent values and absent
-immutable-reference metadata stay unknown. No chain, target execution or
-signature lookup is introduced.
-
-## Public SDK pairs
-
-Two pairs per artifact run serially: complete control then selected candidate,
-followed by candidate then control. Each starts a fresh MCP process, discovers
-the catalog and validates the actual named advertised schema. Host caches are
-not independently controlled. All six fact/settings comparisons pass. Both
-answer projections omit unrequested hex; original complete replies remain intact.
-
-| Input   | Complete / summary result bytes | Reduction | Control seconds, 1 / 2 | Candidate seconds, 1 / 2 |
-| ------- | ------------------------------: | --------: | ---------------------: | -----------------------: |
-| Factory |                110,424 / 14,442 |    86.92% |          3.670 / 3.766 |            3.664 / 3.867 |
-| Pool    |                110,998 / 19,922 |    82.05% |          4.110 / 3.740 |            3.977 / 3.870 |
-| WETH    |                 26,760 / 15,378 |    42.53% |          3.671 / 3.710 |            3.930 / 3.673 |
-
-These measurements support smaller delivery, not faster interpretation. Analysis
-still runs and the full parent still incurs producer/retention costs. Catalog
-count and order stay at 184 tools. The complete catalog grows from 2,422,229 to
-2,429,938 compact JSON bytes (+7,709); all name/description/input definitions
-grow from 512,655 to 514,074 bytes. The EVM input definition grows from 1,443 to
-2,029 bytes. Only `inspect_analysis_view` and `inspect_evm_interface` definitions
-change. These discovery costs are visible and are not converted into token counts.
-
-Nine separate measurements verify new-server complete defaults, old-server
-summary fallback and retained reads for all three inputs. The four-call retained
-proofs retrieve the complete canonical parent plus pages and cost 160,110,
-177,106 and 79,160 bytes for Factory, Pool and WETH respectively. They are
-verification workflows, not examples of one-call delivery savings.
-
-## Real Codex pairs and answer qualification
-
-Twelve serial Codex CLI 0.161.0 trials use the existing identical questions for
-each pair, the same artifact path, one enabled EVM tool, temporary MCP profiles
-and requested `gpt-5.6-terra` high. The requested alias is not proof of the
-resolved model identity. Trials include schema discovery, reasoning, one actual
-successful EVM call and final answer. No call fails or retries. Profiles are
-removed and input bytes remain unchanged. This fixed one-tool profile does not
-test selection from the full catalog.
-
-| Input / repetition | Uncached input, control → candidate | Seconds, control → candidate | Candidate delivery |
-| ------------------ | ----------------------------------: | ---------------------------: | ------------------ |
-| Factory / 1        |                     22,901 → 25,668 |              52.485 → 48.768 | summary            |
-| Factory / 2        |                     37,181 → 15,270 |              53.404 → 45.345 | summary            |
-| Pool / 1           |                     36,652 → 26,657 |              57.764 → 66.642 | summary            |
-| Pool / 2           |                     28,305 → 36,259 |              62.068 → 71.756 | complete           |
-| WETH / 1           |                     21,128 → 25,187 |              44.869 → 46.809 | summary            |
-| WETH / 2           |                     17,417 → 17,529 |              30.364 → 39.943 | summary            |
-
-Keep all trials, including the candidate that explicitly chose complete delivery.
-Five of six candidates select summary, but uncached input improves in only two
-pairs and time improves in only two. Aggregate control → candidate observations
-are 362,496 → 357,770 total input; 198,912 → 211,200 cached input;
-163,584 → 146,570 uncached input; 8,953 → 10,397 output; and
-300.954 → 319.263 seconds. Cache state and model/service variation are not
-separated; the aggregate does not establish a repeatable saving for an individual
-question or a qualified performance recommendation.
-
-Every answer passes exact core-field checks: both identities/byte counts, every
-function selector/offset/dispatch/argument/mutability including null, inference,
-unknown completeness/kind/hardfork/authenticity, and absent runtime execution.
-All reported IDs occur in actual responses. However, the existing grader requires
-the final limitation list to equal the producer list verbatim and in order.
-Only three trials pass that additional check; nine fail. The questions request
-preserving limitations but do not explicitly request a verbatim ordered list.
-Four failures contain all original strings with extra correct scope statements
-or different ordering. The other five paraphrase or omit source caveats, including
-worker or upstream-metadata limitations. Do not silently waive those omissions
-or turn these into twelve fully acceptable answers. The strict reports and
-original transcripts remain intact; core-field success is a narrower result.
-
-Model scope sampled peaks range from 562.5 to 710.5 MiB, with last-observed CPU
-5.945–6.878 seconds. CPU includes the local process family, not remote model
-computation. All heavy jobs use one CPU, a 4 GiB hard limit, 3 GiB early-stop,
-no swap and 192 tasks. No scope abort occurs in this cohort. Final cgroup
-counters are unavailable after teardown: final OOM/task/limit-event assertions
-remain **unverified**. Last-observed counters are not substituted for final ones.
-Consequently neither strict answer acceptance nor resource-qualified performance
-success is claimed for the whole cohort.
-
-## Existing-user compatibility
-
-Omitted and explicit-complete MCP requests, the existing CLI and provider inputs
-preserve their full behavior. `detail` is removed before the unchanged provider
-input; original full Evidence parameters, raw result and identity are retained.
-Summary receives its own identity linked to that parent. All candidate facts,
-original report limitations, stderr/truncation and explicit unknowns stay inline.
-Complete-within-view candidate coverage is not global discovery completeness.
-Function pages retain original order; text pages use UTF-16 code units, with
-hex characters distinguished from decoded-byte function offsets.
-
-Actual new default replies for all three artifacts validate against the frozen
-old advertised input/output schemas, and structured/text payloads agree. Older
-servers reject neither request nor unsupported fields because the experimental
-client discovers support before selecting summary and otherwise calls complete.
-This is an explicit client fallback, not universal server forward compatibility.
-
-Three authentic old-runtime records and old-created canonical bundles pass new
-MCP import, retained summary, CLI inline summary and export. Original records,
-IDs and bundle source bytes stay deeply equal. The reproducible verifier below
-also checks function/hex pages with the analysis limiter explicitly unavailable,
-so retained reads cannot silently start successful producer analysis. This
-proves the pinned old/new Linux workflows, not every historical client release.
-
-The initial retained experiment failed because its driver read the bundle's
-wrong envelope. Correcting that consumer produced passing retained proofs; the
-failed receipt stays archived and is not recorded as a REA defect. Separately,
-one static-check attempt hit the unchanged 3 GiB early-stop. The bounded retry
-passes with Node heap 512 MiB/native checker memory controls; its roughly 3 GiB
-peak and soft-limit events are excluded from efficiency comparisons.
-
-## Reproduction and checks
-
-Use [the shared instructions](README.md), explicit frozen revisions/runtimes and
-fresh private output directories. Run `measure.mjs` for `weth.hex`,
-`uniswap-v3.factory.hex` and `uniswap-v3.pool.hex`, with `--schemas selected` and
-paired `--delivery complete` / `summary`; run `compare.mjs` on equivalent pairs.
-Add `--verify-retained` only for the separate four-call proof. Use the unchanged
-[WETH](questions/evm.txt) or [template](questions/evm-uniswap.txt) question and the
-same one-tool profile for `agent-trial.py`, preserving all usage and grader results.
-
-Export complete Evidence with the old runtime's public ledger workflow, then run:
-
-```sh
-node experiments/analysis-efficiency/verify-evm-retention.mjs \
-  --runtime-root ABS_FROZEN_NEW_RUNTIME --revision NEW_SHA \
-  --bundle ABS_OLD_BUNDLE_JSON --output NEW_PRIVATE_ABS_DIR
-```
-
-The script acquires no dependencies and preserves the old bundle. Revision is
-caller-supplied; retain the frozen file-table receipt alongside it. Raw JSON,
-transcripts, profiles, bytecode, compiler inputs and generated artifacts stay
-outside Git. This checkpoint adds source verification and curated observations.
-
-The production change passes 64 focused EVM/WASM/generic-view/domain/service
-checks and full static/docs gates. Recording provider seams establish exact
-schemas, old defaults, inference/null preservation, historical identity failures,
-peer availability, cancellation and cleanup retry; they are not real-provider
-claims. Real-provider and shared-domain checks are recorded separately.
-
-The same frozen candidate also passes six actual public MCP artifact workflows:
-SQLite WASM with WABT summary, ShareX managed metadata, Obsidian inventory,
-NewPipe with JADX, an OpenWrt region inspection, and jq entry analysis with
-Ghidra. These are shared-contract regressions; they do not establish AST analysis
-of all Obsidian code, full firmware reconstruction, browser coverage, or new token
-savings in those domains. Native Windows PE and DOS coverage remains at the
-[earlier native checkpoint](native-entry-views.md), not a new Ghidra/Windows claim.
-The source retention verifier passes for all three authentic old EVM bundles,
-including exact summaries, function/hex pages, CLI inline views and unchanged
-exported originals with the limiter explicitly unavailable.
-
-The frozen candidate passes all 59 existing real EVM CLI/MCP verifier cases with
-caller-supplied solc 0.8.30 and strace 6.1, including malformed/unsupported
-carriers, unavailable limiter and capacity failures. Its scope takes 96.076
-seconds with 1,345,052,672 sampled peak bytes and 95.130 last-observed CPU seconds.
-This is regression evidence, not an interpreter speedup comparison; final
-resource counters remain unverified. Fresh fast static and generated-document
-checks also pass after adding the migration verifier and this report.
-
-## Latest-main integration
-
-The branch rebases without conflict onto main
-`0043d9b134c0a353e8bf85c0bde4492275f1f720`. Production integration commit
-`3766749316c345ccb594b1b748747b1af9582b34` preserves the same EVM projection,
-provider and delivery semantics; intervening main adds unrelated capabilities.
-The above performance cohort stays pinned to its original frozen runtimes and
-is not relabeled as a measurement of the larger integrated catalog.
-
-At `cda794fb9d4a5ca2bd661853a899d579fb8a47b2`, all 30 affected EVM/WASM/generic-view
-MCP tests pass again, as do full `npm run check` and `npm run docs:check`. A fresh
-real Factory SDK selected-summary/retained-parent/page workflow and the original
-Pool bundle's SDK/CLI migration verifier also pass against the rebuilt integrated
-runtime. The latter still has an explicitly unavailable analysis limiter.
-
-The initial integrated static-check scope stops at 3,221,446,656 sampled bytes,
-just above the unchanged 3 GiB early-stop. Running the same typecheck through
-its single Turbo task with less launcher overhead passes at 3,219,353,600 sampled
-bytes; the subsequent full gate uses that valid cached typecheck and passes.
-No memory threshold or check requirement is relaxed. Preserve both receipts;
-these near-limit validation jobs are excluded from efficiency conclusions.
@@ -1,159 +0,0 @@
-# EVM descriptor lifecycle acceptance
-
-Continues [#2016](https://github.com/morluto/rea/issues/2016) after
-[#2349](https://github.com/morluto/rea/pull/2349) merged. The
-[public verifier](verify-evm-lifecycle.mjs) exercises actual compiled CLI and
-stdio MCP workflows with unchanged EVMole 0.9.3/WASM. This increment adds
-verification only; production contracts, factories, algorithms and defaults
-remain unchanged. It does not introduce a plugin SDK or database cache.
-
-## Runtime and public artifacts
-
-The verified runtime is explicitly frozen from
-`67f817e3653efad35f7044e68fbd6f163b86864b`, built with Node 24.18.0 and the
-matching locked dependencies. Its `dist/` and `bridge/` file-table SHA-256 is
-`cf03167870ac9def929cfaab536d6bd791089031660d1b35bff20672ac07cbbf`.
-The table is checked again after each workflow; source and target bytes must
-remain unchanged before a success receipt is published.
-
-Inputs are the digest-pinned [corpus](corpus.json): published historical WETH
-and official Uniswap v3-core 1.0.1 Factory/Pool compiler runtime templates.
-They are not independently authenticated live deployments. Their deployment,
-hardfork, immutable-reference and inferred-interface limitations remain as
-recorded in [the descriptor checkpoint](evm-descriptor.md). The healthy peer
-is the shipped SQLite WASM 3.53.4-build1 module, inspected by real WABT 1.0.42.
-No contract, native target, chain/RPC query or transaction is executed.
-
-## Actual cancellation and retained cleanup
-
-The verifier supplies a private test launcher through the existing explicit
-`REA_EVM_PRLIMIT_COMMAND` setting. It passes the original arguments to real
-`/usr/bin/prlimit`, runs the unchanged Node/EVMole worker, then briefly gates
-launcher completion after that worker exits and writes its complete reply.
-This controls a real lifecycle boundary without replacing the analysis engine.
-It adds process overhead and is not a performance comparison.
-
-Before cancellation or permission changes, production inspection primitives
-verify the live launcher's run token, parent/group relationship and native
-start identity. The complete worker reply must match the original selected
-bytecode and producer facts. Filesystem changes apply only to the verified,
-non-root user's temporary runtime directory.
-
-Three scenarios are verified:
-
- **Late cancellation:** the real worker has completed, while the public SDK
-  request remains pending. SDK cancellation reports `REQUEST_TIMEOUT` locally;
-  token sweeps and directory removal independently confirm provider cleanup.
-  A subsequent complete request returns identical analysis facts.
- **Successful analysis followed by cleanup failure:** removing write permission
-  produces actual `EACCES`. MCP reports `cleanup_incomplete` and retains the
-  original resource path. A retry before permission repair fails on that same
-  resource. Real SQLite WASM analysis still succeeds. Restoring permission lets
-  the provider retire the old resource and perform a fresh complete EVM query.
- **Format failure followed by cleanup failure:** a deliberately malformed
-  odd-nibble carrier reaches the unchanged worker. The cleanup error preserves
-  its original `invalid_input` category and exact producer diagnostic rather
-  than overwriting the failure. The same repair/retry and healthy-peer checks
-  succeed.
-
-The existing CLI `inspect-evm-interface PATH hex --json` produces the same
-complete normalized facts, parameters and subject as MCP. Fresh Evidence IDs
-are not equated. Final verifier lineage is checked after client/transport close;
-an empty descendant list is a point-in-time observation, not proof that the
-workflow never launched children. Cleanup callbacks always run and preserve
-verification and cleanup failures together.
-
-This proves cancellation after actual analysis, not interruption inside
-EVMole's synchronous WASM computation. Server-shutdown cleanup retry still has
-the separately labeled injected-owner SDK tests from the descriptor checkpoint.
-These Linux x64 observations do not establish Windows/macOS provider behavior.
-Earlier real CLI/MCP malformed/unavailable/capacity checks remain linked in the
-descriptor checkpoint; they are not silently rerun or attributed to this script.
-
-## Measurements and compatibility scope
-
-Initial three-carrier verifier source SHA-256 is
-`2fec069b53324ef82070d323b26dd613b6da0caa7f18100adbeb39b045cf98dc`.
-All three carriers pass all three scenarios and CLI parity with this same source.
-
-| Carrier | Seconds | Sampled peak family bytes | Last-observed CPU seconds |
-| ------- | ------: | ------------------------: | ------------------------: |
-| WETH    |  25.595 |             1,116,884,992 |                    23.926 |
-| Factory |  23.979 |             1,132,994,560 |                    23.419 |
-| Pool    |  24.589 |             1,141,415,936 |                    24.043 |
-
-Runs are serial under the existing one-CPU quota, 4 GiB hard memory, unchanged
-3 GiB early-stop, no swap and 192-task ceiling. Resource receipts, complete
-producer replies, derived malformed input, launcher and runtime copies stay in
-the private lab outside Git. Final cgroup counters disappear at scope teardown
-and remain unknown; sampled zero events do not prove final no-OOM/no-limit
-results. This is compatibility and recovery evidence, not a model-token,
-whole-task latency or CPU saving claim.
-
-Latest main `81cca2e0e3ebd98c21f41d7ad63d6a00e4cbc3f9` could not build during
-setup: its shared partial-error handler passes three arguments to an interface
-requiring four. Independently completed main CI at
-`fdd8f826023c568937d237c2f97d855de283a9b8` reports the same TypeScript failure
-([run 38309578208](https://github.com/morluto/rea/actions/runs/38309578208)).
-The unrelated regression is recorded in the maintainer-requested private bug
-handoff; this change does not repair it. The maintainer independently corrected
-the producing caller in main `8fc2043eb8bcedbf34dce064f977e455438635d6`.
-The frozen-runtime observations above remain pinned to their original revision;
-synchronizing the branch does not relabel them as latest-main verification.
-
-After rebasing, a fresh build and all 10 focused EVM MCP boundary tests pass.
-The same unchanged source verifier also passes all three real Factory scenarios,
-CLI parity, healthy SQLite WASM checks and final cleanup on the newly built
-runtime `b3eadf147221a2fa997ac26667a183ca5bccb1f4` (parent is corrected main
-`8fc2043eb8bcedbf34dce064f977e455438635d6`). Its `dist/`/`bridge/` file-table
-SHA-256 is `7a4cec0fa4f7e929356b50a6b13472f80bd6f526221e427125370cca3ef98d00`.
-This related rerun takes 24.285 seconds, samples 1,146,167,296 peak family bytes
-and records 23.662 last-observed CPU seconds. The older failed build and earlier
-cohort receipts are preserved; wider domain/model matrices are not repeated.
-
-Static composition continues to bind one named canonical contract and one
-typed factory. Existing SDK checks reject duplicate registration before use
-and reject malformed inputs before invoking the provider. Producer contract
-violations are detected when the producer returns a result; they cannot be
-validated in advance without that result. A dynamic third-party module ABI
-preflight is not implemented or claimed. The corresponding broader acceptance
-item remains open rather than creating the deferred generic plugin registry.
-
-## Final launcher review
-
-A missing gate marker while gating is disabled cannot establish absence of a
-new launch. The fixture now appends a launch record before starting the actual
-worker; both permission-failure retries must leave that log byte-identical.
-This independently verifies that retained cleanup failure stops a new EVM
-launch, while preserving the original resource and healthy WASM peer.
-
-Final verifier source SHA-256 is
-`fc9a50e2e54e4c8eede4b8a19283e11ddaa1faadea52eebc390b55b5a1902668`.
-All three related real Factory scenarios, CLI parity and final cleanup pass
-again on the corrected-main runtime: 23.579 seconds, 1,163,685,888 peak sampled
-family bytes and 23.110 last-observed CPU seconds. The earlier three-carrier
-receipts remain pinned to their earlier source; wider artifacts/models are
-not repeated for this review fix.
-
-## Reproduction
-
-Build and freeze the explicit source revision as documented in the measurement
-README. Supply an object of explicit string-valued provider settings, including
-the caller-installed WABT paths. As a non-root Linux x64 user, run under the
-existing resource wrapper:
-
-```bash
-python3 experiments/analysis-efficiency/resource-run.py -- \
-  node experiments/analysis-efficiency/verify-evm-lifecycle.mjs \
-  --runtime-root /absolute/frozen-runtime \
-  --revision 67f817e3653efad35f7044e68fbd6f163b86864b \
-  --path /absolute/UniswapV3Factory.runtime.hex \
-  --peer-path /absolute/sqlite3.wasm \
-  --providers /absolute/explicit-providers.json \
-  --output /absolute/new-private-receipt-directory
-```
-
-The verifier checks the carrier and SQLite module against the committed corpus,
-creates an owner-only receipt directory without overwriting existing receipts,
-and acquires no dependencies. Preserve failed attempts separately. A shorter
-reply or a successful cleanup verifier does not establish an agent-cost gain.
--- a/Show More
+++ b/Show More