[PR #4391] [CLOSED] fix(browser): bound observe_web_session windows to the Node.js timer limit #6211

New issue

Closed

opened 2026-10-31 01:12:43 +00:00 by bsakaguchi · 0 comments

bsakaguchi commented 2026-10-31 01:12:43 +00:00

Owner

Copy link

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/4391
Author: @Adolanium
Created: 10/16/2026
Status: ❌ Closed

Base: main ← Head: fix/observe-window-timer-bound

---

📝 Commits (2)

• 63d0cc6 fix(browser): bound observe_web_session windows to the Node.js timer limit
• 809bca8 Merge remote-tracking branch 'upstream/main' into fix/observe-window-timer-bound

📊 Changes

3 files changed (+32 additions, -2 deletions)

View changed files

📝 docs/browser-observation.md (+1 -1)
➕ src/domain/browserSession.test.ts (+30 -0)
📝 src/domain/browserSession.ts (+1 -1)

📄 Description

Summary

Fixes #4392.

observe_web_session accepted any positive observation_ms. Values above 2,147,483,647 overflow Node's timer, so the window ended after about 1 ms but the result still reported end_reason: "window_elapsed" with the large requested_ms. The input schema now rejects those values, as observe_web_execution already does.

Problem and expected behavior

observeWebSessionInputSchema in src/domain/browserSession.ts declared observation_ms: z.number().int().min(1).default(10_000) with no maximum. waitForWindow in src/browser/CdpObservationSession.ts passes the value straight to setTimeout. Node clamps a delay above 2^31-1 to 1 ms and prints TimeoutOverflowWarning. The result then claims a window of the requested length elapsed when it did not.

observeWebExecutionInputSchema in src/domain/webExecution.ts already uses .max(2_147_483_647) for the same field.

Change and scope

• observeWebSessionInputSchema adds .max(2_147_483_647) to observation_ms. The schema is the owning input boundary: the MCP tool contract in src/contracts/browserToolContracts.ts uses it as inputSchema, and the CLI command in src/cli/browserCommands.ts parses its input with it, so both reject the value with an out_of_range issue that carries maximum.
• docs/browser-observation.md states the accepted range.

Not included: other observation tools (inspect_web_page, discover_webmcp_tools, Electron and JavaScript runtime observation) wait through delayWithCancellation, which splits long delays into timer-sized chunks, so they are not affected and keep accepting larger values. #3392 (scenario timers overflow) is related but separate and is not changed here.

Follow the contribution scope.
Unresolved scope, authority, side effects, or required verification block
integration. Link the required maintainer scope decision for new providers or
capabilities involving target execution, injection, mutation, or protection
recovery; ordinary fixes within existing boundaries may state "not applicable".
Draft PRs may leave the scope decision pending and the readiness and merge checklists
unchecked. Maintainers can help resolve open questions.

Scope decision: not applicable. This is an input-bound fix for an existing tool.

Contract and boundary impact

• Semantic owner and earliest changed stage: observeWebSessionInputSchema, request parsing.
• Contribution scope fit and linked maintainer decision: ordinary fix within existing boundaries; not applicable.
• CLI and MCP/tool-catalog contract: observation_ms now has maximum: 2147483647 in the advertised input schema. Requests above it fail validation instead of returning a false window_elapsed result.
• Provider, bridge, target-format, or platform compatibility: none.
• Evidence, artifact, provenance, or reconstruction contract: a returned window.requested_ms with end_reason: "window_elapsed" now matches a timer that actually ran for that long.
• Target selection, authority, upstream behavior, and cleanup details (if applicable): none.
• Generated metadata (docs/public/product-catalog.json), package, or installation impact (CI generates and validates ignored catalogs and skills/; edit authored instructions in .agents/skills/reverse-engineer-anything/ and never commit build outputs): the generated catalog will show the new maximum. No authored catalog source lists the bound.

Expected effects (check known effects; use documentation-only on its own).
Unchecked items do not establish absence; leave uncertainties visible.

• Read existing files or captured data.
• Launch or attach to a process.
• Inject instrumentation or run scripts/code.
• Change process memory, registers, files, or configuration.
• Contact network services.
• Recover protected code or work around protections.
• Documentation or usability only; no target interaction.
• Not sure yet; investigation or maintainer guidance needed.

Evidence and regression coverage

• Tests added or updated: new src/domain/browserSession.test.ts checks that 2,147,483,647 is accepted, that 2,147,483,648 fails with a too_big issue on observation_ms with maximum: 2147483647, and that the input JSON Schema from z.toJSONSchema has minimum: 1 and maximum: 2147483647.
• Base reproduction or other evidence: executed. With the upstream/main schema the new test fails because 2,147,483,648 is accepted. Separately, setTimeout(…, 2_147_483_648) on Node 24.14.1 printed TimeoutOverflowWarning: 2147483648 does not fit into a 32-bit signed integer. Timeout duration was set to 1. and fired after 7 ms. I did not run observe_web_session against a browser.
• User-visible CLI/MCP output (if applicable): rea observe-web-session <endpoint> <target> --observation-ms 2147483648 --json should now return invalid_request with the issue { "path": ["observation_ms"], "reason": "out_of_range", "maximum": 2147483647 }. This is source-derived; the CLI boundary tests need a built CLI, which I could not build on this Windows checkout.
• Remaining proof gaps: no live browser session and no CLI or MCP boundary run. The regression is at the schema.

For evidence-bearing changes:

• Observed, derived, and inferred claims remain distinguishable.
• Artifact identity, source provenance, and failed attempts remain preserved.
• Unsupported, incomplete, unavailable, or uncertain outcomes remain visible.

Validation performed

• npm run test:focused -- src/domain/browserSession.test.ts — 1 test passed.
• npx vitest run src/domain/browserSession.test.ts with the upstream/main schema — failed (expected true to be false on the rejection check).
• npx tsc --noEmit --pretty false — no errors.
• npx oxlint src/domain/browserSession.ts src/domain/browserSession.test.ts — 0 warnings, 0 errors.
• npx oxfmt --check on the three changed files — formatted.
• npm run build:cached — did not complete on Windows. It stopped because the packaged Windows native artifact is missing, so the CLI boundary tests were not run.

Compatibility, safety, and release

• Breaking changes or migration steps: requests with observation_ms above 2,147,483,647 (about 24.8 days) now fail validation. Those requests previously ended after about 1 ms while reporting the full window, so no working call is affected.
• Real Hopper/Ghidra, browser, or OS coverage: not run.
• Package or release metadata impact: none.
• Security, privacy, process, or containment review: none.

Author readiness

Human owner: @Adolanium

• I reviewed the final diff and relevant existing code, understand the change and its edge cases, and take responsibility for the complete PR, including AI-assisted work.
• I checked the evidence above, confirmed it supports the current change, and recorded meaningful validation gaps.
• I declare this PR ready for initial maintainer review.

Before merge

• This PR addresses a concrete problem or an agreed enhancement.
• Material scope and authority questions are resolved, and any required maintainer scope decision covers the final diff.
• The PR has one focused outcome and the title follows type(scope): outcome.
• Related issue is linked, or the reason for not linking one is stated above.
• Tests cover changed observable behavior and meaningful failure paths.
• Owning docs, contracts, and generated metadata are updated where needed.
• User-visible CLI/MCP changes include representative output.
• I checked the final diff for secrets, unrelated cleanup, and unsupported claims.

---

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/morluto/rea/pull/4391 **Author:** [@Adolanium](https://github.com/Adolanium) **Created:** 10/16/2026 **Status:** ❌ Closed **Base:** `main` ← **Head:** `fix/observe-window-timer-bound` --- ### 📝 Commits (2) - [`63d0cc6`](https://github.com/morluto/rea/commit/63d0cc63ab8dd1663a902b1a7a68658a775e3305) fix(browser): bound observe_web_session windows to the Node.js timer limit - [`809bca8`](https://github.com/morluto/rea/commit/809bca8f1ad9f53fa6c770d2c6fe01ca681cf245) Merge remote-tracking branch 'upstream/main' into fix/observe-window-timer-bound ### 📊 Changes **3 files changed** (+32 additions, -2 deletions) <details> <summary>View changed files</summary> 📝 `docs/browser-observation.md` (+1 -1) ➕ `src/domain/browserSession.test.ts` (+30 -0) 📝 `src/domain/browserSession.ts` (+1 -1) </details> ### 📄 Description ## Summary Fixes #4392. `observe_web_session` accepted any positive `observation_ms`. Values above 2,147,483,647 overflow Node's timer, so the window ended after about 1 ms but the result still reported `end_reason: "window_elapsed"` with the large `requested_ms`. The input schema now rejects those values, as `observe_web_execution` already does. ## Problem and expected behavior `observeWebSessionInputSchema` in `src/domain/browserSession.ts` declared `observation_ms: z.number().int().min(1).default(10_000)` with no maximum. `waitForWindow` in `src/browser/CdpObservationSession.ts` passes the value straight to `setTimeout`. Node clamps a delay above 2^31-1 to 1 ms and prints `TimeoutOverflowWarning`. The result then claims a window of the requested length elapsed when it did not. `observeWebExecutionInputSchema` in `src/domain/webExecution.ts` already uses `.max(2_147_483_647)` for the same field. ## Change and scope - `observeWebSessionInputSchema` adds `.max(2_147_483_647)` to `observation_ms`. The schema is the owning input boundary: the MCP tool contract in `src/contracts/browserToolContracts.ts` uses it as `inputSchema`, and the CLI command in `src/cli/browserCommands.ts` parses its input with it, so both reject the value with an `out_of_range` issue that carries `maximum`. - `docs/browser-observation.md` states the accepted range. Not included: other observation tools (`inspect_web_page`, `discover_webmcp_tools`, Electron and JavaScript runtime observation) wait through `delayWithCancellation`, which splits long delays into timer-sized chunks, so they are not affected and keep accepting larger values. #3392 (scenario timers overflow) is related but separate and is not changed here. Follow the [contribution scope](https://github.com/morluto/rea/blob/main/CONTRIBUTING.md#contribution-scope). Unresolved scope, authority, side effects, or required verification block integration. Link the required maintainer scope decision for new providers or capabilities involving target execution, injection, mutation, or protection recovery; ordinary fixes within existing boundaries may state "not applicable". Draft PRs may leave the scope decision pending and the readiness and merge checklists unchecked. Maintainers can help resolve open questions. Scope decision: not applicable. This is an input-bound fix for an existing tool. ## Contract and boundary impact - Semantic owner and earliest changed stage: `observeWebSessionInputSchema`, request parsing. - Contribution scope fit and linked maintainer decision: ordinary fix within existing boundaries; not applicable. - CLI and MCP/tool-catalog contract: `observation_ms` now has `maximum: 2147483647` in the advertised input schema. Requests above it fail validation instead of returning a false `window_elapsed` result. - Provider, bridge, target-format, or platform compatibility: none. - Evidence, artifact, provenance, or reconstruction contract: a returned `window.requested_ms` with `end_reason: "window_elapsed"` now matches a timer that actually ran for that long. - Target selection, authority, upstream behavior, and cleanup details (if applicable): none. - Generated metadata (`docs/public/product-catalog.json`), package, or installation impact (CI generates and validates ignored catalogs and `skills/`; edit authored instructions in `.agents/skills/reverse-engineer-anything/` and never commit build outputs): the generated catalog will show the new maximum. No authored catalog source lists the bound. Expected effects (check known effects; use documentation-only on its own). Unchecked items do not establish absence; leave uncertainties visible. - [ ] Read existing files or captured data. - [ ] Launch or attach to a process. - [ ] Inject instrumentation or run scripts/code. - [ ] Change process memory, registers, files, or configuration. - [ ] Contact network services. - [ ] Recover protected code or work around protections. - [ ] Documentation or usability only; no target interaction. - [ ] Not sure yet; investigation or maintainer guidance needed. ## Evidence and regression coverage - Tests added or updated: new `src/domain/browserSession.test.ts` checks that 2,147,483,647 is accepted, that 2,147,483,648 fails with a `too_big` issue on `observation_ms` with `maximum: 2147483647`, and that the input JSON Schema from `z.toJSONSchema` has `minimum: 1` and `maximum: 2147483647`. - Base reproduction or other evidence: executed. With the `upstream/main` schema the new test fails because 2,147,483,648 is accepted. Separately, `setTimeout(…, 2_147_483_648)` on Node 24.14.1 printed `TimeoutOverflowWarning: 2147483648 does not fit into a 32-bit signed integer. Timeout duration was set to 1.` and fired after 7 ms. I did not run `observe_web_session` against a browser. - User-visible CLI/MCP output (if applicable): `rea observe-web-session <endpoint> <target> --observation-ms 2147483648 --json` should now return `invalid_request` with the issue `{ "path": ["observation_ms"], "reason": "out_of_range", "maximum": 2147483647 }`. This is source-derived; the CLI boundary tests need a built CLI, which I could not build on this Windows checkout. - Remaining proof gaps: no live browser session and no CLI or MCP boundary run. The regression is at the schema. For evidence-bearing changes: - [x] Observed, derived, and inferred claims remain distinguishable. - [x] Artifact identity, source provenance, and failed attempts remain preserved. - [x] Unsupported, incomplete, unavailable, or uncertain outcomes remain visible. ## Validation performed - `npm run test:focused -- src/domain/browserSession.test.ts` — 1 test passed. - `npx vitest run src/domain/browserSession.test.ts` with the `upstream/main` schema — failed (`expected true to be false` on the rejection check). - `npx tsc --noEmit --pretty false` — no errors. - `npx oxlint src/domain/browserSession.ts src/domain/browserSession.test.ts` — 0 warnings, 0 errors. - `npx oxfmt --check` on the three changed files — formatted. - `npm run build:cached` — did not complete on Windows. It stopped because the packaged Windows native artifact is missing, so the CLI boundary tests were not run. ## Compatibility, safety, and release - Breaking changes or migration steps: requests with `observation_ms` above 2,147,483,647 (about 24.8 days) now fail validation. Those requests previously ended after about 1 ms while reporting the full window, so no working call is affected. - Real Hopper/Ghidra, browser, or OS coverage: not run. - Package or release metadata impact: none. - Security, privacy, process, or containment review: none. ## Author readiness <!-- The human owner completes these declarations before requesting review. The PR author is the owner by default. A different owner must explicitly accept ownership on this PR. AI agents must leave these declarations to a human to dictate to them or there could be catastrophic consequences for many users of REA. Draft PRs may leave them unchecked. These declarations record initial readiness when opening the PR for review; later pushes do not require a new human sign-off. Keep the description and validation evidence current as the work changes. See CONTRIBUTING.md#pull-request-ownership-and-readiness. --> Human owner: @Adolanium - [x] I reviewed the final diff and relevant existing code, understand the change and its edge cases, and take responsibility for the complete PR, including AI-assisted work. - [x] I checked the evidence above, confirmed it supports the current change, and recorded meaningful validation gaps. - [x] I declare this PR ready for initial maintainer review. ## Before merge <!-- Draft PRs may leave pending items unchecked. Resolve material scope and authority questions before integration. --> - [ ] This PR addresses a concrete problem or an agreed enhancement. - [ ] Material scope and authority questions are resolved, and any required maintainer scope decision covers the final diff. - [ ] The PR has one focused outcome and the title follows `type(scope): outcome`. - [ ] Related issue is linked, or the reason for not linking one is stated above. - [ ] Tests cover changed observable behavior and meaningful failure paths. - [ ] Owning docs, contracts, and generated metadata are updated where needed. - [ ] User-visible CLI/MCP changes include representative output. - [ ] I checked the final diff for secrets, unrelated cleanup, and unsupported claims. --- _{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

bsakaguchi 2026-10-31 01:12:43 +00:00

• closed this issue
• added the
  pull-request
  label

bsakaguchi referenced this issue 2026-11-01 21:10:54 +00:00

[GH-ISSUE #3795] [Tracker] Open documentation issues and pull requests (October 2026) #1468

bsakaguchi referenced this issue 2026-11-01 21:10:57 +00:00

[GH-ISSUE #3796] [Tracker] Open feature requests by area (October 2026) #1471

bsakaguchi referenced this issue 2026-11-01 21:11:00 +00:00

[GH-ISSUE #5653] [Tracker] New issue intake by area (October 2026) #3423

bsakaguchi referenced this issue 2026-11-03 13:39:44 +00:00

[PR #7179] [CLOSED] feat(postgres): add read-only postgresql database inspection (#6211) #7700

bsakaguchi referenced this issue 2026-11-03 13:39:55 +00:00

[PR #7223] docs(design): propose read-only PostgreSQL inspection (#6211) #7727

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#6211

No description provided.