[GH-ISSUE #406] Add end-to-end agent reconstruction readiness conformance #252

New issue

Closed

opened 2026-10-15 18:23:00 +00:00 by bsakaguchi · 0 comments

bsakaguchi commented 2026-10-15 18:23:00 +00:00

Owner

Copy link

Originally created by @morluto on GitHub (Jul 22, 2026).
Original GitHub issue: https://github.com/morluto/rea/issues/406

Problem

REA has individual capabilities for artifact classification, provider analysis, Evidence v2, process/browser/Electron capture, differential comparison, residual unknowns, and reconstruction verification. Individual feature tests do not prove that an agent can traverse the complete workflow without discovering hidden limits, incompatible providers, stale servers, missing authority, broken host runtimes, or false equivalence only after invocation.

Several previously separate failures illustrate the integration risk:

• a tool declaration can omit an effective numeric limit even when runtime validation knows it;
• an artifact can be accepted for inventory but routed to an analysis provider that cannot interpret its format;
• a newly installed CLI can coexist with a stale connected MCP server/catalog;
• a gated operation can require startup policy even when a narrow session grant would be sufficient;
• host runtime/linker failure can be presented as an analysis failure;
• a structured operation failure can be mistaken for process success;
• one integrity contradiction can either abort all unaffected comparison or be ignored unsafely;
• concurrent runtime schedules can be compared with unsafe total-order or broad-sorting semantics;
• green component tests can coexist with unowned reconstruction surfaces.

These are not adequately covered by testing each tool in isolation. REA needs a product-agnostic, public-contract conformance journey that proves the catalog, schemas, permissions, providers, evidence, comparison, and closure layers compose.

Outcome

Add an end-to-end agent reconstruction readiness suite and a machine-readable report. The suite should run representative native, generated JavaScript CLI/TUI, and Electron fixtures through the supported public CLI and MCP contracts.

The result should answer:

1. Could an agent discover the correct workflow before making an invalid call?
2. Were exact limits, authority requirements, side effects, and unavailable capabilities visible?
3. Did setup/preflight distinguish server drift, provider absence, target incompatibility, and broken host dependencies?
4. Did every failure propagate consistently through structured results and process status?
5. Did capture preserve complete, bounded, attributable Evidence?
6. Did comparison handle concurrency, contradictions, truncation, and missing authority without false equivalence?
7. Did reconstruction verification identify every remaining unowned or unverified obligation?

Conformance journey

1. Discover and classify

• Start MCP target-free.
• Inventory the artifact without launching an incompatible provider.
• Classify format, runtime family, packaging, architecture, and candidate workflow.
• Query capability-aware discovery and select a compatible provider family.
• Confirm exact schema limits and effective host/provider/policy constraints are visible before invocation.

2. Diagnose environment and version state

• Detect a deliberately broken runtime dependency separately from target-analysis failure.
• Detect installed CLI, connected MCP server, catalog/skill, and provider version skew.
• Return an actionable restart/setup path without claiming the requested analysis ran.
• Re-run after correction and prove discovery state/revision changes.

3. Acquire bounded authority

• Begin with process/evidence/workspace authority absent.
• Report the exact missing scope.
• Where elicitation is supported, grant only the required operation/session scope and resume.
• Where it is unsupported, return exact narrow configuration and restart requirements.
• Prove that scope expansion re-prompts and that denial/cancellation launches nothing.

4. Perform static analysis

• Route native artifacts to a compatible native provider.
• Route generated JavaScript to application-graph and semantic workflows rather than Hopper/Ghidra procedure analysis.
• Preserve static observations, derived relations, ambiguities, unsupported syntax, truncation, and residual unknowns distinctly.

5. Run reactive dynamic scenarios

• Wait for terminal/process/filesystem/HTTP/WebSocket predicates rather than sleeping.
• Send bounded input, resize, signal, answer controlled peers, and checkpoint.
• Capture root and descendant lifecycle through settlement and teardown.
• For Electron, correlate main, preload, renderer, utility, IPC, shell, deep-link, and error evidence.
• Cancel one run and prove owned cleanup plus retained diagnostic Evidence.

6. Compare authority and candidate

• Run repeated authority and candidate scenarios from reset environments.
• Validate exact event fields before schedule canonicalization.
• Accept declared concurrent schedules through partial-order/finite-trace semantics.
• Localize a deliberate primary divergence and distinguish downstream effects.
• Treat truncation, unavailable authority, and instability as unknown rather than pass.

7. Preserve contradictions

• Introduce one declared-versus-observed artifact integrity mismatch.
• Require explicit record-and-continue policy.
• Preserve both hashes, mark affected evidence untrusted, and continue unaffected comparisons.
• Prevent any equivalence claim over the contradicted entry.

8. Verify reconstruction closure

• Import observed boundaries into a reconstruction obligation workspace/ledger.
• Bind owners, parsers/types, positive and negative fixtures, and runtime verifiers.
• Keep the result partial while one packaged/process/persistence/Electron obligation is missing despite green component tests.
• Close only the obligation proven by each new verifier.
• Fail a candidate that delegates back to the authority.

9. Export and replay

• Export deterministic Evidence bundles, comparison specification, scenario, obligation ledger, and conformance report.
• Replay from a clean checkout/isolated environment using public contracts.
• Detect tampering, stale digests, widened normalization, missing dimensions, and version incompatibility.

Fixtures

Use synthetic, redistributable fixtures with no product-specific identifiers or external production services:

• a small native executable with stable symbols plus a deliberate version change;
• a generated/minified JavaScript CLI with prompts, alternate-screen TUI, configuration precedence, child process, filesystem persistence, loopback HTTP/WebSocket behavior, and signal teardown;
• an Electron application with main/preload/renderer/utility roles, bidirectional IPC, multiple windows, renderer restart, blocked external shell effect, and deterministic deep link;
• an intentionally incomplete reconstruction whose component tests pass;
• a broken-runtime fixture or controlled dependency probe that does not modify the user's global installation.

Every fixture should include deliberate faults so the suite proves diagnostic quality, not just happy-path execution.

Machine-readable report

Emit a versioned report containing:

• REA CLI/server/catalog/provider versions and digests;
• negotiated MCP client capabilities;
• effective capability records and exact limits;
• fixture/artifact/environment identities;
• selected and rejected workflow candidates with reason codes;
• grants/approvals by opaque ID and scope, excluding secrets;
• Evidence bundle IDs and completeness/authority classifications;
• comparison verdicts and minimal divergence references;
• contradiction and residual-unknown records;
• reconstruction obligations by status;
• cleanup, cancellation, and replay results;
• per-stage pass, fail, unknown, unsupported, truncated, or skipped status.

An aggregate pass is allowed only when every required stage passes. Unsupported, skipped, truncated, and unknown must never collapse into success.

CLI and MCP parity

• Exercise both surfaces from the same fixture definitions.
• Structured outcomes, evidence identities, limits, and error classifications must agree.
• Expected operation failure returns nonzero CLI status while MCP returns a typed non-success result.
• Long-running stages expose meaningful progress and cancellation where negotiated.
• Large reports and artifacts are available as resources rather than oversized tool responses.

Acceptance criteria

• A documented command runs the complete synthetic reconstruction journey from a clean checkout.
• A corresponding MCP-driven evaluation reaches the same semantic results without private/internal APIs.
• Invalid provider routing is prevented before expensive invocation.
• Exact effective limits are present in discovery/schema and repeated in validation errors.
• Broken host runtime and stale connected server/catalog cases have distinct actionable diagnoses.
• Missing authority supports narrow elicitation or a precise non-elicitation fallback.
• Reactive CLI/TUI and Electron scenarios require no external Expect/PTY orchestration framework.
• Concurrent valid schedules compare equivalent only under explicit partial-order/finite-trace rules.
• A deliberate divergence is localized; a deliberate contradiction remains visible and blocks affected equivalence.
• The incomplete reconstruction remains partial until every named obligation has comparable Evidence and a passing verifier.
• Cancellation cleans only owned resources and preserves diagnostic Evidence.
• CLI/MCP failures cannot be interpreted as success by ordinary automation.
• Exported conformance artifacts replay deterministically and detect tampering or stale inputs.
• CI publishes a compact summary and retains full reports as artifacts/resources.
• Documentation maps every failing stage to the responsible capability issue and next action.

Evaluation metrics

Track at least:

• first valid workflow/tool selection rate;
• malformed or over-limit call rate;
• incompatible-provider invocation rate;
• number of failed calls required to discover prerequisites;
• recovery rate after typed setup/permission errors;
• authority-to-candidate divergence localization precision;
• false-equivalence rate under truncation/concurrency/contradiction;
• unowned-obligation detection rate;
• cleanup leaks and nondeterministic replay rate.

Relationships

• Agent-first platform roadmap: #32
• Evidence/process fidelity epic: #48
• Investigation and reconstruction workflows: #18 and #37
• Reactive scenarios: #330
• Partial-order comparison: #403
• JavaScript runtime semantics: #404
• Reconstruction closure: #405
• Electron lifecycle capture: #375
• Scoped grants: #96
• Capability-aware discovery: #101
• Integrity continuation, exit status, stale-server detection, runtime diagnosis, and schema-limit work: #112, #113, #115, #262, and #261

Non-goals

• Declaring global behavioral equivalence from a finite suite.
• Adding product-specific fixtures, credentials, endpoints, or identifiers.
• Replacing focused unit/provider conformance tests.
• Requiring unavailable private server behavior to be reconstructed.
• Automatically granting authority or weakening startup policy.

Originally created by @morluto on GitHub (Jul 22, 2026). Original GitHub issue: https://github.com/morluto/rea/issues/406 ## Problem REA has individual capabilities for artifact classification, provider analysis, Evidence v2, process/browser/Electron capture, differential comparison, residual unknowns, and reconstruction verification. Individual feature tests do not prove that an agent can traverse the complete workflow without discovering hidden limits, incompatible providers, stale servers, missing authority, broken host runtimes, or false equivalence only after invocation. Several previously separate failures illustrate the integration risk: - a tool declaration can omit an effective numeric limit even when runtime validation knows it; - an artifact can be accepted for inventory but routed to an analysis provider that cannot interpret its format; - a newly installed CLI can coexist with a stale connected MCP server/catalog; - a gated operation can require startup policy even when a narrow session grant would be sufficient; - host runtime/linker failure can be presented as an analysis failure; - a structured operation failure can be mistaken for process success; - one integrity contradiction can either abort all unaffected comparison or be ignored unsafely; - concurrent runtime schedules can be compared with unsafe total-order or broad-sorting semantics; - green component tests can coexist with unowned reconstruction surfaces. These are not adequately covered by testing each tool in isolation. REA needs a product-agnostic, public-contract conformance journey that proves the catalog, schemas, permissions, providers, evidence, comparison, and closure layers compose. ## Outcome Add an end-to-end agent reconstruction readiness suite and a machine-readable report. The suite should run representative native, generated JavaScript CLI/TUI, and Electron fixtures through the supported public CLI and MCP contracts. The result should answer: 1. Could an agent discover the correct workflow before making an invalid call? 2. Were exact limits, authority requirements, side effects, and unavailable capabilities visible? 3. Did setup/preflight distinguish server drift, provider absence, target incompatibility, and broken host dependencies? 4. Did every failure propagate consistently through structured results and process status? 5. Did capture preserve complete, bounded, attributable Evidence? 6. Did comparison handle concurrency, contradictions, truncation, and missing authority without false equivalence? 7. Did reconstruction verification identify every remaining unowned or unverified obligation? ## Conformance journey ### 1. Discover and classify - Start MCP target-free. - Inventory the artifact without launching an incompatible provider. - Classify format, runtime family, packaging, architecture, and candidate workflow. - Query capability-aware discovery and select a compatible provider family. - Confirm exact schema limits and effective host/provider/policy constraints are visible before invocation. ### 2. Diagnose environment and version state - Detect a deliberately broken runtime dependency separately from target-analysis failure. - Detect installed CLI, connected MCP server, catalog/skill, and provider version skew. - Return an actionable restart/setup path without claiming the requested analysis ran. - Re-run after correction and prove discovery state/revision changes. ### 3. Acquire bounded authority - Begin with process/evidence/workspace authority absent. - Report the exact missing scope. - Where elicitation is supported, grant only the required operation/session scope and resume. - Where it is unsupported, return exact narrow configuration and restart requirements. - Prove that scope expansion re-prompts and that denial/cancellation launches nothing. ### 4. Perform static analysis - Route native artifacts to a compatible native provider. - Route generated JavaScript to application-graph and semantic workflows rather than Hopper/Ghidra procedure analysis. - Preserve static observations, derived relations, ambiguities, unsupported syntax, truncation, and residual unknowns distinctly. ### 5. Run reactive dynamic scenarios - Wait for terminal/process/filesystem/HTTP/WebSocket predicates rather than sleeping. - Send bounded input, resize, signal, answer controlled peers, and checkpoint. - Capture root and descendant lifecycle through settlement and teardown. - For Electron, correlate main, preload, renderer, utility, IPC, shell, deep-link, and error evidence. - Cancel one run and prove owned cleanup plus retained diagnostic Evidence. ### 6. Compare authority and candidate - Run repeated authority and candidate scenarios from reset environments. - Validate exact event fields before schedule canonicalization. - Accept declared concurrent schedules through partial-order/finite-trace semantics. - Localize a deliberate primary divergence and distinguish downstream effects. - Treat truncation, unavailable authority, and instability as unknown rather than pass. ### 7. Preserve contradictions - Introduce one declared-versus-observed artifact integrity mismatch. - Require explicit record-and-continue policy. - Preserve both hashes, mark affected evidence untrusted, and continue unaffected comparisons. - Prevent any equivalence claim over the contradicted entry. ### 8. Verify reconstruction closure - Import observed boundaries into a reconstruction obligation workspace/ledger. - Bind owners, parsers/types, positive and negative fixtures, and runtime verifiers. - Keep the result partial while one packaged/process/persistence/Electron obligation is missing despite green component tests. - Close only the obligation proven by each new verifier. - Fail a candidate that delegates back to the authority. ### 9. Export and replay - Export deterministic Evidence bundles, comparison specification, scenario, obligation ledger, and conformance report. - Replay from a clean checkout/isolated environment using public contracts. - Detect tampering, stale digests, widened normalization, missing dimensions, and version incompatibility. ## Fixtures Use synthetic, redistributable fixtures with no product-specific identifiers or external production services: - a small native executable with stable symbols plus a deliberate version change; - a generated/minified JavaScript CLI with prompts, alternate-screen TUI, configuration precedence, child process, filesystem persistence, loopback HTTP/WebSocket behavior, and signal teardown; - an Electron application with main/preload/renderer/utility roles, bidirectional IPC, multiple windows, renderer restart, blocked external shell effect, and deterministic deep link; - an intentionally incomplete reconstruction whose component tests pass; - a broken-runtime fixture or controlled dependency probe that does not modify the user's global installation. Every fixture should include deliberate faults so the suite proves diagnostic quality, not just happy-path execution. ## Machine-readable report Emit a versioned report containing: - REA CLI/server/catalog/provider versions and digests; - negotiated MCP client capabilities; - effective capability records and exact limits; - fixture/artifact/environment identities; - selected and rejected workflow candidates with reason codes; - grants/approvals by opaque ID and scope, excluding secrets; - Evidence bundle IDs and completeness/authority classifications; - comparison verdicts and minimal divergence references; - contradiction and residual-unknown records; - reconstruction obligations by status; - cleanup, cancellation, and replay results; - per-stage `pass`, `fail`, `unknown`, `unsupported`, `truncated`, or `skipped` status. An aggregate pass is allowed only when every required stage passes. Unsupported, skipped, truncated, and unknown must never collapse into success. ## CLI and MCP parity - Exercise both surfaces from the same fixture definitions. - Structured outcomes, evidence identities, limits, and error classifications must agree. - Expected operation failure returns nonzero CLI status while MCP returns a typed non-success result. - Long-running stages expose meaningful progress and cancellation where negotiated. - Large reports and artifacts are available as resources rather than oversized tool responses. ## Acceptance criteria - [ ] A documented command runs the complete synthetic reconstruction journey from a clean checkout. - [ ] A corresponding MCP-driven evaluation reaches the same semantic results without private/internal APIs. - [ ] Invalid provider routing is prevented before expensive invocation. - [ ] Exact effective limits are present in discovery/schema and repeated in validation errors. - [ ] Broken host runtime and stale connected server/catalog cases have distinct actionable diagnoses. - [ ] Missing authority supports narrow elicitation or a precise non-elicitation fallback. - [ ] Reactive CLI/TUI and Electron scenarios require no external Expect/PTY orchestration framework. - [ ] Concurrent valid schedules compare equivalent only under explicit partial-order/finite-trace rules. - [ ] A deliberate divergence is localized; a deliberate contradiction remains visible and blocks affected equivalence. - [ ] The incomplete reconstruction remains partial until every named obligation has comparable Evidence and a passing verifier. - [ ] Cancellation cleans only owned resources and preserves diagnostic Evidence. - [ ] CLI/MCP failures cannot be interpreted as success by ordinary automation. - [ ] Exported conformance artifacts replay deterministically and detect tampering or stale inputs. - [ ] CI publishes a compact summary and retains full reports as artifacts/resources. - [ ] Documentation maps every failing stage to the responsible capability issue and next action. ## Evaluation metrics Track at least: - first valid workflow/tool selection rate; - malformed or over-limit call rate; - incompatible-provider invocation rate; - number of failed calls required to discover prerequisites; - recovery rate after typed setup/permission errors; - authority-to-candidate divergence localization precision; - false-equivalence rate under truncation/concurrency/contradiction; - unowned-obligation detection rate; - cleanup leaks and nondeterministic replay rate. ## Relationships - Agent-first platform roadmap: #32 - Evidence/process fidelity epic: #48 - Investigation and reconstruction workflows: #18 and #37 - Reactive scenarios: #330 - Partial-order comparison: #403 - JavaScript runtime semantics: #404 - Reconstruction closure: #405 - Electron lifecycle capture: #375 - Scoped grants: #96 - Capability-aware discovery: #101 - Integrity continuation, exit status, stale-server detection, runtime diagnosis, and schema-limit work: #112, #113, #115, #262, and #261 ## Non-goals - Declaring global behavioral equivalence from a finite suite. - Adding product-specific fixtures, credentials, endpoints, or identifiers. - Replacing focused unit/provider conformance tests. - Requiring unavailable private server behavior to be reconstructed. - Automatically granting authority or weakening startup policy.

bsakaguchi 2026-10-15 18:23:00 +00:00

• closed this issue
• added the
  P1: high
  enhancement
  labels

bsakaguchi referenced this issue 2026-10-15 18:28:29 +00:00

[GH-ISSUE #2383] [Tracker] Audit analysis and debugging coverage for the TIOBE top 100 languages (October 2026) #794

bsakaguchi referenced this issue 2026-10-16 21:12:21 +00:00

[PR #252] [MERGED] feat(electron): map static process and IPC boundaries #1902

bsakaguchi added

enhancement

and removed

enhancement

labels 2026-10-31 00:28:55 +00:00

Sign in to join this conversation.

No Branch/Tag specified

Branches Tags

main

codex/procedure-reference-stacked

release-please--branches--main--components--rea-agents

release-please--branches--main--components--rea-agents--release-notes

codex/kuna-independent-retry

codex/byte-search-overlay-coverage

codex/open-failure-target-receipt

codex/kuna-xref-evidence

codex/ghidra-ambiguous-procedure-recovery

codex/function-source-bundle

codex/trace-function-integration-prototype

codex/snapshot-source-closure

codex/recorded-evidence-array-pages

codex/evidence-recovery-redesign

codex/trace-feature-address-scope

codex/call-discovery-scope

codex/ghidra-literal-candidate-evidence

codex/decompile-directory-independent-retry

codex/retry-provenance-base

codex/value-flow-capability-experiment

codex/ghidra-containing-instruction

cursor/readme-discord-button-ef9f

dependabot/github_actions/actions/setup-node-7.1.0

dependabot/github_actions/actions/upload-artifact-7.0.2

dependabot/npm_and_yarn/npm-minor-and-patch-d8d97ce6df

codex/kuna-1989

fix/8559-native-ui-fixture-ownership

fix/8555-go-verifier-mcp-ownership

codex/provider-capability-recovery

fix/8642-rizin-target-stdin

codex/ghidra-memory-effect-scope

codex/ghidra-annotation-entry-selector

codex/ghidra-readonly-recovery

codex/ghidra-regex-verifier-recovery

codex/evidence-discovery-view-guidance

fix/8545-bulk-append-overflow

fix/8428-navigation-refusal-alternatives

codex/address-context-recovery

codex/matching-member-limitations

codex/unknown-scope-contract

codex/evidence-view-guidance

feat/8373-native-trace-views

codex/ghidra-snapshot-verifier-binding

codex/elf-export-visibility

codex/evidence-view-recovery

codex/native-reference-cli-help

codex/provider-candidate-observation-scope

codex/kuna-session-verification

codex/ghidra-switch-lifetime-guidance

codex/pseudocode-paging-discovery

codex/clarify-evidence-view-support

codex/kuna-xrefs-selector-recovery

codex/context-capacity-recovery

codex/evidence-closure-large-links

codex/same-function-evidence-identity

codex/ghidra-verifier-inspected-jdk

codex/audit-guided-workflows

codex/crash-prompt-retained-dossiers

codex/analysis-view-error-recovery

codex/kuna-verifier-target-selection

codex/ghidra-selected-project-call-coverage

codex/docs-native-analysis-scope

codex/ghidra-java-socket-boundary

codex/ghidra-retained-snapshot-verifier

codex/ghidra-search-inventory-facts

fix/8284-zero-argument-parameter-bindings

fix/8198-ui-action-handler-offset

fix/8257-elf-entry-label-identity

fix/8304-deferred-output-schema-projection

fix/8277-call-path-computed-target-uncertainty

fix/pr-8089-conflicts

fix/ci-static-duplicate-export

dependabot/npm_and_yarn/lint-staged-17.6.0

dependabot/github_actions/actions/download-artifact-8.0.2

dependabot/npm_and_yarn/write-file-atomic-8.0.0

dependabot/npm_and_yarn/canonicalize-5.1.0

dependabot/github_actions/actions/cache/restore-6.1.0

dependabot/npm_and_yarn/toon-format/toon-4.4.0

dependabot/github_actions/actions/deploy-pages-5.0.1

codex/review-fixes-pr-2403

codex/review-fixes-pr-2400

codex/process-terminal-width

codex/test-brittleness-cleanup

verify/7167-browser-connect-macos

fix/7167-browser-connect

feat/native-matching-allowance-setting

feat/browser-scenario-dry-run

test/managed-caller-parameters-20261024

codex/parser-fortythird-boundaries

fix/6926-pinvoke-platform-decorations-20261023

fix/6889-har-body-encoding-20261023

fix/6888-sqlite-schema-budget-20261023

fix/dependency-security-gates-6708

cursor/evidence-overwrite-rebase-b4ac

feat/4057-verify-native-exports

fix/windows-acl-observer-overhead-20261022

cursor/erlang-beam-restack-4476

cursor/pe-certificate-review-bf32

fix/6116-javascript-application-fs-errors

fix/6061-unmapped-runtime-script-unknown

feat/browser-scenario-summary

fix/pe-certificates

codex/verify-3407

cursor/rebase-5699

cursor/rebase-5352

cursor/rebase-5600

cursor/fix-cli-schema-omission-10a8

codex/audit-hopper-shutdown-reasons-20261021

fix/demangle-swift-omitted-record

fix/nib-boolean-value-types

cursor/cancellation-partial-observation-a5ac

fix/ib-object-limit-reasons

fix/electron-fuse-limit-advice

fix/kuna-doctor-dangling-cache

fix/fixed-budget-refusal-advice

fix/js-ipc-listener-dedup

fix/js-return-member-provenance

fix/dmg-integrity-retry-advice

fix/ida-doctor-readiness

fix/kuna-version-probe-output-drain

fix/legacy-swift-runtime-name-matching

fix/dylib-lazy-load-commands

fix/browser-scenario-startup-cancel

fix/swift-nested-punycode-classification

fix/compare-unselected-scopes

fix/objc-method-budget-coverage

fix/dmg-mounted-root-observations

audit/ci-tests-20261019-round2

release/6.7.0

fix/wabt-cleanup-retry-resolution

fix/electron-fuse-elf-pe-architecture

fix/native-plist-descriptor-ownership

fix/kuna-caller-cleanup-ownership

experiment/atomic-codemode-20261016

review/first-contributor-3776

fix/call-resolution-full-read-cycles

fix/member-mutation-selection-repeat

experiment/atomic-re-tools-20261015

perf/member-mutation-lazy-origins

perf/static-network-mutation-index

fix/hopper-startup-lifecycle

audit/3050-windows-proof-20261015

feat/windows-window-capture-2183

audit/3049-windows-proof-20261015

audit/3735-macos-fixtures-20261015

fix/batch-decompile-null-pseudocode

fix/kuna-inventory-honors-jobs

experiment/browser-codemode-tool-design-20261015

fix/hopper-clean-runtime-argv

codex/review-2049-27f1b367

review-fixes/pr-2787-routing

fix/3360-scoped-this-emitters

fix/3367-replaced-global-effects

fix/3838-compact-any-value-items

test/hopper-download-probe-20261015

codex/windows-runtime-creation-red-green-20261015

codex/windows-readonly-root-red-green-20261015

codex/windows-root-share-red-green-20261015

codex/exp-1685-win-mcp-startup

codex/bug-sweep-20261015

investigate/2190-windows-package-phases

investigate/3543-macos-cli-deadline

perf/3281-reverse-tools-feedback-quality

fix/3406-hopper-doctor-fixture

fix/3341-wrapper-require-test-context

fix/3301-owned-uninstall-fixtures

fix/3164-compiler-input-ownership

fix/pcap-cleanup-stdout-newline-20261014

perf/interface-builder-summary

codex/review-fixes-pr-1977

fix/ghidra-effective-jvm-platform

fix/docs-turkish-rust-link-20261013

fix/main-maintenance-ci-20261010

fix/recover-binary-session-process-effects

codex/review-fixes-pr-2457

codex/ci-required-cancellation-gate

fix/main-format-baseline-20261013

fix/setup-preserve-entry-fields

cursor/restore-main-checks-1ffc

fix/ghidra-bridge-hashmap-import

codex/shared-ci-jadx-json-default-20261013

codex/shared-ci-ghidra-test-groups-20261013

codex/shared-ci-java-fixture-format-20261013

codex/fix-intrinsic-invocation-boundaries

test/release-preflight-reusable-jobs

test/js-parameter-provenance-expectation

fix/linux-hopper-verification-current

test/2419-ghidra-elf-probe-size

followup/pr-1544-native-ida

codex/fold-pr-2230-contribution

docs/readme-responsible-use

fix/issue-2064

fix/issue-2050

fix/issue-2053

fix/issue-1968

fix/issue-1945

experiment/codemode-bridge-20261011

fix/tool-effects-negative-wording-1904-20261012

fix/1842-electron-interop-provenance

feat/recover-javascript-multi-input

refactor/website-i18n-prep

fix/nativeaot-pe-virtual-extent

fix/browser-verifier-ci-hang

fix/pe-resources-input-selection

docs/beginner-friendly-guides

docs/beginner-setup-guide

fix/javascript-analysis-worker-1563

fix/1649-ghidra-duplicate-names

fix/javascript-export-keys-integration-1369

test/maintenance-boundary-contracts-20261011

review/javascript-export-keys-1369

review/process-live-progress-1483

test/javascript-1495-growth-ratio

fix/ci-escape-timing

docs/normalized-terminal-geometry-1450

release/6.3.0

archive/release-6.3.0-pr1381

release/6.2.0

fix/electron-preload-dynamic-override

fix/javascript-self-referential-bundler-edges

release/6.1.0

cursor/grok-client-cherry-pick-0b56

feat/signature-posture

feat/dyld-shared-cache

feat/artifact-integrity-policy

feat/pkg-inventory

release/6.0.0

chore/sync-release-5.0.0

release/5.0.0

cursor/cloud-agent-node-787e

fix/javascript-xhr-open-endpoints

review/pr-711-realpath-fallback-wording

cleanup/replay-confinement

codex/test-suite-performance

codex/issue-foundations

codex/address-open-issues-2026-07-20

agent/javascript-vite-rollup-esbuild-adapters

agent/process-cleanup

agent/triage-integration

agent/unknown-commands-registry

feat/mcp-identity-metadata

morlvps/issue_cleanup

codex/installer-redesign

morl/roadmap-investigation-core

morl/roadmap-investigation-docs

release-please--branches--main--components--rea

rea-agents-6.8.0

rea-agents-6.7.0

rea-agents-6.6.0

experiment/atomic-codemode-wait-runtime-20261016

rea-agents-6.5.0

rea-agents-6.4.0

rea-agents-6.3.0

rea-agents-6.2.0

rea-agents-6.1.0

rea-agents-6.0.0

rea-agents-5.0.0

rea-agents-4.1.0

rea-agents-4.0.1

rea-agents-4.0.0

rea-agents-3.2.1

rea-agents-3.2.0

rea-agents-3.1.0

rea-agents-3.0.0

rea-agents-2.7.0

rea-agents-2.6.0

rea-agents-2.5.1

rea-agents-2.5.0

rea-agents-2.4.0

rea-agents-2.3.0

rea-agents-2.2.0

rea-agents-2.1.0

rea-agents-2.0.0

rea-agents-1.7.0

rea-agents-1.6.0

rea-agents-1.5.0

rea-agents-1.4.0

rea-agents-1.3.0

rea-agents-1.2.0

rea-agents-1.1.0

rea-agents-1.0.0

rea-agents-0.5.0

rea-agents-0.4.0

rea-agents-0.3.0

rea-0.2.1

rea-0.2.0

Labels

Clear labels   

area: bridge

  

area: bridge

  

area: build

  

area: build

  

area: build

  

area: cli

  

area: domain

  

area: evidence

  

area: mcp

  

area: native

  

area: providers

  

area: runtime

  

area: server

  

area: setup

  

area: tests

  

bug

  

design

  

documentation

  

enhancement

  

enhancement

  

enhancement

  

experiment

  

help wanted

  

i18n

  

invalid

  

P0: critical

  

P1: high

  

P2: medium

  

P2: medium

  

P2: medium

  

P3: low

  

performance

  

provider-request

  

pull-request

Mirrored from GitHub Pull Request

  

question

  

roadmap

  

triage

No labels

area: bridge

area: bridge

area: build

area: build

area: build

area: cli

area: domain

area: evidence

area: mcp

area: native

area: providers

area: runtime

area: server

area: setup

area: tests

bug

design

documentation

enhancement

enhancement

enhancement

experiment

help wanted

i18n

invalid

P0: critical

P1: high

P2: medium

P2: medium

P2: medium

P3: low

performance

provider-request

pull-request

question

roadmap

triage

Milestone

Clear milestone

No items

No milestone

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

1 participant

Notifications

Subscribe

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

morluto/rea#252

No description provided.