fix(native): mark Objective-C declarations partial when the budget cuts their methods

inspect-native-dispatch-metadata returned protocols, classes and categories
with decode status "decoded" and a short or empty method list when the
max_records budget stopped inside that list, which made a truncated list
indistinguishable from a genuinely empty one. Each method-list reader now
reports whether the budget stopped it, and the declaring record reports
partial / method_list_record_budget_exhausted.

Fixes #5543

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

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

@@ -2,7 +2,7 @@
 name: reverse-engineer-anything
 description: Reverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.
 metadata:
-  version: "44"
+  version: "43"
 ---
 
 # REA
@@ -30,8 +30,6 @@ unavailable, read [connection and recovery](references/connection-and-recovery.m
 Diagnose the observed blocker, continue useful supported work, and resume the
 original task after repair. Client approval, shell PATH, registration and engine
 availability have different remedies; avoid repeating setup for all of them.
-If the host times out without a REA result, do not repeat the unchanged call or
-assume work stopped. Read the recovery guide's deadline distinction before retrying.
 
 1. Diagnose without changing REA or client configuration. `npx` may download
    the package and write to npm's cache. For Codex, run
@@ -91,19 +89,9 @@ explicit path or endpoint and do not need it.
 
 - ASAR or extracted JavaScript/Electron tree:
   `analyze_javascript_application`.
-- Archive/package member inventory (ZIP/APK/IPA/MSIX/AppX, DMG, or a PyInstaller
-  executable): `open_binary` with the supplied local path; use `inspect_artifact`
-  when its graph and findings help answer the question. A PyInstaller CArchive
-  is the application layer; the bootloader is only the native prefix. Start with
-  `detail: "summary"` for large inventories, then use retained inventory views
-  for selected member fields/pages. A complete small inventory can cost less
-  than extra calls and schemas. Runtime options are metadata, not files.
-  Compact delivery still inventories and hashes members. See the
-  [Python packaged applications guide](https://github.com/morluto/rea/blob/main/docs/python-packaged-applications.md).
-- Apple app plist, Interface Builder, asset catalog, or keyed archive resources:
-  `open_bundle_resources`, then the selected resource tool. This does not
-  require `CFBundleExecutable` or a deep provider. Resource sessions have no
-  executable digest or binary snapshot; use `open_binary` for native code.
+- Archive/package member inventory (ZIP/APK/IPA/MSIX/AppX or DMG):
+  `open_binary` with the supplied local path; use `inspect_artifact` when its
+  graph and findings help answer the question.
 - Android APK code, classes, methods, or incoming references:
   `inspect_android_package`, then focused Android tools when advertised.
   Archive member inventory still uses the archive route above.
@@ -167,9 +155,7 @@ explicit path or endpoint and do not need it.
   ambiguity. No implicit fetch or target execution; WAT is not original source.
   See the [WASM guide](https://github.com/morluto/rea/blob/main/docs/wasm-artifacts.md).
 - Explicit local EVM bytecode carrier: `inspect_evm_interface` with caller-selected
-  `raw` or `hex` encoding. The owned worker deadline is `timeout_ms` (default
-  30000 ms, range 1..2147483647, next call). It does not raise the fixed byte,
-  address-space, or CPU allowances. Preserve carrier/decoded digests and treat selectors,
+  `raw` or `hex` encoding. Preserve carrier/decoded digests and treat selectors,
   argument strings and mutability as inferred candidates; this performs no chain
   lookup or target execution. For the complete inferred interface without hex or
   duplicate stdout, discover support and select `detail: "summary"`; complete
@@ -183,17 +169,6 @@ explicit path or endpoint and do not need it.
   absent metadata does not prove a binary is not Go, and unparsed text records
   remain explicit. See the
   [Go binary guide](https://github.com/morluto/rea/blob/main/docs/go-binaries.md).
-- Embedded CUDA/HIP code objects: `inspect_gpu_code_objects`; inventory targets
-  first, then decode selected payloads and query retained GPU Evidence.
-- Bundled GGUF or safetensors model declarations: `inspect_model_artifact`
-  with the explicit local file. Default header hashing leaves full-file identity
-  unknown; `hash: "full"` additionally reads all weights for SHA-256. MCP returns
-  retained summaries; optional `view` selects one page in the initial call. Use
-  `inspect_analysis_view` kind `model-artifact` for
-  batched metadata keys, tensor names or type totals, selected fields and pages.
-  Preserve header-scoped indices and array preview omissions; do not infer model
-  behavior from declared architecture or tensor types. See the
-  [model file guide](https://github.com/morluto/rea/blob/main/docs/model-artifacts.md).
 - Unity IL2CPP names, member owners and string literals from `global-metadata.dat`:
   `inspect_il2cpp_metadata` with the explicit local file; MCP defaults to compact
   counts. Query sections, images, types, methods, fields, properties, events,
@@ -211,21 +186,8 @@ explicit path or endpoint and do not need it.
   package order, dependency indices, and the section file range. A missing
   `.dep-v0` section is null metadata, not proof the binary has no dependencies.
   A rustc commit hash is an inference from a read-only `/rustc/<40-hex>/` path.
-  For selected crates, use `view: {collection: "packages", names: [...],
-  fields: ["name", "version", "source"]}` on the first call; explicitly include
-  `dependencies` for direct index references. Use `detail: "summary"` for counts
-  and ranges, or retained `inspect_analysis_view` Rust package/edge pages for
-  subsequent filters. Keep the complete parent Evidence accessible; CLI compact
-  delivery requires `--evidence_output`.
   See the
   [Rust binary guide](https://github.com/morluto/rea/blob/main/docs/rust-binaries.md).
-- PE Authenticode certificate table: `inspect_pe_certificates` with the explicit
-  local PE32/PE32+ file. This built-in target-free inspection requires no
-  Windows SDK. Preserve WIN_CERTIFICATE ranges, types, payload SHA-256, and
-  PKCS#7 signer/X.509 identity fields. A missing security directory is observed
-  absence of that table, not proof the image is unsigned in every catalog sense.
-  Signatures are not verified. See the
-  [PE certificate guide](https://github.com/morluto/rea/blob/main/docs/pe-certificates.md).
 
 - Explicit local SQLite database snapshot: `inspect_sqlite_database`. Inspect
   with Node.js 24.x >=24.15 or 26+ providing native SQLite limits. Read schema

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

@@ -25,9 +25,8 @@ stdio. A full JDK, including `jdk.compiler`, is required on every host; Windows
 `JAVA_HOME` selects `bin\java.exe`. Consult the Android guide for actual host
 verification coverage. Calls use one worker and provider deadlines; optional
 `REA_JADX_HEAP_MIB` selects the JVM heap and `REA_JADX_OPERATION_TIMEOUT_MS`
-the per-operation deadline (integer milliseconds from 1 to 2147483647, default
-120000; a change applies on the next process start; the MCP client's tool
-timeout must also allow it). The APK is never launched,
+the per-operation deadline (default 120000 ms; the MCP client's tool timeout
+must also allow it). The APK is never launched,
 and no emulator is required.
 
 Manifest entries and decompiled text are static observations, not execution or

.agents/skills/reverse-engineer-anything/references/connection-and-recovery.md

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

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

@@ -94,9 +94,3 @@ extract the data those reads observed instead: entity types and identity
 fields, entities with recorded values, documents, and per-tool render plans
 checked against the recordings. The state comes only from reads before the
 first related write; types, identity and list membership are inferences.
-`rea environment-serve manifest.json --evidence capture.json` derives that
-state at startup, answers read tools from it and serves `data/reset`,
-`data/add` and `data/get` on `/agentenv`; write tools are not served. It
-replays the capture instead with `--replay-only` or when the state is
-unavailable (not derivable, or a catalog over the discovery budget), and its
-stopped document's `state` says which applied.

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

@@ -18,15 +18,9 @@ only selected files. The result and summary record `source_selection`; files
 outside scope and their relationships remain unknown, so partial application
 coverage does not mean the selected source failed. Use repeated `--source-path`
 on either static application CLI route. Omit the selection when the question
-requires complete application analysis; `source_paths: []` is invalid, not an
-unfiltered request. `detail: "summary"` reduces delivery
+requires complete application analysis. `detail: "summary"` reduces delivery
 and does not by itself reduce analysis work.
 
-ASAR header/index admission defaults to 16 MiB / 16777216 bytes;
-`REA_ASAR_MAX_HEADER_BYTES` (at most 256 MiB, set where REA starts) changes it.
-`source_paths`, `detail`, and `max_heap_mb` do not bypass or raise it. Or
-analyze an extracted directory.
-
 Exact `#alias` specifiers resolve through the importer's
 enclosing package `imports` map to package-local files; nested `node_modules`
 packages use their own map. Wildcard, recursive, and external-package import
@@ -41,9 +35,7 @@ the complete application Evidence inline when it fits.
 When the connected schema advertises `max_heap_mb` and `analysis_timeout_ms`,
 these select the isolated source analyzer's old-space heap and per-source
 deadline. Defaults are 1024 MiB and 300000 ms. They do not change the MCP
-process heap or the client's tool deadline. For a host timeout without REA
-output, use the [deadline recovery guide](connection-and-recovery.md#distinguish-client-and-server-deadlines)
-instead of raising the server budget. A Bun-hosted REA does not enforce the heap choice; on Windows it
+process heap. A Bun-hosted REA does not enforce the heap choice; on Windows it
 instead limits the analyzer's committed memory to that choice plus a 512 MiB
 runtime reserve.
 Resource-limited analyses preserve completed static facts and

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

@@ -11,22 +11,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.
 
-## Apple app resources
-
-Use `open_bundle_resources` with the selected app path, then `inspect_plist`,
-`decode_interface_builder`, `inspect_asset_catalog`, or `inspect_keyed_archive`.
-The resource session reads the app without resolving `CFBundleExecutable` or
-starting a deep provider. Preserve `resource_root` provenance, per-resource
-hashes where reported, and null executable identity; a directory path is not
-an executable digest. Export retained Evidence before closing or switching
-roots. Binary analysis snapshots do not apply. Use `open_binary` to switch to
-executable analysis, and `close_binary` to release either session kind.
-
-The four matching CLI commands accept the app path directly. For an archive
-inside the app, use `inspect-keyed-archive APP_PATH RELATIVE_ARCHIVE_PATH`.
-Host requirements for plist and compiled asset/Interface Builder tooling still
-apply; a resource-only session does not establish provider availability.
-
 ## Desktop installation directories
 
 When an installation directory is supplied and its runtime is unknown, use
@@ -45,8 +29,7 @@ See [desktop installations](https://github.com/morluto/rea/blob/main/docs/deskto
 
 ## Go build metadata
 
-Use `inspect_go_binary` for an explicit local ELF, PE or Mach-O (universal
-files need `architecture`) when the
+Use `inspect_go_binary` for an explicit local ELF, PE or thin Mach-O when the
 question concerns the embedded compiler version, module/dependency versions,
 local replacements or build settings. No `open_binary`, Go installation or
 target execution is required. The CLI equivalent is `inspect-go-binary PATH`.
@@ -55,16 +38,6 @@ unparsed module-text line. A missing record is an unknown, not proof of a
 non-Go binary; observed metadata does not authenticate its claims. Function,
 source and type recovery remain a separate native-analysis question.
 
-## Model files
-
-Use `inspect_model_artifact` (`inspect-model-artifact PATH`) for local GGUF v2/v3
-and safetensors declarations without a model runtime. Header-only mode does not
-read weights or establish full-file identity. `hash: "full"` explicitly streams
-all bytes. Retained `model-artifact` views page `metadata`, `tensors` and derived
-`types`, with exact batch filters and selected fields. Arrays retain typed counts
-and eight-element previews; omitted values, unknown types and runtime behavior
-stay explicit. See [model files](https://github.com/morluto/rea/blob/main/docs/model-artifacts.md).
-
 ## IL2CPP metadata
 
 Use `inspect_il2cpp_metadata` for an explicit local Unity `global-metadata.dat`
@@ -85,8 +58,7 @@ See [IL2CPP metadata](https://github.com/morluto/rea/blob/main/docs/il2cpp-metad
 
 ## Rust dependency metadata
 
-Use `inspect_rust_binary` for an explicit local ELF, PE, or Mach-O (universal
-files need `architecture`) when
+Use `inspect_rust_binary` for an explicit local ELF, PE, or thin Mach-O when
 the question concerns the cargo-auditable crate list embedded in `.dep-v0`
 (Mach-O: `__DATA,.dep-v0`). No `open_binary`, Rust installation, or target
 execution is required. The CLI equivalent is `inspect-rust-binary PATH`.
@@ -96,19 +68,6 @@ dependencies. An omitted package kind stays null. A rustc commit hash is
 inferred from a read-only `/rustc/<40-hex>/` path and does not by itself
 identify the compiler. See [Rust binaries](https://github.com/morluto/rea/blob/main/docs/rust-binaries.md).
 
-## PE Authenticode certificate tables
-
-Use `inspect_pe_certificates` for an explicit local PE32/PE32+ image when the
-question concerns the Authenticode certificate table, WIN_CERTIFICATE types, or
-embedded PKCS#7 signer and X.509 identity fields. No `open_binary`, Windows SDK,
-or target execution is required. The CLI equivalent is
-`inspect-pe-certificates PATH`. Preserve artifact SHA-256, table file ranges,
-payload hashes, and original validity-time spellings. A missing
-`IMAGE_DIRECTORY_ENTRY_SECURITY` directory is observed absence of that table,
-not proof the image is unsigned in every catalog or overlay sense. Signatures,
-chains, timestamps, and Authenticode digest coverage remain unobserved. See
-[PE Authenticode certificate tables](https://github.com/morluto/rea/blob/main/docs/pe-certificates.md).
-
 ## SQLite snapshots
 
 Use `inspect_sqlite_database` with an explicit local database snapshot for its
@@ -360,8 +319,8 @@ every executable in the bundle. It also lists missing or weak loads and earlier
 `architecture`. System paths stay undetermined because the dyld shared cache
 provides them.
 
-Use `extract_artifact` when materialized files from a supported format are needed.
-It extracts the active target and accepts optional `integrity_policy`; see the [MCP contracts](https://github.com/morluto/rea/blob/main/docs/mcp-contracts.md).
+Use `extract_artifact` when materialized files are needed. It extracts the active
+target and accepts optional `integrity_policy`; see the [MCP contracts](https://github.com/morluto/rea/blob/main/docs/mcp-contracts.md).
 It materializes all regular files into a fresh temporary directory chosen by
 REA. Symlinks and encrypted entries are inventory facts, not extractable files.
 The result reports the materialized directory; callers do not choose the
@@ -370,11 +329,8 @@ destination. No separate permission grant is needed.
 Native DMG traversal automatically uses a read-only mount on supported macOS
 hosts, with an owned temporary mount directory and cleanup. It needs no approval
 flag. Unsupported hosts or mount failures remain explicit limitations; do not
-claim child inventory when only root identity is available. DMG extraction is
-unavailable through `extract_artifact`. To access DMG files on macOS, create a
-read-only mount with your own tools, select files from that mount for analysis,
-and detach the mount you created when finished. REA's inspection mount is
-temporary, not a retained export of the image's contents.
+claim child inventory when only root identity is available. Extraction is a
+separate filesystem-writing operation.
 
 For headerless DOS COM, explicitly open with `format: "dos-com"` (CLI
 `--target-format dos-com`). Inspect the load image before trusting function

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

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

.github/workflows/cache-retention.yml

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

.github/workflows/ci.yml

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

.github/workflows/mutation.yml

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

.github/workflows/real-agentenv.yml

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

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

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

.github/workflows/real-browser.yml

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

.github/workflows/real-cutter.yml

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

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

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

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

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

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

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

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

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

.github/workflows/real-hopper.yml

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

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

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

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

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

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

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

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

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

.github/workflows/real-termux.yml

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

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

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

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

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

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

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

.github/workflows/release.yml

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

README.md

@@ -90,12 +90,6 @@ Setup supports Claude Code, Codex, Cursor, Gemini CLI, Grok Build and
 [installation and setup](docs/installation.md) for provider configuration and
 manual MCP registration.
 
-MCP uses compact input schemas by default to reduce context overhead. Set
-`REA_MCP_INPUT_SCHEMA_PROFILE=full` in your MCP registration when you need the
-complete advertised field guidance and nested validation details. Both profiles
-keep the full tool set and canonical server validation. See
-"Compact input schema profile" in the MCP contracts guide.
-
 ### Ask your agent
 
 ```text
@@ -180,38 +174,34 @@ CLI commands use the same workflows.
 REA requires Node.js 22.x (>=22.19), 24.x (>=24.11), or 26+, plus npm.
 Additional tools and host support depend on the target:
 
-| Target                  | What REA returns                                                                                  | Requirements and guide                                                                                                                |
-| ----------------------- | ------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------- |
-| Desktop installations   | Runtime candidates, supporting files, component markers and next probes                           | Built-in bounded directory/header inspection; [desktop applications](docs/desktop-applications.md)                                    |
-| Native binaries         | Pseudocode, assembly, strings, symbols, calls and references                                      | Hopper, Ghidra or IDA; [native analysis](docs/native-investigation.md)                                                                |
-| Offline ELF layout      | Sections, segments, original symbols/relocations and static mitigation candidates                 | Caller-supplied pwntools on Linux x64; [binary diagnostics](docs/binary-diagnostics.md)                                               |
-| Go binaries             | Embedded compiler version, modules, replacements and build settings                               | Built-in static ELF/PE/thin Mach-O inspection; no Go installation required                                                            |
-| GPU code objects        | CUDA/HIP targets, selected kernel parameters and resources, retained PTX text                     | Built-in static ELF/PE/fatbin/CUBIN/PTX inspection; [GPU code objects](docs/gpu-code-objects.md)                                      |
-| Model artifacts         | GGUF / safetensors metadata, tensor declarations and derived totals                               | Built-in header inspection; optional full-file hash; [model files](docs/model-artifacts.md)                                           |
-| IL2CPP metadata         | Unity global-metadata.dat assembly images, type and method names and index ranges                 | Built-in static decoding of versions 24, 27, 29, 31 and 39; no Unity required                                                         |
-| Godot PCK               | Archive inventory and extraction, original header/directory facts and selected content identities | Built-in static formats 2, 3 and 4; no Godot required                                                                                 |
-| Rust binaries           | Embedded cargo-auditable crate names, versions, sources and dependency edges                      | Built-in static ELF/PE/thin Mach-O inspection; [Rust binaries](docs/rust-binaries.md)                                                 |
-| PE certificates         | Authenticode WIN_CERTIFICATE entries and PKCS#7 signer/X.509 identity fields                      | Built-in static PE inspection; [PE certificates](docs/pe-certificates.md)                                                             |
-| WASM artifact           | Validation, sections, exact import/export WAT forms and decoded WAT                               | Caller-supplied WABT 1.0.42; `inspect_wasm_artifact`                                                                                  |
-| EVM bytecode            | Dispatch selectors, byte offsets, inferred arguments and mutability                               | Local raw/hex carrier on Linux x64; [offline EVM guide](docs/evm-bytecode.md)                                                         |
-| SQLite databases        | Tables, columns, indexes, views, triggers and selected ordinary-table rows                        | Local database/WAL snapshot; Node.js 24.x >=24.15 or 26+ with native SQLite limits                                                    |
-| Recorded Linux crashes  | Raw notes, every recorded thread's registers/signals and optional mapping candidates              | Caller-supplied pwntools on Linux x64; optional GDB/pwndbg; [recorded crashes](docs/recorded-crashes.md)                              |
-| JavaScript / Electron   | Modules, imports, source maps, routes, IPC and native add-on relationships                        | Node.js and npm; Linux: procps-compatible `ps`; [application analysis](docs/javascript-application-workflows.md)                      |
-| Websites                | Page structure, scripts, network observations and requested screenshots                           | A Chrome-family browser; [browser analysis](docs/browser-observation.md)                                                              |
-| Saved network captures  | Requests, responses, exposed payloads and source locations                                        | HAR or Fiddler Everywhere SAZ; mitmdump on Linux for native mitmproxy; [capture guide](docs/web-network-captures.md)                  |
-| .NET assemblies         | Metadata, CIL instructions, declared native dependencies and build comparisons                    | None (static only); [managed-code guide](docs/managed-code-analysis.md)                                                               |
-| Android APKs            | Manifest declarations, classes, decompiled methods and references                                 | Headless JADX and a full JDK on Linux/macOS/Windows x64; [Android guide](docs/android-analysis.md)                                    |
-| Android devices         | Devices, packages, processes, logs, dumps, screen captures, and APK/file transfers                | Caller-supplied adb (emulator or hardware); [ADB guide](docs/adb-device-analysis.md)                                                  |
-| JEB projects            | Engine-backed project units, artifact digests and type/method pseudo-code                         | A caller-started JEB client serving MCP, selected with REA_JEB_MCP_URL; [JEB guide](docs/jeb-analysis.md)                             |
-| Android resources       | Decoded manifest, string tables, locales and version facts                                        | Caller-supplied Apktool launcher; [resource guide](docs/apktool-resource-analysis.md)                                                 |
-| Flutter apps            | Dart snapshot hash, per-ABI library digests and engine build provenance                           | None (static APK parsing); [Flutter guide](docs/flutter-analysis.md)                                                                  |
-| Firmware                | Regions, extraction results and native-analysis handoffs                                          | Binwalk / Unblob on Linux; [firmware guide](docs/firmware-analysis.md)                                                                |
-| Recorded packets        | Selected fields, repeated values, filters and decode-as rules                                     | Linux: TShark 4.x + prlimit; [capture guide](docs/packet-captures.md)                                                                 |
-| Packet summaries        | Endpoints, DNS, TLS SNI, protocol distribution and HTTP requests                                  | Caller-supplied tshark and capinfos (Linux-verified); [pcap guide](docs/pcap-analysis.md)                                             |
-| Recorded logic signals  | Decoder annotations, sample ranges and diagnostics                                                | Linux: sigrok-cli 0.7.2 + prlimit; [signal recordings](docs/signal-recordings.md)                                                     |
-| Packages and resources  | File inventories, digests, plists, Apple bundle anatomy and extracted resources                   | [Artifact and JavaScript guide](docs/javascript-artifact-reconstruction.md), [Apple applications](docs/apple-application-analysis.md) |
-| Process behavior        | Terminal output, interactions, exit and filesystem observations, and run comparisons              | Linux/macOS with a native PTY; [process capture](docs/process-capture.md)                                                             |
-| PyInstaller executables | CArchive members, Python version, entry scripts and extracted bytecode                            | None (static only); [Python packaged applications](docs/python-packaged-applications.md)                                              |
+| Target                 | What REA returns                                                                                  | Requirements and guide                                                                                                                |
+| ---------------------- | ------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------- |
+| Desktop installations  | Runtime candidates, supporting files, component markers and next probes                           | Built-in bounded directory/header inspection; [desktop applications](docs/desktop-applications.md)                                    |
+| Native binaries        | Pseudocode, assembly, strings, symbols, calls and references                                      | Hopper, Ghidra or IDA; [native analysis](docs/native-investigation.md)                                                                |
+| Offline ELF layout     | Sections, segments, original symbols/relocations and static mitigation candidates                 | Caller-supplied pwntools on Linux x64; [binary diagnostics](docs/binary-diagnostics.md)                                               |
+| Go binaries            | Embedded compiler version, modules, replacements and build settings                               | Built-in static ELF/PE/thin Mach-O inspection; no Go installation required                                                            |
+| IL2CPP metadata        | Unity global-metadata.dat assembly images, type and method names and index ranges                 | Built-in static decoding of versions 24, 27, 29, 31 and 39; no Unity required                                                         |
+| Godot PCK              | Archive inventory and extraction, original header/directory facts and selected content identities | Built-in static formats 2, 3 and 4; no Godot required                                                                                 |
+| Rust binaries          | Embedded cargo-auditable crate names, versions, sources and dependency edges                      | Built-in static ELF/PE/thin Mach-O inspection; [Rust binaries](docs/rust-binaries.md)                                                 |
+| WASM artifact          | Validation, sections, exact import/export WAT forms and decoded WAT                               | Caller-supplied WABT 1.0.42; `inspect_wasm_artifact`                                                                                  |
+| EVM bytecode           | Dispatch selectors, byte offsets, inferred arguments and mutability                               | Local raw/hex carrier on Linux x64; [offline EVM guide](docs/evm-bytecode.md)                                                         |
+| SQLite databases       | Tables, columns, indexes, views, triggers and selected ordinary-table rows                        | Local database/WAL snapshot; Node.js 24.x >=24.15 or 26+ with native SQLite limits                                                    |
+| Recorded Linux crashes | Raw notes, every recorded thread's registers/signals and optional mapping candidates              | Caller-supplied pwntools on Linux x64; optional GDB/pwndbg; [recorded crashes](docs/recorded-crashes.md)                              |
+| JavaScript / Electron  | Modules, imports, source maps, routes, IPC and native add-on relationships                        | Node.js and npm; Linux: procps-compatible `ps`; [application analysis](docs/javascript-application-workflows.md)                      |
+| Websites               | Page structure, scripts, network observations and requested screenshots                           | A Chrome-family browser; [browser analysis](docs/browser-observation.md)                                                              |
+| Saved network captures | Requests, responses, exposed payloads and source locations                                        | HAR or Fiddler Everywhere SAZ; mitmdump on Linux for native mitmproxy; [capture guide](docs/web-network-captures.md)                  |
+| .NET assemblies        | Metadata, CIL instructions, declared native dependencies and build comparisons                    | None (static only); [managed-code guide](docs/managed-code-analysis.md)                                                               |
+| Android APKs           | Manifest declarations, classes, decompiled methods and references                                 | Headless JADX and a full JDK on Linux/macOS/Windows x64; [Android guide](docs/android-analysis.md)                                    |
+| Android devices        | Devices, packages, processes, logs, dumps, screen captures, and APK/file transfers                | Caller-supplied adb (emulator or hardware); [ADB guide](docs/adb-device-analysis.md)                                                  |
+| JEB projects           | Engine-backed project units, artifact digests and type/method pseudo-code                         | A caller-started JEB client serving MCP, selected with REA_JEB_MCP_URL; [JEB guide](docs/jeb-analysis.md)                             |
+| Android resources      | Decoded manifest, string tables, locales and version facts                                        | Caller-supplied Apktool launcher; [resource guide](docs/apktool-resource-analysis.md)                                                 |
+| Flutter apps           | Dart snapshot hash, per-ABI library digests and engine build provenance                           | None (static APK parsing); [Flutter guide](docs/flutter-analysis.md)                                                                  |
+| Firmware               | Regions, extraction results and native-analysis handoffs                                          | Binwalk / Unblob on Linux; [firmware guide](docs/firmware-analysis.md)                                                                |
+| Recorded packets       | Selected fields, repeated values, filters and decode-as rules                                     | Linux: TShark 4.x + prlimit; [capture guide](docs/packet-captures.md)                                                                 |
+| Packet summaries       | Endpoints, DNS, TLS SNI, protocol distribution and HTTP requests                                  | Caller-supplied tshark and capinfos (Linux-verified); [pcap guide](docs/pcap-analysis.md)                                             |
+| Recorded logic signals | Decoder annotations, sample ranges and diagnostics                                                | Linux: sigrok-cli 0.7.2 + prlimit; [signal recordings](docs/signal-recordings.md)                                                     |
+| Packages and resources | File inventories, digests, plists, Apple bundle anatomy and extracted resources                   | [Artifact and JavaScript guide](docs/javascript-artifact-reconstruction.md), [Apple applications](docs/apple-application-analysis.md) |
+| Process behavior       | Terminal output, interactions, exit and filesystem observations, and run comparisons              | Linux/macOS with a native PTY; [process capture](docs/process-capture.md)                                                             |
 
 Static JavaScript and .NET inspection read the supplied files without running
 the application. Runtime capture runs or interacts with the selected target

docs/.vitepress/config.ts

@@ -30,9 +30,7 @@ export default defineConfig({
           { text: "Native binaries", link: "/native-investigation" },
           { text: "Go build metadata", link: "/go-binaries" },
           { text: "IL2CPP metadata", link: "/il2cpp-metadata" },
-          { text: "Model artifacts", link: "/model-artifacts" },
           { text: "Rust dependencies", link: "/rust-binaries" },
-          { text: "PE certificates", link: "/pe-certificates" },
           {
             text: "JavaScript and Electron",
             link: "/javascript-artifact-reconstruction",
@@ -51,10 +49,6 @@ export default defineConfig({
           { text: "Electron fuses", link: "/electron-fuses" },
           { text: "Process capture", link: "/process-capture" },
           { text: ".NET assemblies", link: "/managed-code-analysis" },
-          {
-            text: "Python packaged applications",
-            link: "/python-packaged-applications",
-          },
           { text: "Android applications", link: "/android-analysis" },
           { text: "Apple applications", link: "/apple-application-analysis" },
           { text: "Desktop installations", link: "/desktop-applications" },

docs/adb-device-analysis.md

@@ -162,9 +162,8 @@ and during shutdown.
   APKs keep other names report the `unknown` role rather than guessing.
 - **Partial results keep facts.** Failed individual pulls return successful
   artifacts with `coverage: "partial"` and per-file `failures`. Listings
-  and package searches that contain unrecognized lines report the first ten
-  as `unparsed_lines`, state the exact total in a limitation when more were
-  seen, and mark partial coverage instead of dropping rows.
+  that contain unrecognized lines report them as `unparsed_lines` and mark
+  partial coverage instead of dropping rows.
 - **Mutations are explicit.** `push_adb_file`, `install_adb_package`, and
   `uninstall_adb_package` declare `mutatesTarget` and never run implicitly:
   pushes check for existing device files before transfer and refuse them
@@ -172,9 +171,7 @@ and during shutdown.
   transfer even with `overwrite`; only a clean `test -e` exit of 1 with no
   output is interpreted as absence. The check is not atomic, so a different
   process can create the path before `adb push` writes it. When available, the device's
-  `sha256sum` verifies the transfer. A missing command or output without a
-  recognizable digest reports `device_digest_source: "unavailable"` with an
-  unverified-transfer limitation; installs preserve the
+  `sha256sum` verifies the transfer; installs preserve the
   device's `Failure [...]` reason verbatim.
 - **Producer identity stays attached.** Every result embeds the producing
   adb client (`binary_path`, `path_source`, `version`, `installed_path`).
@@ -186,11 +183,9 @@ and during shutdown.
   The app/activity lifecycle tools use `am start -W` and `am force-stop`.
 - Per-invocation budgets: client/devices 10-20 s, shell reads 20-60 s with
   64 KiB-8 MiB capture caps (logcat 4 MiB, screen 32 MiB), transfers and
-  bugreports 600 s. Output capture overflow reports `resource_constraint`
-  and names the byte allowance. Deadline expiration, including the
-  client-version probe, reports `provider_timeout` and names the effective
-  milliseconds. This release has no runtime override for those deadlines or
-  capture caps. Command cancellation preserves the caller's exact reason;
+  bugreports 600 s. Output capture overflow reports `resource_constraint`;
+  deadline expiration, including the client-version probe, reports
+  `provider_timeout`. Command cancellation preserves the caller's exact reason;
   a later abort does not replace an already completed command failure.
 - Pull and capture outputs are additive: the destination must not already
   exist. Re-running a completed pull refuses the existing directory instead

docs/agent-environments.md

@@ -1,15 +1,11 @@
 # Agent environments from recorded captures
 
 Use `rea environment-serve` to serve an environment manifest as an agent
-environment: an MCP server whose tools answer from what one retained web
-network capture observed, plus the environment card the agentenv framework
-reads to discover it. By default the server derives the
-[state the capture observed](#the-state-a-capture-observed) at startup and
-answers read tools from it; `--replay-only` replays the capture's records
-instead. Nothing is fetched from the recorded application; every answer comes
-from retained Evidence. `rea environment-export` writes the same pair as a
-bundle folder `agent-env run` builds and runs; see
-[Export a bundle](#export-a-bundle).
+environment: an MCP server whose tools answer from the records of one retained
+web network capture, plus the environment card the agentenv framework reads to
+discover it. Nothing is fetched from the recorded application; every answer is
+retained Evidence. `rea environment-export` writes the same pair as a bundle
+folder `agent-env run` builds and runs; see [Export a bundle](#export-a-bundle).
 
 ```sh
 rea inspect-web-network-capture /absolute/session.har har --format json > capture.json
@@ -31,10 +27,9 @@ it, where `view.json` wraps the capture Evidence as the inline source:
 }
 ```
 
-The third command serves that manifest from the state it derives from the
-capture; see [Serve from the state](#serve-from-the-state). Both served files
-are complete REA Evidence JSON as the commands write it with `--format json`;
-the `evidence` member of `view.json` is the whole of `capture.json`.
+The third command serves that manifest. Both served files are complete REA
+Evidence JSON as the commands write it with `--format json`; the `evidence`
+member of `view.json` is the whole of `capture.json`.
 
 ## From a browser scenario
 
@@ -115,9 +110,7 @@ record's ordinal is its zero-based position; a transaction whose URL carried a
 redacted secret is left unrepresented rather than templated, and one the
 capture cannot attribute to a single request and response is left
 unrepresented too. Tools are chosen by response media type, so a scenario that
-selected neither response bodies nor header values is refused; one that
-selected header values but no response bodies yields a manifest but no state,
-so it is served by replay. The browser
+selected neither response bodies nor header values is refused. The browser
 scenario redacts credential headers and the secrets it declares; values the
 application returns in response bodies, such as session tokens, are kept, and
 the replayed body is the bytes the browser exposes for each response, with any
@@ -151,16 +144,10 @@ This was calibrated with 1500 query fields and eight concurrent SDK discovery
 requests (183,798-byte card, 507.27 MiB sampled process-family RSS). Over-capacity
 catalogs return `resource_constraint`, retain complete input Evidence, and require
 a smaller capture or manifest. Fields and tools are never silently omitted.
-Served from the state, each description is longer and the card declares the
-data plane, so a catalog replay admits can exceed the reservation; the state
-is then unavailable and the server serves replay instead (see
-[Serve from the state](#serve-from-the-state)).
 
 ## What replay means and does not mean
 
-Replay answers every tool with `--replay-only` or when the state is unavailable,
-and, served from the state, each read tool whose view the state does not back.
-Each such MCP tool call selects one of the records its manifest tool cites and
+Each MCP tool call selects one of the records its manifest tool cites and
 returns that record's recorded response. Selection compares the supplied path
 parameters against the record's path segments at the parameter indexes, then
 the supplied query values against the record's query string, and keeps the
@@ -215,8 +202,7 @@ degrades into an omitted one.
 Replay is not emulation. A served environment does not establish the
 application's authorization model, response semantics or state transitions,
 which the manifest lists as unknowns; it does not validate supplied values; and
-it answers only from the capture's recordings and the state they observed or a
-caller loaded through `data/add`. Replayed content is
+it does not answer requests the capture never recorded. Replayed content is
 target content: every tool result, including the argument errors the MCP server
 returns before a replay runs, carries `_meta.provenance.untrusted_content: true`
 with `source: "analysis_target"`. The server advertises REA's untrusted-content
@@ -234,23 +220,17 @@ moment of the capture recorded them. The
 [environment state](web-network-captures.md#environment-state) view extracts
 instead the data the capture's reads observed before the first related write:
 entity types with an identity field, entities with their recorded values,
-documents for reads that are not entities, and a render plan per read tool,
-kept only where it reproduces that tool's recordings from the state. It is the
-starting state an environment holds, loads and reports: `environment-serve`
-derives it from the capture at startup; see
-[Serve from the state](#serve-from-the-state). With `--replay-only`, replay is
-unchanged.
+documents for written paths, and a render plan per read tool, kept only where
+it reproduces that tool's recordings from the state. It is the starting state
+an environment can hold, load and report; serving from it is a later increment
+and does not change replay.
 
 ## Serve a manifest
 
 ```sh
-rea environment-serve manifest.json --evidence capture.json [--replay-only] [--host 127.0.0.1] [--port 0]
+rea environment-serve manifest.json --evidence capture.json [--host 127.0.0.1] [--port 0]
 ```
 
-The server derives the state from the capture before it binds and serves from
-it, or serves replay with `--replay-only` or when the state is unavailable;
-see [Serve from the state](#serve-from-the-state).
-
 `--host` and `--port` default to `MCP_HOST` and `MCP_PORT` from the
 environment, then to `127.0.0.1` and an ephemeral port, exactly as
 [`rea mcp --http`](cli.md#serve-mcp-over-streamable-http) resolves them. The
@@ -262,8 +242,7 @@ manifest's `name` is used, and a set but blank value is refused as
 listener serves one MCP client at a time with the same session, `Host` header
 and shutdown contract as [transports](mcp-contracts.md#transports) describes.
 It runs until SIGINT or SIGTERM, then closes the listener, prints one
-`{"status":"stopped", …}` document whose `state` member says whether it served
-from the state, and exits `130` or `143`.
+`{"status":"stopped", …}` document and exits `130` or `143`.
 Signals during input loading or DNS/bind cancel the owning reader/listener before
 a listening announcement;
 that path returns a structured `cancelled` result instead of a stopped-listener
@@ -271,19 +250,19 @@ document, with the same signal exit status.
 
 Three routes are served:
 
-| Route                             | Answer                                                                                                                                                         |
-| --------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `POST /mcp`                       | The MCP server: from the state, one tool per read tool, answering from the state where it backs them; in replay, one tool per manifest tool, replaying records |
-| `GET /.well-known/agent-env.json` | The environment card                                                                                                                                           |
-| `POST /agentenv`                  | From the state, `data/reset`, `data/add` and `data/get`; in replay, JSON-RPC `-32601 method not found: <method>` for every method                              |
+| Route                             | Answer                                                                 |
+| --------------------------------- | ---------------------------------------------------------------------- |
+| `POST /mcp`                       | The MCP server: one tool per manifest tool, replaying retained records |
+| `GET /.well-known/agent-env.json` | The environment card                                                   |
+| `POST /agentenv`                  | JSON-RPC `-32601 method not found: <method>` for every method          |
 
 Numeric JSON-RPC IDs outside JavaScript's safe range or whose precision would
 be lost are refused as invalid requests with a null ID. They are never echoed
 as a different number.
 
-In replay the data plane at `/agentenv` is advertised by the card but carries
-no operations; the error names the requested method so a caller can see that
-the method, not the transport, is unsupported. Its request body is
+The data plane at `/agentenv` is advertised by the card but carries no
+operations in this release; the error names the requested method so a caller
+can see that the method, not the transport, is unsupported. Its request body is
 read within the same 4 MiB bound the MCP endpoint applies: a larger body is
 answered `413` with a JSON-RPC `-32000` error before any of it is parsed, and a
 body that is not JSON is answered `400` with `-32700`. A notification (no `id`)
@@ -295,7 +274,7 @@ that are not an object or array) gets `-32600 invalid request`.
 ## The environment card
 
 The card is the discovery document the agentenv framework reads before
-connecting to `/mcp`. A replay environment's card reads:
+connecting to `/mcp`:
 
 ```json
 {
@@ -309,7 +288,7 @@ connecting to `/mcp`. A replay environment's card reads:
     "tools": [
       {
         "name": "get_users_by_id",
-        "description": "Untrusted captured API catalog: … GET /api/users/{numeric}; returns a JSON object with fields \"id\", \"uid\", \"login\", \"email\"; recorded statuses 200; replays retained records [5, 6]; evidence ev_…",
+        "description": "GET /api/users/{numeric}; replays retained records [5, 6]; evidence ev_…",
         "inputSchema": {
           "type": "object",
           "properties": {
@@ -330,38 +309,7 @@ connecting to `/mcp`. A replay environment's card reads:
 ```
 
 `capabilities.tools` lists the same names, descriptions and input schemas that
-`tools/list` advertises over MCP. After the catalog warning, each description
-names the method and path template, then what the tool returns, one level deep:
-`returns a JSON object with fields …`, `returns a JSON array of objects with
-fields …` or `returns a JSON object whose <member> lists objects with fields …`,
-where a list is an array of objects found by the
-[environment state](web-network-captures.md#environment-state)'s list rule (the
-root array, or the one array of objects an envelope carries). Field and member
-names are written as JSON strings, so a captured name cannot read as more of
-the description; a member name too long to show whole is a quoted prefix marked
-as truncated. The summary comes
-from the first cited `2xx` record that replay answers as JSON; only when none
-did, the first cited JSON record of another status gives it, labelled with that
-status (`status 401 returns …`). It describes one recorded response, not a
-contract. Field names are sampled within the same budget as other captured
-values, and the manifest's `statuses` for the tool follow; a tool with no JSON
-record states only its statuses. The description then lists the replayed
-records and the evidence ID, and the whole catalog stays within its
-serialization reservation, which the summaries and MCP annotations are charged
-to.
-
-Over MCP, every tool also carries annotations: `readOnlyHint` is true for the
-safe methods (`GET`, `HEAD`, `OPTIONS` and `TRACE`) and for query `POST`s (a
-path segment such as `search` or `query`); `destructiveHint` is true for `DELETE` and left unset for other
-writes, so the MCP default (destructive) applies to them, and read-only tools
-omit it because clients ignore it there; `idempotentHint` is true for the safe
-methods, `PUT` and `DELETE`; and `openWorldHint` is false for every tool,
-because answers come from the capture rather than the captured application. The
-hints describe the captured method; replay itself changes nothing. The card
-keeps the `name`, `description` and `inputSchema` of the echo example's tool
-shape and carries no annotations.
-
-Path parameters are required strings whose
+`tools/list` advertises over MCP. Path parameters are required strings whose
 description names the segment index, the templating rule and the observed
 values (sampled within the list budget above; the manifest keeps them all);
 query parameter names are optional strings; write methods accept an
@@ -372,207 +320,9 @@ advertised as `query_<name>`, a query name longer than 64 characters as
 and the write body as `request_body` when a query parameter is named `body`. Every
 schema closes with `additionalProperties: false`, a key the echo example's
 schema does not carry.
-In replay, `extensions`, `operations` and `children_environments` are fixed to
-`null`, `[]` and `null`: a replay environment declares no extensions, no
-data-plane operations and no children. Served
-[from the state](#serve-from-the-state), the card declares the three data-plane
-operations and one intake extension instead, leaves write tools out and
-describes each tool as answering from the state where the state backs it.
-
-## Serve from the state
-
-```sh
-rea environment-serve manifest.json --evidence capture.json
-```
-
-Before it binds, the server derives the
-[environment state](web-network-captures.md#environment-state) the capture
-observed: it runs the `environment-state` view on the capture in-process with
-the manifest's `template_rules` in the same order, exactly as
-`inspect-analysis-view` projects it from the same capture, so the state
-Evidence id it reports is the one that projection produces. The view's own
-budget and refusals apply, and the result is checked like the view's Evidence
-for this manifest: extracted from the served capture, with the manifest's
-rules, naming only manifest tools. The server keeps one live state, shared by
-every MCP session and the data plane, starting from the derived state.
-
-A state that is unavailable does not stop the server: it logs a warning naming
-the error `code` and message before it binds, then serves replay. The state is
-unavailable when it cannot be derived, such as from a
-`capture_browser_scenario` capture that selected header values but no response
-bodies or over the view's budget, and when its catalog under the served name
-exceeds the [discovery reservation](#what-a-manifest-is). That check runs
-first, so no state is derived for it, and replay is then admitted exactly as
-with `--replay-only`. `--replay-only`
-serves replay without deriving anything; the card, tools and `/agentenv`
-answers are then exactly those of replay. The stopped document's `state`
-member reports which applied:
-
-- `{"served": true, "evidence_id": "ev_…"}`: served from the derived state.
-- `{"served": false, "reason": "replay-only"}`: `--replay-only` was given.
-- `{"served": false, "reason": "unavailable", "code": "unsupported_target", "message": "…"}`:
-  the state is unavailable; `code` and `message` are those of the refusal
-  (`resource_constraint` for a catalog over the reservation), as the warning
-  logged them.
-
-Each read tool answers according to its view in the state:
-
-| View       | Answer                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
-| ---------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `item`     | The entity the path arguments name, rendered into the recorded envelope of `envelope_ordinal`. Arguments match as replay matches them: each collection segment equals the held collection's segment as written or after percent-decoding, and the identity is the last argument percent-decoded, then as written; values are never re-split on `/`. Any entity the state holds answers, including one `data/add` loaded; query arguments only decide `replay.exact_match`. An entity the state does not hold, or one lacking a field every recording carried, is a tool error; a body is never invented. |
-| `list`     | When the arguments name one of the lines the view checked exactly (its latest recordings before the first related write; every path and query value equal to the recording's, and every recorded query parameter supplied), that recorded envelope with its array rendered from the state: every entity of the collection in state order for `membership: "all"`, or the recorded members still held. A member lacking a field every recording carried makes the call a tool error rather than a partial list.                                                                                           |
-| `document` | When the arguments name the document's checked line exactly, the state's value for it; a tool error when the state holds none.                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
-| `recorded` | The recording, as replay answers it.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
-
-A list or document call that names no checked line, including a line recorded
-after a write or with other query values, answers from the recording. Every
-answer has the replay shape plus `state`: `{"source": "state", "view": …}`
-naming the entity, collection or document path, or `{"source": "recording",
-"reason": …}` with the view's reason, `no-view` or `unrecorded-request`. A
-state answer carries the base record's status, content type and `replay`
-provenance with `truncated: false`; one whose JSON would exceed 256 KiB is
-refused as a `resource_constraint` tool error rather than cut. Extraction does
-not state-back a document whose rendered JSON exceeds 256 KiB; that read stays
-recorded (`rendered-oversize`) and replays the captured body. Serving is
-read-only: `POST`, `PUT`, `PATCH` and `DELETE` tools, other than query `POST`s,
-are not served, so nothing a call does changes the state. Query `POST`s stay
-served and answer from their recordings with the reason `query-body`.
-
-The data plane serves three JSON-RPC methods:
-
-| Method       | Result                                                                                                    |
-| ------------ | --------------------------------------------------------------------------------------------------------- |
-| `data/reset` | `{}` after restoring the state the Evidence holds                                                         |
-| `data/add`   | `{}` after replacing the whole state with one valid `rea-state/v1` document                               |
-| `data/get`   | `{"parts": [{"kind": "data", "data": <rea-state/v1 document>}]}` with `state_evidence_id` and the `types` |
-
-Calls run one at a time in arrival order across requests. Every message of a
-batch is queued when the batch arrives, so another request's call never lands
-between them and each message sees the changes of those before it; a reset
-sent while a download is loading applies after that load. `data/add`
-takes exactly one part: a `data` part whose `data` is the document, or a
-`file` part whose `file` carries `bytes` (base64 of UTF-8 JSON) or a `uri`,
-either a `file://` URL of a local regular file, whose host is empty or
-`localhost`, or an `https://` URL fetched without following redirects and
-within 30 seconds, including reading the body; `mimeType`, when given, is
-`application/json`. A `file://` URL naming another host, or a UNC path such as
-`file:////server/share/state.json`, is refused before anything is opened, so a
-load never reaches a network share. A loaded document is at most 32
-MiB, and so is the state as `data/get` writes it back with the members a
-document may omit (`types`, `state_evidence_id`, record citations), so a
-reported state always loads again; an inline part also stays within the 4 MiB
-request body bound, so larger states arrive by `uri`. Anything else, including `{"parts": []}`, is `-32602
-invalid params`; a download that fails or answers a non-2xx status is
-`-32000`. Errors never echo the uri or the content; a file or download failure
-names its category in `error.data.reason`: `not-found`, `permission`,
-`not-regular-file`, `changed` or `read-failed` for files, `timeout`,
-`http-status` or `network` (connection, TLS or a refused redirect) for
-downloads, and `cancelled` for a download the server's stop or its caller's
-departure ended.
-
-Stopping the server cancels every pending call, and a caller that leaves before
-its reply cancels its own: a download in progress ends, and calls not yet run
-are answered `-32000` with `error.data.reason` `cancelled` without running. A
-cancelled call leaves the state unchanged, and shutdown never waits for a
-download.
-
-A `file://` state file whose close fails stays owned by the server, and
-the `data/add` gets `-32000`. The next `file://` load retries that close first
-and, while it still fails, answers `-32000` without reading another file;
-inline and `https://` documents still load. Closing the server retries it once
-more and fails with the unfinished close rather than dropping the descriptor.
-
-One `/agentenv` response carries at most 64 MiB of replies, twice the 32 MiB
-a loaded document may hold: room for a `data/get` of a loaded state, while a
-batch of reads cannot multiply a large state into one body. Replies are
-measured in order as they are produced, in bounded parts and before they are
-assembled, and room is kept for every later reply's budget error and the
-batch's brackets and commas, so one that would take the response past the
-budget is never built whole and is answered instead with `-32000` whose `error.data` gives
-`max_response_bytes` and the `reply_bytes` it would have taken. That call still
-ran, so repeat such a read in another request. A reply no larger than that
-error, such as a write's `{}`, is always kept.
-
-```json
-{
-  "rea_state": {
-    "version": 1,
-    "entities": [
-      {
-        "type": "/api/users",
-        "collection": "/api/users",
-        "id": "2",
-        "fields": { "id": 2, "login": "probe" }
-      }
-    ],
-    "documents": []
-  }
-}
-```
-
-Each entity's `type` is a state type's `collection_template`, its `collection`
-matches that template segment by segment (a template parameter matches any one
-segment), its identity field's value is its `id`, and its type, collection and
-id are unique; `view_fields` is optional and names item or list views of its
-type. Views render their values over the entity's fields, so a view's values
-must not set the type's identity field to a value whose text differs from the
-entity's `id`. Spell a collection as requests spell it, as `data/get` reports it: list
-calls find entities under the checked line's recorded path. Each document
-names a `document` view once, at its initial document's `path`. The `version`,
-and the `state_evidence_id` and `types` that `data/get` reports, must match
-the served state, so a `data/get` result loads back unchanged. A number without
-an exact native value, or whose serialized spelling would not be read as exact
-(an integer from 2^53 below 1e21, such as `1e20`, in any spelling), or a
-`__proto__` member is refused rather than altered.
-An invalid document is `-32602` naming the first problem by JSON pointer, as in
-`/rea_state/entities/3/collection` (also in `error.data.path`); a problem
-inside caller data (`fields`, `value`, `types`) is located at that member, so
-the pointer never names the caller's keys. A refused document changes nothing;
-a valid one replaces the whole state at once. The order of `entities` is the
-state order lists use.
-
-Record citations stay Evidence provenance. An entity's `record_ordinals` may
-be omitted or empty and a document's `record_ordinal` omitted; otherwise they
-must be the served Evidence's citations for that entity or document, or the
-document is refused. After loading, an entity or document whose values equal the Evidence's cites
-the Evidence's records, and one whose values were edited or added cites none
-(`record_ordinals: []`, no `record_ordinal`), so `data/get` never presents a
-loaded value as recorded.
-
-The card declares the operations and what `data/add` accepts:
-
-```json
-{
-  "extensions": [
-    {
-      "uri": "urn:agentenv:intake/v1",
-      "description": "data/add replaces the whole environment state with one rea-state/v1 document; data/get returns the current state in the same format.",
-      "params": {
-        "add": [
-          { "part": "data", "format": "rea-state/v1", "load": "replace" },
-          {
-            "part": "file",
-            "format": "rea-state/v1",
-            "mimeTypes": ["application/json"],
-            "load": "replace"
-          }
-        ],
-        "get": [{ "part": "data", "format": "rea-state/v1" }]
-      }
-    }
-  ],
-  "operations": ["data/reset", "data/add", "data/get"]
-}
-```
-
-The state is a projection of recorded reads. List and document calls answer
-from the state only for the lines their views checked, and every recorded view
-answers from recordings; item calls answer for any held entity but render only
-the envelope one recording carried. Values copied outside entity objects,
-derived values and counters other than those that count a list stay as
-recorded; no write has an effect. An exported bundle carries no state file:
-its server derives the state at startup, as the export does to predict what it
-serves.
+`extensions`, `operations` and `children_environments` are fixed to `null`,
+`[]` and `null`: a replay environment declares no extensions, no data-plane
+operations and no children.
 
 ## Export a bundle
 
@@ -586,12 +336,12 @@ agent-env run ./grafana-example
 
 ```text
 grafana-example/
-  README.md                                 provenance, what it serves, run command, rights note
+  README.md                                 provenance, replay limits, run command, rights note
   envs/grafana-example/Dockerfile           pinned image: node:24.18.0-bookworm-slim + rea-agents@<this version>
   envs/grafana-example/env.toml             environment_name = "grafana-example"
   envs/grafana-example/manifest.json        byte-exact copy of manifest.json
   envs/grafana-example/evidence.json        byte-exact copy of capture.json
-  artifacts/check_grafana-example/verify.py the verifier
+  artifacts/check_grafana-example/verify.py the replay verifier
   tasks/smoke.json                          deploy_env (local sandbox), then env_outcome_verifier
 ```
 
@@ -602,12 +352,8 @@ pair as `environment-serve` does, so a manifest projected from another capture
 is refused with the same `invalid_request` before anything is written, and the
 bytes it copies are the bytes it authenticated. The bundle directory must be
 absent or empty; an occupied directory is refused and nothing in it changes.
-After checking the bundle name, the export prepares the state from the capture
-exactly as the bundle's server will at startup under that name, to predict what
-the bundle serves; an unavailable state, including one whose catalog exceeds
-the discovery reservation, does not stop the export, and the bundle then
-serves replay. The complete tool catalog the bundle serves must also fit the
-server's advertised catalog budget before any files are written. Privately parsed JSON is sealed once so authentication
+The complete tool catalog must also fit the server's advertised catalog budget
+before any files are written. Privately parsed JSON is sealed once so authentication
 and replay share immutable response trees rather than copying the capture repeatedly.
 `--name` replaces the manifest's portable kebab-case name as the env folder and env id
 (Windows device names such as `con` and `lpt1` are refused);
@@ -615,9 +361,7 @@ and replay share immutable response trees rather than copying the capture repeat
 folder and makes the Dockerfile install it instead of the registry package and
 remove it in the same layer, which is how a checkout rather than a release is
 run. The command prints the
-written files with their sizes, the pinned package source, the number of tools
-the bundle serves as `tool_count`, and in `state` whether it serves from the
-state, in the shape of the serve command's stopped document.
+written files with their sizes and the pinned package source.
 
 Export uses the shared output-tree owner to check directory identities around
 exclusive creates, verify written bytes, and reject unowned entries before
@@ -639,31 +383,21 @@ user, so a private host umask cannot leave them unreadable, runs as that user an
 name from Python sources the image does not have.
 
 `verify.py` is the framework's `async def verify(mcp_url)` shape over its
-Python MCP client: it lists the tools and checks the count equals the number
-the bundle serves (the manifest's read tools from the state, every manifest
-tool in replay), calls one tool with no arguments and checks the call did not
-fail and its `status` is the expected one, and returns one `serve` result
-whose description reports both checks. The tool is the first served `GET` tool
-without path parameters whose answer to no arguments is not an error, and the
-expected status is the status of that answer: the export calls the same answer
-function the server uses, from the derived state or by replay, so a state
-answer carries its base record's status and a replayed one its record's (an
-unknown recorded status stays unknown; it is not borrowed from another
-record). A bundle with no such tool yields a verifier that checks the count
-only and says so. `tasks/smoke.json` deploys the env on the local
+Python MCP client: it lists the tools and checks the count equals the
+manifest's, calls the first `GET` tool without path parameters with no
+arguments and checks the call did not fail and its replayed `status` equals the
+recorded status of that tool's first cited record (an unknown recorded status
+stays unknown; it is not borrowed from another record), and returns one
+`replay` result whose description
+reports both checks. A manifest with no such tool yields a verifier that checks
+the count only and says so. `tasks/smoke.json` deploys the env on the local
 sandbox and runs that verifier against the env's MCP endpoint; the first run
 also builds the framework's own infrastructure, and the run tears everything
 down when it ends.
 
 The README written into the bundle records the capture artifact's SHA-256, the
-capture and manifest Evidence ids, the manifest view digest, the served tool
-count, the derived state's Evidence id or that no state is served, and the
-package source. It says what the environment serves: read tools from the state
-the capture observed, the `/agentenv` data plane on it and no write tools yet,
-replay when the state is unavailable, and `--replay-only` for pure replay; it
-says which applies to this bundle, with the error code and message when the
-state is unavailable, and that neither is emulation and served
-content is untrusted data. It states that the recorded content belongs to the
+capture and manifest Evidence ids, the manifest view digest, the tool count and
+the package source, and states that the recorded content belongs to the
 captured application and must not be published without the rights to it.
 
 ## Compatibility verification
@@ -680,21 +414,13 @@ framework versions.
 
 ## Resource and lifecycle boundaries
 
-The Evidence files are read once at startup through the bounded JSON input
+Both Evidence files are read once at startup through the bounded JSON input
 reader and authenticated as Evidence before the listener binds; a file that is
 not Evidence, a manifest of another view kind, a capture of another format, or
 a manifest projected from a different capture is refused before any port is
-opened. The state is derived once, in-process and before binding, from the
-already authenticated capture: it is projected as retained Evidence, so the
-capture's strings are not charged again as inline view input, and the view's
-96 MiB budget bounds the derivation. Because authentication covers the capture's records, a manifest whose
+opened. Because authentication covers the capture's records, a manifest whose
 parent check passes cites only records the capture retains. The server keeps
-only the cited records' request lines and response text in memory, plus the
-live state when it serves from one: the derived initial state, or one
-validated document whose JSON was at most 32 MiB. Data-plane calls run one at a time, so
-at most one loaded document is being read and parsed at once; `data/get`
-serializes the held state whole. No process is launched and nothing is
-written to disk. No outbound network request is made unless a `data/add` call names an
-`https://` uri, which is fetched once within the limits above; a `file://` uri
-is read once. A listener that fails after binding is logged and ends the command with
+only the cited records' request lines and response text in memory. No outbound
+network request is made, no process is launched and nothing is written to
+disk. A listener that fails after binding is logged and ends the command with
 a `resource_constraint` error and exit `1` instead of serving nothing.

docs/android-analysis.md

@@ -335,12 +335,9 @@ export REA_JADX_OPERATION_TIMEOUT_MS=600000
 ```
 
 The value must be a decimal millisecond count from 1 to 2147483647; anything
-else is refused before Java starts. REA reads it from the environment captured
-at process start. A change applies on the next process start; an already
-running server keeps the deadline it started with. The same deadline bounds
-each upstream call. A timeout names `REA_JADX_OPERATION_TIMEOUT_MS`, the
-effective milliseconds, and that range. A passing JADX configuration check in
-`rea doctor` reports the effective `operation_timeout_ms`. Explicit
+else is refused before Java starts. The same deadline bounds each upstream
+call, a timeout reports the selected value, and a passing JADX configuration
+check in `rea doctor` reports the effective `operation_timeout_ms`. Explicit
 cancellation still ends the operation immediately, and partial observations
 and owned-process cleanup are unchanged. Raising the deadline does not extend
 the bridge's 30-second startup handshake or the upstream **90-second**

docs/apktool-resource-analysis.md

@@ -65,7 +65,6 @@ rea decode-android-resources /targets/Example.apk --locale de
 rea decode-android-resources /targets/Example.apk --locales de --locales pt-BR
 rea decode-android-resources /targets/Example.apk --locales de --locales pt-BR --string-tables-only
 rea decode-android-resources /targets/Example.apk --no-strings
-rea decode-android-resources /targets/Example.apk --decode-timeout-ms 900000
 ```
 
 Equivalent MCP methods are `inspect_apktool_client` and
@@ -134,14 +133,9 @@ still suppresses all string projection, including in this mode.
 
 ## Resource and lifecycle limits
 
-- The decode wall clock is `decode_timeout_ms` (CLI `--decode-timeout-ms`).
-  Omitted means 600000 ms. The integer range is 1 to 2147483647. A change
-  applies on the next decode. It does not raise the 4194304-byte (4 MiB)
-  output capture budget. That capture budget has no runtime override. A
-  stopped decode reports `provider_timeout` and names the effective
-  milliseconds; an exceeded capture budget reports `resource_constraint`.
-- The version probe waits 20000 ms and retains 65536 bytes. This release has
-  no runtime override for that probe. `decode_timeout_ms` does not raise it.
+- The decode runs with a 600 s deadline and a 4 MiB output capture budget;
+  a stopped decode reports `provider_timeout` and exceeded budgets report
+  `resource_constraint`.
 - Manifest reads are bounded to 512 KiB before decoding UTF-8. Strings XML
   reads are bounded to 8 MiB; larger documents are skipped with partial
   coverage and an explicit limit, rather than reported as missing.

docs/apple-application-analysis.md

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

docs/browser-observation.md

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

docs/browser-scenario-contract.md

@@ -23,21 +23,9 @@ that rejection does not roll back browser effects. REA removes its owned
 future-document scripts, restores live frame methods, then disconnects.
 Add secret declarations, storage seeds, and additional artifact or event
 capture only when needed. Action, secret, and storage counts are not capped.
-Duration, action, and navigation timeouts remain separate from CDP command
-deadlines. `command_timeout_ms` (default 20000; omit it to keep that default
-and leave it out of Evidence) bounds launch startup, the connect-over-CDP
-handshake, target lookup, environment commands, and storage CDP commands,
-including replies from attached child targets. Set it in the scenario JSON.
-`capture-browser-scenario` has no `--command-timeout-ms` option.
-It does not change action `timeout_ms`, `wait_for_timeout.duration_ms`, or
-navigation. Service-worker restoration keeps a fixed 5000 ms grace and does
-not inherit a raised `command_timeout_ms`. CDP discovery stays on its own
-fixed deadline. When service workers are blocked, the registration check
-before discovery has its own fixed 10000 ms deadline; `command_timeout_ms`
-does not apply because discovery has not started. The discovery deadline
-covers endpoint discovery only. The following WebSocket handshake and
-`Target.attachToTarget` each use `command_timeout_ms`. `capture.limits` controls retained event and network-content
-budgets; it does not change those liveness deadlines.
+Duration, action, and navigation timeouts remain fixed provider-owned liveness
+limits. `capture.limits` controls retained event and network-content budgets;
+it does not change those liveness deadlines.
 
 ## Minimal launch example
 
@@ -224,9 +212,7 @@ statements remain under the attached debugger client's control.
 The result is Evidence with an initial state followed by one record per
 declared action. Each step reports action status, elapsed time, sanitized URLs,
 event bounds, and independently typed capture states for screenshot, DOM,
-accessibility, URL, history, and storage. Actions after a failed or cancelled
-action are not run and are recorded as `cancelled` with a not-executed error.
-Console, page-error, network,
+accessibility, URL, history, and storage. Console, page-error, network,
 WebSocket, frame, worker, popup, and cancelled-download events are attributed to
 steps. Retained events and requested artifacts are returned inline; omitted
 events are counted by kind and identify affected network transactions.

docs/cli.md

@@ -63,16 +63,6 @@ or repeat it to select several types.
 Selection limits decoding to the selected types; member references remain an
 assembly-wide inventory, so the output can still be large.
 
-Select `--detail summary --evidence-bundle /absolute/path/members.json` to
-receive identity, selection, coverage, limitations and collection counts while
-saving the complete original Evidence in a new bundle. Summary requires that
-explicit destination; existing files are preserved. Later
-`inspect-analysis-view` calls can page the exact parent from the saved bundle
-without reopening the assembly. See
-[CLI summary and saved member rows](managed-code-analysis.md#cli-summary-and-saved-member-rows)
-for the complete command sequence. Omitted or `--detail complete` retains the
-full inline response.
-
 Choose the workflow from the artifact's contents rather than its `.exe` or
 `.dll` extension. The managed parser requires PE/CLI metadata; it does not
 unpack .NET single-file hosts or decode IL2CPP. For the image, type and method
@@ -113,19 +103,6 @@ Formats 2, 3 and 4 retain header, directory and integrity facts. Compact deliver
 keeps complete Evidence in the requested bundle. See [Godot PCK](godot-pck.md)
 for embedded packs, batch queries and unknown encrypted coverage.
 
-Inspect local model declarations without loading weights:
-
-```bash
-rea inspect-model-artifact /absolute/path/model.gguf --json
-rea inspect-model-artifact /absolute/path/model.safetensors --hash full --json
-```
-
-Default hashing reads only headers and leaves full-file identity unknown.
-`--hash full` streams the complete file for SHA-256. Both return typed metadata,
-original tensor declarations and derived totals. MCP summaries retain complete
-Evidence for filtered metadata, tensor and type-total pages; CLI compact delivery
-uses `--detail summary --evidence_output FILE`. See [model files](model-artifacts.md).
-
 Inspect Unity IL2CPP metadata names without Unity or a disassembler:
 
 ```bash
@@ -155,18 +132,6 @@ dependency edges, and the section's file range. A missing `.dep-v0` section is
 null metadata, not proof that the binary has no dependencies. See
 [Rust binaries](rust-binaries.md).
 
-Inspect a PE Authenticode certificate table without executing the image or
-verifying signatures:
-
-```bash
-rea inspect-pe-certificates /absolute/path/to/application.exe --json
-```
-
-The workflow reports `WIN_CERTIFICATE` entries and, for PKCS#7 signedData,
-embedded X.509 serial, issuer, subject, and validity fields. A missing security
-directory is observed absence of that table. See
-[PE Authenticode certificate tables](pe-certificates.md).
-
 Configure [Hopper or Ghidra](installation.md#hopper), the
 [IDA adapter](ida-provider.md), or [Kuna](kuna-provider.md) before analyzing a
 native target. Substitute
@@ -226,7 +191,7 @@ The selected provider remains bound to the session until an explicit switch
 or close. Provider failures are returned with their original reason. For an
 `ambiguous` selection error, choose from `details.candidate_ids`; for
 `provider_unavailable`, follow `message`, `remediation.action`, and the original
-reasons in `details.rejections`. For Hopper, Ghidra, IDA, JADX, and Kuna, run
+reasons in `details.rejections`. For Hopper, Ghidra, IDA, and JADX, run
 `rea doctor --provider ID --json` to diagnose the selected engine. Other adapters,
 such as `pwntools-elf`, report their configuration requirements directly and are
 not accepted by `doctor --provider`. See
@@ -301,12 +266,7 @@ Exports preserve an existing destination unless `--overwrite` is explicit.
 For application traces and version comparisons, see
 [JavaScript application workflows](javascript-application-workflows.md).
 MCP [retained Evidence references](mcp-contracts.md#retained-application-evidence-inputs)
-belong to one connection. Separate CLI calls can consume full saved records.
-`inspect-analysis-view REQUEST.json --evidence-bundle BUNDLE.json` resolves
-the request's `retained-evidence` source ID from that authenticated bundle,
-including bundles exported from an MCP session. The same view JSON works for
-every supported parent kind; no target is reopened and no record is selected
-by file order. Omit `--evidence-bundle` when the request supplies inline Evidence.
+belong to one connection. Separate CLI calls consume full saved records.
 
 ## Import historical source
 
@@ -417,25 +377,14 @@ entry keep stdio.
 
 ## Serve an environment manifest
 
-`rea environment-serve <manifest.json> --evidence <capture.json>
-[--replay-only] [--host H] [--port N]` serves an environment manifest
-projected by `inspect-analysis-view` as an agent environment: an MCP server at
-`/mcp`, the environment card at `/.well-known/agent-env.json`, and a
-`/agentenv` data plane. The manifest's `parent_evidence_id` must equal the
-evidence file's `evidence_id`; otherwise the command refuses with
-`invalid_request` before binding. Before binding it derives the
-`environment-state` view of the capture with the manifest's `template_rules`,
-as `inspect-analysis-view` would, and serves from it: read tools whose views
-are state-backed answer from a live state, write tools are not served, and
-`/agentenv` serves `data/reset`, `data/add` and `data/get`. When the state
-cannot be derived, or its catalog exceeds the discovery reservation, it logs a
-warning with the error code and message and serves replay; `--replay-only` serves replay without deriving. In replay every
-manifest tool replays the retained capture records it cites and `/agentenv`
-answers every method with JSON-RPC `-32601`. The stopped document's `state`
-member is `{"served": true, "evidence_id": …}`,
-`{"served": false, "reason": "replay-only"}` or
-`{"served": false, "reason": "unavailable", "code": …, "message": …}`; see
-[serve from the state](agent-environments.md#serve-from-the-state).
+`rea environment-serve <manifest.json> --evidence <capture.json> [--host H]
+[--port N]` serves an environment manifest projected by `inspect-analysis-view`
+as an agent environment: an MCP server at `/mcp` with one tool per manifest
+tool, each replaying the retained capture records it cites, the environment
+card at `/.well-known/agent-env.json`, and a `/agentenv` data plane that
+answers every method with JSON-RPC `-32601`. The manifest's
+`parent_evidence_id` must equal the evidence file's `evidence_id`; otherwise
+the command refuses with `invalid_request` before binding.
 
 ```sh
 rea environment-serve manifest.json --evidence capture.json --port 8765
@@ -446,8 +395,8 @@ rea environment-serve manifest.json --evidence capture.json --port 8765
 the served environment; set but blank, it is refused as `configuration_invalid`
 like a blank `MCP_HOST`. The bound URL is written to stderr as one JSON log line
 (`"msg":"MCP transport listening"`). See
-[agent environments](agent-environments.md) for what the state and replay
-return and do not establish.
+[agent environments](agent-environments.md) for what replay returns and does
+not establish.
 
 ## Export an environment bundle
 
@@ -455,11 +404,9 @@ return and do not establish.
 [--package-tarball <path>] [--name <override>]` writes the same manifest and
 capture pair as a bundle folder the agentenv framework runs with
 `agent-env run <dir>`. It reads each file once, authenticates and cross-checks
-the pair with the same checks as `environment-serve`, checks the bundle name,
-then prepares the state under that name as the bundle's server will at startup
-to predict what the bundle serves (replay when the state is unavailable),
-copies the bytes it authenticated, refuses to write into a directory that
-exists and is not empty, and never overwrites a file.
+the pair with the same checks as `environment-serve`, copies the bytes it
+authenticated, refuses to write into a directory that exists and is not empty,
+and never overwrites a file.
 
 ```sh
 rea environment-export manifest.json --evidence capture.json ./grafana-example --json
@@ -469,16 +416,14 @@ The folder holds a `README.md` with the bundle's provenance, an env folder
 `envs/<name>/` with a `Dockerfile` that installs this exact `rea-agents`
 version and serves the copied `manifest.json` and `evidence.json` (written
 with mode `0600` on POSIX; Windows retains inherited ACLs) with
-`environment-serve` (from the state by default), a Python verifier under
-`artifacts/check_<name>/` that checks the served tool count and one served
-answer, and the smoke task `tasks/smoke.json`. `--package-tarball` copies a packed `rea-agents`
+`environment-serve`, a Python verifier under `artifacts/check_<name>/` and the
+smoke task `tasks/smoke.json`. `--package-tarball` copies a packed `rea-agents`
 tarball into the env folder and installs it instead of the registry package,
 which is how the hosted lane proves a checkout rather than a release. `--name`
 replaces the manifest's kebab-case name as the env folder and env id; a device
 name Windows reserves (`con`, `nul`, `com1` and the like) is refused. The
-command prints one JSON document listing the written files with their sizes,
-the pinned package source, the served `tool_count`, and `state` in the shape
-of the serve command's stopped document. See
+command prints one JSON document listing the written files with their sizes
+and the pinned package source. See
 [agent environments](agent-environments.md#export-a-bundle) for the folder
 layout and what the smoke task checks.
 
@@ -530,20 +475,18 @@ SIGTERM, closes the listener, then prints one structured
 `{"status":"stopped", …}` document naming the URL, environment and tool count
 and exits `130` or `143` through the shared cancellation handler below.
 Refusals before binding (unreadable files, non-Evidence JSON, capture Evidence
-in a format other than HAR, a manifest or state whose parent is not the
-supplied evidence, an unbindable port) print a structured
+in a format other than HAR, a manifest whose parent is not the supplied
+evidence, an unbindable port) print a structured
 error and exit `1`, as does a listener that fails after binding.
 `rea environment-export` is one-shot: it prints the written files and exits
 `0`, or prints a structured `invalid_request` error and exits `1` for the same
 pair refusals, a non-empty or file-occupied directory, a missing package
 tarball or a name that is not a kebab-case label or is a Windows device name,
 writing nothing in each case.
-A write that fails after the first file (a permission, disk-space or
-pathname-length failure on a later path) propagates as the host's failure,
-naming its cause and, when it failed on one bundle file or the package
-tarball, that file. A failure while syncing the finished folder names only its
-cause. Either way the partial folder stays in place for inspection; remove it
-before retrying, since the next attempt refuses the non-empty directory.
+A write that fails after the first file (a permission or disk-space failure
+on a later path) propagates as the host's failure and leaves the partial
+folder in place for inspection; remove it before retrying, since the next
+attempt refuses the non-empty directory.
 
 A `cancelled` result does not by itself determine the exit status; it depends on
 the command's signal handling. Commands routed through the shared
@@ -563,14 +506,6 @@ command, objdump, Rizin and GDB, and the agent environment server
 signal-derived status. This describes the current source routing; it is not a
 claim that every command or provider runtime has been independently exercised.
 
-Commands with `--evidence_output` select their delivered view, then publish the
-complete Evidence bundle atomically. Cancellation before publication leaves no
-new file. A publication that has committed can win a later cancellation; the
-`cancelled` result then keeps the written path and byte count under
-`details.diagnostics.evidence_bundle`. If staging cleanup stays incomplete
-after commit, the `cleanup_incomplete` error reports the same file as
-`details.published_path` and `details.bytes`.
-
 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

@@ -153,8 +153,8 @@ headroom. The default is 450000 ms, covering the default 330-second Ghidra
 startup; an explicit Ghidra startup timeout of 2700000 ms produces a 2820000 ms
 tool timeout. The startup allowance follows an explicitly selected Ghidra or
 Hopper provider, and otherwise uses the larger known Ghidra/Hopper deadline.
-An explicit `REA_JEB_MCP_TIMEOUT_MS` deadline, shared by catalog discovery and
-each tools/call, also contributes to that maximum. For `ida` or `auto` selection, a valid IDA registration's parsed
+An explicit `REA_JEB_MCP_TIMEOUT_MS` request budget also contributes to that
+maximum. For `ida` or `auto` selection, a valid IDA registration's parsed
 `timeoutMs` also contributes to that maximum; its default is 300000 ms.
 Setup forwards these explicitly selected REA deadlines and the input schema
 profile into the registration; unrelated process values are omitted. An

docs/client-verification.md

@@ -17,8 +17,8 @@ shared form would leave later fields unknown instead. The existing
 `REA_MCP_INPUT_SCHEMA_PROFILE=compact` profile lets callers stay below
 its character limit by advertising reduced nested validation structure, while
 REA continues to validate calls against the complete canonical input schema.
-Compact is the default for the server's advertised inputs; an explicit `full`
-choice is preserved. See the [compact input schema profile](mcp-contracts.md#compact-input-schema-profile)
+Compact applies to the server's advertised inputs and is not an automatic
+full-profile fallback; see the [compact input schema profile](mcp-contracts.md#compact-input-schema-profile)
 for details of its reduced forms.
 
 Custom renderer hosts can raise `inputMaxChars` through `renderToolSignature` or
@@ -457,22 +457,13 @@ disposable HOME and CODEX_HOME under `~/.cache/rea-agent-evaluations/`. Set
 `REA_AGENT_EVAL_ROOT` to choose another parent directory outside the OS temporary
 directory: current Codex refuses helper aliases under `/tmp`, preventing shell
 commands and skill reads even if MCP works. Each owned run directory is removed
-after verification unless fixture retention is requested. Commands share the
-owned-process supervisor: native ownership preparation has its own bounded
-deadline before each short command budget, and timeouts join bounded process-tree
-and output cleanup before returning. If cleanup remains incomplete, the lane retries its retained
-owner and preserves the run directory (including disposable auth) rather than
-removing files still in use; the error retains ownership and recovery details.
-Command stderr is limited to 32 KiB and combined version output to 8 KiB;
-exceeding these diagnostic budgets fails explicitly. Scenario JSON events stream
-to the evaluator without retaining a second raw stdout copy. Cleanup attempts the
+after verification unless fixture retention is requested. Cleanup attempts the
 remaining run tree even if auth removal fails, and reports unresolved cleanup
 together with the original verification failure. The lane
 installs the packaged skill and MCP registration through public `rea setup`,
 rather than copying a skill into a project that also inherits the caller's
 skills and configuration. Only authentication is copied, when present, and it
-is removed after confirmed process cleanup even with
-`REA_AGENT_EVAL_KEEP_FIXTURES=true`. No user configuration,
+is removed even with `REA_AGENT_EVAL_KEEP_FIXTURES=true`. No user configuration,
 rules, plugins or history is copied; shell snapshots and additional agents are
 disabled. Existing API-key environment authentication remains available.
 The native missing-provider scenario preapproves only `open_binary` and

docs/desktop-applications.md

@@ -91,20 +91,17 @@ same bundle. Export writes only the caller-selected output file.
 
 ## Facts and uncertainty
 
-| Family       | Evidence used                                                                                                                                                                                                                                  |
-| ------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| .NET         | A PE optional header declares a nonempty CLI directory.                                                                                                                                                                                        |
-| Unity Mono   | A managed assembly below `*_Data/Managed` or `Contents/Resources/Data/Managed` has an exact UnityEngine assembly reference.                                                                                                                    |
-| Unity IL2CPP | A recognized IL2CPP metadata magic (with the raw version when complete) coexists with a conventionally named native `GameAssembly.dll`, `GameAssembly.so`, `GameAssembly.dylib` or `libil2cpp.so` image. Build correspondence remains unknown. |
-| Godot        | A `GDPC` header at file start or a validated executable trailer offset.                                                                                                                                                                        |
-| GameMaker    | A bounded `FORM` container starts with a `GEN8` chunk.                                                                                                                                                                                         |
-| Unreal       | `Content/Paks` path conventions or an IoStore TOC signature; arbitrary `.pak` filenames are insufficient.                                                                                                                                      |
-| Electron     | A `resources/app.asar` or `resources/default_app.asar` path convention; archive validity is unverified.                                                                                                                                        |
+| Family       | Evidence used                                                                                                                                                                                    |
+| ------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| .NET         | A PE optional header declares a nonempty CLI directory.                                                                                                                                          |
+| Unity Mono   | A managed assembly below `*_Data/Managed` or `Contents/Resources/Data/Managed` has an exact UnityEngine assembly reference.                                                                      |
+| Unity IL2CPP | An IL2CPP metadata header coexists with a conventionally named native `GameAssembly.dll`, `GameAssembly.so`, `GameAssembly.dylib` or `libil2cpp.so` image. Build correspondence remains unknown. |
+| Godot        | A `GDPC` header at file start or a validated executable trailer offset.                                                                                                                          |
+| GameMaker    | A bounded `FORM` container starts with a `GEN8` chunk.                                                                                                                                           |
+| Unreal       | `Content/Paks` path conventions or an IoStore TOC signature; arbitrary `.pak` filenames are insufficient.                                                                                        |
+| Electron     | A `resources/app.asar` or `resources/default_app.asar` path convention; archive validity is unverified.                                                                                          |
 
-When the four-byte metadata magic is present but version bytes are incomplete,
-the fact retains `raw_version: null`; it does not offer an IL2CPP metadata
-inspection probe. A complete magic/version prefix with supported raw version 29,
-31 or 39 offers an
+An observed metadata header with supported raw version 29, 31 or 39 offers an
 `inspect_il2cpp_metadata` follow-up at its admitted file path, including when no
 native library was found. This probe does not establish full metadata validity
 or correspondence to a native binary. See [IL2CPP metadata](il2cpp-metadata.md).

docs/electron-observation.md

@@ -116,9 +116,7 @@ The CLI and MCP surfaces accept the same schema. For a JSON request file:
 rea capture-electron-scenario scenario.json --json
 ```
 
-The result records one status and target per declared action; actions after a
-failed or cancelled action are not run and are recorded as `cancelled` with a
-not-executed error. It also records correlated app/window/WebContents,
+The result records action status and targets, correlated app/window/WebContents,
 preload, session, navigation, shell, permission, popup, download, protocol,
 native-addon, process, and IPC timeline events. IPC channels and argument-shape
 metadata retain their observed lengths; payload values are never retained.
@@ -245,10 +243,4 @@ application path and capture outcome to the static graph, while frames, scripts,
 workers, and execution claims remain unavailable until a separate passive runtime
 capture provides them.
 
-ASAR observation reads the header through one open file handle and validates its
-declared lengths against the archive size. Header/index admission is the same
-budget used by static ASAR reads: 16 MiB / 16777216 bytes by default, or
-`REA_ASAR_MAX_HEADER_BYTES` (at most 256 MiB) when set. An oversized header is
-not parsed; selecting a member path does not bypass admission, and the page
-stays unauthorized. The header cache separately retains at most that many bytes
-of already-admitted encoded headers across eight archives. Evicting that cache does not raise admission.
+ASAR observation reads the header through one open file handle, validates its declared lengths against the archive size, and limits encoded JSON headers to 16 MiB before parsing. The header cache also retains at most 16 MiB of encoded headers across eight archives. Oversized headers produce a scope refusal.

docs/evm-bytecode.md

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

docs/firmware-analysis.md

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

docs/frida-instrumentation.md

@@ -6,24 +6,8 @@ For remote devices, pass a host with an optional port (`host[:port]`; bracket IP
 
 MCP exposes `list_frida_devices`, `list_frida_processes`, `start_frida_session`, `load_frida_script`, `resume_frida_session`, `unload_frida_script`, `frida_session_status`, and `close_frida_session`. A spawned process starts paused so scripts can load first. Closing unloads session scripts and detaches. If a spawn remains paused, REA resumes it only after script cleanup or session detach confirms the instrumentation is released; if both cleanup paths fail, the target stays paused and the cleanup error is retained. REA never kills the target. MCP sessions end with the server process. The one-shot CLI command `instrument-with-frida` accepts one inline script or script file, observes messages for a bounded duration, and returns Evidence with the source hash and captured messages.
 
-For state and capture-coverage checks, pass `{"session_id":"SESSION_ID","detail":"summary"}` to `frida_session_status`. Each call reads the observed session state and retains the complete observation. The reply is an `inspect_analysis_view` Evidence summary with the session identity, state, scripts, `messages_retained`, and `messages_truncated`; message payloads remain in its `parent_evidence_id`. The count covers retained queued messages, not every target event. Omitted `detail` or `detail=complete` preserves the existing complete reply.
-
-A summary's selected fields look like this (excerpt):
-
-```json
-{
-  "summary": {
-    "state": "running",
-    "messages_retained": 50,
-    "messages_truncated": false
-  }
-}
-```
-
-Use `get_evidence_bundle` with `detail="summary"` and `filters={"evidence_id":"PARENT_ID"}` to discover parent metadata without message payloads. Filters apply only to summary delivery. Use `export_evidence_bundle` for the complete canonical bundle, then select the record whose `evidence_id` matches `normalized_result.parent_evidence_id` from the status summary. To use the existing CLI `inspect-analysis-view`, extract that record into a standalone Evidence JSON file and select it as an Evidence-file source with `view={"kind":"summary"}`. Reading retained Evidence does not refresh a live session or verify a process after exit or PID reuse.
-
 Failed startup cleanup retains acquired Frida handles, including a paused spawn that has not attached, for later cleanup retries. Its remote connection stays leased until session detach and target resume complete. CLI commands await provider cleanup before returning; MCP retains these resources for cleanup when its server closes. Server shutdown stops admitting new Frida operations and waits for admitted startup, discovery, and queued work before releasing their resources. A failed cleanup remains reported and can be retried by closing the server again, rather than treating an unregistered session as fully released.
 
-Frida scripts execute inside the selected target with that process's memory, filesystem, and network authority. Local device lookup waits 1000 ms. This release has no runtime override for that lookup; another REA timeout does not raise it. Remote endpoints do not use that lookup. Message capture is bounded to 16 MiB and reports truncation. Metadata, type, and text field caps, and the JSON node cap, are also fixed. Evidence names a cap when that observation actually dropped data. This release has no runtime override for those capture caps. Script source is not stored in Evidence; its selected path and SHA-256 digest are. For a file, `source_sha256` identifies the original selected bytes. Invalid UTF-8 continues to use replacement decoding; Evidence then records that limitation and `raw_result.source_representation` with the encoding, decoding mode, and `loaded_source_sha256` of the UTF-8 string passed to Frida. Valid UTF-8 files and inline scripts do not need this additional representation fact. Evidence retains non-authentication target selection such as device or endpoint, mode, program or PID, and spawn arguments. Authentication values remain excluded. Results report the observed session and messages, while unsupported platform metadata remains unknown. A request cancelled before a Frida operation starts has no provider effects. If cancellation arrives during a native Frida call, REA waits for that call to return, then closes any session it created and returns the observed session as a partial observation. A cancelled script load on an existing session releases only its new script before queued operations can run; the session and previously loaded scripts remain available. If cancellation is observed when the native call returns, partial Evidence retains the source identity and captured messages even if that call rejects, including messages emitted during awaited cleanup. The caller's cancellation reason remains primary and a native rejection is retained as a sanitized diagnostic. A failure already observed before cleanup stays primary if cancellation arrives during cleanup. The cancellation cutoff is REA's observation of native completion, rather than a claim about unobservable native event order. `script_id` is REA's load-attempt identity. When creation rejects without returning a handle, `script_cleanup: "no_handle"` means REA acquired no handle to unload; it does not prove that the engine performed no work. Once the provider commits a successful load, later request cancellation does not unload that script; use `unload_frida_script` to release it. If script cleanup fails, the script remains owned and a paused target cannot resume until the pending instrumentation is released. Queued script loads, resumes, and unloads check cancellation before dispatching native effects. Cancellation Evidence separately reports whether a target resume was observed, whether instrumentation cleanup completed, and that final target liveness remains unknown. REA does not kill the target. Remote discovery retains its observations and reports a separate cleanup error if the temporary connection cannot be removed.
+Frida scripts execute inside the selected target with that process's memory, filesystem, and network authority. Message capture is bounded to 16 MiB and reports truncation. Script source is not stored in Evidence; its selected path and SHA-256 digest are. For a file, `source_sha256` identifies the original selected bytes. Invalid UTF-8 continues to use replacement decoding; Evidence then records that limitation and `raw_result.source_representation` with the encoding, decoding mode, and `loaded_source_sha256` of the UTF-8 string passed to Frida. Valid UTF-8 files and inline scripts do not need this additional representation fact. Evidence retains non-authentication target selection such as device or endpoint, mode, program or PID, and spawn arguments. Authentication values remain excluded. Results report the observed session and messages, while unsupported platform metadata remains unknown. A request cancelled before a Frida operation starts has no provider effects. If cancellation arrives during a native Frida call, REA waits for that call to return, then closes any session it created and returns the observed session as a partial observation. A cancelled script load on an existing session releases only its new script before queued operations can run; the session and previously loaded scripts remain available. If cancellation is observed when the native call returns, partial Evidence retains the source identity and captured messages even if that call rejects, including messages emitted during awaited cleanup. The caller's cancellation reason remains primary and a native rejection is retained as a sanitized diagnostic. A failure already observed before cleanup stays primary if cancellation arrives during cleanup. The cancellation cutoff is REA's observation of native completion, rather than a claim about unobservable native event order. `script_id` is REA's load-attempt identity. When creation rejects without returning a handle, `script_cleanup: "no_handle"` means REA acquired no handle to unload; it does not prove that the engine performed no work. Once the provider commits a successful load, later request cancellation does not unload that script; use `unload_frida_script` to release it. If script cleanup fails, the script remains owned and a paused target cannot resume until the pending instrumentation is released. Queued script loads, resumes, and unloads check cancellation before dispatching native effects. Cancellation Evidence separately reports whether a target resume was observed, whether instrumentation cleanup completed, and that final target liveness remains unknown. REA does not kill the target. Remote discovery retains its observations and reports a separate cleanup error if the temporary connection cannot be removed.
 
 The [Frida Core API](https://frida.re/docs/frida-core-api/) documents device management, sessions, and script loading; the [JavaScript API](https://frida.re/docs/javascript-api/) documents target-side instrumentation. [Luma](https://luma.frida.re/) is Frida's standalone GUI; REA does not automate or control it. `npm run verify:frida` requires a Linux host with the optional Frida binding and uses a short-lived local Node.js fixture created by the verifier. Add `-- --address HOST:PORT --pid PID` to run the separate remote attach lane against a caller-selected target. Mock tests do not establish real device/server compatibility.

docs/go-binaries.md

@@ -19,56 +19,6 @@ requires an absolute filesystem path and preserves that exact selection:
 }
 ```
 
-For build identity and counts, select `detail: "summary"`. MCP retains the same
-complete Evidence and returns `normalized_result.parent_evidence_id`. Read
-selected dependency versions without reopening the file:
-
-```json
-{
-  "name": "inspect_analysis_view",
-  "arguments": {
-    "source": {
-      "kind": "retained-evidence",
-      "evidence_id": "ev_<parent digest>"
-    },
-    "view": {
-      "kind": "go",
-      "collection": "dependencies",
-      "paths": ["golang.org/x/crypto"],
-      "fields": ["path", "version", "replacement"],
-      "offset": 0,
-      "limit": 10
-    }
-  }
-}
-```
-
-Go views support `dependencies` (exact `paths`) and `settings` (exact `keys`),
-optional original `indices`, field selection, and pagination. Filters intersect;
-empty filter arrays select no rows and `fields: []` returns only row identity.
-Each row keeps its original `index`, scoped to the parent Evidence and collection;
-duplicate module paths and setting keys keep distinct indices. Page offsets
-count matching records. Exhausting retained rows does not establish complete
-runtime dependencies. Original bytes, unknown lines and all complete metadata
-remain in the parent and can be exported as an Evidence bundle.
-
-One-shot CLI summaries save complete Evidence before returning the projection:
-
-```bash
-rea inspect-go-binary ./application --detail summary --evidence_output ./go-evidence.json --json
-```
-
-`--evidence_output` is required for CLI summary delivery and never overwrites an
-existing file. The default CLI/MCP reply remains complete.
-
-[Measured workflows](../experiments/analysis-efficiency/go-build-views.md) include
-catalog repetition and extra calls. Identity/count questions benefit from a
-single summary. In the tested Codex full-catalog configuration, a compound
-question about identity and one dependency uses fewer tokens in captured request JSON with
-one complete inspection than with a summary followed by a lookup. The complete
-reply remains useful for that initial question; retained views support later
-selected reads. Token figures are serialization estimates, not model usage.
-
 ## Observations
 
 The inline Evidence result contains the artifact path, SHA-256, byte length,
@@ -109,21 +59,11 @@ module record and no dependency records has an observed empty dependency list.
 
 ## Supported boundary
 
-The built-in TypeScript reader supports ELF, PE and thin Mach-O images, and one
-selected slice of a universal Mach-O, with Go's inline or historical pointer
-build-info encoding. Source ranges refer to the original stable file snapshot,
-including pointer-backed strings. It does not scan arbitrary byte strings as
-compiler metadata.
-
-A universal (FAT) Mach-O needs `architecture` (`x86`, `x86_64`, `arm`
-or `arm64`; CLI `--architecture`). REA reads its own FAT table, without `lipo`,
-and validates the selected slice's range, alignment and Mach-O header CPU
-against the table. The result keeps the universal file as `artifact` (its
-SHA-256 and size), adds `selected_slice` with the slice offset, length, raw CPU
-type/subtype and the FAT table digest, and reports every source range as a
-file offset inside that slice. Without `architecture`, or when the file has no
-such slice or several, the request fails on `architecture` and lists the slices
-present. `architecture` on any other image is rejected rather than ignored.
+The built-in TypeScript reader supports ELF, PE and thin Mach-O images with Go's
+inline or historical pointer build-info encoding. Source ranges refer to the
+original stable file snapshot, including pointer-backed strings. It does not
+scan arbitrary byte strings as compiler metadata or interpret a fat Mach-O
+container as one selected architecture.
 
 For ELF images without a named build-info section, discovery checks each
 nonempty writable, non-executable load segment in program-header order. This

docs/gpu-code-objects.md

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

docs/ida-provider.md

@@ -41,15 +41,6 @@ rea function /absolute/path/to/program main --json
 rea decompile /absolute/path/to/program main --json
 ```
 
-If the registration cannot be read or validated, provider diagnostics retain its
-selected `registration_path` and the configuration owner's setting/constraint
-facts in `configuration_details.settings`, plus `configuration_remediation`.
-`configured` means a path was selected, not that it is valid or an IDA connection
-was established; failed registrations remain unavailable. Correct
-`REA_IDA_MCP_CONFIG` in the next CLI invocation's environment or the MCP server's
-launch environment. Restart/reconnect that server after changing its environment;
-an export in another shell does not update a running server.
-
 Open the **original input binary** in REA, not an `.idb` or `.i64` database. Its SHA-256 must match IDA's recorded input hash. REA checks the attached identity and image base around each analysis request. A mismatch or target switch fails with recovery guidance. The original input must remain readable by REA; WSL can use its mounted alias while the GUI runs on Windows. Attached profiles, including native mode, refuse universal Mach-O inputs at admission: every slice shares the recorded whole-file hash, so REA cannot verify which slice the GUI loaded. Open a thin file extracted with `lipo -thin` in both IDA and REA, or use headless mode, which analyzes the selected slice.
 
 REA's close operation releases its MCP connection or proxy. It never saves or closes the existing GUI database. External edits remain visible because results are live and are not replayed from snapshots. These checks do not lock the GUI or prove that the database is unpatched.
@@ -142,7 +133,7 @@ Use a package version that actually includes this adapter; repository main can b
 {"name":"close_binary","arguments":{}}
 ```
 
-Opening an MCP target starts its selected provider session; headless opening waits for auto-analysis. Set the agent's MCP request deadline long enough for the target. The registration JSON named by `REA_IDA_MCP_CONFIG` has an optional `timeoutMs` integer from 1 to 2147483647. Omitted means 300000. REA applies an edited value on the next IDA connection after it re-reads that file; an already open session keeps the timeout it connected with. Changing the `REA_IDA_MCP_CONFIG` path itself is read at process start. An upstream SDK request that reaches this limit returns `provider_timeout` naming the effective milliseconds and `timeoutMs`. A shorter inner request is the time remaining inside that ceiling, and the error names both when they differ. A freshly opened headless worker can briefly report `status: "busy"` from `server_health`; REA re-reads health every 100 ms until the worker answers, the caller cancels, or `timeoutMs` has elapsed since the first read. Each health request is capped by the time remaining in that overall wait, so a stalled read cannot extend the readiness deadline by another full request timeout. Expiry while the worker is still busy produces a retryable `provider_timeout`; no further read is started after the deadline. That error names the busy tool from the last observation, or `unknown` when the worker reported none or a value that is not tool-name-shaped. If a health request itself consumes the remaining wait budget, the same last-busy timeout is returned with the stalled request's captured output. Cancellation during the wait produces `cancelled`. Any other unexpected health payload, including a busy payload with an invalid shape, remains `unreadable_output`. Cancellation drains the current upstream request before cleanup; it does not force-stop GUI analysis. An open request that times out without a completed response retains the private workspace because worker inventory alone cannot prove the request has stopped. `binary_session` reports actual tool availability. Repeated doctor/setup calls are unnecessary when the registration already works.
+Opening an MCP target starts its selected provider session; headless opening waits for auto-analysis. Set the agent's MCP request deadline long enough for the target. The registration's optional `timeoutMs` defaults to 300000 for upstream requests. An upstream SDK request that reaches this limit returns `provider_timeout` with its operation and actual request budget. A freshly opened headless worker can briefly report `status: "busy"` from `server_health`; REA re-reads health every 100 ms until the worker answers, the caller cancels, or `timeoutMs` has elapsed since the first read. Each health request is capped by the time remaining in that overall wait, so a stalled read cannot extend the readiness deadline by another full request timeout. Expiry while the worker is still busy produces a retryable `provider_timeout`; no further read is started after the deadline. That error names the busy tool from the last observation, or `unknown` when the worker reported none or a value that is not tool-name-shaped. If a health request itself consumes the remaining wait budget, the same last-busy timeout is returned with the stalled request's captured output. Cancellation during the wait produces `cancelled`. Any other unexpected health payload, including a busy payload with an invalid shape, remains `unreadable_output`. Cancellation drains the current upstream request before cleanup; it does not force-stop GUI analysis. An open request that times out without a completed response retains the private workspace because worker inventory alone cannot prove the request has stopped. `binary_session` reports actual tool availability. Repeated doctor/setup calls are unnecessary when the registration already works.
 
 For guided registration, set `REA_IDA_MCP_CONFIG` before `rea setup --client <client>`. Setup includes that file reference in its reviewed plan and preserves it after approval; it does not copy upstream credentials into the agent configuration. For `ida` or `auto` selection, Codex/Kimi setup and doctor use the effective client registration's parsed `timeoutMs` (default 300000 ms) when recommending the agent's per-tool deadline. Existing positive client deadlines remain caller choices. `rea doctor --provider ida --json` validates the registration without starting IDA and explicitly leaves runtime compatibility and target binding for analysis.
 

docs/index.md

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

docs/installation.md

@@ -24,10 +24,6 @@ Restart the agents named in the completion message. Quit Claude Desktop fully
 before approving, because a running app can overwrite the registration; on
 Windows, see [where Claude Desktop reads its configuration](client-configuration.md#claude-desktop).
 
-During package resolution, npm may print a deprecation warning for `prebuild-install`
-from transitive native dependencies (such as Frida). This warning originates from
-the upstream dependency tree and does not affect REA or indicate setup failure.
-
 For the latest published release, use `npx rea-agents@latest setup`.
 [Package-runner and global-installation options](#package-runners-and-global-installation)
 cover explicit versions, Bun, runtime requirements, and the curl wrapper.
@@ -344,13 +340,6 @@ A scoped report has `scope.mode: "explicit"`. Its `scope_checks` determine
 `environment_healthy` summarizes the full audit. `--target` adds a target check,
 but the report remains audit-wide unless a scope option is also supplied.
 
-An invalid `REA_LOG_LEVEL` fails every scope, including one client or the
-installed skill, because the executable rejects it before any command. A
-selected client also fails for every other setting that MCP startup rejects,
-including `REA_GHIDRA_STARTUP_TIMEOUT_MS` and `REA_HOPPER_STARTUP_TIMEOUT_MS`.
-Those settings still fail a selected provider and the audit-wide result. A
-skill-only report leaves them informational.
-
 Follow the remediation for the failed check. If a native target has several
 available providers, choose one with `--provider` on the CLI or `provider_id`
 on `open_binary`. A `capability_unavailable` failure carries
@@ -1193,10 +1182,8 @@ truncation markers. Darwin ownership-helper compilation failures also retain
 the compiler outcome, exit code or signal, and bounded stderr; a timed-out
 compiler remains distinguishable from a compiler that exited with an error.
 The helper compile deadline defaults to 120,000 ms; set
-`REA_SWIFTC_COMPILE_TIMEOUT_MS` to an integer between 1 and 2,147,483,647 in
-the environment that starts REA when a busy host needs longer. Restart REA to
-apply a change; the next ownership-helper compile uses the new value. A
-timeout names that effective deadline.
+`REA_SWIFTC_COMPILE_TIMEOUT_MS` to an integer between 1 and 2,147,483,647 when
+a busy host needs longer.
 On macOS, the Java prerequisite probe waits for this independently bounded
 preparation before starting its five-second command deadline. Caller cancellation
 still interrupts preparation, and failed helper cleanup remains owned for retry.

docs/javascript-artifact-reconstruction.md

@@ -106,18 +106,6 @@ only reduces delivery; source selection reduces text acquisition and analysis.
 Explicit native provider or snapshot routing rejects `--source-path` rather
 than ignoring it.
 
-ASAR header/index admission defaults to 16 MiB / 16777216 bytes. Set
-`REA_ASAR_MAX_HEADER_BYTES` in the environment that starts REA to a decimal
-byte count of at most 268435456 (256 MiB) to raise or lower it; restart REA
-after changing it. Invalid values are configuration errors, never a silent
-fallback. The archive index is read before any member can be selected, so
-`source_paths`, `--source-path`, `detail: "summary"`, `max_heap_mb`, and
-available host memory do not bypass or raise it. When the header exceeds the
-effective allowance, the failure names it, whether it came from the default or
-the setting, and the setting's limits. Alternatively, analyze an extracted
-application directory, which does not admit an ASAR header. Repeating the unchanged
-request fails the same way.
-
 ## Read the analysis
 
 `analyze_javascript_application` returns the complete analysis Evidence by
@@ -184,8 +172,7 @@ for the tool-result contract.
 
 Use MCP `detail: "summary"` for a large application, then read selected views of
 the retained analysis. Summary changes delivery only. To reduce source parsing,
-select exact [source paths](#select-sources-before-analysis). Source selection
-does not bypass ASAR header/index admission.
+select exact [source paths](#select-sources-before-analysis).
 
 If a complete response exceeds the transport budget, use its retained Evidence
 ID for a summary, module page, or item, or export the bundle. See
@@ -384,15 +371,7 @@ Recognized literal module-table bootstraps also support bounded lexical
 substitution through module exports, import helper bodies, local wrapper calls,
 returned closures, object spreads, and callback parameters. Recovered Electron
 paths retain source ranges, module identities, literal channels and branch
-conditions as static candidates. A channel the IPC call site itself
-determines, such as a local constant, resolves that call's observation rather
-than adding a second one. A channel or registration handler supplied through
-a wrapper argument is a candidate beside the call's own unresolved
-observation, because callers outside the traced paths may pass other values.
-A wrapper call that is both its own entry and reached through another entry
-is recorded once when both paths find the same facts; calls that supply
-different handlers or channels stay distinct.
-Unknown spreads, reassigned bindings, accessors,
+conditions as static candidates. Unknown spreads, reassigned bindings, accessors,
 dynamic channels and unsupported syntax do not become exact implementations.
 This pass neither executes the bundle nor proves that runtime guards pass.
 An ambiguous or unresolved handler retains its channel registration but does
@@ -610,9 +589,8 @@ The default semantic capacities are 100000 nodes across the application and
 `--max-semantic-nodes-per-file`), each from 1 to 1000000. The per-file offer is
 also bounded by the remaining application capacity. Raising these controls does
 not bypass worker heap, execution deadline or parent result admission. Truncated
-coverage lists both effective ceilings, `max_semantic_nodes` and
-`max_semantic_nodes_per_file`. The limitation names only the ceiling that
-stopped retention. Omitted relationships remain unknown.
+coverage reports both effective node ceilings; omitted relationships remain
+unknown.
 
 Unknown records have independent defaults of 100000 across the application and
 20000 per source. Select `max_semantic_unknowns` and
@@ -620,10 +598,8 @@ Unknown records have independent defaults of 100000 across the application and
 `--max-semantic-unknowns-per-file`), each from 1 to 1000000. The parent offers the
 remaining capacity to the worker, and rejects excess records before adoption.
 Unknown admission happens before canonical identity and provenance construction.
-When capacity is exhausted, coverage is partial and truncated. Coverage lists
-both effective unknown ceilings, `max_semantic_unknowns` and
-`max_semantic_unknowns_per_file`. The limitation names only the ceiling that
-stopped retention. `coverage.omitted_unknown_occurrences` counts examined
+When capacity is exhausted, coverage is partial and truncated and names both
+effective unknown ceilings. `coverage.omitted_unknown_occurrences` counts examined
 emission occurrences by family and reason, including repeated emissions. It does
 not claim distinct discarded identities or count frontiers in unexamined source.
 Omitted unknown provenance and IDs are not retained. Existing source, node,
@@ -636,35 +612,12 @@ checkpoint at its 8 MiB bound with the same 6x retention expansion used at
 admission. Earlier checkpoints are already charged to retained bytes; the
 remaining inventory does not multiply the reserve. Streamed file transfers keep the default 512 MiB
 allowance, and can grow with the parent's offered retention budget (8x byte
-expansion), up to 2 GiB. Individual records remain bounded to 8 MiB. The 8 MiB
-record ceiling and the 2 GiB file maximum have no runtime override, and raising
-`max_heap_mb` does not raise them. The effective file ceiling follows the
-parent's offered result budget. On Node, a larger CLI/MCP process heap
-(`NODE_OPTIONS`, for example `--max-old-space-size=<MiB>`, after restarting that
-process) can raise it up to 2 GiB. Selecting fewer `source_paths` can also
-raise that effective allowance, because the reserve for remaining sources and
-earlier retained results reduce the offered budget. Neither change raises the
-record ceiling or the 2 GiB maximum. The parent
+expansion), up to 2 GiB. Individual records remain bounded to 8 MiB. The parent
 still independently checks actual bytes, record overhead, digests and source
 identities before adopting results.
 
 A source that exhausts the analyzer heap does not terminate the CLI/MCP
-process. On Node, the failure names `max_heap_mb` (CLI `--max-heap-mb`), the
-effective mebibytes, the inclusive range 128 to 16384, and the 1024 MiB
-default. A changed value applies on the next analysis, which starts a new
-worker. It does not change a worker that is already running and does not
-require restarting the REA server. On Bun, the same heap-exhaustion diagnostic
-is not attributed to that V8 old-space limit, because Bun ignores the flag.
-Raising `max_heap_mb` does not raise the parent result budget,
-the transfer record ceiling, the 2 GiB transfer file maximum, the CLI/MCP
-process heap, or fixed parser limits. The parent result budget follows that
-process heap. On Node, set `NODE_OPTIONS` (for example `--max-old-space-size=<MiB>`)
-in the environment that starts the CLI or MCP server, then restart that
-process, to raise the parent heap and the result budget. A completed static
-checkpoint that does not fit the parent's remaining heap names that parent
-process heap. Increasing `max_heap_mb` does not raise it. On Node, the same
-`NODE_OPTIONS` restart can raise the parent heap and admit the checkpoint.
-Completed static facts are retained, other files can still be analyzed,
+process. Completed static facts are retained, other files can still be analyzed,
 and unexamined semantic relationships remain explicit unknowns. The parent
 also checks transfer expansion and accumulated results against its remaining
 heap before accepting semantic facts. A resource-limited result has partial

docs/javascript-recovery.md

@@ -129,15 +129,10 @@ equivalence remain unknown. No network fetching occurs.
 
 ## Resource policy and verification
 
-Each operation uses one worker, a 1 GiB address-space ceiling and a 120000 ms
-deadline. That deadline has no runtime override: raising `analysis_timeout_ms`
-or `max_heap_mb` does not raise it. An unchanged retry may hit the deadline
-again. The operation accepts up to 64 MiB of total
-input across all selected files and 128 MiB/10000 entries of staged output,
-with 8 MiB per diagnostic/report stream. A `provenance.json` over that report
-allowance names the fixed limit: this release has no runtime override, and
-raising `max_heap_mb` or `analysis_timeout_ms` does not raise it. Malformed
-reports stay distinct from that size refusal. Exceeding a limit is an explicit
+Each operation uses one worker, a 1 GiB address-space ceiling and a 120-second
+deadline; it accepts up to 64 MiB of total input across all selected files and
+128 MiB/10000 entries of staged
+output, with 8 MiB per diagnostic/report stream. Exceeding a limit is an explicit
 failure with rollback. Selected inputs beyond the total input allowance return a
 non-retryable `resource_constraint` with `resource: "file-size"` and
 `reported_limits.maximum_input_bytes`/`remaining_input_bytes`; input that is not

docs/javascript-runtime-reconciliation.md

@@ -106,12 +106,7 @@ nodes. REA evaluates compatible static candidates conservatively:
    that disagreement. If a mapped candidate's digest is unavailable and no
    mapped content match is known, the comparison remains `unknown`.
 6. Missing authorization mappings and incomplete or truncated input coverage
-   remain unknown or truncated rather than becoming absence claims. A runtime
-   location with no automatic artifact-root or caller-declared mapping into
-   any layer, and no content match, is `unknown` with
-   `no-authorized-location-mapping`, with or without captured bytes; several
-   content matches remain `ambiguous` under rule 4. Only a mapped location can
-   be `unmatched` with `no-static-content-match`.
+   remain unknown or truncated rather than becoming absence claims.
 
 Every successful cross-layer `observed_as` edge has
 `authority: cross-layer-reconciliation` and `state: inferred`. The underlying

docs/jeb-analysis.md

@@ -28,19 +28,17 @@ JEB service is reachable or that a project is open; use the existing
 MCP `binary_session` probes the live JEB service and its advertised tool catalog.
 Availability is reported per operation: a reachable headless client can support
 inspection and decompilation while refusing `open_jeb_project`. Catalog discovery
-is one deadline across connection and pagination; a responsive server cannot keep
-discovery running indefinitely by returning more pages.
+uses one 60-second deadline across connection and pagination; a responsive server
+cannot keep discovery running indefinitely by returning more pages.
 
-Catalog discovery and each `tools/call` share `REA_JEB_MCP_TIMEOUT_MS`. Set it
-in REA's launch environment to an integer from 1 to 2147483647 milliseconds,
-for example `REA_JEB_MCP_TIMEOUT_MS=300000` for a five-minute budget. Omitted
-means the pinned MCP client SDK default of 60000 ms (`@modelcontextprotocol/client`
-2.3.1). Restart REA and reconnect to apply a change. Raising the setting raises
-both phases. It does not make one end-to-end deadline across a whole CLI or MCP
-operation: discovery and each `tools/call` each get that budget. A request that
-reaches its budget returns a typed timeout naming the phase and the effective
-milliseconds, while caller cancellation remains a cancellation. Allow execution,
-cleanup, and delivery headroom in the outer MCP client deadline.
+Each upstream tool call has an absolute 60-second request deadline by default.
+Set `REA_JEB_MCP_TIMEOUT_MS` to a positive decimal number of milliseconds to
+select a different per-request budget, for example `REA_JEB_MCP_TIMEOUT_MS=300000`
+for a five-minute decompilation. This budget starts after discovery and applies
+to each individual `tools/call`; it does not extend the separate catalog deadline
+or establish one end-to-end deadline across a whole CLI or MCP operation. A
+request that reaches its budget returns a typed timeout, while caller
+cancellation remains a cancellation.
 
 Earlier verification used JEB 5.48.0 (Linux x64, licensed build) serving `jeb-mcp-server` 1.3.0 over streamable HTTP. The official Linux x64 CE build `5.48.0.202610071539` was also verified through real CLI and production stdio MCP native-code workflows; see the [Linux CE audit](../experiments/analysis-efficiency/jeb-linux-native.md) for measurements and limits. CE verification does not establish licensed/Demo Android decompilation or GUI behavior.
 

docs/kuna-provider.md

@@ -68,7 +68,7 @@ The background export belongs to the session. `close_binary`, or the end of a CL
 
 The assembly label index is scanned once per export reader. Cancelling a request stops its wait without interrupting other readers; closing the session aborts and drains the shared scan before releasing its files.
 
-Regex procedure and string search uses ECMAScript Unicode matching in a cancellable worker with a five-second matching deadline and a worker old-generation heap. Literal matching remains the default. Cancellation or a matching deadline leaves the session available. This release has no runtime override for that deadline. The worker requests 128 MiB. A positive Node.js `--max-old-space-size` on the process that starts REA, including `NODE_OPTIONS`, overrides that request and sets the effective heap. `--max-old-space-size-percentage` takes precedence over that flag in either order. REA does not turn the percentage into a MiB, so the effective heap stays unestablished instead of the 128 MiB request or the absolute flag. The reported `NODE_OPTIONS` value is the process initial environment when that block can be read. A later edit to the environment is not the value Node applied, and an unreadable initial value leaves the effective heap unestablished. The launch Node options are the initial command line on Linux when that buffer still has a program entry, not a later edit to `process.execArgv`. A preload can clear that array after V8 has applied the flags. Setting `process.title` or `--title` overwrites the command line, so a buffer without a program entry leaves the effective heap unestablished. `--env-file` or `--env-file-if-exists` can supply `NODE_OPTIONS` when the initial environment has none. That file is not part of the initial environment block, so the effective heap stays unestablished instead of the 128 MiB request. An initial `NODE_OPTIONS` is still used, because Node does not let the file replace it. A positive `--max-heap-size`, including the underscore form and launch `NODE_OPTIONS` on Node versions that allow it, sets the total heap rather than the old generation and can be lower than the 128 MiB request. The effective old generation stays unestablished while that value is in effect. A zero or empty value clears it. `--experimental-config-file` or `--experimental-default-config-file` can set `nodeOptions`, including a heap percentage, from a file that is not read back. The effective heap stays unestablished when either flag is present, including when an absolute `--max-old-space-size` is also on the command line or in the recovered `NODE_OPTIONS`. Node accepts the config path as `=` or the next argument.
+Regex procedure and string search uses ECMAScript Unicode matching in a cancellable worker with a five-second matching deadline. Literal matching remains the default. Cancellation or a matching deadline leaves the session available.
 
 Single-function subprocess output and each cached source facet share a 16 MiB buffered-text capacity. Cached spans are checked before allocation; larger text remains in the local export and the error identifies the file and range. `analyze_function` initially returns the complete dossier, which can still be large; later retained views do not remove that first transfer. Prefer the individual text tools for a focused question.
 

docs/managed-code-analysis.md

@@ -85,7 +85,7 @@ rejects selected summary before analysis; complete delivery remains available.
 
 Complete `inspect_managed_members` delivery always includes the assembly-wide
 `member_refs` and `exported_types`, which `type_names` does not narrow, so even
-one selected or unmatched type can return megabytes. In MCP, select
+one selected or unmatched type can return megabytes. Select
 `{"path":"/absolute/path/Assembly.dll","type_names":["Namespace.Type"],"detail":"summary"}`
 to keep the complete source in the session and receive identity, metadata
 status, the selection with its unmatched names, coverage/issues, the separate
@@ -115,49 +115,6 @@ literal pool's own coverage. Older Evidence that never examined exported types
 or user strings reports a null count and refuses those pages rather than
 returning an empty one.
 
-#### CLI summary and saved member rows
-
-The CLI accepts the same `complete` and `summary` detail choices. Omitted or
-`--detail complete` returns complete Evidence. To receive a summary, choose a
-new Evidence bundle destination so its original complete parent remains
-available after the command exits:
-
-```bash
-rea inspect-managed-members /absolute/path/Assembly.dll --type Namespace.Type \
-  --detail summary --evidence-bundle /absolute/path/evidence/members.json --json
-```
-
-`--evidence-bundle` writes the complete original Evidence in REA's canonical
-bundle format. Its parent directory must exist, and it never replaces an
-existing path. Relative paths resolve against the command's working directory.
-The option also works with complete delivery when a saved bundle is useful.
-Summary without a destination is rejected before analysis. A publication failure
-returns a typed error with the completed Evidence under
-`details.partial_observation`; it does not report successful summary delivery.
-Cancellation before publication prevents the new output. Once atomic
-publication has started, it can complete despite cancellation; a cancelled
-delivery then retains the committed path and byte count under
-`details.diagnostics.evidence_bundle`.
-
-Copy `normalized_result.parent_evidence_id` from the summary into the
-`source.evidence_id` field of the `managed-members` request above, then save that
-small request as `members-page.json` and run:
-
-```bash
-rea inspect-analysis-view /absolute/path/evidence/members-page.json \
-  --evidence-bundle /absolute/path/evidence/members.json --json
-```
-
-The view command authenticates the selected bundle and resolves that exact
-parent ID. It does not reopen the assembly, so the original target may have
-been moved or removed. Subsequent calls can select another collection or use
-the returned `coverage.next_offset` to continue the same collection. An inline
-source already includes its parent and cannot also select `--evidence-bundle`.
-
-Summary changes delivery, while type selection still controls decoding and the
-same inspection resource limits apply. Each separate CLI page reads and
-authenticates the saved bundle; the full source is retained on disk.
-
 ## Shipped scope
 
 The canonical parser admits PE/CLI bytes and their metadata/CIL without loading
@@ -665,9 +622,6 @@ which managed methods executed or how the CLR resolved them.
 
 Managed member comparisons report a `metadata` dimension when an observed
 MethodDef flags or implementation flags value differs, including accessibility
-or synchronization changes. Observed method-body `init_locals` and `max_stack`
-differences also contribute to `metadata`, even when CIL decoding is incomplete.
-An unavailable header value keeps body coverage unknown rather than establishing
-equality or a difference. These comparisons are separate from the CIL/signature
-matching tiers: identical instructions do not establish unchanged method metadata.
-The reported difference is static metadata evidence, not proof of runtime behavior.
+or synchronization changes. This is separate from the CIL/signature matching
+tiers: identical instructions do not establish unchanged method metadata. The
+reported difference is static metadata evidence, not proof of runtime behavior.

docs/mcp-contracts.md

@@ -95,10 +95,9 @@ optional bounded `recovery` next step. `recovery.kind=inspect_input_contract`
 names the rejected operation: re-read that operation's advertised input schema
 (call `tools/list` if the catalog may be stale), correct the listed fields, and
 do not repeat the unchanged call. `recovery.kind=inspect_timeout_state` names
-the operation and the REA server/provider deadline; inspect partial Evidence
-and reported cleanup state, then follow producer-specific remediation or reduce
-supported work. Generic errors do not assume adjustable timeout controls. Raising
-only the MCP client's deadline cannot extend this budget. These hints never
+the operation and the REA server/provider deadline; inspect session/provider
+state before retrying, and raise the MCP client's tool deadline only when the
+client ended the call before REA returned this response. These hints never
 include the complete catalog or caller arguments.
 Failures omit `structuredContent`, since each advertised `outputSchema`
 describes successful results. Successful replies retain their schema-validated
@@ -234,31 +233,11 @@ The destination changes only when a complete export is atomically published.
 
 Clients that explicitly configure a larger receive buffer can set the REA
 server's `REA_MCP_MAX_RESPONSE_BYTES` environment variable to the same byte
-count. This setting must be a safe decimal integer at least 10485760 (10 MiB);
-REA reserves 1024 bytes for the envelope. The value is read when the REA
-process starts, so a change requires a restart and a matching client receive
-buffer. Raising it restores complete inline delivery for responses that fit
-that buffer. It does not raise REA's reserved single-string limit, which is
-1024 UTF-16 code units below Node's single-string ceiling, and it does not
-raise that Node ceiling. It does not change analysis coverage or retained
-content. Ordinary responses keep their existing complete result contract.
-
-### Error recovery and deadline ownership
-
-Initialization instructions and the static JavaScript tool description teach
-recovery before a host can discard a tool response. Invalid input calls should be corrected from the connected schema
-(refresh `tools/list` only if stale), not retried unchanged. REA's returned
-`provider_timeout` describes its server/provider deadline; provider-authored
-remediation names the applicable controls and preserves partial Evidence and
-cleanup uncertainty.
-
-A host timeout without a REA result is different: execution and cleanup remain
-unknown. Increasing an advertised `analysis_timeout_ms` cannot fix a shorter
-client deadline. Configure the client's tool timeout with execution, cleanup
-and delivery headroom, or report that change is needed when not authorized.
-Session status does not establish that all target-free work stopped. Detailed
-host settings and bounded retry guidance live in the shipped skill's
-[recovery reference](https://github.com/morluto/rea/blob/main/.agents/skills/reverse-engineer-anything/references/connection-and-recovery.md#distinguish-client-and-server-deadlines).
+count. This setting must be a safe decimal integer at least 10485760; REA
+reserves 1024 bytes for the envelope. Raising it restores complete inline
+delivery for responses that fit that buffer and Node's single-string limit.
+It does not change the client's buffer, analysis coverage, or retained content.
+Ordinary responses keep their existing complete result contract.
 
 ### Untrusted target content
 
@@ -332,7 +311,7 @@ See [environment manifests](web-network-captures.md#environment-manifest).
 
 `inspect_analysis_view` also accepts `environment-state` for the same parents,
 extracting the initial state the recorded reads observed: entity types with an
-identity field, entities, documents for non-entity reads, and a render
+identity field, entities, documents for written non-entity paths, and a render
 plan per read tool that reproduces its recordings from the state or names why it
 cannot. Types and identity are inferences, so the Evidence is always inferred.
 See [environment state](web-network-captures.md#environment-state).
@@ -355,41 +334,10 @@ application and semantic coverage. The result carries a digest of the selected
 facts. Actual serialized size determines MCP transport admission: reduce the
 page size or export retained Evidence if the view is too large.
 
-`compare_source_to_bundle` accepts the committed historical graph inline or as
-`reference: {"kind":"file","path":"/absolute/reference.json"}`. The shared
-reader checks resource bounds and the graph's root commitment on every read. File-backed
-comparison Evidence records `parameters.reference_source`: the exact
-`requested_path` and the reader's absolute selected `path`, preserving POSIX
-`..`/symlink semantics. Normalized comparison facts and mapping identities agree
-with inline input; Evidence IDs distinguish caller-selected file origins.
-Omitting `view` preserves the complete comparison. For a compact initial reply,
-select `view: {"kind":"summary"}` or a `source-to-bundle` page; the session retains
-the complete comparison before delivery. Later calls use `inspect_analysis_view`
-with the returned `parent_evidence_id`.
-
-A `source-to-bundle` view selects `collection: "mappings"` or `"candidates"` with
-exact `source_paths`, `mapping_ids`, `statuses`, `fields`, `offset` and `limit`.
-Omitted filters select all; empty arrays select none. The default mapping fields
-include status, confidence, source digest/language and candidate/mapped counts.
-Candidate defaults include kind, score and confidence; request `signals` for exact
-supporting values. Mapping identity and `source_index` always remain; candidates
-also retain `current_node_id`, `candidate_index` and whether they were actually
-mapped. Indices refer to the complete comparison's item array and that item's
-candidate array. All classifications are computed before selection. The original
-`source_coverage` remains separate from page `coverage`; exhausting a page never
-turns unknown correspondence into absence or proves behavioral equivalence.
-
-The CLI accepts the same reference-file alternative (relative paths resolve from
-the working directory). Save its complete `--json` Evidence, then use
-`inspect-analysis-view` with an `evidence-file` source and the same view. Neither
-adapter executes the target or repeats analysis for retained queries.
-
 Completed `inspect_artifact` and atomic `inventory_artifact` Evidence also
 support summary and inventory views. A summary reports the manifest's expected
 counts separately from available record counts, observed entry kinds, inventory
-Evidence IDs, the inventory producer's traversal `source_coverage` and
-inspection coverage. Inspection coverage is `partial` when that traversal
-coverage is unknown. An inventory view selects `nodes`,
+Evidence IDs and inspection coverage. An inventory view selects `nodes`,
 `occurrences`, `edges`, or `integrity_contradictions`, with `offset` and `limit`
 defaulting to 0 and 64. For occurrences, optional `logical_paths` matches exact
 recorded strings: omission selects all available records; `[]` selects none.
@@ -562,17 +510,6 @@ concrete version, selection source, and complete analysis profile through
 choices return typed selection details. A selected provider is never replaced
 automatically after a runtime failure.
 
-`open_bundle_resources` selects a separate read-only app resource session
-without resolving `CFBundleExecutable`, including when it is absent or
-unresolvable. `binary_session` reports `session_kind: "bundle_resources"` and the
-caller and canonical resource-root paths; it does not report a binary target or
-deep-provider binding. `inspect_plist`, `decode_interface_builder`,
-`inspect_asset_catalog`, and `inspect_keyed_archive` retain resource-root
-provenance and use a null Evidence subject when executable identity is unknown.
-Binary-only operations and binary analysis snapshots do not apply in this
-session. `open_binary` can switch back to executable analysis, and
-`close_binary` retires either session kind.
-
 Each provider client receives `binary_session.analysis_run.run_id` before any
 provider startup, including clients whose startup fails. `process_lineage` is
 `not_observed` until a dynamic provider starts, then becomes `snapshots` with
@@ -839,13 +776,13 @@ auto-analysis, bridge connection, and health readiness before returning analysis
 
 These deadlines have different owners:
 
-| Deadline             | Owner and effect                                                                                                                                                                                                                                                                                                    |
-| -------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| MCP initialize       | The client bounds transport/REA connection startup, before any target query.                                                                                                                                                                                                                                        |
-| Hopper startup       | REA allows 120,000 ms by default; `REA_HOPPER_STARTUP_TIMEOUT_MS` accepts decimal integers from 1–2,147,483,647 ms. Invalid values fail configuration validation. Startup failure is reported by the first provider query.                                                                                          |
-| Ghidra startup       | REA allows 330,000 ms by default; `REA_GHIDRA_STARTUP_TIMEOUT_MS` accepts decimal integers from 1–2,147,483,647 ms. Invalid supplied values fail configuration validation. Startup failure is reported by the first provider query.                                                                                 |
-| Darwin swiftc helper | REA allows 120,000 ms by default for ownership-helper compilation; `REA_SWIFTC_COMPILE_TIMEOUT_MS` accepts decimal integers from 1–2,147,483,647 ms. Invalid values fail configuration validation. Set it in the environment that starts REA and restart REA; the next ownership-helper compile uses the new value. |
-| Individual tool call | The client bounds its wait, including cold engine startup. The pinned client SDK 2.3.1 defaults to 60,000 ms and can cancel earlier than REA's startup deadline.                                                                                                                                                    |
+| Deadline             | Owner and effect                                                                                                                                                                                                                    |
+| -------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| MCP initialize       | The client bounds transport/REA connection startup, before any target query.                                                                                                                                                        |
+| Hopper startup       | REA allows 120,000 ms by default; `REA_HOPPER_STARTUP_TIMEOUT_MS` accepts decimal integers from 1–2,147,483,647 ms. Invalid values fail configuration validation. Startup failure is reported by the first provider query.          |
+| Ghidra startup       | REA allows 330,000 ms by default; `REA_GHIDRA_STARTUP_TIMEOUT_MS` accepts decimal integers from 1–2,147,483,647 ms. Invalid supplied values fail configuration validation. Startup failure is reported by the first provider query. |
+| Darwin swiftc helper | REA allows 120,000 ms by default for ownership-helper compilation; `REA_SWIFTC_COMPILE_TIMEOUT_MS` accepts decimal integers from 1–2,147,483,647 ms. Invalid values fail configuration validation.                                  |
+| Individual tool call | The client bounds its wait, including cold engine startup. The pinned client SDK 2.3.1 defaults to 60,000 ms and can cancel earlier than REA's startup deadline.                                                                    |
 
 For [Codex and Kimi registrations](client-configuration.md), setup supplies
 missing tool deadlines from the known provider allowance plus 120 seconds of
@@ -853,8 +790,7 @@ operation headroom: 450 seconds with the default Ghidra allowance, or 2820
 seconds with `REA_GHIDRA_STARTUP_TIMEOUT_MS=2700000`. Positive caller-selected
 deadlines remain unchanged. Doctor reports an informational recommendation
 when a configured deadline is shorter than the known provider allowance. An
-explicit JEB upstream deadline (`REA_JEB_MCP_TIMEOUT_MS`, shared by catalog
-discovery and each tools/call) also contributes to that allowance.
+explicit JEB upstream request budget also contributes to that allowance.
 
 For an already connected client using the pinned SDK, request options are the
 **second** argument of `callTool`:
@@ -1053,15 +989,14 @@ verify the compact advertisement through the same client boundary.
 
 Some function-calling providers reject a request while any single tool's
 `parameters` schema exceeds a literal serialized size cap; Moonshot clients
-such as kimi-cli have reported failures with the full catalog attached
+such as kimi-cli fail every request while the default catalog is attached
 ([#1484](https://github.com/morluto/rea/issues/1484)). Setting the server's
-`REA_MCP_INPUT_SCHEMA_PROFILE` environment variable to `compact` (the default)
-renders every advertised input schema within a 13,312-byte budget, measured to sit below
+`REA_MCP_INPUT_SCHEMA_PROFILE` environment variable to `compact` renders every
+advertised input schema within a 13,312-byte budget, measured to sit below
 Moonshot's observed cap (community measurements: a 13.7 KB schema is accepted
 while a ~15 KB one is rejected). The setting is read at startup; restart the
-server to apply changes, as with `REA_MCP_MAX_RESPONSE_BYTES`. Explicitly select
-`full` to retain complete advertised input guidance and nested validation detail.
-Existing explicit profile choices are preserved. Compact presentation
+server to apply changes, as with `REA_MCP_MAX_RESPONSE_BYTES`. The default
+value `full` keeps the complete advertisement unchanged. Compact presentation
 also reduces schemas whose expanded JSON tree exceeds ten levels, the limit
 reported by strict-depth MCP clients in [#2813](https://github.com/morluto/rea/issues/2813).
 WorkBuddy/CodeBuddy gateways have also rejected full REA catalogs with an

docs/model-artifacts.md

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

docs/native-investigation.md

@@ -202,38 +202,8 @@ Function dossiers retain this same string evidence. Native call edges retain
 Hopper's partial `CallReference` classification and exact endpoints; detailed
 reference flags remain unavailable rather than being invented.
 Regex searches use ECMAScript Unicode syntax in a cancellable worker with a
-five-second matching deadline and a worker old-generation heap. Deadline or
-cancellation stops matching while leaving the Hopper API available. This
-release has no runtime override for that deadline. The worker requests 128
-MiB. A positive Node.js `--max-old-space-size` on the process that starts
-REA, including `NODE_OPTIONS`, overrides that request and sets the effective
-heap. `--max-old-space-size-percentage` takes precedence over that flag in
-either order. REA does not turn the percentage into a MiB, so the effective
-heap stays unestablished instead of the 128 MiB request or the absolute flag.
-The reported `NODE_OPTIONS` value is the process initial environment when that
-block can be read. A later edit to the environment is not the value Node
-applied, and an unreadable initial value leaves the effective heap
-unestablished. The launch Node options are the initial command line on Linux
-when that buffer still has a program entry, not a later edit to
-`process.execArgv`. A preload can clear that array after V8 has applied the
-flags. Setting `process.title` or `--title` overwrites the command line, so a
-buffer without a program entry leaves the effective heap unestablished.
-`--env-file` or `--env-file-if-exists` can supply `NODE_OPTIONS`
-when the initial environment has none. That file is not part of the initial
-environment block, so the effective heap stays unestablished instead of the
-128 MiB request. An initial `NODE_OPTIONS` is still used, because Node does
-not let the file replace it. A positive `--max-heap-size`, including the
-underscore form and launch `NODE_OPTIONS` on Node versions that allow it,
-sets the total heap rather than the old generation and can be lower than the
-128 MiB request. The effective old generation stays unestablished while that
-value is in effect. A zero or empty value clears it.
-`--experimental-config-file` or `--experimental-default-config-file` can set
-`nodeOptions`, including a heap percentage, from a file that is not read
-back. The effective heap stays unestablished when either flag is present,
-including when an absolute `--max-old-space-size` is also on the command
-line or in the recovered `NODE_OPTIONS`. Node accepts the config path as
-`=` or the next argument.
-Literal mode retains Unicode casefold matching.
+five-second matching deadline. Deadline or cancellation stops matching while
+leaving the Hopper API available. Literal mode retains Unicode casefold matching.
 
 ## Bounded static traces
 
@@ -328,25 +298,13 @@ markup, including UTF-8 and BOM-marked UTF-16 sources. Unidentified text and
 OpenStep plists, including a data-only value such as `<deadbeef>`, report
 `unknown` even when plutil decodes their values through an XML conversion.
 
-Binary plist inspection reads the original bytes through an owned file descriptor,
-so conversion cannot erase control characters, fractional dates, negative zero,
-or the high word of a 128-bit integer. It accepts at most 64 MiB of input and
-reserves an estimated 64 MiB decode budget before parsing; this estimate is not
-a hard process-memory bound. A refused input reports non-retryable
-`resource_constraint` with `reported_limits.maximum_input_bytes`,
-`maximum_decoded_bytes` or, for nesting deeper than 128 levels,
-`maximum_nesting_depth`. These are fixed allowances: worker limits and host
-memory do not raise them, and the unchanged request fails the same way.
-Binary-source provenance records the `file` classification without claiming a
-`plutil` conversion.
-
 A plist explicitly selected through the path input or as the active plist target
 reports an unreadable or malformed selection as `invalid_request`. A missing or
 unreadable default plist of another target reports `capability_unavailable`.
 Permission failures remain `access_denied`; output and cleanup failures retain
 their own error categories.
 
-A conversion refusal includes plutil's diagnostic from either output stream.
+A plist decode refusal includes plutil's diagnostic from either output stream.
 `details.captured_output` retains bounded stdout/stderr excerpts, observed byte
 totals and exit status. `truncated: true` means those excerpts are incomplete.
 
@@ -467,40 +425,10 @@ complete observation.
   vtable descriptors. Records include exact virtual addresses/file offsets and
   artifact evidence. Vtable indexes are metadata word offsets; witness indexes
   start after the conformance header. Names unavailable in metadata remain null.
-  The byte reader holds the whole selected file in memory, so it admits files up
-  to 64 MiB / 67108864 bytes by default. Select a larger budget with
-  `max_input_bytes` (CLI `--max-input-bytes`), at most 1 GiB / 1073741824
-  bytes. The whole file counts, including every slice of a universal Mach-O.
-  Results record `input_admission` with the effective budget, its source
-  (`default` or `caller`) and the bytes retained. A refusal names the observed
-  file size, the effective budget and its source, and either the budget to
-  select or, above 1 GiB, a deep analysis provider.
-  The `swift_class_vtable_descriptors` coverage counters count examined vtable
-  slots and successfully decoded slots, rather than type-section entries.
-  The `objc_class_method_ivar_metadata` counters count admitted class and
-  metaclass objects and successfully decoded objects.
   Pointers are decoded through the image's fixups:
   - `LC_DYLD_CHAINED_FIXUPS` rebases and binds, including the authenticated
     arm64e formats;
-  - legacy `LC_DYLD_INFO` rebase and bind opcodes.
-
-  A Swift conformance whose type or protocol reference is an external bind
-  keeps its name as `null` and carries the raw dyld identity in
-  `type_binding` or `protocol_binding`; that record and its facet coverage are
-  partial. Consumers of this output must handle nullable conformance names
-  and use the typed binding fields instead of substituting a symbol as a
-  display name. Indirect relative-pointer records also retain their binding
-  identity. A decoded rebase to virtual address zero remains an address; only
-  an unfixed zero in a nullable ABI field is treated as null. Incomplete or
-  conflicting fixup streams keep affected pointers unresolved; coverage reports
-  parsing and resource limits while retaining validated prefix facts.
-  Conformance records preserve the raw three-bit `type_reference_kind`. Kinds
-  0 and 1 identify direct and indirect nominal descriptors; kind 2 preserves
-  the inline Objective-C class name and its source location. Kind 3 preserves
-  an imported class binding or the local class-object address when available,
-  but class metadata/name recovery requiring the Objective-C runtime remains
-  partial. Unknown kinds retain the raw kind and reference location without
-  being treated as absent or assigned a guessed type name.
+  - legacy `LC_DYLD_INFO` bind opcodes.
 
   So an external superclass resolves from its `_OBJC_CLASS_$_` bind (for
   example `NSObject`). The `pointer_fixups` coverage facet names the mechanism.
@@ -538,21 +466,6 @@ complete observation.
   that operation is unavailable; runtime failures remain failures rather than
   being replaced by symbol-only results.
 
-`get_objc_classes` keeps names from the provider inventory. It coalesces rows
-only when their exact selected-image pointer slots decode to the same class
-import, including its binding stream, raw library ordinal, resolved library, weak status, and addend. A literal filter is
-applied to the original names before that join; if the filter selects only an
-alias, the output keeps that exact row. `identity_coverage` distinguishes a
-complete selected-inventory scan from partial, unsupported, and unknown cases.
-Recognized Mach-O formats outside the native metadata reader's support retain
-the provider's class labels with unknown import identity; malformed headers and
-read failures remain errors.
-The join also requires matching whole-artifact digests and matching provider-
-owned selected-image facts: container, byte range, full raw CPU type/subtype,
-and FAT table digest when present. A missing or overridden loader selection
-remains unknown; the result describes agreement on the selected artifact image,
-not an atomic observation of a running process or whole-program class coverage.
-
 ## Native desktop observation
 
 `observe_native_ui` captures one explicitly selected existing PID/window ID.
@@ -575,10 +488,8 @@ cleanup. A later abort does not replace an earlier helper or output failure.
 Cleanup failures retain their runtime owner until a confirmed cleanup retry.
 
 Scenarios accept caller-selected action lists and accessibility node counts.
-One wait step stays capped at 180000 ms. That cap has no runtime override.
-The operation deadline is `native_ui_deadline_ms` (omitted means 180000 ms)
-and does not raise the wait-step cap. The complete scenario result has a
-64 MiB output budget. Screenshots are scaled to
+Individual waits cannot exceed the operation's 180-second deadline, and the
+complete scenario result has a 64 MiB output budget. Screenshots are scaled to
 at most 2,048 pixels and captured only for the selected window. REA compiles one
 owned helper per scenario, removes its temporary compiler cache and stops its
 helper on cancellation. It does not launch or own the selected application. UI
@@ -773,13 +684,7 @@ leap seconds) and out-of-range dates remain explicit unknowns. REA does not
 emulate CoreFoundation's normalization of overflowing calendar fields. Invalid
 dates returned by other decoders retain `{ "$plist_type": "date", "iso8601": null }`
 with a counted limitation. `inspect_plist` and Interface Builder decoding use
-the same projection. Binary plist decoding refuses a reachable date whose marker
-is not `0x33`; date and numeric payloads must end before the offset table.
-Valid overlapping object records retain their independent source values. A valid `0x33` date is
-reported with an ISO-8601 timestamp only when its float64 seconds are exactly
-the canonical encoding of that millisecond instant. Any other finite binary
-date uses `{ "$plist_type": "date", "iso8601": null }` and the counted
-limitation; the archive bytes remain the source of the instant.
+the same projection.
 
 A negative-zero real is reported as `{ "$plist_type": "real", "value": "-0" }`
 because a JSON number cannot carry the sign of zero. `inspect_plist` and

docs/pcap-analysis.md

@@ -67,11 +67,7 @@ Addresses count once per packet, including loopback and nested IP occurrences.
 DNS addresses are associated only with one question in the same response packet;
 additional records may be included, so this does not prove final resolution.
 Ambiguous addresses remain in a separate inventory. Protocol distribution counts
-exact nonempty `frame.protocols` stack strings. Frames for which TShark reports
-an empty stack, including zero-length packets, still contribute to the packet
-count without adding a protocol row. An all-empty stack inventory can have
-complete examined coverage; it does not establish the absence of network traffic.
-TLS SNI is recorded handshake metadata,
+exact `frame.protocols` stack strings. TLS SNI is recorded handshake metadata,
 not process identity or proof of the destination's authenticity.
 
 All examined inventories are retained within the resource budget; no fixed

docs/pe-certificates.md

@@ -1,49 +0,0 @@
-# PE Authenticode certificate tables
-
-`inspect_pe_certificates` / `inspect-pe-certificates` answers whether one
-selected local PE32/PE32+ image declares an `IMAGE_DIRECTORY_ENTRY_SECURITY`
-table, which `WIN_CERTIFICATE` entries that table stores, and which PKCS#7
-signer and X.509 fields those entries carry. It reads the file without
-executing it and does not require a Windows SDK, catalog file, or disassembler.
-
-```bash
-rea inspect-pe-certificates /absolute/path/to/application.exe --json
-```
-
-The CLI resolves relative paths against the caller's working directory. MCP
-requires an absolute filesystem path and preserves that exact selection:
-
-```json
-{
-  "name": "inspect_pe_certificates",
-  "arguments": { "path": "/artifacts/application.exe" }
-}
-```
-
-## Observations
-
-The inline Evidence result contains the artifact path, SHA-256, and byte length.
-`table` is the file-offset security directory, or `null` when the directory is
-absent or zero. Each `entries[]` item reports `WIN_CERTIFICATE` length,
-revision, type, and the payload SHA-256.
-
-For `WIN_CERTIFICATE` type 2 (PKCS#7 signedData) `pkcs7` contains digest
-algorithm OIDs, embedded X.509 serial/issuer/subject/validity fields, and
-signer identifier facts. Other certificate types keep `pkcs7` null.
-
-A missing table is observed absence of that directory. It is not proof the
-image is unsigned in every catalog or overlay sense.
-
-## Limits and failures
-
-The selected file is limited to 64 MiB by default (512 MiB maximum). At most
-eight `WIN_CERTIFICATE` entries are examined by default. Malformed PE headers,
-truncated certificate entries, and PKCS#7 that is not structurally signedData
-fail without partial success. A security directory that ends in fewer than
-eight header bytes, including zeros, is a truncated `WIN_CERTIFICATE` and
-fails the same way. SignedData must contain at least one `SignerInfo`, and
-each `SignerInfo` must carry a non-empty signature value. Decoded certificate
-name text shares a 64 KiB budget per PKCS#7 payload.
-
-This workflow does not verify signatures, certificate chains, timestamps, or
-Authenticode digest coverage of image bytes.

docs/process-capture.md

@@ -461,33 +461,7 @@ selected roots; it is not a per-file allowance. File contents are read in
 
 Ownership inspections bind run-token reads to native start identities and retain
 related generations through reparenting, group changes, omitted rows, and cleanup
-retries. A host without native identity reads still token-checks process-table
-rows that appear only in a launcher-exit refresh before reporting that group
-clean or publishing an empty lineage. A matching token authorizes a signal only
-for a group whose leader carries the same token. A matching token whose leader
-is absent, or an unreadable token for a still-live new row, stays unresolved. A
-readable foreign token is not signaled. An unreadable row that has exited by
-the confirmation read does not hide a new row in that confirmation table, and a
-group proven while revalidating another owned group is signaled in the same
-cleanup. A matched row that changes parent or group on the confirmation read
-is token-checked again. A PID whose token was already read is read again
-on the next confirmation even when its parent and group return to the
-pre-exit values. A PID whose first token was foreign is read again
-on that table, because the PID alone does not identify the process. A PID
-from the pre-exit table is read again when its parent or group changes, and
-an unchanged pre-existing row that was never token-read stays unread. Lineage
-publishes one row for each PID. Confirmation reads are bounded; a table that keeps producing unreadable
-replacements stays unresolved. That refresh does not retain a ledger
-for a later attempt that never observes the launcher. Lineage reads a row again
-when its parent, group, or launcher-tree membership changes, and it reads a
-token again on the next refresh even when those fields are unchanged. The
-launcher is read on every lineage refresh; a missing, unowned, or
-relation-changed launcher PID is not published as a verified lineage. A
-descendant absent from the latest refresh is omitted. An
-ancestor move cannot leave a foreign descendant inside a verified result. A
-group that reappears after cleanup already processed it is revalidated once;
-another appearance stays unresolved. The captured run keeps
-one evidence owner through settlement and cleanup.
+retries. The captured run keeps one evidence owner through settlement and cleanup.
 An absent or changed token leaves a previously related generation unresolved;
 current token proof is still required before signaling. Swept cleanup verifies the
 remaining family after its group signals. Coverage is bounded by the native
@@ -545,15 +519,6 @@ missing or relative SDK/compiler path fails with an actionable prerequisite
 error before compilation. An incompatible installation reports the compiler's
 bounded diagnostics; REA does not repair or replace the toolchain.
 
-The compile deadline is `REA_SWIFTC_COMPILE_TIMEOUT_MS`. An omitted value is
-120,000 ms, and accepted values are integers from 1 to 2,147,483,647. REA reads
-the variable from the environment that starts the process and keeps that
-deadline for every helper compile in that process. Restart REA to apply a
-change; the next ownership-helper compile uses the new value. A timeout names
-the effective milliseconds. Invalid values fail configuration validation at
-startup. Embedded compiler diagnostics are cut at 512 bytes, and this release
-has no runtime override for that excerpt.
-
 For example, select paths from your existing Xcode or Command Line Tools
 installation **before** entering an enforced write boundary:
 

docs/python-packaged-applications.md

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

docs/readme/README_ar.md

@@ -143,7 +143,6 @@ npx rea-agents@latest setup
 | ------------------------------- | ---------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------- |
 | الملفات الثنائية للشيفرة الأصلية | شيفرة شبه برمجية، وتعليمات تجميع، وسلاسل نصية، ورموز، واستدعاءات، ومراجع                                    | Hopper أو Ghidra أو IDA؛ [تحليل الشيفرة الأصلية](../native-investigation.md)                                                   |
 | بنية ELF دون تشغيل              | الأقسام والمقاطع والرموز ومعلومات إعادة التموضع الأصلية، وآليات الحماية المحتملة المستدلّ عليها بالفحص الثابت | pwntools يوفّره المستدعي على Linux x64؛ [تشخيص الملفات الثنائية](../binary-diagnostics.md)                                     |
-| PE certificates                 | Authenticode WIN_CERTIFICATE entries and PKCS#7 signer/X.509 identity fields                               | Built-in static PE inspection; [PE certificates](../pe-certificates.md)                                                       |
 | شيفرة EVM البايتية              | محددات التوجيه، وإزاحات البايتات، والمعاملات المستنتجة، وقابلية تغيير الحالة                                | مدخل محلي يحمل بايتات خامًا أو تمثيلًا سداسيًا عشريًا على Linux x64؛ [دليل EVM دون تشغيل](../evm-bytecode.md)                      |
 | Rust binaries                   | Embedded cargo-auditable dependency list                                                                   | [Rust binaries](../rust-binaries.md)                                                                                          |
 | أعطال Linux المسجّلة             | سجلات note الخام، ومسجّلات المعالج/الإشارات لكل خيط مسجّل، وترشيحات اختيارية لخرائط الذاكرة                     | pwntools يوفّره المستدعي على Linux x64؛ GDB/pwndbg اختياريان؛ [الأعطال المسجّلة](../recorded-crashes.md)                         |
@@ -153,7 +152,6 @@ npx rea-agents@latest setup
 | تسجيلات الشبكة المحفوظة          | الطلبات، والاستجابات، ومحتويات الحمولة المتاحة، ومواضعها في المصدر                                          | HAR؛ وmitmdump على Linux لتسجيلات mitmproxy بصيغتها الأصلية؛ [دليل تسجيلات الشبكة](../web-network-captures.md)                   |
 | التقاط الحزم                    | نقاط النهاية وDNS وTLS SNI وتوزيع البروتوكولات وطلبات HTTP                                                  | tshark وcapinfos يوفّرهما المُستدعي؛ [دليل pcap](../pcap-analysis.md)                                                           |
 | تجميعات .NET                    | البيانات الوصفية، وتعليمات CIL، واعتماديات الشيفرة الأصلية المعلنة، ومقارنات البناء                         | فحص ثابت؛ [دليل الشيفرة المُدارة](../managed-code-analysis.md)                                                                 |
-| PyInstaller                     | CArchive, PYZ, Python bytecode                                                                             | Static inspection; [Python packaged applications](../python-packaged-applications.md)                                         |
 | حزم Android APK                 | تصريحات ملف manifest، والأصناف، والدوال الناتجة عن فك الترجمة، والمراجع                                     | JADX دون واجهة رسومية وJDK كامل على Linux/macOS/Windows x64؛ [دليل Android](../android-analysis.md)                           |
 | أجهزة Android                   | الأجهزة والحزم والعمليات والسجلات والدامبات ولقطات الشاشة ونقل APK/الملفات                                   | adb يوفّره المُستدعي (محاكي أو جهاز)؛ [دليل ADB](../adb-device-analysis.md)                                                     |
 | مشاريع JEB                      | وحدات المشروع من المحرك وبصمات المصنّفات والكود الزائف للأنواع/الدوال                                        | عميل JEB يبدأه المُستدعي ويقدّم MCP، ويُختار عبر REA_JEB_MCP_URL؛ [دليل JEB](../jeb-analysis.md)                                 |
@@ -268,8 +266,6 @@ npx rea-agents@latest setup
 
 - [التثبيت والإعداد](../installation.md): تسجيل الوكلاء، وتهيئة الموفّرين، والتحديثات، وإلغاء التثبيت.
 - [الجاهزية واستكشاف الأخطاء](../installation.md#check-readiness-for-your-task): تشخيص وكيل أو محرك تحليل محدد.
-- [CUDA / HIP](../gpu-code-objects.md)
-- [GGUF / safetensors](../model-artifacts.md)
 - [CLI وEvidence](../cli.md): الأوامر، واختيار الموفّر، واللقطات، والاستيراد/التصدير، وحالات الخروج.
 - [عقود MCP](../mcp-contracts.md) و[تعليمات الوكلاء](../mcp-prompts.md): نتائج الأدوات، والجلسات، والاستقصاءات الموجّهة.
 - [كتالوج الأدوات](../mcp-contracts.md#generated-catalog): قائمة الأدوات والموفّرين وأوامر CLI المولّدة أثناء البناء.

docs/readme/README_de.md

@@ -143,7 +143,6 @@ REA benötigt Node.js 22.x (>=22.19), 24.x (>=24.11) oder 26+ sowie npm. Zusätz
 | ----------------------------------- | --------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------- |
 | Native Binärdateien                 | Pseudocode, Assemblercode, Zeichenketten, Symbole, Aufrufe und Verweise                                         | Hopper, Ghidra oder IDA; [native Analyse](../native-investigation.md)                                                                       |
 | Offline-ELF-Struktur                | Sektionen, Segmente, ursprüngliche Symbole/Relokationen und mögliche Schutzmaßnahmen aus statischer Analyse     | Vom Aufrufer bereitgestelltes pwntools unter Linux x64; [Binärdiagnostik](../binary-diagnostics.md)                                         |
-| PE certificates                     | Authenticode WIN_CERTIFICATE entries and PKCS#7 signer/X.509 identity fields                                    | Built-in static PE inspection; [PE certificates](../pe-certificates.md)                                                                     |
 | EVM-Bytecode                        | Dispatch-Selektoren, Byte-Offsets, abgeleitete Argumente und Veränderbarkeit des Zustands                       | Lokale Eingabe mit Rohbytes oder Hexdarstellung unter Linux x64; [Offline-EVM-Leitfaden](../evm-bytecode.md)                                |
 | Rust binaries                       | Embedded cargo-auditable dependency list                                                                        | [Rust binaries](../rust-binaries.md)                                                                                                        |
 | Aufgezeichnete Linux-Abstürze       | Unverarbeitete Note-Einträge, Register/Signale aller aufgezeichneten Threads und optionale Zuordnungskandidaten | Vom Aufrufer bereitgestelltes pwntools unter Linux x64; optional GDB/pwndbg; [aufgezeichnete Abstürze](../recorded-crashes.md)              |
@@ -153,7 +152,6 @@ REA benötigt Node.js 22.x (>=22.19), 24.x (>=24.11) oder 26+ sowie npm. Zusätz
 | Gespeicherte Netzwerkaufzeichnungen | Anfragen, Antworten, zugängliche Nutzdaten und Quellpositionen                                                  | HAR; mitmdump unter Linux für Aufzeichnungen im nativen mitmproxy-Format; [Leitfaden zu Netzwerkaufzeichnungen](../web-network-captures.md) |
 | Paketerfassungen                    | Endpunkte, DNS, TLS SNI, Protokollverteilung und HTTP-Anfragen                                                  | Vom Aufrufer bereitgestellte tshark- und capinfos-Binaries; [pcap-Leitfaden](../pcap-analysis.md)                                           |
 | .NET-Assemblies                     | Metadaten, CIL-Anweisungen, deklarierte native Abhängigkeiten und Build-Vergleiche                              | Statische Untersuchung; [Leitfaden für verwalteten Code](../managed-code-analysis.md)                                                       |
-| PyInstaller                         | CArchive, PYZ, Python bytecode                                                                                  | Static inspection; [Python packaged applications](../python-packaged-applications.md)                                                       |
 | Android-APKs                        | Manifest-Deklarationen, Klassen, dekompilierte Methoden und Verweise                                            | JADX ohne grafische Oberfläche und ein vollständiges JDK unter Linux/macOS/Windows x64; [Android-Leitfaden](../android-analysis.md)         |
 | Android-Geräte                      | Geräte, Pakete, Prozesse, Logs, Dumps, Bildschirmaufnahmen sowie APK- und Dateiübertragungen                    | Vom Aufrufer bereitgestelltes adb (Emulator oder Gerät); [ADB-Leitfaden](../adb-device-analysis.md)                                         |
 | JEB-Projekte                        | Engine-gestützte Projekteinheiten, Artefakt-Prüfsummen und Pseudokode von Typen/Methoden                        | Ein vom Aufrufer gestarteter JEB-Client mit MCP, ausgewählt über REA_JEB_MCP_URL; [JEB-Leitfaden](../jeb-analysis.md)                       |
@@ -266,8 +264,6 @@ Beginne mit den [praxisnahen Anleitungen](https://rea.tools/de/guides/) auf der
 
 - [Installation und Einrichtung](../installation.md): Agentenregistrierung, Provider-Konfiguration, Updates und Deinstallation.
 - [Bereitschaft und Fehlerbehebung](../installation.md#check-readiness-for-your-task): Diagnose eines bestimmten Agenten oder einer Analyse-Engine.
-- [CUDA / HIP](../gpu-code-objects.md)
-- [GGUF / safetensors](../model-artifacts.md)
 - [CLI und Evidence](../cli.md): Befehle, Provider-Auswahl, Snapshots, Import/Export und Exit-Status.
 - [MCP-Kontrakte](../mcp-contracts.md) und [Agenten-Prompts](../mcp-prompts.md): Werkzeugergebnisse, Sitzungen und geführte Untersuchungen.
 - [Werkzeugkatalog](../mcp-contracts.md#generated-catalog): Beim Build erzeugtes Inventar von Werkzeugen, Providern und CLI-Befehlen.

docs/readme/README_el.md

@@ -149,7 +149,6 @@ npx rea-agents@latest setup
 | Δομή ELF χωρίς εκτέλεση                | Ενότητες, τμήματα, αρχικά σύμβολα/εγγραφές μετεγκατάστασης και ενδείξεις πιθανών μέτρων προστασίας από στατική ανάλυση      | pwntools που παρέχει ο χρήστης σε Linux x64· [διαγνωστικά δυαδικών αρχείων](../binary-diagnostics.md)                               |
 | Δυαδικά αρχεία Go                      | Ενσωματωμένη έκδοση μεταγλωττιστή, modules, αντικαταστάσεις και ρυθμίσεις μεταγλώττισης                                     | Ενσωματωμένη στατική εξέταση ELF/PE/thin Mach-O· δεν απαιτείται εγκατάσταση του Go                                                  |
 | Δυαδικά αρχεία Rust                    | Ενσωματωμένα ονόματα, εκδόσεις, πηγές και σχέσεις εξάρτησης των crates από το cargo-auditable                               | Ενσωματωμένη στατική εξέταση ELF/PE/thin Mach-O· [δυαδικά αρχεία Rust](../rust-binaries.md)                                         |
-| PE certificates                        | Authenticode WIN_CERTIFICATE entries and PKCS#7 signer/X.509 identity fields                                                | Built-in static PE inspection; [PE certificates](../pe-certificates.md)                                                             |
 | Αρχείο WASM                            | Έλεγχο εγκυρότητας, ενότητες, ακριβείς μορφές εισαγωγών/εξαγωγών σε WAT και αποκωδικοποιημένο WAT                           | WABT 1.0.42 που παρέχει ο χρήστης· `inspect_wasm_artifact`                                                                          |
 | Bytecode EVM                           | Selectors επιλογής συνάρτησης, μετατοπίσεις σε bytes, εκτιμώμενα ορίσματα και δυνατότητα μεταβολής της κατάστασης           | Τοπική είσοδος σε ακατέργαστα bytes ή δεκαεξαδική μορφή σε Linux x64· [οδηγός EVM χωρίς εκτέλεση](../evm-bytecode.md)               |
 | Βάσεις δεδομένων SQLite                | Πίνακες, στήλες, ευρετήρια, όψεις, triggers και επιλεγμένες γραμμές κανονικών πινάκων                                       | Τοπικό στιγμιότυπο βάσης δεδομένων/WAL· Node.js 24.x >=24.15 ή 26+ με εγγενή όρια SQLite                                            |
@@ -159,7 +158,6 @@ npx rea-agents@latest setup
 | Ιστότοποι                              | Δομή σελίδων, scripts, παρατηρήσεις δικτύου και ζητούμενα στιγμιότυπα οθόνης                                                | Πρόγραμμα περιήγησης της οικογένειας Chrome· [ανάλυση μέσω προγράμματος περιήγησης](../browser-observation.md)                      |
 | Αποθηκευμένες καταγραφές δικτύου       | Αιτήματα, αποκρίσεις, διαθέσιμα δεδομένα φορτίου και θέσεις στην πηγή                                                       | HAR ή SAZ του Fiddler Everywhere· mitmdump σε Linux για την εγγενή μορφή mitmproxy· [οδηγός καταγραφών](../web-network-captures.md) |
 | Assemblies .NET                        | Μεταδεδομένα, εντολές CIL, δηλωμένες εξαρτήσεις από κώδικα μηχανής και συγκρίσεις builds                                    | Καμία πρόσθετη απαίτηση (μόνο στατική ανάλυση)· [οδηγός διαχειριζόμενου κώδικα](../managed-code-analysis.md)                        |
-| PyInstaller                            | CArchive, PYZ, Python bytecode                                                                                              | Static inspection; [Python packaged applications](../python-packaged-applications.md)                                               |
 | APK Android                            | Δηλώσεις manifest, κλάσεις, απομεταγλωττισμένες μέθοδοι και αναφορές                                                        | JADX χωρίς γραφικό περιβάλλον και πλήρες JDK σε Linux/macOS/Windows x64· [οδηγός Android](../android-analysis.md)                   |
 | Συσκευές Android                       | Συσκευές, πακέτα, διεργασίες, logs, dumps, στιγμιότυπα οθόνης και μεταφορές APK/αρχείων                                     | adb που παρέχει ο χρήστης (εξομοιωτής ή φυσική συσκευή)· [οδηγός ADB](../adb-device-analysis.md)                                    |
 | Έργα JEB                               | Μονάδες έργου από τη μηχανή ανάλυσης, ψηφιακά αποτυπώματα αρχείων και ψευδοκώδικα τύπων/μεθόδων                             | Client JEB που έχει ξεκινήσει ο χρήστης και παρέχει MCP, επιλεγμένος μέσω REA_JEB_MCP_URL· [οδηγός JEB](../jeb-analysis.md)         |
@@ -279,8 +277,6 @@ npx rea-agents@latest setup
 
 - [Εγκατάσταση και ρύθμιση](../installation.md): καταχώριση agents, ρύθμιση παρόχων ανάλυσης, ενημερώσεις και απεγκατάσταση.
 - [Έλεγχος ετοιμότητας και αντιμετώπιση προβλημάτων](../installation.md#check-readiness-for-your-task): διάγνωση ενός agent ή μιας μηχανής ανάλυσης.
-- [CUDA / HIP](../gpu-code-objects.md)
-- [GGUF / safetensors](../model-artifacts.md)
 - [CLI και Evidence](../cli.md): εντολές, επιλογή παρόχου, στιγμιότυπα, εισαγωγή/εξαγωγή και κωδικοί εξόδου.
 - [Προδιαγραφές MCP](../mcp-contracts.md) και [prompts για agents](../mcp-prompts.md): αποτελέσματα εργαλείων, συνεδρίες και καθοδηγούμενες διερευνήσεις.
 - [Κατάλογος εργαλείων](../mcp-contracts.md#generated-catalog): αυτόματα παραγόμενος κατάλογος εργαλείων, παρόχων και εντολών CLI.

docs/readme/README_es.md

@@ -143,7 +143,6 @@ REA requiere Node.js 22.x (>=22.19), 24.x (>=24.11) o 26+, además de npm. Las h
 | --------------------------- | ------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------- |
 | Binarios nativos            | Pseudocódigo, ensamblador, cadenas, símbolos, llamadas y referencias                                                           | Hopper, Ghidra o IDA; [análisis nativo](../native-investigation.md)                                                                    |
 | Estructura ELF sin ejecutar | Secciones, segmentos, símbolos/reubicaciones originales y posibles medidas de mitigación detectadas mediante análisis estático | pwntools proporcionado por quien llama, en Linux x64; [diagnóstico de binarios](../binary-diagnostics.md)                              |
-| PE certificates             | Authenticode WIN_CERTIFICATE entries and PKCS#7 signer/X.509 identity fields                                                   | Built-in static PE inspection; [PE certificates](../pe-certificates.md)                                                                |
 | Bytecode EVM                | Selectores de despacho, desplazamientos en bytes, argumentos inferidos y mutabilidad                                           | Entrada local con bytes sin procesar o representación hexadecimal, en Linux x64; [guía de EVM sin ejecutar](../evm-bytecode.md)        |
 | Rust binaries               | Embedded cargo-auditable dependency list                                                                                       | [Rust binaries](../rust-binaries.md)                                                                                                   |
 | Fallos de Linux registrados | Registros note sin procesar, registros/señales de cada hilo registrado y posibles correspondencias de memoria opcionales       | pwntools proporcionado por quien llama, en Linux x64; GDB/pwndbg opcionales; [fallos registrados](../recorded-crashes.md)              |
@@ -153,7 +152,6 @@ REA requiere Node.js 22.x (>=22.19), 24.x (>=24.11) o 26+, además de npm. Las h
 | Capturas de red guardadas   | Solicitudes, respuestas, contenido accesible de las cargas útiles y ubicaciones de origen                                      | HAR; mitmdump en Linux para capturas en formato nativo de mitmproxy; [guía de capturas](../web-network-captures.md)                    |
 | Capturas de paquetes        | Endpoints, DNS, TLS SNI, distribución de protocolos y solicitudes HTTP                                                         | tshark y capinfos suministrados por el autor de la llamada; [guía pcap](../pcap-analysis.md)                                           |
 | Ensamblados .NET            | Metadatos, instrucciones CIL, dependencias nativas declaradas y comparaciones de compilaciones                                 | Inspección estática; [guía de código administrado](../managed-code-analysis.md)                                                        |
-| PyInstaller                 | CArchive, PYZ, Python bytecode                                                                                                 | Static inspection; [Python packaged applications](../python-packaged-applications.md)                                                  |
 | APK de Android              | Declaraciones del manifiesto, clases, métodos descompilados y referencias                                                      | JADX sin interfaz gráfica y un JDK completo en Linux/macOS/Windows x64; [guía de Android](../android-analysis.md)                      |
 | Dispositivos Android        | Dispositivos, paquetes, procesos, registros, volcados, capturas de pantalla y transferencias de APK/archivos                   | adb suministrado por el autor de la llamada (emulador o dispositivo); [guía de ADB](../adb-device-analysis.md)                         |
 | Proyectos JEB               | Unidades de proyecto del motor, resúmenes de artefactos y pseudocódigo de tipos/métodos                                        | Un cliente JEB iniciado por el autor de la llamada que sirve MCP, seleccionado con REA_JEB_MCP_URL; [guía de JEB](../jeb-analysis.md)  |
@@ -266,8 +264,6 @@ Empieza con las [guías prácticas](https://rea.tools/es/guides/) del sitio web.
 
 - [Instalación y configuración](../installation.md): registro de agentes, configuración de proveedores, actualizaciones y desinstalación.
 - [Preparación y resolución de problemas](../installation.md#check-readiness-for-your-task): diagnóstico de un agente o motor de análisis concreto.
-- [CUDA / HIP](../gpu-code-objects.md)
-- [GGUF / safetensors](../model-artifacts.md)
 - [CLI y Evidence](../cli.md): comandos, selección de proveedores, instantáneas, importación/exportación y estados de salida.
 - [Contratos de MCP](../mcp-contracts.md) y [prompts para agentes](../mcp-prompts.md): resultados de herramientas, sesiones e investigaciones guiadas.
 - [Catálogo de herramientas](../mcp-contracts.md#generated-catalog): inventario de herramientas, proveedores y comandos de CLI generado durante la compilación.

docs/readme/README_fa.md

@@ -135,7 +135,6 @@ REA به Node.js 22.x (>=22.19)، 24.x (>=24.11) یا 26+، به‌همراه np
 | ---------------------- | ----------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------- |
 | باینری‌های بومی         | شبه‌کد، اسمبلی، رشته‌ها، نمادها، فراخوانی‌ها و ارجاعات                                 | Hopper، Ghidra یا IDA؛ [تحلیل بومی](../native-investigation.md)                                                                   |
 | ساختار ELF آفلاین       | بخش‌ها، سگمنت‌ها، نمادها و relocationهای اصلی و گزینه‌های احتمالی کاهش آسیب‌پذیری ایستا | pwntools تأمین‌شده توسط فراخواننده روی Linux x64؛ [تشخیص باینری](../binary-diagnostics.md)                                         |
-| PE certificates        | Authenticode WIN_CERTIFICATE entries and PKCS#7 signer/X.509 identity fields        | Built-in static PE inspection; [PE certificates](../pe-certificates.md)                                                           |
 | بایت‌کد EVM             | selectorهای dispatch، offsetهای بایتی، آرگومان‌های استنباط‌شده و قابلیت تغییر وضعیت   | دادهٔ خام/hex محلی روی Linux x64؛ [راهنمای EVM آفلاین](../evm-bytecode.md)                                                          |
 | Rust binaries          | Embedded cargo-auditable dependency list                                            | [Rust binaries](../rust-binaries.md)                                                                                              |
 | کرش‌های ثبت‌شدهٔ لینوکس   | یادداشت‌های خام، رجیسترها/سیگنال‌های تمام threadهای ثبت‌شده و گزینه‌های احتمالی نگاشت   | pwntools تأمین‌شده توسط فراخواننده روی Linux x64؛ GDB/pwndbg اختیاری؛ [کرش‌های ثبت‌شده](../recorded-crashes.md)                      |
@@ -144,7 +143,6 @@ REA به Node.js 22.x (>=22.19)، 24.x (>=24.11) یا 26+، به‌همراه np
 | وب‌سایت‌ها               | ساختار صفحه، اسکریپت‌ها، مشاهدات شبکه و اسکرین‌شات‌های درخواستی                        | مرورگر مبتنی بر Chrome؛ [تحلیل مرورگر](../browser-observation.md)                                                                 |
 | داده‌های ضبط‌شدهٔ شبکه    | درخواست‌ها، پاسخ‌ها، payloadهای آشکارشده و مکان آن‌ها در منبع                          | HAR؛ ابزار mitmdump در لینوکس برای ضبط‌های بومی mitmproxy؛ [راهنمای ضبط شبکه](../web-network-captures.md)                          |
 | اسمبلی‌های .NET         | فراداده، دستورالعمل‌های CIL، وابستگی‌های بومی اعلام‌شده و مقایسهٔ buildها                | بررسی ایستا؛ [راهنمای کد مدیریت‌شده](../managed-code-analysis.md)                                                                  |
-| PyInstaller            | CArchive, PYZ, Python bytecode                                                      | Static inspection; [Python packaged applications](../python-packaged-applications.md)                                             |
 | فایل‌های APK اندروید    | تعاریف Manifest، کلاس‌ها، متدهای دیکامپایل‌شده و ارجاعات                               | JADX بدون رابط گرافیکی و JDK کامل در Linux/macOS/Windows x64؛ [راهنمای اندروید](../android-analysis.md)                           |
 | دستگاه‌های اندروید      | دستگاه‌ها، بسته‌ها، فرایندها، لاگ‌ها، دامپ‌ها، اسکرین‌شات‌ها و انتقال APK/فایل             | adb تأمین‌شده توسط فراخوان‌کننده (شبیه‌ساز یا دستگاه)؛ [راهنمای ADB](../adb-device-analysis.md)                                      |
 | پروژه‌های JEB           | واحدهای پروژه از موتور، هش‌های مصنوع و شبه‌کدِ نوع/متد                                 | یک کلاینت JEB که توسط فراخوان‌کننده اجرا شده و MCP ارائه می‌دهد و با REA_JEB_MCP_URL انتخاب می‌شود؛ [راهنمای JEB](../jeb-analysis.md) |
@@ -251,8 +249,6 @@ npx rea-agents@latest setup
 
 - [نصب و راه‌اندازی](../installation.md): ثبت ایجنت، پیکربندی ارائه‌دهنده، به‌روزرسانی و حذف نصب.
 - [آمادگی و رفع اشکال](../installation.md#check-readiness-for-your-task): عیب‌یابی یک ایجنت یا موتور تحلیل.
-- [CUDA / HIP](../gpu-code-objects.md)
-- [GGUF / safetensors](../model-artifacts.md)
 - [CLI و شواهد](../cli.md): دستورات، انتخاب ارائه‌دهنده، snapshotها، ورود/خروج داده و وضعیت‌های خروج.
 - [قراردادهای MCP](../mcp-contracts.md) و [پرامپت‌های ایجنت](../mcp-prompts.md): نتایج ابزارها، نشست‌ها و بررسی‌های هدایت‌شده.
 - [فهرست ابزارها](../mcp-contracts.md#generated-catalog): فهرست تولیدشده هنگام build از ابزارها، ارائه‌دهندگان و دستورات CLI.

docs/readme/README_fr.md

@@ -146,7 +146,6 @@ REA nécessite Node.js 22.x (>=22.19), 24.x (>=24.11) ou 26+, ainsi que npm. Les
 | ---------------------------- | ----------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------- |
 | Binaires natifs              | Pseudo-code, assembleur, chaînes, symboles, appels et références                                            | Hopper, Ghidra ou IDA ; [analyse native](../native-investigation.md)                                                              |
 | Structure ELF hors ligne     | Sections, segments, symboles et relocations d'origine, et protections statiques candidates                  | pwntools fourni par l'utilisateur sous Linux x64 ; [diagnostics binaires](../binary-diagnostics.md)                               |
-| PE certificates              | Authenticode WIN_CERTIFICATE entries and PKCS#7 signer/X.509 identity fields                                | Built-in static PE inspection; [PE certificates](../pe-certificates.md)                                                           |
 | Artefact WASM                | Validation, sections, formes WAT exactes d'import/export et WAT décodé                                      | WABT 1.0.42 fourni par l'utilisateur ; `inspect_wasm_artifact`                                                                    |
 | Bytecode EVM                 | Sélecteurs de dispatch, offsets en octets, arguments inférés et mutabilité                                  | Fichier local brut ou hexadécimal sous Linux x64 ; [guide EVM hors ligne](../evm-bytecode.md)                                     |
 | Rust binaries                | Embedded cargo-auditable dependency list                                                                    | [Rust binaries](../rust-binaries.md)                                                                                              |
@@ -157,7 +156,6 @@ REA nécessite Node.js 22.x (>=22.19), 24.x (>=24.11) ou 26+, ainsi que npm. Les
 | Captures réseau enregistrées | Requêtes, réponses, payloads exposés et emplacements dans le code source                                    | HAR ; mitmdump sous Linux pour les captures mitmproxy natives ; [guide des captures](../web-network-captures.md)                  |
 | Captures de paquets          | Points de terminaison, DNS, TLS SNI, distribution des protocoles et requêtes HTTP                           | tshark et capinfos fournis par l'appelant ; [guide pcap](../pcap-analysis.md)                                                     |
 | Assemblys .NET               | Métadonnées, instructions CIL, dépendances natives déclarées et comparaisons de builds                      | Inspection statique ; [guide du code managé](../managed-code-analysis.md)                                                         |
-| PyInstaller                  | CArchive, PYZ, Python bytecode                                                                              | Static inspection; [Python packaged applications](../python-packaged-applications.md)                                             |
 | APK Android                  | Déclarations du manifeste, classes, méthodes décompilées et références                                      | JADX headless et un JDK complet sous Linux/macOS/Windows x64 ; [guide Android](../android-analysis.md)                            |
 | Appareils Android            | Appareils, paquets, processus, journaux, dumps, captures d'écran et transferts d'APK/fichiers               | adb fourni par l'appelant (émulateur ou appareil) ; [guide ADB](../adb-device-analysis.md)                                        |
 | Projets JEB                  | Unités de projet fournies par le moteur, condensés d'artefacts et pseudo-code de types/méthodes             | Un client JEB démarré par l'appelant servant MCP, sélectionné via REA_JEB_MCP_URL ; [guide JEB](../jeb-analysis.md)               |
@@ -270,8 +268,6 @@ Commencez par les [guides pas à pas](https://rea.tools/fr/guides/) du site web.
 
 - [Installation et configuration](../installation.md) : enregistrement des agents, configuration des fournisseurs, mises à jour et désinstallation.
 - [Vérification et dépannage](../installation.md#check-readiness-for-your-task) : diagnostiquer un agent ou un moteur d'analyse donné.
-- [CUDA / HIP](../gpu-code-objects.md)
-- [GGUF / safetensors](../model-artifacts.md)
 - [CLI et Evidence](../cli.md) : commandes, choix du fournisseur, snapshots, import/export et codes de sortie.
 - [Contrats MCP](../mcp-contracts.md) et [prompts pour agents](../mcp-prompts.md) : résultats des outils, sessions et investigations guidées.
 - [Catalogue des outils](../mcp-contracts.md#generated-catalog) : inventaire des outils, fournisseurs et commandes CLI, généré lors du build.

docs/readme/README_id.md

@@ -149,7 +149,6 @@ Alat tambahan dan dukungan sistem host bergantung pada target yang dianalisis:
 | -------------------------- | ----------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------ |
 | Biner native               | Pseudocode, assembly, string, simbol, pemanggilan, dan referensi                                      | Hopper, Ghidra, atau IDA; [analisis native](../native-investigation.md)                                                        |
 | Tata letak ELF offline     | Bagian, segmen, simbol/relokasi asli, dan kandidat mitigasi statis                                    | pwntools yang disediakan pemanggil pada Linux x64; [diagnostik biner](../binary-diagnostics.md)                                |
-| PE certificates            | Authenticode WIN_CERTIFICATE entries and PKCS#7 signer/X.509 identity fields                          | Built-in static PE inspection; [PE certificates](../pe-certificates.md)                                                        |
 | Artefak WASM               | Validasi, bagian, bentuk WAT import/ekspor yang tepat, dan WAT yang didekode                          | WABT 1.0.42 yang disediakan pemanggil; `inspect_wasm_artifact`                                                                 |
 | Bytecode EVM               | Selector dispatch, offset byte, argumen yang disimpulkan, dan sifat mutabilitas                       | Pembawa data raw/hex lokal; [panduan EVM offline](../evm-bytecode.md)                                                          |
 | Rust binaries              | Embedded cargo-auditable dependency list                                                              | [Rust binaries](../rust-binaries.md)                                                                                           |
@@ -160,7 +159,6 @@ Alat tambahan dan dukungan sistem host bergantung pada target yang dianalisis:
 | Rekaman jaringan tersimpan | Permintaan, respons, payload yang terekspos, dan lokasi sumber                                        | HAR; mitmdump di Linux untuk rekaman native mitmproxy; [panduan rekaman](../web-network-captures.md)                           |
 | Capturan paket             | Endpoint, DNS, TLS SNI, distribusi protokol, dan permintaan HTTP                                      | tshark dan capinfos buatan pemanggil; [panduan pcap](../pcap-analysis.md)                                                      |
 | Assembly .NET              | Metadata, instruksi CIL, dependensi native yang dideklarasikan, dan perbandingan build                | Tidak ada (hanya analisis statis); [panduan kode terkelola](../managed-code-analysis.md)                                       |
-| PyInstaller                | CArchive, PYZ, Python bytecode                                                                        | Static inspection; [Python packaged applications](../python-packaged-applications.md)                                          |
 | APK Android                | Deklarasi manifest, kelas, metode hasil dekompilasi, dan referensi                                    | JADX mode headless dan JDK lengkap di Linux/macOS/Windows x64; [panduan Android](../android-analysis.md)                       |
 | Perangkat Android          | Perangkat, paket, proses, log, dump, tangkapan layar, serta transfer APK/berkas                       | adb buatan pemanggil (emulator atau perangkat); [panduan ADB](../adb-device-analysis.md)                                       |
 | Proyek JEB                 | Unit proyek bertenaga mesin, hash artefak, dan pseudokode tipe/metode                                 | Klien JEB yang dijalankan pemanggil dan menyajikan MCP, dipilih dengan REA_JEB_MCP_URL; [panduan JEB](../jeb-analysis.md)      |
@@ -291,8 +289,6 @@ Untuk mengetahui opsi, prasyarat, dan kontrak hasil secara tepat:
 
 - [Instalasi dan penyiapan](../installation.md): pendaftaran agen, konfigurasi penyedia, pembaruan, dan penghapusan instalasi.
 - [Kesiapan dan pemecahan masalah](../installation.md#check-readiness-for-your-task): mendiagnosis satu agen atau mesin analisis.
-- [CUDA / HIP](../gpu-code-objects.md)
-- [GGUF / safetensors](../model-artifacts.md)
 - [CLI dan Bukti](../cli.md): perintah, pemilihan penyedia, snapshot, impor/ekspor, dan status keluar.
 - [Kontrak MCP](../mcp-contracts.md) dan [prompt agen](../mcp-prompts.md): hasil alat, sesi, dan investigasi terpandu.
 - [Katalog alat](../mcp-contracts.md#generated-catalog): inventaris alat, penyedia, dan perintah CLI yang dibuat secara otomatis.

docs/readme/README_it.md

@@ -146,7 +146,6 @@ REA richiede Node.js 22.x (>=22.19), 24.x (>=24.11) o 26+, oltre a npm. Strument
 | ---------------------------- | ------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------- |
 | Binari nativi                | Pseudocodice, assembly, stringhe, simboli, chiamate e riferimenti                                 | Hopper, Ghidra o IDA; [analisi nativa](../native-investigation.md)                                                              |
 | Layout ELF offline           | Sezioni, segmenti, simboli/relocazioni originali e candidati mitigazioni statiche                 | pwntools fornito dal chiamante su Linux x64; [diagnostica binaria](../binary-diagnostics.md)                                    |
-| PE certificates              | Authenticode WIN_CERTIFICATE entries and PKCS#7 signer/X.509 identity fields                      | Built-in static PE inspection; [PE certificates](../pe-certificates.md)                                                         |
 | Artefatto WASM               | Convalida, sezioni, forme WAT di import/export esatte e WAT decodificato                          | WABT 1.0.42 fornito dal chiamante; `inspect_wasm_artifact`                                                                      |
 | Bytecode EVM                 | Selettori di dispatch, offset dei byte, argomenti inferiti e mutabilità                           | Carrier raw/hex locale; [guida EVM offline](../evm-bytecode.md)                                                                 |
 | Rust binaries                | Embedded cargo-auditable dependency list                                                          | [Rust binaries](../rust-binaries.md)                                                                                            |
@@ -157,7 +156,6 @@ REA richiede Node.js 22.x (>=22.19), 24.x (>=24.11) o 26+, oltre a npm. Strument
 | Acquisizioni di rete salvate | Richieste, risposte, payload esposti e posizioni sorgente                                         | HAR; mitmdump su Linux per acquisizioni mitmproxy native; [guida alle acquisizioni](../web-network-captures.md)                 |
 | Captured di pacchetti        | Endpoint, DNS, TLS SNI, distribuzione dei protocolli e richieste HTTP                             | tshark e capinfos forniti dal chiamante; [guida pcap](../pcap-analysis.md)                                                      |
 | Assembly .NET                | Metadati, istruzioni CIL, dipendenze native dichiarate e confronti di build                       | Nessuno (solo statico); [guida managed-code](../managed-code-analysis.md)                                                       |
-| PyInstaller                  | CArchive, PYZ, Python bytecode                                                                    | Static inspection; [Python packaged applications](../python-packaged-applications.md)                                           |
 | APK Android                  | Dichiarazioni manifest, classi, metodi decompilati e riferimenti                                  | JADX headless e un JDK completo su Linux/macOS/Windows x64; [guida Android](../android-analysis.md)                             |
 | Dispositivi Android          | Dispositivi, pacchetti, processi, log, dump, screenshot e trasferimenti APK/file                  | adb fornito dal chiamante (emulatore o hardware); [guida ADB](../adb-device-analysis.md)                                        |
 | Progetti JEB                 | Unità di progetto dal motore, digest degli artifact e pseudocodice di tipi/metodi                 | Client JEB avviato dal chiamante via MCP, selezionato con REA_JEB_MCP_URL; [guida JEB](../jeb-analysis.md)                      |
@@ -270,8 +268,6 @@ Inizia dalle [guide pratiche](https://rea.tools/it/guides/) del sito web. Per op
 
 - [Installazione e configurazione](../installation.md): registrazione agente, configurazione provider, aggiornamenti e disinstallazione.
 - [Pronto all'uso e risoluzione dei problemi](../installation.md#check-readiness-for-your-task): diagnostica un agente o un motore di analisi.
-- [CUDA / HIP](../gpu-code-objects.md)
-- [GGUF / safetensors](../model-artifacts.md)
 - [CLI ed Evidence](../cli.md): comandi, selezione provider, snapshot, import/export e stati di uscita.
 - [Contratti MCP](../mcp-contracts.md) e [prompt agente](../mcp-prompts.md): risultati degli strumenti, sessioni e indagini guidate.
 - [Catalogo strumenti](../mcp-contracts.md#generated-catalog): inventario generato di strumenti, provider e comandi CLI.

docs/readme/README_ja.md

@@ -143,7 +143,6 @@ REA には Node.js 22.x（>=22.19）、24.x（>=24.11）、または 26+ と npm
 | -------------------------------- | ------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------- |
 | ネイティブバイナリ               | 疑似コード、アセンブリ、文字列、シンボル、呼び出し、参照                                    | Hopper、Ghidra、または IDA；[ネイティブ分析](../native-investigation.md)                                                                       |
 | オフライン ELF レイアウト        | セクション、セグメント、元のシンボル／再配置情報、静的解析によるセキュリティ対策の候補      | Linux x64 で利用者が用意する pwntools；[バイナリ診断](../binary-diagnostics.md)                                                                |
-| PE certificates                  | Authenticode WIN_CERTIFICATE entries and PKCS#7 signer/X.509 identity fields                | Built-in static PE inspection; [PE certificates](../pe-certificates.md)                                                                        |
 | EVM バイトコード                 | ディスパッチセレクター、バイトオフセット、推定された引数と状態変更の可否                    | Linux x64 上のローカルの生バイト／16 進数の入力ファイル；[オフライン EVM ガイド](../evm-bytecode.md)                                           |
 | Rust binaries                    | Embedded cargo-auditable dependency list                                                    | [Rust binaries](../rust-binaries.md)                                                                                                           |
 | 記録済みの Linux クラッシュ      | 生の note レコード、記録された全スレッドのレジスター／シグナル、任意のマッピング候補        | Linux x64 で利用者が用意する pwntools；GDB/pwndbg は任意；[記録済みクラッシュ](../recorded-crashes.md)                                         |
@@ -153,7 +152,6 @@ REA には Node.js 22.x（>=22.19）、24.x（>=24.11）、または 26+ と npm
 | 保存済みのネットワークキャプチャ | リクエスト、レスポンス、取得可能なペイロード、ソース内の位置                                | HAR；mitmproxy ネイティブ形式のキャプチャには Linux 上の mitmdump；[キャプチャガイド](../web-network-captures.md)                              |
 | パケットキャプチャ               | エンドポイント、DNS、TLS SNI、プロトコル分布、HTTPリクエスト                                | 呼び出し側が用意した tshark と capinfos；[pcapガイド](../pcap-analysis.md)                                                                     |
 | .NET アセンブリ                  | メタデータ、CIL 命令、宣言されたネイティブ依存関係、ビルドの比較                            | 静的な検査；[マネージドコードのガイド](../managed-code-analysis.md)                                                                            |
-| PyInstaller                      | CArchive, PYZ, Python bytecode                                                              | Static inspection; [Python packaged applications](../python-packaged-applications.md)                                                          |
 | Android APK                      | マニフェストの宣言、クラス、逆コンパイルされたメソッド、参照                                | Linux/macOS/Windows x64 上のヘッドレス JADX と完全な JDK；[Android ガイド](../android-analysis.md)                                             |
 | Android デバイス                 | デバイス、パッケージ、プロセス、ログ、ダンプ、スクリーンキャプチャ、APK/ファイル転送        | 呼び出し側が用意した adb（エミュレーターまたは実機）；[ADB ガイド](../adb-device-analysis.md)                                                  |
 | JEBプロジェクト                  | エンジンによるプロジェクトユニット、アーティファクトのダイジェスト、型/メソッドの擬似コード | 呼び出し側が起動し MCP を提供する JEB クライアント（REA_JEB_MCP_URL で選択）；[JEB ガイド](../jeb-analysis.md)                                 |
@@ -268,8 +266,6 @@ npx rea-agents@latest setup
 
 - [インストールとセットアップ](../installation.md)：エージェントの登録、プロバイダーの設定、更新、アンインストール。
 - [準備状況の確認とトラブルシューティング](../installation.md#check-readiness-for-your-task)：特定のエージェントや分析エンジンを診断。
-- [CUDA / HIP](../gpu-code-objects.md)
-- [GGUF / safetensors](../model-artifacts.md)
 - [CLI と Evidence](../cli.md)：コマンド、プロバイダーの選択、スナップショット、インポート／エクスポート、終了ステータス。
 - [MCP 契約](../mcp-contracts.md)と[エージェント向けプロンプト](../mcp-prompts.md)：ツールの結果、セッション、ガイド付き調査。
 - [ツールカタログ](../mcp-contracts.md#generated-catalog)：ビルド時に生成されるツール、プロバイダー、CLI コマンドの一覧。

docs/readme/README_ko.md

@@ -153,7 +153,6 @@ REA에는 Node.js 22.x(>=22.19), 24.x(>=24.11) 또는 26+와 npm이 필요합니
 | 오프라인 ELF 레이아웃  | 섹션, 세그먼트, 원본 심볼/재배치 정보, 정적 분석으로 얻은 보안 완화 기법 후보 | Linux x64에서 호출자가 제공하는 pwntools; [바이너리 진단](../binary-diagnostics.md)                                               |
 | Go 바이너리            | 내장된 컴파일러 버전, 모듈, `replace` 지시어, 빌드 설정                       | REA 내장 ELF/PE/thin Mach-O 정적 검사; Go 설치 불필요                                                                             |
 | Rust 바이너리          | cargo-auditable이 내장한 크레이트 이름, 버전, 소스, 의존성 관계               | REA 내장 ELF/PE/thin Mach-O 정적 검사; [Rust 바이너리](../rust-binaries.md)                                                       |
-| PE certificates        | Authenticode WIN_CERTIFICATE entries and PKCS#7 signer/X.509 identity fields  | Built-in static PE inspection; [PE certificates](../pe-certificates.md)                                                           |
 | WASM 아티팩트          | 유효성 검사, 섹션, import/export의 정확한 WAT 형식, 디코딩된 WAT              | 호출자 제공 WABT 1.0.42; `inspect_wasm_artifact`                                                                                  |
 | EVM 바이트코드         | 디스패치 선택자, 바이트 오프셋, 추론한 인자와 상태 변경 가능 여부             | Linux x64의 로컬 원시 바이트/16진수 입력 파일; [오프라인 EVM 가이드](../evm-bytecode.md)                                          |
 | SQLite 데이터베이스    | 테이블, 열, 인덱스, 뷰, 트리거, 선택한 일반 테이블의 행                       | 로컬 데이터베이스/WAL 스냅샷; Node.js 24.15 이상의 24.x 또는 26 이상(네이티브 SQLite 한도 적용)                                   |
@@ -174,7 +173,6 @@ REA에는 Node.js 22.x(>=22.19), 24.x(>=24.11) 또는 26+와 npm이 필요합니
 | 기록된 논리 신호       | 디코더 주석, 샘플 범위, 진단 정보                                             | Linux: sigrok-cli 0.7.2 + prlimit; [신호 기록 가이드](../signal-recordings.md)                                                    |
 | 패키지 및 리소스       | 파일 목록, 다이제스트, plist, Apple 번들 구조, 추출한 리소스                  | [아티팩트 및 JavaScript 가이드](../javascript-artifact-reconstruction.md), [Apple 애플리케이션](../apple-application-analysis.md) |
 | 프로세스 동작          | 터미널 출력, 상호작용, 종료 및 파일 시스템 관찰 결과, 실행 비교               | 네이티브 PTY를 지원하는 Linux/macOS; [프로세스 캡처](../process-capture.md)                                                       |
-| PyInstaller            | CArchive, PYZ, Python bytecode                                                | Static inspection; [Python packaged applications](../python-packaged-applications.md)                                             |
 
 정적 JavaScript 및 .NET 검사는 제공된 파일을 읽으며 애플리케이션을 실행하지 않습니다. 런타임 캡처는 사용자의 권한으로 선택한 대상을 실행하거나 대상과 상호작용합니다. 각 런타임 가이드에서 그 영향을 설명합니다.
 
@@ -281,8 +279,6 @@ npx rea-agents@latest setup
 
 - [설치 및 설정](../installation.md): 에이전트 등록, 제공자 설정, 업데이트, 제거.
 - [준비 상태 확인 및 문제 해결](../installation.md#check-readiness-for-your-task): 특정 에이전트 또는 분석 엔진 진단.
-- [CUDA / HIP](../gpu-code-objects.md)
-- [GGUF / safetensors](../model-artifacts.md)
 - [CLI 및 Evidence](../cli.md): 명령, 제공자 선택, 스냅샷, 가져오기/내보내기, 종료 상태.
 - [MCP 계약](../mcp-contracts.md) 및 [에이전트 프롬프트](../mcp-prompts.md): 도구 결과, 세션, 안내에 따른 조사.
 - [도구 카탈로그](../mcp-contracts.md#generated-catalog): 빌드 시 생성되는 도구, 제공자, CLI 명령 목록.

docs/readme/README_ml.md

@@ -151,7 +151,6 @@ REA-യ്ക്ക് Node.js 22.x (>=22.19), 24.x (>=24.11), അല്ലെ
 | Offline ELF layout     | Sections, segments, യഥാർത്ഥ symbols/relocations, static mitigation candidates         | Linux x64-ൽ caller നൽകുന്ന pwntools; [binary diagnostics](../binary-diagnostics.md)                                                 |
 | Go binaries            | ഉൾച്ചേർത്ത compiler version, modules, replacements, build settings                    | Built-in static ELF/PE/thin Mach-O പരിശോധന; Go installation ആവശ്യമില്ല                                                              |
 | Rust binaries          | ഉൾച്ചേർത്ത cargo-auditable crate പേരുകൾ, versions, sources, dependency edges           | Built-in static ELF/PE/thin Mach-O പരിശോധന; [Rust binaries](../rust-binaries.md)                                                  |
-| PE certificates        | Authenticode WIN_CERTIFICATE entries and PKCS#7 signer/X.509 identity fields        | Built-in static PE inspection; [PE certificates](../pe-certificates.md)                                                           |
 | WASM artifact          | Validation, sections, കൃത്യമായ import/export WAT രൂപങ്ങൾ, decoded WAT                    | Caller നൽകുന്ന WABT 1.0.42; `inspect_wasm_artifact`                                                                                 |
 | EVM bytecode           | Dispatch selectors, byte offsets, അനുമാനിച്ച arguments, mutability                     | Linux x64-ൽ local raw/hex carrier; [offline EVM guide](../evm-bytecode.md)                                                        |
 | SQLite databases       | Tables, columns, indexes, views, triggers, തിരഞ്ഞെടുത്ത സാധാരണ table rows                | Local database/WAL snapshot; native SQLite പരിമിതികളോടെ Node.js 24.x >=24.15 അല്ലെങ്കിൽ 26+                                         |
@@ -161,7 +160,6 @@ REA-യ്ക്ക് Node.js 22.x (>=22.19), 24.x (>=24.11), അല്ലെ
 | Websites               | Page structure, scripts, network observations, ആവശ്യപ്പെട്ട screenshots                | Chrome-family browser; [browser analysis](../browser-observation.md)                                                              |
 | Saved network captures | Requests, responses, പുറത്തുകാണുന്ന payload-ുകൾ, source locations                          | HAR അല്ലെങ്കിൽ Fiddler Everywhere SAZ; native mitmproxy-നായി Linux-ൽ mitmdump; [capture guide](../web-network-captures.md)           |
 | .NET assemblies        | Metadata, CIL instructions, പ്രഖ്യാപിച്ച native dependencies, build comparisons         | ഒന്നും ആവശ്യമില്ല (static മാത്രം); [managed-code guide](../managed-code-analysis.md)                                                    |
-| Python packaged apps   | CArchive/PYZ entries, Python version, bytecode, resources and runtime options       | Static PyInstaller parsing; [Python guide](../python-packaged-applications.md)                                                    |
 | Android APKs           | Manifest declarations, classes, decompiled methods, references                      | Linux/macOS/Windows x64-ൽ Headless JADX-ഉം full JDK-ഉം; [Android guide](../android-analysis.md)                                   |
 | Android devices        | Devices, packages, processes, logs, dumps, screen captures, APK/file transfers      | Caller നൽകുന്ന adb (emulator അല്ലെങ്കിൽ hardware); [ADB guide](../adb-device-analysis.md)                                             |
 | JEB projects           | Engine-backed project units, artifact digests, type/method pseudo-code              | MCP സേവനം നൽകുന്ന caller ആരംഭിച്ച JEB client; REA_JEB_MCP_URL ഉപയോഗിച്ച് തിരഞ്ഞെടുക്കുക; [JEB guide](../jeb-analysis.md)                   |
@@ -284,8 +282,6 @@ npx rea-agents@latest setup
 
 - [Installation and setup](../installation.md): agent registration, provider configuration, updates, uninstall.
 - [Readiness and troubleshooting](../installation.md#check-readiness-for-your-task): ഒരു agent-ന്റെയോ analysis engine-ന്റെയോ പ്രശ്നങ്ങൾ കണ്ടെത്തുക.
-- [CUDA / HIP](../gpu-code-objects.md)
-- [GGUF / safetensors](../model-artifacts.md)
 - [CLI and Evidence](../cli.md): commands, provider തിരഞ്ഞെടുക്കൽ, snapshots, import/export, exit statuses.
 - [MCP contracts](../mcp-contracts.md), [agent prompts](../mcp-prompts.md): tool results, sessions, guided investigations.
 - [Tool catalog](../mcp-contracts.md#generated-catalog): tools, providers, CLI commands എന്നിവയുടെ സ്വയമേവ സൃഷ്ടിച്ച പട്ടിക.

docs/readme/README_pl.md

@@ -143,7 +143,6 @@ REA wymaga Node.js 22.x (>=22.19), 24.x (>=24.11) lub 26+ oraz npm. Dodatkowe na
 | --------------------------------------- | --------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------ |
 | Natywne pliki binarne                   | Pseudokod, kod asemblera, ciągi znaków, symbole, wywołania i odwołania                                                | Hopper, Ghidra lub IDA; [analiza kodu natywnego](../native-investigation.md)                                                         |
 | Układ pliku ELF w trybie offline        | Sekcje, segmenty, oryginalne symbole/relokacje i potencjalne mechanizmy zabezpieczeń wskazane przez analizę statyczną | pwntools dostarczone przez użytkownika w systemie Linux x64; [diagnostyka plików binarnych](../binary-diagnostics.md)                |
-| PE certificates                         | Authenticode WIN_CERTIFICATE entries and PKCS#7 signer/X.509 identity fields                                          | Built-in static PE inspection; [PE certificates](../pe-certificates.md)                                                              |
 | Kod bajtowy EVM                         | Selektory wywołań, przesunięcia bajtowe, wywnioskowane argumenty i mutowalność                                        | Lokalny plik z surowymi bajtami lub zapisem szesnastkowym w systemie Linux x64; [przewodnik EVM offline](../evm-bytecode.md)         |
 | Rust binaries                           | Embedded cargo-auditable dependency list                                                                              | [Rust binaries](../rust-binaries.md)                                                                                                 |
 | Zarejestrowane awarie systemu Linux     | Surowe rekordy note, rejestry/sygnały każdego zarejestrowanego wątku i opcjonalni kandydaci na mapowania              | pwntools dostarczone przez użytkownika w systemie Linux x64; opcjonalnie GDB/pwndbg; [zarejestrowane awarie](../recorded-crashes.md) |
@@ -153,7 +152,6 @@ REA wymaga Node.js 22.x (>=22.19), 24.x (>=24.11) lub 26+ oraz npm. Dodatkowe na
 | Zapisane przechwycenia ruchu sieciowego | Żądania, odpowiedzi, dostępne dane przesyłane i lokalizacje źródłowe                                                  | HAR; mitmdump w systemie Linux dla natywnych przechwyceń mitmproxy; [przewodnik przechwytywania](../web-network-captures.md)         |
 | Przechwytywanie pakietów                | Punkty końcowe, DNS, TLS SNI, dystrybucja protokołów i żądania HTTP                                                   | Dostarczone przez wywołującego tshark i capinfos; [przewodnik pcap](../pcap-analysis.md)                                             |
 | Zestawy .NET                            | Metadane, instrukcje CIL, zadeklarowane zależności natywne i porównania kompilacji                                    | Analiza statyczna; [przewodnik kodu zarządzanego](../managed-code-analysis.md)                                                       |
-| PyInstaller                             | CArchive, PYZ, Python bytecode                                                                                        | Static inspection; [Python packaged applications](../python-packaged-applications.md)                                                |
 | Pakiety APK dla Androida                | Deklaracje manifestu, klasy, zdekompilowane metody i odwołania                                                        | JADX bez interfejsu graficznego i pełny JDK w systemach Linux/macOS/Windows x64; [przewodnik Androida](../android-analysis.md)       |
 | Urządzenia z Androidem                  | Urządzenia, pakiety, procesy, logi, zrzuty, zrzuty ekranu oraz transfery APK/plików                                   | adb dostarczony przez wywołującego (emulator lub urządzenie); [przewodnik ADB](../adb-device-analysis.md)                            |
 | Projekty JEB                            | Jednostki projektu obsługiwane przez silnik, skróty artefaktów i pseudokod typów/metod                                | Uruchomiony przez wywołującego klient JEB udostępniający MCP, wybrany przez REA_JEB_MCP_URL; [przewodnik JEB](../jeb-analysis.md)    |
@@ -266,8 +264,6 @@ Zacznij od [przewodników z przykładami](https://rea.tools/pl/guides/) na stron
 
 - [Instalacja i konfiguracja](../installation.md): rejestracja agentów, konfiguracja dostawców analizy, aktualizacje i odinstalowanie.
 - [Gotowość i rozwiązywanie problemów](../installation.md#check-readiness-for-your-task): diagnostyka jednego agenta lub silnika analizy.
-- [CUDA / HIP](../gpu-code-objects.md)
-- [GGUF / safetensors](../model-artifacts.md)
 - [CLI i Evidence](../cli.md): polecenia, wybór dostawcy, migawki, import/eksport i kody zakończenia.
 - [Kontrakty MCP](../mcp-contracts.md) i [prompty dla agentów](../mcp-prompts.md): wyniki narzędzi, sesje i prowadzone analizy.
 - [Katalog narzędzi](../mcp-contracts.md#generated-catalog): generowany podczas kompilacji wykaz narzędzi, dostawców i poleceń CLI.

docs/readme/README_pt-BR.md

@@ -143,7 +143,6 @@ O REA requer Node.js 22.x (>=22.19), 24.x (>=24.11) ou 26+, além do npm. As fer
 | --------------------------- | ----------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------- |
 | Binários nativos            | Pseudocódigo, assembly, strings, símbolos, chamadas e referências                                                       | Hopper, Ghidra ou IDA; [análise nativa](../native-investigation.md)                                                               |
 | Estrutura ELF sem execução  | Seções, segmentos, símbolos/relocações originais e possíveis mecanismos de mitigação identificados por análise estática | pwntools fornecido pelo chamador no Linux x64; [diagnóstico de binários](../binary-diagnostics.md)                                |
-| PE certificates             | Authenticode WIN_CERTIFICATE entries and PKCS#7 signer/X.509 identity fields                                            | Built-in static PE inspection; [PE certificates](../pe-certificates.md)                                                           |
 | Bytecode EVM                | Seletores de despacho, offsets de bytes, argumentos inferidos e mutabilidade                                            | Entrada local com bytes brutos ou representação hexadecimal no Linux x64; [guia de EVM sem execução](../evm-bytecode.md)          |
 | Rust binaries               | Embedded cargo-auditable dependency list                                                                                | [Rust binaries](../rust-binaries.md)                                                                                              |
 | Falhas do Linux registradas | Registros note brutos, registradores/sinais de cada thread registrada e candidatos opcionais a mapeamentos              | pwntools fornecido pelo chamador no Linux x64; GDB/pwndbg opcionais; [falhas registradas](../recorded-crashes.md)                 |
@@ -153,7 +152,6 @@ O REA requer Node.js 22.x (>=22.19), 24.x (>=24.11) ou 26+, além do npm. As fer
 | Capturas de rede salvas     | Requisições, respostas, payloads acessíveis e localizações de origem                                                    | HAR; mitmdump no Linux para capturas no formato nativo do mitmproxy; [guia de capturas](../web-network-captures.md)               |
 | Capturas de pacotes         | Endpoints, DNS, TLS SNI, distribuição de protocolos e requisições HTTP                                                  | tshark e capinfos fornecidos pelo chamador; [guia pcap](../pcap-analysis.md)                                                      |
 | Assemblies .NET             | Metadados, instruções CIL, dependências nativas declaradas e comparações de builds                                      | Inspeção estática; [guia de código gerenciado](../managed-code-analysis.md)                                                       |
-| PyInstaller                 | CArchive, PYZ, Python bytecode                                                                                          | Static inspection; [Python packaged applications](../python-packaged-applications.md)                                             |
 | APKs Android                | Declarações do manifesto, classes, métodos descompilados e referências                                                  | JADX sem interface gráfica e um JDK completo no Linux/macOS/Windows x64; [guia de Android](../android-analysis.md)                |
 | Dispositivos Android        | Dispositivos, pacotes, processos, logs, despejos, capturas de tela e transferências de APK/arquivos                     | adb fornecido pelo chamador (emulador ou aparelho); [guia de ADB](../adb-device-analysis.md)                                      |
 | Projetos JEB                | Unidades de projeto do motor, hashes de artefatos e pseudocódigo de tipos/métodos                                       | Um cliente JEB iniciado pelo chamador servindo MCP, selecionado com REA_JEB_MCP_URL; [guia de JEB](../jeb-analysis.md)            |
@@ -266,8 +264,6 @@ Comece pelos [guias práticos](https://rea.tools/pt-BR/guides/) do site. Para op
 
 - [Instalação e configuração](../installation.md): registro de agentes, configuração de provedores, atualizações e desinstalação.
 - [Prontidão e solução de problemas](../installation.md#check-readiness-for-your-task): diagnóstico de um agente ou motor de análise específico.
-- [CUDA / HIP](../gpu-code-objects.md)
-- [GGUF / safetensors](../model-artifacts.md)
 - [CLI e Evidence](../cli.md): comandos, seleção de provedores, snapshots, importação/exportação e status de saída.
 - [Contratos MCP](../mcp-contracts.md) e [prompts para agentes](../mcp-prompts.md): resultados das ferramentas, sessões e investigações guiadas.
 - [Catálogo de ferramentas](../mcp-contracts.md#generated-catalog): inventário de ferramentas, provedores e comandos da CLI gerado durante o build.

docs/readme/README_ru.md

@@ -145,7 +145,6 @@ REA требует Node.js 22.x (>=22.19), 24.x (>=24.11) или 26+, а так
 | Структура ELF без запуска           | Секции, сегменты, исходные символы/релокации и возможные механизмы защиты по данным статического анализа                   | pwntools, предоставленный вызывающей стороной, в Linux x64; [диагностика бинарных файлов](../binary-diagnostics.md)                      |
 | Байт-код EVM                        | Селекторы диспетчеризации, смещения байтов, предполагаемые аргументы и изменяемость состояния                              | Локальные необработанные байты или шестнадцатеричное представление в Linux x64; [руководство по EVM без запуска](../evm-bytecode.md)     |
 | Rust binaries                       | Embedded cargo-auditable dependency list                                                                                   | [Rust binaries](../rust-binaries.md)                                                                                                     |
-| PE certificates                     | Authenticode WIN_CERTIFICATE entries and PKCS#7 signer/X.509 identity fields                                               | Built-in static PE inspection; [PE certificates](../pe-certificates.md)                                                                  |
 | Записанные сбои Linux               | Необработанные записи note, регистры/сигналы каждого записанного потока и необязательные кандидаты сопоставления с памятью | pwntools, предоставленный вызывающей стороной, в Linux x64; необязательные GDB/pwndbg; [записанные сбои](../recorded-crashes.md)         |
 | Установленные настольные приложения | Возможные среды выполнения, файлы с доказательствами, компоненты и дальнейшие шаги                                         | Ограниченная проверка каталогов и заголовков；[Настольные приложения](../desktop-applications.md)                                        |
 | JavaScript / Electron               | Модули, импорты, карты исходного кода, маршруты, IPC и связи с нативными дополнениями                                      | Node.js и npm; [анализ приложений](../javascript-application-workflows.md)                                                               |
@@ -163,7 +162,6 @@ REA требует Node.js 22.x (>=22.19), 24.x (>=24.11) или 26+, а так
 | Записанные логические сигналы       | Аннотации декодера, диапазоны отсчётов и диагностика                                                                       | Linux: sigrok-cli 0.7.2 + prlimit; [руководство по сигналам](../signal-recordings.md)                                                    |
 | Пакеты и ресурсы                    | Списки файлов, хеши, plist, структура пакетов Apple и извлечённые ресурсы                                                  | [Руководство по артефактам и JavaScript](../javascript-artifact-reconstruction.md), [приложения Apple](../apple-application-analysis.md) |
 | Поведение процессов                 | Вывод терминала, взаимодействия, наблюдения за завершением и файловой системой, сравнения запусков                         | Linux/macOS с нативным PTY; [захват процессов](../process-capture.md)                                                                    |
-| PyInstaller                         | CArchive, PYZ, Python bytecode                                                                                             | Static inspection; [Python packaged applications](../python-packaged-applications.md)                                                    |
 
 Статическое исследование JavaScript и .NET читает предоставленные файлы, не запуская приложение. Захват во время выполнения запускает выбранную цель или взаимодействует с ней с правами вашего пользователя; соответствующие руководства описывают последствия.
 
@@ -266,8 +264,6 @@ npx rea-agents@latest setup
 
 - [Установка и настройка](../installation.md): регистрация агентов, настройка провайдеров, обновление и удаление.
 - [Готовность и устранение неполадок](../installation.md#check-readiness-for-your-task): диагностика конкретного агента или движка анализа.
-- [CUDA / HIP](../gpu-code-objects.md)
-- [GGUF / safetensors](../model-artifacts.md)
 - [CLI и Evidence](../cli.md): команды, выбор провайдера, снимки, импорт/экспорт и коды завершения.
 - [Контракты MCP](../mcp-contracts.md) и [промпты агентов](../mcp-prompts.md): результаты инструментов, сеансы и исследования с подсказками.
 - [Каталог инструментов](../mcp-contracts.md#generated-catalog): создаваемый при сборке перечень инструментов, провайдеров и команд CLI.

docs/readme/README_th.md

@@ -143,7 +143,6 @@ REA ต้องใช้ Node.js 22.x (>=22.19), 24.x (>=24.11) หรือ 26
 | ---------------------------- | ------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------- |
 | ไบนารีเนทีฟ                    | โค้ดเทียม แอสเซมบลี สตริง สัญลักษณ์ การเรียก และการอ้างอิง                                | Hopper, Ghidra หรือ IDA; [การวิเคราะห์เนทีฟ](../native-investigation.md)                                                       |
 | โครงสร้าง ELF แบบออฟไลน์       | เซกชัน เซกเมนต์ สัญลักษณ์/รีโลเคชันต้นฉบับ และตัวเลือกกลไกป้องกันที่พบจากการวิเคราะห์แบบสถิต      | pwntools ที่ผู้ใช้จัดเตรียมบน Linux x64; [การวินิจฉัยไบนารี](../binary-diagnostics.md)                                                |
-| PE certificates              | Authenticode WIN_CERTIFICATE entries and PKCS#7 signer/X.509 identity fields    | Built-in static PE inspection; [PE certificates](../pe-certificates.md)                                                    |
 | ไบต์โค้ด EVM                   | ตัวเลือกฟังก์ชันสำหรับการเรียก ออฟเซ็ตไบต์ อาร์กิวเมนต์และความสามารถในการเปลี่ยนสถานะที่อนุมานได้ | ไฟล์บนเครื่องที่มีไบต์ดิบหรือข้อมูลเลขฐานสิบหกบน Linux x64; [คู่มือ EVM แบบออฟไลน์](../evm-bytecode.md)                                    |
 | Rust binaries                | Embedded cargo-auditable dependency list                                        | [Rust binaries](../rust-binaries.md)                                                                                       |
 | ข้อมูลการแครชของ Linux ที่บันทึกไว้ | ระเบียน note ดิบ รีจิสเตอร์/สัญญาณของทุกเธรดที่บันทึกไว้ และตัวเลือกการแมปเพิ่มเติม              | pwntools ที่ผู้ใช้จัดเตรียมบน Linux x64; เลือกใช้ GDB/pwndbg เพิ่มเติมได้; [การแครชที่บันทึกไว้](../recorded-crashes.md)                     |
@@ -153,7 +152,6 @@ REA ต้องใช้ Node.js 22.x (>=22.19), 24.x (>=24.11) หรือ 26
 | ข้อมูลเครือข่ายที่บันทึกไว้           | คำขอ คำตอบ เพย์โหลดที่ปรากฏ และตำแหน่งต้นทาง                                         | HAR; mitmdump บน Linux สำหรับข้อมูลที่บันทึกในรูปแบบเนทีฟของ mitmproxy; [คู่มือการบันทึกข้อมูล](../web-network-captures.md)                |
 | การจับแพ็กเก็ต                  | จุดเชื่อมต่อ, DNS, TLS SNI, การกระจายโปรโตคอล และคำขอ HTTP                          | tshark และ capinfos ที่ผู้เรียกจัดเตรียม; [คู่มือ pcap](../pcap-analysis.md)                                                         |
 | แอสเซมบลี .NET                | เมทาดาทา คำสั่ง CIL การพึ่งพาเนทีฟที่ประกาศไว้ และการเปรียบเทียบผลการบิลด์                  | การตรวจสอบแบบสถิต; [คู่มือโค้ดแบบจัดการ](../managed-code-analysis.md)                                                            |
-| PyInstaller                  | CArchive, PYZ, Python bytecode                                                  | Static inspection; [Python packaged applications](../python-packaged-applications.md)                                      |
 | APK ของ Android              | การประกาศใน manifest คลาส เมธอดที่ดีคอมไพล์ และการอ้างอิง                             | JADX แบบไม่มี GUI และ JDK แบบเต็มบน Linux/macOS/Windows x64; [คู่มือ Android](../android-analysis.md)                            |
 | อุปกรณ์ Android                | อุปกรณ์ แพ็กเกจ โพรเซส บันทึก ดัมพ์ ภาพหน้าจอ และการถ่ายโอน APK/ไฟล์                      | adb ที่ผู้เรียกจัดเตรียม (โปรแกรมจำลองหรืออุปกรณ์จริง); [คู่มือ ADB](../adb-device-analysis.md)                                          |
 | โปรเจกต์ JEB                  | หน่วยโปรเจกต์จากเอนจิน, แฮชของอาร์ติแฟกต์ และซูโดโค้ดของไทป์/เมท็อด                       | ไคลเอนต์ JEB ที่ผู้เรียกเริ่มและให้บริการ MCP เลือกด้วย REA_JEB_MCP_URL; [คู่มือ JEB](../jeb-analysis.md)                                 |
@@ -266,8 +264,6 @@ npx rea-agents@latest setup
 
 - [การติดตั้งและตั้งค่า](../installation.md): การลงทะเบียนเอเจนต์ การตั้งค่าผู้ให้บริการ การอัปเดต และการถอนการติดตั้ง
 - [ความพร้อมใช้งานและการแก้ไขปัญหา](../installation.md#check-readiness-for-your-task): ตรวจวินิจฉัยเอเจนต์หรือเอนจินวิเคราะห์หนึ่งตัว
-- [CUDA / HIP](../gpu-code-objects.md)
-- [GGUF / safetensors](../model-artifacts.md)
 - [CLI และ Evidence](../cli.md): คำสั่ง การเลือกผู้ให้บริการ สแนปช็อต การนำเข้า/ส่งออก และรหัสการสิ้นสุด
 - [สัญญา MCP](../mcp-contracts.md) และ[พรอมป์ต์สำหรับเอเจนต์](../mcp-prompts.md): ผลลัพธ์เครื่องมือ เซสชัน และการตรวจสอบตามคำแนะนำ
 - [แค็ตตาล็อกเครื่องมือ](../mcp-contracts.md#generated-catalog): รายการเครื่องมือ ผู้ให้บริการ และคำสั่ง CLI ที่สร้างระหว่างการบิลด์

docs/readme/README_tr.md

@@ -147,7 +147,6 @@ REA; Node.js 22.x (>=22.19), 24.x (>=24.11) veya 26+ ve npm gerektirir. Ek araç
 | Çevrimdışı ELF yapısı                   | Bölümler, segmentler, özgün semboller/yeniden konumlandırmalar ve statik analizden olası güvenlik önlemleri | Linux x64 üzerinde çağıranın sağladığı pwntools; [ikili dosya tanılama](../binary-diagnostics.md)                                  |
 | Go ikili dosyaları                      | Gömülü compiler sürümü, modüller, replacement'lar ve build ayarları                                         | Yerleşik statik ELF/PE/thin Mach-O incelemesi; Go kurulumu gerekmez                                                                |
 | Rust ikili dosyaları                    | Gömülü cargo-auditable crate adları, sürümleri, kaynakları ve bağımlılık ilişkileri                         | Yerleşik statik ELF/PE/thin Mach-O incelemesi; [Rust ikili dosyaları](../rust-binaries.md)                                         |
-| PE certificates                         | Authenticode WIN_CERTIFICATE entries and PKCS#7 signer/X.509 identity fields                                | Built-in static PE inspection; [PE certificates](../pe-certificates.md)                                                            |
 | WASM artefaktı                          | Doğrulama, bölümler, tam import/export WAT biçimleri ve decode edilmiş WAT                                  | Çağıranın sağladığı WABT 1.0.42; `inspect_wasm_artifact`                                                                           |
 | EVM bayt kodu                           | Yönlendirme seçicileri, bayt ofsetleri, çıkarımla belirlenen argümanlar ve durum değiştirilebilirliği       | Linux x64 üzerinde yerel ham bayt/onaltılık girdi; [çevrimdışı EVM rehberi](../evm-bytecode.md)                                    |
 | SQLite veritabanları                    | Tablolar, sütunlar, index'ler, view'lar, trigger'lar ve seçilen sıradan tablo satırları                     | Yerel database/WAL snapshot'ı; native SQLite sınırlarıyla Node.js 24.x >=24.15 veya 26+                                            |
@@ -157,7 +156,6 @@ REA; Node.js 22.x (>=22.19), 24.x (>=24.11) veya 26+ ve npm gerektirir. Ek araç
 | Web siteleri                            | Sayfa yapısı, betikler, ağ gözlemleri ve istenen ekran görüntüleri                                          | Chrome ailesinden bir tarayıcı; [tarayıcı analizi](../browser-observation.md)                                                      |
 | Kaydedilmiş ağ yakalamaları             | İstekler, yanıtlar, erişilebilir yük içerikleri ve kaynak konumları                                         | HAR veya Fiddler Everywhere SAZ; Linux'ta native mitmproxy için mitmdump; [ağ yakalama rehberi](../web-network-captures.md)        |
 | .NET derlemeleri                        | Meta veriler, CIL talimatları, bildirilmiş yerel bağımlılıklar ve derleme karşılaştırmaları                 | Statik inceleme; [yönetilen kod rehberi](../managed-code-analysis.md)                                                              |
-| PyInstaller                             | CArchive, PYZ, Python bytecode                                                                              | Static inspection; [Python packaged applications](../python-packaged-applications.md)                                              |
 | Android APK'leri                        | Manifest bildirimleri, sınıflar, tersine derlenmiş metotlar ve referanslar                                  | Linux/macOS/Windows x64 üzerinde arayüzsüz JADX ve tam bir JDK; [Android rehberi](../android-analysis.md)                          |
 | Android cihazları                       | Cihazlar, paketler, süreçler, günlükler, dökümler, ekran görüntüleri ve APK/dosya aktarımları               | Çağıranın sağladığı adb (emülatör veya cihaz); [ADB rehberi](../adb-device-analysis.md)                                            |
 | JEB projeleri                           | Motor destekli proje birimleri, artefakt özetleri ve tür/metot sözdekodu                                    | Çağıranın başlattığı, MCP sunan bir JEB istemcisi, REA_JEB_MCP_URL ile seçilir; [JEB rehberi](../jeb-analysis.md)                  |
@@ -271,8 +269,6 @@ Web sitesindeki [uygulamalı rehberlerden](https://rea.tools/tr/guides/) başlay
 
 - [Yükleme ve kurulum](../installation.md): ajan kaydı, sağlayıcı yapılandırması, güncellemeler ve kaldırma.
 - [Hazırlık ve sorun giderme](../installation.md#check-readiness-for-your-task): belirli bir ajanı veya analiz motorunu tanılama.
-- [CUDA / HIP](../gpu-code-objects.md)
-- [GGUF / safetensors](../model-artifacts.md)
 - [CLI ve Evidence](../cli.md): komutlar, sağlayıcı seçimi, anlık görüntüler, içe/dışa aktarma ve çıkış durumları.
 - [MCP sözleşmeleri](../mcp-contracts.md) ve [ajan istemleri](../mcp-prompts.md): araç sonuçları, oturumlar ve yönlendirmeli araştırmalar.
 - [Araç kataloğu](../mcp-contracts.md#generated-catalog): derleme sırasında oluşturulan araç, sağlayıcı ve CLI komutu envanteri.

docs/readme/README_uk.md

@@ -143,7 +143,6 @@ REA потребує Node.js 22.x (>=22.19), 24.x (>=24.11) або 26+, а та
 | ------------------------------------ | ----------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------- |
 | Нативні бінарні файли                | Псевдокод, асемблерний код, рядки, символи, виклики й посилання                                                   | Hopper, Ghidra або IDA; [нативний аналіз](../native-investigation.md)                                                                             |
 | Структура ELF без запуску            | Секції, сегменти, початкові символи/релокації та можливі захисні механізми за даними статичного аналізу           | pwntools, наданий стороною, що викликає інструмент, у Linux x64; [діагностика бінарних файлів](../binary-diagnostics.md)                          |
-| PE certificates                      | Authenticode WIN_CERTIFICATE entries and PKCS#7 signer/X.509 identity fields                                      | Built-in static PE inspection; [PE certificates](../pe-certificates.md)                                                                           |
 | Байт-код EVM                         | Селектори диспетчеризації, зміщення байтів, виведені припущення про аргументи та змінюваність стану               | Локальні необроблені байти або шістнадцяткове представлення у Linux x64; [посібник EVM без запуску](../evm-bytecode.md)                           |
 | Rust binaries                        | Embedded cargo-auditable dependency list                                                                          | [Rust binaries](../rust-binaries.md)                                                                                                              |
 | Записані аварійні завершення в Linux | Необроблені записи note, регістри/сигнали кожного записаного потоку й необов'язкові кандидати зіставлення пам'яті | pwntools, наданий стороною, що викликає інструмент, у Linux x64; необов'язкові GDB/pwndbg; [записані аварійні завершення](../recorded-crashes.md) |
@@ -153,7 +152,6 @@ REA потребує Node.js 22.x (>=22.19), 24.x (>=24.11) або 26+, а та
 | Збережені мережеві захоплення        | Запити, відповіді, доступні корисні дані та місця в джерелі                                                       | HAR; mitmdump у Linux для захоплень у власному форматі mitmproxy; [посібник мережевих захоплень](../web-network-captures.md)                      |
 | Захоплення пакетів                   | Кінцеві точки, DNS, TLS SNI, розподіл протоколів та HTTP-запити                                                   | Надані викликаючою стороною tshark та capinfos; [підручник pcap](../pcap-analysis.md)                                                             |
 | Збірки .NET                          | Метадані, інструкції CIL, оголошені нативні залежності й порівняння збірок                                        | Статична перевірка; [посібник керованого коду](../managed-code-analysis.md)                                                                       |
-| PyInstaller                          | CArchive, PYZ, Python bytecode                                                                                    | Static inspection; [Python packaged applications](../python-packaged-applications.md)                                                             |
 | Android APK                          | Оголошення маніфесту, класи, декомпільовані методи й посилання                                                    | JADX без графічного інтерфейсу й повний JDK у Linux/macOS/Windows x64; [посібник Android](../android-analysis.md)                                 |
 | Пристрої Android                     | Пристрої, пакети, процеси, журнали, дампи, знімки екрана та передавання APK/файлів                                | adb, наданий викликаючою стороною (емулятор або пристрій); [підручник ADB](../adb-device-analysis.md)                                             |
 | Проєкти JEB                          | Єдиниці проєкту від рушія, дайджести артефактів і псевдокод типів/методів                                         | Запущений викликаною стороною клієнт JEB з MCP, обирається через REA_JEB_MCP_URL; [посібник JEB](../jeb-analysis.md)                              |
@@ -266,8 +264,6 @@ npx rea-agents@latest setup
 
 - [Встановлення й налаштування](../installation.md): реєстрація агентів, конфігурація провайдерів, оновлення та видалення.
 - [Готовність та усунення неполадок](../installation.md#check-readiness-for-your-task): діагностика конкретного агента або рушія аналізу.
-- [CUDA / HIP](../gpu-code-objects.md)
-- [GGUF / safetensors](../model-artifacts.md)
 - [CLI та Evidence](../cli.md): команди, вибір провайдера, знімки, імпорт/експорт і статуси завершення.
 - [Контракти MCP](../mcp-contracts.md) і [промпти агентів](../mcp-prompts.md): результати інструментів, сеанси й керовані дослідження.
 - [Каталог інструментів](../mcp-contracts.md#generated-catalog): створюваний під час збірки перелік інструментів, провайдерів і команд CLI.

docs/readme/README_vi.md

@@ -145,7 +145,6 @@ REA yêu cầu Node.js 22.x (>=22.19), 24.x (>=24.11) hoặc 26+, cùng với np
 | Bố cục ELF ngoại tuyến            | Các section, segment, ký hiệu/thông tin tái định vị gốc và các biện pháp giảm thiểu có thể có từ phân tích tĩnh | pwntools do bên gọi cung cấp trên Linux x64; [chẩn đoán tệp nhị phân](../binary-diagnostics.md)                                           |
 | Bytecode EVM                      | Bộ chọn điều phối, độ lệch byte, tham số suy luận và khả năng thay đổi trạng thái                               | Đầu vào cục bộ chứa byte thô hoặc dạng thập lục phân trên Linux x64; [hướng dẫn EVM ngoại tuyến](../evm-bytecode.md)                      |
 | Rust binaries                     | Embedded cargo-auditable dependency list                                                                        | [Rust binaries](../rust-binaries.md)                                                                                                      |
-| PE certificates                   | Authenticode WIN_CERTIFICATE entries and PKCS#7 signer/X.509 identity fields                                    | Built-in static PE inspection; [PE certificates](../pe-certificates.md)                                                                   |
 | Sự cố Linux đã ghi lại            | Bản ghi note thô, thanh ghi/tín hiệu của mọi luồng được ghi lại và các ứng viên ánh xạ tùy chọn                 | pwntools do bên gọi cung cấp trên Linux x64; GDB/pwndbg tùy chọn; [sự cố đã ghi lại](../recorded-crashes.md)                              |
 | Thư mục cài đặt ứng dụng máy tính | Các runtime có khả năng được dùng, tệp bằng chứng, dấu hiệu thành phần và bước tiếp theo                        | Kiểm tra thư mục và phần đầu tệp có giới hạn；[Ứng dụng máy tính](../desktop-applications.md)                                             |
 | JavaScript / Electron             | Mô-đun, các khai báo import, source map, tuyến, IPC và quan hệ với tiện ích mở rộng mã máy                      | Node.js và npm; [phân tích ứng dụng](../javascript-application-workflows.md)                                                              |
@@ -163,7 +162,6 @@ REA yêu cầu Node.js 22.x (>=22.19), 24.x (>=24.11) hoặc 26+, cùng với np
 | Tín hiệu logic đã ghi             | Chú thích bộ giải mã, phạm vi mẫu và chẩn đoán                                                                  | Linux: sigrok-cli 0.7.2 + prlimit; [hướng dẫn tín hiệu](../signal-recordings.md)                                                          |
 | Gói và tài nguyên                 | Danh sách tệp, giá trị băm, plist, cấu trúc bundle Apple và tài nguyên được trích xuất                          | [Hướng dẫn hiện vật phần mềm và JavaScript](../javascript-artifact-reconstruction.md), [ứng dụng Apple](../apple-application-analysis.md) |
 | Hành vi tiến trình                | Đầu ra terminal, tương tác, quan sát khi thoát và hệ thống tệp, cùng so sánh các lần chạy                       | Linux/macOS có PTY gốc; [ghi lại tiến trình](../process-capture.md)                                                                       |
-| PyInstaller                       | CArchive, PYZ, Python bytecode                                                                                  | Static inspection; [Python packaged applications](../python-packaged-applications.md)                                                     |
 
 Kiểm tra tĩnh JavaScript và .NET đọc các tệp được cung cấp mà không chạy ứng dụng. Ghi lại khi chạy sẽ khởi chạy hoặc tương tác với mục tiêu đã chọn bằng quyền người dùng của bạn; từng hướng dẫn mô tả tác động của nó.
 
@@ -266,8 +264,6 @@ Bắt đầu với [hướng dẫn thực hành](https://rea.tools/vi/guides/) t
 
 - [Cài đặt và thiết lập](../installation.md): đăng ký tác nhân, cấu hình trình phân tích, cập nhật và gỡ cài đặt.
 - [Kiểm tra mức sẵn sàng và khắc phục sự cố](../installation.md#check-readiness-for-your-task): chẩn đoán một tác nhân hoặc bộ máy phân tích cụ thể.
-- [CUDA / HIP](../gpu-code-objects.md)
-- [GGUF / safetensors](../model-artifacts.md)
 - [CLI và Evidence](../cli.md): lệnh, lựa chọn trình phân tích, ảnh chụp trạng thái, nhập/xuất và trạng thái thoát.
 - [Hợp đồng MCP](../mcp-contracts.md) và [prompt cho tác nhân](../mcp-prompts.md): kết quả công cụ, phiên làm việc và điều tra có hướng dẫn.
 - [Danh mục công cụ](../mcp-contracts.md#generated-catalog): danh sách công cụ, trình phân tích và lệnh CLI được tạo khi dựng dự án.

docs/readme/README_zh-TW.md

@@ -141,33 +141,31 @@ AI 代理通過 MCP 呼叫 REA，檢查目標並追蹤相關程式碼。REA 返
 
 REA 需要 Node.js 22.x（>=22.19）、24.x（>=24.11）或 26+，以及 npm。額外工具和主機支援取決於分析目標：
 
-| 目標                  | REA 返回的內容                                                               | 要求與指南                                                                                                         |
-| --------------------- | ---------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------ |
-| 原生二進位檔案        | 偽程式碼、組合語言、字串、符號、呼叫和引用                                   | Hopper、Ghidra 或 IDA；[原生分析](../native-investigation.md)                                                      |
-| 離線 ELF 佈局         | 節、段、原始符號/重定位資訊及靜態防護機制候選項                              | Linux x64 上由呼叫方提供的 pwntools；[二進位診斷](../binary-diagnostics.md)                                        |
-| Go 二進位檔案         | 內嵌編譯器版本、模組、替換項和建置設定                                       | 內建靜態 ELF/PE/thin Mach-O 檢查；無需安裝 Go                                                                      |
-| WASM 工件             | 驗證、節、精確的匯入/匯出 WAT 形式及解碼後的 WAT                             | 呼叫方提供的 WABT 1.0.42；`inspect_wasm_artifact`                                                                  |
-| EVM 位元組碼          | 分派選擇器、位元組偏移、推斷的參數和狀態可變性                               | Linux x64 上的本地原始位元組/十六進位輸入載體；[離線 EVM 指南](../evm-bytecode.md)                                 |
-| Rust binaries         | Embedded cargo-auditable dependency list                                     | [Rust binaries](../rust-binaries.md)                                                                               |
-| PE certificates       | Authenticode WIN_CERTIFICATE entries and PKCS#7 signer/X.509 identity fields | Built-in static PE inspection; [PE certificates](../pe-certificates.md)                                            |
-| 已記錄的 Linux 崩潰   | 原始 note 記錄、每個已記錄執行緒的暫存器/訊號及可選的對映候選項              | Linux x64 上由呼叫方提供的 pwntools；可選的 GDB/pwndbg；[已記錄崩潰](../recorded-crashes.md)                       |
-| 桌面安裝目錄          | 執行階段候選、支持檔案、元件標記與後續操作                                   | 有界的目錄與檔頭檢查；[桌面應用](../desktop-applications.md)                                                       |
-| JavaScript / Electron | 模組、匯入、source map、路由、IPC 和原生附加元件關係                         | Node.js 和 npm；[應用分析](../javascript-application-workflows.md)                                                 |
-| 網站                  | 頁面結構、腳本、網路觀察結果和按請求獲取的螢幕擷取畫面                       | Chrome 系瀏覽器；[瀏覽器分析](../browser-observation.md)                                                           |
-| 已保存的網路擷取      | 請求、回應、可訪問的酬載和來源位置                                           | HAR；原生 mitmproxy 擷取需要 Linux 上的 mitmdump；[擷取指南](../web-network-captures.md)                           |
-| 封包擷取              | 端點、DNS、TLS SNI、通訊協定分佈和 HTTP 請求                                 | 呼叫端提供的 tshark 和 capinfos；[pcap 指南](../pcap-analysis.md)                                                  |
-| .NET 程式集           | 中繼資料、CIL 指令、聲明的原生依賴和建置對比                                 | 靜態檢查；[托管程式碼指南](../managed-code-analysis.md)                                                            |
-| PyInstaller           | CArchive, PYZ, Python bytecode                                               | Static inspection; [Python packaged applications](../python-packaged-applications.md)                              |
-| Android APK           | 清單聲明、類別、反編譯的方法和引用                                           | Linux/macOS/Windows x64 上的無界面 JADX 和完整 JDK；[Android 指南](../android-analysis.md)                         |
-| Android 裝置          | 裝置、套件、程序、日誌、傾印、螢幕擷取以及 APK/檔案傳輸                      | 呼叫端提供的 adb（模擬器或實體裝置）；[ADB 指南](../adb-device-analysis.md)                                        |
-| JEB 專案              | 引擎支援的專案單元、成品摘要和型別/方法的虛擬碼                              | 由呼叫端啟動、提供 MCP 的 JEB 用戶端，透過 REA_JEB_MCP_URL 選擇；[JEB 指南](../jeb-analysis.md)                    |
-| Android 資源          | 解碼後的清單、字串表、語系和版本資訊                                         | 呼叫端提供的 Apktool 啟動器；[資源指南](../apktool-resource-analysis.md)                                           |
-| Flutter 應用          | Dart 快照雜湊、依 ABI 的程式庫雜湊及引擎建置來源                             | 無（靜態 APK 解析）；[Flutter 指南](../flutter-analysis.md)                                                        |
-| 韌體                  | 區域、提取結果和轉交原生分析的內容                                           | Linux 上的 Binwalk / Unblob；[韌體指南](../firmware-analysis.md)                                                   |
-| 封包記錄              | 指定欄位、重複值、篩選條件與解碼規則                                         | Linux: TShark 4.x + prlimit; [封包分析指南](../packet-captures.md)                                                 |
-| 錄製的邏輯訊號        | 解碼註解、樣本範圍與診斷資訊                                                 | Linux: sigrok-cli 0.7.2 + prlimit; [訊號記錄指南](../signal-recordings.md)                                         |
-| 軟體包與資源          | 檔案清單、摘要、plist、Apple bundle 結構和提取的資源                         | [製品與 JavaScript 指南](../javascript-artifact-reconstruction.md)、[Apple 應用](../apple-application-analysis.md) |
-| 處理程序行為          | 終端輸出、互動、退出和檔案系統觀察結果，以及執行對比                         | 支援原生 PTY 的 Linux/macOS；[處理程序擷取](../process-capture.md)                                                 |
+| 目標                  | REA 返回的內容                                                  | 要求與指南                                                                                                         |
+| --------------------- | --------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------ |
+| 原生二進位檔案        | 偽程式碼、組合語言、字串、符號、呼叫和引用                      | Hopper、Ghidra 或 IDA；[原生分析](../native-investigation.md)                                                      |
+| 離線 ELF 佈局         | 節、段、原始符號/重定位資訊及靜態防護機制候選項                 | Linux x64 上由呼叫方提供的 pwntools；[二進位診斷](../binary-diagnostics.md)                                        |
+| Go 二進位檔案         | 內嵌編譯器版本、模組、替換項和建置設定                          | 內建靜態 ELF/PE/thin Mach-O 檢查；無需安裝 Go                                                                      |
+| WASM 工件             | 驗證、節、精確的匯入/匯出 WAT 形式及解碼後的 WAT                | 呼叫方提供的 WABT 1.0.42；`inspect_wasm_artifact`                                                                  |
+| EVM 位元組碼          | 分派選擇器、位元組偏移、推斷的參數和狀態可變性                  | Linux x64 上的本地原始位元組/十六進位輸入載體；[離線 EVM 指南](../evm-bytecode.md)                                 |
+| Rust binaries         | Embedded cargo-auditable dependency list                        | [Rust binaries](../rust-binaries.md)                                                                               |
+| 已記錄的 Linux 崩潰   | 原始 note 記錄、每個已記錄執行緒的暫存器/訊號及可選的對映候選項 | Linux x64 上由呼叫方提供的 pwntools；可選的 GDB/pwndbg；[已記錄崩潰](../recorded-crashes.md)                       |
+| 桌面安裝目錄          | 執行階段候選、支持檔案、元件標記與後續操作                      | 有界的目錄與檔頭檢查；[桌面應用](../desktop-applications.md)                                                       |
+| JavaScript / Electron | 模組、匯入、source map、路由、IPC 和原生附加元件關係            | Node.js 和 npm；[應用分析](../javascript-application-workflows.md)                                                 |
+| 網站                  | 頁面結構、腳本、網路觀察結果和按請求獲取的螢幕擷取畫面          | Chrome 系瀏覽器；[瀏覽器分析](../browser-observation.md)                                                           |
+| 已保存的網路擷取      | 請求、回應、可訪問的酬載和來源位置                              | HAR；原生 mitmproxy 擷取需要 Linux 上的 mitmdump；[擷取指南](../web-network-captures.md)                           |
+| 封包擷取              | 端點、DNS、TLS SNI、通訊協定分佈和 HTTP 請求                    | 呼叫端提供的 tshark 和 capinfos；[pcap 指南](../pcap-analysis.md)                                                  |
+| .NET 程式集           | 中繼資料、CIL 指令、聲明的原生依賴和建置對比                    | 靜態檢查；[托管程式碼指南](../managed-code-analysis.md)                                                            |
+| Android APK           | 清單聲明、類別、反編譯的方法和引用                              | Linux/macOS/Windows x64 上的無界面 JADX 和完整 JDK；[Android 指南](../android-analysis.md)                         |
+| Android 裝置          | 裝置、套件、程序、日誌、傾印、螢幕擷取以及 APK/檔案傳輸         | 呼叫端提供的 adb（模擬器或實體裝置）；[ADB 指南](../adb-device-analysis.md)                                        |
+| JEB 專案              | 引擎支援的專案單元、成品摘要和型別/方法的虛擬碼                 | 由呼叫端啟動、提供 MCP 的 JEB 用戶端，透過 REA_JEB_MCP_URL 選擇；[JEB 指南](../jeb-analysis.md)                    |
+| Android 資源          | 解碼後的清單、字串表、語系和版本資訊                            | 呼叫端提供的 Apktool 啟動器；[資源指南](../apktool-resource-analysis.md)                                           |
+| Flutter 應用          | Dart 快照雜湊、依 ABI 的程式庫雜湊及引擎建置來源                | 無（靜態 APK 解析）；[Flutter 指南](../flutter-analysis.md)                                                        |
+| 韌體                  | 區域、提取結果和轉交原生分析的內容                              | Linux 上的 Binwalk / Unblob；[韌體指南](../firmware-analysis.md)                                                   |
+| 封包記錄              | 指定欄位、重複值、篩選條件與解碼規則                            | Linux: TShark 4.x + prlimit; [封包分析指南](../packet-captures.md)                                                 |
+| 錄製的邏輯訊號        | 解碼註解、樣本範圍與診斷資訊                                    | Linux: sigrok-cli 0.7.2 + prlimit; [訊號記錄指南](../signal-recordings.md)                                         |
+| 軟體包與資源          | 檔案清單、摘要、plist、Apple bundle 結構和提取的資源            | [製品與 JavaScript 指南](../javascript-artifact-reconstruction.md)、[Apple 應用](../apple-application-analysis.md) |
+| 處理程序行為          | 終端輸出、互動、退出和檔案系統觀察結果，以及執行對比            | 支援原生 PTY 的 Linux/macOS；[處理程序擷取](../process-capture.md)                                                 |
 
 靜態 JavaScript 和 .NET 檢查讀取提供的檔案，不執行應用。執行階段擷取會以你的使用者權限執行目標或與之互動；各執行階段指南說明瞭具體影響。
 
@@ -272,8 +270,6 @@ npx rea-agents@latest setup
 
 - [安裝與設定](../installation.md)：AI 代理註冊、提供者組態、更新和卸載。
 - [就緒檢查與故障排查](../installation.md#check-readiness-for-your-task)：診斷特定 AI 代理或分析引擎。
-- [CUDA / HIP](../gpu-code-objects.md)
-- [GGUF / safetensors](../model-artifacts.md)
 - [CLI 與 Evidence](../cli.md)：命令、提供者選擇、快照、匯入/匯出和退出狀態。
 - [MCP 契約](../mcp-contracts.md)和[AI 代理提示詞](../mcp-prompts.md)：工具結果、會話和引導式調查。
 - [工具目錄](../mcp-contracts.md#generated-catalog)：建置時生成的工具、提供者和 CLI 命令清單。

docs/readme/README_zh.md

@@ -141,33 +141,31 @@ npx rea-agents@latest setup
 
 REA 需要 Node.js 22.x（>=22.19）、24.x（>=24.11）或 26+，以及 npm。额外工具和主机支持取决于分析目标：
 
-| 目标                  | REA 返回的内容                                                               | 要求与指南                                                                                                         |
-| --------------------- | ---------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------ |
-| 原生二进制文件        | 伪代码、汇编、字符串、符号、调用和引用                                       | Hopper、Ghidra 或 IDA；[原生分析](../native-investigation.md)                                                      |
-| 离线 ELF 布局         | 节、段、原始符号/重定位信息及静态防护机制候选项                              | Linux x64 上由调用方提供的 pwntools；[二进制诊断](../binary-diagnostics.md)                                        |
-| Go 二进制文件         | 内嵌编译器版本、模块、替换项和构建设置                                       | 内置静态 ELF/PE/thin Mach-O 检查；无需安装 Go                                                                      |
-| WASM 工件             | 验证、节、精确的导入/导出 WAT 形式及解码后的 WAT                             | 调用方提供的 WABT 1.0.42；`inspect_wasm_artifact`                                                                  |
-| EVM 字节码            | 分派选择器、字节偏移、推断的参数和状态可变性                                 | Linux x64 上的本地原始字节/十六进制输入载体；[离线 EVM 指南](../evm-bytecode.md)                                   |
-| Rust binaries         | Embedded cargo-auditable dependency list                                     | [Rust binaries](../rust-binaries.md)                                                                               |
-| PE certificates       | Authenticode WIN_CERTIFICATE entries and PKCS#7 signer/X.509 identity fields | Built-in static PE inspection; [PE certificates](../pe-certificates.md)                                            |
-| 已记录的 Linux 崩溃   | 原始 note 记录、每个已记录线程的寄存器/信号及可选的映射候选项                | Linux x64 上由调用方提供的 pwntools；可选的 GDB/pwndbg；[已记录崩溃](../recorded-crashes.md)                       |
-| 桌面安装目录          | 运行时候选、支持文件、组件标记和后续操作                                     | 有界的目录与文件头检查；[桌面应用](../desktop-applications.md)                                                     |
-| JavaScript / Electron | 模块、导入、source map、路由、IPC 和原生扩展关系                             | Node.js 和 npm；[应用分析](../javascript-application-workflows.md)                                                 |
-| 网站                  | 页面结构、脚本、网络观察结果和按请求获取的截图                               | Chrome 系浏览器；[浏览器分析](../browser-observation.md)                                                           |
-| 已保存的网络捕获      | 请求、响应、可访问的载荷和来源位置                                           | HAR；原生 mitmproxy 捕获需要 Linux 上的 mitmdump；[捕获指南](../web-network-captures.md)                           |
-| 数据包捕获            | 端点、DNS、TLS SNI、协议分布和 HTTP 请求                                     | 调用方提供的 tshark 和 capinfos；[pcap 指南](../pcap-analysis.md)                                                  |
-| .NET 程序集           | 元数据、CIL 指令、声明的原生依赖和构建对比                                   | 静态检查；[托管代码指南](../managed-code-analysis.md)                                                              |
-| PyInstaller           | CArchive, PYZ, Python bytecode                                               | Static inspection; [Python packaged applications](../python-packaged-applications.md)                              |
-| Android APK           | 清单声明、类、反编译的方法和引用                                             | Linux/macOS/Windows x64 上的无界面 JADX 和完整 JDK；[Android 指南](../android-analysis.md)                         |
-| Android 设备          | 设备、软件包、进程、日志、转储、屏幕截图以及 APK/文件传输                    | 调用方提供的 adb（模拟器或实体设备）；[ADB 指南](../adb-device-analysis.md)                                        |
-| JEB 项目              | 引擎支持的项目单元、工件摘要和类型/方法的伪代码                              | 由调用方启动、提供 MCP 的 JEB 客户端，通过 REA_JEB_MCP_URL 选择；[JEB 指南](../jeb-analysis.md)                    |
-| Android 资源          | 解码后的清单、字符串表、语言区域和版本信息                                   | 调用方提供的 Apktool 启动器；[资源指南](../apktool-resource-analysis.md)                                           |
-| Flutter 应用          | Dart 快照哈希、按 ABI 的库摘要及引擎构建溯源                                 | 无（静态 APK 解析）；[Flutter 指南](../flutter-analysis.md)                                                        |
-| 固件                  | 区域、提取结果和转交原生分析的内容                                           | Linux 上的 Binwalk / Unblob；[固件指南](../firmware-analysis.md)                                                   |
-| 抓包文件              | 指定字段、重复值、过滤条件与解码规则                                         | Linux: TShark 4.x + prlimit; [抓包分析指南](../packet-captures.md)                                                 |
-| 录制的逻辑信号        | 解码注释、样本范围和诊断信息                                                 | Linux: sigrok-cli 0.7.2 + prlimit; [信号记录指南](../signal-recordings.md)                                         |
-| 软件包与资源          | 文件清单、摘要、plist、Apple bundle 结构和提取的资源                         | [制品与 JavaScript 指南](../javascript-artifact-reconstruction.md)、[Apple 应用](../apple-application-analysis.md) |
-| 进程行为              | 终端输出、交互、退出和文件系统观察结果，以及运行对比                         | 支持原生 PTY 的 Linux/macOS；[进程捕获](../process-capture.md)                                                     |
+| 目标                  | REA 返回的内容                                                | 要求与指南                                                                                                         |
+| --------------------- | ------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------ |
+| 原生二进制文件        | 伪代码、汇编、字符串、符号、调用和引用                        | Hopper、Ghidra 或 IDA；[原生分析](../native-investigation.md)                                                      |
+| 离线 ELF 布局         | 节、段、原始符号/重定位信息及静态防护机制候选项               | Linux x64 上由调用方提供的 pwntools；[二进制诊断](../binary-diagnostics.md)                                        |
+| Go 二进制文件         | 内嵌编译器版本、模块、替换项和构建设置                        | 内置静态 ELF/PE/thin Mach-O 检查；无需安装 Go                                                                      |
+| WASM 工件             | 验证、节、精确的导入/导出 WAT 形式及解码后的 WAT              | 调用方提供的 WABT 1.0.42；`inspect_wasm_artifact`                                                                  |
+| EVM 字节码            | 分派选择器、字节偏移、推断的参数和状态可变性                  | Linux x64 上的本地原始字节/十六进制输入载体；[离线 EVM 指南](../evm-bytecode.md)                                   |
+| Rust binaries         | Embedded cargo-auditable dependency list                      | [Rust binaries](../rust-binaries.md)                                                                               |
+| 已记录的 Linux 崩溃   | 原始 note 记录、每个已记录线程的寄存器/信号及可选的映射候选项 | Linux x64 上由调用方提供的 pwntools；可选的 GDB/pwndbg；[已记录崩溃](../recorded-crashes.md)                       |
+| 桌面安装目录          | 运行时候选、支持文件、组件标记和后续操作                      | 有界的目录与文件头检查；[桌面应用](../desktop-applications.md)                                                     |
+| JavaScript / Electron | 模块、导入、source map、路由、IPC 和原生扩展关系              | Node.js 和 npm；[应用分析](../javascript-application-workflows.md)                                                 |
+| 网站                  | 页面结构、脚本、网络观察结果和按请求获取的截图                | Chrome 系浏览器；[浏览器分析](../browser-observation.md)                                                           |
+| 已保存的网络捕获      | 请求、响应、可访问的载荷和来源位置                            | HAR；原生 mitmproxy 捕获需要 Linux 上的 mitmdump；[捕获指南](../web-network-captures.md)                           |
+| 数据包捕获            | 端点、DNS、TLS SNI、协议分布和 HTTP 请求                      | 调用方提供的 tshark 和 capinfos；[pcap 指南](../pcap-analysis.md)                                                  |
+| .NET 程序集           | 元数据、CIL 指令、声明的原生依赖和构建对比                    | 静态检查；[托管代码指南](../managed-code-analysis.md)                                                              |
+| Android APK           | 清单声明、类、反编译的方法和引用                              | Linux/macOS/Windows x64 上的无界面 JADX 和完整 JDK；[Android 指南](../android-analysis.md)                         |
+| Android 设备          | 设备、软件包、进程、日志、转储、屏幕截图以及 APK/文件传输     | 调用方提供的 adb（模拟器或实体设备）；[ADB 指南](../adb-device-analysis.md)                                        |
+| JEB 项目              | 引擎支持的项目单元、工件摘要和类型/方法的伪代码               | 由调用方启动、提供 MCP 的 JEB 客户端，通过 REA_JEB_MCP_URL 选择；[JEB 指南](../jeb-analysis.md)                    |
+| Android 资源          | 解码后的清单、字符串表、语言区域和版本信息                    | 调用方提供的 Apktool 启动器；[资源指南](../apktool-resource-analysis.md)                                           |
+| Flutter 应用          | Dart 快照哈希、按 ABI 的库摘要及引擎构建溯源                  | 无（静态 APK 解析）；[Flutter 指南](../flutter-analysis.md)                                                        |
+| 固件                  | 区域、提取结果和转交原生分析的内容                            | Linux 上的 Binwalk / Unblob；[固件指南](../firmware-analysis.md)                                                   |
+| 抓包文件              | 指定字段、重复值、过滤条件与解码规则                          | Linux: TShark 4.x + prlimit; [抓包分析指南](../packet-captures.md)                                                 |
+| 录制的逻辑信号        | 解码注释、样本范围和诊断信息                                  | Linux: sigrok-cli 0.7.2 + prlimit; [信号记录指南](../signal-recordings.md)                                         |
+| 软件包与资源          | 文件清单、摘要、plist、Apple bundle 结构和提取的资源          | [制品与 JavaScript 指南](../javascript-artifact-reconstruction.md)、[Apple 应用](../apple-application-analysis.md) |
+| 进程行为              | 终端输出、交互、退出和文件系统观察结果，以及运行对比          | 支持原生 PTY 的 Linux/macOS；[进程捕获](../process-capture.md)                                                     |
 
 静态 JavaScript 和 .NET 检查读取提供的文件，不运行应用。运行时捕获会以你的用户权限运行目标或与之交互；各运行时指南说明了具体影响。
 
@@ -272,8 +270,6 @@ npx rea-agents@latest setup
 
 - [安装与设置](../installation.md)：智能体注册、提供方配置、更新和卸载。
 - [就绪检查与故障排查](../installation.md#check-readiness-for-your-task)：诊断特定智能体或分析引擎。
-- [CUDA / HIP](../gpu-code-objects.md)
-- [GGUF / safetensors](../model-artifacts.md)
 - [CLI 与 Evidence](../cli.md)：命令、提供方选择、快照、导入/导出和退出状态。
 - [MCP 契约](../mcp-contracts.md)和[智能体提示词](../mcp-prompts.md)：工具结果、会话和引导式调查。
 - [工具目录](../mcp-contracts.md#generated-catalog)：构建时生成的工具、提供方和 CLI 命令清单。

docs/reconstruction-obligation-ledgers.md

@@ -320,13 +320,6 @@ close a `packaged-process` obligation. A static-only source cannot close a
 runtime or process claim. Marking a claim `blocked` or `out-of-scope` records the
 disposition but does not silently count it as verified.
 
-The `summary` counts obligations. `by_status`, `by_application_layer`, and
-`by_source_state` place each obligation in exactly one bucket.
-`by_evidence_authority` groups obligations by the Evidence `authority` of their
-`authority_references`: an obligation counts once under each distinct authority
-it cites, so those counts can exceed `total`. A reference's own `state` and the
-obligation's `source_state` do not affect its authority bucket.
-
 The tool returns every obligation inline. Its `ledger_id` and `closure_digest`
 identify the complete result, including summaries, reports, ownership and
 dependency graphs, Evidence links, and limitations.

docs/reverse-engineering-tools.md

@@ -27,13 +27,11 @@ rea inspect-with-objdump ./program dwarf
 rea inspect-with-objdump ./program dwarf --follow-debug-links
 ```
 
-Captured stdout and stderr are retained up to a 16 MiB combined limit; `output_truncated` marks output beyond that limit. That cap has no runtime override.
-
-`inspect_with_objdump`, `rea list-objdump-architectures`, and one-shot `execute_rizin_command` accept `command_timeout_ms` (CLI: `--command-timeout-ms`). Omitted means 120000. The integer range is 1 to 2147483647. Target preflight shares one budget across stat and digest. The one-shot command receives that budget again. It applies on the next call; no restart is required. It does not raise the 16 MiB cap, a Ghidra or Hopper startup deadline, or a debugger session deadline.
+Captured stdout and stderr are retained up to a 16 MiB combined limit; `output_truncated` marks output beyond that limit.
 
 ## GDB
 
-Persistent GDB sessions, including the MCP workflow and one-shot `rea debug-with-gdb` CLI, are available only on Linux. REA verifies a live inferior's output descriptors through `/proc` before detaching it; it does not claim equivalent descriptor verification on macOS. Windows is also unsupported because owned Job Object cleanup can terminate debugger inferiors. On supported Linux hosts, `start_gdb_session`, `gdb_console`, `gdb_session_status`, and `close_gdb_session` manage a persistent GDB/MI session in MCP. The one-shot CLI requires a caller-selected durable TTY: `rea debug-with-gdb --inferior-tty /dev/pts/7 'file ./program'`. The TTY must remain available after GDB exits so a detached inferior can continue writing. MCP starts GDB with `--nx --quiet --interpreter=mi3`, retries initialization with MI2 if MI3 initialization returns an error and cleanup succeeds, waits for its prompt, and disables auto-loading. Pass optional `inferior_tty` to select the terminal that future inferior runs use; REA configures it before the session becomes ready and checks the exact value with GDB/MI. `gdb_session_status` reports the selected path, whether REA still considers the configuration verified, and whether invalid UTF-8 has been observed in MI bytes (`mi_invalid_utf8`) or stderr (`stderr_invalid_utf8`). Commands that can change the inferior TTY or redirect a run revoke that verification permanently for the session, so close retains GDB ownership if a live inferior remains. Closing a session with one live inferior and a verified TTY automatically detaches the target, which can resume execution; MCP clients receive destructive-operation annotations for this behavior. The console remains unrestricted and can run shell commands, change target state, access files, and use network in the REA process user's security context. Raw MI records and console/target/log streams are returned with Evidence; command output is retained up to 16 MiB and explicitly marked when truncated. GDB startup waits 10000 ms and each MI command waits 120000 ms. This release has no runtime override for those deadlines, the 16 MiB command output budget, session capacity, or the pending-command queue. `command_timeout_ms` does not change them.
+Persistent GDB sessions, including the MCP workflow and one-shot `rea debug-with-gdb` CLI, are available only on Linux. REA verifies a live inferior's output descriptors through `/proc` before detaching it; it does not claim equivalent descriptor verification on macOS. Windows is also unsupported because owned Job Object cleanup can terminate debugger inferiors. On supported Linux hosts, `start_gdb_session`, `gdb_console`, `gdb_session_status`, and `close_gdb_session` manage a persistent GDB/MI session in MCP. The one-shot CLI requires a caller-selected durable TTY: `rea debug-with-gdb --inferior-tty /dev/pts/7 'file ./program'`. The TTY must remain available after GDB exits so a detached inferior can continue writing. MCP starts GDB with `--nx --quiet --interpreter=mi3`, retries initialization with MI2 if MI3 initialization returns an error and cleanup succeeds, waits for its prompt, and disables auto-loading. Pass optional `inferior_tty` to select the terminal that future inferior runs use; REA configures it before the session becomes ready and checks the exact value with GDB/MI. `gdb_session_status` reports the selected path, whether REA still considers the configuration verified, and whether invalid UTF-8 has been observed in MI bytes (`mi_invalid_utf8`) or stderr (`stderr_invalid_utf8`). Commands that can change the inferior TTY or redirect a run revoke that verification permanently for the session, so close retains GDB ownership if a live inferior remains. Closing a session with one live inferior and a verified TTY automatically detaches the target, which can resume execution; MCP clients receive destructive-operation annotations for this behavior. The console remains unrestricted and can run shell commands, change target state, access files, and use network in the REA process user's security context. Raw MI records and console/target/log streams are returned with Evidence; command output is retained up to 16 MiB and explicitly marked when truncated.
 
 Before a normal close, REA checks for live GDB thread groups. If one remains and a durable `inferior_tty` is verified, REA asks GDB to detach it and confirms the detach before stopping the debugger. Without that sink, select and apply a disposition to each inferior through `gdb_console` (for example, detach or kill as appropriate), then retry close. REA never infers target ownership from a PID or path. When the MCP server shuts down, REA terminates only its directly owned GDB process after confirming no inferior or a sink-backed detach; otherwise it retains the process and its output streams for retry.
 
@@ -51,7 +49,7 @@ close_gdb_session {"session_id":"…"}
 
 Persistent command Evidence retains the caller-selected and resolved startup paths in `parameters.launch_provenance`. These paths describe launch provenance, not the current target after unrestricted commands. `rizin_debug_session_status.output_invalid_utf8` reports whether lossy frame decoding has been observed during the session. Command Evidence sets `output_invalid_utf8` only when loss was observed in frames collected for that command, including retained partial output; earlier startup or command frames do not mark later valid output as lossy.
 
-Session status retains up to 64 recent protocol frames. Each history entry keeps a complete-character UTF-8 prefix of at most 16 KiB, plus a truncation marker when needed; `recent_output_truncated` reports omitted history. This history budget also accounts for replacement characters from invalid UTF-8. It does not shorten command Evidence, which has its own 16 MiB output budget. Rizin debug startup waits 30000 ms and each command frame waits 120000 ms. This release has no runtime override for those deadlines, the 16777216 byte frame cap, the 16777216 byte command-output cap, the 4096 frame command cap, session capacity, or the pending-command queue. Evidence names the cap that stopped the command. The one-shot `command_timeout_ms` setting does not change a debug session.
+Session status retains up to 64 recent protocol frames. Each history entry keeps a complete-character UTF-8 prefix of at most 16 KiB, plus a truncation marker when needed; `recent_output_truncated` reports omitted history. This history budget also accounts for replacement characters from invalid UTF-8. It does not shorten command Evidence, which has its own 16 MiB output budget.
 
 ```sh
 rea debug-with-rizin --inferior-tty /dev/pts/7 ./program dr
@@ -63,7 +61,7 @@ rea debug-with-rizin --inferior-tty /dev/pts/7 ./program dr
 rea execute-rizin-command ./program iI
 ```
 
-Captured stdout and stderr are retained up to a 16 MiB combined limit; `output_truncated` marks output beyond that limit. One-shot commands use the `command_timeout_ms` budget described above. That 16 MiB cap has no runtime override.
+Captured stdout and stderr are retained up to a 16 MiB combined limit; `output_truncated` marks output beyond that limit.
 
 ## Cutter bridge
 
@@ -72,11 +70,8 @@ The client and plugin must support the current v2 handshake; older peers are
 rejected before dispatch because they cannot preserve cross-caller recovery proof.
 The client checks the final encoded request against the bridge's 16 MiB frame
 limit before dispatch; an oversized command does not retain a cleanup owner.
-Each bridge request waits 25000 ms. Discovery admits at most 256 descriptor
-candidates and reads and probes at most eight concurrently. A larger directory
-reports `bridge_directory_capacity_exceeded`. This release has no runtime
-override for the 25000 ms request deadline, the 16777216 byte frame, or the
-256-candidate discovery budget.
+Discovery admits at most 256 descriptor candidates and reads and probes at most
+eight concurrently. A larger directory reports `bridge_directory_capacity_exceeded`.
 
 Terminal receipts are recovered before another command, including from a new CLI
 invocation. A signed status response also confirms completion of older bridge

docs/rust-binaries.md

@@ -21,72 +21,11 @@ requires an absolute filesystem path and preserves that exact selection:
 
 ## Observations
 
-Complete delivery remains the default. For a dependency question, select the
-needed records on the first call instead of returning the complete graph:
-
-```json
-{
-  "name": "inspect_rust_binary",
-  "arguments": {
-    "path": "/artifacts/application",
-    "view": {
-      "collection": "packages",
-      "names": ["serde", "serde_derive"],
-      "fields": ["name", "version", "source", "dependencies"]
-    }
-  }
-}
-```
-
-`detail: "summary"` returns section ranges, root index, package/edge/cycle counts
-and compiler-hash count. A `view` selects compact delivery automatically;
-combining it with explicit `detail: "complete"` is an input error. The complete
-parent Evidence is retained in the MCP session and remains exportable. Subsequent
-`inspect_analysis_view` calls accept that `parent_evidence_id`, or its portable
-Evidence file, without reopening the binary:
-
-```json
-{
-  "source": {
-    "kind": "retained-evidence",
-    "evidence_id": "ev_<parent digest>"
-  },
-  "view": {
-    "kind": "rust",
-    "collection": "edges",
-    "from_indices": [12],
-    "limit": 20
-  }
-}
-```
-
-Package filters accept exact `names`, `versions` and original `indices`; edge
-filters accept original edge `indices`, `from_indices` and `to_indices`.
-Filters intersect, and an empty filter array selects nothing. `offset` counts
-matching records; `limit` defaults to 64. Pages retain original indices scoped
-to the parent Evidence, selected fields, examined coverage and the next offset.
-Default package fields omit dependency vectors; explicitly select
-`dependencies` to obtain direct references. No dependency path is traversed.
-
-The CLI uses the same views and requires an exclusive output bundle for compact
-delivery so the complete Evidence survives process exit:
-
-```bash
-rea inspect-rust-binary /artifacts/application --json \
-  --view '{"collection":"packages","names":["serde"],"fields":["name","version"]}' \
-  --evidence_output /artifacts/rust-evidence.json
-```
-
-Compact results distinguish complete embedded-record coverage from unknown
-runtime dependency coverage. A missing section remains unknown rather than an
-empty dependency set. Retained views describe the captured artifact digest;
-they do not assert that the current file or running application is unchanged.
-
 The inline Evidence result contains the artifact path, SHA-256, byte length,
 container format, architecture, word size, and byte order. When a `.dep-v0`
 section is present, `auditable_metadata` contains:
 
-- `section_name`, `.dep-v0` for ELF and PE or `__DATA,.dep-v0` for Mach-O;
+- `section_name`, `.dep-v0` for ELF and PE or `__DATA,.dep-v0` for thin Mach-O;
 - `file_offset` and `section_bytes`, the exact file range of the compressed section;
 - `compressed_bytes` and `uncompressed_bytes`;
 - `format_version`, the embedded integer, or `null` when the field is omitted;
@@ -124,17 +63,8 @@ verified. An omitted revision remains `null` and follows revision 0 semantics.
 Embedded names and versions are file content. They do not authenticate the
 packages or the compiler.
 
-ELF, PE, thin Mach-O and one selected slice of a universal Mach-O are the
-supported containers.
-A universal (FAT) Mach-O needs `architecture` (`x86`, `x86_64`, `arm`
-or `arm64`; CLI `--architecture`). REA reads its own FAT table, without `lipo`,
-and validates the selected slice's range, alignment and Mach-O header CPU
-against the table. The result keeps the universal file as `artifact` (its
-SHA-256 and size), adds `selected_slice` with the slice offset, length, raw CPU
-type/subtype and the FAT table digest, and reports the section and rustc-path offsets as a
-file offset inside that slice. Without `architecture`, or when the file has no
-such slice or several, the request fails on `architecture` and lists the slices
-present. `architecture` on any other image is rejected rather than ignored.
+Universal Mach-O containers are unsupported. Select a thin slice first. ELF,
+PE, and thin Mach-O are the supported containers.
 
 Package and dependency counts are checked against the minimum required JSON
 representation before graph allocation or schema cloning. Oversized graphs

docs/signal-recordings.md

@@ -126,9 +126,6 @@ matching help retains original one-based line numbers. Empty query selects all.
 returns all remaining matches; CLI `--all` and `--limit` conflict.
 The window reports examined, matching and returned records and `has_more`.
 A filtered empty page is not evidence that the installation has no decoders.
-When sigrok reports a selected decoder ID as not installed, help and decoding
-return `invalid_request` naming `decoder` or `decoders`; omit `decoder` to list
-installed IDs. An installed decoder that fails to load remains an execution failure.
 
 Discovery refuses more than 65,535 line separators before constructing record
 objects (65,536-line representation budget), in addition to the 4 MiB output cap.

docs/specs/agent-environments/prefix-variance/plan.md

@@ -1,18 +0,0 @@
-# Plan
-
-1. Move tool naming (`parameterNames`, `pathTemplate`, `toolName`,
-   `compareTools`) from `environmentManifestRules.ts` to a new
-   `environmentManifestNames.ts`, so the rules module has room for the rule.
-2. Add `prefix-variance` to `TEMPLATE_RULES`. A `prefix-variance` parameter
-   records the rule it shares (`sharedRule`), which names it and keys it.
-3. Add the pass after `sibling-variance`: walk positions in order, index the
-   opt-in parameters at each position by their preceding parts, template
-   qualifying literals, then rebucket by naming key, keeping a tool's own rule
-   for each merged position.
-4. Share the 32-segment split between the three comparing passes and list the
-   segment-limited rules once for the limitation.
-5. Document the rule in the view schema description and in
-   `docs/web-network-captures.md`.
-6. Tests: shared positions across methods and depths, the spelling condition,
-   merges that keep a tool's own rule, pairs, format-rule positions and the
-   segment limit.

docs/specs/agent-environments/prefix-variance/spec.md

@@ -1,59 +0,0 @@
-# Share templated positions across tools
-
-Issue: https://github.com/morluto/rea/issues/4933
-
-## Outcome
-
-A session usually edits one scratch entity: it creates it, then updates and
-deletes it at a fixed path such as `/api/v1/collections/0RZ576QZQA5KG`. The
-manifest templates a segment only when sibling routes of the same method vary
-there, so those writes stay literal tools (`patch_collections_0rz576qzqa5kg`)
-even though the reads of the same collection were templated as
-`/api/v1/collections/{collection_id}`. A literal write tool addresses one
-entity that may not exist in a later state, and nothing can model its effect.
-
-A new opt-in template rule, `prefix-variance`, templates such a literal with
-the parameter another tool already uses at that position, so the write becomes
-`patch_collections_by_collection_id` on the same template as the read.
-
-## Requirements
-
-- `prefix-variance` applies only when listed, after every other opt-in rule, so
-  it can share the parameters they produce.
-- A literal at position `p` is templated when another tool on the same origin,
-  of any method and any segment count, has a parameter at `p` from one of the
-  other opt-in rules, after the same preceding parts. Parameters in the
-  preceding parts compare by the rule that names them, so a position templated
-  by `prefix-variance` matches the parameter it shares.
-- The literal qualifies when it is one of the values such a parameter
-  observed at that position, when it carries a digit and has the length and
-  character classes (digits, lower case, upper case, each other character) of
-  one of them, or when every value the parameter observed, one or more, has one
-  length of eight or more characters, as generated identifiers often do, and
-  the literal has that length and uses only their character classes, so an
-  identifier that happens to hold no digit still qualifies. An empty literal, a
-  stop word or a `v1`-style version never qualifies. Each parameter's spelling
-  is summarised once, so a literal is checked without rescanning its values,
-  and a value longer than 128 characters is compared only exactly, so a huge
-  segment costs no classification.
-- Positions templated by the four format rules are never shared, so
-  `/api/teams/{numeric}` still absorbs no literal.
-- Values stay with the parameter that observed them: when parameters of
-  different rules share a position, the literal shares the one that observed
-  it, else the earliest one it is spelled like.
-- The parameter takes the name of the parameter it shares (`collection_id`,
-  `uid`, a pair's `_namespace` and `_name`) and is labelled `prefix-variance`.
-- Tools whose routes now match, by method and by the rule that names each
-  parameter, merge. A merged parameter keeps the rule of a tool that templated
-  that position itself, when one did.
-- Like the sibling rules, it compares routes of at most 32 segments and says so
-  in a limitation when a longer route exists.
-
-## Non-goals
-
-- No change to the default rules or to any other rule: manifests that do not
-  list `prefix-variance` are byte-for-byte unchanged.
-- No templating from response bodies, such as an id a create returned; the
-  manifest reads request lines only.
-- No change to which groups are excluded: a write whose response has no body
-  or content type outside `/api/` is still excluded as `non-json`.

docs/specs/agent-environments/prefix-variance/tasks.md

@@ -1,10 +0,0 @@
-# Tasks
-
-- [x] Record the outcome, requirements and non-goals.
-- [x] Move tool naming into its own module.
-- [x] Add the `prefix-variance` rule, its names, its merge and its limitation.
-- [x] Document the rule in the schema and the capture guide.
-- [x] Add rule tests.
-- [x] Run static, formatting, duplication, documentation and test gates.
-- [x] Project the 51 corpus captures with and without the rule and record the results.
-- [x] Rebuild five randomly drawn environments end to end and compare them with their published versions and the live applications.

docs/specs/agent-environments/prefix-variance/verification.md

@@ -1,149 +0,0 @@
-# Verification
-
-Verified base: 33b0643e on main 1629266e (the rule, the alias removal `knip`
-asked for, and the fixed-length clause the end-to-end runs below led to). Executed on macOS with Node v22.23.1 (the repository pins
-24.18.0 in `.nvmrc`, which was not installed).
-
-## Gates
-
-- `npm run build:cached`, `npm run check:fast` (typecheck and lint),
-  `npm run format:check`, `npx knip`, `npm run scan:todos`,
-  `npm run docs:check`, `npm run verify:test-discovery` and
-  `npm run mcp-catalog:check`: passed.
-- `npm run jscpd`: 3.49% duplicated lines over 3561 files with 3067 clones;
-  main measures 3.49% with 3068, since the shared segment-limit split removes
-  one clone.
-- oxlint reports no new finding on the changed files. The manifest accumulator
-  keeps main's three warnings (file length, and the complexity and parameter
-  count of its record append), one line longer.
-- `npx vitest run --project domain --project services`: 7119 passed, 5
-  pre-existing skips.
-- `npm run test:prepare`, then `npm run test:focused --` the analysis-view MCP
-  and CLI boundaries, the compact input schema and tool schema validity
-  boundaries, and the environment serve and export boundaries:
-  7 files, 76 passed.
-
-New tests in `environmentManifestView.test.ts` cover:
-
-- a literal shared across methods and depths, and the same capture without the rule;
-- the spelling condition: same classes and length, case, missing digit, a colon word, a version;
-- a digit-free member of a fixed-length identifier family, against a shorter word, a hyphenated
-  value and a family shorter than eight characters;
-- merges that keep a tool's own rule, including a sibling-variance parameter under a shared one;
-- both halves of a templated pair;
-- format-rule positions and the segment limit.
-
-## The showcase captures
-
-The 50 showcase captures (45 HAR inspections and 5 `capture_browser_scenario`
-captures) were projected with main's build and this branch's.
-
-- Without the rule, both builds give identical results for every capture: the
-  manifest with no rules, the manifest with `after-uid-literal`,
-  `opaque-token`, `sibling-variance` and `sibling-pair-variance`, and the
-  environment-state view. 150 of 150 outputs hash equal.
-- With `prefix-variance` added to `after-uid-literal`, `opaque-token` and
-  `sibling-variance`, 69 literal tools in 10 captures are templated, 25 of them
-  writes:
-  - Komga: collection and readlist `PATCH` and `DELETE`, book pages.
-  - n8n: workflow `PATCH`, `DELETE` and archive, and the reads of a workflow
-    whose id holds no digit.
-  - Memos: memo `PATCH` and `DELETE`, user settings reads, and the reads of
-    two memos whose ids hold no digit.
-  - Navidrome: playlist `PUT` and `DELETE`.
-  - Mealie: recipe `PATCH` and `DELETE`.
-  - Grist: document `PATCH` and `DELETE`, and table record writes.
-  - Redpanda Console: subject and topic writes.
-  - Sentry: release `PUT` and `DELETE`.
-  - Shlink: short URL `PATCH`.
-  - Mattermost: `me` reads, which `sibling-variance` already folds into the
-    user parameter.
-
-  Tools go from 1591 to 1578, because Redpanda Console's per-subject reads and
-  the per-memo and per-workflow reads merge.
-
-- Literals the rule leaves alone, as intended, include Espo CRM `layout`,
-  Federal Register `facets`, Ghost `slug`, Shlink `stats`, Lychee
-  `Metrics::photo` and Vault's path names.
-- The environment-state view succeeds on every capture with the rule. Its types
-  move to the templated collections (531 become 526 as literal ones merge); the
-  one fewer item view is the Redpanda Console merge.
-
-With the write plans of #5600 (its branch with this commit and main merged in,
-locally):
-
-- Served write tools rise from 33 to 39: Komga collection create, update and
-  delete; n8n workflow delete; Sentry release update and delete.
-- Write tools with no state target fall from 102 to 87.
-- The newly modelled tools that stay unserved are limited by the capture:
-  - no read after the write: Komga readlists, Mealie, Navidrome, Redpanda Console;
-  - n8n's item read shows an expanded `shared` relation its create response
-    never returned;
-  - Shlink returns `tags` sorted while the update echoes the request's order.
-
-## Five environments end to end
-
-Five of the ten environments the rule changes were drawn at random, redrawing
-until the draw held one whose new writes are served: Komga, Mealie, n8n,
-Sentry and Shlink. Each was rebuilt on its own Linux VM with `npm pack` of
-#5600, main and this branch merged locally, from the same scoped HAR as its
-published version: manifest with `prefix-variance`, exported bundle, smoke
-task, the generated retrieval tasks for `gpt-oss-120b` and `GLM-5.3-Flash`, and
-a dry-run dataset. Where writes are served, hand-written write tasks ask for a
-change in plain language and are graded from the environment's state through
-`data/get`. The first n8n run found that a digit-free workflow id stayed
-literal; the fixed-length clause fixed it, and n8n was rebuilt.
-
-| Environment | Tools (published → rebuilt) | Served from state (reads / writes) | Retrieval gpt-oss | Retrieval GLM | Writes gpt-oss | Writes GLM |
-| ----------- | --------------------------- | ---------------------------------- | ----------------- | ------------- | -------------- | ---------- |
-| Komga       | 42 → 46                     | 26 / 3                             | 12/12 (was 11/12) | 12/12 (11/12) | 3/4            | 4/4        |
-| Mealie      | 39 → 39                     | 36 / 0                             | 12/12 (12/12)     | 12/12 (12/12) | –              | –          |
-| n8n         | 30 → 33                     | 17 / 1                             | 9/9 (9/9)         | 9/9 (9/9)     | 2/2            | 2/2        |
-| Sentry      | 34 → 34                     | 26 / 3                             | 12/12 (12/12)     | 11/12 (12/12) | 2/4, rerun 0/4 | 4/4        |
-| Shlink      | 17 → 17                     | 5 / 0                              | 5/7, rerun 7/7    | 7/7 (7/7)     | –              | –          |
-
-Every smoke task passed. The misses:
-
-- Sentry writes with gpt-oss: every failed episode passed `id: "sentry"` for
-  the `/api/0/` segment the tool schema describes as `observed: 0`, so its calls
-  addressed `/api/sentry/…`; every passing episode, and every GLM episode, passed
-  `0`. The served tools work; the format-rule parameter for a segment that only
-  ever held `0` invites the guess.
-- Komga update with gpt-oss and Shlink's first gpt-oss run: the model provider
-  rejected tool calls the model generated (`null` and `undefined` for optional
-  query arguments) before the environment saw them.
-- Sentry `qa-03` with GLM: the model never called the alert-rules tool.
-
-The same calls were also replayed against the live applications, seeded by
-the same scripts (ids differ, so each side maps its ids to names):
-
-- Komga 1.29.1, 9 of 12 steps equal: create, update and delete of a
-  collection and the reads after them agree except for the generated id. The
-  collection list after a create omits the new collection, because that list
-  keeps its recorded membership, and the 404 for a deleted collection replays
-  the recorded body with its path and timestamp.
-- n8n 1.123.85, 3 of 8 steps equal: n8n refuses to delete a workflow that is
-  not archived (400) and the environment deletes it; the workflow list replays
-  its recorded response, so a delete does not show in it; archiving is not
-  served. The read of the digit-free workflow failed in the first build (the
-  state held only its list fields) and agrees in the second, apart from ids the
-  seed generates.
-
-## After the review round
-
-The branch merged main at 52c84f6f, then kept each shared position's values
-with the parameter that observed them (one donor per naming rule, the literal
-taking the donor that observed it, else the earliest it is spelled like),
-summarised each donor's spelling once, and let one observation form a
-fixed-length family, as the requirement states. Two new tests, a mixed-rule
-position and a single observed workflow id, fail on the previous head and pass
-here. The gates above passed again (domain and services 7255 passed with 5
-pre-existing skips; the focused boundaries 76; `jscpd` 3.49%). Over the 50
-showcase captures the tools with and without `prefix-variance` are unchanged,
-name for name: 69 literal tools templated, 25 of them writes.
-
-A second review round bounded the spelling summary: characters are classified
-in one pass, and a value longer than 128 characters is compared only exactly.
-Its test fails on the previous head, the gates passed again (domain and
-services 7257, focused boundaries 76, `jscpd` 3.49%), and the census over the 50
-captures is again unchanged.

docs/specs/agent-environments/state-coverage/plan.md

@@ -1,32 +0,0 @@
-# Implementation plan
-
-1. In `environmentStateRules.ts`, parse pointers into tokens and let `at` and
-   `replaceAt` read and replace element 0 of a one-element array at the root
-   or in one member; extend `locateItem` with those forms after the object
-   forms, requiring an identity name there; add `identityCandidates`, the
-   identity names then suffix-named fields, and let `locateList` prefer arrays
-   identified by name, then arrays of two or more items identified by suffix.
-2. In `EnvironmentStateExtraction.ts`, plan lists with the shared candidates,
-   treat an empty recording as unconstraining, accept a suffix-named field only
-   once a recording shows it distinct across two or more items, leave reads
-   without a list or identity to documents, drop the written-path requirement
-   and the `not-entity` fallback, record `path-varies` apart from
-   `query-varies`, and keep each entity's earliest sighting;
-   `environmentStateMerge.ts` cites records in timeline order. Remove
-   `not-entity` from the reason type and result schema, add `path-varies`, and
-   describe the new pointer forms and `field-name` basis.
-3. Move the classification of retained bodies (none, base64, cut, JSON, text)
-   into `replayedBody` in `environmentSource.ts`, which owns recorded
-   exchanges; replay renders from it and tool descriptions read its JSON case.
-4. Make `environmentToolDefinitions` take the `EnvironmentSource`; describe the
-   first `2xx` JSON record, else the first JSON record labelled with its status,
-   one level deep with the state's list rule and the existing sample budget;
-   list the manifest tool's statuses; and charge the whole description and the
-   tool's MCP annotations to the catalog reservation. Update the serve and
-   bundle callers.
-5. Let the tool definitions own the MCP annotations derived from the method and
-   the query-`POST` rule; `serveEnvironment.ts` registers them and the card
-   leaves them out.
-6. Cover domain, services, adapters and the compiled MCP boundary; document the
-   rules in the capture guide, descriptions and hints in the agent environments
-   guide, and the contract text.

docs/specs/agent-environments/state-coverage/spec.md

@@ -1,99 +0,0 @@
-# Wider environment state coverage and tool descriptions
-
-Issue: https://github.com/morluto/rea/issues/4933
-
-## Outcome
-
-The `environment-state` view backs more read tools with state, and a served
-environment tells agents more about each tool. Read-only paths whose responses
-are not entities become documents, listed items may be identified by an
-`…Id` or `…_id` field, an item wrapped in a one-element array is located
-inside it, and reads that vary by path get their own recorded reason. Each tool description says what the tool returns and which statuses
-were recorded, and every MCP tool carries method hints. This increment adds no
-tool, view kind, provider, network activity or write effect.
-
-## Requirements
-
-- A `GET` list tool (its template does not end in a parameter) that yields no
-  item or list plan holds its latest initial value as a `document` when its
-  initial reads have one request line, whether or not the capture writes its
-  path, unless its value changed between two of those reads across any
-  recorded write (even under another root), which leaves it `fields-differ`. A
-  value whose rendered JSON exceeds 256 KiB stays `rendered-oversize` and is
-  replayed from the recorded body, which itself fit. More request lines give
-  `path-varies` when they differ by path (a template with a parameter before
-  its end) and `query-varies` when they share one path. With every such read
-  now a document, `path-varies`, `query-varies`, `body-unusable` or
-  `rendered-oversize`, the unreachable `not-entity` reason leaves the result
-  schema, and `no-identity` names item tools only. A document holds the value
-  of its one `path`.
-- When no path parameter proves an identity and no identity name identifies
-  the listed items, the `field-name` identity is the first key of the first
-  listed item, in its order, whose name ends in `Id` or `_id`, that every item
-  carries as a distinct string or number, and that at least one initial
-  recording shows distinct across two or more items. The last condition goes
-  beyond "every item carries it distinctly": one item satisfies that
-  vacuously, and a lone item's suffix-named fields are often foreign keys (a
-  reaction keyed by its user, a comment by its post), so a list that only ever
-  held one item stays a document. Empty recordings constrain no field.
-  Identity names keep precedence, also when choosing among an envelope's
-  arrays, where a suffix-named field identifies only an array of two or more
-  items.
-- An item response that is a root array of exactly one object, or an object
-  with one member holding such an array, locates its entity at `/0` or
-  `/<member>/0` when one of the identity names in that object repeats the path
-  value. Objects at the root or in one member keep precedence. `at` and
-  `replaceAt` read and replace exactly these forms besides the root and one
-  member, so the gate and renderers run unchanged.
-- An entity's state order is its earliest sighting on the timeline and it cites
-  its records in timeline order, whichever plan observed it first.
-- Each tool description reads `METHOD template; <returns>; recorded statuses
-  …; replays retained records […]; evidence ev_…` after the untrusted-catalog
-  warning. `<returns>` describes one level deep the first cited `2xx` record
-  replay answers as JSON: an object's fields, an array of objects' fields, or
-  an envelope whose member lists objects, where a list is an array of objects
-  found by the state's list rule; an empty field set reads `with no fields`.
-  Only when no `2xx` record replays as JSON does the first cited JSON record of
-  another status give it, labelled `status <code> returns …`; with no JSON
-  record it is omitted. The statuses are the manifest tool's `statuses`, the
-  one owner of that set (`no recorded status` when it is empty). Field names
-  and statuses are sampled within the description sample budget and charged
-  with the whole description to the catalog reservation before it is retained.
-  One owner in the environment source classifies each retained body as none,
-  base64, cut, JSON or text; replay answers from that classification and
-  descriptions read only its JSON case.
-- MCP tools carry `readOnlyHint` (true for the safe methods `GET`, `HEAD`,
-  `OPTIONS` and `TRACE`, and for query `POST`s),
-  `destructiveHint: true` for `DELETE` (unset for other writes, so the MCP
-  default applies, and for reads, where clients ignore it), `idempotentHint`
-  (true for the safe methods, `PUT` and `DELETE`) and `openWorldHint: false`. The
-  tool definitions own the hints and charge them to the catalog reservation;
-  the environment card keeps its `name`, `description`, `inputSchema` tool
-  shape.
-
-## Acceptance and limits
-
-Synthetic captures cover read-only documents, `path-varies` and
-`query-varies`, suffix-named identities with their key order, their
-two-item proof, empty first recordings and their precedence (including the
-choice between an envelope's arrays), a Ghost-like `{"posts":[...]}` item under
-a trailing-slash path merging with its list view, a root one-element array, a
-one-element filtered list that stays unidentified, and the pointer forms. The
-Grafana-shaped fixture covers documents for its read-only paths (its one-member
-team list among them) and object, array and enveloped-list descriptions;
-synthetic sources cover the `2xx` preference over an earlier error body, the
-first of several JSON records, the labelled fallback, the manifest's statuses,
-empty, scalar and fieldless bodies, a truncated member name, a name whose
-JSON quoting exceeds the sample, a recorded body under 256 KiB whose rendered
-JSON exceeds it, non-JSON bodies and the catalog budget; the in-process and
-compiled MCP servers advertise the
-hints. A filtered list may still answer with one element whose identity name
-repeats the requested value; list filters, pagination, lossless big integers
-and cross-endpoint entity linking remain out of scope. Documents inline whole
-recorded values and enlarge the state result; agent tokens, CPU time and peak
-memory of the state and description build were not measured.
-
-## Deferred issue criteria
-
-Serving from the state, the AgentEnv data plane and write effects remain later
-increments of #4933. This PR must reference rather than close the issue.

docs/specs/agent-environments/state-coverage/tasks.md

@@ -1,16 +0,0 @@
-# Tasks
-
-- [x] Record the coverage and description contract and its limits.
-- [x] Extend pointers, item location and identity candidates.
-- [x] Require two distinct items before a suffix-named field identifies a list.
-- [x] Hold read-only non-entity reads as documents, retire `not-entity` and
-      separate `path-varies` from `query-varies`.
-- [x] Order entities by earliest sighting and cite records in timeline order.
-- [x] Classify retained bodies in one owner and describe tool responses,
-      preferring `2xx` records, with the manifest's statuses.
-- [x] Advertise MCP tool annotations, charged to the catalog, without changing
-      the card.
-- [x] Add domain, services, adapters and compiled-boundary coverage.
-- [x] Document the rules, descriptions and hints; update the contract text.
-- [x] Run static, formatting, duplication, documentation and test gates and the
-      real-capture measurement.

docs/specs/agent-environments/state-coverage/verification.md

@@ -1,123 +0,0 @@
-# Verification
-
-Verified base: 7a668b73f4783b42eb0e8ce1eeff079f86d53e22 (the environment-state
-view branch).
-
-Executed on the implementation worktree with its existing locked installation
-under Node.js v22.23.1 (the repository pins 24.18.0, which was not available);
-every check below ran as written in this pass, after the last source change.
-
-- `npm run format` then `npm run format:check`: passed.
-- `npm run check:fast`: typecheck and lint passed (3959 files, no errors). The
-  touched files carry two lint warnings, both present on the base: `max-params`
-  in `environmentReplay.ts` and an unused `_` in `environmentCapacity.test.ts`.
-- `npx knip`: passed (exit 0).
-- `npm run jscpd`: 3.40% duplicated lines over 3348 files, under the 3.5%
-  gate. The three clones that touch changed test files pair the same blocks as
-  on the base; none involves code this change adds.
-- `npm run scan:todos`: no markers.
-- `npm run docs:check`: the built documentation checks and the README
-  consistency conformance test (5 tests) passed.
-- `npx vitest run --project domain --project services`: 341 files, 5859 tests
-  passed, 5 pre-existing skips.
-- `npm run build:cached`: passed.
-- `npm run test:focused --` the environment serve adapters and capacity tests,
-  the environment serve MCP boundary, the environment serve and export CLI
-  boundaries, the environment serve shutdown process boundary, the
-  analysis-view MCP and CLI boundaries, the compact input-schema contract and
-  MCP boundary, the tool-schema validity boundary, the analysis-detail and
-  advertised-input-example contracts and the qlog acceptance test: 14 files,
-  113 tests passed, 1 pre-existing skip.
-
-Real captures (outside the test suite): the built view ran through the
-application service on the same 44 recorded captures (39 HAR, 5 browser
-scenario) with all three template rules, in 7 to 50 ms each. 42 produced a
-state, and the same two browser-scenario captures are refused with
-`resource_constraint` as on the base. The base column is the brief's baseline,
-which the same script reproduced on the base build in an earlier pass; this
-pass did not rebuild the base.
-
-| Measure                            | Base  | This change |
-| ---------------------------------- | ----- | ----------- |
-| Types                              | 568   | 576         |
-| Entities                           | 2,213 | 2,246       |
-| Documents                          | 2     | 299         |
-| Item views                         | 211   | 213         |
-| List views                         | 497   | 504         |
-| Document views                     | 2     | 299         |
-| State-backed read tools (of 1,258) | 710   | 1,016       |
-| Recorded: `not-entity`             | 306   | (retired)   |
-| Recorded: `no-identity`            | 129   | 32          |
-| Recorded: `path-varies`            | (new) | 32          |
-| Recorded: `query-varies`           | 5     | 69          |
-| Recorded: `body-unusable`          | 32    | 32          |
-| Recorded: `list-differs`           | 31    | 31          |
-| Recorded: `no-init-recording`      | 26    | 26          |
-| Recorded: `query-body`             | 12    | 12          |
-| Recorded: `fields-differ`          | 3     | 4           |
-| Recorded: `envelope-varies`        | 4     | 4           |
-
-Seven list types gained a suffix-named identity (`permissionId`, `product_id`,
-`ItemId`, `user_id`, `channel_id`, `spl_id` and `eventId`). Seven more had one
-before the two-item proof and lost it, because every initial response listed a
-single item: an Airbyte organization, a Mattermost reaction and team
-membership, and a Redpanda broker and schema reference became documents; a
-NOAA station read is `query-varies` and a Redpanda consumer read
-`path-varies`. Two Ghost item tools render from `/members/0` and `/tags/0`. A
-third Ghost item tool is located at `/posts/0` but stays `fields-differ`: its
-recordings differ by an `include` query.
-
-State result size, as the JSON length of each Evidence summed over the 42
-states: 2,677 KiB on the base and 3,196 KiB now (+19%), measured by the same
-script. The largest growth per capture is Metabase (133 to 236 KiB), Directus
-(21 to 93), Redpanda Console (26 to 68) and Vault (9 to 43). Documents take
-492,516 of the 3,274,243 UTF-8 bytes of the results now; the base held two.
-Agent tokens, CPU time and peak memory of the state view were not measured.
-
-Tool descriptions on the 44 captures' manifests: all 44 catalogs were admitted
-within their reservation. 1,336 of 1,400 tools state what they return: 1,333
-from a `2xx` record and three labelled with another status (Miniflux and
-NocoDB 404, Shlink 501), because none of their records succeeded as JSON. The
-summaries add 261,502 bytes to a 1,185,893-byte catalog of names, descriptions
-and input schemas (median 136, 95th percentile 554, maximum 1,133 bytes per
-tool); five reached the field sample bound (one Keycloak, one Lychee and three
-Sentry tools with 46 to 105 fields). The MCP annotations add 113,182 bytes to
-`tools/list` and none to the card. Building a catalog took a median 1.6 ms and
-at most 7.6 ms (Metabase), after the source was loaded. Agent tokens, CPU time
-and peak memory of the description build were not measured.
-
-After merging the environment state view's review fixes (its branch at
-6ad63bcc, which also brings main's evidence-file sources), every gate ran
-again on the merged tree: `npm run check:fast`, `npm run format:check`,
-`npx knip`, `npm run scan:todos` and `npm run docs:check` passed; `npm run
-jscpd`: 3.39% duplicated lines over 3362 files; `npx vitest run --project
-domain --project services`: 344 files, 5914 tests passed, 5 pre-existing
-skips; `npm run build:cached`, then `npm run test:focused --` the serve and
-tool-definition adapters, the serve MCP and CLI boundaries, the export CLI
-boundary, the analysis-view MCP and CLI boundaries, the compact input-schema
-budget and the analysis-detail and advertised-input-example contracts: 10
-files, 98 tests passed.
-
-The real-capture comparison was repeated on the merged code, with the base
-measured on the merged state view without this change: all 44 captures now
-produce a state, and 1,011 of 1,277 read tools are state-backed against 625
-on the base (216 item, 416 list and 379 document views against 214, 409 and
-2). Recorded reasons: `no-identity` 216 to 32 and `not-entity` 310 to none;
-`query-varies` 5 to 76 and `path-varies` 36 are document reads under more
-than one query or path; `list-differs` 35, `body-unusable` 33,
-`no-init-recording` 28, `query-body` 12, `envelope-varies` 4 are unchanged,
-and `fields-differ` is 9 to 10.
-
-Not covered here: serving from the state, the AgentEnv data plane and write
-effects, which are later increments.
-
-## After the squash onto main
-
-The branch was squashed onto main once the state-serve branch merged (166fb082). Against a merge of the previous head
-into that main, the squash keeps both sides of every conflict and drops nothing of this branch. Two tests then failed
-on it and were refitted with the oversized-document fix in 2a926a0a: the bundle test of a state catalog over the
-discovery budget uses 300 read tools, inside the window where the state's catalog is refused and replay's, with its
-response summaries, still fits (280–320 by a probe), and the rea-state validation test names the pushed document by
-the count of documents the state holds. The replay-only card test pinned main's 11,131-byte card; it now pins this
-branch's 12,818-byte card, whose descriptions name each tool's recorded responses. The branch then merged main at
-d7ca93cc without conflicts.

docs/specs/agent-environments/state-serve/plan.md

@@ -1,44 +0,0 @@
-# Implementation plan
-
-1. Export the Evidence file authenticator from `environmentSource.ts` with a
-   `state` role, and validate a HAR capture there with the owned borrowing
-   parse so later views reuse it. Add `environmentState.ts` to check state
-   Evidence against a loaded source, build the served catalog (the tools a
-   state serves and the data plane its card declares), derive the state from
-   the capture through the analysis view service with the capture as retained
-   Evidence, and prepare it: unavailable when its catalog exceeds the
-   discovery budget under the served name or it cannot be derived.
-2. Add `environmentStateDocument.ts` to validate `rea-state/v1` documents
-   against the served types and views, and `environmentStateStore.ts` for the
-   live store with reset, atomic replace and the `data/get` snapshot.
-3. Export `selectsRecordedLine`, the body-taking `replayAnswer` and the path
-   rule `pathValueMatches` from `environmentReplay.ts`, export one recorded-body
-   predicate `stateBodyJson` from the state accumulator and `changesState` from
-   the state rules, and widen `collectionPathOf` to any value with a path, so
-   state answers reuse selection, matching, body and write rules.
-4. Add `environmentStateAnswer.ts` for item, list and document answers, the
-   recorded fallback and the answer function serve and export share.
-5. Declare the state data plane on the card in `environmentTools.ts`, taking
-   the data plane in an options object so the discovery budget reserves the
-   card and descriptions actually served.
-6. Add `stateIntake.ts` for parts, files on this host and downloads
-   (injectable fetcher and timeout, cancellation, coarse failure categories)
-   and `environmentDataPlane.ts` for the three methods, run one at a time in
-   arrival order and cancelled by the server's stop or the caller's
-   departure; let `serveEnvironment.ts` serve the shared catalog and answer
-   function, queue every message of a batch at arrival, bound the replies of
-   one response and stop the data plane before closing the listener.
-7. Make `environment-serve` prepare the state under its served name after
-   loading the source, add `--replay-only`, log an unavailable state as a
-   warning before binding, and report `state` in the stopped document.
-8. Let `environment-export` prepare the state the same way under the bundle
-   name, only after the name checks, and plan the served
-   tool count, the verifier check from the shared answer function, the `serve`
-   verifier and the README's serving section from it; report `state` in the
-   export output and expect the served count in the hosted-lane script.
-9. Cover services, adapters, cli-boundary, mcp-boundary and process-boundary
-   behaviour; document default serving, `--replay-only`, the fallback, the
-   answers, the data plane, the card and the export.
-
-No dependency, provider or REA tool contract changes. The only new network
-activity is an `https://` download that a `data/add` call names.

docs/specs/agent-environments/state-serve/spec.md

@@ -1,196 +0,0 @@
-# Serve the environment from its state by default
-
-Issue: https://github.com/morluto/rea/issues/4933
-
-## Outcome
-
-`rea environment-serve <manifest> --evidence <capture>` serves the environment
-from the initial state the capture observed, with nothing else to supply: at
-startup it derives the `environment-state` view of the capture in-process with
-the manifest's `template_rules`. Read tools whose views are state-backed answer
-from one live state, the `/agentenv` data plane implements `data/reset`,
-`data/add` and `data/get` against it, and the card advertises those operations
-and an intake declaration. `--replay-only` serves exactly the stateless replay
-main serves: every manifest tool replays its recordings, `/agentenv` answers every method as not found and the card is
-byte-identical. A state that cannot be derived, or whose catalog exceeds the
-discovery budget, starts the server in replay mode, logs why and reports it. Exported bundles serve the state by default,
-and their verifier and README match what they serve. Serving is read-only in
-this increment: write tools are not served from the state.
-
-## Requirements
-
-- Derive the state in the application layer, shared by serve and export:
-  `deriveEnvironmentState(source, capture, operation)` authenticates the
-  capture value the command already read (an owned snapshot authenticated by
-  the source load is reused, not parsed again), projects the
-  `environment-state` view with the manifest's `template_rules` through
-  `inspectAnalysisViewValidated` with the capture as retained Evidence (the
-  Evidence id equals that of a projection by hand, and the capture's strings
-  are not charged again as inline input, which refuses captures of a few MiB),
-  then applies `loadEnvironmentState`: `inspect_analysis_view` Evidence of kind
-  `environment-state`, its `parent_evidence_id` equal to the capture's, its
-  `template_rules` equal to the manifest's in the same order, and every view
-  naming a manifest tool, refusing otherwise with `invalid_request` whose issue
-  path starts with `state`. The source validates a HAR capture with the owned
-  borrowing parse, so the view reuses that validation.
-- `prepareServedState(source, capture, {name, operation})` first builds the
-  state catalog under the served name, then derives the state, and reports
-  `{served: true, evidence_id}` or
-  `{served: false, reason: "unavailable", code, message}` with the refusal's
-  projected code and message: a state catalog over the discovery budget is
-  unavailable with `resource_constraint`, and no state is derived for it. A
-  derived state whose catalog fits always serves from the state. The CLI
-  reports `{served: false, reason: "replay-only"}` itself for `--replay-only`
-  and derives nothing.
-- Keep one state store per server process, shared by every MCP session and the
-  data plane: entities keyed by type, collection and id with per-collection
-  order taken from the entities array, documents keyed by tool. `reset`
-  restores the Evidence state, `replace` installs a validated document whole,
-  and mutations are synchronous.
-- Answer item views by rendering the entity the path arguments name into the
-  recorded envelope of `envelope_ordinal`. Match arguments as replay does: a
-  held collection segment equal to the argument as written or after
-  percent-decoding, preferring verbatim spellings, and the identity as the last
-  argument percent-decoded, then as written, never re-split on `/`. Any held
-  entity answers, and query arguments only set `replay.exact_match`. Refuse an
-  entity the state does not hold, or one lacking a required field, as a tool
-  error and never invent a body.
-- Answer list views from the state only when the arguments name one of the
-  view's `checked_record_ordinals` exactly (every path and query value equal and
-  no recorded query parameter unsupplied), choosing among them as replay
-  chooses: every collection entity in state order for `membership: "all"`,
-  otherwise the recorded members the state still holds. A member lacking one
-  of the view's `required_fields` makes the call a tool error stating that the
-  state holds no complete member, never a partial body, as for items. Lines
-  recorded after a write or with other filters were never checked and answer
-  from recordings.
-- Answer document views with the state's value when the arguments name the
-  document's checked line exactly.
-- Answer recorded views, tools without a view and unrecorded requests from the
-  recording, labelled `state: {source: "recording", reason}`; label state
-  answers `state: {source: "state", view, …}` with the base record's replay
-  provenance and `truncated: false`; refuse a state answer over 256 KiB as a
-  tool error rather than cut it.
-- Serve `data/reset` (`{}`), `data/add` with exactly one `data` or `file` part
-  (`bytes`, a `file://` regular file or an `https://` download with a 30 s
-  timeout covering the body, no redirects and a streamed 32 MiB cap;
-  `mimeType` when given is `application/json`) and `data/get` (`{parts:
-  [{kind: "data", data: rea_state}]}`). A `file://` uri whose host is neither
-  empty nor `localhost`, or whose path is a UNC path, is `-32602` before
-  anything is opened. A document that `data/get` would write back past 32 MiB,
-  once it adds the members a document may omit, is `-32602`, so a reported
-  state always loads again. Anything else is `-32602`, including empty `parts`; a
-  failed download is `-32000`; errors never echo a uri or content and name a
-  coarse failure category in `error.data.reason`. Calls run one at a time in
-  arrival order across requests; every message of a batch is queued when the
-  batch arrives, so no other request's call lands between them, and
-  notifications run without a reply.
-- Stopping the server (`close` or `prepareShutdown`) aborts the data plane's
-  stop signal, and a request's own signal aborts when its client leaves: the
-  download in progress ends with reason `cancelled`, queued calls are answered
-  `-32000` with reason `cancelled` without running, and a `data/add` whose
-  file read finished after the cancellation does not replace the state.
-- A `file://` read whose descriptor close fails answers `-32000` and keeps the
-  descriptor in a server-lifetime owner. The next file read retries the close
-  first and, while it still fails, answers `-32000` without opening the file.
-  `close` retries it again and rejects while it is still open.
-- Bound one `/agentenv` response to 64 MiB of replies (twice the intake
-  limit). Each reply is measured in bounded JSON parts as it is produced, in
-  message order, and assembled only when it fits, so a reply past the budget is
-  counted but never serialized whole. Room is kept for every later reply's
-  budget error and for a batch's brackets and commas, so the body never
-  passes the budget; a reply that does not fit is replaced by `-32000` with
-  `data: {max_response_bytes, reply_bytes}`, unless that error is no smaller
-  than the reply, so the body is never built past the budget and small write
-  replies are kept.
-- Validate `rea-state/v1` documents against the served types and views: known
-  types, collections that instantiate their template, ids equal to the identity
-  field, unique keys, `view_fields` naming item or list views of the type
-  without setting the type's identity field to a value whose scalar text
-  differs from the entity's id (refused at that view's `fields`),
-  documents naming document views once at the initial path, and the optional
-  `state_evidence_id` and `types` that `data/get` reports equal to the served
-  ones. Refuse numbers without an exact native value and `__proto__` members.
-  Name the first problem by JSON pointer, never deeper than a caller-data
-  member (`fields`, `value`, `types`), and leave the state unchanged.
-- Keep record citations Evidence provenance: refuse `record_ordinals` or a
-  `record_ordinal` other than the Evidence's for that entity or document, and
-  hold the Evidence's citations only for loaded values equal to the Evidence's;
-  edited or added values cite none.
-- In state mode, declare `operations: ["data/reset", "data/add", "data/get"]`
-  and the `urn:agentenv:intake/v1` extension, describe tools as answering from
-  the state where it backs them, and leave out `POST`, `PUT`, `PATCH` and
-  `DELETE` tools other than query `POST`s. The discovery budget reserves the
-  card and descriptions actually served (`servedCatalog` returns the tools and
-  the data plane the card declares). A state catalog can exceed the budget a
-  replay catalog fits, so such a state is unavailable and the environment and
-  its export serve replay: everything main served and exported is still
-  served and exported.
-- The CLI has no `--state`; `--replay-only` (default false) serves replay
-  without deriving. Otherwise it prepares the state under the name it serves
-  (`ENVIRONMENT_NAME` or the manifest's). When the state is unavailable the
-  command logs a warning with the code and message through its listener logger
-  before binding, and serves replay. The stopped document's `state` member is
-  the report. `serveEnvironment` keeps taking an optional prepared state and
-  serves replay without one; the served catalog (`servedCatalog`) and the
-  answer function (`environmentToolAnswer`) are shared with export.
-- `environment-export` keeps the bundle command
-  `rea environment-serve /env/manifest.json --evidence /env/evidence.json` and,
-  after its name checks, prepares the state under the bundle name as that
-  server will, to predict what it serves, so a refused `--name` derives
-  nothing; its report is served or unavailable, never replay-only. The
-  verifier's `TOOL_COUNT` and the command's `tool_count` are the served tool
-  count, and its check tool and expected status come from calling the server's
-  answer function with `{}` on the first served `GET` tool without path
-  parameters whose answer is not an error. The verifier and smoke task use the
-  id `serve`. The README's "What the environment serves" section describes
-  serving from the state, the replay fallback and `--replay-only`, says which
-  applies to the bundle (with the code and message when the state is
-  unavailable), and keeps the not-emulation and untrusted-content caveats. The
-  export output adds `state`. The hosted-lane verifier script expects the
-  served count.
-
-## Acceptance and limits
-
-Services tests cover derivation (the by-hand Evidence id and state, a capture
-the manifest was not projected from, a capture inline admission refuses),
-the prepared reports (served, unavailable for a `capture_browser_scenario`
-capture with header values but no response bodies, unavailable with
-`resource_constraint` for a 350-tool read-only manifest whose replay catalog
-fits), bundle plans served from the state and in replay (tool count, check tool
-and status, a check whose state answer differs from replay's in record and
-status, a check that skips a tool the server cannot answer, the replay fallback
-of that 350-tool manifest, name refusals before any preparation, a manifest
-neither mode admits, verifier, smoke task and README wording), the loader
-refusals, store reset, order, round trip and
-atomic replace, the first-problem pointers, citation provenance after a load and
-every answer path: item (including percent-encoded collection segments and
-ids), list `all`, list `recorded`, lines recorded after a write or with other
-filters, a line replay's tie-break would not pick, document, recorded view, tool
-without a view, unrecorded request, missing entity, missing required field and
-the body limit, a view value that changes an entity's identity, and a list
-member missing a required field. Adapters tests cover the data-plane shapes,
-`-32602` for empty and malformed parts and invalid documents, inexact numbers,
-bytes, `file://` and its failure categories, `file://` uris naming another
-host or a UNC path, injected https downloads (status, declared and streamed
-size, the timeout whether or not the fetcher honours its signal), the default
-fetch's refused redirects, arrival-order application across requests, a batch
-another request's reset cannot split, cancellation by the server's stop and by
-a departed caller, a server that closes while a download is stalled, a
-retained state-file close that the next file read and `close` retry, the
-response budget, batches and notifications, the card declaration, absent write
-tools, a served query `POST`, the per-mode discovery reservation and a
-`data/add` that changes the next tool answer over MCP. The mcp-boundary tests serve the state the
-built CLI derives from only a manifest and a capture, and `--replay-only` with
-every manifest tool, `-32601` data-plane answers and a card whose SHA-256
-equals that of the card main serves for the fixture; the process-boundary test checks the stopped document's
-`state` for a derived state, `--replay-only` and an unavailable state, and the
-warning logged before binding; the cli-boundary export test checks the served
-tool count, the verifier and the README of an exported bundle. No test reaches
-an external network. Write effects, list filters beyond recorded lines and
-`tables` in the intake declaration are out of scope.
-
-## Deferred issue criteria
-
-Write effects are a later increment of #4933. This PR must reference rather
-than close the issue.

docs/specs/agent-environments/state-serve/tasks.md

@@ -1,32 +0,0 @@
-# Tasks
-
-- [x] Record the serving contract, requirements and deferred increments.
-- [x] Load and cross-check state Evidence for a served source.
-- [x] Add the store, the document validator and the snapshot.
-- [x] Answer item, list and document views from the state with recorded
-      fallbacks.
-- [x] Serve the data plane and declare it on the card; leave write tools out.
-- [x] Address review: answer lists and documents only from checked lines,
-      match item arguments as replay does, reserve the served card only, keep
-      record citations Evidence provenance, and run data-plane calls in arrival
-      order with a tested download timeout.
-- [x] Derive the state from the capture at startup, as retained Evidence, with
-      the loader's checks; reuse the capture's validation.
-- [x] Replace `--state` with `--replay-only`, fall back to replay with a logged
-      warning when no state can be derived, and report `state` when stopped.
-- [x] Derive the state in `environment-export` to plan the served tool count,
-      the verifier check and the README; report `state` in its output.
-- [x] Add services, adapters and boundary coverage; remove the `--state` flag
-      tests.
-- [x] Document default serving, `--replay-only`, the fallback, answers, data
-      plane, document format, card and export.
-- [x] Address review: serve and export replay when the state's catalog
-      exceeds the discovery budget, check the bundle name before preparing the
-      state, keep replay-only out of export plans, test a check the state
-      answers differently from replay, and pin main's replay card digest.
-- [x] Address review: bound one `/agentenv` response's replies, queue a
-      batch's messages together at arrival, cancel the running download and
-      queued calls when the server stops or the caller leaves, refuse
-      `file://` uris naming another host or a UNC path, refuse view values
-      that change an entity's identity, and apply list views' required fields.
-- [x] Run static, formatting, duplication, documentation and test gates.

docs/specs/agent-environments/state-serve/verification.md

@@ -1,79 +0,0 @@
-# Verification
-
-Verified base: 6676582675e08574146a812ae58cff67e2e53282 (this branch's head),
-with the review fixes of this pass uncommitted.
-
-Executed on the implementation worktree on macOS with Node v22.23.1 (the
-repository pins 24.18.0 in `.nvmrc`, which was not installed). Every check
-below ran as written after the last source change, in this order.
-
-- `npm run format` then `npm run format:check`: passed (4330 files).
-- `npm run check:fast`: typecheck and lint passed. The lint report holds 0
-  errors and no diagnostic in any file this pass touches.
-- `npx knip`: passed (exit 0, no findings).
-- `npm run jscpd`: 3.37% duplicated lines over 3373 files (2800 clones), under
-  the 3.5% gate; no clone involves a file this pass changed.
-- `npm run scan:todos`: passed, no markers.
-- `npm run docs:check`: the built documentation checks (6 tasks) and the README
-  consistency conformance test (5 tests) passed.
-- `npx vitest run --project domain --project services`: 347 files, 5948 tests
-  passed, 5 pre-existing skips.
-- `npm run build:cached` (the built output already included this pass's
-  sources), then `npm run test:focused --` the serve CLI, MCP and process
-  boundaries, the export CLI boundary, the CLI startup imports, the agentenv
-  verifier identity boundary, the bundle package pin conformance test, the CI
-  change scope boundary, the analysis-view CLI and MCP boundaries, and the
-  `serveEnvironment`, `serveEnvironmentState`, `environmentCapacity` and
-  `stateIntake` adapters tests: 14 files, 335 tests passed.
-- After this file was written: `npm run format`, `npm run format:check`,
-  `npm run scan:todos` and `npm run docs:check` passed again.
-
-The review fixes are covered by these tests, all passing in the runs above:
-
-- Response budget: a batch of four `data/get`s over a loaded state of about a
-  third of the budget keeps two results, answers the other two with `-32000`
-  and `max_response_bytes`, keeps the trailing reset's `{}`, and its body stays
-  within the budget.
-- Batch order: a batch `[data/add (gated download), data/get]` with a
-  `data/reset` from another request sent while the download is held reports
-  the loaded state from its `data/get`, and the reset applies last.
-- Cancellation: aborting the data plane's stop signal ends a stalled download
-  (its fetcher's signal is aborted) and answers the queued reset as
-  `cancelled` without running it; a call made after the stop does not run; a
-  caller whose request signal aborts gets `cancelled` and the state is
-  unchanged. Over loopback HTTP, `close()` of a served state returned while a
-  download that never answers was in progress, and that download's signal was
-  aborted.
-- File closes: with an injected close failure, `data/add` of a `file://` uri
-  answered `-32000` without echoing the uri. The descriptor stayed open, and
-  the next file load closed it before loading. While the close kept failing,
-  over loopback HTTP the next file load answered `-32000` ("still open") and
-  an inline `data` part still loaded. `close()` rejected with the unfinished
-  close, then resolved and closed the descriptor once the close succeeded.
-  Both tests fail on the previous head, which dropped the descriptor.
-- File hosts: `file://remote.example.test/...` and
-  `file:////remote.example.test/...` are refused with the network-share
-  message and no failure category; a `file://localhost/...` uri loads.
-- Loaded identity: `view_fields` setting `id` to `3`, `"3"` or `null` on user 2
-  is refused at `/rea_state/entities/7/view_fields/0/fields`; `"2"` loads.
-- List required fields: a folder without `title` makes `get_folders` a tool
-  error naming the incomplete entity.
-
-That each test fails without its fix is source-derived; the fixes were not
-reverted to show it.
-
-Not covered here: a Windows host (the UNC refusal ran on macOS, where
-`file:////host/share` converts to `//host/share`; the host check runs before
-any path conversion on every platform), a real `https://` download (tests
-inject the fetcher), the memory and time of a budgeted batch (not measured),
-agent token usage, a real AgentEnv framework run, a real-world capture, and
-write effects, which are a later increment.
-
-After refusing bodies too deep for the state's own nesting (a recorded body
-must nest at most the JSON depth limit minus 16 levels to enter the state):
-`npm run check:fast`, `npm run format:check`, `npx knip`, `npm run scan:todos`
-passed; `npm run jscpd`: 3.37% over 3373 files; `npx vitest run --project
-domain --project services`: 347 files, 5950 tests passed, 5 pre-existing
-skips; `npm run build:cached`, then `npm run test:focused --` the serve CLI,
-MCP and process boundaries, the export CLI boundary and the two serve adapter
-tests: 6 files, 48 tests passed.

docs/sqlite-databases.md

@@ -57,12 +57,7 @@ triggers or arbitrary SQL.
 Rows are optional. `table` selects one exact ordinary-table name. `columns`
 (CLI repeated `--column`) selects exact visible column names in the requested
 order; omission selects all visible columns, including generated columns.
-Unselected cells are not evaluated or projected. A selected virtual generated
-column whose expression needs a function REA's connection lacks (extensions and
-application functions are not loaded), or raises an SQL error for a sampled
-row, is refused as `capability_unavailable`. The error names the table and
-each failing selected column with SQLite's message, and recommends only columns
-whose sampled values were read; stored and other generated cells stay readable. Malformed column-name bytes
+Unselected cells are not evaluated or projected. Malformed column-name bytes
 cause a format refusal when all columns are requested. In inventory scope, an explicit valid subset can
 still be sampled without decoding unrelated malformed column names.
 Column selection requires a
@@ -107,29 +102,8 @@ bounds simultaneous input buffering and private snapshot/worker counts.
 
 The database and WAL together are limited to 256 MiB. SQLite values/records,
 SQL statements and the complete worker JSON reply each have a 16 MiB limit.
-The owned worker has a 256 MiB JavaScript heap limit and defaults to a 30,000 ms
-deadline. Select optional MCP `worker_timeout_ms`, or CLI
-`--worker-timeout-ms <milliseconds>`, to change the budget for that call. Values
-must be integer milliseconds from 1 to 2,147,483,647 (the runtime timer range).
-It covers worker startup, queries and reply writing, **not** DB/WAL snapshot
-acquisition, final reply reads, cleanup or delivery. Allow corresponding headroom
-in the MCP client's whole-call deadline; increasing only that deadline does not
-change the worker budget. No server restart is needed.
-
-The result's `worker_timeout_ms` reports the actual parent-supervised budget,
-including the default. Historical Evidence without this field has unknown
-execution settings, not an inferred default. Explicit input selection is also
-retained in Evidence parameters; omission stays omitted. Completed observations
-retained under cancellation or cleanup failure keep the same budget facts.
-Timeout errors name the selected milliseconds, exact CLI/MCP controls, and
-cleanup-before-retry requirements. Incomplete cleanup remains a blocker even
-when a larger budget is available.
-
-For example, `rea inspect-sqlite-database ./application.sqlite
---worker-timeout-ms 60000 --json` selects 60 seconds; equivalent MCP input is
-`{"path":"/artifacts/application.sqlite","worker_timeout_ms":60000}`.
-
-SQLite native allocations are separate from the JavaScript heap;
+The owned worker has a 256 MiB JavaScript heap limit and a 30-second inspection
+deadline. SQLite native allocations are separate from the JavaScript heap;
 overall native heap and total resident memory are not capped. Row limits do not
 override these byte and resource limits. Resource-limit failures do not return
 an incomplete schema as successful complete evidence.