[PR #5539] fix(gdb): keep inferior-tty verification for read-only queries #6954

New issue

Open

opened 2026-11-01 21:44:17 +00:00 by bsakaguchi · 0 comments

bsakaguchi commented 2026-11-01 21:44:17 +00:00

Owner

Copy link

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/5539
Author: @akushonkamen
Created: 10/20/2026
Status: 🔄 Open

Base: main ← Head: fix/5099-show-inferior-tty-verified

---

📝 Commits (4)

• bede9d6 fix(gdb): keep TTY verification across read-only inferior-tty inspection
• 6c67980 merge: resolve TTY-query exemption with origin/main
• 846529e test(gdb): classify show inferior-tty in the one-shot table and rename the TTY classification table
• 0da5d0b Merge remote-tracking branch 'origin/main' into fix/5099-show-inferior-tty-verified

📊 Changes

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

View changed files

📝 src/gdb/GdbSessionManager.ts (+9 -3)
📝 tests/boundary/providers/GdbSessionManagerCoverage.test.ts (+73 -0)

📄 Description

Summary

commandMayChangeInferiorOutput matched any command whose text merely mentioned the inferior TTY setting, so the read-only query show inferior-tty (and its MI form -inferior-tty-show) permanently revoked inferiorTtyVerified: an inspection mutated session state as a side effect, no in-session path ever restored the flag, and an inspect-then-close flow then failed the detach proof with capability_unavailable (#5099). This PR exempts exactly the read-only TTY query forms; every other command that mentions the setting keeps revoking the verified flag.

Fixes #5099

Problem and expected behavior

Smallest trigger: start a GDB session with a verified inferior TTY, send the console command show inferior-tty, then close the live session. Violated invariant: a read-only inspection must not invalidate the verified output sink. Before the fix, the close failed detach verification (the sink could no longer be proven live) instead of detaching cleanly.

Change and scope

commandMayChangeInferiorOutput (src/gdb/GdbSessionManager.ts) now returns false only for the exact, full-string read-only forms (show inferior-tty, help inferior-tty, MI -inferior-tty-show; the help form arrived independently on main and the merge keeps both semantics). Compound commands fall back to revocation by design: the exemption is an exact full-string match, so show inferior-t; set inferior-tty /tmp/other still revokes — abbreviation prefixes, ;-chained or multiline composites, and redirections all stay under the conservative fail-closed rules.

Two behavior notes:

• One-shot CLI: debug-with-gdb ... "show inferior-tty" changes from refused to runnable. This is user-visible but directional-correct: the query is read-only and cannot reconfigure the output sink.
• The MI form -inferior-tty-show is a defensive exemption. REA's own MI TTY calls do not route through this user-command gate, and the console interpreter may not accept MI text; the form is exempted so that, if it ever reaches the gate, it cannot revoke verification.

Intentionally not included: any restoration path that re-verifies the TTY after a genuinely mutating command — mutating commands keep revoking, and detach keeps re-reading the live TTY before -target-detach.

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.

Contract and boundary impact

• Semantic owner and earliest changed stage: the GDB session manager's output-mutation classifier (commandMayChangeInferiorOutput); consumers are the console-command gate that clears inferiorTtyVerified and the detach proof. No superseded paths removed; the fail-closed revocation policy is retained for every non-exact match.
• Contribution scope fit and linked maintainer decision: ordinary fix within the existing GDB boundary; not applicable.
• CLI and MCP/tool-catalog contract: one-shot debug-with-gdb ... "show inferior-tty" moves from refused to runnable (read-only query); no other catalog changes.
• Provider, bridge, target-format, or platform compatibility: GDB console and MI command classification only; no version-specific behavior added.
• Evidence, artifact, provenance, or reconstruction contract: not applicable.
• Target selection, authority, upstream behavior, and cleanup details (if applicable): none — the change does not alter target selection, detach authority, or cleanup; detach still re-verifies the live TTY.
• Generated metadata (docs/public/product-catalog.json), package, or installation impact: none.

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: tests/boundary/providers/GdbSessionManagerCoverage.test.ts — query-form and composite-command classification rows (classifies inferior TTY commands), a show inferior-tty row in the one-shot classification table (classifies one-shot GDB commands), and the inspect-then-close detach path (keeps the verified sink across the read-only show inferior-tty inspection, including an execute-path assertion for the MI form and recorded-command assertions that the query text is dispatched and -target-detach follows).
• Base reproduction or other evidence: the regression tests fail against the pre-fix classification (and against the current main source, which lacks the MI exemption) and pass with this branch.
• User-visible CLI/MCP output (if applicable): debug-with-gdb ... "show inferior-tty" now executes the query instead of refusing it.
• Remaining proof gaps: no test asserts that a real GDB console interpreter accepts the MI text -inferior-tty-show; the exemption there is defensive (see Change and scope).

For boundary fixes, identify the applicable boundary regressions
and lifecycle regressions
covered by the evidence above, and explain relevant gaps.

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

• npx vitest run tests/boundary/providers/GdbSessionManagerCoverage.test.ts — 195/195 passed on this branch.
• Same command with src/gdb/GdbSessionManager.ts temporarily reset to origin/main's version — 2 failed (the -inferior-tty-show classification row and the MI execute-path assertion), confirming red on the affected base.
• npx prettier --check src/gdb/GdbSessionManager.ts tests/boundary/providers/GdbSessionManagerCoverage.test.ts — clean.
• npx oxlint on both touched files — 0 errors (pre-existing warnings only).
• npx tsc --noEmit -p . — only pre-existing unrelated errors from missing optional fixtures dependencies (@bufbuild/protobuf, @msgpack/msgpack) in this environment; none in the touched files.

Compatibility, safety, and release

• Breaking changes or migration steps: none; the only observable change is that read-only TTY queries are no longer refused/revoking.
• Real Hopper/Ghidra, browser, or OS coverage: not applicable (GDB provider only).
• Package or release metadata impact: none.
• Security, privacy, process, or containment review: the exemption is exact full-string match only; abbreviations, composites, and redirections keep revoking the verified flag, so the fail-closed direction is preserved.

Author readiness

Human owner: @akushonkamen

• 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.

---

_{🔄 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/5539 **Author:** [@akushonkamen](https://github.com/akushonkamen) **Created:** 10/20/2026 **Status:** 🔄 Open **Base:** `main` ← **Head:** `fix/5099-show-inferior-tty-verified` --- ### 📝 Commits (4) - [`bede9d6`](https://github.com/morluto/rea/commit/bede9d6abb1294ff35176f8a153af0214d8ed367) fix(gdb): keep TTY verification across read-only inferior-tty inspection - [`6c67980`](https://github.com/morluto/rea/commit/6c679800cad1bc9415a89e3be05fafe658984db6) merge: resolve TTY-query exemption with origin/main - [`846529e`](https://github.com/morluto/rea/commit/846529e1e93bbfad503b34af13febb564e23e6fc) test(gdb): classify show inferior-tty in the one-shot table and rename the TTY classification table - [`0da5d0b`](https://github.com/morluto/rea/commit/0da5d0bd04f61ffca92aa37943e5213794ebe9a0) Merge remote-tracking branch 'origin/main' into fix/5099-show-inferior-tty-verified ### 📊 Changes **2 files changed** (+82 additions, -3 deletions) <details> <summary>View changed files</summary> 📝 `src/gdb/GdbSessionManager.ts` (+9 -3) 📝 `tests/boundary/providers/GdbSessionManagerCoverage.test.ts` (+73 -0) </details> ### 📄 Description ## Summary `commandMayChangeInferiorOutput` matched any command whose text merely mentioned the inferior TTY setting, so the read-only query `show inferior-tty` (and its MI form `-inferior-tty-show`) permanently revoked `inferiorTtyVerified`: an inspection mutated session state as a side effect, no in-session path ever restored the flag, and an inspect-then-close flow then failed the detach proof with capability_unavailable (#5099). This PR exempts exactly the read-only TTY query forms; every other command that mentions the setting keeps revoking the verified flag. Fixes #5099 ## Problem and expected behavior Smallest trigger: start a GDB session with a verified inferior TTY, send the console command `show inferior-tty`, then close the live session. Violated invariant: a read-only inspection must not invalidate the verified output sink. Before the fix, the close failed detach verification (the sink could no longer be proven live) instead of detaching cleanly. ## Change and scope `commandMayChangeInferiorOutput` (src/gdb/GdbSessionManager.ts) now returns `false` only for the exact, full-string read-only forms (`show inferior-tty`, `help inferior-tty`, MI `-inferior-tty-show`; the `help` form arrived independently on main and the merge keeps both semantics). Compound commands fall back to revocation by design: the exemption is an exact full-string match, so `show inferior-t; set inferior-tty /tmp/other` still revokes — abbreviation prefixes, `;`-chained or multiline composites, and redirections all stay under the conservative fail-closed rules. Two behavior notes: - One-shot CLI: `debug-with-gdb ... "show inferior-tty"` changes from refused to runnable. This is user-visible but directional-correct: the query is read-only and cannot reconfigure the output sink. - The MI form `-inferior-tty-show` is a defensive exemption. REA's own MI TTY calls do not route through this user-command gate, and the console interpreter may not accept MI text; the form is exempted so that, if it ever reaches the gate, it cannot revoke verification. Intentionally not included: any restoration path that re-verifies the TTY after a genuinely mutating command — mutating commands keep revoking, and detach keeps re-reading the live TTY before `-target-detach`. 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. ## Contract and boundary impact - Semantic owner and earliest changed stage: the GDB session manager's output-mutation classifier (`commandMayChangeInferiorOutput`); consumers are the console-command gate that clears `inferiorTtyVerified` and the detach proof. No superseded paths removed; the fail-closed revocation policy is retained for every non-exact match. - Contribution scope fit and linked maintainer decision: ordinary fix within the existing GDB boundary; not applicable. - CLI and MCP/tool-catalog contract: one-shot `debug-with-gdb ... "show inferior-tty"` moves from refused to runnable (read-only query); no other catalog changes. - Provider, bridge, target-format, or platform compatibility: GDB console and MI command classification only; no version-specific behavior added. - Evidence, artifact, provenance, or reconstruction contract: not applicable. - Target selection, authority, upstream behavior, and cleanup details (if applicable): none — the change does not alter target selection, detach authority, or cleanup; detach still re-verifies the live TTY. - Generated metadata (`docs/public/product-catalog.json`), package, or installation impact: none. Expected effects (check known effects; use documentation-only on its own). Unchecked items do not establish absence; leave uncertainties visible. - [x] 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: tests/boundary/providers/GdbSessionManagerCoverage.test.ts — query-form and composite-command classification rows (`classifies inferior TTY commands`), a `show inferior-tty` row in the one-shot classification table (`classifies one-shot GDB commands`), and the inspect-then-close detach path (`keeps the verified sink across the read-only show inferior-tty inspection`, including an execute-path assertion for the MI form and recorded-command assertions that the query text is dispatched and `-target-detach` follows). - Base reproduction or other evidence: the regression tests fail against the pre-fix classification (and against the current main source, which lacks the MI exemption) and pass with this branch. - User-visible CLI/MCP output (if applicable): `debug-with-gdb ... "show inferior-tty"` now executes the query instead of refusing it. - Remaining proof gaps: no test asserts that a real GDB console interpreter accepts the MI text `-inferior-tty-show`; the exemption there is defensive (see Change and scope). For boundary fixes, identify the applicable [boundary regressions](https://github.com/morluto/rea/blob/main/docs/testing.md#boundary-regressions) and [lifecycle regressions](https://github.com/morluto/rea/blob/main/docs/testing.md#lifecycle-regressions) covered by the evidence above, and explain relevant gaps. 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 - `npx vitest run tests/boundary/providers/GdbSessionManagerCoverage.test.ts` — 195/195 passed on this branch. - Same command with `src/gdb/GdbSessionManager.ts` temporarily reset to `origin/main`'s version — 2 failed (the `-inferior-tty-show` classification row and the MI execute-path assertion), confirming red on the affected base. - `npx prettier --check src/gdb/GdbSessionManager.ts tests/boundary/providers/GdbSessionManagerCoverage.test.ts` — clean. - `npx oxlint` on both touched files — 0 errors (pre-existing warnings only). - `npx tsc --noEmit -p .` — only pre-existing unrelated errors from missing optional fixtures dependencies (`@bufbuild/protobuf`, `@msgpack/msgpack`) in this environment; none in the touched files. ## Compatibility, safety, and release - Breaking changes or migration steps: none; the only observable change is that read-only TTY queries are no longer refused/revoking. - Real Hopper/Ghidra, browser, or OS coverage: not applicable (GDB provider only). - Package or release metadata impact: none. - Security, privacy, process, or containment review: the exemption is exact full-string match only; abbreviations, composites, and redirections keep revoking the verified flag, so the fail-closed direction is preserved. ## 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: @akushonkamen - [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. --- _{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

bsakaguchi added the

pull-request

label 2026-11-01 21:44:17 +00:00

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

[PR #6966] [MERGED] perf(artifacts): bound stable reads to one snapshot buffer #7479

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

No description provided.