morluto/rea
1
0
Fork 0
mirror of https://github.com/morluto/rea.git synced 2026-11-05 06:45:22 +00:00
Code Issues 1.3k Projects Packages Wiki Activity

[PR #5652] [MERGED] perf(ci): keep fast built shards under ten minutes #7015

New issue
Closed
opened 2026-11-01 21:44:44 +00:00 by bsakaguchi · 0 comments
bsakaguchi commented 2026-11-01 21:44:44 +00:00
Owner
Copy link

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/5652
Author: @morluto
Created: 10/20/2026
Status: ✅ Merged
Merged: 10/20/2026
Merged by: @morluto

Base: main ← Head: cursor/ci-shard-budget-82da

📝 Commits (6)

  • 1b1ef06 test(acceptance): split competing loader ownership across files
  • 70cb99a perf(ci): run eight fast built shards under a ten-minute budget
  • 5538c11 fix(ci): keep each scheduled file on one worker lane
  • 2d7b6e6 docs(testing): separate the shard budget from workflow time
  • 94fbf85 docs(testing): match fast shard count to lane scheduling
  • b4239e0 fix(ci): seed split loader durations from pre-split history

📊 Changes

9 files changed (+775 additions, -464 deletions)

View changed files

📝 .github/workflows/ci.yml (+5 -3)
📝 docs/testing.md (+43 -17)
➕ tests/acceptance/applications/javascriptLiteralLoaderOwnership.ts (+401 -0)
➕ tests/acceptance/applications/javascriptLiteralLoaderOwnershipEarly.test.ts (+29 -0)
➕ tests/acceptance/applications/javascriptLiteralLoaderOwnershipLate.test.ts (+18 -0)
➕ tests/acceptance/applications/javascriptLiteralLoaderOwnershipMiddle.test.ts (+18 -0)
📝 tests/acceptance/applications/javascriptLiteralPercentPaths.test.ts (+0 -385)
📝 tests/boundary/filesystem/ciTestSequencer.test.ts (+102 -19)
📝 tests/ciTestSequencer.ts (+159 -40)

📄 Description

Summary

Fast built Vitest shards were still about 15 minutes because one file took 578 seconds and five shards with two workers cannot schedule the built suite under ten minutes. This PR splits that loader matrix, schedules each file onto one worker lane, and runs eight fast built shards. The ten-minute target is the uncontended built shard job. Classification, build, and the portable-test merge are measured separately.

Rebased onto main 0add6a5aa after #5634. The fast/deep static split stays. The IDA retryable expectation stays main's: an unchanged invalid request is not retryable.

No linked issue. This continues the requested CI wall-time work on a new branch, separate from #5634, #5655, and #5658.

Problem and expected behavior

On 2026-10-20, run 39451548945 spent 925 seconds in its slowest built shard job (shard 4/5) and 874 seconds in built Vitest on shard 1/5. File timings from that run contain 7944 seconds of built module time. javascriptLiteralPercentPaths.test.ts alone was 578 seconds.

process-boundary stays serial and runs after the parallel projects (groupOrder 1, resolved maxWorkers 1). Dividing a parallel file by its worker count removes that file's own floor and can pack it onto a serial tail.

Published timings still name that one path. Without a bridge, the shortened file would keep the 578-second weight and the three new files would get only the suite median.

node_modules is 674 MiB. Shipping it between jobs would move more bytes than the 9-second npm ci. The existing npm download cache remains the setup cache.

Change and scope

  • Split the competing-loader matrix into three acceptance files. Every CLI and stdio MCP case is still asserted. The files share one helper.
  • Fast CI runs eight built shards after the build, plus the existing source job. Full qualification stays six covered shards.
  • The history sequencer places each file whole on one lane. Peers overlap only inside a sequence group, up to that group's resolved worker count. Later groups add their makespan.
  • Until history records one of the three new loader files, the sequencer shares the old path's duration by the pre-split case counts: 54/192 for the remaining file and 46/192 for each new file. A later artifact that names any new file is used as published.
  • docs/testing.md records the shard-job budget, that history bridge, and the measured classification, build, and merge that sit outside the shard job.

Not in this change: child-workflow concurrency (those lanes must keep the caller's group), and caching node_modules. Four local workers only improved a six-file sample from 96–101 seconds to 71–73 seconds, and a single file still occupies one worker, so the cap stays two. process-boundary is not made parallel; host sampling still shares one lane.

Follow the contribution scope. Not applicable: no new provider, target execution, injection, mutation, or protection recovery.

Contract and boundary impact

  • Semantic owner and earliest changed stage: CI test scheduling and acceptance test file layout. No product behavior change.
  • Contribution scope fit and linked maintainer decision: CI orchestration and test harness only. Not applicable.
  • CLI and MCP/tool-catalog contract: none. The same CLI and MCP cases still run.
  • Provider, bridge, target-format, or platform compatibility: none.
  • Evidence, artifact, provenance, or reconstruction contract: none.
  • 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: none of the target-interaction effects below. This changes CI scheduling and test file layout only.

  • 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: loader cases moved, not dropped; a partition test checks the three groups cover the name list once. Sequencer tests keep a 300-second file whole on a two-worker lane, add a serial file after a parallel file (160 seconds), and place one 100-second parallel file alone while two 60-second serial files share the other shard. A history test divides 192000 ms into 54000 and three times 46000, and leaves the map unchanged once any new path is present. ciFeedback merges one source blob and eight built blobs.
  • Base reproduction or other evidence: run 39451548945. Classification 15 seconds, build 49 seconds, portable-test merge 29 seconds, shard 1/5 setup 25 seconds around 874 seconds of built Vitest, slowest shard job 925 seconds. Lane schedule of that built inventory: five shards peak at 820 seconds of tests; six at 684 seconds. After splitting the 578-second file by case count (54 remain, 46 in each of three files), eight shards peak at 513 seconds of tests, about 538 seconds with the measured shard setup. Adding classification, build, and merge makes about 631 seconds of uncontended critical path. On this PR's pre-rebase run 39475793479, the one finished successful shard (5/8) spent 463 seconds in Vitest and 488 seconds for the job. Fail-fast then cancelled the rest. The red lanes matched main: IDA retryable and spawn E2BIG.
  • User-visible CLI/MCP output (if applicable): none.
  • Remaining proof gaps: hosted wall time for a complete eight-shard matrix on this head is not measured yet. The file schedule under-reads the five-shard run's hosted Vitest. Queue time can grow because each fast code PR starts three more shard jobs. Full qualification is still six covered shards. The 399-second loader-review file is still one file. The history bridge retires when a published artifact names one of the new loader files.

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 check:ci:fast after the history seed — succeeded in 15.9 seconds (typecheck, lint:built, format:check).
  • npx vitest run tests/boundary/filesystem/ciTestSequencer.test.ts — 7 passed in 640ms (Node 24.18.0).
  • After the rebase onto 0add6a5aa, before this seed: npm run check:ci:fast succeeded in 48 seconds, and sequencer plus ciFeedback tests passed 13 tests in 5.1 seconds.
  • Earlier, before the rebase: npx vitest run on the three loader files, javascriptLiteralPercentPaths.test.ts, ciFeedback, and ciTestSequencer — 206 passed in 200.6 seconds.
  • Local worker sample, six acceptance/CLI files, 96 tests each run, all passed: two workers 96.3s and 100.8s; four workers 70.7s and 72.7s.
  • Lane probe during vitest --shard=1/2: process-boundary resolved maxWorkers=1; boundary resolved maxWorkers=2.

Compatibility, safety, and release

  • Breaking changes or migration steps: none.
  • Real Hopper/Ghidra, browser, or OS coverage: not run. This change does not select those lanes.
  • Package or release metadata impact: none.
  • Security, privacy, process, or containment review: not applicable.

Author readiness

Human owner: @morluto

  • 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.
Open in Web Open in Cursor 

🔄 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/5652 **Author:** [@morluto](https://github.com/morluto) **Created:** 10/20/2026 **Status:** ✅ Merged **Merged:** 10/20/2026 **Merged by:** [@morluto](https://github.com/morluto) **Base:** `main` ← **Head:** `cursor/ci-shard-budget-82da` --- ### 📝 Commits (6) - [`1b1ef06`](https://github.com/morluto/rea/commit/1b1ef069a37e7e01bcef8f254dc9172bef0361e4) test(acceptance): split competing loader ownership across files - [`70cb99a`](https://github.com/morluto/rea/commit/70cb99aec36399bf6869ce75f98efe6690e0e254) perf(ci): run eight fast built shards under a ten-minute budget - [`5538c11`](https://github.com/morluto/rea/commit/5538c113f13f2e2635ff0dd955befd0b56e6e547) fix(ci): keep each scheduled file on one worker lane - [`2d7b6e6`](https://github.com/morluto/rea/commit/2d7b6e61641aa3cbdcca2af08b0c292c8edcbab7) docs(testing): separate the shard budget from workflow time - [`94fbf85`](https://github.com/morluto/rea/commit/94fbf859a8e29fed990718204fc9d4a7e8b2db42) docs(testing): match fast shard count to lane scheduling - [`b4239e0`](https://github.com/morluto/rea/commit/b4239e07d5c9a894432feef6884d282850377a99) fix(ci): seed split loader durations from pre-split history ### 📊 Changes **9 files changed** (+775 additions, -464 deletions) <details> <summary>View changed files</summary> 📝 `.github/workflows/ci.yml` (+5 -3) 📝 `docs/testing.md` (+43 -17) ➕ `tests/acceptance/applications/javascriptLiteralLoaderOwnership.ts` (+401 -0) ➕ `tests/acceptance/applications/javascriptLiteralLoaderOwnershipEarly.test.ts` (+29 -0) ➕ `tests/acceptance/applications/javascriptLiteralLoaderOwnershipLate.test.ts` (+18 -0) ➕ `tests/acceptance/applications/javascriptLiteralLoaderOwnershipMiddle.test.ts` (+18 -0) 📝 `tests/acceptance/applications/javascriptLiteralPercentPaths.test.ts` (+0 -385) 📝 `tests/boundary/filesystem/ciTestSequencer.test.ts` (+102 -19) 📝 `tests/ciTestSequencer.ts` (+159 -40) </details> ### 📄 Description <!-- CURSOR_AGENT_PR_BODY_BEGIN --> ## Summary Fast built Vitest shards were still about 15 minutes because one file took 578 seconds and five shards with two workers cannot schedule the built suite under ten minutes. This PR splits that loader matrix, schedules each file onto one worker lane, and runs eight fast built shards. The ten-minute target is the uncontended built shard job. Classification, build, and the portable-test merge are measured separately. Rebased onto main `0add6a5aa` after #5634. The fast/deep static split stays. The IDA retryable expectation stays main's: an unchanged invalid request is not retryable. No linked issue. This continues the requested CI wall-time work on a new branch, separate from #5634, #5655, and #5658. ## Problem and expected behavior On 2026-10-20, run `39451548945` spent 925 seconds in its slowest built shard job (shard 4/5) and 874 seconds in built Vitest on shard 1/5. File timings from that run contain 7944 seconds of built module time. `javascriptLiteralPercentPaths.test.ts` alone was 578 seconds. `process-boundary` stays serial and runs after the parallel projects (`groupOrder` 1, resolved `maxWorkers` 1). Dividing a parallel file by its worker count removes that file's own floor and can pack it onto a serial tail. Published timings still name that one path. Without a bridge, the shortened file would keep the 578-second weight and the three new files would get only the suite median. `node_modules` is 674 MiB. Shipping it between jobs would move more bytes than the 9-second `npm ci`. The existing npm download cache remains the setup cache. ## Change and scope - Split the competing-loader matrix into three acceptance files. Every CLI and stdio MCP case is still asserted. The files share one helper. - Fast CI runs eight built shards after the build, plus the existing source job. Full qualification stays six covered shards. - The history sequencer places each file whole on one lane. Peers overlap only inside a sequence group, up to that group's resolved worker count. Later groups add their makespan. - Until history records one of the three new loader files, the sequencer shares the old path's duration by the pre-split case counts: 54/192 for the remaining file and 46/192 for each new file. A later artifact that names any new file is used as published. - `docs/testing.md` records the shard-job budget, that history bridge, and the measured classification, build, and merge that sit outside the shard job. Not in this change: child-workflow concurrency (those lanes must keep the caller's group), and caching `node_modules`. Four local workers only improved a six-file sample from 96–101 seconds to 71–73 seconds, and a single file still occupies one worker, so the cap stays two. `process-boundary` is not made parallel; host sampling still shares one lane. Follow the [contribution scope](https://github.com/morluto/rea/blob/main/CONTRIBUTING.md#contribution-scope). Not applicable: no new provider, target execution, injection, mutation, or protection recovery. ## Contract and boundary impact - Semantic owner and earliest changed stage: CI test scheduling and acceptance test file layout. No product behavior change. - Contribution scope fit and linked maintainer decision: CI orchestration and test harness only. Not applicable. - CLI and MCP/tool-catalog contract: none. The same CLI and MCP cases still run. - Provider, bridge, target-format, or platform compatibility: none. - Evidence, artifact, provenance, or reconstruction contract: none. - 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: none of the target-interaction effects below. This changes CI scheduling and test file layout only. - [ ] 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: loader cases moved, not dropped; a partition test checks the three groups cover the name list once. Sequencer tests keep a 300-second file whole on a two-worker lane, add a serial file after a parallel file (160 seconds), and place one 100-second parallel file alone while two 60-second serial files share the other shard. A history test divides 192000 ms into 54000 and three times 46000, and leaves the map unchanged once any new path is present. `ciFeedback` merges one source blob and eight built blobs. - Base reproduction or other evidence: run `39451548945`. Classification 15 seconds, build 49 seconds, portable-test merge 29 seconds, shard 1/5 setup 25 seconds around 874 seconds of built Vitest, slowest shard job 925 seconds. Lane schedule of that built inventory: five shards peak at 820 seconds of tests; six at 684 seconds. After splitting the 578-second file by case count (54 remain, 46 in each of three files), eight shards peak at 513 seconds of tests, about 538 seconds with the measured shard setup. Adding classification, build, and merge makes about 631 seconds of uncontended critical path. On this PR's pre-rebase run `39475793479`, the one finished successful shard (5/8) spent 463 seconds in Vitest and 488 seconds for the job. Fail-fast then cancelled the rest. The red lanes matched main: IDA `retryable` and `spawn E2BIG`. - User-visible CLI/MCP output (if applicable): none. - Remaining proof gaps: hosted wall time for a complete eight-shard matrix on this head is not measured yet. The file schedule under-reads the five-shard run's hosted Vitest. Queue time can grow because each fast code PR starts three more shard jobs. Full qualification is still six covered shards. The 399-second loader-review file is still one file. The history bridge retires when a published artifact names one of the new loader files. 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 check:ci:fast` after the history seed — succeeded in 15.9 seconds (typecheck, lint:built, format:check). - `npx vitest run tests/boundary/filesystem/ciTestSequencer.test.ts` — 7 passed in 640ms (Node 24.18.0). - After the rebase onto `0add6a5aa`, before this seed: `npm run check:ci:fast` succeeded in 48 seconds, and sequencer plus `ciFeedback` tests passed 13 tests in 5.1 seconds. - Earlier, before the rebase: `npx vitest run` on the three loader files, `javascriptLiteralPercentPaths.test.ts`, `ciFeedback`, and `ciTestSequencer` — 206 passed in 200.6 seconds. - Local worker sample, six acceptance/CLI files, 96 tests each run, all passed: two workers 96.3s and 100.8s; four workers 70.7s and 72.7s. - Lane probe during `vitest --shard=1/2`: `process-boundary` resolved `maxWorkers=1`; `boundary` resolved `maxWorkers=2`. ## Compatibility, safety, and release - Breaking changes or migration steps: none. - Real Hopper/Ghidra, browser, or OS coverage: not run. This change does not select those lanes. - Package or release metadata impact: none. - Security, privacy, process, or containment review: not applicable. ## Author readiness Human owner: @morluto - [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. - [x] 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. <!-- CURSOR_AGENT_PR_BODY_END --> <div><a href="https://cursor.com/agents/bc-f85d7d37-0a4b-5e62-9992-2a20ade282da?cursor_ref=pr_footer&cursor_cta=open_in_web"><picture><source media="(prefers-color-scheme: dark)" srcset="https://cursor.com/assets/images/open-in-web-dark.png"><source media="(prefers-color-scheme: light)" srcset="https://cursor.com/assets/images/open-in-web-light.png"><img alt="Open in Web" width="114" height="28" src="https://cursor.com/assets/images/open-in-web-dark.png"></picture></a>&nbsp;<a href="https://cursor.com/background-agent?bcId=bc-f85d7d37-0a4b-5e62-9992-2a20ade282da&cursor_ref=pr_footer&cursor_cta=open_in_cursor"><picture><source media="(prefers-color-scheme: dark)" srcset="https://cursor.com/assets/images/open-in-cursor-dark.png"><source media="(prefers-color-scheme: light)" srcset="https://cursor.com/assets/images/open-in-cursor-light.png"><img alt="Open in Cursor" width="131" height="28" src="https://cursor.com/assets/images/open-in-cursor-dark.png"></picture></a>&nbsp;</div> --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
bsakaguchi 2026-11-01 21:44:44 +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
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#7015
No description provided.