[PR #6294] test(javascript): order the caller abort by frame, not wall clock #7262

New issue

Open

opened 2026-11-01 21:46:34 +00:00 by bsakaguchi · 0 comments

bsakaguchi commented 2026-11-01 21:46:34 +00:00

Owner

Copy link

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/6294
Author: @cainiao1992
Created: 10/22/2026
Status: 🔄 Open

Base: main ← Head: fix/worker-order-audit-abort-timing

---

📝 Commits (1)

• 90cd530 test(javascript): order the caller abort by frame, not wall clock

📊 Changes

1 file changed (+6 additions, -3 deletions)

View changed files

📝 tests/boundary/javascript/workerOrderAudit.test.ts (+6 -3)

📄 Description

Summary

Stabilizes tests/boundary/javascript/workerOrderAudit.test.ts case retains coalesced static evidence when abort follows a resource frame, which failed in CI (Test shard (3/8) of run 39743487960) with AssertionError: expected false to be true on controller.signal.aborted. The test ordered the caller abort with a 5 ms wall-clock timer; it now orders it with the worker protocol itself while keeping the coalesced static-plus-failure dispatch.

Problem and expected behavior

The regression intends to prove that an abort delivered after the worker reported a failure (reason: "resource") frame leaves that resource failure primary and keeps the already-coalesced static evidence. The fixture wrote the static frame and the resource frame in one write and armed setTimeout(() => controller.abort(null), 5) when the chunk surfaced, so the abort had to win a sub-millisecond race against the runtime's own completion path (checkpoint read, admission reply, terminal frame, temp-file removal). That path can run entirely within one event-loop iteration, while the timer is only observed in a later timers phase, so under CI load the abort arrived after analyze() had already resolved — the assertion that the abort was delivered inside the operation then failed. Nothing about the runtime behavior was wrong; the ordering was asserted with wall-clock timing.

Expected behavior after the change: the frame that establishes the ordering is the protocol frame itself, and the abort is delivered at a point the implementation defines, independent of machine speed.

Change and scope

• The fixture still writes the static checkpoint frame and the resource failure frame in one write, so the coalesced multi-frame dispatch this case names and covers is unchanged. Only the abort ordering changed.
• The abort is triggered by the observed failure frame through the file's existing observeWorkerFrames helper and deferred by one microtask, which places it behind the runtime's own reader for that chunk: the failure is recorded as primary before cancellation is delivered, and the frame loop still observes the cancellation before resolving. No timer, no delay constant.
• Assertions are unchanged: abort delivered, AnalysisResourceConstraintError with reason: "resource failure before abort", retained javascript.parse_status === "complete".

Intentionally not included: the other four cases in the same file that still order aborts with setTimeout:

• clears a consumed resource frame before the next reusable worker job (5 ms; the abort has to follow a response in a second reusable job, so the observation point is a different job's frame).
• selects a control-frame budget failure observed before caller abort (20 ms; the abort is armed by accumulated stdout bytes past 64 KiB, where no parseable frame exists to key on and the timer is the ordering itself).
• preserves a complete current-job failure parsed before caller abort (5 ms; convertible to the same frame ordering, but it needs its own phase-frame sequencing and is a separate change).
• does not let a wrong-job failure frame override later caller abort (5 ms; same).

They passed in CI and are left alone rather than converted speculatively; the last two are the natural follow-up if this ordering proves stable.

Follow the contribution scope: not applicable — a test-only stabilization inside existing boundaries; no new provider and no capability involving target execution, injection, mutation, or protection recovery.

Contract and boundary impact

• Semantic owner and earliest changed stage: JavaScript analysis worker regression test only; no production code changed.
• Contribution scope fit and linked maintainer decision: not applicable (test stabilization; ordinary fix within existing boundaries).
• CLI and MCP/tool-catalog contract: none.
• Provider, bridge, target-format, or platform compatibility: none.
• Evidence, artifact, provenance, or reconstruction contract: none; the covered contract is "resource failure recorded before cancellation stays primary and retains static evidence".
• Target selection, authority, upstream behavior, and cleanup details (if applicable): not applicable.
• 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): 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.

The test launches fixture child processes only; no analyzed-target interaction is introduced or changed.

Evidence and regression coverage

• Tests added or updated: tests/boundary/javascript/workerOrderAudit.test.ts — retains coalesced static evidence when abort follows a resource frame reordered as described, with the single-write static-plus-failure dispatch preserved. No other case changed.
• Base reproduction or other evidence: the failure is observed at the affected base revision in CI, CI required run 39743487960, Test shard (3/8): AssertionError: expected false to be true at expect(controller.signal.aborted).toBe(true). It was not reproduced locally before the change (30 CPU-contention loops on the whole file still passed), so the CI log is the reproduction evidence, not a local one.
• User-visible CLI/MCP output (if applicable): not applicable.
• Remaining proof gaps: the ordering proof is now structural rather than empirical; the previously flaky delivery point is no longer time-based. Local stress runs cannot prove the original CI timing was the only cause, only that the timing dependency is gone.

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/javascript/workerOrderAudit.test.ts — 35/35 passed, on this head rebased onto 2b8fb387b
• npx vitest run tests/boundary/javascript/workerOrderAudit.test.ts -t "retains coalesced static evidence when abort follows a resource frame" — 5/5 consecutive runs, same head
• Ordering-sensitivity check: replacing the deferred abort with a synchronous controller.abort(null) in the same observation makes the case fail with AnalysisCancelledError instead of the resource failure, which confirms the case still asserts "failure recorded before cancellation" rather than passing vacuously; re-run on this head
• npx oxfmt --check tests/boundary/javascript/workerOrderAudit.test.ts — formatted
• npx oxlint tests/boundary/javascript/workerOrderAudit.test.ts — 0 warnings, 0 errors
• npm run check:fast — passed

Compatibility, safety, and release

• Breaking changes or migration steps: none.
• Real Hopper/Ghidra, browser, or OS coverage: not applicable (fixture child processes only).
• Package or release metadata impact: none.
• Security, privacy, process, or containment review: no production behavior changed; the fixture child processes are spawned through the existing spawnOwnedProviderProcess owner.

Author readiness

Human owner: @cainiao1992

• 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/6294 **Author:** [@cainiao1992](https://github.com/cainiao1992) **Created:** 10/22/2026 **Status:** 🔄 Open **Base:** `main` ← **Head:** `fix/worker-order-audit-abort-timing` --- ### 📝 Commits (1) - [`90cd530`](https://github.com/morluto/rea/commit/90cd530a8c21cf812e0969b2134504eec1d8c1b6) test(javascript): order the caller abort by frame, not wall clock ### 📊 Changes **1 file changed** (+6 additions, -3 deletions) <details> <summary>View changed files</summary> 📝 `tests/boundary/javascript/workerOrderAudit.test.ts` (+6 -3) </details> ### 📄 Description ## Summary Stabilizes `tests/boundary/javascript/workerOrderAudit.test.ts` case `retains coalesced static evidence when abort follows a resource frame`, which failed in CI (`Test shard (3/8)` of run 39743487960) with `AssertionError: expected false to be true` on `controller.signal.aborted`. The test ordered the caller abort with a 5 ms wall-clock timer; it now orders it with the worker protocol itself while keeping the coalesced static-plus-failure dispatch. ## Problem and expected behavior The regression intends to prove that an abort delivered after the worker reported a `failure` (`reason: "resource"`) frame leaves that resource failure primary and keeps the already-coalesced static evidence. The fixture wrote the static frame and the resource frame in one write and armed `setTimeout(() => controller.abort(null), 5)` when the chunk surfaced, so the abort had to win a sub-millisecond race against the runtime's own completion path (checkpoint read, admission reply, terminal frame, temp-file removal). That path can run entirely within one event-loop iteration, while the timer is only observed in a later timers phase, so under CI load the abort arrived after `analyze()` had already resolved — the assertion that the abort was delivered inside the operation then failed. Nothing about the runtime behavior was wrong; the ordering was asserted with wall-clock timing. Expected behavior after the change: the frame that establishes the ordering is the protocol frame itself, and the abort is delivered at a point the implementation defines, independent of machine speed. ## Change and scope - The fixture still writes the static checkpoint frame and the resource `failure` frame in one write, so the coalesced multi-frame dispatch this case names and covers is unchanged. Only the abort ordering changed. - The abort is triggered by the observed `failure` frame through the file's existing `observeWorkerFrames` helper and deferred by one microtask, which places it behind the runtime's own reader for that chunk: the failure is recorded as primary before cancellation is delivered, and the frame loop still observes the cancellation before resolving. No timer, no delay constant. - Assertions are unchanged: abort delivered, `AnalysisResourceConstraintError` with `reason: "resource failure before abort"`, retained `javascript.parse_status === "complete"`. Intentionally not included: the other four cases in the same file that still order aborts with `setTimeout`: - `clears a consumed resource frame before the next reusable worker job` (5 ms; the abort has to follow a response in a second reusable job, so the observation point is a different job's frame). - `selects a control-frame budget failure observed before caller abort` (20 ms; the abort is armed by accumulated stdout bytes past 64 KiB, where no parseable frame exists to key on and the timer is the ordering itself). - `preserves a complete current-job failure parsed before caller abort` (5 ms; convertible to the same frame ordering, but it needs its own phase-frame sequencing and is a separate change). - `does not let a wrong-job failure frame override later caller abort` (5 ms; same). They passed in CI and are left alone rather than converted speculatively; the last two are the natural follow-up if this ordering proves stable. Follow the [contribution scope](https://github.com/morluto/rea/blob/main/CONTRIBUTING.md#contribution-scope): not applicable — a test-only stabilization inside existing boundaries; no new provider and no capability involving target execution, injection, mutation, or protection recovery. ## Contract and boundary impact - Semantic owner and earliest changed stage: JavaScript analysis worker regression test only; no production code changed. - Contribution scope fit and linked maintainer decision: not applicable (test stabilization; ordinary fix within existing boundaries). - CLI and MCP/tool-catalog contract: none. - Provider, bridge, target-format, or platform compatibility: none. - Evidence, artifact, provenance, or reconstruction contract: none; the covered contract is "resource failure recorded before cancellation stays primary and retains static evidence". - Target selection, authority, upstream behavior, and cleanup details (if applicable): not applicable. - 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): 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. - [x] 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. The test launches fixture child processes only; no analyzed-target interaction is introduced or changed. ## Evidence and regression coverage - Tests added or updated: `tests/boundary/javascript/workerOrderAudit.test.ts` — `retains coalesced static evidence when abort follows a resource frame` reordered as described, with the single-write static-plus-failure dispatch preserved. No other case changed. - Base reproduction or other evidence: the failure is observed at the affected base revision in CI, `CI required` run 39743487960, `Test shard (3/8)`: `AssertionError: expected false to be true` at `expect(controller.signal.aborted).toBe(true)`. It was not reproduced locally before the change (30 CPU-contention loops on the whole file still passed), so the CI log is the reproduction evidence, not a local one. - User-visible CLI/MCP output (if applicable): not applicable. - Remaining proof gaps: the ordering proof is now structural rather than empirical; the previously flaky delivery point is no longer time-based. Local stress runs cannot prove the original CI timing was the only cause, only that the timing dependency is gone. 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/javascript/workerOrderAudit.test.ts` — 35/35 passed, on this head rebased onto `2b8fb387b` - `npx vitest run tests/boundary/javascript/workerOrderAudit.test.ts -t "retains coalesced static evidence when abort follows a resource frame"` — 5/5 consecutive runs, same head - Ordering-sensitivity check: replacing the deferred abort with a synchronous `controller.abort(null)` in the same observation makes the case fail with `AnalysisCancelledError` instead of the resource failure, which confirms the case still asserts "failure recorded before cancellation" rather than passing vacuously; re-run on this head - `npx oxfmt --check tests/boundary/javascript/workerOrderAudit.test.ts` — formatted - `npx oxlint tests/boundary/javascript/workerOrderAudit.test.ts` — 0 warnings, 0 errors - `npm run check:fast` — passed ## Compatibility, safety, and release - Breaking changes or migration steps: none. - Real Hopper/Ghidra, browser, or OS coverage: not applicable (fixture child processes only). - Package or release metadata impact: none. - Security, privacy, process, or containment review: no production behavior changed; the fixture child processes are spawned through the existing `spawnOwnedProviderProcess` owner. ## 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. Draft PRs may leave them unchecked. Keep the description and validation evidence current as the work changes. See CONTRIBUTING.md#pull-request-ownership-and-readiness. --> Human owner: @cainiao1992 - [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 - [x] This PR addresses a concrete problem or an agreed enhancement. - [x] Material scope and authority questions are resolved, and any required maintainer scope decision covers the final diff. - [x] The PR has one focused outcome and the title follows `type(scope): outcome`. - [x] Related issue is linked, or the reason for not linking one is stated above. - [x] 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. - [x] 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 added the

pull-request

label 2026-11-01 21:46:34 +00:00

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

[PR #7262] [CLOSED] fix(scripts): format the APK signature verifier import #7757

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

No description provided.