Merge main into PR 8089

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

@@ -1,6 +1,6 @@
 ---
 name: rea-tool-design
-description: Audit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.
+description: Design or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.
 ---
 
 # REA tool design
@@ -10,20 +10,6 @@ contract semantics, provider ownership, and discoverability. Inspect the current
 contract and nearest existing tool relevant to the analyst question; source,
 documentation, and live catalogs may describe different versions.
 
-For provider-backed work, exercise the analyst's task through REA and compare
-relevant native provider and independent artifact observations where available.
-Check applicable partial results, recovery and session boundaries; report what
-was not exercised. For failure guidance, follow [design recovery around the
-failure](../../../docs/tool-design.md#design-recovery-around-the-failure).
-Use [workflow verification](../../../docs/testing.md#provider-backed-workflow-verification)
-to select evidence for the proposed contract instead of seeking provider API
-parity.
-
-For an audit, follow [audit existing tools](../../../docs/tool-design.md#audit-existing-tools):
-scope representative tasks, exercise the live workflow, and distinguish
-reproduced bugs, supported limitations, design opportunities and unverified
-claims. Report working alternatives and evidence limits as well as findings.
-
 For a design request, return the proposed boundary, input/result shape, Evidence
 semantics, nearest alternative, and verification approach. Implement when
 requested, preserving the user's scope and existing authorization.

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

@@ -2,7 +2,7 @@
 name: reverse-engineer-anything
 description: Reverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture. 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: "59"
+  version: "55"
 ---
 
 # REA
@@ -377,9 +377,8 @@ unless the group overrides them. The grouped name union is the complete tool
 inventory; use `tools/list` for canonical tool schemas. The default summary keeps
 each provider candidate's availability and target-support status, code and
 reason; `omitted_fields` lists what it leaves out. Request `{"detail": "complete"}`
-only when you need an unavailable candidate's remediation, provider
-diagnostics, candidate capability sets, or tool surface, effect and annotation
-flags; in those closed flag vocabularies, listed
+only when you need provider diagnostics, candidate capability sets, or tool
+surface, effect and annotation flags; in those closed flag vocabularies, listed
 flags are true and omitted known flags are false. Provider candidate facts
 describe possible providers, while top-level session capabilities describe the
 current route and `analysis_provider_binding` names the selected provider. Do
@@ -402,18 +401,9 @@ call `analyze_javascript_application` or `inspect_binary_layout` with
 a flag: its default reply is the summary, and the complete dossier stays
 retained under `parent_evidence_id` for facet paging. Pass that ID as a
 `retained-evidence` reference to `compare_functions`, or inside
-`match_native_functions` `left_observations`/`right_observations` or
-`build_call_path.functions`; request `"detail": "complete"` only when the
-dossier must travel inline.
-Use the same exact-reference form in other advertised logical Evidence inputs,
-including optional sources, arrays and nested sources across domains. Each
-source can independently be inline or retained; preserve its source identity,
-coverage, partial facts and unknowns. A summary or inspection page has its own
-Evidence ID: use `normalized_result.parent_evidence_id` when the consumer needs
-the complete source. For portable CLI follow-ups, commands advertising
-`--evidence-bundle` resolve references from that selected exported bundle.
-See [Evidence composition](references/evidence-workflows.md) for scope and
-recovery; file selectors are supported only where explicitly advertised.
+`match_native_functions` `left_observations`/`right_observations`; request
+`"detail": "complete"` only when the dossier must travel inline, as
+`build_call_path` requires.
 Page module identities and select the returned `node_id` before requesting an
 item; a single file path can represent several graph roles. Do not repeat an
 identical analysis or rejected call without a changed input or resolved blocker.
@@ -432,10 +422,7 @@ output also streams without a single MCP frame.
 When the retained parent ID is unknown, use `get_evidence_bundle` with
 `detail: "summary"` and exact filters for operation, target SHA-256,
 analysis-profile digest or canonical procedure address. Select its returned
-Evidence ID for the next view instead of requesting the complete bundle. When
-that record has no supported view (for example an annotation), read it with
-`detail: "records"` and an `evidence_id` filter; `missing_evidence_links`
-names linked sources this session does not retain.
+Evidence ID for the next view instead of requesting the complete bundle.
 `retention: "complete-record"` means the whole record is stored; native
 value-flow truncation and unknown metadata remain separate. For an exported
 portable bundle, use `rea inspect-evidence-bundle` with JSON containing `path`,
@@ -518,8 +505,4 @@ as complete while required questions remain open.
 Explain findings in plain language and tie them to returned evidence. When the
 user asks to build something, use normal coding tools and separate observed
 behavior from design choices. Close an opened native session with
-`close_binary` when its engine is no longer needed. Evidence references and Unknown
-history remain in memory on the same MCP connection. End the investigation with
-`reset_investigation`; supply `save_path` to checkpoint the complete bundle before
-clearing. Import the saved bundle to restore original references and Unknown
-history in a new process. Retention is bounded and is not automatic persistence.
+`close_binary` when the investigation is complete.

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

@@ -11,44 +11,6 @@ returned inline. When complete `inspect_binary_layout` or
 `inspect_analysis_view` for a summary, one section/symbol/module, or a stable
 page instead of repeating the producer.
 
-For any logical Evidence source that advertises retained references, pass
-`{kind: "retained-evidence", evidence_id}` instead of copying the complete
-record back into a call. The same contract covers individual, optional, array
-and nested sources across native, process, JavaScript, managed, mobile and WASM
-workflows. Sources can independently mix inline records and exact references.
-Resolution preserves the source's identity, provenance, coverage, partial facts
-and unknowns; it neither reruns analysis nor makes incomplete facts complete.
-Keep domain role and identity requirements: a native dossier cannot substitute
-for a managed member observation, for example.
-
-When starting from a summary or inspection page, use its
-`normalized_result.parent_evidence_id` to reference the complete source.
-The view's own `evidence_id` names
-only that view. `compare_artifacts` explicitly supports artifact summary inputs
-and resolves their parents; do not assume every consumer does. When a workflow
-follows source links, keep those linked records available too.
-
-MCP references belong to the current connection's ledger. If the ID is known,
-pass it directly; no discovery call or provider setup is needed. If it is missing,
-import the exported bundle or supply complete inline Evidence. Do not retry an
-unchanged reference or rerun a producer merely to move an existing record.
-Export before closing the session when the source must survive it. For CLI JSON
-workflows that advertise `--evidence-bundle`, the same reference JSON resolves
-against one explicitly selected authenticated bundle:
-
-```bash
-rea trace-application-feature request.json --evidence-bundle /absolute/path/evidence.json --json
-```
-
-This includes JavaScript traces/comparisons and runtime reconciliation, managed
-reconstruction/native verification/graph projection, Android/Apple/Harmony graph
-projection, WASM interface comparison and retained analysis views. The managed
-member comparison CLI still takes two assembly paths; process comparison takes
-two capture Evidence JSON paths. Check command help for the installed version.
-An input bundle grants no implicit file lookup: `evidence-file` and historical
-graph file selectors are accepted only by contracts advertising them. See the
-[CLI reuse guide](https://github.com/morluto/rea/blob/main/docs/cli.md#import-export-and-compare-evidence).
-
 Completed `inspect_artifact` inventory also supports a summary and
 `view: {kind: "inventory", collection: "occurrences", logical_paths: ["package.json", "main.js"]}`.
 Omit `logical_paths` to page all available occurrences; `[]` selects none.
@@ -73,14 +35,6 @@ Parent Evidence ID plus source index preserves same-address
 alternatives. Follow `coverage.next_offset` only as far as the question needs;
 exhausting retained rows does not establish complete program discovery.
 
-`batch_decompile` returns every body unless you select `detail: "summary"` when
-the connected tool advertises it. Use its parent Evidence ID with
-`view: {kind: "batch-decompile", collection: "items"}` for body-free rows and
-exact `where.indices`, `addresses`, `procedure_addresses` or `statuses`. Add
-`include_pseudocode: true` for several chosen bodies, or use
-`collection: "pseudocode"` with one row's `index` to page a large body. Batch
-limitations aggregate every item, so do not attribute them to one successful row.
-
 Use `record_unknown` to track unresolved questions in the user's investigation
 and name the authority or environment still required. Supply supporting and
 contradicting evidence IDs. It updates the session registry directly.
@@ -102,12 +56,11 @@ or absence:
   the complete dossier.
 - `compare_bundles` compares canonical bundle membership and unknown history.
 - `find_changed_behavior` combines existing comparisons; static differences
-  remain candidates, not causal proof. Its `comparisons` accept exact references.
+  remain candidates, not causal proof.
 - `build_call_path` needs explicit function dossiers from one artifact/provider;
-  pass complete parent IDs in `functions`. An incomplete frontier makes absence
-  unknown.
+  an incomplete frontier makes absence unknown.
 - `correlate_static_and_runtime` uses explicit mappings; matching patterns are
-  hypotheses, not causality. Both comparison arrays accept exact references.
+  hypotheses, not causality.
 - `verify_reconstruction` evaluates a finite typed specification. A pass covers
   only declared comparable claims, not global equivalence.
 

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

@@ -169,10 +169,7 @@ leaving it, and `both` when the question needs both. Trace traversal includes
 containment relationships, so even a narrow seed can expand many nodes; a
 bidirectional trace can reach unrelated sibling modules. A module item or page
 is preferable when its observations already answer the question. Do not treat
-all reached nodes as participants in the feature. For a broad trace, pass
-`view: {"kind": "feature-trace", "collection": "paths"}` (or `summary`) to
-retain the complete trace and read terminal paths first; page `nodes` or `edges`
-with exact `where.node_ids` through `inspect_analysis_view` as needed.
+all reached nodes as participants in the feature.
 
 Reuse retained parent Evidence when the server advertises it, or supply complete
 Evidence inline. Include Hopper or Ghidra Evidence only when its artifact digest
@@ -239,19 +236,10 @@ This notation is
 a template: replace it with the actual returned ID. Versions before 4.1.0 accept only full
 inline Evidence. Use the exact ID
 returned by the producer on the same MCP connection. Resolution does not run
-analysis or select a provider; findings remain inline. For summary or inspection
-replies, select the complete `normalized_result.parent_evidence_id`. Native
-observation arrays and runtime reconciliation's `static_layers[].analysis` and
-`runtime_observations[]` also accept exact references where advertised. Each
-source can independently be inline or retained, preserving identity, coverage
-and unknowns. CLI workflows advertising `--evidence-bundle` resolve these inputs
-from the explicitly selected bundle. `close_binary` releases the engine while
-retaining references and complete Unknown history on the same MCP connection.
-`reset_investigation` explicitly clears them; optional `save_path` checkpoints the
-complete bundle before clearing. Import that bundle in another connection to
-restore its original references. Retention is bounded, in-memory and never silently
-evicted; `binary_session.investigation` reports the budget. A missing reference
-includes its ID and recovery guidance.
+analysis or select a provider; findings remain inline. Native observation
+arrays still take full Evidence. `close_binary` clears retained references;
+export a bundle before closing, or supply portable inline Evidence in another
+connection. A missing reference includes its ID and recovery guidance.
 
 For exact file/native metadata or processing gaps, use
 `view: {kind: "javascript-facts", where: {paths: ["package.json"]}, property_keys: ["name", "operation", "analysis_status"], limit: 32}`.

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

@@ -1,11 +1,8 @@
 # Native, managed, and packaged artifacts
 
-For release comparisons on one MCP connection, retain `list_procedures` Evidence
-from each target and reuse its exact IDs after target switches or `close_binary`.
-For a handoff or new process, export the complete bundle and import it there,
-including its source closure. `reset_investigation` explicitly clears retained
-records; optional `save_path` checkpoints them before clearing.
-`match_native_functions` pairs unique exact names and, when supplied,
+For release comparisons, export `list_procedures` Evidence from each target before
+closing it. Close clears session records: import both bundles after collecting the
+two targets, or supply portable inline Evidence. `match_native_functions` pairs unique exact names and, when supplied,
 complete observed body bytes. Reuse optional same-context `list_names`,
 `procedure_info`, `read_bytes` and existing `analyze_function` dossiers as
 `left_observations`/`right_observations`; an MCP `analyze_function` summary
@@ -16,13 +13,6 @@ Select columns, batch IDs and page individual facts; aliases remain unresolved.
 Unpaired observations do not prove additions/removals. Existing matched dossier
 pairs include inputs for `compare_functions`; otherwise analyze just chosen pairs.
 
-Aggregate completed comparisons with `find_changed_behavior`, selecting each
-comparison's exact `retained-evidence` ID instead of resending full records.
-Inline comparison Evidence remains accepted. References belong to the current
-server: after handoff, import the original bundle including its source closure.
-Do not substitute dossier IDs or summary views. Static differences remain
-behavior candidates, with runtime behavior unknown unless separately observed.
-
 For a matching representation refusal, inspect `details.limit` and raise
 `native.matching_representation_bytes` with `update_analysis_settings` before
 retrying the unchanged MCP request. CLI launch seed:
@@ -346,9 +336,8 @@ the complete tool inventory grouped by current status. Expand each group's
 overrides them; availability, reasons, remediation, and modes remain inline.
 Provider candidates keep availability and target-support status, code, and
 reason. `omitted_fields` names what the summary leaves out; `{"detail":
-"complete"}` adds each unavailable candidate's `remediation`, provider
-diagnostics, candidate capability sets, and tool surface, `effects`, and
-`annotations`. Those arrays name true flags from fixed
+"complete"}` adds provider diagnostics, candidate capability sets, and tool
+surface, `effects`, and `annotations`. Those arrays name true flags from fixed
 vocabularies, so an omitted known flag is false. `tools/list` remains the
 canonical source for full tool schemas when target or provider state changes.
 
@@ -589,16 +578,6 @@ 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.
 
-For classic iNES cartridges, `open_binary` recognizes the byte signature without
-an executable architecture. `inspect_artifact` retains header facts and each
-PRG/CHR file unit's offset, length and SHA-256; its nested inventory's
-`ines.reconstruction` verifies the actual ordered region bytes against the
-whole-file digest. Extraction includes the original header, optional trainer
-and uninterpreted trailing bytes. These file units are not mapper/CPU bank
-maps. NES 2.0, UNIF, dirty legacy headers and truncated payloads are explicitly
-refused. No emulator or 6502 analysis is performed. See the
-[iNES guide](https://github.com/morluto/rea/blob/main/docs/ines-containers.md).
-
 Native DMG traversal automatically uses a read-only mount on supported macOS
 hosts, with an owned temporary mount directory and cleanup. It needs no approval
 flag. Unsupported hosts or mount failures remain explicit limitations; do not
@@ -627,27 +606,10 @@ semantics are unsupported. `m68k` requires an even entry and decodes the 68040
 superset of the 68000 family; Amiga/Atari containers and vector-table entry
 discovery are unsupported. Windows Ghidra P0 admits raw images only for `6502`. See [raw binary guide](https://github.com/morluto/rea/blob/main/docs/raw-binary.md).
 
-Intel HEX, S-record, UF2 and DfuSe files are containers, not raw images:
-`inspect_artifact` lists address regions (UF2 per familyID, DfuSe per element
-with its alternate setting), and `extract_artifact` writes each region. Open an
-extracted region as `raw-binary` with its start address as `entry_point`. UF2
-numbering gaps leave coverage unknown; a DfuSe suffix CRC mismatch follows
-`integrity_policy`. See [UF2 and DfuSe](https://github.com/morluto/rea/blob/main/docs/uf2-dfuse.md).
-
 ### Function annotations in Ghidra
 
 Fresh-import sessions admit annotations; existing-project reuse is read-only.
-Use `annotate_native_function` for one function name and/or entry comments, with at least one explicit change. Review its annotation readback and refreshed dossier inline. Changes are atomic and session-scoped; empty comments clear them, omitted fields preserve them. Later MCP calls observe edits until close. CLI `annotate-native-function` returns the updated analysis before discarding the session. Original executable bytes are unchanged; edits invalidate immutable snapshots. Windows P0 does not admit database mutations. For naming only, `set_address_name` / `set_addresses_names` also work with Ghidra: they name function entries or data addresses (primary labels) and return compact per-address success booleans instead of a dossier. Ghidra rejects batch addresses that request the same name or a name another selected address holds; `raw_result.failures` gives each failure's reason.
-
-For `compare_functions`, obtain `analyze_function` Evidence before and after the
-edit while the MCP session is open; annotation Evidence is not a comparison
-input. Export the needed Evidence before close if comparison will happen later.
-Authenticated same-artifact coordinates preserve renamed entries as
-`matched / same-entry`, with the canonical `entry_address` inline; name and
-exact-text changes remain separate dimensions. This requires compatible
-architecture, provider-owned mapping and selected-image commitments. Equal
-numeric addresses alone cannot establish correspondence; inspect retained
-source Evidence and coverage when the match remains ambiguous.
+Use `annotate_native_function` for one function name and/or entry comments, with at least one explicit change. Review its annotation readback and refreshed dossier inline. Changes are atomic and session-scoped; empty comments clear them, omitted fields preserve them. Later MCP calls observe edits until close. CLI `annotate-native-function` returns the updated analysis before discarding the session. Original executable bytes are unchanged; edits invalidate immutable snapshots. Windows P0 does not admit database mutations. For naming only, `set_address_name` / `set_addresses_names` also work with Ghidra: they name function entries or data addresses (primary labels) and return compact per-address success booleans instead of a dossier.
 
 ## Offline PE resource inventory
 
@@ -675,9 +637,7 @@ For exact core-module import/export differences, use `compare_wasm_interfaces`
 with two complete inspection Evidence records (or current-session retained
 references) and explicit scope. Preserve unknown types/duplicate names; static
 interface equality is not runtime compatibility. CLI accepts complete inline
-Evidence in `rea compare-wasm-interfaces input.json --json`, or exact references
-with `--evidence-bundle /absolute/path/evidence.json`. Use the complete parent
-ID when the inspection returned a summary.
+Evidence in `rea compare-wasm-interfaces input.json --json`.
 
 ## Godot PCK
 
@@ -736,32 +696,6 @@ recognized. Segments are not disassembled, and RISC-V or Xtensa segments
 cannot be opened as raw-binary. See
 [ESP images](https://github.com/morluto/rea/blob/main/docs/esp-image.md).
 
-## ESP flash images
-
-A whole-flash dump opens as `esp-flash-image`. `root_format_metadata` holds
-`partition_table` (its `method`: `default`, `caller` or a derived
-`scan`), `bootloader` and `apps` ESP image facts, the `otadata` records,
-`partitions_outside_dump` and `boot_selection`. Every table has a
-`boot_selection`: its `basis` names the bootloader's branch (`no-otadata`
-without otadata, `none` when the bootloader rejects the table, `unknown`
-when a record is missing), and it lists its `assumptions`;
-`running_partition` is always `unknown`. Each image names its entry
-`path`. With `detail: "summary"` the root kind is `esp-flash-image-summary`
-and each image is a compact `summary` (chip, entry point, segment count,
-classified load ranges, signature block count, descriptor identity,
-integrity); complete detail keeps every segment. Partition rows
-(`partitions/<label>.bin`) carry the declared `type`, `subtype`, names,
-`flash_address`, `size` and flags; `encrypted` is a storage flag, not
-proof of ciphertext. `written_offset`/`written_end` bound the bytes that
-are not erased: an app slot whose facts say `erased` can still hold an older
-image, and a limitation says so. For a dump read from another flash address, call
-`open_binary` with `format: "esp-flash-image"` and `flash_offset`; an
-`esp-image` whose `flash_dump` is set names that offset in a next probe; a
-relocated table can be named with `partition_table_offset`. No table found
-means unknown, often flash encryption. Extraction writes `nvs_keys` as
-ordinary data. See
-[ESP flash images](https://github.com/morluto/rea/blob/main/docs/esp-flash-image.md).
-
 ## Bun standalone executables
 
 A `bun build --compile` executable stores its module graph in Mach-O

.github/codeql/production.yml

@@ -1,21 +0,0 @@
-name: REA production code
-
-# Match the existing default-setup scan's local-input threat model.
-threat-models: [local]
-
-# Retain root traversal, including future production roots. Hidden directories
-# need their own root; use a directory so Python can share this configuration.
-paths:
-  - .
-  - docs/.vitepress
-
-# Keep the default query suite and all production roots, including bridge/,
-# install.sh, runtime scripts, release controllers, and GitHub Actions.
-# Exclude test inputs at extraction time so they cannot taint production callers.
-paths-ignore:
-  - tests
-  - scripts/fixtures
-  - "**/*.test.*"
-  - "**/*.fixture.*"
-  - "**/test_*.py"
-  - "**/*_test.py"

.github/pull_request_template.md

@@ -106,8 +106,7 @@ limits, security/privacy/containment implications, and meaningful proof gaps. --
 
 ## Author readiness
 
-<!-- The human owner completes these declarations before requesting review,
-unless the PR author is exempt as listed in CONTRIBUTING.md.
+<!-- The human owner completes these declarations before requesting review.
 The PR author is the owner by default. A different owner must explicitly accept
 ownership on this PR.
 AI agents must leave these declarations to a human to dictate to them or there could be catastrophic consequences for many users of REA.

.github/workflows/ci.yml

@@ -779,12 +779,6 @@ jobs:
           npm run verify:legacy-simulator
           npm run verify:apple-dispatch
           npm run verify:interface-builder
-      - name: Verify portable iNES CLI, MCP and source boundaries
-        run: >-
-          npm run test:focused --
-          tests/acceptance/inesContainer.test.ts
-          tests/boundary/filesystem/inesArtifact.test.ts
-          tests/boundary/filesystem/inesCancellation.test.ts
       - name: Run native Apple and process boundary regressions
         run: >-
           npm run test:focused --
@@ -805,10 +799,7 @@ jobs:
           tests/boundary/cli/nativeDemangleCli.test.ts
           tests/boundary/cli/nativeDispatchPropertyAttributes.test.ts
           tests/boundary/mcp/nativeDemangleMcp.test.ts
-          tests/boundary/mcp/nativeMachoSummaryMcp.test.ts
           tests/boundary/providers/native/nativeSignatureTargetBinding.test.ts
-          tests/boundary/providers/native/nativeUiOffscreenWindow.test.ts
-          tests/boundary/process/nativeUiVerifierLane.test.ts
           tests/boundary/cli/nativeSignatureCli.test.ts
           tests/boundary/cli/nativeMachoArm64_32Cli.test.ts
           tests/boundary/cli/nativeMachoEncryptionCli.test.ts

.github/workflows/codeql.yml

@@ -1,61 +0,0 @@
-name: CodeQL production
-
-on:
-  push:
-    branches: [main]
-  pull_request:
-    branches: [main]
-  schedule:
-    - cron: "37 5 * * 1"
-  workflow_dispatch:
-
-permissions:
-  contents: read
-
-concurrency:
-  group: codeql-production-${{ github.event.pull_request.number || github.ref }}
-  cancel-in-progress: true
-
-jobs:
-  analyze:
-    # A repository administrator must disable default setup before enabling
-    # this workflow; default setup rejects advanced CodeQL result uploads.
-    if: vars.REA_CODEQL_ADVANCED == 'true'
-    name: Analyze production (${{ matrix.language }})
-    runs-on: ubuntu-latest
-    timeout-minutes: 45
-    permissions:
-      contents: read
-      security-events: write
-    strategy:
-      fail-fast: false
-      max-parallel: 1
-      matrix:
-        language: [javascript-typescript, python, actions]
-    steps:
-      - uses: actions/checkout@d23441a48e516b6c34aea4fa41551a30e30af803 # v6.1.0
-        with:
-          persist-credentials: false
-      - name: Initialize production analysis
-        uses: github/codeql-action/init@9b3254085494b55a0f7c4c2b3d2d52cc712ce370 # v4
-        with:
-          languages: ${{ matrix.language }}
-          build-mode: none
-          config-file: .github/codeql/production.yml
-          threads: 2
-          ram: 4096
-      - name: Analyze production code
-        uses: github/codeql-action/analyze@9b3254085494b55a0f7c4c2b3d2d52cc712ce370 # v4
-        with:
-          category: /language:${{ matrix.language }}
-          output: ${{ runner.temp }}/codeql-production-results
-          threads: 2
-          ram: 4096
-      - name: Retain complete analysis evidence
-        if: always()
-        uses: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02 # v4.6.2
-        with:
-          name: codeql-production-${{ matrix.language }}
-          path: ${{ runner.temp }}/codeql-production-results
-          if-no-files-found: error
-          retention-days: 7

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

@@ -55,12 +55,12 @@ jobs:
       - uses: ./.github/actions/portable-build-cache
         with:
           build_cache_artifact: ${{ inputs.build_cache_artifact }}
-      - name: Install AArch64 and ELF32 cross toolchains for source-owned fixtures
+      - name: Install ELF32 cross toolchains for source-owned fixtures
         run: |
           sudo apt-get update
           sudo apt-get install --yes --no-install-recommends \
-            gcc-aarch64-linux-gnu gcc-i686-linux-gnu gcc-arm-linux-gnueabi gcc-mips-linux-gnu gcc-mipsel-linux-gnu \
-            libc6-dev-arm64-cross libc6-dev-i386-cross libc6-dev-armel-cross libc6-dev-mips-cross libc6-dev-mipsel-cross
+            gcc-i686-linux-gnu gcc-arm-linux-gnueabi gcc-mips-linux-gnu gcc-mipsel-linux-gnu \
+            libc6-dev-i386-cross libc6-dev-armel-cross libc6-dev-mips-cross libc6-dev-mipsel-cross
       - name: Acquire exact upstream libraries in an isolated runner environment
         shell: bash
         run: |

.github/workflows/real-browser.yml

@@ -53,8 +53,3 @@ jobs:
         env:
           REA_BROWSER_EXECUTABLE: /usr/bin/google-chrome
           REA_BROWSER_NO_SANDBOX: "true"
-      # The preceding verifier builds the runtime used by this request journey.
-      - run: dbus-run-session -- node scripts/verify-browser-request.mjs
-        env:
-          REA_BROWSER_EXECUTABLE: /usr/bin/google-chrome
-          REA_BROWSER_NO_SANDBOX: "true"

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

@@ -54,7 +54,7 @@ jobs:
           mkdir -p .cache
           rm -f "$report"
           node scripts/run-exact-tests.mjs run --reporter=default --reporter=json --outputFile.json="$report" \
-            tests/boundary/captures/fieldDiscovery.test.ts src/process/LinuxResourceLimits.test.ts tests/boundary/captures/captureProvider.test.ts tests/boundary/captures/captureDescriptorCleanup.test.ts tests/boundary/pcap/pcapProvider.test.ts tests/boundary/pcap/pcapProviderCrossPlatform.test.ts tests/boundary/captures/resourceLimits.test.ts tests/boundary/captures/packetOutput.test.ts tests/boundary/mcp/packetCaptureMcp.test.ts tests/boundary/cli/captureCleanup.test.ts tests/acceptance/pcapVerifier.test.ts
+            tests/boundary/captures/fieldDiscovery.test.ts src/process/LinuxResourceLimits.test.ts tests/boundary/captures/captureProvider.test.ts tests/boundary/captures/captureDescriptorCleanup.test.ts tests/boundary/pcap/pcapProvider.test.ts tests/boundary/pcap/pcapProviderCrossPlatform.test.ts tests/boundary/captures/resourceLimits.test.ts tests/boundary/captures/packetOutput.test.ts tests/boundary/mcp/packetCaptureMcp.test.ts tests/boundary/cli/captureCleanup.test.ts
           node scripts/ci/require-provider-tests.mjs packet "$report"
       - run: node scripts/verify-packet-capture.mjs
         env:

.github/workflows/website-check.yml

@@ -21,10 +21,6 @@ jobs:
           python-version: "3.12"
           cache: pip
           cache-dependency-path: website/requirements.txt
-      - name: Set up Node.js for the website Worker checks
-        uses: actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020 # v4.4.0
-        with:
-          node-version-file: .nvmrc
       - name: Install sharing-image dependencies
         run: |
           sudo apt-get update

.github/workflows/website-pages.yml

@@ -54,10 +54,6 @@ jobs:
           python-version: "3.12"
           cache: pip
           cache-dependency-path: website/requirements.txt
-      - name: Set up Node.js for the website Worker checks
-        uses: actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020 # v4.4.0
-        with:
-          node-version-file: .nvmrc
       - name: Install sharing-image dependencies
         run: |
           sudo apt-get update
@@ -79,21 +75,10 @@ jobs:
           PY
       - name: Configure Pages
         uses: actions/configure-pages@983d7736d9b0ae728b81ab479565c72886d7745b # v5.0.0
-      # upload-pages-artifact excludes dot directories, including .well-known.
-      - name: Package the website including agent discovery
-        run: |
-          tar --dereference --hard-dereference --directory website/_site \
-            --exclude=.git --exclude=.github -cf "$RUNNER_TEMP/artifact.tar" .
-          tar -tf "$RUNNER_TEMP/artifact.tar" \
-            ./.well-known/ard.json ./.well-known/ai-catalog.json \
-            ./.well-known/agent-skills/index.json > /dev/null
       - name: Upload the website
-        uses: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02 # v4.6.2
+        uses: actions/upload-pages-artifact@7b1f4a764d45c48632c6b24a0339c27f5614fb0b # v4.0.0
         with:
-          name: github-pages
-          path: ${{ runner.temp }}/artifact.tar
-          retention-days: 1
-          if-no-files-found: error
+          path: website/_site
 
   deploy:
     needs: prepare
@@ -145,24 +130,14 @@ jobs:
           PUBLISH_TARGET: ${{ inputs.target }}
         run: |
           python3 -u - <<'PY'
-          import hashlib
           import json
           import os
           import sys
           import time
           from urllib.error import URLError
-          from urllib.parse import urljoin, urlsplit
+          from urllib.parse import urljoin
           from urllib.request import Request, urlopen
 
-          def open_public(url, accept=None):
-              headers = {
-                  "Cache-Control": "no-cache",
-                  "User-Agent": "REA-Website-Verifier/1.0 (+https://github.com/morluto/rea)",
-              }
-              if accept:
-                  headers["Accept"] = accept
-              return urlopen(Request(url, headers=headers), timeout=10)
-
           expected = os.environ["GITHUB_SHA"]
           pages_url = os.environ["PAGES_URL"]
           if not pages_url:
@@ -178,7 +153,11 @@ jobs:
               for name, base in list(pending.items()):
                   url = urljoin(base, "deployment.json") + "?commit=" + expected
                   try:
-                      with open_public(url) as response:
+                      request = Request(url, headers={
+                          "Cache-Control": "no-cache",
+                          "User-Agent": "REA-Website-Verifier/1.0 (+https://github.com/morluto/rea)",
+                      })
+                      with urlopen(request, timeout=10) as response:
                           actual = json.load(response).get("commit")
                       if actual == expected:
                           print(f"{name} serves {expected}: {base}")
@@ -193,27 +172,6 @@ jobs:
                   time.sleep(5)
           if pending:
               sys.exit("Could not verify published revision on: " + ", ".join(pending))
-          for name, base in hosts.items():
-              with open_public(urljoin(base, ".well-known/agent-skills/index.json")) as response:
-                  skill, = json.load(response)["skills"]
-              # Fetch from each selected host, including the /rea/ mirror.
-              artifact_url = urljoin(base, urlsplit(skill["url"]).path.lstrip("/"))
-              with open_public(artifact_url) as response:
-                  digest = "sha256:" + hashlib.sha256(response.read()).hexdigest()
-              if digest != skill["digest"]:
-                  sys.exit(name + " serves a skill archive with the wrong digest")
-              for manifest in ("ard.json", "ai-catalog.json"):
-                  with open_public(urljoin(base, ".well-known/" + manifest)) as response:
-                      if not json.load(response).get("entries"):
-                          sys.exit(name + " serves an empty discovery manifest")
-              if name == "Cloudflare":
-                  with open_public(base, accept="text/markdown") as response:
-                      vary = {value.strip().lower() for value in response.headers.get("Vary", "").split(",")}
-                      if response.headers.get_content_type() != "text/markdown" or "accept" not in vary:
-                          sys.exit("Cloudflare did not negotiate Markdown with Vary: Accept")
-                      if 'rel="ard"' not in response.headers.get("Link", ""):
-                          sys.exit("Cloudflare is missing its discovery Link header")
-              print(name + " serves the discovery manifests and verified skill archive")
           with open(os.environ["GITHUB_STEP_SUMMARY"], "a", encoding="utf-8") as summary:
               links = " and ".join(f"[{name}]({url})" for name, url in hosts.items())
               summary.write(f"Published commit `{expected}` to {links}.\n")

AGENTS.md

@@ -28,10 +28,6 @@ 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.
 
-After confirming a bug, search sibling adapters, consumers and similar workflows
-for the same failure. Verify suspected matches, record working comparisons, and
-group findings by root cause instead of filing duplicate reports.
-
 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.
@@ -79,9 +75,6 @@ Use [.nvmrc](.nvmrc) and `package.json#packageManager` for the pinned toolchain.
 
 Use relevant checks for the change. The complete local gate, `npm run check:pr`, is optional for broad changes or CI diagnosis. See [CONTRIBUTING.md](CONTRIBUTING.md) for development, generated-file ownership, and release conventions.
 
-When changing installers or setup recovery, follow
-[Checking installers and publisher downloads](docs/testing.md#checking-installers-and-publisher-downloads).
-
 Coordinate expensive checks across agents. If a test unexpectedly consumes heavy CPU, stop its owned process family and profile a bounded representative case before retrying. Inspect production work, fixture generation, subprocesses, and repeated setup; preserve regression coverage when optimizing. Follow the [test resource guidance](docs/testing.md#developer-commands).
 
 `docs/public/product-catalog.json`, `docs/verification/managed-conformance-*.json`, and `skills/` are ignored outputs. Edit source contracts and `.agents/skills/reverse-engineer-anything/`, then regenerate as needed. `.cache/mcp-tool-catalog.json` is test metadata; runtime builds and source checking do not consume it. Never commit binaries, provider project documents, credentials, `dist/`, `node_modules/`, or local planning artifacts.
@@ -90,12 +83,6 @@ Coordinate expensive checks across agents. If a test unexpectedly consumes heavy
 
 For tool design, follow [docs/tool-design.md](docs/tool-design.md): start from the analyst question, reuse existing contracts, preserve caller choices, and return useful evidence inline. Limits must follow real format, protocol, authority, or resource constraints. Account for representation expansion before allocation; derive completeness from examined coverage.
 
-For user- or agent-facing tool problems, prioritize fixing the owning behavior,
-contract, and actionable result or recovery at the point of use. Document the
-result in product docs when explanation is needed. Add skill guidance only for
-workflow judgment or context that the tool cannot reasonably convey; do not use
-a skill as the primary repair for a discoverability or contract defect.
-
 For test changes or provider claims, use [docs/testing.md](docs/testing.md). Select applicable [boundary regressions](docs/testing.md#boundary-regressions) for parser, inventory, snapshot, and projection fixes. Prefer real public CLI/MCP workflows, then production-boundary integration, then producer goldens. Keep module tests for distinct semantics stronger workflows cannot reliably reproduce. Preserve malformed-input, cancellation, cleanup, permission, capacity, and target-identity coverage when pruning. Report unverified coverage explicitly; simulated providers do not establish real-provider behavior.
 
 Use Conventional Commit subjects and PR titles. Mark breaking changes with `!` or a `BREAKING CHANGE:` footer. Describe behavior changes, relevant validation, and real-provider verification scope.
@@ -128,8 +115,8 @@ owner to complete. Never attest to human review on their behalf. Draft status
 is optional; preserve the PR's current draft status unless the user asks to change
 it. Later pushes do not invalidate the readiness declaration or require another
 human sign-off. Keep the PR body and affected validation current as work changes.
-The readiness check validates the filled declaration or the author exemption
-listed in CONTRIBUTING.md; CI and automated review results do not establish that
+The readiness check validates
+the filled declaration; CI and automated review results do not establish that
 human review occurred, maintainer scope approval, or merge permission.
 
 <!-- BEGIN:turborepo-agent-rules -->

CONTRIBUTING.md

@@ -16,9 +16,10 @@ import inventory. For current provider wiring, start with
 [`src/composition/binary.ts`](src/composition/binary.ts) for deep candidates and
 the other `src/composition/` factories for tool services, including
 [`gpu.ts`](src/composition/gpu.ts) and [`model.ts`](src/composition/model.ts).
-Live Frida, Cutter, GDB and Rizin construction also uses shared composition
-factories. For service ownership, availability and catalog declarations, follow
-the [capability composition guide](docs/capability-composition.md).
+Live Frida and Cutter adapters are constructed directly in
+[`src/cli/fridaCommands.ts`](src/cli/fridaCommands.ts),
+[`src/cli/cutterCommands.ts`](src/cli/cutterCommands.ts), and
+[`src/server/createServer.ts`](src/server/createServer.ts).
 Production factories construct fresh providers without starting engines or
 acquiring targets; optional adapter failures must preserve successful peers. Run
 `npm run verify:test-discovery` after adding or moving tests. Resolved import
@@ -93,8 +94,7 @@ Before requesting maintainer review, the human owner must:
   passing. Follow the [verification requirements](#development-feedback-and-pr-verification)
   for required checks and real-provider coverage.
 - Complete the **Author readiness** declaration in the PR template, explicitly
-  stating that the PR is ready for initial review, unless the PR author is
-  exempt from the declaration as listed below.
+  stating that the PR is ready for initial review.
 
 Keep the PR description concise and current. Explain the problem, observable
 outcome, approach, and useful evidence; link long logs or put them in optional
@@ -115,12 +115,9 @@ validation current as work changes. AI agents must leave human declarations to
 the human owner and must not attest to a human review on their behalf.
 
 The `PR readiness` check reports pending for drafts and requires a named human
-owner and all three template declarations for non-drafts. PRs authored by
-@morluto, @kaoru0822-kitauji, @N0zoM1z0, or @gensokyo-dev are exempt from
-the declaration; their human ownership, review, and evidence responsibilities
-above still apply. The check identifies authors by GitHub account ID. It checks
-that the declaration is filled, not whether the code or evidence is correct.
-Existing PRs can copy the **Author readiness** section from the current template.
+owner and all three template declarations for non-drafts. It checks that the
+declaration is filled, not whether the code or evidence is correct. Existing PRs
+can copy the **Author readiness** section from the current template.
 Open PRs must have distinct head commits because GitHub shares commit statuses.
 
 Maintainers enable merge enforcement after the workflow is merged: run

README.md

@@ -20,8 +20,6 @@
 
 **[Website](https://rea.tools/) · [Guides](https://rea.tools/guides/) · [Showcases](https://rea.tools/showcase/)**
 
-<a href="https://discord.com/invite/GkcryMnJDM"><img alt="Join the REA community on Discord" src="https://img.shields.io/badge/Join%20us%20on%20Discord-5865F2?style=for-the-badge&logo=discord&logoColor=white" height="40"></a>
-
 [Quick start](#quick-start) · [How REA works](#how-rea-works) · [What you can analyze](#what-you-can-analyze) · [Showcases](#showcases) · [Build RL environments](#build-rl-environments) · [FAQ](#faq) · [Documentation](#documentation)
 
 <code>npx rea-agents setup</code>

THIRD_PARTY_NOTICES.md

@@ -17,7 +17,6 @@ notices supplied with the software you actually obtain or redistribute.
 | ------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
 | npm dependencies         | [Complete inventory](licenses/npm-dependencies.txt) of every entry in `package-lock.json`, including transitive, optional platform, development, and website dependencies. [Runtime notices](licenses/npm-runtime-notices.txt) preserve the copyright, license, and NOTICE documents from integrity-verified release archives, plus the MIT notice for Rolldown's generated runtime helpers. Development dependencies are inventoried but are not all distributed in REA's npm package.                                                                                                                                                                                                                       |
 | pefile ordinal tables    | Import-hash ordinal names are derived from [pefile 2024.8.26](https://github.com/erocarrera/pefile/tree/4b3b1e2e568a88d4f1897d694d684f23d9e270c4), copyright 2004–2024 Ero Carrera. Preserve the [MIT license](licenses/pefile-2024.8.26-LICENSE.txt). The Python package is not a runtime dependency.                                                                                                                                                                                                                                                                                                                                                                                                        |
-| UF2 family names         | UF2 family IDs and short names are copied from [microsoft/uf2 `utils/uf2families.json`](https://github.com/microsoft/uf2/blob/cf3bd7f9c274b949528f8cd6a19eef2502a687d2/utils/uf2families.json), copyright Microsoft Corporation. Preserve the [MIT license](licenses/microsoft-uf2-MIT.txt).                                                                                                                                                                                                                                                                                                                                                                                                                  |
 | NativeAOT parser         | REA's derived parser uses the MIT-licensed [ghidra-nativeaot](https://github.com/Washi1337/ghidra-nativeaot/tree/effeb734fc570c32650f88b159608979dc7b423e) work of Washi and the NativeAOT layout definitions in [dotnet/runtime](https://github.com/dotnet/runtime/tree/a3b2d40328be0be3f8dd43f0e5cc925b8827b044). Preserve [Washi's MIT notice](licenses/nativeaot-parser-MIT.txt) and the [.NET Foundation MIT notice](licenses/dotnet-runtime-MIT.txt).                                                                                                                                                                                                                                                   |
 | EVM analysis             | `[email protected]`, MIT, copyright 2023 Maxim Andreev. The published npm archive omits its license document; REA retains the [original upstream license](third_party/evmole/LICENSE) and [provenance](third_party/evmole/README.md). It is also included in the runtime notices.                                                                                                                                                                                                                                                                                                                                                                                                                                  |
 | Windows native addon     | The release addon is compiled with MinGW-w64 and statically links GCC runtime libraries. Preserve the [MinGW-w64 runtime notices](licenses/MinGW-w64-runtime.txt), [GPLv3 text](licenses/GPL-3.0.txt), and [GCC Runtime Library Exception 3.1](licenses/GCC-Runtime-Library-Exception-3.1.txt). The exception governs eligible compiled combinations; it does not relicense the runtime itself under MIT. The Node-API build headers are from Node 22.19.0; its [original license and component notices](licenses/Node-22.19.0-LICENSE.txt) are retained. Node itself is supplied by the user. Snapshot provenance and release-toolchain review requirements are in [licenses/README.md](licenses/README.md). |
@@ -60,7 +59,7 @@ pin inspection sources; they are not included in the npm package.
 | ghidra-nativeaot               | [MIT](https://github.com/Washi1337/ghidra-nativeaot/blob/effeb734fc570c32650f88b159608979dc7b423e/LICENSE.md)                                                                                                                                            | Pinned inspection source; derived parser attribution above.                                                                                                                                                                                                                        |
 | JADX                           | [Apache-2.0](https://github.com/skylot/jadx/blob/v1.5.6/LICENSE)                                                                                                                                                                                         | The audited jadx-headless-mcp source uses JADX 1.5.6 for Android decompilation; the engine JAR is separately supplied.                                                                                                                                                             |
 | jadx-headless-mcp              | [Apache-2.0](https://github.com/1013503897/jadx-headless-mcp/blob/5844800a486d2248fa949b74c9896285f5b54de2/LICENSE)                                                                                                                                      | v0.7.1; pinned submodule and user-supplied JAR.                                                                                                                                                                                                                                    |
-| Kuna                           | [Apache-2.0](https://github.com/Noelo-Lab/kuna/blob/v1.990/LICENSE), with its [NOTICE](https://github.com/Noelo-Lab/kuna/blob/v1.990/NOTICE)                                                                                                             | Bring your own `kuna`; REA verified 1.990 and never downloads, installs or bundles it. REA invokes it as a separate process.                                                                                                                                                       |
+| Kuna                           | [Apache-2.0](https://github.com/Noelo-Lab/kuna/blob/v1.833/LICENSE), with its [NOTICE](https://github.com/Noelo-Lab/kuna/blob/v1.833/NOTICE)                                                                                                             | Bring your own `kuna`; REA verified 1.833 and never downloads, installs or bundles it. REA invokes it as a separate process.                                                                                                                                                       |
 | Apktool                        | [Apache-2.0](https://github.com/iBotPeaches/Apktool/blob/master/LICENSE.md)                                                                                                                                                                              | User-supplied Android resource decoder.                                                                                                                                                                                                                                            |
 | Binwalk                        | [MIT](https://github.com/ReFirmLabs/binwalk/blob/4fdab3d464d97b68e0af9088df3f9e2e1545b21c/LICENSE)                                                                                                                                                       | v3.1.0; pinned submodule and user-supplied firmware engine.                                                                                                                                                                                                                        |
 | Unblob                         | [MIT](https://github.com/onekey-sec/unblob/blob/1fcc7a0a584a70a96c31f5a276c20944d199a089/LICENSE)                                                                                                                                                        | 26.6.4; pinned submodule and user-supplied firmware engine.                                                                                                                                                                                                                        |

bridge/ghidra/ReaGhidraBridge.java

@@ -40,7 +40,6 @@ import java.util.Locale;
 import java.util.Map;
 import java.util.Set;
 import java.util.TreeMap;
-import java.util.TreeSet;
 import java.util.regex.Pattern;
 import java.util.regex.PatternSyntaxException;
 
@@ -549,11 +548,6 @@ public final class ReaGhidraBridge extends HeadlessScript {
         String softFloat = currentProgram.getOptions(ghidra.program.model.listing.Program.PROGRAM_INFO)
             .getString("REA MIPS soft-float storage", null);
         if (softFloat != null) result.add("mips_soft_float_storage", JsonParser.parseString(softFloat));
-        // Written by ReaGhidraRiscvCallingConvention after analysis; REA requires it
-        // exactly when the committed profile declares a RISC-V calling-convention policy.
-        String riscvCallingConvention = currentProgram.getOptions(ghidra.program.model.listing.Program.PROGRAM_INFO)
-            .getString("REA RISC-V calling convention", null);
-        if (riscvCallingConvention != null) result.add("riscv_calling_convention", JsonParser.parseString(riscvCallingConvention));
         return result;
     }
 
@@ -693,7 +687,6 @@ public final class ReaGhidraBridge extends HeadlessScript {
             }
             row.addProperty("status", relocation.getStatus().toString());
             row.addProperty("type", relocation.getType());
-            row.add("symbol", GSON.toJsonTree(relocation.getSymbolName()));
             row.add("values", GSON.toJsonTree(relocation.getValues() == null ? new long[0] : relocation.getValues()));
             byte[] original = relocation.getBytes();
             row.add("original_bytes_hex", original == null ? JsonNull.INSTANCE : GSON.toJsonTree(bytesHex(original)));
@@ -929,33 +922,17 @@ public final class ReaGhidraBridge extends HeadlessScript {
         requireKeys(params, Set.of("document", "address"));
         requireDocument(params);
         Address address = requireAddress(params, "address");
-        String at = canonicalAddress(address);
-        // A well-formed address can still lack one exact source offset. Each
-        // outcome has its own code, so REA reports the reason rather than
-        // schema repair. Initialization, not the loaded flag, decides whether
-        // source bytes can exist: file-backed overlays are not loaded.
         MemoryBlock block = currentProgram.getMemory().getBlock(address);
-        if (block == null)
-            throw new RequestFailure("address_unmapped",
-                "Address " + at + " is outside every Ghidra memory block");
-        if (!block.isInitialized())
-            throw new RequestFailure("address_uninitialized",
-                "Address " + at + " is in uninitialized Ghidra memory block " + block.getName());
+        if (block == null || !block.isInitialized())
+            throw new RequestFailure("invalid_request", "Address has no initialized file-backed memory: " + canonicalAddress(address));
         TargetFileOffset mapping = targetFileOffset(block, address);
-        if (mapping.mappings() == 0)
-            throw new RequestFailure("file_mapping_absent",
-                "Address " + at + " in initialized Ghidra memory block " + block.getName() +
-                " has no authoritative mapping to the admitted target file");
-        if (mapping.mappings() > 1)
-            throw new RequestFailure("file_mapping_ambiguous",
-                "Address " + at + " has " + mapping.mappings() +
-                " authoritative mappings to the admitted target file");
+        if (mapping.mappings() != 1)
+            throw new RequestFailure("invalid_request", "Address has " + mapping.mappings() + " authoritative target-file mappings: " + canonicalAddress(address));
         Long fileOffset = mapping.offset();
         if (fileOffset == null)
-            throw new RequestFailure("file_offset_unrepresentable",
-                "Address " + at + " maps to an admitted target-file offset beyond the exact JSON integer range");
+            throw new RequestFailure("invalid_request", "Address lacks a safe file offset: " + canonicalAddress(address));
         JsonObject result = new JsonObject();
-        result.addProperty("address", at);
+        result.addProperty("address", canonicalAddress(address));
         result.addProperty("file_offset", fileOffset);
         return result;
     }
@@ -1954,62 +1931,41 @@ public final class ReaGhidraBridge extends HeadlessScript {
         return symbol == null ? JsonNull.INSTANCE : GSON.toJsonTree(symbol.getName(true));
     }
 
-    // Analyst naming: a function entry renames the function; another mapped
-    // address renames its non-dynamic primary label or receives a new global
-    // label. Resolve that destination without editing the program.
-    private AddressNameTarget addressNameTarget(Address address, String name)
-        throws ghidra.util.exception.InvalidInputException {
+    // Analyst naming: a function entry renames the function, other addresses get a primary label.
+    private boolean applyAddressName(Address address, String name) throws Exception {
         if (!currentProgram.getMemory().contains(address))
             throw new RequestFailure("invalid_request", "Address is not mapped: " + canonicalAddress(address));
         validateAnnotationText(name, "name");
-        Symbol edited = editedNameSymbol(address);
-        return edited == null
-            ? new AddressNameTarget(address, currentProgram.getGlobalNamespace(), name)
-            : new AddressNameTarget(address, edited.getParentNamespace(), symbolLeafName(edited, name));
-    }
-
-    private Symbol editedNameSymbol(Address address) {
-        Function function = currentProgram.getFunctionManager().getFunctionAt(address);
-        if (function != null) return function.getSymbol();
-        Symbol primary = currentProgram.getSymbolTable().getPrimarySymbol(address);
-        return primary == null || primary.isDynamic() ? null : primary;
-    }
-
-    // Every address whose label or function symbol holds the destination.
-    private List<Address> addressNameHolders(AddressNameTarget target) {
-        Set<Address> holders = new TreeSet<>();
-        for (Symbol symbol : currentProgram.getSymbolTable().getLabelOrFunctionSymbols(target.leaf(), target.namespace()))
-            holders.add(symbol.getAddress());
-        return List.copyOf(holders);
-    }
-
-    // Apply one planned destination in its own transaction. Null means the
-    // edit committed with matching primary-symbol readback.
-    private String applyAddressName(AddressNameTarget target) {
-        Address address = target.address();
         int transaction = currentProgram.startTransaction("REA address name");
         boolean commit = false;
         try {
             Function function = currentProgram.getFunctionManager().getFunctionAt(address);
-            Symbol edited = editedNameSymbol(address);
+            SymbolTable table = currentProgram.getSymbolTable();
+            Symbol primary = function == null ? table.getPrimarySymbol(address) : function.getSymbol();
+            Namespace namespace = primary == null
+                ? currentProgram.getGlobalNamespace()
+                : primary.getParentNamespace();
+            String expected = primary == null ? name : symbolLeafName(primary, name);
+            for (Symbol symbol : table.getLabelOrFunctionSymbols(expected, namespace)) {
+                if (!address.equals(symbol.getAddress())) return false;
+            }
             if (function != null) {
-                function.setName(target.leaf(), SourceType.USER_DEFINED);
-            } else if (edited != null) {
-                edited.setName(target.leaf(), SourceType.USER_DEFINED);
+                function.setName(expected, SourceType.USER_DEFINED);
             } else {
-                Symbol created = currentProgram.getSymbolTable().createLabel(address, target.leaf(), SourceType.USER_DEFINED);
-                created.setPrimary();
+                if (primary != null && !primary.isDynamic()) {
+                    primary.setName(expected, SourceType.USER_DEFINED);
+                } else {
+                    Symbol created = table.createLabel(address, expected, SourceType.USER_DEFINED);
+                    created.setPrimary();
+                }
             }
             invalidateAnalysisCaches();
             Symbol readback = currentProgram.getSymbolTable().getPrimarySymbol(address);
-            commit = readback != null && target.leaf().equals(readback.getName());
-            return commit ? null : "readback_mismatch";
+            commit = readback != null && expected.equals(readback.getName());
+            return commit;
         }
-        catch (ghidra.util.exception.InvalidInputException exception) {
-            return "invalid_name";
-        }
-        catch (ghidra.util.exception.DuplicateNameException exception) {
-            return "duplicate_name";
+        catch (ghidra.util.exception.InvalidInputException | ghidra.util.exception.DuplicateNameException exception) {
+            return false;
         }
         finally {
             currentProgram.endTransaction(transaction, commit);
@@ -2019,17 +1975,7 @@ public final class ReaGhidraBridge extends HeadlessScript {
     private JsonElement setAddressName(JsonObject params) throws Exception {
         requireKeys(params, Set.of("document", "address", "name"));
         requireDocument(params);
-        String key = requireString(params, "address");
-        Address address = requireAddress(params, "address");
-        String name = requireString(params, "name");
-        // A single edit keeps request errors for unmapped addresses and
-        // unrepresentable text; other outcomes share the batch representation.
-        if (!currentProgram.getMemory().contains(address))
-            throw new RequestFailure("invalid_request", "Address is not mapped: " + canonicalAddress(address));
-        validateAnnotationText(name, "name");
-        Map<String, String> requested = new LinkedHashMap<>();
-        requested.put(key, name);
-        return applyAddressNames(requested);
+        return GSON.toJsonTree(applyAddressName(requireAddress(params, "address"), requireString(params, "name")));
     }
 
     private JsonElement setAddressesNames(JsonObject params) throws Exception {
@@ -2037,129 +1983,34 @@ public final class ReaGhidraBridge extends HeadlessScript {
         requireDocument(params);
         if (!params.has("names") || !params.get("names").isJsonObject())
             throw new RequestFailure("invalid_request", "names must be an object of address -> name");
-        Map<String, String> requested = new LinkedHashMap<>();
-        for (Map.Entry<String, JsonElement> entry : params.getAsJsonObject("names").entrySet())
-            requested.put(entry.getKey(), entry.getValue().getAsString());
-        return applyAddressNames(requested);
-    }
-
-    // Decide every request from the names held before any edit, so object
-    // member order never selects which address receives a name. Reply with
-    // per-key results and reasons; a contested destination is listed once in
-    // conflicts and failures refer to it by index.
-    private JsonObject applyAddressNames(Map<String, String> requested) {
-        Map<String, Address> addressesByKey = new LinkedHashMap<>();
         Map<Address, List<AddressNameRequest>> requestsByAddress = new LinkedHashMap<>();
-        for (Map.Entry<String, String> entry : requested.entrySet()) {
-            Address address = null;
+        JsonObject result = new JsonObject();
+        for (Map.Entry<String, JsonElement> entry : params.getAsJsonObject("names").entrySet()) {
             try {
-                address = parseReaAddress(entry.getKey());
+                Address address = parseReaAddress(entry.getKey());
                 requestsByAddress.computeIfAbsent(address, ignored -> new ArrayList<>())
-                    .add(new AddressNameRequest(entry.getKey(), address, entry.getValue()));
+                    .add(new AddressNameRequest(entry.getKey(), address, entry.getValue().getAsString()));
             }
             catch (RequestFailure failure) {
-                // The key keeps its own invalid_address outcome below.
-            }
-            addressesByKey.put(entry.getKey(), address);
-        }
-        Map<Address, AddressNameFailure> failures = new HashMap<>();
-        Map<AddressNameDestination, List<AddressNameTarget>> destinations = new LinkedHashMap<>();
-        for (Map.Entry<Address, List<AddressNameRequest>> selected : requestsByAddress.entrySet()) {
-            Address address = selected.getKey();
-            String name = selected.getValue().get(0).name;
-            if (selected.getValue().stream().anyMatch(request -> !request.name.equals(name))) {
-                failures.put(address, new AddressNameFailure("conflicting_alias_names", null));
-                continue;
-            }
-            if (!currentProgram.getMemory().contains(address)) {
-                failures.put(address, new AddressNameFailure("unmapped_address", null));
-                continue;
-            }
-            try {
-                AddressNameTarget target = addressNameTarget(address, name);
-                destinations.computeIfAbsent(target.destination(), ignored -> new ArrayList<>()).add(target);
-            }
-            catch (RequestFailure | ghidra.util.exception.InvalidInputException exception) {
-                failures.put(address, new AddressNameFailure("invalid_name", null));
+                result.addProperty(entry.getKey(), false);
             }
         }
-        // Reject a destination that several selected addresses request, or
-        // that another address holds, instead of letting order pick a winner.
-        List<AddressNameConflict> conflicts = new ArrayList<>();
-        List<AddressNameTarget> independent = new ArrayList<>();
-        for (List<AddressNameTarget> requesters : destinations.values()) {
-            AddressNameTarget first = requesters.get(0);
-            List<Address> holders = addressNameHolders(first);
-            String reason;
-            if (requesters.size() > 1) {
-                reason = "duplicate_requested_name";
-            } else if (holders.stream().allMatch(first.address()::equals)) {
-                independent.add(first);
-                continue;
-            } else if (holders.stream().anyMatch(holder ->
-                !holder.equals(first.address()) && !requestsByAddress.containsKey(holder))) {
-                reason = "name_held_by_unselected_address";
-            } else {
-                reason = "name_held_by_selected_address";
+        for (List<AddressNameRequest> requests : requestsByAddress.values()) {
+            String name = requests.get(0).name;
+            boolean conflictingAliasNames = requests.stream()
+                .anyMatch(request -> !request.name.equals(name));
+            boolean success = false;
+            if (!conflictingAliasNames) {
+                try {
+                    success = applyAddressName(requests.get(0).address, name);
+                }
+                catch (RequestFailure failure) {
+                    // Keep per-address failures in the existing batch result shape.
+                }
             }
-            AddressNameConflict conflict = new AddressNameConflict(
-                first.namespace(),
-                first.leaf(),
-                requesters.stream().map(AddressNameTarget::address).sorted().toList(),
-                holders
-            );
-            conflicts.add(conflict);
-            for (AddressNameTarget target : requesters)
-                failures.put(target.address(), new AddressNameFailure(reason, conflict));
+            for (AddressNameRequest request : requests)
+                result.addProperty(request.inputAddress, success);
         }
-        // Independent edits have distinct destinations that no other address
-        // holds, so their results do not depend on application order.
-        for (AddressNameTarget target : independent) {
-            String reason = applyAddressName(target);
-            if (reason != null) failures.put(target.address(), new AddressNameFailure(reason, null));
-        }
-        // Requesters belong to exactly one destination, so ordering conflicts
-        // by their first requester gives indexes independent of member order.
-        conflicts.sort(Comparator.comparing((AddressNameConflict conflict) -> conflict.requesters().get(0)));
-        Map<AddressNameConflict, Integer> indexes = new IdentityHashMap<>();
-        JsonArray contested = new JsonArray();
-        for (AddressNameConflict conflict : conflicts) {
-            indexes.put(conflict, contested.size());
-            JsonObject value = new JsonObject();
-            if (conflict.namespace().isGlobal()) value.add("namespace", JsonNull.INSTANCE);
-            else value.addProperty("namespace", conflict.namespace().getName(true));
-            value.addProperty("name", conflict.leaf());
-            value.add("requested_by", canonicalAddresses(conflict.requesters()));
-            value.add("held_by", canonicalAddresses(conflict.holders()));
-            contested.add(value);
-        }
-        JsonObject results = new JsonObject();
-        JsonObject failed = new JsonObject();
-        for (Map.Entry<String, Address> entry : addressesByKey.entrySet()) {
-            Address address = entry.getValue();
-            AddressNameFailure failure = address == null
-                ? new AddressNameFailure("invalid_address", null)
-                : failures.get(address);
-            results.addProperty(entry.getKey(), failure == null);
-            if (failure == null) continue;
-            JsonObject value = new JsonObject();
-            if (address == null) value.add("address", JsonNull.INSTANCE);
-            else value.addProperty("address", canonicalAddress(address));
-            value.addProperty("reason", failure.reason());
-            if (failure.conflict() == null) value.add("conflict", JsonNull.INSTANCE);
-            else value.addProperty("conflict", indexes.get(failure.conflict()));
-            failed.add(entry.getKey(), value);
-        }
-        JsonObject result = new JsonObject();
-        result.add("results", results);
-        result.add("failures", failed);
-        result.add("conflicts", contested);
-        return result;
-    }
-
-    private static JsonArray canonicalAddresses(List<Address> addresses) {
-        JsonArray result = new JsonArray();
-        for (Address address : addresses) result.add(canonicalAddress(address));
         return result;
     }
 
@@ -2275,6 +2126,9 @@ public final class ReaGhidraBridge extends HeadlessScript {
             throw new RequestFailure("invalid_request", "mode must be literal or regex");
         }
         boolean caseSensitive = requireBoolean(params, "case_sensitive");
+        List<InventoryItem> inventory = procedureSearch
+            ? procedures().stream().map(FunctionEntry::item).toList()
+            : strings();
         ValueMatcher matcher;
         if (mode.equals("literal") && !caseSensitive) {
             if (!params.has("literal_ascii_candidate"))
@@ -2288,26 +2142,7 @@ public final class ReaGhidraBridge extends HeadlessScript {
                 : regexMatcher(expression, caseSensitive);
         }
         JsonArray items = new JsonArray();
-        if (procedureSearch) {
-            // Search the names exact lookup accepts, keeping one row per
-            // procedure under its primary name.
-            for (FunctionEntry entry : procedures()) {
-                monitor.checkCancelled();
-                ProcedureNameMatch match = matchProcedureNames(entry, matcher);
-                if (!match.matched()) {
-                    continue;
-                }
-                JsonObject item = resultItem(entry.item, null);
-                if (!match.aliases().isEmpty()) {
-                    JsonArray aliases = new JsonArray();
-                    for (String alias : match.aliases()) aliases.add(alias);
-                    item.add("matched_aliases", aliases);
-                }
-                items.add(item);
-            }
-            return items;
-        }
-        for (InventoryItem item : strings()) {
+        for (InventoryItem item : inventory) {
             monitor.checkCancelled();
             if (!matcher.matches(item.value)) {
                 continue;
@@ -2317,36 +2152,6 @@ public final class ReaGhidraBridge extends HeadlessScript {
         return items;
     }
 
-    /**
-     * The one definition of the names that select a procedure, shared by exact
-     * lookup and search: its primary name and every other symbol at its exact
-     * entry, each in leaf or namespace-qualified spelling. A label inside the
-     * body never names the procedure. Matching secondary symbols are reported
-     * by their qualified names, sorted.
-     */
-    private ProcedureNameMatch matchProcedureNames(FunctionEntry entry, ValueMatcher matcher) throws Exception {
-        Function function = entry.function;
-        boolean primary = spellingMatches(function.getName(), entry.item.value, matcher);
-        Set<String> aliases = null;
-        for (Symbol symbol : currentProgram.getSymbolTable().getSymbols(function.getEntryPoint())) {
-            monitor.checkCancelled();
-            String qualified = symbol.getName(true);
-            if (!spellingMatches(symbol.getName(), qualified, matcher)) continue;
-            if (qualified.equals(entry.item.value)) {
-                primary = true;
-                continue;
-            }
-            if (aliases == null) aliases = new TreeSet<>();
-            aliases.add(qualified);
-        }
-        return new ProcedureNameMatch(primary, aliases == null ? List.of() : List.copyOf(aliases));
-    }
-
-    /** A leaf is the suffix of its qualified spelling, so a literal found in it is found in both. */
-    private static boolean spellingMatches(String leaf, String qualified, ValueMatcher matcher) {
-        return matcher.matches(qualified) || (!leaf.equals(qualified) && matcher.matches(leaf));
-    }
-
     private List<InventoryItem> names() throws Exception {
         if (nameInventory != null) {
             return nameInventory;
@@ -2449,13 +2254,26 @@ public final class ReaGhidraBridge extends HeadlessScript {
         // exact symbol name, even when every character is a hexadecimal digit.
         boolean explicitAddress = isExplicitReaAddress(value);
         if (!explicitAddress) {
-            // Imported labels (for example Mach-O _main) can share a function
-            // entry without becoming its primary symbol; search accepts the same.
-            ValueMatcher selector = value::equals;
             List<Function> matches = new ArrayList<>();
             for (FunctionEntry entry : procedures()) {
                 monitor.checkCancelled();
-                if (matchProcedureNames(entry, selector).matched()) matches.add(entry.function);
+                Function function = entry.function;
+                Symbol symbol = function.getSymbol();
+                String qualified = symbol == null ? function.getName() : symbol.getName(true);
+                boolean matchesName = function.getName().equals(value) || qualified.equals(value);
+                if (!matchesName) {
+                    // Imported labels (for example Mach-O _main) can share a
+                    // function entry without becoming its primary symbol. Only
+                    // exact entries qualify; an interior label is not a selector.
+                    for (Symbol entrySymbol : currentProgram.getSymbolTable().getSymbols(function.getEntryPoint())) {
+                        monitor.checkCancelled();
+                        if (entrySymbol.getName().equals(value) || entrySymbol.getName(true).equals(value)) {
+                            matchesName = true;
+                            break;
+                        }
+                    }
+                }
+                if (matchesName) matches.add(function);
             }
             if (matches.size() > 1)
                 throw new RequestFailure("ambiguous", "Ghidra procedure name is ambiguous: " + value +
@@ -5163,20 +4981,7 @@ public final class ReaGhidraBridge extends HeadlessScript {
 
     private record InventoryItem(Address address, String value, JsonObject facts, JsonObject symbol) {}
     private record AddressNameRequest(String inputAddress, Address address, String name) {}
-    private record AddressNameDestination(long namespace, String leaf) {}
-    private record AddressNameTarget(Address address, Namespace namespace, String leaf) {
-        AddressNameDestination destination() {
-            return new AddressNameDestination(namespace.getID(), leaf);
-        }
-    }
-    private record AddressNameConflict(Namespace namespace, String leaf, List<Address> requesters, List<Address> holders) {}
-    private record AddressNameFailure(String reason, AddressNameConflict conflict) {}
     private record FunctionEntry(Function function, InventoryItem item) {}
-    private record ProcedureNameMatch(boolean primary, List<String> aliases) {
-        boolean matched() {
-            return primary || !aliases.isEmpty();
-        }
-    }
     private record FunctionAnalysisObservation(JsonObject dossier, List<String> limitations, JsonObject relationshipCoverage, boolean decompilerFailed) {}
     private record CallBoundaryObservation(List<String> limitations, Integer unrepresentedCalleeCalls, JsonArray unresolvedCalls) {}
     private record SwiftStringLiteralDecode(JsonArray literals, JsonArray omissions) {}

bridge/ghidra/ReaGhidraRiscvCallingConvention.java

@@ -1,283 +0,0 @@
-import ghidra.app.script.GhidraScript;
-import ghidra.program.database.SpecExtension;
-import ghidra.program.model.data.DataType;
-import ghidra.program.model.data.DoubleDataType;
-import ghidra.program.model.data.Float16DataType;
-import ghidra.program.model.data.FloatDataType;
-import ghidra.program.model.data.FunctionDefinition;
-import ghidra.program.model.data.IntegerDataType;
-import ghidra.program.model.data.StructureDataType;
-import ghidra.program.model.lang.CompilerSpec;
-import ghidra.program.model.lang.Language;
-import ghidra.program.model.lang.PrototypeModel;
-import ghidra.program.model.lang.Register;
-import ghidra.program.model.listing.Function;
-import ghidra.program.model.listing.Parameter;
-import ghidra.program.model.listing.Program;
-import ghidra.program.model.listing.VariableStorage;
-import ghidra.program.model.pcode.Varnode;
-import ghidra.program.model.pcode.XmlEncode;
-import java.io.StringReader;
-import java.io.StringWriter;
-import java.util.ArrayList;
-import java.util.Iterator;
-import java.util.List;
-import java.util.regex.Pattern;
-import javax.xml.parsers.DocumentBuilderFactory;
-import javax.xml.transform.OutputKeys;
-import javax.xml.transform.TransformerFactory;
-import javax.xml.transform.dom.DOMSource;
-import javax.xml.transform.stream.StreamResult;
-import org.w3c.dom.Document;
-import org.w3c.dom.Element;
-import org.w3c.dom.Node;
-import org.w3c.dom.NodeList;
-import org.xml.sax.InputSource;
-
-/**
- * Apply the committed RISC-V calling-convention policy after analysis. Ghidra's generic RV32
- * compiler specification models ilp32d. Each policy derives a program-specific prototype from the
- * program's own default prototype, as its {@link Policy} row and docs/ghidra-riscv.md state. The
- * script installs the prototype as a specification extension and assigns it, with dynamic
- * storage, to every non-thunk function, external function and function definition.
- */
-public final class ReaGhidraRiscvCallingConvention extends GhidraScript {
-  static final String REPORT_KEY = "REA RISC-V calling convention";
-  /** RISC-V floating-point registers by ABI name: ft0-ft11, fs0-fs11 and fa0-fa7. */
-  private static final Pattern FLOAT_REGISTER = Pattern.compile("f[ast]\\d+");
-
-  /**
-   * What a policy changes in the default ilp32d prototype. Every policy also passes values of 9
-   * bytes or more, such as {@code long double}, by reference.
-   *
-   * @param floatEntryBytes the largest value a floating-point register may pass or return; 0
-   *     removes those entries and every rule that assigns floating-point storage
-   * @param preservesFloatRegisters whether fs0-fs11 stay preserved across calls
-   */
-  private record Policy(
-      String id, String prototype, int floatEntryBytes, boolean preservesFloatRegisters) {}
-
-  private static final List<Policy> POLICIES =
-      List.of(new Policy("ilp32-prototype-v1", "__rea_ilp32", 0, false));
-
-  @Override
-  public void run() throws Exception {
-    String[] arguments = getScriptArgs();
-    Policy policy =
-        POLICIES.stream()
-            .filter(candidate -> arguments.length == 1 && candidate.id().equals(arguments[0]))
-            .findFirst()
-            .orElseThrow(
-                () ->
-                    new IllegalArgumentException(
-                        "REA RISC-V calling convention requires one of the policies "
-                            + POLICIES.stream().map(Policy::id).toList()));
-    Language language = currentProgram.getLanguage();
-    if (!language.getProcessor().toString().equals("RISCV")
-        || currentProgram.getDefaultPointerSize() != 4)
-      throw new IllegalStateException(
-          "REA " + policy.id() + " requires a 32-bit RISC-V program, not "
-              + language.getLanguageID());
-    CompilerSpec spec = currentProgram.getCompilerSpec();
-    new SpecExtension(currentProgram)
-        .addReplaceCompilerSpecExtension(
-            derive(spec.getDefaultCallingConvention(), spec, language, policy), monitor);
-    PrototypeModel model =
-        currentProgram.getCompilerSpec().getCallingConvention(policy.prototype());
-    if (model == null)
-      throw new IllegalStateException("REA " + policy.prototype() + " was not installed");
-    selfCheck(model, policy, language);
-    int functions = 0;
-    List<Function> callables = new ArrayList<>();
-    currentProgram.getFunctionManager().getFunctions(true).forEach(callables::add);
-    currentProgram.getFunctionManager().getExternalFunctions().forEach(callables::add);
-    for (Function function : callables) {
-      // A thunk's signature is its target's; the target is in this list.
-      if (function.isThunk()) continue;
-      if (function.hasCustomVariableStorage()) function.setCustomVariableStorage(false);
-      function.setCallingConvention(policy.prototype());
-      if (policy.floatEntryBytes() == 0) {
-        List<VariableStorage> storage = new ArrayList<>();
-        storage.add(function.getReturn().getVariableStorage());
-        for (Parameter parameter : function.getParameters())
-          storage.add(parameter.getVariableStorage());
-        // An untyped function has no assigned storage yet; the decompiler applies the
-        // prototype when it recovers one.
-        requireIntegerStorage(
-            storage.toArray(VariableStorage[]::new), function.getName(true), true);
-      }
-      functions += 1;
-    }
-    int definitions = 0;
-    Iterator<DataType> types = currentProgram.getDataTypeManager().getAllDataTypes();
-    while (types.hasNext()) {
-      if (!(types.next() instanceof FunctionDefinition definition)) continue;
-      definition.setCallingConvention(policy.prototype());
-      definitions += 1;
-    }
-    // Written last: any failure above leaves no report, and REA refuses the session.
-    currentProgram.getOptions(Program.PROGRAM_INFO).setString(
-        REPORT_KEY,
-        "{\"policy\":\"" + policy.id() + "\",\"functions\":" + functions
-            + ",\"definitions\":" + definitions + "}");
-    println(
-        "REA RISC-V " + policy.prototype() + ": functions=" + functions
-            + " definitions=" + definitions);
-  }
-
-  /** The default ilp32d prototype changed as the policy states. */
-  private static String derive(
-      PrototypeModel base, CompilerSpec spec, Language language, Policy policy) throws Exception {
-    XmlEncode encoder = new XmlEncode();
-    base.encode(encoder, spec.getPcodeInjectLibrary());
-    DocumentBuilderFactory factory = DocumentBuilderFactory.newInstance();
-    factory.setFeature("http://apache.org/xml/features/disallow-doctype-decl", true);
-    Document document =
-        factory.newDocumentBuilder().parse(new InputSource(new StringReader(encoder.toString())));
-    Element root = document.getDocumentElement();
-    if (!root.getTagName().equals("prototype"))
-      throw new IllegalStateException("Unexpected default prototype encoding " + root.getTagName());
-    root.setAttribute("name", policy.prototype());
-    List<Element> floatEntries = new ArrayList<>();
-    NodeList entries = root.getElementsByTagName("pentry");
-    for (int index = 0; index < entries.getLength(); index += 1) {
-      Element entry = (Element) entries.item(index);
-      if (entry.getAttribute("storage").equals("float")) floatEntries.add(entry);
-    }
-    if (floatEntries.isEmpty())
-      throw new IllegalStateException("Default prototype has no floating-point entries");
-    if (policy.floatEntryBytes() == 0) {
-      List<Node> removed = new ArrayList<>(floatEntries);
-      NodeList rules = root.getElementsByTagName("rule");
-      for (int index = 0; index < rules.getLength(); index += 1) {
-        Element rule = (Element) rules.item(index);
-        if (usesFloatStorage(rule)) removed.add(rule);
-      }
-      if (removed.size() == floatEntries.size())
-        throw new IllegalStateException("Default prototype has no floating-point rules to remove");
-      for (Node node : removed) node.getParentNode().removeChild(node);
-    } else
-      for (Element entry : floatEntries)
-        entry.setAttribute("maxsize", Integer.toString(policy.floatEntryBytes()));
-    // Values over 2 x XLEN go by reference. Returns need no rule: a value that the return
-    // registers cannot hold already becomes a caller buffer passed in a0.
-    NodeList inputs = root.getElementsByTagName("input");
-    if (inputs.getLength() != 1)
-      throw new IllegalStateException("Default prototype has no single input list");
-    Element input = (Element) inputs.item(0);
-    Element last = null;
-    for (Node child = input.getFirstChild(); child != null; child = child.getNextSibling())
-      if (child instanceof Element element && element.getTagName().equals("rule")) last = element;
-    if (last == null || !joinsAnyValue(last))
-      throw new IllegalStateException("Default prototype's input list does not end with a join");
-    Element byReference = document.createElement("rule");
-    Element datatype = document.createElement("datatype");
-    datatype.setAttribute("name", "any");
-    datatype.setAttribute("minsize", "9");
-    byReference.appendChild(datatype);
-    byReference.appendChild(document.createElement("convert_to_ptr"));
-    input.insertBefore(byReference, last);
-    if (!policy.preservesFloatRegisters()) {
-      NodeList killedLists = root.getElementsByTagName("killedbycall");
-      Element killed = killedLists.getLength() == 0 ? null : (Element) killedLists.item(0);
-      if (killed == null) {
-        killed = document.createElement("killedbycall");
-        root.appendChild(killed);
-      }
-      List<Element> moved = new ArrayList<>();
-      NodeList preservedLists = root.getElementsByTagName("unaffected");
-      for (int list = 0; list < preservedLists.getLength(); list += 1) {
-        NodeList preserved = preservedLists.item(list).getChildNodes();
-        for (int index = 0; index < preserved.getLength(); index += 1) {
-          if (preserved.item(index) instanceof Element varnode
-              && isFloatRegister(varnode, language))
-            moved.add(varnode);
-        }
-      }
-      for (Element varnode : moved) {
-        varnode.getParentNode().removeChild(varnode);
-        killed.appendChild(varnode);
-      }
-    }
-    StringWriter xml = new StringWriter();
-    var transformer = TransformerFactory.newInstance().newTransformer();
-    transformer.setOutputProperty(OutputKeys.OMIT_XML_DECLARATION, "yes");
-    transformer.transform(new DOMSource(document), new StreamResult(xml));
-    return xml.toString();
-  }
-
-  /** The installed prototype places each class of value as its policy states. */
-  private void selfCheck(PrototypeModel model, Policy policy, Language language) {
-    StructureDataType pair = new StructureDataType("rea_float_pair", 0);
-    pair.add(FloatDataType.dataType);
-    pair.add(FloatDataType.dataType);
-    VariableStorage[] storage =
-        model.getStorageLocations(
-            currentProgram,
-            new DataType[] {
-              DoubleDataType.dataType, FloatDataType.dataType, DoubleDataType.dataType,
-              IntegerDataType.dataType, pair, Float16DataType.dataType
-            },
-            false);
-    VariableStorage quad = storage[storage.length - 1];
-    if (quad.size() != currentProgram.getDefaultPointerSize() || quad.getRegister() == null)
-      throw new IllegalStateException(
-          "REA " + policy.prototype() + " does not pass a 16-byte value by reference: " + quad);
-    if (policy.floatEntryBytes() == 0)
-      requireIntegerStorage(storage, policy.prototype() + " self-check", false);
-    if (policy.preservesFloatRegisters()) return;
-    for (Varnode preserved : model.getUnaffectedList()) {
-      Register register = language.getRegister(preserved.getAddress(), preserved.getSize());
-      if (register != null && FLOAT_REGISTER.matcher(register.getName()).matches())
-        throw new IllegalStateException(
-            "REA " + policy.prototype() + " still preserves " + register.getName());
-    }
-  }
-
-  private static boolean joinsAnyValue(Element rule) {
-    List<Element> children = new ArrayList<>();
-    for (Node child = rule.getFirstChild(); child != null; child = child.getNextSibling())
-      if (child instanceof Element element) children.add(element);
-    return children.size() == 2
-        && children.get(0).getTagName().equals("datatype")
-        && children.get(0).getAttribute("name").equals("any")
-        && children.get(1).getTagName().equals("join");
-  }
-
-  /** Whether a rule's action, at any depth, assigns floating-point storage. */
-  private static boolean usesFloatStorage(Element element) {
-    NodeList children = element.getChildNodes();
-    for (int index = 0; index < children.getLength(); index += 1) {
-      if (!(children.item(index) instanceof Element child)) continue;
-      if (child.getAttribute("storage").equals("float") || usesFloatStorage(child)) return true;
-    }
-    return false;
-  }
-
-  private static boolean isFloatRegister(Element varnode, Language language) {
-    if (!varnode.getTagName().equals("varnode")
-        || !varnode.getAttribute("space").equals("register"))
-      return false;
-    Register register =
-        language.getRegister(
-            language.getAddressFactory().getRegisterSpace()
-                .getAddress(Long.decode(varnode.getAttribute("offset"))),
-            Integer.parseInt(varnode.getAttribute("size")));
-    return register != null && FLOAT_REGISTER.matcher(register.getName()).matches();
-  }
-
-  private static void requireIntegerStorage(
-      VariableStorage[] storage, String owner, boolean allowUnassigned) {
-    for (VariableStorage item : storage) {
-      if (item.isBadStorage() || (!allowUnassigned && item.isUnassignedStorage()))
-        throw new IllegalStateException("REA RISC-V storage unresolved for " + owner);
-      List<Register> registers = item.getRegisters();
-      if (registers == null) continue; // stack-only storage
-      for (Register register : registers) {
-        if (FLOAT_REGISTER.matcher(register.getName()).matches())
-          throw new IllegalStateException(
-              "REA RISC-V storage still uses " + register.getName() + " for " + owner);
-      }
-    }
-  }
-}

bridge/native/ReaNativeUI.swift

@@ -65,10 +65,7 @@ func observe(_ request: Request) async throws -> [String: Any] {
   guard SHA256.hash(data: executableBytes).map({ String(format: "%02x", $0) }).joined() == request.sha256 else {
     try fail("target-mismatch", "Running executable bytes differ from the active target digest")
   }
-  // .optionIncludingWindow omits a selected window while it is off screen, which
-  // is not absence: select from every window, and let capture report what it can.
-  guard let windows = (CGWindowListCopyWindowInfo([.optionAll], kCGNullWindowID) as? [[String: Any]])?
-    .filter({ ($0[kCGWindowNumber as String] as? NSNumber)?.uint32Value == request.window_id }),
+  guard let windows = CGWindowListCopyWindowInfo([.optionIncludingWindow], request.window_id) as? [[String: Any]],
     windows.count == 1, let window = windows.first,
     (window[kCGWindowOwnerPID as String] as? NSNumber)?.int32Value == request.pid,
     (window[kCGWindowLayer as String] as? NSNumber)?.intValue == 0,

bridge/process/ProcessRunTokenReader.swift

@@ -15,8 +15,6 @@ struct ProcessIdentityObservation: Encodable {
   let effective_uid: UInt32?
   let lifecycle: String?
   let relation: ProcessRelationObservation?
-  /** Display-only kernel accounting name (p_comm, at most MAXCOMLEN bytes). */
-  let name: String?
   let reason: String?
 }
 
@@ -33,7 +31,6 @@ struct ProcessMetadata {
   let parentPid: Int32
   let processGroupId: Int32
   let pointerSize: Int
-  let name: String
 }
 
 struct ProcessSnapshot {
@@ -95,8 +92,7 @@ func readProcessSnapshot(
             lifecycle: process.kp_proc.p_stat == SZOMB ? "zombie" : "non-zombie",
             parentPid: process.kp_eproc.e_ppid,
             processGroupId: process.kp_eproc.e_pgid,
-            pointerSize: process.kp_proc.p_flag & P_LP64 != 0 ? 8 : 4,
-            name: processName(process)
+            pointerSize: process.kp_proc.p_flag & P_LP64 != 0 ? 8 : 4
           )
         )
       },
@@ -107,13 +103,6 @@ func readProcessSnapshot(
   return ProcessSnapshot(metadata: [:], failure: "process_table_failed_\(ENOMEM)")
 }
 
-/** Decode the NUL-terminated accounting name; invalid UTF-8 is replaced for display. */
-private func processName(_ process: kinfo_proc) -> String {
-  withUnsafeBytes(of: process.kp_proc.p_comm) { bytes in
-    String(decoding: bytes.prefix { $0 != 0 }, as: UTF8.self)
-  }
-}
-
 func readProcessIdentities(pids: [Int32]) -> [ProcessIdentityObservation] {
   readProcessIdentities(pids: pids, snapshot: readProcessSnapshot())
 }
@@ -141,7 +130,6 @@ func readProcessIdentities(
         effective_uid: nil,
         lifecycle: nil,
         relation: nil,
-        name: nil,
         reason: "not-in-snapshot"
       )
     }
@@ -156,7 +144,6 @@ func readProcessIdentities(
         parent_pid: metadata.parentPid,
         process_group_id: metadata.processGroupId
       ),
-      name: metadata.name,
       reason: nil
     )
   }
@@ -170,25 +157,12 @@ private func unavailableIdentity(pid: Int32, reason: String) -> ProcessIdentityO
     effective_uid: nil,
     lifecycle: nil,
     relation: nil,
-    name: nil,
     reason: reason
   )
 }
 
-enum ProcargsMalformedStage: String, CaseIterable {
-  case header
-  case argumentCount = "argument_count"
-  case executablePath = "executable_path"
-  case pointerSize = "pointer_size"
-  case pathPadding = "path_padding"
-  case arguments
-  case terminator
-  case trailingEntries = "trailing_entries"
-}
-
 enum RunTokenReadError: Error {
   case invalidBuffer
-  case invalidBufferAt(ProcargsMalformedStage)
   case duplicateToken
   case invalidTokenEncoding
   case environmentUnavailable
@@ -228,22 +202,6 @@ func processRunTokenObservation(
   parse: Result<ParsedRunToken, RunTokenReadError>,
   codeSigningFlags: () -> UInt32?
 ) -> RunTokenObservation {
-  // Native inspection restrictions apply even when argv is incomplete or
-  // overwritten, before parsing reaches the environment. Keep this fact at
-  // the native boundary; cleanup still decides whether the process is related.
-  func withheldEnvironment() -> RunTokenObservation? {
-    guard let flags = codeSigningFlags() else { return nil }
-    if (flags & csPlatformBinary) != 0 {
-      return unavailable(pid: pid, reason: "platform_binary_environment_withheld")
-    }
-    if (flags & csRestrict) != 0 {
-      return unavailable(pid: pid, reason: "restricted_process_environment_withheld")
-    }
-    return nil
-  }
-  func unavailableEnvironment(_ reason: String) -> RunTokenObservation {
-    withheldEnvironment() ?? unavailable(pid: pid, reason: reason)
-  }
   switch parse {
   case .success(let parsed):
     if let runId = parsed.runId {
@@ -254,25 +212,38 @@ func processRunTokenObservation(
     if parsed.environmentEntryCount > 0 {
       return RunTokenObservation(pid: pid, state: "readable", run_id: nil, reason: nil)
     }
-    if let withheld = withheldEnvironment() { return withheld }
+    let flags = codeSigningFlags()
+    if let flags, (flags & csPlatformBinary) != 0 {
+      return unavailable(pid: pid, reason: "platform_binary_environment_withheld")
+    }
+    if let flags, (flags & csRestrict) != 0 {
+      return unavailable(pid: pid, reason: "restricted_process_environment_withheld")
+    }
     return RunTokenObservation(pid: pid, state: "readable", run_id: nil, reason: nil)
   case .failure(let failure):
     switch failure {
     case .environmentUnavailable:
-      return unavailableEnvironment("environment_unavailable")
+      let flags = codeSigningFlags()
+      if let flags, (flags & csPlatformBinary) != 0 {
+        return unavailable(pid: pid, reason: "platform_binary_environment_withheld")
+      }
+      if let flags, (flags & csRestrict) != 0 {
+        return unavailable(pid: pid, reason: "restricted_process_environment_withheld")
+      }
+      return unavailable(pid: pid, reason: "environment_unavailable")
     case .ambiguousEnvironmentBoundary:
-      return unavailableEnvironment("ambiguous_environment_boundary")
-    // These failures already establish that token bytes were available.
+      if let flags = codeSigningFlags(), (flags & csRestrict) != 0 {
+        return unavailable(pid: pid, reason: "restricted_process_environment_withheld")
+      }
+      return unavailable(pid: pid, reason: "ambiguous_environment_boundary")
     case .duplicateToken:
       return unavailable(pid: pid, reason: "duplicate_run_token")
     case .invalidTokenEncoding:
       return unavailable(pid: pid, reason: "invalid_run_token_encoding")
     case .appleVectorUnavailable:
-      return unavailableEnvironment("apple_vector_unavailable")
+      return unavailable(pid: pid, reason: "apple_vector_unavailable")
     case .invalidBuffer:
-      return unavailableEnvironment("malformed_procargs")
-    case .invalidBufferAt(let stage):
-      return unavailableEnvironment("malformed_procargs_\(stage.rawValue)")
+      return unavailable(pid: pid, reason: "malformed_procargs")
     }
   }
 }
@@ -331,30 +302,27 @@ func parseProcessEnvironment(
   in bytes: [UInt8],
   pointerSize: Int = MemoryLayout<UnsafeRawPointer>.size
 ) throws -> ParsedRunToken {
-  guard bytes.count >= MemoryLayout<Int32>.size else { throw RunTokenReadError.invalidBufferAt(.header) }
+  guard bytes.count >= MemoryLayout<Int32>.size else { throw RunTokenReadError.invalidBuffer }
   let argc = bytes.withUnsafeBytes { $0.loadUnaligned(as: Int32.self).littleEndian }
-  guard argc >= 0, Int(argc) <= bytes.count else { throw RunTokenReadError.invalidBufferAt(.argumentCount) }
+  guard argc >= 0, Int(argc) <= bytes.count else { throw RunTokenReadError.invalidBuffer }
   var offset = MemoryLayout<Int32>.size
   guard let executablePath = readString(in: bytes, offset: &offset) else {
-    throw RunTokenReadError.invalidBufferAt(.executablePath)
+    throw RunTokenReadError.invalidBuffer
   }
-  guard pointerSize == 4 || pointerSize == 8 else { throw RunTokenReadError.invalidBufferAt(.pointerSize) }
+  guard pointerSize == 4 || pointerSize == 8 else { throw RunTokenReadError.invalidBuffer }
   let pathRecordSize = Array("executable_path=".utf8).count + executablePath.count + 1
   let padding = (pointerSize - pathRecordSize % pointerSize) % pointerSize
   guard offset + padding <= bytes.count,
         bytes[offset..<(offset + padding)].allSatisfy({ $0 == 0 }) else {
-    throw RunTokenReadError.invalidBufferAt(.pathPadding)
+    throw RunTokenReadError.invalidBuffer
   }
   offset += padding
-  let tokenPrefix = Array("REA_PROCESS_RUN_ID=".utf8)
-  var tokenInArgument = false
   for _ in 0..<argc {
-    guard let argument = readString(in: bytes, offset: &offset, allowEmpty: true) else {
-      throw RunTokenReadError.invalidBufferAt(.arguments)
+    guard readString(in: bytes, offset: &offset, allowEmpty: true) != nil else {
+      throw RunTokenReadError.invalidBuffer
     }
-    tokenInArgument = tokenInArgument || argument.starts(with: tokenPrefix)
   }
-  guard bytes.last == 0 else { throw RunTokenReadError.invalidBufferAt(.terminator) }
+  guard bytes.last == 0 else { throw RunTokenReadError.invalidBuffer }
   if offset == bytes.count {
     throw RunTokenReadError.environmentUnavailable
   }
@@ -372,7 +340,7 @@ func parseProcessEnvironment(
       continue
     }
     guard let entry = readString(in: bytes, offset: &offset) else {
-      throw RunTokenReadError.invalidBufferAt(.trailingEntries)
+      throw RunTokenReadError.invalidBuffer
     }
     trailingEntries.append(entry)
   }
@@ -393,28 +361,22 @@ func parseProcessEnvironment(
     throw RunTokenReadError.appleVectorUnavailable
   }
   if trailingEntries[appleVectorStart...].contains(where: {
-    $0.starts(with: tokenPrefix)
+    $0.starts(with: Array("REA_PROCESS_RUN_ID=".utf8))
   }) {
     throw RunTokenReadError.ambiguousEnvironmentBoundary
   }
   let environmentEntries = trailingEntries[..<appleVectorStart]
   var found: String?
   for entry in environmentEntries {
-    if entry.starts(with: tokenPrefix) {
+    if entry.starts(with: Array("REA_PROCESS_RUN_ID=".utf8)) {
       guard found == nil else { throw RunTokenReadError.duplicateToken }
-      let value = entry.dropFirst(tokenPrefix.count)
+      let value = entry.dropFirst("REA_PROCESS_RUN_ID=".utf8.count)
       guard let decoded = String(bytes: value, encoding: .utf8) else {
         throw RunTokenReadError.invalidTokenEncoding
       }
       found = decoded
     }
   }
-  // A changed process title can overwrite the original argument boundaries,
-  // causing a real environment entry to be consumed as an argument. A real
-  // argument can have this form too, so it proves neither ownership nor absence.
-  if tokenInArgument {
-    throw RunTokenReadError.ambiguousEnvironmentBoundary
-  }
   return ParsedRunToken(runId: found, environmentEntryCount: environmentEntries.count)
 }
 

bridge/pwntools/layout_impl.py

@@ -16,10 +16,10 @@ PROFILE = "[email protected];[email protected];[email protected]"
 PACKAGES = {"pwntools": "4.15.0", "pyelftools": "0.33", "unicorn": "2.1.2"}
 OUTPUT_BYTES = 64 * 1024 * 1024
 # (e_machine, ELF class bits, byte order) -> architecture pwntools must also report.
-PROFILES = {(62, 64, "little"): "amd64", (183, 64, "little"): "aarch64", (3, 32, "little"): "i386",
-            (40, 32, "little"): "arm", (8, 32, "little"): "mips", (8, 32, "big"): "mips"}
-PROFILE_SCOPE = ("Layout profile requires ELF64 x86-64, ELF64 AArch64 little-endian, ELF32 i386, "
-                 "ELF32 ARM little-endian or ELF32 MIPS little- or big-endian objects.")
+PROFILES = {(62, 64, "little"): "amd64", (3, 32, "little"): "i386", (40, 32, "little"): "arm",
+            (8, 32, "little"): "mips", (8, 32, "big"): "mips"}
+PROFILE_SCOPE = ("Layout profile requires ELF64 x86-64, ELF32 i386, ELF32 ARM little-endian "
+                 "or ELF32 MIPS little- or big-endian objects.")
 
 
 class LayoutFailure(Exception):

docs/.vitepress/config.ts

@@ -70,7 +70,6 @@ export default defineConfig({
           { text: "Apple applications", link: "/apple-application-analysis" },
           { text: "Desktop installations", link: "/desktop-applications" },
           { text: "Firmware", link: "/firmware-analysis" },
-          { text: "iNES containers", link: "/ines-containers" },
           { text: "SQLite databases", link: "/sqlite-databases" },
           { text: "Packet captures", link: "/packet-captures" },
           { text: "Signal recordings", link: "/signal-recordings" },

docs/adb-device-analysis.md

@@ -257,12 +257,12 @@ beyond already-connected devices (`adb connect`) are not exposed yet.
 
 ## Real verification
 
-`npm run verify:adb` exercises observation and transfer operations against a live device. It
+`npm run verify:adb` exercises every operation against a live device. It
 requires `adb` (or `REA_ADB_PATH`) and any attached emulator or phone;
 `--serial` selects one when several are attached, `--pull PACKAGE` pulls a
-real package and verifies the returned digests against the files on disk.
-The optional `--install-apk` lifecycle is unavailable until the selected APK
-identity and device cleanup ownership can be established safely.
+real package and verifies the returned digests against the files on disk,
+and `--install-apk PATH` drives a full install → resolve → uninstall
+lifecycle with a lane-owned probe.
 
 Record: verified against adb 34.0.5 on Linux against an Android 14
 (API 34) x86_64 emulator — all operations above, a 224-package inventory,

docs/agent-environments.md

@@ -1149,12 +1149,7 @@ global conflict involving an equal pair is not used to normalize either pair; th
 
 A step agrees when the statuses and the normalised bodies are equal. The report gives agreement overall, per probe and
 per tool, `agreement_ignoring_order` for steps that differ only in item order, and each step's differences, at most 20,
-with a JSON pointer and both values cut short. Each step reports `differences_total` before that cap,
-`differences_omitted`, and `differences_truncated` (true when entries were omitted). Agreement and categories use the
-complete comparison. Omitted entries are not retained, so `--full-output` cannot recover them; inspect the original
-capture and probe Evidence to investigate beyond the returned pointers.
-
-The difference categories are:
+with a JSON pointer and both values cut short:
 
 | Category        | Meaning                                                                                                      |
 | --------------- | ------------------------------------------------------------------------------------------------------------ |

docs/architecture.mermaid

@@ -8,7 +8,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/>typed capability bindings: construction, availability and retryable lifetimes<br/>pure capability declarations feed provider catalogs"]
+        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"]
     end
 
     subgraph "Adapters"
@@ -23,7 +23,6 @@ graph TD
         SESSION["SessionProviderRouter + BinarySession<br/>one immutable deep binding per target<br/>disjoint auxiliary routing"]
         REGISTRY["AnalysisProviderRegistry<br/>sorted deep candidates<br/>deterministic selection, no fallback<br/>ProviderInspectionScope: prerequisite observation lifetime"]
         RECORDS["src/application/investigation/<br/>composed InvestigationRecords + narrow ports<br/>EvidenceLedger and Unknown ownership"]
-        LIFETIMES["CapabilityScope<br/>host-owned service close capabilities<br/>released peers removed; failed cleanup retained for retry"]
         SNAPSHOT["BinarySessionRecords + AnalysisSnapshotCache<br/>binary target/profile snapshots and session file ownership<br/>record coordination and post-commit notifications"]
         JS_RECON["src/application/javascript/ + src/artifacts/javascript/<br/>JavaScript artifact reconstruction<br/>directory/ASAR reads<br/>AST-only bundle projection"]
     end
@@ -100,7 +99,6 @@ graph TD
     MAIN --> COMPOSITION
     CLI --> COMPOSITION
     SERVER --> COMPOSITION
-    COMPOSITION --> LIFETIMES
     COMPOSITION --> SESSION
     APP --> FIRMWARE
     FIRMWARE --> PROCESS
@@ -151,7 +149,8 @@ graph TD
     OBJDUMP --> DOMAIN
     COMPOSITION --> RIZIN
     RIZIN --> DOMAIN
-    COMPOSITION --> GDB
+    CLI --> GDB
+    SERVER --> GDB
     GDB --> PROCESS
     GDB --> DOMAIN
     HOPPER --> HOPPER_BRIDGE
@@ -207,7 +206,8 @@ graph TD
     NATIVE_READERS --> DOMAIN
     COMPOSITION --> FORMAT_READERS
     FORMAT_READERS --> DOMAIN
-    COMPOSITION --> RUNTIME
+    SERVER --> RUNTIME
+    CLI --> RUNTIME
     RUNTIME --> DOMAIN
     PROCESS --> FILESYSTEM
     AUX --> FILESYSTEM

docs/binary-diagnostics.md

@@ -9,11 +9,9 @@ ordinary binary inspection use the same modular capability.
 ## Bring your own engine
 
 Real verification covers **Linux x64** hosts and **EXEC/DYN/REL** objects in
-these profiles: ELF64 x86-64, ELF64 little-endian AArch64, ELF32 i386, ELF32
-little-endian ARM and ELF32 little- or big-endian MIPS. Other machines, classes
-and byte orders, including big-endian ARM, return `unsupported_target`. Other
-hosts, including Linux arm64, return `capability_unavailable` naming the
-detected host before any target is read. Provide an absolute
+these profiles: ELF64 x86-64, ELF32 i386, ELF32 little-endian ARM and ELF32
+little- or big-endian MIPS. Other machines, classes and byte orders, including
+AArch64 and big-endian ARM, return `unsupported_target`. Provide an absolute
 Python executable whose environment already contains unchanged pwntools 4.15.0,
 pyelftools 0.33 and Unicorn 2.1.2:
 
@@ -426,10 +424,8 @@ rea inspect-native-exports ./libexample.so --detail summary --evidence_output ./
   without an export directory is a complete empty inventory.
 - ELF rows list defined `.dynsym` symbols with global, weak or GNU-unique
   binding and default or protected visibility. Each row keeps `value`
-  (`st_value` as stored; bit 0 marks Thumb code on 32-bit ARM), `size`, `type`,
-  `binding` and `visibility` (`"default"` or `"protected"`; `"unknown"` in older
-  historical Evidence where visibility was not recorded). ELF string tables do
-  not declare a text encoding. Names that
+  (`st_value` as stored; bit 0 marks Thumb code on 32-bit ARM), `size`, `type`
+  and `binding`. ELF string tables do not declare a text encoding. Names that
   contain non-ASCII bytes are decoded as UTF-8 when those bytes form valid
   UTF-8; `name_utf8_decodable` records whether the non-ASCII name bytes are
   valid UTF-8 and `name_bytes_base64` retains those exact bytes (`null` for

docs/browser-observation.md

@@ -500,7 +500,7 @@ REA retains local observation data and removes only URL userinfo credentials, ex
   connection/frame inventories; matching direction/opcode sequences alone do
   not prove alignment after drops. Redirect resource types use only shared known metadata:
   an omitted type leaves equality unknown rather than proving a modification.
-- Console observations with a stack source retain call type, argument types, the CDP `Runtime.Timestamp` in milliseconds since Unix epoch, and source location. An absent or invalid timestamp is `null` and makes `console_events` incomplete; an observed zero remains zero. Argument types are listed by CDP argument position. An absent or non-array argument inventory is `null`, and a malformed argument keeps its position as `unknown`; either makes `console_events` incomplete, while an observed empty inventory remains `[]`. A malformed stack or top stack frame is not replaced by its caller: the console event is excluded, and a request initiator location or WebMCP `registration_source` is `null`; each is reported as `invalid_protocol_value`. Source locations are CDP's zero-based lines and UTF-16 columns. A negative column, which Chrome reports on the first line of some inline scripts, is kept as reported and does not locate a column in the source URL; an invalid line or a non-integer column is `null` (WebMCP `registration_source` is `null`) and is reported as `invalid_protocol_value`. This epoch-millisecond clock is separate from the monotonic-second timestamps in `observe-web-session`. When console text capture is selected, already-delivered primitive values are retained verbatim with their original `argument_index`; objects, getters, and remote properties are never expanded. Text capture is `unavailable` when the argument inventory is unknown.
+- Console observations with a stack source retain call type, argument types, the CDP `Runtime.Timestamp` in milliseconds since Unix epoch, and source location. An absent or invalid timestamp is `null` and makes `console_events` incomplete; an observed zero remains zero. Argument types are listed by CDP argument position. An absent or non-array argument inventory is `null`, and a malformed argument keeps its position as `unknown`; either makes `console_events` incomplete, while an observed empty inventory remains `[]`. A malformed stack or top stack frame is not replaced by its caller: the console event is excluded, and a request initiator location or WebMCP `registration_source` is `null`; each is reported as `invalid_protocol_value`. This epoch-millisecond clock is separate from the monotonic-second timestamps in `observe-web-session`. When console text capture is selected, already-delivered primitive values are retained verbatim with their original `argument_index`; objects, getters, and remote properties are never expanded. Text capture is `unavailable` when the argument inventory is unknown.
 - WebSocket observations retain direction, opcode, and payload byte length. A missing or malformed CDP opcode is returned as `null`, with opcode-dependent payload byte length and shape also `null`, and marks `websocket_frames` incomplete. Missing or wrong-typed payload data is not treated as empty; its byte length is `null`, and a text payload shape is unknown. Numeric opcode `0` and an observed empty payload remain distinct from missing data. Opcode is nullable in the public inspection schema, so clients must handle unknown protocol values. When shape capture is selected, text messages are classified as text or complete value-free JSON shape; binary bytes, hashes, prefixes, and raw payloads are never retained.
 - Storage observations always redact values. Key names, IndexedDB names, and cache names require `include_storage_keys`; stable content fingerprints require the additional `include_storage_fingerprints` selection. Cookie fingerprints cover cookies applicable to the current main-frame URL, including its path, rather than every cookie path on that origin. Other storage remains scoped to the origin. Cache fingerprints hash all decoded response bytes, including bodies above 64 KiB, subject to the [64 MiB per-message CDP limit](#request-boundary). Missing or undecodable cache bodies and partial IndexedDB remote objects make fingerprint coverage incomplete, so identical observations remain `unknown`.
 - Unavailable or malformed storage inventories mark `storage_keys` unavailable, even without fingerprints. Comparisons suppress inferred key additions and removals while preserving modifications proven by complete fingerprints on both sides. Previously exported captures are not retroactively corrected; recapture them to obtain these coverage markers.

docs/capability-composition.md

@@ -1,107 +0,0 @@
-# Capability composition and ownership
-
-REA keeps domain contracts and shared workflows separate from provider adapters
-and CLI/MCP translation. A capability can have several provider identities; a
-provider can contribute operations to several capabilities. Those associations
-are source facts, while host availability is an observation.
-
-## Source declarations and runtime bindings
-
-`src/composition/capabilityDeclarations.ts` contains static provider identities,
-named contract-group references and precise operation subsets. Complete groups
-refer to `TOOL_CONTRACT_GROUPS` in the existing contract owner; family definitions
-and provider catalogs read the same arrays, so a new group operation is included
-without updating a copied provider list. Metadata imports only the group ID type
-and pure metadata leaves; it must not load factories, schemas, engines or
-generated catalogs. Catalog generation resolves groups and subsets against the
-canonical contracts and rejects unknown groups/operations and conflicting
-identities. New provider provenance must come from the implementation
-that actually produces the Evidence, including format-specific capture adapters
-and derived workflows.
-
-`src/composition/capabilityServices.ts` binds typed service factories to those
-capability keys. Each runtime entry owns construction, cleanup and any available
-host/configuration facts or live probes. A service entry requires a close
-capability; entries adapting managers retain their existing `closeAll` operation.
-The host maps entries without erasing their individual service/port types. There
-is no generic JSON operation dispatcher.
-
-These two declarations have different loading needs. Static facts can be read
-without loading a schema or provider graph. The full runtime composition is
-materialized only when the MCP runtime needs it. One-shot CLI adapters import the
-selected factory rather than constructing a complete capability host. CLI and MCP
-reuse the same provider/service factories and application workflows, while
-keeping their respective argument translation and lifetime.
-
-## Resource lifetime
-
-`CapabilityScope` registers a module's actual close capability when its instance
-is composed. There is no independent server provider-close list to update.
-Concurrent shutdown calls join the same cleanup attempt. A successful peer is
-removed from pending cleanup; failed peers remain owned and are retried on the
-next close. Synchronous throws and rejections without a reason remain failures,
-and cannot prevent other peers from attempting cleanup. Shutdown seals further
-ownership registration.
-
-The host distinguishes these lifetimes:
-
-- Host-owned service instances are released by that host.
-- Caller-owned optional observations remain borrowed by SDK server instances;
-  their process-level owner closes them, including discarded discovery probes.
-- CLI invocations use their existing finalizers to join cleanup and preserve the
-  original observation, cancellation and cleanup errors.
-- Binary engines, bundle readers and investigation records retain their existing
-  owners. The `BinarySession` transition/drain barrier still coordinates target
-  changes, reset and disposal. A module refactor must not create independent
-  barriers that allow late work to repopulate reset records.
-
-An application workflow may borrow a shared resource scope, such as byte entropy
-using the host's artifact scope. Its wrapper does not acquire a second ownership
-claim over the borrowed scope.
-
-## Availability and registration
-
-Module bindings provide host support, selected configuration and precisely typed
-live availability probes through `CapabilityAvailabilityFacts`. Constructors do
-not run these probes or launch engines. Session discovery invokes the existing
-provider-owned probes only for advertised families; live failures remain fresh
-observations. Caller policy, selected environments and injected providers retain
-their existing precedence.
-
-MCP registration remains in the MCP adapter. It consumes composed services,
-record ports, admission and logging; it must not add fallback constructors that
-can escape the host owner. Named contracts bind handlers and schemas. The complete
-tool-family registrar map is checked by TypeScript, and catalog order never
-selects a handler or schema.
-
-## Extending a capability
-
-1. Add or reuse the domain contract and application workflow, with explicit
-   Evidence provenance, coverage, unknowns and caller choices.
-2. Put concrete construction in `src/composition/` and keep its default factory
-   lazy. Reference adapter-owned pure identity metadata from both the provider
-   and its static capability declaration.
-3. Add the runtime binding if a host-owned service is needed. Bind cleanup and
-   availability/probes there, preserving borrowed versus owned resources.
-4. Add the CLI/MCP argument adapters and their named registrations. A one-shot
-   command uses the shared selected factory and existing finalization helpers.
-5. Run source-boundary, discovery, SDK-schema and relevant public workflow checks.
-   Exercise partial cleanup, retry, cancellation and caller-owned peers at the
-   applicable production seam; use actual applications/providers for routing and
-   complete Evidence verification. Recording ports do not prove real providers.
-
-The constructor boundary guard covers the centralized Frida, Cutter, GDB and
-Rizin constructors without rejecting legitimate type-only injected interfaces.
-Other settled pure/provider boundaries continue checking type imports too. The
-shared parser records module-edge erasure once. Whole-declaration type imports
-are erased; inline type bindings retain their runtime module edge under
-`verbatimModuleSyntax`. Static dynamic imports remain runtime edges too.
-Tests belong with their semantic owner and must be
-found exactly once; provider roots need the corresponding adapter discovery lane.
-
-This is an internal composition contract. External plugin distribution, automatic
-provider installation and a universal provider interface are separate concerns.
-
-The [initial verification report](verification/capability-composition-2026-11-01.md)
-records the executed public workflows, cleanup boundaries, resource measurements
-and remaining provider qualification gaps for this composition increment.

docs/cli.md

@@ -281,18 +281,6 @@ The inventory lists each segment with its ESP-IDF load classification, the
 checksum and SHA-256 results, the descriptor and any Secure Boot v2 signature
 blocks. See [ESP images](esp-image.md) for recognition, coverage and refusals.
 
-Inspect an ESP flash dump, or one read from a flash address other than 0:
-
-```sh
-rea inspect-artifact flash.bin --json
-rea inspect-artifact dump.bin --target-format esp-flash-image --flash-offset 0x1000 --json
-rea extract-artifact flash.bin --json
-```
-
-The inventory lists the bootloader, the partition table and each partition,
-with ESP image facts for app partitions and the OTA records. See
-[ESP flash images](esp-flash-image.md) for table location, inputs and limits.
-
 Inspect a Node.js SEA carrier without running it:
 
 ```sh
@@ -329,16 +317,6 @@ overlap and archive expansion checks. The native streaming decoder keeps the
 existing 128 MiB Zstandard window cap; frames requiring a larger window are
 refused. Deprecated method 20 and other unregistered ZIP codecs remain unsupported.
 
-Inventory and extract UF2 or DfuSe regions:
-
-```sh
-rea inspect-artifact ./firmware.uf2 --json
-rea extract-artifact ./firmware.dfu --json
-```
-
-See [UF2 and DfuSe images](uf2-dfuse.md) for recognition, families, numbering,
-the DfuSe suffix CRC and limits.
-
 Inventory and extract U-Boot FIT images:
 
 ```sh
@@ -561,25 +539,6 @@ be verified. See [MCP contracts](mcp-contracts.md) for session lifecycle and
 [Ghidra first-query deadlines](mcp-contracts.md#ghidra-first-query-deadlines-and-recovery)
 for import, client timeouts and recovery.
 
-A one-shot command releases its provider session and REA runtime before it
-prints a failure, so it omits the same-session reuse and
-`update_analysis_settings` guidance an MCP connection receives. Its
-`details.limit` reports `scope: "rea-invocation"` and
-`applies_at: "next_invocation"`; set the named `environment` (or the per-call
-`parameter`) for a new invocation and rerun. For example, a Ghidra decompile
-deadline names `REA_GHIDRA_DECOMPILE_TIMEOUT_SECONDS`.
-
-`rea debug-with-gdb` and `rea debug-with-rizin` hold their debugger only for the
-command's own process. If cleanup cannot confirm the debugger stopped, they print
-`cleanup_incomplete` and exit nonzero without stopping it. `remediation.action`
-names the process, as does `retained_debugger_pids` in `details.diagnostics`, or
-in `details.diagnostics.cleanup_error.details.diagnostics` when the command also
-failed or was interrupted. Exiting closes the debugger's command and output pipes.
-REA does not establish what the debugger or its target does next, so check that
-process. An MCP server that shuts down likewise exits with status 1 instead of
-waiting on a debugger it could not stop. It names the process on stderr and as
-`retained_debugger_pids` in its error log.
-
 If one-shot analysis fails and closing its session also fails, the original
 error details remain inline and `details.cleanup_error` describes the later
 close failure. Each diagnostic retains its own reported resources; the later
@@ -612,9 +571,6 @@ Saved snapshots include only cache entries whose subject identifies the selected
 target. Unbound observations and observations of child artifacts remain available
 in the open session and its Evidence bundle; they are excluded from the target's
 saved replay entries without changing their subjects.
-The snapshot also retains available Evidence linked by selected records, including
-transitive sources with an unbound or different subject. Those sources are not
-replay entries for the selected target. Unrelated records remain excluded.
 
 Snapshots retain eligible target-scoped question histories in full, including
 mutation Evidence recorded while another target was active. Observations and
@@ -629,6 +585,11 @@ rea analyze /absolute/path/to/program --provider ghidra --snapshot /absolute/pat
 ```
 
 An exact CLI cache hit is normally read before starting a provider process.
+`decompile --provider ghidra --snapshot ...` also retains its single selected
+Program's pseudocode result, even without an explicit document selector. Old
+snapshots that contain only the Evidence need one new query to add that replay
+entry. This does not retain every body from `decompile-all` or make a persistent
+session's implicit document replayable.
 On Windows, Ghidra first admits the selected source through its native snapshot
 owner, so replay can start that provider.
 In MCP, `open_binary` accepts `snapshot_path` to import a snapshot atomically
@@ -637,30 +598,6 @@ cached result. `close_binary` accepts `snapshot_path` and optional
 `overwrite: true` to save before releasing provider resources. A failed save
 leaves the session open so the caller can resolve the output failure.
 
-When a validated snapshot does not match the selected binding, the error's
-`details.binding_mismatch` reports confirmed target identities, provider
-identities, or profile digests that differ. `snapshot` is the saved value and
-`selected` is the requested value. Multiple differences can be reported. A
-`profile_comparison: "not_compared"` means the profile was not available at
-that boundary; it does not establish a match. A profileless snapshot can report
-`workflow_scope: "incompatible"` even when its target and profile match.
-Choose a matching target, provider, and profile, or analyze without the snapshot
-and save a new one for the intended binding.
-
-For a profile mismatch, the saved snapshot contains
-`binding.analysis_profile.parameters`. If `binary_session` reports an active
-profile whose digest matches `binding_mismatch.profile_digest.selected`, its
-`analysis_provider_binding.analysis_profile.parameters` can be compared with
-those saved parameters. A rejected switch leaves the previous session active,
-so its profile may be different from the attempted selection; check the digest
-before using it for this comparison. A configuration difference does not by
-itself establish why analysis results differ.
-
-If no target is open and you intend to inspect the selected binding, open that
-target without the snapshot, then check its profile digest in `binary_session`
-before comparing parameters. This may start the selected provider; the saved
-snapshot remains a separate file.
-
 If a selected snapshot's file descriptor cannot close, `open_binary` reports
 `cleanup_incomplete`. `binary_session` reports `cleanup_pending` even when no
 target opened. Retry `close_binary` to release the retained descriptor before
@@ -719,45 +656,12 @@ with `details.reason: path-limit` and `boundary: filesystem-path`.
 For application traces and version comparisons, see
 [JavaScript application workflows](javascript-application-workflows.md).
 MCP [retained Evidence references](mcp-contracts.md#retained-application-evidence-inputs)
-belong to one connection. Separate CLI calls can consume full saved records or
-resolve exact retained IDs from an explicitly selected local bundle:
-
-```bash
-rea trace-application-feature request.json --evidence-bundle /absolute/path/evidence.json --json
-```
-
-Here `request.json` uses the same logical Evidence input as MCP, for example
-`"application": {"kind":"retained-evidence","evidence_id":"ev_<64 lowercase hex characters>"}`.
-Inline records and references may be mixed in the request's declared source
-fields, including arrays and nested inputs. The bundle is read and authenticated
-once for that command; no target is reopened, no producer is rerun, and no
-record is selected by file order. Source identity, provenance, coverage and
-partial or unknown facts agree with the complete inline form. When starting
-from summary or inspection Evidence, select its
-`normalized_result.parent_evidence_id` for a workflow requiring complete source
-facts. Omit `--evidence-bundle` when all sources are inline.
-
-The JSON workflow commands supporting this option are:
-
-- `trace-application-feature`, `trace-javascript-semantics`,
-  `compare-application-versions`, `compare-javascript-export-shapes`,
-  `compare-source-to-bundle`, and `reconcile-javascript-runtime`.
-- `import-managed-reconstruction`, `verify-managed-native-boundaries`, and
-  `project-managed-application-graph`.
-- `project-android-application-graph`, `project-apple-application-graph`, and
-  `project-harmony-application-graph`.
-- `compare-wasm-interfaces` and `inspect-analysis-view`.
-
-For `inspect-analysis-view`, the request's source reference selects a parent
-from the bundle for every supported view kind. Bundles exported from MCP work
-for these commands. Its inline source form cannot also select a bundle.
-A missing ID is refused with `details.reason: "missing"`;
-supplying a bundle does not make incompatible Evidence valid for a workflow.
-`compare-managed-members` keeps its two assembly paths, and
-`compare-process-captures` keeps its two capture Evidence JSON paths. The bundle
-option above selects an input; producer options that write a new bundle, such
-as `inspect-managed-members --evidence-bundle`, retain their existing meaning.
-File selectors remain available only on contracts that explicitly support them.
+belong to one connection. Separate CLI calls can consume full saved records.
+`inspect-analysis-view REQUEST.json --evidence-bundle BUNDLE.json` resolves
+the request's `retained-evidence` source ID from that authenticated bundle,
+including bundles exported from an MCP session. The same view JSON works for
+every supported parent kind; no target is reopened and no record is selected
+by file order. Omit `--evidence-bundle` when the request supplies inline Evidence.
 
 Compare two artifact inventories with `compare-artifacts`. It takes the same
 `left` and `right` input as MCP `compare_artifacts`: complete Evidence, or an
@@ -770,7 +674,7 @@ rea inspect-artifact new.zip --json > new.json
 rea compare-artifacts '{"left":{"kind":"evidence-file","path":"old.json"},"right":{"kind":"evidence-file","path":"new.json"}}' --json
 ```
 
-A one-shot `compare-artifacts` command keeps no session Evidence, so it refuses a
+A one-shot command keeps no session Evidence, so it refuses a
 `retained-evidence` source with `details.reason: "missing"`. Select the record
 from a saved bundle instead.
 For an artifact summary selected from a bundle, include its complete parent
@@ -954,13 +858,7 @@ rea mcp --http --port 8765
 `--host` and `--port` default to `MCP_HOST` and `MCP_PORT` from the environment,
 then to `127.0.0.1` and an ephemeral port. A bind outside loopback requires
 `MCP_ALLOWED_HOSTS` or `--allowed-hosts`, a comma-separated list of client host
-names or IP addresses without URLs or ports.
-
-Repeat `--allowed-hosts` to append names, or put multiple names in one
-comma-separated value. All occurrences are validated together and deduplicated
-after hostname normalization; the explicit list replaces `MCP_ALLOWED_HOSTS`.
-
-For example:
+names or IP addresses without URLs or ports. For example:
 
 ```sh
 rea mcp --http --host 0.0.0.0 --allowed-hosts 127.0.0.1,rea.lan
@@ -1308,18 +1206,6 @@ new file. A publication that has committed can win a later cancellation; the
 after commit, the `cleanup_incomplete` error reports the same file as
 `details.published_path` and `details.bytes`.
 
-When a failure retains a completed observation and no bundle committed,
-`details.source_closure` states what that observation cites. `publication` is
-`not_published`. `records` holds authentic source Evidence this invocation
-captured, within 64 KiB. `omitted` lists up to 64 other identities and
-`omitted_count` the total: `not_captured` means the invocation holds no such
-record, so nothing is shown for it or its ancestors; `not_inlined` means it was
-captured but is not in this response. `complete` is true only when every cited
-record is in `records` or embedded in the observation. If examining the closure
-itself fails, `collection_failure` names the error type and the closure state is
-unknown; the original failure is still returned. Nothing is retained after exit,
-and running the command again is a new observation.
-
 When the reader of piped output closes early, as `rea ... | head` does, the
 CLI stops writing, prints no error and exits `141` (`128 + 13`, the status of a
 SIGPIPE-terminated writer). The operation itself may have completed; only its

docs/client-configuration.md

@@ -45,10 +45,6 @@ the client's configured command or reproduce the client's environment. If doctor
 passes but the client disconnects, inspect the client's startup error and registered
 launcher; see [verification scope](client-verification.md#launch-environment-verification).
 
-`rea doctor` has the same limit for provider checks, and reports a provider setting
-the registration's file does not carry as a
-[non-blocking unknown](installation.md#check-readiness-for-your-task).
-
 ## Runtime settings and client deadlines
 
 `update_analysis_settings` changes curated defaults inside the running REA

docs/design/limits-and-recovery.md

@@ -222,25 +222,6 @@ Error copying, attribution, redaction, and delivery must preserve these facts.
 Human-readable remediation explains the same failure; clients should not need
 to parse that sentence to identify an editable setting.
 
-`scope` and `applies_at` describe a continuing caller, such as an MCP
-connection. A one-shot invocation, such as a CLI command, has released its
-provider session and exited its runtime before its caller reads the failure,
-so its adapter projects with an explicit `"invocation"` caller lifetime.
-`details.limit` then keeps every other field and reports
-`scope: "rea-invocation"`, `applies_at: "next_invocation"` and the launch
-`environment` seed when one exists. `agent_editable: true` still holds, because
-the caller chooses that environment value or per-call `parameter` for the new
-invocation; `rea_restart_required: false` means no running REA process needs a
-restart. A producer keeps guidance that holds only while its caller retains the
-session, such as "the Ghidra session remains usable" or a same-session runtime
-update, in `continuingCallerGuidance`; the shared presentation adds it only for
-a continuing caller. The producer's own message and remediation must stay true
-after the session is released. A composed error records each embedded child
-failure through `childFailureDiagnostics`, which snapshots it at composition
-for both lifetimes when they differ, so cleanup history keeps its state and
-the final projection selects the caller's form. Failures retained inside
-Evidence keep the continuing form, so CLI and MCP Evidence stay identical.
-
 Cache policy is part of enforcement. Successful reusable analysis can survive
 a budget update. Transient Ghidra decompile failures remain uncached so a raised
 deadline can recover on the same Program. Admission checks still apply to reused
@@ -305,9 +286,7 @@ whether live repair is possible.
 ## What agents do
 
 Use `details.limit` for a direct runtime update when it names an editable
-setting with `scope: "rea-runtime"`. For `scope: "rea-invocation"`, set its
-`environment` or `parameter` for a new invocation instead.
-Follow `remediation.action` for per-call, fixed and external controls.
+setting. Follow `remediation.action` for per-call, fixed and external controls.
 Inspect settings only when bounds or application details are missing. Restart only when it says the value is
 read at startup. A sentence that a control does not raise the limit is not a
 request to change it.
@@ -337,12 +316,8 @@ request to change it.
   `runtime-configuration:` check. Re-run `rea setup` for that client when the
   setting is on the registration allowlist, then reconnect so the new process
   sees it.
-- `invalid_request`: follow the specific recovery and reported issue. Inspect
-  the schema or CLI help when the input violates the contract or the response
-  asks for `inspect_input_contract`. A valid selector can instead require a
-  different choice, such as selecting a reported address; an inventory miss
-  does not establish that the target lacks the item. Do not repeat the
-  unchanged call when the response says it cannot succeed unchanged.
+- `invalid_request`: correct the reported fields from the current schema or
+  CLI help. Do not repeat the unchanged call.
 
 A restart is required to adopt a changed launch environment or registration.
 The curated runtime settings above require no REA restart. It is not the first step for a transient

docs/electron-observation.md

@@ -147,14 +147,6 @@ window-targeted renderer reload/crash actions, and synthetic `open-url` or
 WebContents identities, process metrics, and IPC channel and value-shape metadata.
 Payload values are not retained.
 
-For the exact Playwright launch sequence, the active hook removes only REA's
-bootstrap arguments from the application-visible `process.argv`. The vector keeps
-the selected entry point and every caller argument, in order, including repeated
-hook paths, `.asar` filenames, and debug-like options. The private launch handoff
-is consumed before application code runs. If the observed sequence cannot be
-matched exactly, argv stays unchanged and capture coverage reports `hook_conflict`;
-REA does not guess an entry point or remove arguments by filename patterns.
-
 `window_index` selects from Playwright's current Page list at the start of each action. REA resolves that Page to its corresponding BrowserWindow once; the action's `target` uses the BrowserWindow's capture-scoped `window_id`, matching the window inventory. Reordering either enumeration after selection does not retarget the action. Handle cleanup failures retain the completed action records and remain owned for provider cleanup retry.
 
 Run the real fixture verifier with an operator-provided Electron runtime:
@@ -201,9 +193,6 @@ neither result means the requested host operation occurred. The existing
 `openExternal`, `openPath`, and `trashItem` blocks reject their promises.
 The `trashItem` block prevents that call from reaching the OS trash operation;
 it does not intercept other ways the application can remove files.
-Process rejection and uncaught-exception events are observed at dispatch without
-adding exception handlers. The runtime and application retain their warning,
-handler, and fatal-exit policies, including for rejected shell-block promises.
 CLI SIGINT/SIGTERM requests cancellation and awaits owned-process cleanup.
 Window IDs, URLs, and cached titles come from one main-process Electron snapshot,
 so a crashed renderer does not require a successful renderer-side title query.

docs/elf-notes.md

@@ -38,12 +38,6 @@ were examined; an unavailable section name does not erase those note facts.
 For GNU notes, `gnu.build_id_hex`, `gnu.abi_tag`, or `gnu.gold_version` are
 filled when the descriptor matches that type. Other owners keep `gnu` null.
 
-For Linux `CORE` notes, `core.prpsinfo`, `core.file`, `core.siginfo`, or
-`core.auxv` are decoded for process arguments and status (`NT_PRPSINFO`), mapped
-file memory regions and paths (`NT_FILE`), fault signal and code (`NT_SIGINFO`), and
-auxiliary vectors (`NT_AUXV`) across 32-bit and 64-bit images. Other owners or unparsed
-notes keep `core` null.
-
 `PT_NOTE` and `SHT_NOTE` are examined independently. The same file range may
 appear twice when both tables declare it.
 
@@ -54,7 +48,7 @@ the image never carried notes in another container or overlay.
 
 The selected file is limited to 64 MiB by default (512 MiB maximum). At most
 32 note entries are examined by default across every table. Retained note
-names, section names, GNU descriptor text, and core dump string representations share a scan budget based on
+names, section names, and GNU descriptor text share a scan budget based on
 the source bytes plus any decoded section-name table, capped at
 `max_file_bytes`. The raw source and decoded table must also fit together
 within that ceiling. If admission fails, the error reports the required

docs/error-contract.schema.json

@@ -52,15 +52,6 @@
               },
               "required": ["kind", "operation", "timeout_ms"],
               "additionalProperties": false
-            },
-            {
-              "type": "object",
-              "properties": {
-                "kind": { "type": "string", "const": "retry_cleanup" },
-                "operation": { "type": "string", "minLength": 1 }
-              },
-              "required": ["kind", "operation"],
-              "additionalProperties": false
             }
           ]
         },
@@ -124,15 +115,6 @@
               },
               "required": ["kind", "operation", "timeout_ms"],
               "additionalProperties": false
-            },
-            {
-              "type": "object",
-              "properties": {
-                "kind": { "type": "string", "const": "retry_cleanup" },
-                "operation": { "type": "string", "minLength": 1 }
-              },
-              "required": ["kind", "operation"],
-              "additionalProperties": false
             }
           ]
         },
@@ -196,15 +178,6 @@
               },
               "required": ["kind", "operation", "timeout_ms"],
               "additionalProperties": false
-            },
-            {
-              "type": "object",
-              "properties": {
-                "kind": { "type": "string", "const": "retry_cleanup" },
-                "operation": { "type": "string", "minLength": 1 }
-              },
-              "required": ["kind", "operation"],
-              "additionalProperties": false
             }
           ]
         },
@@ -268,15 +241,6 @@
               },
               "required": ["kind", "operation", "timeout_ms"],
               "additionalProperties": false
-            },
-            {
-              "type": "object",
-              "properties": {
-                "kind": { "type": "string", "const": "retry_cleanup" },
-                "operation": { "type": "string", "minLength": 1 }
-              },
-              "required": ["kind", "operation"],
-              "additionalProperties": false
             }
           ]
         },
@@ -340,15 +304,6 @@
               },
               "required": ["kind", "operation", "timeout_ms"],
               "additionalProperties": false
-            },
-            {
-              "type": "object",
-              "properties": {
-                "kind": { "type": "string", "const": "retry_cleanup" },
-                "operation": { "type": "string", "minLength": 1 }
-              },
-              "required": ["kind", "operation"],
-              "additionalProperties": false
             }
           ]
         },
@@ -412,15 +367,6 @@
               },
               "required": ["kind", "operation", "timeout_ms"],
               "additionalProperties": false
-            },
-            {
-              "type": "object",
-              "properties": {
-                "kind": { "type": "string", "const": "retry_cleanup" },
-                "operation": { "type": "string", "minLength": 1 }
-              },
-              "required": ["kind", "operation"],
-              "additionalProperties": false
             }
           ]
         },
@@ -484,15 +430,6 @@
               },
               "required": ["kind", "operation", "timeout_ms"],
               "additionalProperties": false
-            },
-            {
-              "type": "object",
-              "properties": {
-                "kind": { "type": "string", "const": "retry_cleanup" },
-                "operation": { "type": "string", "minLength": 1 }
-              },
-              "required": ["kind", "operation"],
-              "additionalProperties": false
             }
           ]
         },
@@ -556,15 +493,6 @@
               },
               "required": ["kind", "operation", "timeout_ms"],
               "additionalProperties": false
-            },
-            {
-              "type": "object",
-              "properties": {
-                "kind": { "type": "string", "const": "retry_cleanup" },
-                "operation": { "type": "string", "minLength": 1 }
-              },
-              "required": ["kind", "operation"],
-              "additionalProperties": false
             }
           ]
         },
@@ -628,15 +556,6 @@
               },
               "required": ["kind", "operation", "timeout_ms"],
               "additionalProperties": false
-            },
-            {
-              "type": "object",
-              "properties": {
-                "kind": { "type": "string", "const": "retry_cleanup" },
-                "operation": { "type": "string", "minLength": 1 }
-              },
-              "required": ["kind", "operation"],
-              "additionalProperties": false
             }
           ]
         },
@@ -700,15 +619,6 @@
               },
               "required": ["kind", "operation", "timeout_ms"],
               "additionalProperties": false
-            },
-            {
-              "type": "object",
-              "properties": {
-                "kind": { "type": "string", "const": "retry_cleanup" },
-                "operation": { "type": "string", "minLength": 1 }
-              },
-              "required": ["kind", "operation"],
-              "additionalProperties": false
             }
           ]
         },
@@ -772,15 +682,6 @@
               },
               "required": ["kind", "operation", "timeout_ms"],
               "additionalProperties": false
-            },
-            {
-              "type": "object",
-              "properties": {
-                "kind": { "type": "string", "const": "retry_cleanup" },
-                "operation": { "type": "string", "minLength": 1 }
-              },
-              "required": ["kind", "operation"],
-              "additionalProperties": false
             }
           ]
         },
@@ -827,32 +728,6 @@
                 "unpacked"
               ],
               "additionalProperties": {}
-            },
-            {
-              "type": "object",
-              "properties": {
-                "logical_path": { "type": "string" },
-                "algorithm": { "type": "string", "const": "dfu-crc32" },
-                "declared_crc32": {
-                  "type": "string",
-                  "pattern": "^[a-f0-9]{8}$"
-                },
-                "calculated_crc32": {
-                  "anyOf": [
-                    { "type": "string", "pattern": "^[a-f0-9]{8}$" },
-                    { "type": "null" }
-                  ]
-                },
-                "unpacked": { "type": "boolean" }
-              },
-              "required": [
-                "logical_path",
-                "algorithm",
-                "declared_crc32",
-                "calculated_crc32",
-                "unpacked"
-              ],
-              "additionalProperties": {}
             }
           ]
         }
@@ -918,15 +793,6 @@
               },
               "required": ["kind", "operation", "timeout_ms"],
               "additionalProperties": false
-            },
-            {
-              "type": "object",
-              "properties": {
-                "kind": { "type": "string", "const": "retry_cleanup" },
-                "operation": { "type": "string", "minLength": 1 }
-              },
-              "required": ["kind", "operation"],
-              "additionalProperties": false
             }
           ]
         },
@@ -990,15 +856,6 @@
               },
               "required": ["kind", "operation", "timeout_ms"],
               "additionalProperties": false
-            },
-            {
-              "type": "object",
-              "properties": {
-                "kind": { "type": "string", "const": "retry_cleanup" },
-                "operation": { "type": "string", "minLength": 1 }
-              },
-              "required": ["kind", "operation"],
-              "additionalProperties": false
             }
           ]
         },
@@ -1062,15 +919,6 @@
               },
               "required": ["kind", "operation", "timeout_ms"],
               "additionalProperties": false
-            },
-            {
-              "type": "object",
-              "properties": {
-                "kind": { "type": "string", "const": "retry_cleanup" },
-                "operation": { "type": "string", "minLength": 1 }
-              },
-              "required": ["kind", "operation"],
-              "additionalProperties": false
             }
           ]
         },
@@ -1134,15 +982,6 @@
               },
               "required": ["kind", "operation", "timeout_ms"],
               "additionalProperties": false
-            },
-            {
-              "type": "object",
-              "properties": {
-                "kind": { "type": "string", "const": "retry_cleanup" },
-                "operation": { "type": "string", "minLength": 1 }
-              },
-              "required": ["kind", "operation"],
-              "additionalProperties": false
             }
           ]
         },
@@ -1206,15 +1045,6 @@
               },
               "required": ["kind", "operation", "timeout_ms"],
               "additionalProperties": false
-            },
-            {
-              "type": "object",
-              "properties": {
-                "kind": { "type": "string", "const": "retry_cleanup" },
-                "operation": { "type": "string", "minLength": 1 }
-              },
-              "required": ["kind", "operation"],
-              "additionalProperties": false
             }
           ]
         },
@@ -1278,15 +1108,6 @@
               },
               "required": ["kind", "operation", "timeout_ms"],
               "additionalProperties": false
-            },
-            {
-              "type": "object",
-              "properties": {
-                "kind": { "type": "string", "const": "retry_cleanup" },
-                "operation": { "type": "string", "minLength": 1 }
-              },
-              "required": ["kind", "operation"],
-              "additionalProperties": false
             }
           ]
         },
@@ -1350,15 +1171,6 @@
               },
               "required": ["kind", "operation", "timeout_ms"],
               "additionalProperties": false
-            },
-            {
-              "type": "object",
-              "properties": {
-                "kind": { "type": "string", "const": "retry_cleanup" },
-                "operation": { "type": "string", "minLength": 1 }
-              },
-              "required": ["kind", "operation"],
-              "additionalProperties": false
             }
           ]
         },
@@ -1422,15 +1234,6 @@
               },
               "required": ["kind", "operation", "timeout_ms"],
               "additionalProperties": false
-            },
-            {
-              "type": "object",
-              "properties": {
-                "kind": { "type": "string", "const": "retry_cleanup" },
-                "operation": { "type": "string", "minLength": 1 }
-              },
-              "required": ["kind", "operation"],
-              "additionalProperties": false
             }
           ]
         },
@@ -1494,15 +1297,6 @@
               },
               "required": ["kind", "operation", "timeout_ms"],
               "additionalProperties": false
-            },
-            {
-              "type": "object",
-              "properties": {
-                "kind": { "type": "string", "const": "retry_cleanup" },
-                "operation": { "type": "string", "minLength": 1 }
-              },
-              "required": ["kind", "operation"],
-              "additionalProperties": false
             }
           ]
         },

docs/esp-flash-image.md

@@ -1,348 +0,0 @@
-# ESP flash images
-
-REA reads a dump of an ESP32-family SPI flash, such as the output of
-`esptool read-flash 0 ALL dump.bin` or `esptool merge-bin`, through
-`inspect_artifact` and `extract_artifact`. The reader is static: no device,
-esptool or ESP-IDF is needed, and no code is run.
-
-The container format is `esp-flash-image`. Entries are the bootloader region,
-the partition table sector and one file per partition. The bootloader and
-each app partition are also decoded as [ESP images](esp-image.md), so their
-headers, segments, integrity and descriptors appear in the root
-`format_metadata`. Layout facts are cited to ESP-IDF v6.1
-(`esp_flash_partitions.h`, `flash_partitions.c`, `gen_esp32part.py`,
-`bootloader_common_loader.c`, `bootloader_utility.c` and each chip's
-`esp_rom_caps.h`).
-
-## Recognition
-
-A file is a flash image when REA finds a partition table in the entry
-structure ESP-IDF's bootloader verifies (`esp_partition_table_verify`):
-32-byte `0x50AA` entries, at most one `0xEBEB` MD5 entry over the entries
-before it, and a terminating entry within `0xC00` bytes. ESP-IDF accepts a
-table with no partition entries, but REA requires one, so that neither
-erased flash nor a lone MD5 entry is read as a table. A table whose MD5 does not match, or that has a second MD5 entry, is
-still read, with `md5.status` `invalid` and a limitation, because the
-bootloader would refuse it. The table is located in this order:
-
-1. at the caller's `partition_table_offset`, when given; no scan follows;
-2. at the default `0x8000`;
-3. by scanning every `0x1000`-aligned flash sector for a table whose MD5
-   verifies. This location is derived, and the inventory says so.
-
-A table never lies inside the located bootloader image, so the default
-offset and the scan are tried only after the image's last segment. Without
-a caller selection, the scan runs only when an ESP image sits at a ROM
-bootloader offset, and a single app or bootloader image ends at its last
-segment, so neither ordinary files nor single images are scanned. A C3 or
-S3 dump begins with its bootloader, so flash layouts are detected before a
-file is read as one ESP image.
-
-Unless the caller names the table with `partition_table_offset`, REA
-refuses two kinds of dump before looking for a table:
-
-- an image of a known chip at another chip's ROM offset, such as an ESP32
-  bootloader at the start of a dump read from `0x1000`. The dump's origin
-  is not the flash address REA assumed, given or default, and a table found
-  there would place every partition at the wrong file offset; pass the
-  `flash_offset` where the dump starts. When a partition table sits where
-  the image's own ROM offset puts `0x8000`, after the image's segments, the
-  refusal names that offset.
-  Without a selected format such a dump opens as its bootloader image, whose
-  [ESP image](esp-image.md) facts say how to reopen it.
-- an ESP8266 image at a ROM offset. ESP8266 dumps can hold the same table
-  format, and they keep the [ESP image](esp-image.md) reader's ESP8266
-  refusal.
-
-When no table is found the layout is not recognized. This is an unknown
-outcome, not a malformed file: flash encryption, which encrypts the
-bootloader and the table, is one cause. When a table is found without a
-located bootloader and `flash_offset` is omitted, a limitation says that
-each partition's file offset assumes the dump starts at flash `0x0`.
-
-## Caller inputs
-
-| Input                     | Meaning                                                                       |
-| ------------------------- | ----------------------------------------------------------------------------- |
-| `format: esp-flash-image` | Read the file as a flash dump; with no table found, refuse it                 |
-| `flash_offset`            | Flash address (`0x…`) of the dump's first byte; default 0                     |
-| `partition_table_offset`  | Flash address (`0x…`, a multiple of `0x1000`) of the table; disables the scan |
-
-MCP takes these on `open_binary`; the CLI takes `--target-format
-esp-flash-image`, `--flash-offset` and `--partition-table-offset` on
-`inspect-artifact` and `extract-artifact`. The offsets require the format, and
-the format takes no `architecture` or `entry_point`. The inputs are part of
-the target's identity, so reopening the same bytes with other inputs reads
-them again instead of reusing the earlier reading. The `open_binary` summary
-reports them as `flash_offset` and `partition_table_offset`, null when
-omitted.
-
-## Layout facts
-
-The root `format_metadata` (`esp-flash-image`) records:
-
-- `flash_offset`: its `value` and whether the `caller` gave it or it is the
-  `default`;
-- `chip`: from the bootloader's `chip_id`, or null without a located
-  bootloader;
-- `bootloader`: the region from the chip's ROM bootloader offset to the
-  table, with its ESP image facts;
-- `partition_table`: its flash address, the `method` that found it
-  (`default`, `caller` or `scan`), the partition count and the MD5 `status`
-  (`valid`, `invalid` or `absent`) with the stored and computed digests;
-- `apps`: ESP image facts for each app partition the dump holds; app
-  partitions declared over the same bytes share one decode;
-- `otadata`: the otadata partition's records, or null without one;
-- `boot_selection`: the app the bootloader would select, for every table;
-- `partitions_outside_dump`: declared partitions that begin before the
-  dump's first byte, which have no entry;
-- `undescribed`: ranges outside every region, each from a byte that is not
-  erased flash to the end of its gap.
-
-The ROM loads the bootloader from `ESP_ROM_BOOTLOADER_OFFSET_FLASH`:
-`0x1000` for ESP32 and ESP32-S2; `0x0` for ESP32-S3, C2, C3, C6, C61, H2 and
-H21; and `0x2000` for ESP32-C5, H4, P4 and S31. A bootloader is located only
-where its own `chip_id` says the ROM loads it.
-
-### Partitions
-
-Each partition entry is `partitions/<label>.bin` when the label is a safe
-name of up to 16 letters, digits, `.`, `_` and `-` that starts with a
-letter, digit or underscore and has at least one letter or underscore, is
-not a Windows device name such as `NUL` or `COM1`, alone or before a dot,
-and no other label repeats it, ignoring case as some file systems do; it is
-`partitions/<index>.bin` otherwise. `source_path` keeps the label, the
-table's own name for the partition. Its `format_metadata`
-(`esp-flash-partition`) records the table `index`, `label` (null when not
-UTF-8), `label_hex` (the label's bytes when it is not UTF-8, else null),
-`type`, `subtype`, ESP-IDF's `type_name` and `subtype_name`,
-`flash_address`, `size`, the `encrypted` and `readonly` flags and any
-`unknown_flags`. The `encrypted` flag says how a device with flash
-encryption stores the partition; it does not establish that the dump's
-bytes are ciphertext.
-
-Each partition entry also records where the bytes the dump holds are
-written, relative to the partition's start: `written_offset`, the first
-byte that is not erased flash (`0xFF`), `written_end`, just past the last
-such byte, and `written_bytes`, how many bytes are not `0xFF`. A partition
-erased throughout has null offsets and `written_bytes` `0`; a partition the
-file holds none of has all three null. The range bounds the written
-bytes and does not say whether erased flash lies between them; extract the
-partition to read them. REA reads the bytes the partitions cover once, so
-overlapping partitions share that read however many the table declares.
-
-ESP-IDF 5.3 and later may declare primary `bootloader` and `partition_table`
-entries over the bootloader region and the table sector. They are
-partitions like any other, whose bytes are also `bootloader.bin` and
-`partition-table.bin`, and they are exempt from the rule that partitions
-follow the table, as in `gen_esp32part.py`.
-
-Every partition from the dump's first byte on is an entry holding the bytes
-the file has. One that the file holds only in part, as when an `esptool
-merge-bin` dump ends inside its last partition, has an entry limitation that
-gives the size the table declares; one that lies past the end of the file is
-an entry with no bytes and a limitation, and has no image facts. A partition
-that begins before the dump's first byte has no entry and is listed in
-`partitions_outside_dump`. One unreadable partition does not hide the
-others: partitions outside the dump or overlapping another are each reported
-while the rest stay readable.
-
-### App partitions and the bootloader
-
-Each app partition and the bootloader region carry their entry's `path`
-and ESP image `facts`:
-`status` is `esp-image`, `erased` (the image header bytes are erased flash,
-as in an empty OTA slot) or `unrecognized` (ciphertext or other data). For an
-image they hold the [ESP image](esp-image.md) root facts, `segments`,
-`signature_blocks`, `coverage` and `limitations`, with offsets relative to
-the region. Extract a partition and inspect it as an ESP image for its
-segments as entries.
-
-The summary view (`inspect_artifact` with `detail: "summary"`, or the
-inventory summary of `inspect_analysis_view`) reports the root facts under
-their own kind, `esp-flash-image-summary`, and gives each of these images a
-`summary` instead of its `facts`: `status`, `chip`, `entry_addr`,
-`segment_count`, `load_ranges` (the load address, declared length and
-classification of each segment that is mapped, loaded or unclassified),
-`signature_block_count`, the `descriptor` kind with the fields that tell
-builds apart (an app's `project_name`, `version`, `idf_ver`,
-`secure_version` and `app_elf_sha256`; a bootloader's `version`, `idf_ver`
-and `secure_version`), the `checksum` and `appended_sha256` statuses,
-`coverage` and `limitations`. The default complete detail keeps the full
-facts, every segment included, and the summary's `inventory_evidence_ids`
-name the Evidence that holds them.
-
-`erased` is the bootloader's view: with no image header at the start of the
-slot, it finds no app there. An erased slot can still hold data further in,
-even a complete app image. When it does, its entry's `written_offset` and
-`written_end` say where, and a limitation says that the slot holds bytes the
-bootloader does not read; REA does not look for images in them.
-
-### OTA data
-
-The otadata partition holds two `esp_ota_select_entry_t` records, one at the
-start of each 4 KiB sector. Like the bootloader, REA reads the last otadata
-partition the table declares, and the last factory app and OTA app of each
-subtype; a limitation names any repeated declaration. REA reports each
-record the partition and the dump hold: its `ota_seq`, `seq_label`,
-`ota_state` and its name, `crc`, whether the CRC matches (CRC-32 of
-`ota_seq` seeded with `0xFFFFFFFF`) and whether the bootloader would treat
-it as valid.
-
-### Boot selection
-
-`boot_selection` is present for every table. It is derived as
-`bootloader_utility_get_selected_boot_partition` does without app rollback
-or anti-rollback, and `basis` names its branch:
-
-- `otadata`: the valid record with the higher `ota_seq` (record 0 on a tie)
-  selects slot `(ota_seq - 1) % ota_app_count`, indexed by OTA subtype;
-- `factory-fallback`: no record is usable, or the table has no OTA app, and
-  a factory app is declared; or records are set but none is valid, as after
-  a CRC mismatch, which selects the factory index whether or not a factory
-  app is declared;
-- `ota_0-fallback`: no record is usable, or the table has no OTA app, and no
-  factory app is declared, so the bootloader selects boot index 0;
-- `no-otadata`: the table declares no otadata partition, or one at offset 0,
-  which the bootloader takes for none, so it selects the factory index, as in
-  the common factory-only layout;
-- `none`: the bootloader rejects the table, for an MD5 mismatch or a second
-  MD5 entry, or cannot read an otadata partition smaller than two 4 KiB
-  sectors, and resets without selecting an app;
-- `unknown`: the dump lacks an otadata record the bootloader reads.
-
-Without an OTA app the records do not matter, so a dump that lacks them
-still selects a fallback. REA does not compare the partitions with the
-flash size in the bootloader header, which the bootloader also checks.
-
-`active_record` and `slot` are set for `otadata` and `slot` for
-`ota_0-fallback`. `partition_index` is null when the table declares no
-partition for the selected slot or fallback; the bootloader then tries the
-other apps. `assumptions` list what the derivation leaves out: records used
-as written (for the branches that read them), anti-rollback, load fallback,
-and factory-reset and test-app GPIO holds and a wake from deep sleep; they
-are empty for `none` and `unknown`. `running_partition` is always
-`unknown`: at boot the bootloader may first mark a pending-verify record
-aborted, check the app's secure version against eFuse, and fall back to
-another partition when an app fails to load.
-
-## Coverage and extraction
-
-Erased flash (`0xFF`) between regions is described. In a gap between
-regions, the first byte that is not erased starts an `undescribed` range to
-the end of the gap, and makes coverage `unknown`; the rest of that range is
-not examined. Coverage is also `unknown` when no bootloader is located, or
-when a declared partition begins before the dump's first byte, since it has
-no entry. A partition cut short or left out by the end of the file does not
-make it `unknown`: its entry holds the bytes the file has, none for one past
-the end, and its limitation says what the file lacks. Coverage describes the
-inventory of the file, not the observation of every declared flash byte.
-
-So artifact comparison classifies every partition entry of two dumps. Where
-both lack the same bytes, as two `merge-bin` dumps of the same layout do,
-the entries are equal; a dump against a longer one reports each partition
-it cuts short or lacks as `changed`, and that entry's limitation says the
-file did not hold the bytes.
-
-`extract_artifact` writes every entry as an ordinary file, `nvs_keys`
-partitions included. On a device without flash encryption an `nvs_keys`
-partition holds the NVS encryption keys in plain text, and a dump of it
-contains them. REA decrypts nothing, recovers no keys and does not interpret
-NVS.
-
-## Comparison
-
-Artifact comparison uses each partition's `label`, `label_hex`, `type`,
-`subtype`, `flash_address`, `size` and flags as its declaration, so a
-partition that moves, changes type or flags, or is renamed with unchanged
-bytes is `changed` in `metadata`. Partitions pair by path. The root facts
-are not compared as a declaration: they derive from the dump's bytes, which
-content comparison covers, and from the caller's `flash_offset` and
-`partition_table_offset`, which are part of the target's identity and
-decide each partition's byte range.
-
-## Limits
-
-- A flash dump inside another container, such as a ZIP, is classified from
-  its first bytes and so reads as an ESP image, not as a flash layout; extract
-  it first.
-- ESP8266 dumps are refused; Secure Boot v1 bootloader digests and
-  flash-encrypted layouts are not read.
-- Partitions are not checked against the flash chip size, which the
-  bootloader also verifies.
-- NVS, FAT, SPIFFS and other data partitions are extracted, not decoded.
-- An image nested in a partition is decoded for its facts; its segments are
-  not inventory entries.
-
-## Verification
-
-Synthetic fixtures with computed MD5s and CRCs, and one CRC otatool wrote,
-cover the table rules, every way the table is located, the scan's chunk and
-sector edges, the misplaced-origin guard with the origin omitted or given,
-the ESP8266 refusal, the `0x0`, `0x1000` and `0x2000` ROM bootloader
-offsets, single images that are not scanned, overlaps, primary entries,
-truncation and partitions outside the dump, index names for unsafe labels,
-repeated declarations, the otadata states and records, and each branch of
-the bootloader's selection. CLI and stdio MCP tests exercise the inputs and
-their identity and extraction. MCP `compare_artifacts` tests compare
-partition declarations, labels that are not UTF-8 included, two dumps that
-end inside their last partition, and such a dump against a full one.
-
-The optional real lane builds its dumps with esptool and ESP-IDF's own tools:
-
-```sh
-REA_RISCV_CLANG=/path/to/clang REA_RISCV_LLD=/path/to/ld.lld \
-REA_ESPTOOL_PYTHON=/path/to/python-with-esptool \
-REA_ESP_IDF_PATH=/path/to/esp-idf \
-  npm run verify:esp-flash
-```
-
-It converts the conformance ELFs with esptool, builds a default, a
-relocated and a primary-entry partition table with `gen_esp32part.py`,
-assembles dumps with `esptool merge-bin`, one of them written from flash
-`0x1000` with `--target-offset`, and writes OTA records with `otatool`
-through `tests/conformance/esp/flash_file_tool.py`. That script replaces
-parttool's esptool calls with reads and writes of the dump file, so
-otatool's own OTA logic runs unchanged. The lane then checks:
-
-- the bootloader and app facts against `esptool image-info`;
-- every partition against `gen_esp32part.py`'s decoding of the table REA
-  extracted;
-- both OTA records against `otatool read_otadata` after switching to slot 0,
-  then to slot 1, then erasing the otadata, and the derived selection after
-  each: slot 0, slot 1, then the factory fallback;
-- that each extracted file is the dump's bytes at its range and that the
-  source is unchanged;
-- a table with the primary `bootloader` and `partition_table` entries that
-  `--primary-bootloader-offset` fills, read with complete coverage and no
-  overlap or misplacement limitation; it has no otadata, so its boot
-  selection is `no-otadata` with the factory app;
-- the relocated table, found by scanning and named with
-  `partition_table_offset`, and the dump written from `0x1000`, read with
-  `flash_offset` and, without it, left an ESP image whose `flash_dump`
-  names `flash_offset` `0x1000`;
-- an app with a flipped byte beside valid partitions, and a truncated dump,
-  read with complete coverage and its missing partitions as entries with no
-  bytes.
-
-The lane ran on macOS arm64 with Node 24.22.1, Homebrew Clang and LLD 21.1.8
-and ESP-IDF v5.5.2's `gen_esp32part.py`, `otatool.py` and `parttool.py`,
-once with esptool v5.6.0 and once with 4.12.0. Its `gen_esp32part.py` is
-identical to v6.1's, and its otatool and parttool differ only in import style
-and esptool command spelling. All checks passed in both runs. With v5.6.0 and
-the build already cached, the run took 24.1 s elapsed, 16.9 s user CPU and
-6.3 s system CPU under `/usr/bin/time -l`; the largest single process peaked
-at a 278 MiB resident set, and the combined peak of all processes was not
-measured.
-
-The lane does not establish:
-
-- dumps read from a device: its dumps come from `merge-bin`;
-- chips other than ESP32-C3 and ESP32;
-- `ota_state` and record validity, which `read_otadata` does not print, or
-  OTA states the bootloader writes itself, app rollback or anti-rollback;
-- selection with gaps or repeated OTA subtypes, which otatool does not
-  write;
-- flash-encrypted dumps, which are not recognized by design.
-
-It does not run in CI.

docs/esp-image.md

@@ -223,26 +223,9 @@ first byte that is not erased starts a range to the end of that region. A
 slot that is neither a block nor erased is reported whole. Adjacent ranges
 are merged.
 
-A whole-flash dump whose partition table REA finds is read as an
-[ESP flash image](esp-flash-image.md). Without one, a dump of a chip whose
-bootloader is at offset 0, such as ESP32-C3 or ESP32-S3, is recognized as that
-bootloader image, and the partition table, apps and data follow as
-undescribed bytes.
-
-A dump read from a later flash address, such as an ESP32 dump read from
-`0x1000` with `read-flash 0x1000 …` or `merge-bin --target-offset 0x1000`,
-opens as its bootloader image. REA says so when the file shows it: the image
-at file offset 0 is not an app, its chip's ROM loads the bootloader from a
-later address (`0x1000` for ESP32 and S2, `0x2000` for C5, H4, P4 and S31),
-and a partition table sits where that origin puts `0x8000` (file offset
-`0x7000` for `0x1000`), after the image ends. Then `flash_dump` records
-`flash_offset` and
-`table_file_offset`, a limitation says to reopen the file with
-`format: "esp-flash-image"` and that `flash_offset`, and `inspect_artifact`
-lists the same `open_binary` call as a next probe. `flash_dump` is null for
-every other image. Evidence that REA recorded before it reported the field
-omits it; REA still reads and compares such Evidence, and the omission says
-nothing about where the file was read from.
+A whole-flash dump of a chip whose bootloader is at offset 0, such as
+ESP32-C3 or ESP32-S3, is recognized as that bootloader image; the partition
+table, apps and data follow as undescribed bytes.
 
 ## Limits
 

docs/evm-bytecode.md

@@ -28,15 +28,6 @@ The host must already provide util-linux `prlimit`, normally `/usr/bin/prlimit`;
 no system tools and changes no user configuration. [Upstream provenance and
 license](https://github.com/morluto/rea/blob/main/third_party/evmole/README.md) are packaged.
 
-Limiter discovery validates the selected path without launching it. A relative
-path or directory is reported as `not_configured`, a missing file as
-`executable_missing`, and denied access or another filesystem-probe failure as
-`runtime_unavailable`. Recovery names the selected path and
-`REA_EVM_PRLIMIT_COMMAND`; denied access asks for execute permission and
-filesystem access. The original admission or system code stays in diagnostics.
-An available filesystem probe does not verify the selected tool's version or
-util-linux compatibility, and REA does not substitute another command.
-
 ## Evidence semantics
 
 - `encoding` is required: raw bytes or UTF-8 hex, with optional `0x` prefix and

docs/firmware-analysis.md

@@ -26,9 +26,6 @@ REA does not install these tools, their dependencies or system packages. It
 checks the tool's `--version` banner when executing a request. Binwalk must
 print `binwalk <version>` and Unblob must print the version alone. Inspection and
 extraction have independent prerequisites; one does not require the other.
-Capability discovery recommends `REA_BINWALK_COMMAND` for missing inspection
-and `REA_UNBLOB_COMMAND` for missing extraction. Configuring the other engine
-does not enable the unavailable operation.
 Both require util-linux `prlimit`, normally `/usr/bin/prlimit`; override its
 absolute path with `REA_FIRMWARE_PRLIMIT_COMMAND` if needed. `rea doctor` does
 not currently inspect firmware readiness. Engine selection/version checks run
@@ -303,17 +300,6 @@ v2 signature blocks. `extract-artifact` / `extract_artifact` writes one file
 per segment and signature block. Reading is portable and needs no external
 tool. See [ESP images](esp-image.md).
 
-## Inspect ESP flash dumps
-
-Use the same tools on a whole-flash dump, such as `esptool read-flash 0 ALL`
-output. The inventory reports the bootloader, the partition table and how it
-was found, each partition with its declared type, flags and digest, ESP image
-facts for the bootloader and each app partition, and the OTA records with a
-derived selection; the running partition stays unknown. Extraction writes
-each partition, `nvs_keys` included, as an ordinary file. For a dump that
-does not start at flash address 0, select `esp-flash-image` with
-`flash_offset`. See [ESP flash images](esp-flash-image.md).
-
 ## Inspect extracted devicetrees
 
 Use [`inspect_devicetree`](devicetree.md) / `rea inspect-devicetree` on an
@@ -343,15 +329,6 @@ payloads stay as stored. Intel HEX/S-record and FIT images are separate
 readers and are not covered here. See [U-Boot legacy uImage](uimage.md) for
 component padding, preserved names, resource policies and verification scope.
 
-## Inspect UF2 and DfuSe images
-
-Use `inspect-artifact` / `inspect_artifact` on a UF2 file for each familyID's
-address regions and its block numbering, or on a DfuSe file for its targets,
-elements and DFU suffix, then `extract-artifact` / `extract_artifact` for one
-raw file per region or element. A DfuSe suffix CRC mismatch follows
-`integrity_policy`. Decoding is portable and requires no external tool. See
-[UF2 and DfuSe images](uf2-dfuse.md).
-
 ## Inspect U-Boot FIT images
 
 Use `inspect-artifact` / `inspect_artifact` on a U-Boot FIT (`.itb`) for its

docs/flutter-analysis.md

@@ -109,13 +109,9 @@ server; older servers keep the complete request after schema discovery.
   header check does not establish valid table contents or exported symbols.
 - **`libflutter` facts** are per-ABI observations: byte size, SHA-256
   digest, GNU build IDs from ELF-declared `PT_NOTE` / `SHT_NOTE` ranges,
-  and Dart/toolchain strings the build carries. `dart_version` accepts the
-  labeled `Dart VM version:` form and the unlabeled Dart
-  `Version::String()` form (`<version> (<channel>) (<commit time>)` with an
-  optional ` on "<os>_<arch>"` suffix) that release engines embed. An
-  unlabeled match is a candidate based on its shape; it is not bound to a
-  Dart symbol and another string can match. `null` means no supported pattern
-  was found, not proof that no version exists. Android clang/LLVM toolchain
+  and any _labeled_ strings the build
+  carries. Release engine builds often strip the `Dart VM version` string —
+  absence is reported as `null`, not guessed. Android clang/LLVM toolchain
   lines are reported verbatim as build provenance.
   `build_id_candidates` preserves distinct IDs. `build_id` is populated only
   when all declared note ranges were examined and one ID was found;
@@ -126,13 +122,10 @@ server; older servers keep the complete request after schema discovery.
   Compressed `SHT_NOTE` sections are skipped with an unsupported-compression
   limitation and partial coverage; IDs from other note ranges remain candidates.
   Encoded note storage is never interpreted as note headers or inflated.
-- Version and toolchain strings must fit their complete grammar.
-  `dart_version_capped` and `toolchain_capped` independently report labels
-  omitted by grammar or projection bounds; either makes identification
-  coverage partial. Values split across read chunks are retained without
-  publishing truncated prefixes. Unlabeled runs that miss the
-  `Version::String()` grammar are ignored and do not set
-  `dart_version_capped`.
+- Labeled strings must fit their complete grammar. `dart_version_capped`
+  and `toolchain_capped` independently report labels omitted by grammar or
+  projection bounds; either makes identification coverage partial. Values
+  split across read chunks are retained without publishing truncated prefixes.
 - **`coverage: "partial"`** also appears when an ABI carries `libapp.so`
   without `libflutter.so` (or vice versa).
 - The APK itself is digested before parsing, so `target.sha256` binds the

docs/ghidra-mips.md

@@ -39,9 +39,9 @@ bridge-reported `language_id` after import. A caller-selected
 pin; combining the pinned profile with an environment override is a typed
 refusal. A header that declares an ABI field but carries no record is still
 refused. Two further boundaries apply: an inspection that could not examine
-every ABI declaration source does not establish the recordless admission
-(target opening already refuses a carved ELF whose section table extends past
-the captured bytes, as described below), and an `EF_MIPS_ARCH_1` or
+every ABI declaration source (for example a carved ELF whose section table
+extends past the captured bytes without a program-header record) does not
+establish the recordless admission, and an `EF_MIPS_ARCH_1` or
 `EF_MIPS_ARCH_32` header that _declares_ an ABI is refused rather than
 relabeled, because the declared-ABI lane is verified for
 `EF_MIPS_ARCH_32R2` headers only. The recordless MIPS-I lane pins the same
@@ -77,16 +77,13 @@ argument ABI and unknown nonzero MSA values remain unsupported. Without a
 separate ABI flags record, FP attribute values are admitted only when absent,
 `ANY` (0), double precision (1), or FPXX (5), the values covered by the
 recordless profile. Parsed values are retained in the MIPS analysis profile.
-A carved ELF whose section header table extends beyond the captured file is
-refused when the target is opened, before provider selection, as is every ELF
-declaration beyond EOF ([installation](installation.md#ghidra)). The refusal
-names the declared range and the file size. It applies even when a
-program-header ABI record was captured: an uncaptured section header could
-carry an unsupported or conflicting declaration, so the captured bytes are not
-analyzed as a complete smaller program. The provider also refuses any ABI
-declaration inspection that reports unexamined headers. A missing
-program-header record does not make ABI declarations in uncaptured sections
-absent or supply a default ABI.
+For carved ELFs whose section table extends
+beyond the captured file, REA examines every complete captured section header
+and records the unavailable headers as a limitation. The provider refuses an
+incomplete ABI declaration inspection even when a program-header ABI record is
+valid, because an unavailable section header could carry an unsupported or
+conflicting declaration. A missing program-header record does not make ABI
+declarations in uncaptured sections absent or supply a default ABI.
 The field layout follows
 [`Elf_MIPS_ABIFlags_v0`](https://github.com/bminor/glibc/blob/master/elf/elf.h).
 
@@ -260,13 +257,11 @@ observations and does not relabel the upstream result as verified.
 
 CLI/MCP discovery and decompilation, direct calls, target/profile/Evidence
 identity, snapshot round-trip and final process cleanup remain covered.
-For both byte orders, the lane also cuts the image one byte before its section
-header table, after checking that every program header and payload stays
-captured. `open_binary` and the CLI must both refuse that copy before provider
-selection as `target_unavailable` with constraint `file_format_rejected`,
-naming the declared section-table range and the captured size, and leave it
-unchanged. Caller-selected Ghidra heap limits are passed to the lane's CLI and
-MCP child workflows.
+For both byte orders, the lane also carves away the section table while retaining
+all program-header payloads. It checks the actual Ghidra language, entry-address
+decompilation, distinct artifact digest and missing-section limitations through
+CLI Evidence and an MCP-produced snapshot. Caller-selected Ghidra heap limits
+are passed to these child workflows.
 For soft-float fixtures the lane also checks, through `inspect_native_api`, the
 exact parameter and return types and storage of float, double, mixed (pair
 alignment and stack spill) and struct-returning functions; that a caller's

docs/ghidra-provider.md

@@ -31,8 +31,7 @@ operation-scoped JVM `OutOfMemoryError` observations retain their separate resou
 classification. Automatic kernel or cgroup OOM attribution is not implemented.
 
 After the authenticated startup handshake, rejected inputs (`invalid_request`,
-`not_found`, `ambiguous`, an invalid function name, or an address without one
-exact file offset) use
+`not_found`, `ambiguous`, or an invalid function name) use
 `diagnostics.diagnostic_scope: "request"` when their active output checkpoint is
 available. They preserve the active request's
 `failure_output`, target/profile identity and runtime/log coordinates, while
@@ -172,11 +171,6 @@ have no file backing. ELF mappings are observed
 without independent format-specific load-image verification, as the result's
 status and limitations state.
 
-Relocation rows retain Ghidra's `symbol` value, including an empty string or
-null when returned by Ghidra. It is a provider observation, not proof of the
-runtime-resolved address. Older Evidence may not have recorded this field;
-a relocation page requesting it reports that uncertainty.
-
 For large relocation inventories, select MCP `inspect_native_load_image` with
 `detail: "summary"`. It returns verification state, observed identity and counts,
 while retaining complete Evidence. Use `normalized_result.parent_evidence_id`

docs/ghidra-psp.md

@@ -85,9 +85,9 @@ node scripts/verify-real-ghidra-mips.mjs --psp-missing-extension
 npm run verify:ghidra:mips
 ```
 
-The generic verifier also checks that a section-truncated firmware copy is
-refused when the target is opened. That check runs only in generic mode; the
-PSP report explicitly records carved-PSP coverage as not run.
+The generic verifier also exercises a section-truncated firmware fixture. That
+check uses generic MIPS symbols and language expectations and runs only in generic
+mode; the PSP report explicitly records carved-PSP coverage as not run.
 
 The maintained PSP fixture builds from `tests/conformance/psp/`, never executes,
 and is independent of commercial game data. PSP GNU tools supply ELF/ABI,

docs/ghidra-riscv.md

@@ -9,43 +9,29 @@ lane shape as [generic MIPS support](ghidra-mips.md).
 
 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`, `e_flags`, and the ISA string that `.riscv.attributes`
-declares. Recognition does not mean every provider or RISC-V variant is
-supported. Existing PE, managed and Mach-O architecture sets are unchanged.
-Headerless inputs use the separate [raw-binary admission
+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. Headerless inputs use the separate [raw-binary admission
 boundary](raw-binary.md); raw RISC-V images are not supported.
 
-The Ghidra lane admits little-endian `ET_EXEC` images with no `EF_RISCV_RVE`,
-`EF_RISCV_TSO`, or any bit outside `EF_RISCV_RVC | EF_RISCV_FLOAT_ABI`, in one
-of three lanes:
-
-- ELF64 or ELF32 images that declare `EF_RISCV_FLOAT_ABI_DOUBLE` use Ghidra's
-  stock double-float model unchanged. Their `.riscv.attributes` is not read for
-  admission.
-- ELF32 images that declare the soft-float ABI (`e_flags` float-ABI bits `0`,
-  ilp32) use REA's [ilp32 calling-convention policy](#ilp32). They must also
-  declare an RV32I base and only [decoded extensions](#isa-declarations) in
-  `Tag_RISCV_arch`.
-
-These are header declarations, not proof that every instruction conforms to
-that ISA.
+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`, lane `elf64-exec-le-double-float-generic-v1`                                |
-| Little-endian ELF32 `ET_EXEC`, double-float ABI                            | admitted, `RISCV:LE:32:default` + `gcc`, lane `elf32-exec-le-double-float-generic-v1`                                |
-| Little-endian ELF32 `ET_EXEC`, soft-float ABI, decoded extensions only     | admitted, `RISCV:LE:32:default` + `gcc` with the `__rea_ilp32` prototype, lane `elf32-exec-le-soft-float-generic-v1` |
-| ELF32 soft-float ABI without `Tag_RISCV_arch`, or with any other extension | refused; the reason names the extensions outside the decoded set                                                     |
-| ELF32 single-float ABI (ilp32f)                                            | refused until its [written policy](#ilp32f) is implemented and verified                                              |
-| ELF64 soft- or single-float ABI (lp64, lp64f), or the quad-float ABI       | refused; no verified calling-convention policy                                                                       |
-| 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                                                       |
-| Reserved or newer `e_flags` bits                                           | refused with the offending bits named                                                                                |
+| 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
@@ -72,193 +58,15 @@ with the `gcc` compiler specification per class, records
 pin without changing the requested override. An override that matches the pin is
 accepted and recorded as `configured-v1`.
 
-The soft-float lane pins the same `RISCV:LE:32:default` language. Every RV32
-language in Ghidra 12.1.4, including the deprecated soft-float `RV32I`, `RV32IC`
-and `RV32IMC` variants in `old/riscv_deprecated.ldefs`, uses the same
-`riscv.ilp32d.sla` decoder; only the compiler specification differs. REA keeps
-the generic language and corrects the calling convention instead.
-
-## Calling conventions
-
-Ghidra's generic RV32 compiler specification, `riscv32-fp.cspec`, models the
-ilp32d ABI. Its default prototype passes `float` and `double` values in
-`fa0`–`fa7` and returns them in `fa0`, and it passes a structure of one or two
-floating-point members in floating-point registers. An ilp32 image passes all
-of these in integer registers. Measured on Ghidra 12.1.4 with an ilp32 build of
-the fixture in `tests/conformance/c/riscv-float-abi.c`, the stock model
-decompiles `rea_riscv_abi_pick(1.5f, 2.5f, sel)` as
-`rea_riscv_abi_pick(in_fa0,in_fa1,0x3fc00000)`.
-
-### Decision record: D3, RISC-V float ABIs
-
-Decided in [#7477](https://github.com/morluto/rea/issues/7477).
-
-- **Choice.**
-  - Admit little-endian ELF32 `ET_EXEC` images that declare the soft-float ABI
-    (ilp32) through a new lane, `elf32-exec-le-soft-float-generic-v1`. Lane ids
-    are built from their fields: `elf<class>-exec-le-<float ABI>-float-generic-v1`.
-  - Keep the pinned `RISCV:LE:32:default` language and `gcc` compiler
-    specification. After analysis, `ReaGhidraRiscvCallingConvention.java`
-    derives the program-specific `__rea_ilp32` prototype from the program's
-    default prototype as the [ilp32 policy](#ilp32) states. It installs the
-    prototype through a Ghidra specification extension and assigns it, with
-    dynamic storage, to every non-thunk function, every external function and
-    every function definition. Thunks follow their targets. The script fails,
-    and writes no report, if the derived prototype or any function still
-    places a value in a floating-point register, or if the prototype does not
-    pass a 16-byte value by reference.
-  - One derivation serves every policy. A policy row says how it changes the
-    default prototype's floating-point entries and preserved registers; every
-    policy passes values of 9 bytes or more by reference.
-  - The profile commits `riscv_calling_convention: ilp32-prototype-v1`. The
-    bridge reports the policy and its function and definition counts, and REA
-    requires that report exactly when the profile commits the policy.
-  - Admission requires a `Tag_RISCV_arch` declaration with an RV32I base and
-    only extensions that Ghidra 12.1.4's generic RV32 language implements with
-    p-code ([ISA declarations](#isa-declarations)).
-  - Soft-float profiles add `float_abi` and `arch` to `riscv_elf`. Double-float
-    profiles keep their exact parameters, so their digests, sessions and
-    snapshots are unchanged.
-  - ilp32f keeps its [written policy](#ilp32f) and stays refused until its
-    prototype is implemented and verified. Quad-float, RVE, TSO, and ELF64
-    soft- or single-float images stay refused.
-- **Alternatives** (and what switching to each would take):
-  - Pin the deprecated soft-float languages (`RISCV:LE:32:RV32IMC` and others,
-    `riscv32.cspec`): REA's language catalog would have to read `old/`, the
-    variants cover only I, IC and IMC, Ghidra marks them deprecated, and no
-    stock specification models ilp32f.
-  - Assign `__rea_ilp32` only to callables whose types use floating-point
-    values, as the MIPS soft-float lane does: typed storage is the same, but
-    prototypes Ghidra infers for untyped code would keep the ilp32d model. In
-    an ilp32 image that contains F or D instructions, that model can still
-    claim `fa0`. Switching is one predicate in the Java script and a new
-    policy id.
-  - Admit with a limitation and no correction: a reduced-capability contract
-    that needs its own review, because arguments, returns and aggregates
-    become unverified.
-  - Keep refusing: the lane rows become refusals again.
-  - Admit images without `Tag_RISCV_arch`, or refuse a list of known
-    extensions instead of admitting a list: a declaration that REA cannot
-    check would be treated as compatible. Widening the decoded set later is
-    additive.
-  - Add `float_abi` and `arch` to double-float profiles as well: one shape for
-    every lane, but every existing RISC-V session and snapshot would be
-    invalidated.
-  - Ship ilp32 and ilp32f together (the question in #7477): ilp32f needs a
-    float-and-integer structure rule that Ghidra's model lacks, so it ships
-    separately with its own fixtures.
-- **Semantic owner and consumers.**
-  - Owners:
-    - `src/domain/riscvIsaDeclaration.ts` owns the float-ABI vocabulary of
-      `e_flags` and the parsing of `.riscv.attributes` and `Tag_RISCV_arch`.
-    - `GHIDRA_RISCV_LANES`, `GHIDRA_RISCV_CALLING_CONVENTIONS` and
-      `GHIDRA_RISCV32_DECODED_EXTENSIONS` (`src/ghidra/GhidraRiscvProfile.ts`)
-      own admission, lane ids and the policy table.
-    - `bridge/ghidra/ReaGhidraRiscvCallingConvention.java` owns how each policy
-      becomes a Ghidra prototype.
-  - Consumers: target resolution, Ghidra provider admission, the analysis
-    profile, the provider client and launcher, the session handshake, project
-    history, the real-Ghidra lane and this page. Later work reuses the table:
-    ilp32f adds a row, and RISC-V ESP images (F6) select a row through D5.
-- **Costs of changing it.**
-  - **Code:** S. A policy or lane is one table row plus the Java derivation.
-  - **Compatibility:** the soft-float lane id, `riscv_elf.float_abi`,
-    `riscv_elf.arch` and `riscv_calling_convention` are persisted in sessions,
-    snapshots and Evidence once released. A changed derivation ships as a new
-    policy id, such as `ilp32-prototype-v2`, which invalidates soft-float
-    snapshots only.
-  - **Migration:** none for admitted targets; double-float profiles are pinned
-    by tests. Previously refused soft-float targets become admitted.
-  - **Verification:** rerun `npm run verify:ghidra:riscv`.
-
-### ilp32
-
-Policy `ilp32-prototype-v1`, prototype `__rea_ilp32`. XLEN is 32 bits and no
-floating-point register passes a value.
-
-| Topic                      | psABI rule                                                                                                                                                                                        | `__rea_ilp32`                                                                                                                       |
-| -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------- |
-| Integer and pointer values | `a0`–`a7`, then the stack in 4-byte-aligned slots                                                                                                                                                 | The default integer and stack entries, unchanged                                                                                    |
-| `float`                    | One integer register, or a stack slot                                                                                                                                                             | The `fa0`–`fa7` entries and the `float` rule are removed, so a `float` takes the next integer register                              |
-| `double` and 8-byte values | A register pair with the low word in the lower register. Named arguments need no aligned pair. With one register left, the low word goes in `a7` and the high word on the stack                   | The default `join` rule with stack spill: Ghidra writes `a2:4,a1:4` for a pair and `Stack[0x0]:4,a7:4` for the split                |
-| Aggregates up to 8 bytes   | One or two integer registers, laid out as in memory, also when every member is floating-point                                                                                                     | The homogeneous-float-aggregate rule is removed; the `join` rule applies                                                            |
-| Aggregates over 8 bytes    | By reference: the caller passes the address of a copy                                                                                                                                             | The default rule that converts structures and unions of 9 bytes or more to pointers                                                 |
-| Return values              | As the first argument of the same type: `a0`, or `a0` and `a1`. Larger values go to a caller buffer whose address is an implicit first argument in `a0`                                           | The `fa0`/`fa1` return entries and floating-point rules are removed; Ghidra's hidden-return fallback supplies the pointer in `a0`   |
-| Variadic arguments         | The integer convention. A variadic argument with 8-byte alignment and size takes an aligned (even-numbered) register pair, or the stack; after the first stack argument, the rest go on the stack | The default variadic rule (`join` with alignment), unchanged                                                                        |
-| Preserved registers        | `s0`–`s11` and `sp`; `gp` and `tp` are not allocated. No floating-point register is preserved                                                                                                     | The default preserved list without `fs0`–`fs11`, which join the killed-by-call list                                                 |
-| Scalars over 8 bytes       | By reference (`long double` is 16 bytes), and returned through a caller buffer                                                                                                                    | A rule before the final join converts any value of 9 bytes or more to a pointer; a return that size already goes to a caller buffer |
-
-Ghidra recovers the arguments of a variadic call from the registers the caller
-writes, not from their types. A padding register that still holds an earlier
-value can appear as an argument, and arguments after an unwritten register are
-omitted.
-
-### ilp32f
-
-Written policy for `EF_RISCV_FLOAT_ABI_SINGLE` on ELF32. REA does not admit it
-yet. ABI_FLEN is 32 bits.
-
-| Topic                                                   | psABI rule                                                                                       |
-| ------------------------------------------------------- | ------------------------------------------------------------------------------------------------ |
-| `float`                                                 | `fa0`–`fa7` while one is free, then the integer convention                                       |
-| `double` and other values wider than 32 bits            | The integer convention, as in ilp32                                                              |
-| Structure of one or two floats (after flattening)       | One floating-point register per member when enough are free, otherwise the integer convention    |
-| Structure of one float and one integer, in either order | One floating-point and one integer register when both are free, otherwise the integer convention |
-| Unions                                                  | Never flattened; the integer convention                                                          |
-| Return values                                           | As the first argument: `fa0`, `fa0` and `fa1`, or `fa0` and `a0`                                 |
-| Variadic arguments                                      | The integer convention, as in ilp32                                                              |
-| Preserved registers                                     | `s0`–`s11`, `sp`, and `fs0`–`fs11` for values of 32 bits or fewer                                |
-
-The planned prototype limits the default floating-point entries to 4 bytes and
-keeps the shared rule that passes values of 9 bytes or more by reference.
-Observed on Ghidra 12.1.4, a `double` then takes an integer pair and a structure
-of two floats takes `fa0` and `fa1`. Ghidra's model has no rule for a structure
-of one float and one integer: it joins `struct { float; int; }` into `a1:a0`
-instead of `fa0` and `a0`. The ilp32f policy needs that rule and its own
-fixtures before it is admitted.
-
-### ilp32d and lp64d
-
-The double-float lanes use Ghidra's stock `riscv32-fp.cspec` and
-`riscv64-fp.cspec` models unchanged. This page does not verify them. They share
-the float-and-integer structure gap above.
-
-## ISA declarations
-
-The target reader finds the one `SHT_RISCV_ATTRIBUTES` section and reads
-`Tag_RISCV_arch`, such as `rv32i2p1_m2p0_c2p0_zicsr2p0_zifencei2p0`. It
-retains the string, the base and the extension names, or an unavailable reason
-when the section is malformed, declares other vendors or scopes, or uses a
-non-canonical string. A missing section or tag is recorded as absent.
-
-Calling-convention lanes admit an image only when it declares an RV32I base
-and only extensions that Ghidra 12.1.4's generic RV32 language implements with
-p-code: `m`, `a`, `f`, `d`, `c`, `zicsr`, `zifencei`, and the subset names
-toolchains record, `zmmul`, `zaamo`, `zalrsc`, `zca`, `zcf` and `zcd`. Any
-other extension is refused. In particular:
-
-- Ghidra 12.1.4 decodes no Zcb, Zcmp or Zcmt instruction.
-- Its bit-manipulation, cryptography and packed-SIMD files follow draft
-  encodings and mark nearly every instruction unimplemented.
-- Vendor extensions, such as Espressif's `xesploop`, `xespv` and `xespdsp`,
-  decode only as custom-opcode placeholders.
-
-ESP-IDF builds ESP32-C2 and C3 images as `rv32imc_zicsr_zifencei` and ESP32-C5,
-C6, C61, H2 and H21 images as `rv32imac_zicsr_zifencei_zaamo_zalrsc`, all ilp32.
-Those base strings are admitted. Builds that add `_zba_zbb_zbs`,
-`_zcb_zcmp_zcmt` or an `xesp` extension are refused.
-
 ## Evidence
 
-The lane identity is one of the lane ids above, 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`. Soft-float profiles also retain `float_abi: soft`, the declared
-`arch` string, and `riscv_calling_convention: ilp32-prototype-v1`. Those fields
-report declarations the header and attributes make, and the policy REA applied;
-none of them is evidence of the original compiler or of instruction
-conformance. Session Evidence states the prototype and how many functions and
-definitions use it.
+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
 
@@ -268,9 +76,9 @@ tree ships no host decompiler binary, so `Decompiler/os/<platform>/decompile` an
 [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, LLVM readelf and LLVM objdump. The
-verifier acquires no tools and never executes target code. Select installed
-tools explicitly when they are not on `PATH`:
+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 \
@@ -278,52 +86,20 @@ 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 \
-REA_RISCV_OBJDUMP=/path/to/llvm/bin/llvm-objdump \
 npm run verify:ghidra:riscv
 ```
 
-The lane builds four `ET_EXEC` fixtures from committed freestanding C and
-assembly sources:
+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.
 
-- RV32 and RV64 double-float builds (`rv{32,64}imafdc`) of `riscv.c`.
-- An RV32 soft-float build of `riscv-float-abi.c` with ESP32-C3's
-  `-march=rv32imc_zicsr_zifencei -mabi=ilp32`, typed with DWARF.
-- The same objects linked with `--strip-all`. Every allocated section keeps
-  its address and bytes, so the typed build's symbols locate its functions.
-
-Independent LLVM readelf observations establish ELF declarations,
-`Tag_RISCV_arch` and symbol addresses. Public CLI and stdio MCP workflows verify
-function enumeration, decompilation, pinned language/compiler identity, the
-committed lane and policy, decoded probe bytes, global data, and direct calls.
-They validate advertised MCP output schemas and both JSON representations, save
-and reopen snapshots, and check unchanged source bytes and owned cleanup.
-
-For the soft-float builds the lane also checks:
-
-- `fence.i` and `csrr` decode, as ESP32-C3's Zifencei and Zicsr declare.
-- An LLVM objdump reading of `rea_riscv_abi_caller` finds each call-site word
-  where the [ilp32 policy](#ilp32) puts it: an unaligned `double` in `a1`/`a2`,
-  the `a7`/stack split, two floats in an integer pair, a large structure and a
-  `long double` passed by reference (the pointed-to copies hold the source
-  values), aligned variadic pairs, and an indirect call.
-- `inspect_native_api` reports `__rea_ilp32` with exactly that storage for the
-  typed build. The stripped build has one integer word per parameter location
-  and returns in the typed build's registers, or in none when the result goes
-  through caller memory.
-- The caller's pseudocode passes the source constants through that storage and
-  names no floating-point register.
-- Retained Evidence states the prototype outcome; the stripped build has no
-  function definitions.
-
-Header-mutated copies check admission. The RV32 double-float image relabelled as
-soft-float (`e_flags` `0x1`), refused before this lane, is admitted through the
-soft-float lane over CLI and MCP. The soft-float image relabelled as
-single-float, RV64 soft-float, and unsupported high bits are refused with their
-reasons. Failures retain the diagnostic workspace; successful runs remove it and
-report the observed process lineage.
-
-Module tests cover admission, malformed headers and attribute sections, the
-handshake, and the conformance checks against recorded LLVM and Ghidra output.
-Call-graph completeness, string inventories, dynamic linkage, Andes or RVE/TSO
-images, big-endian targets, ilp32f images, and decoding beyond the probes are
-**not** established by this lane.
+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.

docs/ida-provider.md

@@ -43,8 +43,7 @@ rea decompile /absolute/path/to/program main --json
 
 If the registration cannot be read or validated, provider diagnostics retain its
 selected `registration_path` and the configuration owner's setting/constraint
-facts in `configuration_details.settings`. The availability's `remediation`, and
-each operation it makes unavailable, carry the configuration owner's repair.
+facts in `configuration_details.settings`, plus `configuration_remediation`.
 `configured` means a path was selected, not that it is valid or an IDA connection
 was established; failed registrations remain unavailable. Correct
 `REA_IDA_MCP_CONFIG` in the next CLI invocation's environment or the MCP server's

docs/index.md

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

docs/ines-containers.md

@@ -1,72 +0,0 @@
-# Classic iNES container inspection
-
-REA recognizes classic iNES from the `NES` + `0x1a` byte signature, independently
-of the file extension. This read-only container inspection uses portable
-Node.js file reads; it needs neither Ghidra nor an emulator.
-
-```bash
-rea inspect-artifact ./cartridge.nes --json
-rea extract-artifact ./cartridge.nes --json
-```
-
-Through MCP, call `open_binary` with the local path, then `inspect_artifact`.
-Use `extract_artifact` to materialize the regions in the fresh directory named
-by its result. The caller owns that successful extraction directory.
-
-## Header and file regions
-
-Inspection returns `container-header` and `reconstruction` observations inline.
-The single inventory Evidence under `substeps[].evidence.normalized_result`
-contains the complete graph and an `ines` object:
-
-- `ines.header`: original 16-byte `header_hex`, PRG/CHR file-unit counts, mapper,
-  raw flags 6/7, trainer and battery flags, and the declared mirroring mode.
-- `occurrences[]`: each region's path, `source_location.offset` and
-  `source_location.length` in the original container. Follow `artifact_id` to
-  the node's observed SHA-256 and byte count.
-- `ines.reconstruction`: ordered region paths, concatenated byte count,
-  SHA-256 and `verified: true`. REA accumulates the concatenation digest during
-  the same physical-order region scan that produces node hashes, then compares
-  it with the original whole-file digest. Final source freshness is also checked.
-  No reconstructed file is written during inspection.
-
-Regions are `header.bin`, optional `trainer.bin` (512 bytes),
-`prg/000.bin` onward (16 KiB each), `chr/000.bin` onward (8 KiB each), and
-optional `trailing.bin`. Every input byte is retained, including unused header
-fields and uninterpreted trailing data. Zero CHR-ROM units create no CHR region;
-REA does not fabricate CHR-RAM contents.
-
-After extraction, concatenate the materialized files in
-`ines.reconstruction.region_order` from the inspection inventory. Their bytes
-reproduce the input exactly. Graph path order is lexical and is not physical
-file order; use the explicit region order or source offsets.
-
-## Supported boundary
-
-This increment supports classic iNES with a complete 16-byte header, nonzero
-PRG count, complete declared trainer/PRG/CHR payload, and zero reserved bytes
-12–15. Dirty legacy headers are refused because their upper mapper bits are
-ambiguous; REA does not silently repair them. NES 2.0 and UNIF signatures,
-unsupported header variants and truncated payloads are explicitly refused.
-An arbitrary file named `.nes` is not admitted as iNES.
-
-The PRG/CHR units describe file storage, not mapper bank sizes or CPU windows.
-The mapper number and flags are header declarations, not proof of cartridge
-hardware or runtime behavior. Bank switching, 6502/65816 disassembly, emulator
-sessions and interpretation of console-specific trailing data remain outside
-this lane. Raw-binary Ghidra analysis is a separate workflow. This container
-increment addresses the first milestone of [#2072](https://github.com/morluto/rea/issues/2072);
-the related [#1641](https://github.com/morluto/rea/issues/1641) tracks 6502/65816
-native analysis with explicit load addresses and provider limitations. Extracted
-PRG units still need caller-selected CPU windows before static code analysis;
-their physical file offsets do not establish those addresses.
-
-Source-owned byte fixtures verify original offsets and hashes, extraction and
-byte-exact reconstruction, CLI/stdio MCP parity, malformed/unsupported inputs,
-failed target-switch recovery, cancellation and source identity. These checks
-do not establish emulator behavior or compatibility with every historical ROM.
-The portable CLI/stdio MCP acceptance and source-identity checks run in Linux
-and macOS CI. The same workflows have also been executed on native Windows x64.
-
-Format references: [iNES](https://www.nesdev.org/wiki/INES) and
-[NES 2.0](https://www.nesdev.org/wiki/NES_2.0).

docs/installation.md

@@ -390,20 +390,6 @@ A scoped report has `scope.mode: "explicit"`. Its `scope_checks` determine
 `environment_healthy` summarizes the full audit. `--target` adds a target check,
 but the report remains audit-wide unless a scope option is also supplied.
 
-Provider checks read the terminal running doctor. A client-started server may
-receive a different environment, and doctor cannot observe it. When an available
-provider relies on a setting that a registration's file does not record, or
-records with other text, doctor adds a non-blocking
-`registration_environment:<client>` check with `classification: "unknown"`. The
-setting names appear in that registration's `provider_settings`. Selecting the
-client or an affected provider places the check in `scope_checks`; it never
-changes `healthy`, because the client may still pass the setting on. Preview
-`rea setup --client <client-id> --skill=false --dry-run` from that terminal and
-approve it to record the settings, then restart the client. To see what the
-running server can use, call `binary_session` in the client and read
-`result.tool_availability`. For Hopper, only an explicit `HOPPER_LAUNCHER_PATH`
-is compared.
-
 An invalid `REA_LOG_LEVEL` fails every scope, including one client or the
 installed skill, because the executable rejects it before any command. A
 selected client also fails for every other setting that MCP startup rejects,
@@ -680,8 +666,7 @@ Hopper is separate commercial software with its own license. Its free demo has
 vendor-defined limits, and a paid license is optional. REA reuses any detected
 installation and preserves Hopper during uninstall.
 
-The automated Hopper installer supports macOS 12+, subject to the minimum
-macOS version of the current Hopper release, and x86_64 hosts running
+The automated Hopper installer supports macOS 12+ and x86_64 hosts running
 Ubuntu 24.04+, Fedora 41+, Nobara 44+, Arch Linux, CachyOS, or Omarchy. The
 official Linux packages are x86_64-only, so setup does not offer Hopper on other
 Linux architectures; configure [Ghidra](#ghidra) there instead. REA itself runs on any
@@ -690,33 +675,12 @@ an existing Hopper launcher is selected through `HOPPER_LAUNCHER_PATH`. Ghidra
 and IDA have their own provider-specific host requirements; Windows Ghidra uses
 the [experimental P0 boundary](windows-ghidra-p0.md).
 
-Bazzite uses RPM packages, but REA does not install Hopper automatically on it.
-Setup skips the Hopper offer because Bazzite is outside the supported host list,
-regardless of whether Xvfb is installed. Bazzite documents
-[containers for installing Linux packages](https://docs.bazzite.gg/Installing_and_Managing_Software/Containers/).
-If using a container, check its distribution and architecture against the list
-above. Install REA and Hopper in that container, give it access to the files you
-want to analyze, and configure your agent to launch REA there. Verify installation
-and analysis before relying on that workflow.
-
-`rea doctor` checks health; it does not offer to install Hopper. Run `rea setup`
-for installation. Setup cannot prompt when its output is redirected or during a
-container image build. To approve Hopper installation without prompts, run
-`rea setup --yes --install-hopper`.
-
-If a Hopper request fails on macOS or Linux, the setup result's `download`
-field names the request (`release_feed`, `package` or `public_key`), its `url`,
-and the observed outcome `kind`: `http_status` with `httpStatus`, `timeout`,
-`network`, `response_too_large`, or `url_refused`. The remediation names the
-same URL and outcome. HTTP 404 or 410 means the file is missing, so an
-immediate retry is unlikely to help; 5xx, 408 and 429 indicate a temporary
-service failure. The status does not establish the underlying cause or guarantee
-that retrying will succeed. Doctor and Linux launches report the same request
-and status when publisher verification cannot download the current package.
+If the Linux package download receives an HTTP failure, setup includes the
+observed HTTP status in its `download_failed` diagnostic. The status does not
+establish the underlying cause or guarantee that retrying will succeed.
 
 Hopper metadata and package downloads require HTTPS throughout the redirect
-chain; a redirect to HTTP or to a URL carrying credentials is refused before
-that destination is requested, and those credentials are not reported.
+chain; a redirect to HTTP is refused before that destination is requested.
 
 On macOS, approved setup downloads the official DMG, checks its published size
 and digest, validates the application bundle, and atomically installs it to
@@ -724,15 +688,6 @@ and digest, validates the application bundle, and atomically installs it to
 operator can choose its demo mode or activate an existing license. Homebrew and
 administrator access are not used.
 
-Each Hopper release declares its own minimum macOS version, so the setup plan
-cannot confirm support before approval. Setup compares this Mac's version with
-the release metadata's `deployment_target` before downloading the DMG, and with
-the signed application's `LSMinimumSystemVersion` before copying it. If this Mac
-is older, setup fails with `incompatible_host_version`, names both versions, and
-installs nothing. Update macOS, or install a Hopper release that supports this
-macOS version yourself and set `HOPPER_LAUNCHER_PATH`. An existing Hopper
-installation is not checked against the current release's minimum.
-
 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
@@ -773,12 +728,6 @@ Rotating signing subkeys remain bound to that primary identity.
 The feed row itself is not PGP-signed; doctor labels its display version as
 `reported_release_version`, separately from the authenticated launcher identity.
 
-Even a correctly signed package can contain a launcher whose hash disagrees with
-the feed. REA stops before installing that package. When reporting this error,
-include the release version, package format and both hashes from the diagnostic.
-Each format needs its own check: a matching Ubuntu DEB does not establish that
-the Fedora RPM matches.
-
 The approval plan includes the caller-selected cache location. Approved setup
 retains the signed archive, public key and release metadata under
 `${XDG_CACHE_HOME:-$HOME/.cache}/rea/hopper-releases/<launcher-sha256>`.
@@ -812,16 +761,6 @@ host mount and the rest of `/tmp` remain unchanged; this fallback never invokes
 `sudo`. `rea doctor --provider hopper --json` reports the selected
 strategy and both host and effective mount facts.
 
-You do not need to start a separate `Xvfb :99` server. REA starts and manages its
-own display. After installation, run `rea doctor --provider hopper --json` and
-check `hopper-demo-runtime` for display and Python problems. Setup also runs these
-health checks: installing the package is only one step toward a working provider.
-
-If an image build ends with `exit status 1`, read the setup output immediately
-before that summary to find the failing step. On minimal Ubuntu images, run
-`apt-get update` before setup if an earlier layer deleted the package indexes.
-REA's package installation commands do not refresh those indexes.
-
 Hopper also embeds Python; the Python executable and standard library alone
 are insufficient on Ubuntu. Approved setup checks the system interpreter
 at `/usr/bin/python3` and, when necessary, installs its matching
@@ -1032,9 +971,7 @@ including while a shutdown request is in flight. A helper exit alone is
 insufficient, and an application that never authenticated has no verified
 process identity. If no matching bridge becomes available, inspect and close
 the reported document in Hopper before ending the owning REA connection.
-`close_binary` preserves Evidence and complete Unknown history in memory on the
-same connection. Export the bundle before ending the REA process to resume later;
-`reset_investigation(save_path)` checkpoints and explicitly clears those records.
+Export the Evidence bundle before `close_binary` clears session records.
 `binary_session.cleanup_pending` remains true while provider cleanup is retained,
 and provider health remains visible even with `open: false`; that flag alone
 does not establish successful cleanup.
@@ -1345,8 +1282,7 @@ fails with `provider_timeout` and that message; other Ghidra tools stay
 available. If the caller also cancels while the timeout settles, the session
 still closes and the message says so. Session reuse concerns an active MCP or
 library session; a standalone CLI command still closes its own session when it
-finishes, so its timeout names `REA_GHIDRA_DECOMPILE_TIMEOUT_SECONDS` for a new
-invocation instead. In MCP, `ghidra.decompile_timeout_seconds` can override the launch
+finishes. In MCP, `ghidra.decompile_timeout_seconds` can override the launch
 value for newly accepted operations on the existing Program; explicit `null`
 removes the deadline. A transient timeout remains uncached so the same function
 can be retried after an update. See the

docs/javascript-application-workflows.md

@@ -173,14 +173,7 @@ Results follow retained node order and default to offset 0 and limit 64. Supply
 to examine relationships from that node. Other typed seeds do not search labels.
 
 The result contains the matching basis, complete reachable subgraph, terminal
-paths, authority summaries, and native handoffs. A bidirectional trace of a
-large application can exceed one MCP response. Over MCP, pass
-`view: {"kind":"summary"}` or a `feature-trace` page of `paths`, `nodes`,
-`edges`, `seed_matches` or `native_handoffs` to retain the complete trace in
-the session and return only selected rows with the trace's identity and
-coverage. Page the retained trace with `inspect_analysis_view`; an oversized
-complete reply offers its first `paths` page as a ready-to-call continuation.
-See [MCP contracts](mcp-contracts.md) for filters. A handoff binds
+paths, authority summaries, and native handoffs. A handoff binds
 the exact native artifact digest and requested exports from the application
 graph. Trace direction selects the reachable addons; requested
 exports for each selected addon come from the complete supplied graph, so an
@@ -629,10 +622,8 @@ or process workflows.
 ## CLI and verification
 
 All six CLI commands accept inline JSON or a path to a JSON file. The CLI
-returns an Evidence record directly. Later workflow inputs can contain full
-records, or exact retained references when `--evidence-bundle PATH` selects an
-authenticated exported bundle. A separate CLI process has no retained MCP
-connection state. See [CLI Evidence reuse](cli.md#import-export-and-compare-evidence).
+returns an Evidence record directly. Put the full records in a later CLI input;
+a separate CLI process has no retained MCP connection state.
 
 File inputs must be regular files; symlinks to regular files are accepted.
 Directories, named pipes and device files produce an input error before JSON
@@ -655,12 +646,8 @@ rea trace-application-feature ./trace-input.json --json
 MCP analysis returns the complete Evidence record, with the operation result
 in `normalized_result` and its identity in `evidence_id`. If the connected server advertises retained references, reuse its
 exact returned ID as `{"kind":"retained-evidence","evidence_id":"RETURNED_ID"}`
-in `application`, or `left`/`right` for comparisons. For summary or inspection
-replies, use `normalized_result.parent_evidence_id` to select the complete source.
-`RETURNED_ID` is a template, not a literal valid ID. Native-observation arrays
-and `reconcile_javascript_runtime`'s nested static layers and runtime-observation
-array also accept references where advertised, independently mixed with inline
-records. Exact identity, coverage and partial or unknown facts are preserved.
+in `application`, or `left`/`right` for comparisons. `RETURNED_ID` is a template,
+not a literal valid ID. Native Evidence arrays still use complete records.
 References are scoped to one connection; `close_binary` clears them. Export a
 bundle before closing and import it on another connection, or supply the full
 inline Evidence there. Versions before 4.1.0 accept full inline Evidence only; installing

docs/javascript-artifact-reconstruction.md

@@ -876,22 +876,8 @@ and Evidence. If that expansion does not fit, the file node retains
 `static_analysis` and any admitted `semantic_module_analysis` observations,
 including their exact values and source locations. Use the public modules item
 view to read them. The graph marks those unexpanded relationships as unknown.
-
-The parent charges everything it retains against the heap that was free when
-analysis started, less a transfer reserve. Semantic facts and expanded
-relationships stop at half of that capacity, and a source refused there keeps
-its static facts with the refusal reported. Static facts can continue to three
-quarters of it while the live heap also has room for another copy of what it
-holds, so results charged for earlier sources do not cost later sources their
-static facts when the heap can still hold them. When that share runs short,
-relationships that were reserved but not yet expanded are given up before any
-static facts, and each affected file reports the omission.
-
-If static facts themselves exhaust that share, or the parent's live heap cannot
-hold the next checkpoint, analysis stops; inventoried but unexamined files remain
-present with explicit unknown scopes. The failure reports the limit that applied
-in bytes, what was still available, the live heap in use and what the checkpoint
-needed.
+If cumulative result capacity is exhausted, analysis stops; inventoried but
+unexamined files remain present with explicit unknown scopes.
 
 ### Large local JSON inputs
 
@@ -1016,12 +1002,7 @@ reason in the renderer observations.
 HTML script source ranges follow the HTML parser across LF, CRLF, and bare CR
 line endings, preserving UTF-16 columns.
 Inline JavaScript in local HTML, meaning classic or module `<script>` bodies
-without a `src` attribute, is not analyzed. Embedded SVG scripts use `href`
-(or `xlink:href` when `href` is absent) instead: an existing reference, even
-an empty one, suppresses the inline body. SVG's `src` and HTML-only `language`
-attributes do not suppress its JavaScript body. SVG references and inline
-bodies share the same inert parsing and source coordinates as HTML scripts;
-template content stays inert. Each HTML file that has an inline body gets an
+without a `src` attribute, is not analyzed. Each HTML file that has one gets an
 unknown `parse-html-inline-scripts` scope with the exact body count and the
 script type and source range of the first 100 bodies; beyond that, coverage is
 truncated under the `html_inline_script_locations_per_file` limit, and the

docs/javascript-route-inventory.md

@@ -65,9 +65,8 @@ confidence and basis, and does not prove a backend endpoint or reachability.
 Pages obey the shared 1 MiB projection budget; MCP transport applies its own
 wire-size guard. A byte-limited page returns a continuation; an indivisible
 oversized record or metadata returns a typed resource error. Select fewer
-fields or retrieve the complete retained parent through `get_evidence_bundle`
-(`detail: "records"` with its `evidence_id`), `export_evidence_bundle`, or the
-CLI's exported bundle. Full Evidence is never
+fields or retrieve the complete retained parent through `get_evidence_bundle`,
+`export_evidence_bundle`, or the CLI's exported bundle. Full Evidence is never
 silently truncated.
 
 Collections are `summary`, `routes`, `occurrences`, `sources`, and `unknowns`.

docs/javascript-runtime-reconciliation.md

@@ -93,10 +93,6 @@ coverage. It does not print captured source text.
 Runtime targets, frames, scripts, and workers become capture-scoped graph
 nodes. REA evaluates compatible static candidates conservatively:
 
-V8 Inspector targets whose protocol type is `node` use JavaScript asset/module
-candidates for their verified entry location. A target-only correspondence does
-not mark that script loaded; load-state evidence requires a script observation.
-
 1. A captured-source SHA-256 plus one matching mapped location yields
    a content-and-location match.
 2. When no static candidate exists at a mapped location, one unique exact

docs/kuna-provider.md

@@ -1,27 +1,9 @@
 # Kuna provider
 
-[Kuna](https://github.com/Noelo-Lab/kuna) is an Apache-2.0 decompiler distributed as one `kuna` executable. For a new installation, use Kuna 1.990, REA's recommended verified release. REA uses a `kuna` you supply; it does not download, install, update or bundle Kuna. REA accepts other releases; `rea doctor` and analysis Evidence report them as unverified. Verification compares the reported version; it does not authenticate the executable. Analysis profiles retain the observed version and executable digest, independently of REA's current verified-release policy. The 1.990 real-provider checks ran on macOS arm64; Linux and other hosts have not been verified with that release.
+[Kuna](https://github.com/Noelo-Lab/kuna) is an Apache-2.0 decompiler distributed as one `kuna` executable. REA uses a `kuna` you supply. It does not download, install, update or bundle Kuna. REA verified this provider with Kuna 1.833; it accepts other releases and reports them as unverified in `rea doctor` and in each analysis profile.
 
 Kuna is static: it reads the selected image and never executes it.
 
-This profile change makes earlier Kuna analysis snapshots and resumable directory
-exports incompatible, even with the same Kuna executable. Keep the old files:
-their recorded Evidence remains historical. To continue analysis, open the
-binary without the old snapshot and save a new one, or choose a new export
-directory. Existing snapshot Evidence can be extracted from its
-`evidence_bundle` JSON member and imported as a separate Evidence bundle; that
-does not restore cached workflow entries or resume the old directory export.
-For example, using `jq` and a new output path:
-
-```bash
-jq -e '.evidence_bundle | select(type == "object")' old-snapshot.json > history.json
-rea evidence-import history.json --json
-```
-
-The CLI command validates the bundle in a one-shot session. To use the records
-in an MCP session, call `import_evidence_bundle` with the extracted file path.
-This validates the embedded bundle, not the rest of the snapshot container.
-
 ## Configure
 
 ```bash
@@ -48,10 +30,6 @@ completes. Cleanup retries keep both the observations and the exact file owner.
 | `REA_KUNA_TIMEOUT_MS`         | 120 s                                                                                                                                   | Deadline for one single-function decompile, and for the inventory run REA makes when the export ends without one.                                                                        |
 | `REA_KUNA_JOBS`               | 1                                                                                                                                       | `decompile-project --jobs`. 1 is Kuna's reference answer; more jobs finish sooner but lose callee-first prototypes, and change about 40–60% of function bodies on the measured binaries. |
 
-Pseudocode read from a parallel project export includes a prototype-context
-limitation in its Evidence, including in function dossiers and composed
-workflows. Early single-function results have their own source limitation.
-
 A single-function decompile, inventory, string, graph or xref run that exceeds its deadline fails as `provider_timeout`, naming the setting that owns the deadline and that raising it takes a restart. A project export that exceeds `REA_KUNA_PROJECT_TIMEOUT_MS` is an export failure instead: requests that need the export report `capability_unavailable` with the export's own retry guidance.
 
 Windows is not supported yet. Supported targets are ELF and thin Mach-O executables for x86-64, AArch64 and ARM; PE and universal Mach-O are rejected with a typed reason.
@@ -60,7 +38,7 @@ Windows is not supported yet. Supported targets are ELF and thin Mach-O executab
 
 | Tool                                                        | Source                                                                                                                           |
 | ----------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------- |
-| `list_procedures`, `search_procedures`, `procedure_address` | Kuna's callable inventory (`kuna functions --json`), including import slots but not [Mach-O data](#mach-o-data-entries)          |
+| `list_procedures`, `search_procedures`, `procedure_address` | Kuna's callable inventory (`kuna functions --json`), including import slots it does not decompile                                |
 | `address_name`                                              | Function entries, then the data labels Kuna's export assigns                                                                     |
 | `procedure_pseudo_code`, `batch_decompile`                  | The project export, or a single-function run while the export builds                                                             |
 | `procedure_assembly`                                        | The project export's labeled listing                                                                                             |
@@ -69,8 +47,6 @@ Windows is not supported yet. Supported targets are ELF and thin Mach-O executab
 | `xrefs`                                                     | Exact-address incoming reference sites, with forwarding aliases filtered explicitly                                              |
 | `analyze_function`                                          | Pseudocode and assembly from the export, plus call relationships; typed references, comments, strings and CFG remain unavailable |
 
-Kuna's inventory gives some entries aliases, such as ELF versioned-symbol names and generated `sub_` names. Name selectors accept an alias that names one entry and list every entry a shared alias names. `search_procedures` matches aliases too: each entry appears once under its primary name, with the matching aliases in `matched_aliases`. `list_procedures` shows primary names only.
-
 Typed procedure references, basic blocks, raw-memory tools, annotations and type recovery are not available from this provider. Use another provider for those operations.
 
 ## How answers are produced
@@ -86,7 +62,7 @@ The first text or assembly request in a session looks for this target's export i
   - Assembly and data names wait for the export; progress notifications report the wait every ten seconds. A session does not rebuild a failed export: requests that need it fail with `retryable: false`, the export's failure, its captured Kuna output and what to change before reopening the target. A setting such as `REA_KUNA_PROJECT_TIMEOUT_MS` or `REA_KUNA_JOBS` is read when REA starts, so changing it also needs a restart. Pseudocode keeps using single-function runs.
   - A single-function answer says so in its limitations. It lacks the export's whole-program prototypes, so a later request can return different text for the same function.
 
-Pseudocode, assembly, `analyze_function` and data-name answers record where their text came from in `raw_result.source`: `single-function`, or `project-export` with the cache directory. `procedure_pseudo_code` and `procedure_assembly` answers from the export also name the file, byte span and the file's SHA-256. Combined `analyze_function` answers retain both facet records in `raw_result.source.files`, each with its file, digest and byte span. Both texts come from one export; losing that project retries the complete report. Listings and procedure lookups carry no `raw_result`; omitted [Mach-O data entries](#mach-o-data-entries) are reported in their limitations. Agents can open or search the export's `.c` and `.asm` there directly when that is cheaper than calling a tool per function. Text read that way is target-derived, like any decompiler output, but it bypasses the untrusted-content marker that REA's tool results carry.
+Pseudocode, assembly, `analyze_function` and data-name answers record where their text came from in `raw_result.source`: `single-function`, or `project-export` with the cache directory. `procedure_pseudo_code` and `procedure_assembly` answers from the export also name the file, byte span and the file's SHA-256. Combined `analyze_function` answers retain both facet records in `raw_result.source.files`, each with its file, digest and byte span. Both texts come from one export; losing that project retries the complete report. Listings and procedure lookups carry no `raw_result`. Agents can open or search the export's `.c` and `.asm` there directly when that is cheaper than calling a tool per function. Text read that way is target-derived, like any decompiler output, but it bypasses the untrusted-content marker that REA's tool results carry.
 
 The background export belongs to the session. `close_binary`, or the end of a CLI command, cancels it unless another session still waits for it. A one-shot CLI decompile therefore answers from a single-function run; any request that needs the export, such as `procedure_assembly` or `analyze_function`, keeps it.
 
@@ -96,17 +72,6 @@ Regex procedure and string search uses ECMAScript Unicode matching in a cancella
 
 Single-function subprocess output and each cached source facet share a 16 MiB buffered-text capacity. Cached spans are checked before allocation; larger text remains in the local export and the error identifies the file and range. `analyze_function` with `detail: "complete"` (the CLI default) returns the complete dossier inline, which can still be large; later retained views do not remove that first transfer. The MCP default retains the dossier and returns its summary, so page the facets you need through `inspect_analysis_view`, or prefer the individual text tools for a focused question.
 
-## Mach-O data entries
-
-Kuna's inventory also lists Mach-O exports that are data, such as globals in `__DATA,__data`, constants in `__TEXT,__const` and `__mh_execute_header`. REA classifies each entry with the target's own section table, the same load-command facts `inspect_macho` reports, read from the leading bytes kept while the session's private copy is hashed:
-
-- A section with `S_ATTR_PURE_INSTRUCTIONS` or `S_ATTR_SOME_INSTRUCTIONS`, or of type `S_SYMBOL_STUBS`, holds code; the entry stays.
-- A lazy or non-lazy symbol-pointer section (`__got`, `__la_symbol_ptr`) holds import slots; the entry stays.
-- Any other section, or the header and load commands before the first section, holds data. Listings and searches omit the entry and say how many they omitted in each region. Pseudocode, assembly, `analyze_function` and `procedure_address` refuse it by name or address, and call queries refuse its name, naming its region; call queries by exact address stay validated by Kuna's graph. `address_name` and `xrefs` still accept it.
-- An address outside every section and the header stays, with a limitation saying REA cannot classify it. If the section table cannot be read, every entry stays and listings say why. Answers about one such entry, including pseudocode, assembly, `analyze_function`, `procedure_address`, call queries by name and `address_name`, carry the same limitation; code and import slots carry none.
-
-A section's attributes are the format's declaration, not proof of what runs there, and a kept entry is not proven to be a function. ELF inventories are kept as Kuna reports them. On a Mach-O target, the first listing or lookup establishes the private copy that Kuna commands also use, once per session, even when a warm export answers it.
-
 ## Strings
 
 `list_strings` and `search_strings` share one lazy `kuna strings --json --encoding all --min-length 5 --termination any --no-xrefs` scan of the digest-checked private input. Skipping references avoids program lifting, a call graph and a C export. REA validates the input, scan policy, every row and the total before caching any facts. Encoding, character count, byte length and terminator facts must agree; supplementary UTF-8 characters count as Unicode scalars. Malformed output is an error, not an empty search. REA parses the JSON as Kuna writes it instead of buffering it, so the scan has no fixed size: Kuna writes about 290 bytes per row, 31 MB for a 20 MB Ghostty binary and 179 MB (611k rows) for an arm64 Firefox `XUL`. Rows are validated one at a time, and the first contradiction stops Kuna. Text REA does not keep is dropped unassembled; kept text and retained rows are admitted against the REA process's live heap headroom as they arrive; a refusal is a `memory` resource constraint with `retryable: false`, and closing other targets or starting REA with a larger Node.js heap makes room. String scans use the whole-program `REA_KUNA_PROJECT_TIMEOUT_MS` deadline; `REA_KUNA_TIMEOUT_MS` applies to single-function decompilation. The parsed inventory belongs to one selected target/executable profile and expires on session close; Kuna diagnostics beyond their 8 MiB buffer are retained as a failure until close, while other failures are not cached.
@@ -172,7 +137,7 @@ the manifest's file identity as well as the export files. These refusal and
 migration cases are verified with controlled Kuna-format exports; they do not
 establish behavior of an independently installed Kuna release.
 
-Builds publish by one rename, so a reader sees a complete export or none. If later staging retirement fails, the typed cleanup error retains the completed export's key, directory and manifest in `published_export`. The session adopts that verified project; later queries reuse its immutable files while `project_export.cleanup_incomplete` reports the retained owner's live state. `close_binary` retries only the remaining cleanup, and a successful retry resolves prior cleanup errors. A failed export followed by failed staging cleanup retains both failures; it does not invent a publication receipt. A session keeps the export it uses from eviction only within its own REA process. If another REA process sharing the cache evicts it, the session rebuilds it; meanwhile pseudocode falls back to single-function runs. A damaged or edited export is removed and rebuilt. REA retains the file state verified with each digest, checks it before warm-cache reuse, and checks open descriptors before and after reading text. Assembly indexes are checked against the same state; a changed file makes the whole report retry rather than mixing facets from different exports. Staging moves to `trash/` for removal only after REA proves its Kuna process stopped. Staging of a process it cannot prove stopped is never swept; REA keeps it owned, retries the stop on `close_binary`, and reports it until the stop is proven; that MCP error names the same-connection retry as `recovery.kind=retry_cleanup` ([retained cleanup retry](mcp-contracts.md#retained-cleanup-retry)). Failed file removal also stays bound to its export and is retried by `close_binary`; closing does not report success while that cleanup remains. `rea doctor --provider kuna` reports the cache directory without creating it.
+Builds publish by one rename, so a reader sees a complete export or none. If later staging retirement fails, the typed cleanup error retains the completed export's key, directory and manifest in `published_export`. The session adopts that verified project; later queries reuse its immutable files while `project_export.cleanup_incomplete` reports the retained owner's live state. `close_binary` retries only the remaining cleanup, and a successful retry resolves prior cleanup errors. A failed export followed by failed staging cleanup retains both failures; it does not invent a publication receipt. A session keeps the export it uses from eviction only within its own REA process. If another REA process sharing the cache evicts it, the session rebuilds it; meanwhile pseudocode falls back to single-function runs. A damaged or edited export is removed and rebuilt. REA retains the file state verified with each digest, checks it before warm-cache reuse, and checks open descriptors before and after reading text. Assembly indexes are checked against the same state; a changed file makes the whole report retry rather than mixing facets from different exports. Staging moves to `trash/` for removal only after REA proves its Kuna process stopped. Staging of a process it cannot prove stopped is never swept; REA keeps it owned, retries the stop on `close_binary`, and reports it until the stop is proven. Failed file removal also stays bound to its export and is retried by `close_binary`; closing does not report success while that cleanup remains. `rea doctor --provider kuna` reports the cache directory without creating it.
 
 ## Verify with a real Kuna
 

docs/mcp-contracts.md

@@ -53,9 +53,8 @@ reject the summary record. Give `compare_functions` the retained dossier as
 `{"kind": "retained-evidence", "evidence_id": "<parent_evidence_id>"}`; give
 `match_native_functions` the same reference inside `left_observations` or
 `right_observations`, since its `left` and `right` take `list_procedures`
-Evidence. `build_call_path.functions` also accepts retained references to the
-complete dossiers. Request `detail: "complete"` only when the record must travel
-inline.
+Evidence. Request `detail: "complete"` for `build_call_path`, which accepts
+only inline complete dossiers.
 
 Saved records from the pre-6.6 identity projection that omitted
 `relationship_coverage: null` from its digest remain incompatible, even when
@@ -74,9 +73,7 @@ Ghidra inventories, measured load-image observations and function replies use
 `raw_result: null` when their useful facts are already preserved in
 `normalized_result`, limitations, locations and relationship coverage. Distinct
 overview details, file-offset selection roles and database types supplemented
-with derived metadata keep their upstream representation. When a Ghidra naming
-edit is not applied, `raw_result` keeps the bridge's `failures` and shared
-`conflicts` table without a second copy of the result booleans. Native load-image
+with derived metadata keep their upstream representation. Native load-image
 attestation continues to use the bridge reply locally before Evidence
 projection. Read function results from `normalized_result`; older retained
 Evidence keeps its original representation and identity.
@@ -161,9 +158,7 @@ for the error code, target details, partial observations, remediation, and the
 optional bounded `recovery` next step. `recovery.kind=inspect_input_contract`
 names the rejected operation: re-read that operation's advertised input schema
 (call `tools/list` if the catalog may be stale), correct the listed fields, and
-do not repeat the unchanged call. A well-formed request the selected target
-cannot answer, such as an address without one exact file offset, omits this
-hint; follow its `remediation.action`. `recovery.kind=inspect_timeout_state` names
+do not repeat the unchanged call. `recovery.kind=inspect_timeout_state` names
 the operation and the REA server/provider deadline. Inspect partial Evidence
 and reported cleanup state, then follow the returned remediation. Change a
 request field or REA_* setting only when the returned remediation explicitly
@@ -173,9 +168,6 @@ recommendation to change it. When it names no setting, reduce supported work;
 do not invent one. Raising only the MCP
 client's deadline cannot extend this budget. These hints never include the
 complete catalog or caller arguments.
-`recovery.kind=retry_cleanup` appears only on a `close_binary`
-`cleanup_incomplete` error whose retained resources the session will retry; see
-[retained cleanup](#retained-cleanup-retry).
 Failures omit `structuredContent`, since each advertised `outputSchema`
 describes successful results. Successful replies retain their schema-validated
 structured data and matching text projection. Oversized errors are retained
@@ -210,19 +202,8 @@ unresolved relationship reads. Cancellation remains a tool error.
 
 `trace_feature` validates each reference's containing-procedure resolution using
 the same contract as navigation context. Explicit absence remains a successful
-negative observation. If the provider reports a non-retryable capability refusal
-attributed to the owner lookup without incomplete cleanup, the reference remains visible
-with `containing_procedure.status: "unavailable"` and a residual unknown. That
-unknown does not imply references were truncated.
-Malformed provider replies return `unreadable_output` for
-`resolve_containing_procedure` before successful-result projection;
-cancellation and incomplete cleanup remain errors.
-
-For a procedure match, `procedure_references` with `direction: "incoming"` can
-provide the selected provider's reference kinds when supported. Its scope covers
-the procedure body, so compare target addresses when selecting references to the
-exact entry. It is a separate observation and does not establish runtime use or
-complete reference discovery.
+negative observation; malformed provider replies return `unreadable_output`
+for `resolve_containing_procedure` before successful-result projection.
 
 REA prepares complete MCP results within the pinned stdio client's 10 MiB
 receive-buffer budget, including both text and structured representations and
@@ -298,12 +279,6 @@ limitation and reason IDs index that page's `items.messages` dictionary. Expand
 those references to recover exact text, repeated messages, and absent versus
 empty optional fields. Failed nodes retain their original error.
 
-Retained `xrefs` Evidence also supports `native-observation` address pages and
-`native-context` source caveats. `xrefs` still returns complete Evidence by
-default and does not accept `detail`; when its MCP response exceeds the budget,
-follow the returned continuation to page the retained result. These addresses
-remain untyped; paging does not add reference kinds or establish completeness.
-
 These views reference complete source context through `source_context.digest`
 and caveat counts. Read it using the same parent with
 `view: {"kind":"native-context","facet":"overview"}`. The other facets are
@@ -330,10 +305,6 @@ offered for completed `analyze_function` results only after session recording is
 acknowledged; the complete result and its retention reference remain intact.
 Oversized native inventories likewise include a ready-to-call first
 `native-inventory` page. Reduce its limit or select fields when a row is large.
-An oversized `trace_application_feature` result includes a first `feature-trace`
-page of its retained terminal `paths`; page `nodes` or `edges` from there.
-An oversized `batch_decompile` result includes a first body-free
-`batch-decompile` page of its retained `items`; read bodies from there.
 
 A broad follow-up or `get_evidence_bundle` can also exceed the response budget; exporting
 preserves the complete session without sending it through a single MCP frame.
@@ -347,26 +318,7 @@ a provider. `retention: "complete-record"` describes stored Evidence, while
 `native_dossier.value_flow` independently reports truncation, unavailable or
 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
-or records.
-
-To read a discovered record without transferring the whole bundle, call
-`get_evidence_bundle` with `detail: "records"` and the same exact `filters`.
-The result (`kind: "evidence-record-selection"`) pages the matching complete
-records in canonical bundle (Evidence ID) order with `offset` (default 0) and
-`limit` (default 8), and reports `matching_records`, `total_retained_records`
-and `next_offset`. Each record is the retained Evidence itself, with an
-unchanged ID, subject digest, provider, profile and readback, so it works for
-any operation, including records that `inspect_analysis_view` does not support
-such as annotations. `missing_evidence_links` lists direct `evidence_links` of
-the returned records that this session or bundle does not retain; links are not
-traversed. A selection is not an Evidence bundle: it omits manifests and
-residual unknowns, cannot be imported, and describes historical observations
-rather than current provider or database state. `offset` and `limit` require
-`detail: "records"`. If one page exceeds the response budget, select fewer
-records or one `evidence_id`; a single record larger than one response still
-needs `export_evidence_bundle`, or `inspect_analysis_view` pages where its parent
-supports views.
+`detail` preserves complete canonical bundle delivery; filters require summary.
 
 Residual-unknown mutations reject missing Evidence or unknown references and
 unproven verified resolutions with nonretryable `invalid_request` diagnostics.
@@ -383,12 +335,6 @@ is null. `total` counts all matching heads; each page preserves complete records
 in stable unknown ID order. Filters apply before paging. Pages reflect current
 session state, so keep the unknown ledger unchanged while traversing it.
 
-`list_unknowns` only lists registered heads. Import restores the Unknown records
-present in a bundle; it does not turn residual question text embedded in Evidence
-into registry entries. An empty registry therefore does not establish that
-retained Evidence has no open questions. Inspect the relevant Evidence or its
-analysis view for its residual questions.
-
 Automatically retained workflow questions include their immutable result
 Evidence ID. Distinct results retain independent questions and source links;
 repeating the same result does not create another unknown. Workflow Evidence
@@ -408,26 +354,8 @@ that revision. If a list response overflows, retry on the same connection with
 the same filters and offset and a smaller limit; export if one head still cannot
 fit.
 
-To find missing sources before a downstream analysis refuses them, read
-`missing_direct_links` from the summary, or call `get_evidence_bundle` with
-`detail: "links"`. The result (`kind: "evidence-link-inspection"`) transfers no
-record payload. `filters` select the starting records, while membership is
-checked against every record in the session or file, so a filtered-out source is
-`retained`, not missing. Rows (`evidence_id`, `linked_evidence_id`, `status`) are
-in canonical order, default to `link_status: "missing"` and page with `offset` and
-`limit` (default 64); `links` counts every inspected link regardless of that
-selection. `traversal: "direct"` (the default) reads the selected records' own
-links and sets `retained_closure` to null, because it makes no closure claim.
-`traversal: "retained-closure"` also follows retained links, as composed workflows
-such as `build_call_path` do, and reports `complete` or `incomplete`; anything
-beyond a missing link remains unknown. Missing means absent from this session or
-file, not nonexistent, and neither status describes analysis coverage. Importing
-a missing source changes this membership without changing any Evidence ID.
-
 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`.
-`"detail":"records"` with an `evidence_id` filter returns that complete record,
-and `"detail":"links"` reads link membership.
 The CLI validates and materializes that local bundle under its existing memory
 budget; summary delivery does not make arbitrary large files cheap to import.
 
@@ -588,11 +516,7 @@ names, the native API record, and high-pcode facets without starting a provider.
 and limit default to 0 and 64; pseudocode uses UTF-16 code units and never
 splits surrogate pairs, while other pages count rows. Unavailable facts and
 provider limitations remain explicit. Source is
-an exact same-session retained reference, portable inline Evidence, or an
-Evidence record or bundle file. Native function, inventory, and observation
-views require the `rea.analysis` predicate; function-matching views require
-`rea.native-function-matching`. A mismatched predicate returns an
-`invalid_request` identifying `source.predicate_type`. Views are
+an exact same-session retained reference or portable inline Evidence. Views are
 a summary, a layout mitigations or linkage facet, one section/symbol/module, or
 a stable page with a caller-selected positive `limit`. Module pages include
 JavaScript assets, bundled modules, and source modules. Select an exact
@@ -631,69 +555,6 @@ the working directory). Save its complete `--json` Evidence, then use
 `inspect-analysis-view` with an `evidence-file` source and the same view. Neither
 adapter executes the target or repeats analysis for retained queries.
 
-`trace_application_feature` follows the same delivery contract. Omitting `view`
-returns the complete trace. `view: {"kind":"summary"}` or a `feature-trace` page
-retains the complete trace in the session first and returns only the selected
-facts; query further pages with `inspect_analysis_view` and the returned
-`parent_evidence_id`. The summary carries the trace identity (`trace_id`,
-`source_evidence_id`, `source_graph_id`, seed and direction), the producer's
-`summary` counts, `trace_coverage`, the traced subgraph's `graph_coverage`,
-`evidence_links` and any no-match `semantic_discovery`. A `feature-trace` page
-selects one `collection` in retained order and repeats that context:
-
-- `paths`: exact terminal paths; `where.node_ids` selects paths visiting any of
-  those nodes and `where.end_kinds` selects their terminal node kinds.
-- `nodes`: compact rows with identity, `seed`, `observation_count` and distinct
-  authority/state/confidence `basis`; `where.node_ids` and `where.kinds` filter
-  exactly, and `include_observations: true` adds each node's complete retained
-  observations.
-- `edges`: exact relationships; `where.node_ids` matches either endpoint and
-  `where.relations` the relation.
-- `seed_matches` and `native_handoffs`: the producer's exact rows.
-
-Omitted filters select all; empty arrays select none. `offset` and `limit`
-default to 0 and 64. Page `coverage` counts the selected collection only; it
-never upgrades `trace_coverage`, and graph connectivity does not prove runtime
-reachability. The CLI keeps complete trace JSON; save it and use
-`inspect-analysis-view` with an `evidence-file` source.
-
-### Selected batch decompile results
-
-`batch_decompile` returns every pseudocode body by default. `detail: "summary"`
-retains the complete batch in the session first and returns its producer counts,
-`source_provider` (the composing workflow), `source_analysis_profile_digest`,
-`decompiling_provider`, procedure identity counts, total and largest
-`pseudocode` size, and `limitation_count`. A server that retains no Evidence
-refuses the summary before analysis. Further views use the returned
-`parent_evidence_id` through `inspect_analysis_view`, or a saved Evidence file or
-portable bundle, and never repeat decompilation.
-
-A `batch-decompile` view selects one `collection` and repeats the batch counts
-and provider identities:
-
-- `items`: rows in retained order with their original `index`, so duplicate
-  selectors stay distinct. A row keeps the selector in `address`, its `procedure`
-  identity and `status`, plus `pseudocode_code_units` or its exact `error` and
-  `limitations`. `where.indices`, `where.addresses`, `where.procedure_addresses`
-  and `where.statuses` filter exactly and combine; an item with unknown identity
-  never matches `procedure_addresses`. Omitted filters select all, and empty
-  arrays select none. `offset` and `limit` default to 0 and 64.
-  `include_pseudocode: true` adds each selected body.
-- `pseudocode`: one `index`'s text in UTF-16 code-unit pages. `offset` and `limit`
-  default to 0 and 16,384, and `coverage` measures that body. An offset inside a
-  surrogate pair is refused, and a limit ending inside one stops before it. An
-  error item has no text and is refused with a pointer to `items`.
-
-Page `coverage` counts the selection only: exhausting it establishes nothing
-about functions outside the batch. Evidence `limitations` aggregate every item's
-provider observations and are not attributed to one successful item; only error
-items keep their own. A page over the response budget offers a smaller selection
-from the same `source`: fewer rows, or one body's `pseudocode` pages when a single
-row does not fit. An inline source offers none, because the record cannot be
-repeated in that reply; resend it with a smaller selection.
-`export_evidence_bundle` remains the complete alternative. The CLI has no batch command; save the Evidence and use
-`inspect-analysis-view` with an `evidence-file` source or `--evidence-bundle`.
-
 Completed `inspect_artifact` and atomic `inventory_artifact` Evidence also
 support summary and inventory views. A summary reports the manifest's expected
 counts separately from available record counts, observed entry kinds, inventory
@@ -762,24 +623,10 @@ counts, and whether the decoded graph is incomplete. Each page repeats
 budget (XLD.app: 6.7 MB), so select `detail: "summary"` on the first call.
 Delivery detail never reaches the decoder or changes the source Evidence ID.
 
-Logical Evidence source fields share one input contract across domains:
-complete inline Evidence or an exact reference to a record already retained by
-the current connection. This applies to individual sources, optional sources,
-arrays and nested sources declared by the tool's input schema:
-
-| Workflows                                                                                                   | Retained-reference inputs                                                                                             |
-| ----------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------- |
-| `compare_functions`, `compare_process_captures`, `compare_wasm_interfaces`                                  | `left`, `right`                                                                                                       |
-| `match_native_functions`                                                                                    | `left`, `right`, `left_observations[]`, `right_observations[]`                                                        |
-| `trace_application_feature`, `trace_javascript_semantics`, `compare_source_to_bundle`                       | `application`; feature tracing also accepts `native_observations[]`                                                   |
-| `compare_application_versions`, `compare_javascript_export_shapes`                                          | `left`, `right`; version comparison also accepts both native-observation arrays                                       |
-| `reconcile_javascript_runtime`                                                                              | `static_layers[].analysis`, `runtime_observations[]`                                                                  |
-| `compare_managed_members`, `verify_managed_native_boundaries`, `import_managed_reconstruction`              | Comparison `left`/`right`; verification `managed_boundaries`/`native_observations[]`; reconstruction `static_members` |
-| `project_managed_application_graph`                                                                         | `managed_artifact`, `managed_members`, `managed_native_boundaries`                                                    |
-| `project_android_application_graph`, `project_apple_application_graph`, `project_harmony_application_graph` | `inventory_evidence[]`                                                                                                |
-| `build_call_path`, `find_changed_behavior`, `correlate_static_and_runtime`                                  | `functions[]`, `comparisons[]`, or `static_comparisons[]`/`runtime_comparisons[]`, respectively                       |
-
-For example:
+`trace_application_feature`, `trace_javascript_semantics`,
+`compare_application_versions`, `compare_source_to_bundle`, and
+`compare_javascript_export_shapes` accept complete inline application Evidence
+or an exact reference to a record already retained by the current connection:
 
 ```json
 {
@@ -795,46 +642,27 @@ For example:
 ```
 
 Use the `evidence_id` returned by `analyze_javascript_application` (or another
-compatible application-graph producer). When the producer returned a summary
-or inspection page, use its `normalized_result.parent_evidence_id` to select
-the complete source, rather than the view's own `evidence_id`. Each source can
-independently be inline or retained, including within one array. Both forms use
-the same application workflow and owner validation, preserve exact source
-identity, provenance, authority, coverage and partial or unknown facts, and do
-not run the producer again. A reference cannot supply facts absent from that
-record. Workflows that follow source links also require those linked records
-in the ledger. File references are accepted only where the tool explicitly
-advertises a file selector; a retained ID does not authorize a file read.
+compatible application-graph producer). Comparisons accept this form in `left`
+and `right`; each side can independently be inline or retained. Native
+observation arrays continue to take complete inline Evidence. Results and their
+Evidence remain complete inline, and both input forms pass the same semantic,
+identity, authority, and provenance checks without running the producer again.
 
 References belong to the current connection's Evidence ledger. Opening another
 target or restarting the current target preserves retained records, including
 when provider cleanup fails; records remain available for export and retry.
-`close_binary` releases the engine and replay cache while preserving these records,
-even when no binary is active or cleanup fails. `reset_investigation` explicitly
-clears all records and Unknown revisions after draining earlier work; a healthy
-active engine remains open. Its optional absolute `save_path` saves a complete
-canonical bundle before clearing. Failed save, cancellation observed before clearing or incomplete cleanup
-preserves records, and a published file is reported even if later cleanup fails.
-A fresh connection has its own in-memory ledger; import the saved bundle to restore
-original Evidence IDs and complete Unknown history. A missing reference reports its exact ID and
+`close_binary` clears them, even when no binary is active. A fresh connection
+has its own ledger. A missing reference reports its exact ID and
 `details.reason: "missing"`; the server cannot infer
 whether it was never recorded, cleared, or retained by another connection.
 Supply complete inline Evidence, repeat its producer, or import an exported
-Evidence bundle before referencing that imported record. Export a bundle or use
-`reset_investigation(save_path)` before ending the process if the investigation
-needs it later. Retention has no automatic persistence or silent eviction.
-`binary_session.investigation` reports record/revision/head counts, estimated
-retained representation bytes and the fixed allowance derived from initial V8
-heap headroom. A capacity refusal preserves the existing investigation; checkpoint
-and reset it, or start with a larger Node heap. These byte estimates are not RSS.
+Evidence bundle before referencing that imported record. Export a bundle before
+closing if the investigation needs it later.
 
-CLI workflows that advertise `--evidence-bundle` can resolve the same reference
-JSON from one explicitly selected local bundle, including an MCP export. They
-also accept portable inline Evidence and use the same application workflows.
-A standalone CLI invocation cannot resolve another MCP connection's ledger
-without that exported bundle. See [CLI Evidence reuse](cli.md#import-export-and-compare-evidence)
-for the supported commands. No additional lookup call, provider selection, or
-approval step is required for a same-session follow-up.
+CLI application workflows continue to read portable inline Evidence from files
+and run the same analysis workflows; a standalone CLI invocation cannot resolve
+another MCP connection's retained records. No additional lookup call, provider
+selection, or approval step is required for a same-session follow-up.
 CLI `inspect-artifact` continues to return complete portable Evidence. Save that
 JSON to a file and use `inspect-analysis-view` with inline source Evidence for
 later inventory summaries or pages; a one-shot CLI session cannot retain a
@@ -864,27 +692,13 @@ requirements. Compare the union of group names with `tools/list` when checking
 that a client received the full catalog. An operation absent from all groups is
 missing from the complete inventory; it is not an implicit unavailable entry.
 
-Availability also reflects the active provider client's dispatched requests. A
-refusal or provider failure observed for an operation keeps that operation
-unavailable until a request for it dispatched later succeeds. A provider adapter
-or process failure also marks that provider's other declared-available
-operations unavailable until any request to that provider dispatched later
-succeeds; their remediation states that the status was inferred rather than
-observed for them. Recovery is not proof that each operation works, and failures
-observed on other operations or providers remain. Outcomes are ordered by
-dispatch to the provider client rather than reply completion, so a late reply
-from an older request does not override a newer outcome. Request deadlines and
-cancellations neither mark nor clear availability. A new provider client starts
-without these outcomes.
-
 `detail` selects the projection and the result echoes it. The default
 `summary` keeps open state, target identity, the binding, current-route
 `capabilities`, run, activity and health status, and each provider candidate's
 identity, selection, and availability and target-support `status`, `code`, and
-`reason`. It lists the fields it leaves out in `omitted_fields`: an unavailable
-candidate's `remediation`, provider `diagnostics`, candidate `capabilities`, and
-each tool group's static `surface`, `effects`, and `annotations`. Omitted fields
-are not empty or false.
+`reason`. It lists the fields it leaves out in `omitted_fields`: provider
+`diagnostics`, candidate `capabilities`, and each tool group's static `surface`,
+`effects`, and `annotations`. Omitted fields are not empty or false.
 `detail: "complete"` returns them inline, groups tools by those flags too, and
 has no `omitted_fields`. The output schema keys each result's candidate,
 tool-group and omission fields by its `detail`. CLI `capabilities` and
@@ -901,13 +715,6 @@ finish without reading relationships, even when neither traversal mode is
 available. Discovery does not block that direct invocation or replace its typed
 partial/error outcomes.
 
-`trace_native_ui_action` reports authored-UI and native-seed modes separately.
-Apple dispatch metadata requires a Mach-O target; another provider may supply
-the symbol-only alternative on other formats. If neither mode is available,
-read each mode's missing operations and remediation: a remedy for an authored
-app-bundle route does not by itself describe the native-seed route. Availability
-does not guarantee that every selector or provider operation will succeed.
-
 With complete detail, the `effects` and `annotations` arrays list the true
 members of their fixed vocabularies. A known member omitted from either array is false. This applies
 only to these closed flag sets; it does not make an omitted tool, provider, mode,
@@ -937,9 +744,7 @@ set, `shared_limitations` is the ordered common prefix; append a group's ordered
 `effects` arrays use the same true-only closed-vocabulary rule as tool
 availability. Expand every group operation while retaining its provider
 identity, availability, reason, rejection code, effects, and ordered
-limitations. An unavailable group carries `remediation` when its readiness
-owner supplied a repair instruction; `tool_availability` uses that instruction
-rather than the failure description.
+limitations.
 
 `binary_session.analysis_provider_candidates` is authoritative for deep-engine
 discovery. Each candidate's capability sets, returned with complete detail,
@@ -1014,14 +819,6 @@ is `unavailable` with a reason when ownership could not be revalidated, or
 at that bounded check. These are historical snapshots, not live process
 inventories, and do not claim that no short-lived descendant existed.
 
-After a failed close retires the target, `binary_session.cleanup_retry` names
-`close_binary` only while that session still retains the cleanup bound to the
-close error. Target-dependent availability then gives the same conditional
-cleanup guidance before suggesting `open_binary`. The hint disappears after
-cleanup succeeds. A pending flag alone does not establish this retry: active
-targets, an in-flight initial close, and external-mutation blockers keep their
-own recovery and do not receive this hint.
-
 `binary_session.cleanup_pending` reports whether the session retains a provider
 client, session file resource, or provider-candidate resource whose cleanup
 has not succeeded. It can be true with
@@ -1037,20 +834,6 @@ inspection fails or is cancelled before a provider client exists. If no client
 remains, no provider run or health observation is available; follow the cleanup
 error's reported resources.
 
-### Retained cleanup retry
-
-A `close_binary` that retires the target clears engine replay state while
-retaining investigation Evidence and Unknown history, including when cleanup fails. When the session keeps every reported owner for the next
-`close_binary` on the same connection, its `cleanup_incomplete` error carries
-`recovery: {"kind": "retry_cleanup", "operation": "close_binary"}`.
-Keep the connection open, let the reported condition settle or resolve it, call
-`close_binary` without `snapshot_path`, and check the result. The retry does not
-rerun the failed analysis and can report `cleanup_incomplete` again.
-`retryable` still describes the failed operation and stays `false`. A failed
-`snapshot_path` save returns before retirement, keeps the target open and has
-no `retry_cleanup` hint. `open_binary`, analysis tools and one-shot CLI commands
-do not report this hint either, even when their cleanup remains pending.
-
 ## Initial target at startup
 
 MCP normally starts without a target; use `open_binary` to select one during the
@@ -1311,15 +1094,6 @@ mapping. A successful start-address mapping does not establish that an entire
 range is contiguous in the original file, or that its bytes equal analysis
 memory after loader fixups. Uninitialized, missing, and ambiguous mappings fail
 explicitly; preserve the reported failure rather than guessing an offset.
-For Ghidra, such a well-formed address returns `invalid_request` whose message
-states the bridge's reason and whose remediation points to
-`inspect_native_load_image`. It carries no `inspect_input_contract` recovery.
-`details.issues[0].observed` keeps the caller's exact `address` and a
-`file_mapping` outcome: `unmapped` (outside every memory block),
-`uninitialized`, `absent` (no authoritative target-file source), `ambiguous`,
-or `unrepresentable` (beyond the exact JSON integer range). Initialization, not
-the loaded flag, decides whether source bytes can exist, so an initialized
-file-backed overlay still maps.
 
 For constructor-populated pointer or resource slots, a static zero is not proof
 of a later null value. Inspect the slot's `xrefs` and the writer's assembly or
@@ -1442,11 +1216,11 @@ If the client timed out or cancelled during startup, the pending query may have
 been interrupted. Reissuing `open_binary` for the same active target can reuse
 the current client, so it is not a fresh-start recovery. On the same connection:
 
-1. Keep useful inline Evidence or use the retained investigation references;
-   export a bundle before ending the process to resume later. `binary_session` can show the selected binding and its
+1. Keep any useful inline Evidence, or export a bundle before closing if retained
+   records are needed. `binary_session` can show the selected binding and its
    recorded state; target selection alone does not prove engine readiness.
 2. Call `close_binary` and check its result. It drains owned work, closes the
-   provider and engine replay state while preserving investigation Evidence and Unknown history. A `cleanup_incomplete` result
+   provider, and clears retained session records. A `cleanup_incomplete` result
    must be addressed according to its reported owned resources before retrying.
 3. Call `open_binary` with the same caller-selected path and
    `provider_id: "ghidra"`, then retry the first query with an appropriate client
@@ -1497,9 +1271,7 @@ cursor outside a procedure is represented as
 procedure resolution returns typed unreadable output; provider errors never
 become absence from their message text. `inspect_address_context` requires an explicit address and
 returns name, procedure, comment, inline-comment, and bookmark facets;
-unsupported facets are local `unavailable` outcomes. A facet whose input is
-rejected includes its canonical `error` projection, including any structured
-issues, alongside the other facet outcomes. Use `current_document`,
+unsupported facets are local `unavailable` outcomes. Use `current_document`,
 `current_address`, and `current_procedure` for direct single-field lookups; use
 the aggregate tools when you need related context together.
 
@@ -1545,20 +1317,12 @@ bytes and returns the `integrity_contradictions` records for the extracted
 files. An active ASAR unpacked entry whose companion file is absent cannot be
 materialized; extraction fails as `unavailable` with that logical path.
 
-A container can also declare a checksum over its own bytes; today that is the
-DFU suffix CRC of a DfuSe file. A mismatch is a contradiction of the root
-occurrence (logical path `.`), recorded as a `dfu-crc32` pair. Under
-`record-and-continue` the root becomes `mismatched` while its elements stay
-listed and extractable as observed-untrusted bytes, and `extract_artifact`
-returns the root record with the extracted files' records.
-
 If native DMG child traversal is unavailable after carrier identification,
 the typed failure retains a revalidated root-only inventory under
 `details.partial_observation.inventory`, with unknown child coverage and the
 producer's diagnostics/provenance. It does not borrow or detach an existing
 attachment. Native checksum verification failures still refuse traversal;
-`record-and-continue` recovery applies to structured entry and container
-contradictions.
+`record-and-continue` recovery applies to structured entry contradictions.
 
 Occurrences use normalized logical paths for identity and lookup. Optional
 `source_path` retains the original path within the owning reader when Unicode

docs/mcp-prompts.md

@@ -24,25 +24,13 @@ CLI equivalent is `rea guidance --query "exact JavaScript module"`, followed
 by `rea guidance --action read --locator LOCATOR`. Search is limited to the
 packaged managed skill files, works without providers or a target, and returns
 deterministically paged matches. Every non-generic query word must occur in the
-section or its subsections; generic-only queries return no matches. Results are documentation; locators
+section; generic-only queries return no matches. Results are documentation; locators
 are bound to the installed bundle and report stale or unavailable guidance without
 returning cached section content. A no-match result says nothing about analysis
 capability availability.
 
-Each match reports its `match_scope`. A `section` match has every term in its
-own text, meaning its heading and body before its first subsection. A
-`subsections` match has the terms only spread across subsections, with no
-single subsection holding them all. Its `own_text_terms` lists the terms in its
-own text, and `subsections` lists up to 8 subsection locators, chosen greedily,
-whose own text holds the rest; `omitted_subsections` counts any more that were
-needed. Section matches rank first. A parent is not listed when one subsection
-holds every term, because that subsection is already a match, unless the
-parent's own text also holds them all. `content_length`
-is the size of the section that read returns, so callers can decide before
-reading a broad parent.
-
 Search returns at most 20 matches per page with 500-code-unit context excerpts.
-Read retrieves the complete selected section, including its subsections. Admission permits 1 MiB per file,
+Read retrieves the complete selected section. Admission permits 1 MiB per file,
 4 MiB per bundle, 4,096 sections, and 25,165,824 expanded UTF-16 code units before
 section text is materialized. Unreadable or oversized bundles return
 `bundle_unavailable`, with no partial index or inferred absence. Cleanup failures

docs/native-investigation.md

@@ -68,10 +68,7 @@ function renamed to `dead` remains selectable by name. Use the names returned
 by the inventory, including their namespaces and any platform symbol prefix.
 Ghidra also accepts secondary symbols at a function entry, such as an imported
 `_main` label. A label inside a function is not a procedure-name selector; use
-its address when selecting the containing function. `search_procedures` matches
-the same names, in leaf or qualified spelling: the function appears once with
-its primary name as `value`, and `matched_aliases` lists the qualified names of
-the secondary symbols that matched.
+its address when selecting the containing function.
 Overloads can share a fully qualified name; ambiguity errors return every
 matching entry address so the caller can select the intended function directly.
 
@@ -188,24 +185,12 @@ observed entry label. An interior address therefore remains visible without
 being mistaken for the function entry. Identity failures are reported as
 `procedure.status: "unknown"`; label failures leave a null name and `name_error`.
 Neither failure discards usable pseudocode, and names are not parsed from it.
-A provider answer without pseudocode is an error item that keeps that
-observation's own `limitations`, so a reason the provider reported for that
-entry, such as a Kuna export failure or a missing body, stays with the item.
-Null pseudocode is `capability_unavailable`; empty or non-text pseudocode is
-`unreadable_output`. Provider failures keep their typed error. Successful items
-do not repeat limitations; the batch Evidence aggregates every observation's
-limitations by provider and operation.
 Resolved entries also appear in the composed Evidence locations. New batch
 Evidence commits the revised workflow profile; retained historical Evidence
 remains valid. This tool
 has no dedicated CLI command; the existing `decompile` command remains the
 single-procedure CLI operation.
 
-`detail: "summary"` retains the complete batch and returns only its counts,
-identities and sizes. `inspect_analysis_view` then reads rows or one body from
-the retained record, an Evidence file or a portable bundle without repeating
-decompilation: see [selected batch results](mcp-contracts.md#selected-batch-decompile-results).
-
 Each batch schedules one provider read at a time, but has no shared input-count
 or aggregate retained-output allowance. It retains every requested row and full
 pseudocode body through Evidence construction. The MCP response budget checks
@@ -300,20 +285,6 @@ relationships but reports their completeness as unknown. In particular, a resolv
 tail call observed in one direction does not prove that the reverse inventory is
 complete. An empty Hopper inventory cannot establish that no such call exists.
 No whole-binary reverse scan is performed.
-
-For large native traces, `trace_feature` accepts `detail: "summary"`. It retains
-the complete trace and returns counts and its parent Evidence ID. Use
-`inspect_analysis_view` with that ID and `view: {kind: "native-feature-trace",
-collection: "references", offset: 0, limit: 64}` to page the original rows;
-`matches` and `unknowns` are separate collections. Matches accept an exact
-`address`; references accept exact `source_address` and `target_address`
-filters. Row indices refer to the retained collection, and page coverage does not establish provider discovery
-completeness. `list_unknowns` pages the independently managed question heads.
-In the one-shot CLI, `rea trace ... --detail summary --evidence_output PATH`
-stores the trace and its linked source Evidence for later
-`inspect-analysis-view` calls. This bundle does not include the CLI session's
-Unknown registry; its original question texts remain available in the trace's
-`unknowns` pages.
 Regex searches use ECMAScript Unicode syntax in a cancellable worker with a
 matching deadline and a worker old-generation heap. Deadline or cancellation
 stops matching while leaving the Hopper API available. The deadline is
@@ -402,11 +373,6 @@ sites remain distinct. A static route does not establish runtime reachability.
 Swift/closure dispatch requires resolved static references; unavailable ABI
 forms remain unknown.
 
-Encoded Objective-C method records retain their own locations in dispatch
-Evidence. A handler node uses the implementation address with an unknown file
-offset unless that function already has an independently located graph node;
-the method-record offset does not locate the handler's code.
-
 Incomplete reference kinds do not discard known typed calls or partial
 provider call references. A `provider_call` with `observed` resolution retains
 the provider-reported call site and endpoint without claiming generic direct,
@@ -452,31 +418,10 @@ Within one value trace, each exact procedure selector is attempted at most once,
 including failed analyses. A failed seed returns the provider's original typed
 failure and corrective guidance; it cannot establish a trace or target identity.
 Failures while expanding a validated seed remain unknown observations and do not
-establish canonical function identity. A cancelled expansion read returns the
-cancellation. An expansion read whose provider cannot confirm cleanup of
-resources it owns stops the trace: the result is that provider's own
-`cleanup_incomplete` failure with its resources and any bound cleanup retry, and the work
-admitted before the stop is retained as partial Evidence with a located unknown
-at the stopping read. A successful seed without a native def-use
+establish canonical function identity. A successful seed without a native def-use
 model still returns its procedure and an explicit coverage unknown. A new trace
 can retry failed selectors.
 
-Paging and traversal completeness are separate facts. `page_truncated` means the
-page omits retained nodes, and the edges they source, before `offset` or after
-`next_offset`. Every page repeats `traversal`: `complete`, or `truncated` with
-`reasons` naming each observed cause: the `max_depth`, `max_functions`,
-`max_call_sites`, `max_nodes` or `max_edges` budget, the fixed
-`node_payload_bytes` allowance, `provider_pcode_truncated`,
-`ambiguous_call_candidates`, or, only in a stopped trace's partial Evidence,
-`cleanup_incomplete`. Each cause also has a located unknown. A budget is
-reported only after it rejects work, so an exactly filled budget is not
-truncation; a depth or candidate limit is reported only when no other path
-analyzes or queues that destination. `total_nodes` and `total_edges` count
-retained rows. `truncated` remains true for either kind of omission. Failed
-analyses and unresolved calls stay in `unknowns` and do not truncate the
-traversal. Each page reruns analysis; pages are not pinned to one snapshot
-across session edits.
-
 The raw Java `is_dead` flag can remain set after Ghidra decodes a live block;
 `block_membership` reports actual syntax-tree membership separately.
 
@@ -1023,9 +968,7 @@ with a path-specific gap and incomplete capture coverage. Null alone does not
 establish that an accessibility value was successfully read or absent.
 
 An initial PID or window mismatch is `invalid_request` on `pid` or
-`window_id` and leaves provider availability intact. A selected window that
-exists off screen is not a mismatch: selection succeeds and the permission and
-capture checks report their own outcome. An unavailable executable
+`window_id` and leaves provider availability intact. An unavailable executable
 URL or unresolved executable path leaves identity unknown and reports
 `capability_unavailable`. Identity or window loss
 after the initial capture remains an observation failure with collected facts.
@@ -1174,55 +1117,11 @@ unpaired Unicode surrogate; a rejection identifies the field and UTF-16 index
 and leaves every annotation unchanged. CRLF, supplementary Unicode characters,
 and combining characters are preserved. Windows P0 remains read-only. Ghidra has no
 GUI authority, and REA never falls back automatically to Hopper.
-For a before-and-after `compare_functions` in MCP, call `analyze_function`
-before and after the edit while the session remains open; the annotation Evidence
-itself is not an `analyze_function` input. If comparing after close, export the
-needed Evidence before closing and import it into the later session. A one-shot
-CLI annotation returns its edited dossier before its temporary session is
-discarded; a later CLI invocation with the same fresh-import settings starts from
-the original executable. Comparison preserves correspondence across renames
-when authenticated artifact identity, architecture and provider-owned mapping
-and slice commitments establish the same canonical entry. The result reports
-`matched`, `method: "same-entry"` and `entry_address`; name and exact-text changes
-remain separate dimensions. Equal numeric addresses without applicable coordinate
-commitments do not establish same-entry correspondence. Inspect the retained
-source Evidence and coverage when correspondence remains ambiguous.
-To aggregate already-retained comparison results, pass their exact IDs to
-`find_changed_behavior`, for example:
-
-```javascript
-await call("find_changed_behavior", {
-  comparisons: comparisons.map(({ evidence_id }) => ({
-    kind: "retained-evidence",
-    evidence_id,
-  })),
-});
-```
-
-These IDs select comparison Evidence, not function dossiers or summary views.
-Complete inline comparisons remain accepted and can be mixed with references.
-The current server must retain the comparisons and their original source closure;
-import the complete source bundle after a session handoff. Missing or damaged
-records are explicit failures. A missing required retained record reports its exact
-`evidence_id` with `details.reference_scope: "retained-closure"`. Import the
-originating bundle with its linked sources, or re-create those observations in the
-current investigation, before retrying; resending the inline comparison alone
-does not restore its closure. Aggregating static differences does not establish
-observed runtime change.
-
 `set_address_name` and `set_addresses_names` give Ghidra sessions the same
 compact naming results as Hopper: a local function entry renames that function,
 and any other mapped address, such as a global, receives a new or renamed primary
-label. A batch decides every address from the names held before it: addresses
-that request the same name in one namespace, or a name another selected address
-holds, are rejected without applying them, so JSON member order never selects a
-winner. Every other address applies separately, and each address reports one
-success boolean. `raw_result.failures` gives each failed address's canonical
-address and reason. A contested name appears once in `raw_result.conflicts`,
-with its namespace, requesting addresses and holding addresses, and conflict
-failures refer to it by index. To move a label between
-addresses, rename its holder first and assign the name in a later call. Use
-them to name many globals and helpers cheaply; use
+label. A batch applies each address separately and reports one success boolean
+per address. Use them to name many globals and helpers cheaply; use
 `annotate_native_function` when you also want comments and a refreshed dossier.
 Ghidra name edits preserve the existing namespace. Supply either a leaf name
 such as `renamed` or a fully qualified name in that namespace, such as

docs/process-capture.md

@@ -652,33 +652,6 @@ 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.
 
-With the default `xcrun` compiler and module cache, REA also keeps one verified
-copy of the compiled helper in `~/Library/Caches/rea/process-helper/`, so later
-REA processes skip both the compile and macOS's first-launch assessment of a
-new executable. Each entry is keyed by the helper source, the `swiftc` and SDK
-that `xcrun --find swiftc` and `xcrun --show-sdk-path` resolve (their real
-paths, sizes and modification times, so `DEVELOPER_DIR`, `TOOLCHAINS`,
-`xcode-select` and in-place toolchain updates all select a new entry), the CPU
-architecture and the Darwin release. Before running an entry, REA requires the
-cache directory, the entry and its files to be owned by the current user and
-not writable by group or others, every real parent directory to be owned by
-the current user or root and not writable by others (sticky root-owned
-directories excepted), no ACL on any of them to allow another principal a
-write-class right (the default `deny delete` entries are fine), the helper and
-manifest to be regular files rather than
-links or FIFOs, and the helper's SHA-256 to match the manifest. Anything else is
-never executed and never removed, because another REA process may still be
-verifying or running that path; REA then compiles a per-process helper as
-before. A published entry is never replaced. If the cache is unavailable, for
-example under a read-only home directory, the ownership operation proceeds
-with the per-process compile. These checks reject corruption, loosened
-permissions and other users, but they do not defend against another process
-running as the same user, which could already modify REA itself. Setting
-`REA_DARWIN_SWIFTC_PATH` or `REA_DARWIN_MODULE_CACHE_PATH` keeps the per-process
-compile and writes nothing to this cache. REA does not prune old entries; each
-is about 240 KiB. Delete the directory while no REA process is running, or run
-`rea uninstall --purge-data`, to remove them.
-
 `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

docs/readme/README_ar.md

@@ -20,8 +20,6 @@
 
 **[الموقع](https://rea.tools/ar/) · [الأدلة](https://rea.tools/ar/guides/) · [دراسات الحالة](https://rea.tools/ar/showcase/)**
 
-<a href="https://discord.com/invite/GkcryMnJDM"><img alt="انضم إلى مجتمع REA على Discord" src="https://img.shields.io/badge/Join%20us%20on%20Discord-5865F2?style=for-the-badge&logo=discord&logoColor=white" height="40"></a>
-
 [البدء السريع](#البدء-السريع) · [كيف يعمل REA](#كيف-يعمل-rea) · [ما الذي يمكنك تحليله](#ما-الذي-يمكنك-تحليله) · [دراسات الحالة](#دراسات-الحالة) · [إنشاء بيئات التعلم المعزز](#build-rl-environments) · [الأسئلة الشائعة](#الأسئلة-الشائعة) · [أدوات GNU objdump وRizin](../reverse-engineering-tools.md) · [التوثيق](#التوثيق)
 
 <code>npx rea-agents setup</code>

docs/readme/README_de.md

@@ -20,8 +20,6 @@
 
 **[Website](https://rea.tools/de/) · [Anleitungen](https://rea.tools/de/guides/) · [Fallstudien](https://rea.tools/de/showcase/)**
 
-<a href="https://discord.com/invite/GkcryMnJDM"><img alt="Der REA-Community auf Discord beitreten" src="https://img.shields.io/badge/Join%20us%20on%20Discord-5865F2?style=for-the-badge&logo=discord&logoColor=white" height="40"></a>
-
 [Schnellstart](#schnellstart) · [So funktioniert REA](#so-funktioniert-rea) · [Was du analysieren kannst](#was-du-analysieren-kannst) · [Fallstudien](#fallstudien) · [RL-Umgebungen erstellen](#build-rl-environments) · [Häufige Fragen](#häufige-fragen) · [Dokumentation](#dokumentation)
 
 <code>npx rea-agents setup</code>

docs/readme/README_el.md

@@ -19,8 +19,6 @@
 
 **[Ιστότοπος](https://rea.tools/) · [Οδηγοί](https://rea.tools/guides/) · [Μελέτες περίπτωσης](https://rea.tools/showcase/)**
 
-<a href="https://discord.com/invite/GkcryMnJDM"><img alt="Έλα στην κοινότητα REA στο Discord" src="https://img.shields.io/badge/Join%20us%20on%20Discord-5865F2?style=for-the-badge&logo=discord&logoColor=white" height="40"></a>
-
 [Γρήγορη εκκίνηση](#γρήγορη-εκκίνηση) · [Πώς λειτουργεί το REA](#πώς-λειτουργεί-το-rea) · [Τι μπορείς να αναλύσεις](#τι-μπορείς-να-αναλύσεις) · [Μελέτες περίπτωσης](#μελέτες-περίπτωσης) · [Δημιουργία περιβαλλόντων RL](#build-rl-environments) · [Συχνές ερωτήσεις](#συχνές-ερωτήσεις) · [Τεκμηρίωση](#τεκμηρίωση)
 
 <code>npx rea-agents setup</code>

docs/readme/README_es.md

@@ -20,8 +20,6 @@
 
 **[Sitio web](https://rea.tools/es/) · [Guías](https://rea.tools/es/guides/) · [Casos prácticos](https://rea.tools/es/showcase/)**
 
-<a href="https://discord.com/invite/GkcryMnJDM"><img alt="Únete a la comunidad de REA en Discord" src="https://img.shields.io/badge/Join%20us%20on%20Discord-5865F2?style=for-the-badge&logo=discord&logoColor=white" height="40"></a>
-
 [Inicio rápido](#inicio-rápido) · [Cómo funciona REA](#cómo-funciona-rea) · [Qué puedes analizar](#qué-puedes-analizar) · [Casos prácticos](#casos-prácticos) · [Crear entornos de RL](#build-rl-environments) · [Preguntas frecuentes](#preguntas-frecuentes) · [Documentación](#documentación)
 
 <code>npx rea-agents setup</code>

docs/readme/README_fa.md

@@ -20,8 +20,6 @@
 
 **[وب‌سایت](https://rea.tools/fa/) · [راهنماها](https://rea.tools/fa/guides/) · [نمونه‌های عملی](https://rea.tools/fa/showcase/)**
 
-<a href="https://discord.com/invite/GkcryMnJDM"><img alt="به انجمن REA در دیسکورد بپیوندید" src="https://img.shields.io/badge/Join%20us%20on%20Discord-5865F2?style=for-the-badge&logo=discord&logoColor=white" height="40"></a>
-
 [شروع سریع](#شروع-سریع) · [REA چگونه کار می‌کند؟](#rea-چگونه-کار-می‌کند) · [چه چیزهایی را میتوان تحلیل کرد؟](#چه-چیزهایی-را-می‌توان-تحلیل-کرد) · [نمونه‌های عملی](#نمونه‌های-عملی) · [ساخت محیط‌های RL](#build-rl-environments) · [پرسش‌های متداول](#پرسش‌های-متداول) · [مستندات](#مستندات)
 
 <code>npx rea-agents setup</code>

docs/readme/README_fr.md

@@ -20,8 +20,6 @@
 
 **[Site web](https://rea.tools/fr/) · [Guides](https://rea.tools/fr/guides/) · [Études de cas](https://rea.tools/fr/showcase/)**
 
-<a href="https://discord.com/invite/GkcryMnJDM"><img alt="Rejoignez la communauté REA sur Discord" src="https://img.shields.io/badge/Join%20us%20on%20Discord-5865F2?style=for-the-badge&logo=discord&logoColor=white" height="40"></a>
-
 [Démarrage rapide](#démarrage-rapide) · [Comment fonctionne REA](#comment-fonctionne-rea) · [Ce que vous pouvez analyser](#ce-que-vous-pouvez-analyser) · [Études de cas](#études-de-cas) · [Créer des environnements RL](#build-rl-environments) · [Questions fréquentes](#questions-fréquentes) · [Documentation](#documentation)
 
 <code>npx rea-agents setup</code>

docs/readme/README_id.md

@@ -20,8 +20,6 @@
 
 **[Situs Web](https://rea.tools/id/) · [Panduan](https://rea.tools/id/guides/) · [Contoh Penggunaan](https://rea.tools/id/showcase/)**
 
-<a href="https://discord.com/invite/GkcryMnJDM"><img alt="Bergabunglah dengan komunitas REA di Discord" src="https://img.shields.io/badge/Join%20us%20on%20Discord-5865F2?style=for-the-badge&logo=discord&logoColor=white" height="40"></a>
-
 [Mulai Cepat](#mulai-cepat) · [Cara Kerja REA](#cara-kerja-rea) · [Hal yang Dapat Anda Analisis](#hal-yang-dapat-anda-analisis) · [Contoh Penggunaan](#contoh-penggunaan) · [Membangun lingkungan RL](#build-rl-environments) · [FAQ](#faq) · [Dokumentasi](#dokumentasi)
 
 <code>npx rea-agents setup</code>

docs/readme/README_it.md

@@ -20,8 +20,6 @@
 
 **[Sito web](https://rea.tools/it/) · [Guide](https://rea.tools/it/guides/) · [Showcase](https://rea.tools/it/showcase/)**
 
-<a href="https://discord.com/invite/GkcryMnJDM"><img alt="Unisciti alla community REA su Discord" src="https://img.shields.io/badge/Join%20us%20on%20Discord-5865F2?style=for-the-badge&logo=discord&logoColor=white" height="40"></a>
-
 [Avvio rapido](#avvio-rapido) · [Come funziona REA](#come-funziona-rea) · [Cosa puoi analizzare](#cosa-puoi-analizzare) · [Showcase](#showcase) · [Creare ambienti RL](#build-rl-environments) · [FAQ](#faq) · [Documentazione](#documentazione)
 
 <code>npx rea-agents setup</code>

docs/readme/README_ja.md

@@ -20,8 +20,6 @@
 
 **[ウェブサイト](https://rea.tools/ja/) · [ガイド](https://rea.tools/ja/guides/) · [事例](https://rea.tools/ja/showcase/)**
 
-<a href="https://discord.com/invite/GkcryMnJDM"><img alt="DiscordのREAコミュニティに参加" src="https://img.shields.io/badge/Join%20us%20on%20Discord-5865F2?style=for-the-badge&logo=discord&logoColor=white" height="40"></a>
-
 [クイックスタート](#クイックスタート) · [REA の仕組み](#rea-の仕組み) · [分析できる対象](#分析できる対象) · [事例](#事例) · [RL 環境を構築する](#build-rl-environments) · [よくある質問](#よくある質問) · [ドキュメント](#ドキュメント)
 
 <code>npx rea-agents setup</code>

docs/readme/README_ko.md

@@ -20,8 +20,6 @@
 
 **[웹사이트](https://rea.tools/ko/) · [가이드](https://rea.tools/ko/guides/) · [사례](https://rea.tools/ko/showcase/)**
 
-<a href="https://discord.com/invite/GkcryMnJDM"><img alt="Discord에서 REA 커뮤니티에 참여하세요" src="https://img.shields.io/badge/Join%20us%20on%20Discord-5865F2?style=for-the-badge&logo=discord&logoColor=white" height="40"></a>
-
 [빠른 시작](#빠른-시작) · [REA의 작동 방식](#rea의-작동-방식) · [분석할 수 있는 대상](#분석할-수-있는-대상) · [사례](#사례) · [RL 환경 만들기](#build-rl-environments) · [자주 묻는 질문](#자주-묻는-질문) · [문서](#문서)
 
 <code>npx rea-agents setup</code>

docs/readme/README_ml.md

@@ -20,8 +20,6 @@
 
 **[വെബ്സൈറ്റ്](https://rea.tools/) · [ഗൈഡുകൾ](https://rea.tools/guides/) · [ഉദാഹരണങ്ങൾ](https://rea.tools/showcase/)**
 
-<a href="https://discord.com/invite/GkcryMnJDM"><img alt="Discord-ൽ REA കമ്മ്യൂണിറ്റിയിൽ ചേരുക" src="https://img.shields.io/badge/Join%20us%20on%20Discord-5865F2?style=for-the-badge&logo=discord&logoColor=white" height="40"></a>
-
 [ദ്രുതാരംഭം](#ദ്രുതാരംഭം) · [REA എങ്ങനെ പ്രവർത്തിക്കുന്നു](#rea-എങ്ങനെ-പ്രവർത്തിക്കുന്നു) · [എന്തൊക്കെ വിശകലനം ചെയ്യാം](#എന്തൊക്കെ-വിശകലനം-ചെയ്യാം) · [ഉദാഹരണങ്ങൾ](#ഉദാഹരണങ്ങൾ) · [RL പരിതസ്ഥിതികൾ നിർമ്മിക്കുക](#build-rl-environments) · [പതിവുചോദ്യങ്ങൾ](#പതിവുചോദ്യങ്ങൾ) · [ഡോക്യുമെന്റേഷൻ](#ഡോക്യുമെന്റേഷൻ)
 
 <code>npx rea-agents setup</code>

docs/readme/README_pl.md

@@ -20,8 +20,6 @@
 
 **[Strona internetowa](https://rea.tools/pl/) · [Przewodniki](https://rea.tools/pl/guides/) · [Przykłady zastosowań](https://rea.tools/pl/showcase/)**
 
-<a href="https://discord.com/invite/GkcryMnJDM"><img alt="Dołącz do społeczności REA na Discordzie" src="https://img.shields.io/badge/Join%20us%20on%20Discord-5865F2?style=for-the-badge&logo=discord&logoColor=white" height="40"></a>
-
 [Szybki start](#szybki-start) · [Jak działa REA](#jak-działa-rea) · [Co możesz analizować](#co-możesz-analizować) · [Przykłady zastosowań](#przykłady-zastosowań) · [Tworzenie środowisk RL](#build-rl-environments) · [FAQ](#faq) · [Dokumentacja](#dokumentacja)
 
 <code>npx rea-agents setup</code>

docs/readme/README_pt-BR.md

@@ -20,8 +20,6 @@
 
 **[Site](https://rea.tools/pt-BR/) · [Guias](https://rea.tools/pt-BR/guides/) · [Casos de uso](https://rea.tools/pt-BR/showcase/)**
 
-<a href="https://discord.com/invite/GkcryMnJDM"><img alt="Participe da comunidade REA no Discord" src="https://img.shields.io/badge/Join%20us%20on%20Discord-5865F2?style=for-the-badge&logo=discord&logoColor=white" height="40"></a>
-
 [Início rápido](#início-rápido) · [Como o REA funciona](#como-o-rea-funciona) · [O que você pode analisar](#o-que-você-pode-analisar) · [Casos de uso](#casos-de-uso) · [Criar ambientes de RL](#build-rl-environments) · [Perguntas frequentes](#perguntas-frequentes) · [Documentação](#documentação)
 
 <code>npx rea-agents setup</code>

docs/readme/README_ro.md

@@ -20,8 +20,6 @@
 
 **[Site web](https://rea.tools/) · [Ghiduri](https://rea.tools/guides/) · [Studii de caz](https://rea.tools/showcase/)**
 
-<a href="https://discord.com/invite/GkcryMnJDM"><img alt="Alătură-te comunității REA pe Discord" src="https://img.shields.io/badge/Join%20us%20on%20Discord-5865F2?style=for-the-badge&logo=discord&logoColor=white" height="40"></a>
-
 [Pornire rapidă](#pornire-rapidă) · [Cum funcționează REA](#cum-funcționează-rea) · [Ce poți analiza](#ce-poți-analiza) · [Studii de caz](#studii-de-caz) · [Construiește medii RL](#build-rl-environments) · [Întrebări frecvente](#întrebări-frecvente) · [Documentație](#documentație)
 
 <code>npx rea-agents setup</code>

docs/readme/README_ru.md

@@ -20,8 +20,6 @@
 
 **[Сайт](https://rea.tools/ru/) · [Руководства](https://rea.tools/ru/guides/) · [Примеры](https://rea.tools/ru/showcase/)**
 
-<a href="https://discord.com/invite/GkcryMnJDM"><img alt="Присоединяйтесь к сообществу REA в Discord" src="https://img.shields.io/badge/Join%20us%20on%20Discord-5865F2?style=for-the-badge&logo=discord&logoColor=white" height="40"></a>
-
 [Быстрый старт](#быстрый-старт) · [Как работает REA](#как-работает-rea) · [Что можно анализировать](#что-можно-анализировать) · [Примеры](#примеры) · [Создание RL-окружений](#build-rl-environments) · [Частые вопросы](#частые-вопросы) · [Документация](#документация)
 
 <code>npx rea-agents setup</code>

docs/readme/README_th.md

@@ -20,8 +20,6 @@
 
 **[เว็บไซต์](https://rea.tools/th/) · [คู่มือ](https://rea.tools/th/guides/) · [ตัวอย่างการใช้งาน](https://rea.tools/th/showcase/)**
 
-<a href="https://discord.com/invite/GkcryMnJDM"><img alt="เข้าร่วมชุมชน REA บน Discord" src="https://img.shields.io/badge/Join%20us%20on%20Discord-5865F2?style=for-the-badge&logo=discord&logoColor=white" height="40"></a>
-
 [เริ่มต้นอย่างรวดเร็ว](#เริ่มต้นอย่างรวดเร็ว) · [REA ทำงานอย่างไร](#rea-ทำงานอย่างไร) · [สิ่งที่วิเคราะห์ได้](#สิ่งที่วิเคราะห์ได้) · [ตัวอย่างการใช้งาน](#ตัวอย่างการใช้งาน) · [สร้างสภาพแวดล้อม RL](#build-rl-environments) · [คำถามที่พบบ่อย](#คำถามที่พบบ่อย) · [เอกสาร](#เอกสาร)
 
 <code>npx rea-agents setup</code>

docs/readme/README_tr.md

@@ -20,8 +20,6 @@
 
 **[Web sitesi](https://rea.tools/tr/) · [Rehberler](https://rea.tools/tr/guides/) · [Örnek çalışmalar](https://rea.tools/tr/showcase/)**
 
-<a href="https://discord.com/invite/GkcryMnJDM"><img alt="Discord'da REA topluluğuna katılın" src="https://img.shields.io/badge/Join%20us%20on%20Discord-5865F2?style=for-the-badge&logo=discord&logoColor=white" height="40"></a>
-
 [Hızlı başlangıç](#hızlı-başlangıç) · [REA nasıl çalışır](#rea-nasıl-çalışır) · [Neleri analiz edebilirsiniz](#neleri-analiz-edebilirsiniz) · [Örnek çalışmalar](#örnek-çalışmalar) · [RL ortamları oluşturun](#build-rl-environments) · [Sık sorulan sorular](#sık-sorulan-sorular) · [GNU objdump ve Rizin araçları](../reverse-engineering-tools.md) · [Belgeler](#belgeler)
 
 <code>npx rea-agents setup</code>

docs/readme/README_uk.md

@@ -20,8 +20,6 @@
 
 **[Сайт](https://rea.tools/uk/) · [Посібники](https://rea.tools/uk/guides/) · [Приклади](https://rea.tools/uk/showcase/)**
 
-<a href="https://discord.com/invite/GkcryMnJDM"><img alt="Приєднуйтеся до спільноти REA в Discord" src="https://img.shields.io/badge/Join%20us%20on%20Discord-5865F2?style=for-the-badge&logo=discord&logoColor=white" height="40"></a>
-
 [Швидкий старт](#швидкий-старт) · [Як працює REA](#як-працює-rea) · [Що можна аналізувати](#що-можна-аналізувати) · [Приклади](#приклади) · [Створення RL-середовищ](#build-rl-environments) · [Поширені запитання](#поширені-запитання) · [Документація](#документація)
 
 <code>npx rea-agents setup</code>

docs/readme/README_ur-Latn.md

@@ -20,8 +20,6 @@
 
 **[Website](https://rea.tools/) · [Guides](https://rea.tools/guides/) · [Showcases](https://rea.tools/showcase/)**
 
-<a href="https://discord.com/invite/GkcryMnJDM"><img alt="Discord par REA community mein shamil hon" src="https://img.shields.io/badge/Join%20us%20on%20Discord-5865F2?style=for-the-badge&logo=discord&logoColor=white" height="40"></a>
-
 [Jaldi shuru karein](#jaldi-shuru-karein) · [REA kaise kaam karta hai](#rea-kaise-kaam-karta-hai) · [Kya kuch analyze kar sakte hain](#kya-kuch-analyze-kar-sakte-hain) · [Amli misaalein](#amli-misaalein) · [RL environments banayein](#build-rl-environments) · [FAQ](#faq) · [Documentation](#documentation)
 
 <code>npx rea-agents setup</code>

docs/readme/README_vi.md

@@ -20,8 +20,6 @@
 
 **[Trang web](https://rea.tools/vi/) · [Hướng dẫn](https://rea.tools/vi/guides/) · [Các nghiên cứu điển hình](https://rea.tools/vi/showcase/)**
 
-<a href="https://discord.com/invite/GkcryMnJDM"><img alt="Tham gia cộng đồng REA trên Discord" src="https://img.shields.io/badge/Join%20us%20on%20Discord-5865F2?style=for-the-badge&logo=discord&logoColor=white" height="40"></a>
-
 [Bắt đầu nhanh](#bắt-đầu-nhanh) · [Cách REA hoạt động](#cách-rea-hoạt-động) · [Những gì bạn có thể phân tích](#những-gì-bạn-có-thể-phân-tích) · [Các nghiên cứu điển hình](#các-nghiên-cứu-điển-hình) · [Xây dựng môi trường RL](#build-rl-environments) · [Câu hỏi thường gặp](#câu-hỏi-thường-gặp) · [Tài liệu](#tài-liệu)
 
 <code>npx rea-agents setup</code>

docs/readme/README_zh-TW.md

@@ -20,8 +20,6 @@
 
 **[網站](https://rea.tools/zh-TW/) · [指南](https://rea.tools/zh-TW/guides/) · [案例](https://rea.tools/zh-TW/showcase/)**
 
-<a href="https://discord.com/invite/GkcryMnJDM"><img alt="加入 REA 的 Discord 社群" src="https://img.shields.io/badge/Join%20us%20on%20Discord-5865F2?style=for-the-badge&logo=discord&logoColor=white" height="40"></a>
-
 [快速開始](#快速開始) · [REA 的工作原理](#rea-的工作原理) · [可以分析什麼](#可以分析什麼) · [案例](#案例) · [建立 RL 環境](#build-rl-environments) · [常見問題](#常見問題) · [文件](#文件)
 
 <code>npx rea-agents setup</code>

docs/readme/README_zh.md

@@ -20,8 +20,6 @@
 
 **[网站](https://rea.tools/zh-CN/) · [指南](https://rea.tools/zh-CN/guides/) · [案例](https://rea.tools/zh-CN/showcase/)**
 
-<a href="https://discord.com/invite/GkcryMnJDM"><img alt="加入 REA 的 Discord 社区" src="https://img.shields.io/badge/Join%20us%20on%20Discord-5865F2?style=for-the-badge&logo=discord&logoColor=white" height="40"></a>
-
 [快速开始](#快速开始) · [REA 的工作原理](#rea-的工作原理) · [可以分析什么](#可以分析什么) · [案例](#案例) · [构建 RL 环境](#build-rl-environments) · [常见问题](#常见问题) · [GNU objdump 和 Rizin 工具](../reverse-engineering-tools.md) · [文档](#文档)
 
 <code>npx rea-agents setup</code>

docs/reverse-engineering-tools.md

@@ -14,13 +14,7 @@ can run.
 
 ## GNU objdump
 
-REA sends GNU-style arguments to the selected command but does not verify its
-implementation or version. Evidence identifies the command profile as
-`objdump.command` and retains the selected executable; it does not claim that
-the executable is GNU objdump. Other implementations may accept some commands
-while differing in supported options and output.
-
-`inspect_with_objdump` and `rea inspect-with-objdump` capture stdout and stderr as inline Evidence. Artifact inspection Evidence records SHA-256 digests before and after the provider call and whether those observed digests differ; this cannot prove the exact bytes consumed if the artifact changes during execution. Choose one artifact operation: `file_headers`, `section_headers`, `symbols`, `relocations`, `dwarf`, `disassemble`, or `disassemble_all`. `disassemble` maps to `-d`; `disassemble_all` maps to `-D` and has different symbol-boundary semantics. The pathless `inspect_with_objdump {"operation":"architectures"}` MCP call or `rea list-objdump-architectures` CLI command maps to `-i` and produces subjectless Evidence containing the selected command’s output, not a guarantee that any target is supported. GNU objdump uses this option to list its compiled-in BFD targets.
+`inspect_with_objdump` and `rea inspect-with-objdump` capture stdout and stderr as inline Evidence. Artifact inspection Evidence records SHA-256 digests before and after the provider call and whether those observed digests differ; this cannot prove the exact bytes consumed if the artifact changes during execution. Choose one artifact operation: `file_headers`, `section_headers`, `symbols`, `relocations`, `dwarf`, `disassemble`, or `disassemble_all`. `disassemble` maps to `-d`; `disassemble_all` maps to `-D` and has different symbol-boundary semantics. The pathless `inspect_with_objdump {"operation":"architectures"}` MCP call or `rea list-objdump-architectures` CLI command maps to `-i` and produces subjectless provider-capability Evidence describing BFD targets compiled into the installed binary, not a guarantee that a target is supported.
 
 Failure to launch the selected executable reports provider unavailability, the
 configured command and the host error under `boundary: "provider-launch"`.
@@ -31,7 +25,7 @@ their rejected fields in input issues before artifact reads or provider launch.
 
 For DWARF, REA does not follow local debug links by default. Set `follow_debug_links` to `true` to pass `-WK`; external debug-file identities are not bound to Evidence when following links is enabled. The CLI flag is `--follow-debug-links`; `--no-follow-debug-links` or `--follow-debug-links=false` keeps the default. A separate `true` or `false` word after the flag is not its value. REA clears `DEBUGINFOD_URLS` in the objdump child environment to disable debuginfod network access on GNU binutils versions that do not support `-WE`. The complete raw output is authoritative; REA does not normalize it into a version-independent disassembly schema.
 
-For a known native symbol, use `operation: "disassemble", symbol: "my_function"` in MCP or `--symbol my_function` in CLI. REA passes `--disassemble=my_function` to objdump before collecting output, rather than producing the whole disassembly and filtering it afterward. Omit `symbol` to keep full code-section disassembly. Other operations reject this selector. Use a nonempty, NUL-free name with well-formed Unicode; unsupported values are rejected before reading the artifact or starting objdump. Symbol names are passed unchanged; matching, versioned symbols, aliases and the end of the disassembly follow the selected executable's semantics. Evidence records the selector and actual arguments. An empty match does not establish artifact-wide absence, and the selected observation does not contain the omitted disassembly; request the complete operation when needed.
+For a known native symbol, use `operation: "disassemble", symbol: "my_function"` in MCP or `--symbol my_function` in CLI. REA passes `--disassemble=my_function` to objdump before collecting output, rather than producing the whole disassembly and filtering it afterward. Omit `symbol` to keep full code-section disassembly. Other operations reject this selector. Use a nonempty, NUL-free name with well-formed Unicode; unsupported values are rejected before reading the artifact or starting objdump. Symbol names are passed unchanged; matching, versioned symbols, aliases and the end of the disassembly follow the installed GNU objdump's semantics. Evidence records the selector and actual arguments. An empty match does not establish artifact-wide absence, and the selected observation does not contain the omitted disassembly; request the complete operation when needed.
 
 ```sh
 rea inspect-with-objdump ./program disassemble

docs/specs/agent-environments/fidelity-compare/spec.md

@@ -86,10 +86,7 @@ credentials and resets it between sequences.
   environment refused the call), `not-served`, `no-tool` and `unmapped-id`, each with a JSON pointer and short values.
 - The report gives agreement overall, per probe and per tool, agreement ignoring item order beside it, the counts per
   category, the ids mapped and the values normalised, the records left uncompared, and each step's differences (at most
-  20 per step). Each step gives `differences_total` before that cap, `differences_omitted`, and
-  `differences_truncated`, true when entries were omitted. Equality and categories use all differences.
-  Omitted entries are not retained and `--full-output` cannot recover them; further investigation uses the original
-  capture and probe Evidence.
+  20 per step).
 
 ## Non-goals
 

docs/tool-design.md

@@ -48,100 +48,6 @@ fixture servers. Custom orchestration languages, replay engines, or separate
 prepare/execute plans need an observed requirement those primitives cannot
 satisfy. A plan without execution does not establish runtime behavior.
 
-## Exercise the analyst workflow
-
-Before defining a new provider-backed tool, state the analyst's question, what
-they already have, the intended result and authority, and what must remain
-unknown. Try the nearest existing REA workflow and the relevant native provider
-or ordinary script path when available. Identify the specific gap and what a
-new or extended contract would add; upstream capability alone does not require
-a new tool or equal support from every provider.
-
-Exercise the task through REA as a whole and compare relevant provider behavior
-with an independent artifact or format observation where possible. Use the
-caller's selected target and authority. Record the provider version, target and
-observed coverage, and distinguish an unsupported operation from an empty
-result or an untested path.
-
-Include the boundary cases that could change the answer: provider labels versus
-source facts, addresses versus file locations, partial results, and a useful
-recovery after failure or session close when those apply to the task. Check that
-composed results keep each observation's identity, limitations and source
-association. Existing real-provider lanes and focused tests establish their
-selected scenarios; they do not by themselves establish a different workflow or
-provider equivalence. If a provider cannot be exercised, report that limitation
-and continue with the available evidence. Measure agent tool selection only with
-an actual agent evaluation; a scripted tool sequence does not establish it. Use
-[testing guidance](testing.md#provider-backed-workflow-verification) to select
-the cases that establish the proposed contract.
-
-## Audit existing tools
-
-Scope an audit by analyst tasks and the caller's target, providers and authority.
-Record the source revision and, when used, the running server, catalog and
-provider versions; a connected server can differ from the current checkout.
-Inspect the live CLI help or MCP descriptions and schemas alongside the owning
-contracts and documentation. Choose representative tasks and their nearest REA
-and native alternatives rather than counting upstream commands.
-
-Exercise the selected public workflows, including the steps before and after a
-tool call. Check task selection, input choices, returned facts and their source,
-partial or unsupported outcomes, and applicable session and recovery behavior.
-Compare native provider output and an independent artifact observation where
-available. Inspect existing tests and real-provider lanes for the scenario they
-actually cover; a passing test does not establish a different task or host.
-Use [workflow verification](testing.md#provider-backed-workflow-verification)
-for counterexamples and lifecycle controls relevant to the audit.
-
-Report working routes as well as findings. Separate a reproduced contract bug,
-an intentional limitation, a design opportunity and an unverified hypothesis;
-include the smallest useful reproduction, impact and coverage limits. Do not
-claim autonomous-agent selection from a scripted trace. Check related reports
-before proposing another issue, and avoid treating lack of API parity as a bug.
-
-## Design recovery around the failure
-
-Distinguish a request that violates its input contract from a valid selection
-that the current target, provider inventory, or project cannot resolve. The
-same `invalid_request` code can represent either. Suggest schema inspection
-only when the input contract is the problem; for a valid lookup, preserve the
-caller's exact selector, the observed reason and any candidates, and give a
-next step that addresses that outcome. An inventory miss does not prove that
-the artifact lacks the requested item.
-
-For prerequisite failures, identify what the requested operation actually needs.
-A missing executable, a wrong path, an incompatible host or version, denied
-permission, and a download timeout need different repairs. Preserve the observed
-failure instead of calling all of them "not installed".
-
-Derive the required engine from the operation's execution contract. For example,
-`inspect_firmware_regions` needs Binwalk; `extract_firmware` needs Unblob.
-Configuring the other tool cannot enable the requested operation. An installed
-JDK outside the selected PATH may need `JAVA_HOME`, not another installation.
-Say where a setting must change: a shell export does not change an already
-running MCP server's environment.
-
-Keep repair instructions with the contract that owns the failure, and preserve
-them through provider readiness, capability discovery, doctor and CLI/MCP output.
-An error description is not a repair instruction. Do not make each consumer
-guess the fix from diagnostic text or invent another list of prerequisites.
-
-Keep recovery within the selected target, provider, project and authority. If
-another context could help, describe it as an explicit choice and state any
-relevant loss of state; do not switch or select a candidate automatically.
-Preserve uncertainty, partial observations, and session or cleanup state. A
-suggested retry must be safe and explain any required change or wait.
-
-Verify recovery through the public workflow: reproduce the failure, follow
-the suggested next step when feasible, and check the result and session state.
-Include a malformed-input control so schema guidance remains available when it
-is actually needed. Compare CLI and MCP when both expose the operation.
-
-For each confirmed bug, check sibling adapters and other consumers of the same
-facts. Reproduce suspected matches and retain a working comparison where one
-exists. Group reports and fixes around the shared cause; similar wording alone
-does not establish another instance.
-
 ## Define the contract
 
 - Use strict inputs with explicit target identity and required fields. Preserve
@@ -177,51 +83,6 @@ does not establish another instance.
   ceiling and its recovery as described in
   [admission limits and recovery](design/limits-and-recovery.md).
 
-### Compose declared Evidence inputs
-
-Declare each logical Evidence source with the shared `evidenceInputSchema`:
-complete inline Evidence or an exact
-`{kind: "retained-evidence", evidence_id}` reference. Use that declaration in
-single, optional, array and nested source fields across domains. Keep complete
-record schemas for stored Evidence, bundle records and pure semantic inputs;
-request alternatives do not change those representations. Ordinary IDs in
-parameters or result data are not implicitly source selectors.
-
-Derive borrowing request validation and source resolution from the canonical
-request schema with `getEvidenceInputContract` and `resolveEvidenceRequest`.
-The shared application entrypoint selects references for CLI and MCP before the
-format owner admits, authenticates and interprets their records. Preserve
-admission before copying large source payloads. Do not maintain a second list
-of source paths or resolve references only in an adapter. A resolved reference
-has the same identity, caller-selected observations, provenance, coverage and
-partial or unknown facts as its complete inline record; it never reruns a
-producer or upgrades incomplete evidence.
-Keep Evidence-bearing request unions outside skipping `default` wrappers;
-use `prefault` when a default must pass through branch selection. Catalog
-conformance rejects unsupported source containers rather than silently losing
-their references.
-
-Return authenticated source records alongside derived workflow Evidence when
-the adapter must retain them. Keep links to those exact sources and require the
-source closure when the workflow follows their links. Missing references and
-incompatible workflow roles are explicit failures; do not infer a substitute
-from ledger order, display names or the active target. A summary or inspection
-page has its own identity: consumers needing complete source facts use its
-`normalized_result.parent_evidence_id`, unless their contract explicitly accepts
-that view.
-
-New provider-owned source observations require a retention owner. Existing
-caller-owned inputs can also compose on a fixed port without a recorder;
-when a recorder is available, preserve its acceptance or rejection and retain
-completed sources through cancellation.
-
-MCP supplies the current ledger lookup. CLI commands that advertise
-`--evidence-bundle` use one explicitly selected, authenticated bundle for the
-command's lifetime. Keep cleanup with that owner. A retained reference does not
-grant filesystem access: file selectors remain separate, explicit contracts
-where supported. See [retained Evidence inputs](mcp-contracts.md#retained-application-evidence-inputs)
-and [CLI reuse](cli.md#import-export-and-compare-evidence).
-
 ### Interpret boundary facts once
 
 The format or protocol reader owns interpretation. Pass its parsed facts and
@@ -271,47 +132,6 @@ artifact can execute successfully.
 
 ## Own the lifecycle
 
-The investigation owns authenticated Evidence and complete Unknown revision
-history independently of an engine. `close_binary` drains earlier admitted work,
-releases engine resources and clears replay/invalidation state; investigation
-references survive, including target-free closes and cleanup failures. A target
-switch does not make historical observations current for its new engine.
-
-`reset_investigation` is the explicit destructive boundary. It drains earlier
-analysis, imports, exports and Unknown operations, then clears investigation and
-replay/source bindings while retaining a healthy active engine. Metadata mutation
-invalidation remains in force until that engine is recreated. Later admitted work
-waits for the transition; earlier late results cannot repopulate cleared history.
-Runtime disposal seals new acquisitions and releases records after successful
-owned engine/file cleanup; failed cleanup keeps the owner available for retry.
-
-Records are retained in memory under a fixed per-owner representation allowance
-derived from one quarter of initial available V8 heap. Admission accounts for
-Evidence, Unknown history and indexes before atomic commit; metadata replacement
-uses its size delta and duplicates do not accumulate. There is no silent eviction.
-`binary_session.investigation` reports committed counts, estimated representation
-bytes and the allowance; these estimates are not process RSS measurements. Live
-authentication headroom is checked separately. On refusal, export a checkpoint,
-reset, and import only the required investigation, or start a process with a
-larger heap. Retention does not promise automatic persistence.
-
-An MCP request retains its original session admission until its handler cleanup
-and response send settle. A reset queued behind that request therefore cannot
-invalidate Evidence before its reply is sent. Nested work borrows the same
-admission. Cancellation before sending releases a suppressed reply after handler
-cleanup; cancellation after sending starts still waits for transport settlement.
-Lifecycle tools drain earlier admissions without acquiring one themselves.
-
-`reset_investigation(save_path)` saves the complete cross-domain canonical bundle
-once before clearing. It awaits file sync, atomic publication and staging cleanup;
-failed save, incomplete cleanup or cancellation observed before reset commit
-preserves all records. Publication
-can precede cancellation or cleanup failure; the error retains its committed file
-receipt. Import that bundle to restore original Evidence IDs and all Unknown
-revisions in a new process. Engine replay snapshots remain a separate target and
-profile-bound mechanism. This checkpoint contract does not promise recovery from
-an uncheckpointed process exit or parent-directory loss after a host crash.
-
 `SafeOutputTree` publishes only after file readback, nested-directory fsync
 from children to parents, and root-parent fsync on hosts that support directory
 syncing. Windows skips directory fsync. Failed writes retain a separate pending

docs/uf2-dfuse.md

@@ -1,224 +0,0 @@
-# UF2 and DfuSe images
-
-REA inventories UF2 (Microsoft's USB Flashing Format) and DfuSe (ST's DFU
-update container, `.dfu`) files through `inspect-artifact` /
-`inspect_artifact`, and materializes their decoded bytes through
-`extract-artifact` / `extract_artifact`. UF2 is the drag-and-drop format of the
-RP2040 and RP2350 bootloaders, of TinyUF2 on ESP32-S2 and ESP32-S3, and of
-`esptool merge-bin --format uf2`. Decoding is static and needs no external tool.
-
-```sh
-rea inspect-artifact ./firmware.uf2 --json
-rea inspect-artifact ./firmware.dfu --detail summary --evidence_output evidence.json --json
-rea extract-artifact ./firmware.uf2 --json
-```
-
-For MCP, open the file with `open_binary`, then call `inspect_artifact`. Summary
-delivery retains the complete Evidence; use `parent_evidence_id` with
-`inspect_analysis_view` to read selected regions and fields. `extract_artifact`
-returns a fresh `output_root` containing one raw file per region.
-
-## Recognition
-
-A file is UF2 only when its first 512 bytes are a complete block with all three
-magic numbers: `0x0A324655` and `0x9E5D5157` at the start and `0x0AB16F30` at
-the end. A file is DfuSe only when it begins with `DfuSe` and format version 1
-and ends with a 16-byte DFU 1.1a suffix: `bcdDFU` `0x011A`, the `UFD` signature
-and `bLength` 16. The suffix CRC is not part of recognition. The file name does
-not matter, and a file with only one of the DfuSe markers stays unrecognized.
-The container formats are `uf2` and `dfuse`.
-
-## UF2 regions and metadata
-
-Each entry is one address-contiguous region of one family's main-flash
-payloads, named `family-0x<familyID>/0x<start>-0x<end>.bin` with an inclusive
-end address, for example `family-0xe48bff56/0x10000000-0x1000ffff.bin`. Blocks
-without the familyID flag (`0x2000`) go under `no-family/`. Families are
-separate address spaces: a multi-family file, such as a Pico SDK image for both
-RP2040 and RP2350, has a region per family even at the same addresses. Gaps are
-never filled.
-
-Region `format_metadata` (`uf2-region`) records `family_id` (or `null`),
-`family_name`, `start_address`, `end_address`, `length`, `block_count`, and
-`first_file_block`/`last_file_block`: the zero-based positions in the file of
-the contributing blocks, not their UF2 block numbers. `family_name` is REA's
-label, not file content. It comes from a small table copied from Microsoft's
-`uf2families.json` at commit
-[`cf3bd7f9`](https://github.com/microsoft/uf2/blob/cf3bd7f9c274b949528f8cd6a19eef2502a687d2/utils/uf2families.json),
-which the root's `family_name_registry` names. The table covers the ESP32
-family, ESP8266, RP2040, the RP2350 and RP2XXX download families, STM32F4,
-nRF52840, SAMD21 and SAMD51. It also covers the families that LibreTiny builds
-for and the registry lists: RTL8710A, RTL8710B, RTL8720C, RTL8720D, BK7231U,
-BK7231N, BK7251 and BL602. Other IDs, LibreTiny's LN882H among them, keep their
-value with `family_name: null`. A familyID names a target family; it does not
-establish the CPU state, memory map or entry point.
-
-Root `format_metadata` (`uf2`) records:
-
-| Field                                                      | Meaning                                                                                                                |
-| ---------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------- |
-| `block_count`, `trailing_bytes`                            | Complete 512-byte blocks, and bytes after the last complete block                                                      |
-| `invalid_block_count`                                      | Blocks with a wrong magic number, a payload over 476 bytes, or a payload that wraps past 4 GiB                         |
-| `flash_block_count`                                        | Valid main-flash blocks, the only source of region bytes                                                               |
-| `not_main_flash_block_count`, `file_container_block_count` | Blocks with flag `0x1`, and blocks with flag `0x1000`                                                                  |
-| `md5_block_count`, `extension_tag_block_count`             | Blocks that declare an MD5 flash region (`0x4000`) or extension tags (`0x8000`)                                        |
-| `family_count`, `family_name_registry`                     | Distinct familyIDs among main-flash blocks, and the registry revision of `family_name`                                 |
-| `numbering_group_count`                                    | Groups of valid blocks that share a familyID (or none) and a declared block count                                      |
-| `missing_block_count`                                      | Block numbers below a group's block count that no valid block carries                                                  |
-| `ambiguous_numbering_group_count`                          | Groups whose numbers appear at unequal counts of target addresses                                                      |
-| `repeated_block_count`, `out_of_order_block_count`         | Blocks whose number already appeared in their group, and blocks numbered at or below the previous block of their group |
-| `block_number_out_of_range_count`                          | Blocks numbered at or above their block count, or with a block count of 0                                              |
-| `region_count`, `data_bytes`, `duplicate_bytes`            | Regions, unique decoded bytes, and bytes rewritten with identical values                                               |
-
-Numbering is grouped by familyID because a bootloader ignores every field of
-another family's block, including its numbering. Within a group, a block number
-seen at several target addresses belongs to several copies of a sequence:
-esptool numbers each merged input file from 0, so inputs with equal block
-counts share a group, and each number then appears once per input. A block sent
-twice to the same address is one block. A group is complete when every number
-below its block count is present at the same count of addresses. If some numbers
-appear at more addresses than others, a copy may have lost a block, so coverage
-is unknown and a limitation names the group.
-
-## UF2 facts, limitations and failures
-
-| Situation                                                     | Outcome                                                                                        |
-| ------------------------------------------------------------- | ---------------------------------------------------------------------------------------------- |
-| Blocks out of address order                                   | Sorted into regions                                                                            |
-| Blocks numbered at or below the previous block of their group | Counted in `out_of_order_block_count`; the spec lets blocks arrive in any order                |
-| An address written twice with the same value in one family    | Accepted and counted in `duplicate_bytes`                                                      |
-| An address written twice with different values in one family  | Fails, naming the family, the address and the block spans of both writes                       |
-| The same addresses in different families                      | Separate regions; never a conflict                                                             |
-| Numbered blocks absent from a group                           | Regions are returned; coverage is unknown and a limitation names the groups                    |
-| Reused numbers at unequal address counts                      | Regions are returned; coverage is unknown and a limitation names the groups                    |
-| An invalid block                                              | Excluded; coverage is unknown and a limitation names the first one and its offset              |
-| A partial final block                                         | Excluded; coverage is unknown and the file may be truncated                                    |
-| Block numbers at or above the block count                     | Payloads are kept; coverage is unknown                                                         |
-| Not-main-flash blocks (`0x1`)                                 | Excluded from regions; their count and payload byte count are reported; coverage is unaffected |
-| File-container blocks (`0x1000`)                              | Excluded from regions; their files are not reconstructed, so coverage is unknown               |
-| MD5 (`0x4000`) and extension-tag (`0x8000`) blocks            | Counted and reported as a limitation; neither is decoded or verified                           |
-
-Unlike a malformed Intel HEX record, which fails the whole file, an invalid UF2
-block is excluded and reported: each block carries its own framing and address,
-so its neighbours stay readable.
-
-The MD5 structure is not checked because it is not a checksum of the block's
-bytes in the file. It names a region of device flash, usually aligned to erase
-pages, whose MD5 a flashing tool compares to skip writing. Producers also
-disagree on its place: the specification puts it in the last 24 bytes of the
-data area, while esptool v4.12.0 and v5.6.0 write it right after a shorter final
-payload, so those 24 bytes hold zeros or part of that structure.
-
-## DfuSe regions and metadata
-
-Each element is one entry at its own file range, named
-`target-<t>/element-<e>-0x<start>-0x<end>.bin` with zero-based target and
-element indexes, for example `target-0/element-0-0x08000000-0x0800ffff.bin`.
-Elements are never merged. Each occurrence's `source_location` is the byte range
-of the element data in the file.
-
-Element `format_metadata` (`dfuse-element`) records `target_index`,
-`alternate_setting`, `target_name`, `element_index`, `start_address`,
-`end_address` and `length`. `target_name` is `null` when `bTargetNamed` is 0;
-otherwise it is `szTargetName` up to its first NUL, one character per byte.
-`compare_artifacts` treats an element's alternate setting and target name as
-its declaration, so the same bytes moved to another device memory are
-`changed` in `metadata`.
-
-Root `format_metadata` (`dfuse`) records:
-
-| Field                                                | Meaning                                                                         |
-| ---------------------------------------------------- | ------------------------------------------------------------------------------- |
-| `image_size`, `target_count`                         | `DFUImageSize` and `bTargets` from the prefix                                   |
-| `element_count`, `empty_element_count`, `data_bytes` | All elements, elements of 0 bytes (which have no entry), and element data bytes |
-| `overlapping_element_count`                          | Elements that overlap an earlier element of the same alternate setting          |
-| `device_version`, `product_id`, `vendor_id`          | `bcdDevice`, `idProduct` and `idVendor` from the suffix                         |
-| `suffix_crc`, `computed_crc`                         | The stored `dwCRC`, and the same CRC computed over every byte before it         |
-
-Recognition already requires `bVersion` 1 and `bcdDFU` `0x011A`, so they are
-not repeated. The DFU suffix CRC is CRC-32 without the final inversion, as
-dfu-util stores and checks it.
-
-Producers disagree on `DFUImageSize`. UM0391 calls it the file length, and
-dfu-util's `dfuse-pack.py` writes that value since commit `ee6b393d`
-(2020-10-08). Earlier `dfuse-pack.py` and MicroPython's `tools/dfu.py`
-(checked at `cb99ca98`) write the length before the suffix, and an ST community
-report describes ST's DfuFileMgr the same way; REA has not run DfuFileMgr.
-dfu-util's own parser ignores the field. REA accepts either value and keeps the
-declared one in `image_size`.
-
-## DfuSe facts, limitations and failures
-
-| Situation                                                                          | Outcome                                                                                             |
-| ---------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------- |
-| `dwCRC` differs from the computed CRC                                              | Follows `integrity_policy`, below                                                                   |
-| A target without the `Target` signature                                            | Fails with its byte offset                                                                          |
-| `DFUImageSize` that equals neither the file length nor the bytes before the suffix | Fails with the declared size, the suffix offset, the file length and whether the suffix CRC matches |
-| A target size or an element size that disagrees with the bytes that hold it        | Fails with the byte offset and the declared and available sizes                                     |
-| An element whose address range wraps past `0xFFFFFFFF`                             | Fails with its byte offset                                                                          |
-| Overlapping elements of one alternate setting                                      | Kept as separate entries; a limitation names the first four; coverage is unaffected                 |
-| The same addresses in different alternate settings                                 | Separate entries; an alternate setting selects a device memory                                      |
-| Elements of 0 bytes, and targets with no elements                                  | No entry; counted; a limitation names the first four, with address and alternate setting            |
-
-A CRC mismatch is an integrity contradiction, never proof of a cause. With the
-default `integrity_policy` `fail`, inspection and extraction fail with
-`artifact_integrity_mismatch`, whose details carry `algorithm: "dfu-crc32"`,
-`declared_crc32` and `calculated_crc32`. With `record-and-continue`
-(CLI `--integrity-policy record-and-continue`), the root occurrence becomes
-`mismatched`, `integrity_contradictions` records the pair for logical path `.`,
-and extraction carries that contradiction, because every element came from the
-contradicted container. The root occurrence has no `declared_integrity`: that
-field holds entry digests, so the declared CRC appears in the contradiction and,
-as a number, in `suffix_crc`. Under `fail`, the elements are hashed before the
-mismatch is raised.
-
-## Limits
-
-Each file must be at most 128 MiB. The UF2 decoder reserves at most 476 bytes
-per complete block before reading, merges payloads into regions of at most the
-same total size, and keeps one numbering entry per valid block, so its peak is
-about twice the decoded bytes. It retains at most 65,536 regions as entries; the
-order of blocks does not count against that bound. The DfuSe decoder holds the
-file once, serves elements as views of it, and retains at most 65,536 elements
-with bytes as entries; empty elements are only counted. These are fixed
-resource bounds, not format limits, and fail as limits (`file-size` and
-`capacity`) with no runtime override. Configurable ceilings are tracked in
-[#6176](https://github.com/morluto/rea/issues/6176).
-
-Decoded regions are cached only for the reader's lifetime, and each open checks
-the admitted carrier identity again. These readers share the Intel HEX
-reader's region streams, cancellation and close behavior.
-
-## Analyzing a region
-
-Inventory does not establish the CPU, byte order or memory map, or an entry
-point. To disassemble a region, extract it and open the region file with
-`open_binary` using format `raw-binary`, an architecture you choose, and
-`entry_point` set to the region start address; raw-binary maps file offset 0 at
-`entry_point`. Each region is opened separately, so references between regions
-are not resolved.
-
-## Verification
-
-Fixtures written from the UF2 specification and from ST UM0391 cover block and
-element layouts, numbering groups and reused numbers, families, rewrites and
-conflicts, invalid and partial blocks, not-main-flash and file-container blocks,
-structural faults, overlaps, both integrity policies, accepted boundaries beside
-each refusal, resource refusals, inventory, extraction, comparison and reader
-identity checks. The reader lifecycle (cancellation, close and stream
-ownership) is covered by the Intel HEX reader tests, which exercise the shared
-reader. Two DfuSe fixtures are byte-identical, CRC included, to what the
-`build()` functions of dfu-util's `dfuse-pack.py` (at `f9a537c9`) and
-MicroPython's `tools/dfu.py` (at `cb99ca98`) produce for the same image, one for
-each `DFUImageSize` convention. Those functions were transcribed and run under
-Python 3; the scripts themselves were not run. CLI and stdio MCP tests exercise
-the same artifact provider and advertised schemas.
-
-`npm run verify:uf2` runs esptool's `merge-bin --format uf2` on generated
-inputs at known addresses, with and without MD5, with 256-byte payloads, with
-two inputs of equal block count, and on a concatenation of two chips' outputs.
-Inspection and extraction must return every input at its address under
-esptool's own familyID. It passed with esptool v4.12.0 and v5.6.0 on macOS. Set
-`REA_ESPTOOL_PYTHON` to a Python that runs `-m esptool`. Pico SDK, picotool,
-`uf2conv.py`, TinyUF2 and real DfuSe producers remain unverified, and no device
-accepted these files in REA's tests.

docs/user-visible-errors.csv

@@ -50,7 +50,6 @@ harm_rank,location,trigger,current_copy,user_risk,proposed_replacement,implement
 36,src/main/reportMcpTransportError.ts:reportMcpTransportError,MCP error has no known validation or disconnection identity,MCP reported an error with unknown connection state. Check whether the client is still connected before following connection-loss recovery.,Connection state remains unknown,Keep current copy,implemented,injected unknown-error recovery regression
 37,src/main.ts:serveStdio throw,MCP connection cannot be created,Failed to start MCP stdio transport,Exposes transport implementation and gives no recovery,"Retry once. If it fails again, tell the user REA could not start its MCP connection and ask them to restart the MCP client, then run `rea doctor`.",implemented,verified by injected transport startup-throw runtime test
 38,src/main.ts:requestShutdown catch,Connection or analysis session close rejects,Failed to shut down cleanly,Does not explain duplicate-process risk or recovery,REA could not close cleanly. End the REA process before starting it again.,implemented,verified by injected handle-close rejection runtime test
-38.5,src/domain/analysisErrorRecovery.ts:cleanupRetryRemediation,close_binary returns cleanup_incomplete while the session retains the failed cleanup owners,"Provider cleanup could not be fully confirmed. Review the reported local resources before opening another target. (retryable: false, no recovery)",Agent could abandon the connection that owns the only cleanup retry,"Append: This connection retains that cleanup. Keep it open; after the reported condition settles or is resolved, call close_binary without snapshot_path and check its result. That call retries the retained cleanup without rerunning the failed analysis, preserves investigation Evidence and Unknown history, and can report cleanup_incomplete again. Add recovery.kind=retry_cleanup naming close_binary; keep retryable false",implemented,MCP close_binary with the real KunaProvider and a fake Kuna whose export stop stays unproven; process-capture MCP retry; session tests for an unoffered one-shot close and for failed and completed snapshot saves; one-shot IDA CLI cleanup reports no hint; real Kuna not run
 39,src/main.ts:entrypoint catch,Unhandled rejection escapes run(),Unexpected server startup failure,Vague and lacks diagnostic recovery,"Do not repeat this startup. Tell the user REA could not start and ask them to restart the MCP client, then run `rea doctor`.",implemented,verified by injected entrypoint rejection test
 40,src/application/Update.ts:unknown-install-method,Running package is not owned by detectable global npm installation,Update manually with: npm install --global rea-agents@latest,Old global-npm advice does not identify the owning installation,"Update this installation with the package manager or source checkout that owns it. For a one-off latest invocation, use npx rea-agents@latest.",implemented,36 Update tests passed; public CLI unowned-installation refusal verified with isolated package-manager fixtures
 41,src/application/Update.ts:install,npm global install subprocess exits unsuccessfully,npm install --global rea-agents@latest failed.,Old registry/global-install advice omits the actual version prefix and installer failure,"REA could not install {version} in {prefix}: {failure}. Repair this npm installation, then rerun rea update.",implemented,36 Update tests passed; public CLI owned npm fixture failure preserved version prefix and installer reason
@@ -119,8 +118,7 @@ Then rerun this installer.",implemented,verified by shell branch inspection
 90,install.sh:version mismatch,Installed rea reports a different version,installed version ACTUAL does not match EXPECTED.,Low risk; gives exact integrity mismatch,Keep current copy,unchanged,verified by exact installer test
 90.5,@modelcontextprotocol/server:tool input validation,Caller sends arguments that violate a declared tool schema,"Canonical invalid_request with the SDK diagnostic plus recovery.kind=inspect_input_contract and a bounded instruction to read the advertised schema or call tools/list",Keeps field/type correction while telling the agent how to recover; diagnostics over 4 KiB stay on the existing retained-error path,Normalize ordinary validation failures and retain oversized diagnostics,implemented,verified by real in-memory and stdio MCP client/server calls with wrong argument types
 90.6,incur:unknown CLI command,Caller enters an unknown REA command,"'COMMAND' is not a command for 'rea'. Suggested command: rea --help",Low risk; identifies input and exact discovery action,Keep framework-generated copy,unchanged,verified by real packaged dispatcher invocation
-90.7,src/ghidra/GhidraProviderClient.ts:projectPrimarySessionError,One procedure's decompile reaches REA_GHIDRA_DECOMPILE_TIMEOUT_SECONDS,"Ghidra decompilation of {entry} exceeded the {N}-second limit set by REA_GHIDRA_DECOMPILE_TIMEOUT_SECONDS. Only this procedure's decompilation was stopped. (MCP adds: The Ghidra session remains usable.)",Low risk; names the setting; only a continuing MCP caller is told the session remains usable,Keep current copy,implemented,"provider projection test, CLI/MCP fixture-bridge boundary test and real-provider lane"
-90.8,src/ghidra/GhidraFileOffsetFailure.ts:ghidraFileOffsetUnavailable,"address_to_file_offset receives a well-formed address that is unmapped, uninitialized, without an authoritative target-file source, ambiguous or beyond the exact JSON integer range",{bridge reason}. REA establishes no single exact original-file offset for this well-formed address and does not derive or choose one.,Previous copy called the input invalid and directed schema repair for a valid address,"Keep the bridge reason as the headline, point to inspect_native_load_image, omit recovery.kind=inspect_input_contract and record details.issues[0].observed.file_mapping",implemented,provider projection tests; MCP and CLI analysis path through the real Ghidra client with a simulated bridge; real Ghidra not run
+90.7,src/ghidra/GhidraProviderClient.ts:projectPrimarySessionError,One procedure's decompile reaches REA_GHIDRA_DECOMPILE_TIMEOUT_SECONDS,"Ghidra decompilation of {entry} exceeded the {N}-second limit set by REA_GHIDRA_DECOMPILE_TIMEOUT_SECONDS. Only this procedure's decompilation was stopped; the Ghidra session remains usable.",Low risk; names the setting and keeps the session,Keep current copy,implemented,provider projection test and real-provider lane
 91,src/application/binaryDiagnostics/ByteEntropyService.ts (issues); src/domain/analysisErrorPresentation.ts (recovery),Invalid file or window,Expected a regular file.; Selected file could not be found.; Selected byte window starts beyond the end of the file.; Selected byte window extends beyond the end of the file.; File size exceeds exact numeric offset representation.,Invalid selection cannot produce complete entropy Evidence,"Read the declared input schema or CLI usage for inspect_byte_entropy; if using MCP and the catalog may be stale, call tools/list. Correct the listed fields, then retry. Do not repeat the unchanged call.",unchanged,Executed CLI/stdio MCP: path/offset/length refusals and tiny + system-binary controls; shared canonical recovery; service/MCP tests check classification and fields; remaining listed errors source-inspected
 92,src/domain/analysisView/byteEntropyView.ts,Non-summary entropy view,Byte entropy Evidence supports the summary view; retrieve parent Evidence for the complete block series.,Unsupported view selection,Use the summary view or retrieve complete parent Evidence,implemented,typed input rejection
 93,src/windows/WindowsNativeLoader.ts:load refused,Windows refuses to load the digest-verified native addon (for example Smart App Control or App Control policy),"REA Windows native controls are unavailable: Windows refused to load the verified native/windows/build/rea-windows-x64.node: {OS error} The file matched the package manifest, so restoring or reinstalling it will not help. ...",Previous artifact copy told users to restore or rebuild files that were already intact,"Name the OS refusal, say restoring cannot help, state that Ghidra and JADX need native controls while setup can still register clients, and point to a policy-allowed host or a maintainer-signed build",implemented,simulated loader refusal unit test; real Smart App Control block not reproduced

docs/verification/capability-composition-2026-11-01.md

@@ -1,246 +0,0 @@
-# Capability composition verification — 2026-11-01
-
-Scope: issue #8429, the service composition/ownership increment of #740. Baseline
-`6e9ee97a69cb16c7150d8b550e705cba055ee4f0`; implementation `bd9bf76d8`, followed
-by type-only binding cleanup `161c3c146`. This changes existing composition,
-metadata ownership and cleanup bookkeeping; no new provider/target authority.
-`BinarySession` keeps its existing transition/admission barrier.
-
-## Executed source and boundary checks
-
-Full typecheck, module boundaries, architecture guards, test discovery,
-production reachability, documentation consistency and repository formatting
-passed. Changed-file typed lint passed with one worker and `GOMEMLIMIT=512MiB`:
-39.622 s elapsed, 39.261 s process-family CPU, 2,945,368,064 B kernel peak.
-Initial whole-repository typed and ordinary lint attempts hit the configured
-3 GiB early stop; no OOM occurred. Whole-repository lint is not locally
-qualified; changed-file checks and the final ownership-boundary typed checks
-passed separately.
-
-Relevant executed groups: 216 parser/boundary/metadata/provider-owner tests;
-5 scope/factory tests; 27 MCP availability/composition tests; 28 deferred
-startup/protocol/publication tests; 50 CLI factory/cleanup/target-input tests;
-16 SDK schema tests; 4 compiled-verifier metadata link tests; and investigation
-lifecycle, unknown-history and transport cleanup regressions. These groups
-contain overlapping repeated checks and are not a unique total. The final
-Android transport group passed all 4 cases, including construction failure and
-failed cleanup retry. The moved Frida test body was preserved byte-for-byte;
-its discovery owner changed to the adapter lane.
-
-The old manual provider-close list was temporarily restored as a negative
-control: the new successful-peer cleanup regression failed, then the current
-source was restored. Synchronous close throws, undefined rejection reasons,
-concurrent close joining, borrowed optional observations and failed-owner retry
-are controlled tests, rather than claims of natural failures in real engines.
-An initial new transport assertion omitted the existing outer
-`OwnedMcpServers` AggregateError; its expected nesting was corrected. Other
-preserved harness failures were missing SDK catalog preparation and two wrong
-CLI test paths; corrected commands passed. One formatting issue was corrected.
-
-Ordinary Knip reports one unused exported `DarwinHelperCache` type at
-`src/process/DarwinHelperCache.ts:465`. An independent run on the clean pinned
-baseline reports the identical sole issue; that file is unchanged here.
-
-## Real applications and complete-result parity
-
-Every case used actual public CLI/MCP routes. Inputs were hashed before/after,
-with no source mutation. Both arms used pinned Node 24.22.1/npm 11.16.0 and
-fresh isolated processes/configuration; OS page caches were uncontrolled.
-
-| Domain     | Genuine application/artifact                                        | Independent fact oracle                         |
-| ---------- | ------------------------------------------------------------------- | ----------------------------------------------- |
-| Go         | installed GitHub CLI `/usr/bin/gh`, Go 1.19.6                       | ELF Go build-info bytes/module data             |
-| Managed    | SDK 8.0.427 `NuGet.CommandLine.XPlat.dll`, selected Program members | independent dnfile metadata/CIL facts           |
-| JavaScript | installed agent-browser 0.27, selected entry source                 | original source declarations/imports            |
-| Android    | NewPipe 0.29.1 APK inventory/application graph                      | complete ZIP member census and 9 member digests |
-| WASM       | actual CSS WASM artifact with WABT 1.0.42                           | independent raw sections/types/exports          |
-
-All five full public CLI Evidence results matched across arms. Explicit Go/JS
-per-arm bundle output paths were verified separately, and their complete saved
-parent Evidence matched. MCP performed 117 calls per arm, including six fresh
-producer calls, retained derivation, repeated close, checkpoint/reset, expected
-missing references, same-process restore and actual fresh-process restore.
-Complete producer bundles, full derived Evidence, exact requests/IDs and
-complete checkpoints matched across arms. The analyst Unknown revision 1→2
-history and every canonical mutation/history record remained authenticated;
-fresh re-exported checkpoints were byte-identical. Fresh consumers ran no
-producer calls. Ten independent domain fact assessments passed.
-
-| Completed workflow       | Baseline elapsed / CPU (s) | Feature elapsed / CPU (s) | Baseline / feature kernel peak (B) |
-| ------------------------ | -------------------------- | ------------------------- | ---------------------------------- |
-| Five CLI tasks           | 17.675 / 16.268            | 22.192 / 20.667           | 393,936,896 / 390,504,448          |
-| Five MCP lifecycle tasks | 68.270 / 65.500            | 61.201 / 58.041           | 731,680,768 / 776,331,264          |
-
-Times are single observations including setup and all calls, not a causal
-speedup/regression claim. Fresh-process tasks are reported separately from
-same-process/restored consumers; neither is a controlled cold OS-cache run.
-All tasks ran serially under a one-CPU, 4 GiB hard/3 GiB early-stop, no-swap,
-192-task guard. CPU and peak memory are kernel process-family counters at
-payload exit while the observer remained alive; all completed tasks verified
-owned cleanup and no OOM. Sampling/RSS is not substituted for these counters.
-Scripted checks do not incur model tokens; model usage is recorded separately.
-
-## Native engine and Codex CLI
-
-Real Ghidra 12.1.4/JDK 21 on `/usr/bin/jq` passed 37 public MCP calls per
-arm. Two new light address queries before/after healthy investigation reset
-returned identical Evidence. The same MCP client retained the same owned JVM
-PID, start time, process group and public run identity. Three retained native
-compositions used authenticated historical dossiers; these dossiers were not
-regenerated. Full derived results, original bundles and Unknown histories
-matched across arms and survived same/fresh-process restore.
-
-A mixed-routing task passed 58 calls per arm, with explicit `jq → APK → managed`
-metadata target switches and five new static producer families through the final
-registry. These metadata switches do not imply launching every target engine.
-Complete originals, derived results and checkpoint history matched across arms.
-
-| Completed task              | Baseline elapsed / CPU (s) | Feature elapsed / CPU (s) | Baseline / feature kernel peak (B) |
-| --------------------------- | -------------------------- | ------------------------- | ---------------------------------- |
-| Ghidra/native lifecycle     | 38.196 / 36.804            | 41.741 / 40.369           | 1,111,789,568 / 1,098,362,880      |
-| Mixed target/domain routing | 27.557 / 26.984            | 27.255 / 26.527           | 1,039,253,504 / 1,037,910,016      |
-
-The native task includes a fresh engine start; its second query is a healthy
-same-engine observation. Historical dossier reuse and fresh process consumers
-are separate phases. These are single observations with uncontrolled OS caches.
-
-Local `codex-cli 0.165.0` ran one actual `client-code` trial with the requested
-`gpt-6.1-terra` alias, reasoning `high`, and 19 selected tools. The resolved
-server-side model identity is not inferred. It completed 32 MCP calls across
-JavaScript, managed, Android and WASM: five new producer calls, retained
-compositions, four expected missing-reference controls, close/reset/save/import
-and Unknown revision 1→2. There were no unexpected MCP errors or timeout.
-
-The model's JS self-check remained explicitly **partial/unverified**: it used
-`JSON.stringify`, whose property ordering changed after canonical import.
-Independent full structural comparisons of all three actual results and the
-baseline proved identical fields, values, array order and Evidence ID. The
-first ordering difference was only the keys of
-`graph.nodes[0].observations[0].properties`. This distinction is retained in the
-assessment; the model's self-check is not relabeled a complete pass.
-
-An actual new, target-free MCP process replayed the model's checkpoint in
-9 calls. Complete Evidence and Unknown revision/mutation histories authenticated,
-and its 18,968,472 B export was byte-identical (17 Evidence records,
-2 Unknown revisions, 1 head), SHA-256
-`165188d74298f0173c5730973ecb5354a1b966ca54ec46ee177efa049ebbc755`.
-All four derived results and their complete producer records matched the
-independent baseline. The copied authentication profile was removed; runtime,
-production source and selected input hashes remained unchanged.
-
-Actual client usage for the single attempt: **336,490 input tokens**, of which
-**295,680 were cached**; **3,659 output tokens** and **250 reasoning output
-tokens** were reported. Cached input is a subset, not an additional token total.
-Baseline model usage was not measured; neither token savings nor a speedup is
-claimed. Scripted source-fact and fresh-process verifiers incur no model API
-tokens and are separate from this model usage.
-
-| Completed verification              | Elapsed / process-family CPU (s) | Kernel family peak (B) |
-| ----------------------------------- | -------------------------------- | ---------------------- |
-| Actual Codex CLI trial              | 74.644 / 26.818                  | 1,061,597,184          |
-| Independent fresh checkpoint replay | 6.142 / 5.934                    | 757,895,168            |
-
-Manual final-answer review verified the reported IDs, counts, digests, coverage
-and Unknown state against complete baseline values, all actual model calls and
-the independent replay. The outcome is supported with the explicit model JS
-self-check limitation resolved independently. Maximum observed in-flight MCP
-calls was one; no target command, web or file-change tool items occurred.
-Factual-assessment SHA-256:
-`33451102e5faf57f11c627481899f16c4fc47fa5cba5f12cd2ed781a3de54ccf`.
-Final immutable input/runtime audit SHA-256:
-`73abce493182a7b433b4b78737720640ceb41d6df435cb0fec915468a0a304c8`.
-
-## Catalog and build identity
-
-Both compact/full SDK catalogs are byte-identical to baseline: 234 tools,
-6 prompts, 180 CLI commands. The provider projection changes from 63 to 67 rows
-only for source-proven web-source/module tracing, Harmony and QLOG provenance
-corrections. All other product sections are unchanged. Its expected provider
-SHA-256 is `4234ed15d7e53f34599b59dfba1f678369c0ae95b2135c7ba3414d944ab156b6`.
-The 66 static declarations have 49 runtime keys and 17 explicit source-owned
-workflow/engine groups; 70 bindings union to 67 identities. Static imports reach
-44 pure modules without schema, engine or factory runtime imports.
-
-The baseline runtime is `0e94962f64f3f532cc96b2432916f328f60058e97cd0e8e25f5c3e6ed3cdec10`
-(2,670 files). Static pairs used clean `bd9bf76d8`, runtime
-`62018a023b185dd9c6839799ed1fe4f085810161c723e508fc817d2fccdb59e3`
-(2,713 files). Final type-only cleanup `161c3c146` rebuilt to
-`d7be1d17dc6b5c23f33468398656ac4d3961380368be1f70dc767f0ba1fac6bf`.
-The complete earlier manifest is cryptographically reconstructed by removing
-one emitted trailing comma in `dist/composition/capabilityServices.js`'s
-existing named import; every other runtime file is byte-identical. This is not
-a claim that the two runtime hashes are identical. Native/mixed/model cases use
-the final runtime.
-
-Raw inputs, outputs, commands, hashes, recorded failed checks and resource receipts
-remain outside Git under
-`/home/yann/yann/.rea-worktree-artifacts/20261101/capability-module-ownership/`.
-Static-pair audit receipt SHA-256:
-`801707569577c7cec848334cf72bfab26a7ff4a95c2a87872d71d78eef7765a3`.
-
-## Review corrections and final qualification
-
-Two actionable review findings were fixed at their producing owners:
-
-- `980991573`: import-edge facts now distinguish fully erased declarations from
-  inline type bindings, which still load their module under
-  `verbatimModuleSyntax`. Compiler-backed parser/boundary regressions passed;
-  the old parser fails the new expectations. A separate three-file probe through
-  the actually selected compiler emitted both inline runtime edges and erased
-  whole-declaration/type-query edges, without compiling the repository.
-- `de6a61636`: the existing contract owner exposes 47 named canonical groups.
-  Thirty-seven full provider bindings reference those shared arrays, while
-  33 deliberate provider-subset/engine selections remain precise. The actual
-  ADB metadata now includes a new valid canonical ADB operation without an edit
-  to the provider declaration; reverting to the copied production lists fails
-  the regression. Unknown groups, unknown names and identity conflicts fail
-  catalog generation.
-
-Final full typecheck, module boundaries, test discovery and changed-file typed
-lint passed. Post-review source regressions passed 228 cases and SDK/MCP
-regressions passed 34; the two strengthened boundary/metadata files passed
-31 cases separately. These overlap earlier groups. Product catalog SHA-256
-remains exactly `e942c72047db651939dd47a31042e6818caaca7470092d63645801954a72b523`;
-both SDK catalogs remain byte-identical to the original baseline. Static metadata
-retains its pure loading boundary; canonical group IDs are imported only as types.
-
-The final implementation freeze is `de6a61636f3f84862cb4263c9ea219b7d2d4de36`,
-with 2,713 runtime files, SHA-256
-`be1d60c7dcca57eeb7ad09d682efd172c7f1679215e796a291b29eb52e29bda1`.
-Earlier model/engine measurements remain attributed to their executed revisions;
-they are not relabeled as runs on this later freeze.
-
-A new actual mixed-routing task on this final freeze passed all 58 calls:
-32.970 s elapsed, 32.180282 s process-family CPU, 1,042,538,496 B kernel peak.
-Independent five-domain source facts, complete producer records and all five
-full derived results/requests/IDs matched baseline and the prior qualified
-implementation. Same-process and true fresh-process restore preserved the full
-Unknown 1→2 mutation history and byte-identical 18,978,040 B checkpoint
-(20 Evidence records, 2 Unknown revisions, 1 head), SHA-256
-`0316bd6271c6d401a18c10d552b2005d39c98f3bbbc5945ae4823875af13fd5f`.
-Owned cleanup, runtime/production-source/input hashes and no OOM were verified.
-Append-only final-routing receipt SHA-256:
-`9c410c2c31bf38d7edc569deb95b93b7f9a2cf68a7b9a7f84d3ec924f0ad75cb`.
-This bounded requalification adds no model invocation or repeated native
-analysis query; earlier token measurements remain unchanged.
-
-CodeQL's six reported alert IDs (215, 490, 491, 493, 494, 495) all have open
-instances on exact-base main `6e9ee97`. All 24 SARIF paths were reviewed and
-independently checked: the new factory-default `process.env` sources retain the
-existing command/directory selection and explicit local authority. The shared
-filesystem/process sink files are byte-identical to base; Cutter's sink line
-shift only removes its old identity constant. No source suppression or global
-alert dismissal is included. The PR records the exact-base instance evidence
-and the owner's authorized exception for this unrelated existing-alert check.
-
-## Qualification limits
-
-NewPipe coverage is static inventory/graph, not real JADX decompilation: JADX,
-apktool and aapt2 were unavailable. No genuine local GGUF/safetensors target was
-available. Real Hopper, IDA, JEB, Cutter GUI, GDB/Rizin debugger and Frida target
-attachment are not qualified by these application cases; relevant factory,
-protocol and cleanup tests use controlled seams. Historical native dossiers
-are explicitly labeled reused evidence, not newly reproduced function analysis.
-Retained records remain bounded by existing investigation policies; this does
-not promise unlimited retention or a new durability backend. Further module
-qualification and `BinarySession` simplification remain under parent #740.

docs/verification/evidence-input-composition-2026-10-31.md

@@ -1,263 +0,0 @@
-# Evidence input composition verification
-
-The shared declaration and request resolver cover 20 individual-Evidence
-composition tools. Artifact file sources, analysis views and environment export
-keep their explicit source owners. Catalog conformance checks those boundaries
-and rejects undeclared record inputs or unsupported source containers.
-
-This record accompanies [#8293](https://github.com/morluto/rea/issues/8293) and
-the real Ghidra input-capacity regression
-[#8281](https://github.com/morluto/rea/issues/8281).
-The [machine-readable receipt](evidence-input-composition-2026-10-31.json)
-retains all fourteen model attempts, artifact identities, oracle provenance,
-tool profiles, actual usage, resource measurements and limitations. It also
-records the thirteen subsequent scripted public-transport attempts below.
-
-## Runtime and measurement scope
-
-Tests used Node 24.22.1 and local Codex CLI 0.165.0, explicitly requesting
-`gpt-6.1-terra` with reasoning `high`. This identifies the requested alias;
-the resolved server model is not inferred. Both dirty candidate builds were
-based on `23de10bb2849cdce8ddbe70504aa7cc57de75a98`. Their complete built-file
-fingerprints are recorded in the receipt. The later build includes the shared
-reference-format hint and authenticated source/type-boundary corrections.
-Subsequent cleanup reused the existing pure semantic-query input schema and
-moved SDK tests into their boundary project. Full and compact catalog bytes
-remained identical to the later model build; 22 affected checks were rerun.
-
-Heavy tasks ran serially in owned Linux scopes: one CPU, 4 GiB hard memory,
-3 GiB early stop, no swap and at most 192 tasks. CPU and peak memory are kernel
-process-family counters at payload exit while the observer remains alive;
-they are not final whole-scope counters. Cleanup was verified for every model
-attempt and CLI phase. No OOM event occurred.
-
-Each model task starts a fresh MCP process and isolated client profile. Native
-tasks start a fresh Ghidra database, then reuse its two retained dossiers.
-System/filesystem caches were not cleared; cold filesystem costs are unmeasured.
-Initial primary tasks used the complete catalog. Later scoped tasks are labeled
-`diagnostic/catalog-selection`; their different tools, guidance and selected
-facts prevent a controlled speed or token comparison.
-
-## Real application results
-
-| Domain           | Real artifact                                          | Reviewed outcome                                                                                                                                                                                                                                                                            |
-| ---------------- | ------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| Native           | Installed jq ELF, real Ghidra 12.1.4                   | Each selected function analyzed once; complete parent references supported a direct one-hop path and function comparison. Independent `objdump` corroborated the selected call. Nonexhaustive frontier and behavioral uncertainty remained visible.                                         |
-| Managed          | Shipped NuGet.CommandLine.XPlat.dll, assembly 6.11.2.1 | Artifact/member parent references projected a managed graph. The existing distinct-Evidence rule refused self-comparison. Digest, MVID, owner/token and selected CIL facts matched an independent metadata reader; its parser warnings limit that oracle's scope.                           |
-| JavaScript       | Obsidian 1.14.4 ASAR                                   | Partial: the producer hit its existing 300-second per-source timeout. The retained parent still supported a semantic trace. A bidirectional feature trace exceeded 10 MiB and had no supported retained summary. Tracked separately in [#8296](https://github.com/morluto/rea/issues/8296). |
-| JavaScript       | Shipped agent-browser 0.27.0 CLI entrypoint            | The final scoped task analyzed the exact selected source once, then reused its parent for feature and semantic traces. Independent source facts confirmed builtin imports/call locations. Unselected sources remained unknown; directory and file digests were distinguished.               |
-| WASM             | Shipped VS Code Tree-sitter CSS module                 | One real WABT inspection supplied retained references for export comparison and a portable bundle. An independent raw WASM reader confirmed seven imports, three exports and `tree_sitter_css: () -> i32`. Static interface equality did not imply runtime compatibility.                   |
-| Artifact / Apple | Rectangle 2.0.4 release ZIP                            | One retained inventory supported Apple projection and artifact comparison. Independent ZIP and Mach-O observations corroborated paths/content. Symlink metadata gaps remained unknown.                                                                                                      |
-| Android          | NewPipe 0.29.1 release APK                             | One retained inventory supported Android projection. Independent ZIP observations confirmed manifest, three DEX files and four ABI library members/digests. JNI path-pair hypotheses stayed inferred.                                                                                       |
-| Harmony          | Shark 1.0.8 release APP and its real inner HAP         | Both retained inventories supported Harmony projection. Separate ZIP/JSON checks preserved outer ZIP, APP and HAP identities, Stage/Ark/resource path observations and shallow APP coverage. Signature naming was not treated as cryptographic verification.                                |
-| Process          | Two controlled real jq CLI captures                    | Authentic captures were imported and compared by references, then their retained comparison was aggregated. MCP output deep-equaled the existing inline CLI result. Terminal change, settlement differences, filesystem/process unknowns and source closure were preserved.                 |
-
-The first supplemental agent-browser model task wandered into unrelated
-inventory tools and failed to perform the requested producer analysis. It was
-stopped and retained as an interrupted failure, including cumulative usage as
-a lower bound. The successful later scoped task does not erase that attempt.
-The missing-reference task produced its expected typed failure without opening
-a target, repeating a request or inventing Evidence.
-
-## Actual model task costs
-
-Input counts include schemas, accumulated context, extra calls and retries.
-Cached input is a subset of total input. Reasoning is included in output;
-its separate subset is retained in JSON. These are completed task costs, not
-serialized-byte estimates. The initial partial/interrupted attempts and their
-costs also remain in the receipt.
-
-| Later task                     | Calls / failed | Input tokens | Cached input | Output tokens | Task elapsed (s) | Family CPU (s) |    Peak bytes |
-| ------------------------------ | -------------: | -----------: | -----------: | ------------: | ---------------: | -------------: | ------------: |
-| jq, complete catalog           |         11 / 0 |      599,933 |      535,424 |         1,894 |           80.931 |      38.326466 | 1,269,936,128 |
-| agent-browser, scoped          |         12 / 1 |      619,589 |      563,712 |         2,519 |           54.521 |       9.472096 |   903,847,936 |
-| NewPipe, scoped                |          5 / 0 |      179,635 |      150,528 |         1,750 |           40.835 |      10.080132 |   704,409,600 |
-| Shark APP, scoped              |          6 / 0 |      221,571 |      197,376 |         1,339 |           32.437 |       6.377128 |   560,021,504 |
-| Shark HAP, scoped              |          5 / 0 |      184,452 |      152,576 |         1,212 |           31.108 |       6.012587 |   580,714,496 |
-| WASM plus export, scoped       |          4 / 0 |      161,702 |      141,056 |         1,033 |           32.320 |       9.036127 |   700,076,032 |
-| Imported process chain, scoped |          3 / 0 |       89,101 |       73,984 |           725 |           26.911 |       5.575060 |   531,283,968 |
-
-The later jq task made no malformed reference calls, while the initial task
-omitted the required `kind` twice. It selected a different callee and made three
-guidance calls; its longer elapsed time and different facts preclude attributing
-a general improvement to the new hint.
-
-## Equivalent portable CLI comparison
-
-The actual WASM model task exported a 13,925,066-byte authenticated bundle.
-Both fresh CLI processes selected its same complete inspection parent and
-compared exports against that parent. Their 3,732-byte outputs were byte-identical
-and deep-equal to the model's MCP comparison:
-`ev_b32346965c153a067abff9698aeba1ccbace34c78ac2071ac18311250b68c6da`.
-Bundle, selected source and runtime hashes stayed unchanged. Neither CLI arm
-started a decoder or reanalyzed the module.
-
-| Input                              | Request bytes | Elapsed including scope (s) | Family CPU (s) |  Peak bytes |
-| ---------------------------------- | ------------: | --------------------------: | -------------: | ----------: |
-| Complete inline pair               |    27,823,017 |                       2.832 |       2.612440 | 370,515,968 |
-| Retained pair plus selected bundle |           261 |                       2.632 |       2.385397 | 310,009,856 |
-
-The reference arm still reads/authenticates the existing bundle. This single
-ordered pair ran inline first with shared uncontrolled host caches. It establishes
-equivalent completed results and records observed costs; it does not establish
-a general speedup. Common upstream inspection/export costs appear in the model
-table. Preparation additionally cost 1.119 s / 0.875255 CPU s / 316,796,928 peak
-bytes; verification cost 0.518 s / 0.282755 CPU s / 42,881,024 peak bytes.
-The optional tokenizer was unavailable, so request-token savings are unmeasured.
-Request bytes are not presented as model tokens.
-
-## Fresh-connection public transport matrix
-
-The real transport matrix completed all nine supported domain lanes on built revision `7e10c1cc9` (`63746cf7b340358ac5ce609761ea3198ae3a62e24df52f62ed5be16893940021`). It used public stdio MCP and CLI, real artifacts and authentic exported Evidence; no model or fixture provider ran.
-
-| Lane        | Attempts | Scope seconds, all attempts | CPU seconds, all attempts | Max kernel peak MiB | CLI calls, including negatives |
-| ----------- | -------: | --------------------------: | ------------------------: | ------------------: | -----------------------------: |
-| native      |        1 |                      35.915 |                 34.674174 |              927.99 |                              0 |
-| javascript  |        3 |                      34.324 |                 33.094918 |              658.91 |                              8 |
-| managed     |        2 |                      37.341 |                 36.221694 |              694.65 |                              9 |
-| android     |        1 |                      20.208 |                 19.569397 |              696.40 |                              4 |
-| harmony-app |        1 |                      16.714 |                 15.950327 |              495.68 |                              4 |
-| harmony-hap |        1 |                      16.294 |                 15.886932 |              508.47 |                              4 |
-| apple       |        1 |                      25.453 |                 24.824482 |              642.90 |                              8 |
-| wasm        |        2 |                      22.648 |                 22.027649 |              791.67 |                              4 |
-| process     |        1 |                       9.056 |                  8.586552 |              472.58 |                              2 |
-
-Producer/export costs from the failed JS/managed harness attempts are included. Three harness assumptions and one actual SDK transport-capacity failure are retained individually. Every payload cleanup and kernel observation verified; no OOM or increased allowance.
-
-Fresh imported references match complete CLI inline and selected-bundle outputs where those command contracts support them. Small APP/process/correlation inputs also match admitted MCP inline. Larger MCP inline forms hit the unchanged 1024-element guard. Native and selected managed-member comparisons have no equivalent Evidence-input CLI form; process accepts two complete capture files, and artifact comparison uses explicit evidence-file selectors.
-
-The 27,823,016-byte WASM inline arguments exceeded the default 10,485,760-byte stdio frame buffer and closed the connection before application admission. The resumed attempt reused the same authentic bundle: fresh MCP references and both supported complete CLI forms agree. No WABT replay or limit increase.
-
-Process capture comparison and behavior aggregation preserve changed/unknown facts. Correlation with genuine native comparison Evidence remains unknown with one unresolved branch under an explicit noncausal hypothesis.
-
-These are scripted transport-task costs with uncontrolled caches, not a before/after benchmark or model-token measurement. Earlier WASM inspection/process capture costs are linked in the prior verification report. Later source-only diagnostic fixes have separate focused validation.
-
-The accompanying JSON retains all thirteen attempts, exact kernel counters,
-source/result identities and hashes, CLI arm receipts, failures and limits.
-These scripted costs do not add to the model-token table.
-
-## Review follow-up
-
-An additional local terra/high source-only review found that the refactored
-process CLI read later selected files before authenticating the first capture.
-The shared owner now exposes authenticated source facts and their comparison;
-CLI authenticates each source before reading the next, while MCP uses the same
-readers and comparator. Two public CLI regressions cover invalid left/right
-records with missing later files. The original real captures were compared
-again without target execution and retained the exact comparison Evidence ID.
-
-Greptile found a fixed-server WASM regression: caller-supplied complete inputs
-incorrectly required a recorder. Shared retention now explicitly recognizes
-caller-owned inputs. Provider-produced sources still require a recorder;
-available recorders, their rejections and cancellation sources remain honored.
-A fixture-backed public fixed-server MCP regression and ownership/cancellation
-checks cover that distinction. These follow-up regressions are not additional
-real-provider measurements. The related nine-file run passed 103 checks;
-subsequent schema cleanup and CLI checks passed ten more selected checks.
-Type, lint, Knip and architecture/module-boundary checks were repeated.
-
-The fourteen application-analysis attempts above are separate from source-only
-review; that CLI review did not report usable model-token counts. Its cleanup
-was verified, with 57.860 s task elapsed, 4.720926 s family CPU and 427,364,352
-peak bytes. Existing captured model measurements remain tied to their recorded
-runtime fingerprints, preceding these review corrections.
-
-The additional seven-file boundary run passed 161 checks after the CLI's JSON
-parser was corrected to keep public command names in malformed-input diagnostics.
-It includes 17 fixed-server cases for six JavaScript and three mobile consumers,
-direct inline analysis views, missing references, wrong source roles, summary
-retention and default input admission. These use complete authored fixtures;
-they do not substitute for the real-artifact matrix. The run included a runtime
-build and cost 154.106 s / 153.592029 CPU s / 1,884,516,352 peak bytes. Subsequent
-type, touched-file lint and module checks passed, with no OOM or cleanup gap.
-
-Native function and process workflows send malformed complete source records to
-the canonical Evidence owner after resource admission. Schema or identity failures return
-`evidence_integrity_mismatch` in both MCP schema profiles, including the original
-`relationship_coverage` diagnostics. Other workflows preserve their format-owner
-error projections. The directional-coverage regression still
-checks every malformed case and the advertised full schema. Invalid request
-envelopes and reference grammar remain request errors; no duplicate source parse
-was introduced solely to reproduce the former SDK error classification.
-
-A later review reported a possible null-source dereference in reconciliation.
-On `70db1e816`, the public request has no identity refinement; source authentication
-runs before identity-only validation. A public fixed-server MCP probe passed two
-valid controls and rejected 24 malformed source cases across full/compact profiles
-with structured `invalid_request` and accurate paths. Both complete schemas also
-rejected each of twelve cases without throwing. No provider ran. Cleanup was
-verified: 3.334 s elapsed, 3.155635 CPU s and 287,404,032 peak bytes, with no OOM.
-This authored-fixture probe disproves the reported path on that revision;
-it does not establish real passive-runtime behavior. No production change was
-needed for that finding. The accompanying JSON records its observations.
-
-CI later exposed the corresponding process-depth assertion against the old SDK
-error envelope. Its regression now checks the canonical integrity error while
-preserving the public left-source, `parameters` and exact nesting-limit diagnostic.
-A normal comparison must still succeed afterward and provider startup is forbidden.
-The iterative JSON depth guard still rejects before recursive cloning or hashing;
-no second source parser was added. Runtime code was unchanged. Six related MCP
-files passed 104 checks, including source identity, native/process diagnostics,
-investigation composition and session lifecycle: 64.384 s elapsed, 64.066692 CPU s
-and 1,476,808,704 peak bytes. Cleanup was verified with no OOM.
-
-A retained-closure acceptance assertion also assumed that a complete inline
-comparison must already exist in the ledger. The shared workflow intentionally
-uses that supplied record: a missing dependency is reported for inline input,
-while an unresolved selector reports the comparison itself. Both still require
-the full referenced closure. Importing the originating bundle restores both
-forms to complete, equal Evidence. Five relevant acceptance files passed 17
-checks, covering default-budget aggregation, artifact coverage, replay and public
-local contracts: 123.152 s elapsed, 121.276327 CPU s and 1,466,314,752 peak bytes.
-Cleanup was verified with no OOM; runtime code was unchanged.
-
-The HTTP admission-edge regression now checks the same source-owner semantics.
-An admitted array of 1,019 malformed carriers fails at its first source, while
-1,020 carriers exceed the unchanged 1,024-element envelope allowance. Responses
-were 703 and 824 bytes, respectively; both stayed below 4 KiB and the server kept
-serving. The shared resolver additionally preserves `input_path` on owner errors
-when absent. Original error identity, owner diagnostics and existing paths remain
-intact, with no second source parse. The rebuilt nine-file gate passed 75 checks,
-including all 41 ADB CLI cases, resolver, native references and HTTP/stdio admission:
-98.459 s elapsed, 98.133579 CPU s and 1,605,656,576 peak bytes; cleanup verified,
-no OOM.
-
-CI also terminated one unchanged ADB CLI child at its helper's existing 20-second
-deadline. Two isolated exact 17-extra CLI probes returned the expected argument
-validation failure in 1.970 s with a fresh Node compile cache and 1.170 s reusing
-it. Neither ran ADB or reached a device; the 20-second deadline was unchanged.
-Both local scopes cleaned up with no OOM. The rebuilt full ADB CLI file passed,
-including that case in 1.597 s. The CI delay was not reproduced; these observations
-do not establish baseline flakiness or a controlled before/after startup result.
-
-After the diagnostic change, the untouched genuine jq/Ghidra bundle was imported
-again into a fresh target-free stdio server. Call path, function comparison and
-native matching returned complete public values equal to their original matrix
-goldens, including IDs, provenance, coverage and unknowns. Seven calls included
-no producer, target opening or Ghidra execution. The built runtime fingerprint
-was `1bcdcd29df3b90f2cfa61aad29d647dbfb22176d0bca880c7a537507fdeab271`;
-source bundle and runtime stayed unchanged. The replay cost 5.543 s / 5.263196 CPU s
-/ 447,791,104 peak bytes, with verified cleanup and no OOM. This is an additional
-scripted replay, separate from the thirteen-attempt matrix and fourteen model
-attempts. Its full receipt and the timeout probes are included in JSON.
-
-## Regression and coverage limits
-
-The focused regression run passed 508 checks covering source integrity, exact
-IDs, mixed/optional/nested selections, default constraints, converted full and
-compact SDK schemas, source closure, caller choices, CLI bundle immutability,
-capacity admission and late cancellation/source retention. SDK boundary tests
-are kept in the MCP boundary project; pure declaration checks stay in contracts.
-
-Full-library lint exceeded the local early-stop limit even with one worker.
-The same selected 6,105 files were checked in sequential batches of 400;
-peak family memory was 741,650,432 bytes. Two new test grouping errors were
-corrected and those files rerun. Failed lint/driver attempts remain in local
-receipts. Process-driver path/ANSI oracle corrections reused the original
-authentic captures.
-
-No real Hopper, IDA, Windows capture, Android device, Harmony runtime, passive
-browser reconciliation or managed/native runtime equivalence is established
-by these tests. There is no controlled main-versus-candidate model cohort,
-no cold filesystem measurement and no claim that every provider facet was
-independently verified.

docs/verification/investigation-lifecycle.md

@@ -1,298 +0,0 @@
-# Investigation record lifetime verification
-
-Verified on Linux with Node v24.22.1 and local Codex CLI 0.165.0 for
-[#8347](https://github.com/morluto/rea/issues/8347). The final production revision is
-`40ec9fe79b221b7550bf6a652f55389ea0b7e54f`, including main
-`d54a4661da20382ad8456564a08569fdd24131c5`. Its runtime manifest SHA-256 is
-`f4e55abdc5cb9fc2a86efcec5c410f2b5bc3eb5a7109a8d5ab88f07f8511c48b`.
-Earlier measurements below identify their older revisions explicitly. Documentation
-was being updated during final qualification; production sources and runtime
-remained unchanged.
-
-The [MCP contract](../mcp-contracts.md) separates engine cleanup, investigation
-reset and explicit checkpointing. Automatic journaling remains tracked in
-[#4809](https://github.com/morluto/rea/issues/4809).
-
-## Response publication qualification
-
-The request-publication correction is pinned to
-`40ec9fe79b221b7550bf6a652f55389ea0b7e54f`. An MCP request now retains its
-originating session admission through handler cleanup and physical send
-settlement. Nested operations borrow that admission, avoiding reentry behind a
-queued reset. Cancellation before a suppressed send and during an already-started
-send have separate completion rules. Outgoing server requests cannot acknowledge
-an incoming tool response merely because their IDs coincide.
-
-All nine genuine saved-source workflows were repeated: 313 MCP calls and 19 CLI
-checks, 114.210 s guarded elapsed, 109.411889 s CPU and 1,055,035,392 B maximum
-family peak. Complete original public results and source identities matched
-through close, checkpoint refusal, reset and same/fresh-process recovery; all
-Unknown histories were preserved. No producer replay, source/runtime changes,
-OOM or unresolved owned cleanup occurred. These runs have uncontrolled OS caches
-and are not a paired timing comparison with the earlier cohorts below.
-
-A new local Codex CLI task requested `gpt-6.1-terra`/`high` with the scoped
-four-domain profile. It completed 25 MCP calls, including four expected
-missing-reference controls, with no producer replay. Usage was 232,677 input
-tokens including the 199,552 cached subset, 3,613 output tokens and 195 separately
-reported reasoning tokens; elapsed was 61.466 s, local CPU 11.031356 s and peak
-806,146,048 B. Requested aliases do not establish the server-resolved model
-identity, and remote model compute is unmeasured.
-
-An independent fresh stdio process authenticated that task's 21-record,
-three-revision checkpoint: 16,138,657 B, SHA-256
-`a4395246473397cdc9040cb643e3175fd6f8b24db40597f8b680f0e065643df5`.
-Nine calls reproduced all four complete original results and source records and
-reexported byte-identical bundle bytes. This took 6.353 s elapsed, 6.060161 s CPU
-and 592,621,568 B peak, with verified cleanup and no OOM.
-Independent full-result/source/history authentication and manual answer review
-supported the model's stated conclusions. No task or model retry was needed in
-this cohort; separate checker and report-aggregation CPU was not measured.
-
-The actual Ghidra healthy-engine control also passed on this runtime: 49 calls,
-51.115 s elapsed, 50.000976 s CPU and 1,124,110,336 B peak. The verifier-owned JVM
-PID/start identity/process group, public analysis run and MCP client were the same
-across reset. Two explicit `address_name` queries returned identical Evidence;
-no dossier, inventory or decompile producer was replayed. Full checkpoint/history
-recovery and owned cleanup passed, with no OOM. This observes retained-engine
-behavior rather than a before/after speedup.
-
-Across all three model cohorts, nine actual runs plus one prelaunch failure used
-2,771,744 input tokens including the 2,468,608 cached subset, 23,334 output tokens
-and 1,035 separately reported reasoning tokens. Guarded elapsed totals 480.694 s
-and local CPU 87.103671 s; maximum family peak is 922,148,864 B. All earlier
-failed/partial attempts remain included. These are execution costs, not a paired
-model-token savings claim.
-
-All nine controlled success/error publication cases passed. Reinstating only the
-old admission factory made both successful-publication cases fail at the original
-admission boundary; the corrected source was restored and all nine passed again.
-The final boundary run used 12.872 s elapsed, 12.647482 s CPU and 941,723,648 B
-peak. Existing lifecycle/deferred/shutdown tests passed 79/79; the full HTTP suite
-passed 74/74. These controlled seams establish ordering, separately from real
-application behavior.
-
-CI also exposed the 1500-file JavaScript timeout fixture's retention headroom.
-At a 512 MiB parent heap, the original timeout exceeded the 10 MiB wire budget;
-fallback authentication projected 771,325,184 B against 411,666,312 B available
-and correctly refused. The transport/timeout fixture now uses a finite 1536 MiB
-parent heap while retaining all 1500 files and every recovery/query assertion.
-Its worker remains at 128 MiB; the separate memory-pressure case retains its
-512 MiB parent. All three tests passed in 23.556 s elapsed, 22.989758 s CPU and
-1,064,308,736 B peak, including a public assertion that retained records fit the
-fixed allowance. No production limit was raised for this fixture.
-
-## Earlier review qualification
-
-Review corrections were qualified at clean
-`6d875b3ff73d40b365a713cf4ba69a10cca257b7`, with runtime manifest SHA-256
-`328f05dc2d7b114c33dc0406e488c3046a43e1c12187e15ad9263be65df7cbaa`.
-SDK error Evidence retention and reply publication now share session admission;
-reset retries the MCP artifact scope alongside process cleanup before saving or
-clearing. Controlled public MCP regressions cover both publication orderings,
-queued cancellation, terminal shutdown, ordinary export cleanup failure, mixed
-cleanup outcomes and scope reuse. Reinstating the former wiring made four of the
-five new regression cases fail; all five pass with the correction. Controlled
-waits also use bounded acknowledgements and release/join held work in `finally`.
-
-The nine genuine saved-source cases below were repeated against this runtime:
-**313 MCP calls and 19 CLI checks**, 118.510 s guarded elapsed, 114.859544 s CPU,
-and 1,065,390,080 B maximum kernel-family peak. Every complete original result,
-ID, source, coverage and Unknown revision chain matched through close, checkpoint
-collision refusal, reset, same-process import and fresh-process recovery. No
-producer or target open was replayed in this cohort. Input/checkpoint/runtime
-immutability and owned cleanup were verified, with no OOM. These normal workflows
-complement the controlled error/cleanup timing regressions; they do not reproduce
-those timing faults themselves.
-
-One further local Codex CLI task requested `gpt-6.1-terra`/`high` with the
-scoped four-family code-mode profile. Its 25 MCP calls included four expected
-missing-reference controls and no unexpected model errors or producer replay.
-Independent full-result/source/history authentication and answer review supported
-the answer within its stated scope; it did not claim to query every other
-Unknown. The run used 58.269 s elapsed, 9.837083 s local CPU and 885,448,704 B peak,
-with 239,931 input tokens including 215,168 cached, 3,721 output tokens and 277
-separately reported reasoning tokens.
-
-A real fresh stdio client restored that same new checkpoint: 21 records and
-three Unknown revisions in 16,138,749 B, SHA-256
-`760fc74951abc292a3ff2fe1771391ac0d4345416b2345dfa4e85cbb6ce96181`.
-Nine calls reproduced all four complete original results and source records,
-then reexported byte-identical bundle bytes. This took 5.443 s elapsed,
-5.253212 s CPU and 595,218,432 B peak, with verified cleanup and no OOM.
-Two external-checker failures were preserved and corrected against actual event
-ordinals and query filter/paging semantics; neither required model or backend
-replay. Separate checker CPU and remote model compute were not measured.
-
-Across those two earlier cohorts, eight actual model runs plus one prelaunch failure used
-2,539,067 input tokens including the 2,269,056 cached subset, 19,721 output tokens,
-and 840 separately reported reasoning tokens. Guarded elapsed totals 419.228 s
-and local CPU 76.072315 s; maximum family peak remains 922,148,864 B. Initial
-failed/partial attempts below remain included. This is execution accounting,
-not a paired model-token performance comparison.
-
-That runtime also repeated the actual Ghidra healthy-engine control:
-49 calls, 44.333 s elapsed, 43.348651 s CPU and 1,093,464,064 B peak. The same
-verifier-owned JVM PID/start identity/process group, public analysis run and MCP
-client survived reset; two `address_name` queries returned identical Evidence.
-Startup-inclusive and warm requests took 24,953.573 ms and 6.762 ms respectively,
-without dossier, inventory or decompile replay. These are startup/reuse
-observations rather than a PR before/after speedup. Full checkpoint/history
-recovery and owned cleanup passed, with no OOM.
-
-## Initial main-integration workflows
-
-Main was integrated in `4e20698b7b9883f659e445c059c011aa0e5de834`, with runtime
-manifest SHA-256
-`ee23cbaf0ecbf8d896fb5dc7a88317e2ab8eb77bd3a4467bf5793c3471ca9c7d`.
-
-Nine genuine saved-source cases covered eight target families:
-
-| Family     | Actual source          | Saved-source bundle SHA-256                                        |
-| ---------- | ---------------------- | ------------------------------------------------------------------ |
-| Native     | jq observations        | `0a3adad6ab39bfe29320e1f070a8e598382d2f17c4d6c19079bd6ff16dfe0937` |
-| JavaScript | agent-browser 0.27.0   | `66232b6eb01b3dbf435949a1cd94cb2532b7f989b91cdf952a105b3cee231bda` |
-| Managed    | NuGet CLI, SDK 8.0.427 | `11ac63842299c0ac641a320ec9b2a5161b454a8a322d57724fd5f2ffb2fddfa4` |
-| Android    | NewPipe 0.29.1         | `fa499d0464a40ddc2f5159c893d68b8f50aa8e6d2b0080de22f2f3e5fc326825` |
-| Harmony    | Shark 1.0.8 APP        | `3a526ab0113f80ada26ff5a0631fc95dac91485946f20584fc5a76f5ee8eb880` |
-| Harmony    | Shark inner HAP        | `3431c0a347f331c3effacf7984ecb890f3fef46d8b00b03b50980023b065cd4a` |
-| Apple      | Rectangle 2.0.4        | `8daa6286b28aadf5ba0d41038046805e5c69874eaa0bc5daf0e265360fcae79d` |
-| WASM       | tree-sitter-css        | `acb0cb6c3e0d520f83144e106e171c3ecebba70c5c0498bbb0113185a3e4bf95` |
-| Process    | Controlled jq captures | `55da0f130dc2265aae54261d49949471e5c929163c2b7314b42e95df3325b739` |
-
-Each case imported authenticated observations, composed exact retained references,
-closed without an active target, refused an existing checkpoint destination,
-saved and reset, checked missing references, and restored into the same process
-and a fresh public stdio MCP process. Complete original public results, source
-links, coverage and Evidence IDs matched throughout. Every case included an
-explicit analyst question with revisions 1→2; complete revision histories and
-mutation Evidence authenticated after recovery. Bundle hashes above identify
-the saved observations rather than release binaries. The actual jq target was
-`/usr/bin/jq`, SHA-256
-`90b1eef4498f31836342898fc6e97cfeb8a197c4366773a0fb120ae02a45ea52`.
-
-That cohort completed **313 MCP calls and 19 public CLI checks**, without
-source producer replay. Summed guarded elapsed was 119.445 s and CPU was
-115.040362 s; maximum kernel cgroup-family peak was 1,047,826,432 B. All pinned
-input/runtime hashes stayed unchanged, owned cleanup was verified, and no resource
-stop or OOM occurred.
-
-A separate actual Ghidra 12.1.4 control reset while its jq engine remained open.
-The same verifier-owned JVM PID/start identity/process group, reported analysis
-run and MCP client survived reset. Two identical `address_name` queries at
-`0x104500` returned the same Evidence. The first request including startup took
-21,023.963 ms; the post-reset request took 6.672 ms. This observes startup versus
-reuse, rather than a PR before/after speedup. No function dossiers or procedure
-inventories were regenerated. The complete close/checkpoint/import/fresh-process
-control used 49 calls, 39.351 s elapsed, 38.222523 s CPU and 1,094,340,608 B peak;
-reset acknowledged 15 records and three Unknown revisions with `retained_target`.
-
-Earlier actual-provider controls also passed Ghidra→Rectangle provider-family
-switching and Rectangle→NewPipe target switching, with reset retaining the healthy
-second target. Those pre-sync runs preserved their complete original results and
-histories; they are separate from the latest-runtime qualification above.
-
-## Equivalent completed-task measurements
-
-These pairs used exact baseline `60149282fcfc05ac32fbc94434c107710120da6f` and
-implementation `3c9fb7f44a4496d18d893beb903c5f2ba68c06b4`, before the later main
-integration. The baseline exported, closed and imported before reference
-composition; the candidate closed and reused references directly. Both returned
-the same complete original result for the same authentic inputs.
-
-| Saved source | MCP calls, before→after | Elapsed s   | CPU s             | Kernel-family peak B    |
-| ------------ | ----------------------- | ----------- | ----------------- | ----------------------- |
-| Native       | 9→7                     | 5.846→4.938 | 5.609106→4.760475 | 582,672,384→511,090,688 |
-| JavaScript   | 8→6                     | 3.529→3.333 | 3.371675→3.163932 | 394,170,368→387,428,352 |
-| WASM         | 7→5                     | 4.236→3.731 | 4.035871→3.520731 | 658,063,360→492,548,096 |
-
-Each row is one sequential pair in fresh isolated processes. OS caches were
-uncontrolled; builds and fingerprinting were measured separately. These samples
-establish two fewer necessary calls, rather than statistical speedups or model
-token savings.
-
-## Initial Codex tasks
-
-Local Codex requested `gpt-6.1-terra` with `high` reasoning. Native used the full
-advertised surface without an enabled-tool filter or exact-name guide, both
-before and after the latest main integration. JavaScript, packages and the mixed
-managed/WASM/process/Harmony task used explicit scoped diagnostic profiles. The
-mixed task used the existing experimental client code mode; its development
-warning was retained.
-
-All four task scopes passed independent canonical bundle/history authentication,
-complete original-result comparison and final-answer review. These conclusions
-were checked separately from process exit and token accounting. Native's final
-12 calls preserved the original comparison, acknowledged a 14-record/three-revision
-checkpoint, observed the expected missing-reference control, and restored both
-Unknown heads. The mixed model used 25 calls; a separate latest-runtime fresh
-stdio verifier used nine calls to restore its same 21-record/three-revision
-checkpoint, reproduce all four complete originals, and reexport byte-identical
-bundle bytes.
-
-The initial cohort table includes **all attempts**, partial runs and the native task repeated
-after main integration:
-
-| Task/profile                        | Input tokens (cached subset) | Output tokens | Elapsed s / CPU s   | Kernel-family peak B |
-| ----------------------------------- | ---------------------------- | ------------- | ------------------- | -------------------- |
-| Native, full discovery              | 841,133 (769,536)            | 4,326         | 101.845 / 18.383645 | 888,786,944          |
-| JavaScript, scoped                  | 531,546 (452,224)            | 3,421         | 88.236 / 14.456771  | 922,148,864          |
-| Rectangle→NewPipe, scoped           | 629,186 (567,424)            | 4,384         | 108.062 / 22.589319 | 878,800,896          |
-| Four-family mixed, scoped code mode | 297,271 (264,704)            | 3,869         | 62.816 / 10.805497  | 914,604,032          |
-
-Seven actual model runs plus one prelaunch failure consumed 2,299,136 input tokens
-including the 2,053,888 cached subset, and 16,000 output tokens. Input already
-includes cached input. Reported reasoning output was 563 tokens, recorded
-separately. Canonical verification costs are separate from client/model costs.
-The latest SDK catalog had 234 tools and 3,919,838 JSON bytes; those representation
-bytes are not model tokens. No paired baseline model cohort ran, so these counters
-do not establish causal whole-task token savings.
-
-Three failed or partial attempts were preserved:
-
-- Native's first attempt stopped before model/MCP launch because of a redundant
-  template-only harness argument. Its 0.718 s/0.473821 CPU s remains included.
-- JavaScript saved its six-record/two-revision checkpoint before the isolated
-  client denied `binary_session`. The harness approval was corrected; a new
-  process restored the same checkpoint and identical trace without another
-  producer or reset. Joint accounting includes 16 client attempts, 15 served
-  calls and the client denial.
-- The package model selected an unsupported generic view for a derived Apple
-  projection and stopped before checkpointing. Its continuation rehydrated
-  original authenticated saved inputs after matching current IDs and observed
-  summaries/projections, then used the correct projectors. Two inventory producers
-  ran once total; one additional NewPipe metadata reopen restored active state.
-  This qualifies explicit saved-source recovery. The first run's unsaved full
-  inventory body was not directly transported or checkpointed.
-
-## Resource and regression boundaries
-
-The genuine multi-domain/model workflows used `--max-old-space-size=512` for
-MCP/CLI Node children; retention had no quota override. The controlled timeout
-fixture's separate parent allowance is documented above. An earlier cumulative
-default-policy control admitted all nine genuine
-bundles: 34 records, 87,532,230 estimated representation bytes against its observed
-150,244,580-byte allowance. Exact duplicates did not grow committed state. This
-corpus did not reach default capacity; injected-policy regressions establish
-atomic refusal, metadata replacement accounting and budget release on reset.
-
-Local checks passed across 43 focused source/public-boundary files, 533 distinct
-tests using each file's latest passing run, and 93 Python tests. The main
-integration specifically reran eight lifecycle/recovery files with 61 passing
-tests, including retained candidate cleanup failure/recovery and healthy-client
-preservation. Typecheck, bounded lint, formatting, module/architecture guards,
-documentation and production reachability passed. Controlled providers and
-failure seams qualify cancellation, late work and cleanup orderings separately
-from actual-provider observations.
-
-Heavy tasks ran serially with one CPU, 4 GiB hard memory, 3 GiB early stop, zero
-swap and 192 tasks maximum. Kernel CPU and memory.peak were observed at payload
-exit while a cgroup observer remained alive. They include drivers/helpers and the
-observer, exclude preflight outside the guard, and are distinct from process RSS
-and retained-representation estimates. Failed model attempts, partial results,
-assessments and raw receipts remain local; binaries and authentication data are
-excluded from the repository.
-
-Explicit acknowledged checkpoints qualify cross-process recovery. Uncheckpointed
-process loss, automatic journaling, parent-directory power-loss recovery,
-Windows, IDA/Hopper and a second actual deep engine were not qualified here.

docs/wasm-artifacts.md

@@ -83,8 +83,7 @@ valid: partial results state whether WABT validation is unknown, rejected the
 module, or succeeded before a later inspection failure.
 CLI errors include this partial Evidence inline. MCP errors can return its
 `retained-evidence` reference in `details.partial_observation`; use
-`get_evidence_bundle` with `detail: "records"` and that `evidence_id` filter to
-retrieve the matching record.
+`get_evidence_bundle` with `detail: "complete"` to retrieve the matching record.
 
 Core validation remains authoritative when an optional custom section cannot
 be interpreted. WABT warning output is preserved in `custom_section_warnings`;
@@ -190,13 +189,11 @@ typed interfaces.
 
 `compare_wasm_interfaces` accepts two complete `inspect_wasm_artifact` Evidence
 records, or exact retained references in the current MCP session, and required
-`scope: "imports" | "exports" | "both"`. It uses producer-owned typed facts
-without rereading the artifact and needs no active WABT toolchain. CLI accepts
-portable inline Evidence in one JSON document, or
-resolves the same retained-reference inputs from an explicit saved bundle:
+`scope: "imports" | "exports" | "both"`. It reads no files and needs no active
+WABT toolchain. CLI uses portable inline Evidence in one JSON document:
 
 ```bash
-rea compare-wasm-interfaces comparison-input.json --evidence-bundle /absolute/path/evidence.json --json
+rea compare-wasm-interfaces comparison-input.json --json
 ```
 
 ```json
@@ -207,10 +204,8 @@ rea compare-wasm-interfaces comparison-input.json --evidence-bundle /absolute/pa
 }
 ```
 
-Omit `--evidence-bundle` when the CLI input contains complete inline records.
-Resolve summary delivery to its complete `normalized_result.parent_evidence_id`
-before comparing. References preserve that exact source identity and coverage;
-the bundle supplies no facts absent from the selected record.
+The references above are MCP-only; put complete Evidence objects in the CLI
+input. Resolve summary delivery to its retained complete parent before comparing.
 Results retain both input Evidence IDs, artifact paths/digests/lengths and every
 selected occurrence. Unique names are added, removed, changed or unchanged;
 duplicate names and unsupported signatures are unknown. Incomplete or historical

docs/web-network-captures.md

@@ -97,13 +97,9 @@ it does not invent an empty string or body bytes.
 The observed Playwright 1.58.2 profile can report a bracketed IPv6
 `serverIPAddress`, forwarded from Chromium's `remoteIPAddress` through
 [Playwright's HAR tracer](https://github.com/microsoft/playwright/blob/v1.58.2/packages/playwright-core/src/server/har/harTracer.ts).
-Chromium DevTools exports (declared as `WebInspector` `537.36`, the frozen
-AppleWebKit version in Chromium's user agent) report the same bracketed form:
-[its HAR writer](https://github.com/ChromeDevTools/devtools-frontend/blob/63739e8ec45ca01b9e4be9b8b05946acdadd8f1f/front_end/models/har/Log.ts)
-strips the port but not the brackets.
 REA preserves the original spelling in reported Evidence and removes brackets
-only from its validation copy, only for these declared producers and a valid
-IPv6 literal. Invalid addresses, bracketed IPv4, ports and zone identifiers remain
+only from its validation copy, only for this declared producer and a valid IPv6
+literal. Invalid addresses, bracketed IPv4, ports and zone identifiers remain
 validation failures. Producer declarations do not authenticate origin.
 
 Native mitmproxy decoding requires a caller-supplied **mitmdump 12.2.3 on

docs/web-runtime.md

@@ -22,7 +22,7 @@ Results retain:
 - Main-document script inventory, exact session script IDs, resource start coordinates, sourceURL/source-map declarations, producer hash and independently computed UTF-8 text digest.
 - Armed-window requests from the selected main frame and selected origins, complete reported initiator objects (including stack hierarchy/descriptions), derived callsites, exact script-ID associations and unresolved async parent IDs. Source association does not establish UI causality. Callsite and listener `line_number`/`column_number` values are CDP's zero-based lines and UTF-16 columns in the resource named by `url`. With a `script_id`, that is the script's enclosing resource: the script file for an external script, or the HTML document for an inline script. `resource_start` is where the script text starts in that resource. A callsite with an empty `script_id` comes from the request's reported initiator rather than a script call frame, such as markup that the parser read in a document or a module import in a script file. It still locates a position in `url`, but has no session-script association, so it cannot be joined to captured source or `resource_start`. `trace_web_source_location` takes one-based, script-relative lines and zero-based UTF-16 columns.
 
-For an external script, where `url` is the script file, use `line = line_number + 1` and keep `column = column_number`; this also applies to an empty-`script_id` initiator position in a script file. For an inline script, which requires a `script_id` and its `resource_start`, use `line = line_number - resource_start.line_number + 1`. Subtract `resource_start.column_number` from `column_number` only when `line_number === resource_start.line_number`; keep the reported column on later lines. Columns remain zero-based. This conversion requires known source-start and column coordinates; preserve unavailable coordinates as unknown. Chrome reports a negative start column for some inline scripts, such as one in a helper frame, and positions on that script's first line include it. REA keeps those columns as reported rather than failing the observation; a negative column does not locate a column in `url`, but the subtraction above still gives the script-relative column.
+For an external script, where `url` is the script file, use `line = line_number + 1` and keep `column = column_number`; this also applies to an empty-`script_id` initiator position in a script file. For an inline script, which requires a `script_id` and its `resource_start`, use `line = line_number - resource_start.line_number + 1`. Subtract `resource_start.column_number` from `column_number` only when `line_number === resource_start.line_number`; keep the reported column on later lines. Columns remain zero-based. This conversion requires known source-start and column coordinates; preserve unavailable coordinates as unknown.
 
 The coverage counter interval starts at backend acceptance before the armed receipt and ends at the resetting sample after the local timer. Counts may include execution during these command intervals; request events are restricted to the locally armed window. The result retains both backend timestamps and the distinct local clock.
 

docs/windows-ghidra-p0.md

@@ -87,8 +87,7 @@ example under Smart App Control or an App Control policy, reports failure stage
 invocation or invalid inspection uses `runtime_unavailable` and doctor
 classification `runtime_failure`; it does not
 mean Windows x64 itself is unsupported. Provider diagnostics retain the failure
-stage under `windows_native_failure`; the availability's `remediation` carries
-the corresponding repair.
+stage under `windows_native_failure`, together with the corresponding remediation.
 Self-test failures preserve the native operation and OS error text. Check the
 process's writable local NTFS temporary directory and the reported filesystem,
 DACL, Job Object or cleanup constraint, then rerun doctor after resolving it.

licenses/README.md

@@ -9,7 +9,6 @@ upstream texts; they do not change [REA's MIT license](../LICENSE).
 | `npm-dependencies.txt`                                 | Every package path in the root lockfile, with its exact version, declared license, scope, download URL, and integrity. Includes development and optional platform entries.                                                                                                                |
 | `npm-runtime-notices.txt`                              | Original license, copyright, and NOTICE texts collected from integrity-verified locked runtime npm archives across all platforms; also the license of Rolldown's generated runtime helpers. The archive manifest's name and version are checked.                                          |
 | `protobuf-es-v2.16.0-LICENSE.txt`                      | Original Apache license omitted from the protobuf-es npm archive, preserved from its v2.16.0 source commit. Its embedded Google BSD notice is retained in `npm-runtime-notices.txt`.                                                                                                      |
-| `microsoft-uf2-MIT.txt`                                | Unchanged `LICENSE.txt` from microsoft/uf2 revision `cf3bd7f9c274b949528f8cd6a19eef2502a687d2`, for the UF2 family names copied from its `utils/uf2families.json`.                                                                                                                        |
 | `nativeaot-parser-MIT.txt`                             | Original Washi notice for derived NativeAOT parser code; source revision is recorded in the parser and the root notices.                                                                                                                                                                  |
 | `dotnet-runtime-MIT.txt`                               | Original .NET Foundation MIT text from the NativeAOT reference revision `a3b2d40328be0be3f8dd43f0e5cc925b8827b044`.                                                                                                                                                                       |
 | `ghidra-12.1.4-{LICENSE,NOTICE,DISCLAIMER}.txt`        | Unchanged top-level documents from `Ghidra_12.1.4_build`. Ghidra is not bundled; these reference copies do not replace its component and GPL support-program notices. The US-government-specific disclaimer applies to Ghidra, not to REA.                                                |

licenses/microsoft-uf2-MIT.txt

@@ -1,25 +0,0 @@
-Microsoft UF2
-
-The MIT License (MIT)
-
-Copyright (c) Microsoft Corporation
-
-All rights reserved.
-
-Permission is hereby granted, free of charge, to any person obtaining a copy
-of this software and associated documentation files (the "Software"), to deal
-in the Software without restriction, including without limitation the rights
-to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom the Software is
-furnished to do so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in all
-copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
-SOFTWARE.

licenses/upstream-sources.json

@@ -78,10 +78,5 @@
     "file": "licenses/pefile-2024.8.26-LICENSE.txt",
     "source": "https://raw.githubusercontent.com/erocarrera/pefile/4b3b1e2e568a88d4f1897d694d684f23d9e270c4/LICENSE",
     "sha256": "b44409c067c6da52bfb54bb6624fb11a7b52157c3a13ae1400232f8196e86ad3"
-  },
-  {
-    "file": "licenses/microsoft-uf2-MIT.txt",
-    "source": "https://raw.githubusercontent.com/microsoft/uf2/cf3bd7f9c274b949528f8cd6a19eef2502a687d2/LICENSE.txt",
-    "sha256": "c581accf1e5449482b70ac5fcdfb171599317ccff559cf0794d771671486f800"
   }
 ]

package.json

@@ -65,7 +65,6 @@
     "bridge/ghidra/ReaGhidraAnalysisOptions.java",
     "bridge/ghidra/ReaGhidraNoReturnFix.java",
     "bridge/ghidra/ReaGhidraMipsSoftFloat.java",
-    "bridge/ghidra/ReaGhidraRiscvCallingConvention.java",
     "bridge/ghidra/ReaGhidraPrepareRaw.java",
     "bridge/ghidra/ReaGhidraPrepareDol.java",
     "bridge/android/ReaJadxBridge.java",
@@ -239,11 +238,9 @@
     "verify:javascript:retained-facts": "npm run build:cached && node scripts/verify/javascript/retained-facts.mjs",
     "verify:application-workflows": "npm run build:cached && node scripts/verify/javascript/application-workflows.mjs",
     "verify:managed": "npm run build:cached && node scripts/verify/managed/conformance.mjs",
-    "verify:uf2": "npm run build:cached && node scripts/verify/firmware/uf2-esptool.mjs",
     "verify:firmware": "npm run build:cached && node scripts/verify/firmware/analysis.mjs",
     "verify:devicetree": "npm run build:cached && node scripts/verify/firmware/devicetree.mjs",
     "verify:esp-images": "npm run build:cached && node scripts/verify/firmware/esp-image.mjs",
-    "verify:esp-flash": "npm run build:cached && node scripts/verify/firmware/esp-flash.mjs",
     "fixtures:firmware": "node scripts/fixtures/firmware/generate.mjs",
     "verify:android": "npm run build:cached && node scripts/verify/android/analysis.mjs",
     "verify:jeb": "npm run build:cached && node scripts/verify-jeb.mjs",
@@ -291,7 +288,7 @@
     "verify:native-ui:permissions": "npm run build:cached && node scripts/verify-native-ui.mjs --allow-permission-denial",
     "test:focused": "node scripts/run-development-tests.mjs focused",
     "test:sqlite": "npm run test:prepare && npm run test:sqlite:run",
-    "test:sqlite:run": "node scripts/run-exact-tests.mjs run tests/acceptance/sqliteDatabaseCli.test.ts tests/boundary/mcp/serverLifecycleMcp.test.ts && vitest run src/application/sqlite/ tests/boundary/sqlite/",
+    "test:sqlite:run": "vitest run src/application/sqlite/ tests/boundary/sqlite/ tests/acceptance/sqliteDatabaseCli.test.ts tests/boundary/mcp/serverLifecycleMcp.test.ts",
     "build:windows-native": "node scripts/build-windows-native.mjs",
     "verify:windows-native:artifact": "node scripts/verify-windows-native-artifact.mjs",
     "prepublishOnly": "npm run verify:windows-native:artifact",

patches/release-please+17.3.0.patch

@@ -81,51 +81,6 @@
                  // In this case, there is no squashed merge commit. This could be a simple
                  // merge commit, a rebase merge commit, or a direct commit to the branch.
                  // Fallback to fetching the list of commits from the REST API. In the future
-@@ -1154,15 +1154,40 @@
-      * @returns {string} HTML URL of the new file
-      */
-     async createFileOnNewBranch(filename, contents, newBranchName, baseBranchName) {
--        // create or update new branch to match base branch
--        await this.forkBranch(newBranchName, baseBranchName);
--        // use the single file upload API
-+        // Preserve existing notes until the replacement file is committed.
-+        // A failed write must not leave an open proposal pointing at a missing file.
-+        if (!(await this.getBranchSha(newBranchName))) {
-+            const baseSha = await this.getBranchSha(baseBranchName);
-+            if (!baseSha) {
-+                throw new Error(`Unable to find base branch: ${baseBranchName}`);
-+            }
-+            await this.createNewBranch(newBranchName, baseSha);
-+        }
-+        let existingSha;
-+        try {
-+            const { data } = await this.octokit.repos.getContent({
-+                owner: this.repository.owner,
-+                repo: this.repository.repo,
-+                path: filename,
-+                ref: newBranchName,
-+            });
-+            if (Array.isArray(data) || data.type !== 'file' || !data.sha) {
-+                throw new Error(`Expected a file at ${filename} on branch: ${newBranchName}`);
-+            }
-+            existingSha = data.sha;
-+        }
-+        catch (error) {
-+            if (!(error && error.status === 404)) {
-+                throw error;
-+            }
-+        }
-         const { data: { content }, } = await this.octokit.repos.createOrUpdateFileContents({
-             owner: this.repository.owner,
-             repo: this.repository.repo,
-             path: filename,
-             // contents need to be base64 encoded
--            content: Buffer.from(contents, 'binary').toString('base64'),
-+            content: Buffer.from(contents, 'utf8').toString('base64'),
-+            ...(existingSha ? { sha: existingSha } : {}),
-             message: 'Saving release notes',
-             branch: newBranchName,
-         });
 --- a/build/src/github.d.ts
 +++ b/build/src/github.d.ts
 @@ -47,6 +47,8 @@