[PR #5799] [MERGED] perf(ci): pack each test tier from its own timing history #7070

New issue

Closed

opened 2026-11-01 21:45:09 +00:00 by bsakaguchi · 0 comments

bsakaguchi commented 2026-11-01 21:45:09 +00:00

Owner

Copy link

📋 Pull Request Information

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

Base: main ← Head: cursor/ci-fast-timing-history-f42a

---

📝 Commits (3)

• f13d94c perf(ci): pack each test tier from its own timing history
• df96a74 perf(ci): drop the shared timing-history fallback
• 46570bc test(ci): look up fast history when only full timings exist

📊 Changes

5 files changed (+298 additions, -89 deletions)

View changed files

📝 .github/workflows/ci.yml (+18 -4)
📝 docs/testing.md (+25 -8)
📝 scripts/ci/test-history.mjs (+89 -62)
📝 tests/boundary/filesystem/ciTestHistory.test.ts (+149 -13)
📝 tests/boundary/filesystem/ciTestReports.test.ts (+17 -2)

📄 Description

Summary

Fast built shards are still packed with the latest full-suite timing artifact. That artifact stayed stale across the compiled-CLI session reuse, so some shards finish several minutes before the slowest one. Each tier now publishes and downloads its own history, and the old shared test-timings artifact is no longer read.

Human owner: @morluto.

Problem and expected behavior

On 2026-10-21, successful fast shard jobs still executed for about 5–10 minutes after runner queue. Run 39552964873 (eight built shards, after #5676, #5679, and #5784) ran its shard jobs for 319–591 seconds. The weights came from full history run 39545047294, recorded before the later session-reuse commits.

Replaying that fast run's file durations through allocateByDuration / scheduleWall (two workers, process-boundary after the main group):

• Stale full-suite weights: 293–547 seconds of file time.
• Weights from the same fast run: 404 seconds on every shard.

Hosted shard execution of 319–591 seconds tracks that stale spread plus setup. Fresh fast weights should cut the slowest shard's file schedule by about 140 seconds. The first green default-branch run of a tier has no tier artifact yet, so it uses Vitest's own assignment and then publishes the new one. The following run packs with that artifact.

Runner queue is separate and not fixed here. Across 108 successful shard jobs in 14 completed runs, queue was p50 198s, p95 435s, and max 988s (39542179402, shard 3/8). Cancelled main pushes in the same window had no jobs, so they were pending concurrency slots, not runners held by cancel-in-progress. Adding shards would ask for more runners while that queue is already the tail.

Change and scope

Default-branch push, schedule, and manual runs publish test-timings-fast or test-timings-full after a complete successful merge. Pull requests do not publish: the lookup reads one unpaginated artifact page. The build job downloads only the artifact for its tier. A tier with no qualifying artifact leaves history unset. There is no fallback to the previous test-timings artifact or to the other tier.

Not included: shard-count changes, a higher Vitest worker cap, or cancelling in-progress main runs. Eight fast shards stay inside the existing ten-minute job budget, and docs/testing.md already records that four workers did not remove the long-file floor.

No separate issue is linked. This continues the CI wall-time work in #5676, #5679, and #5784.

Contribution scope: not applicable. This is CI history selection inside the existing test workflow.

Contract and boundary impact

• Semantic owner and earliest changed stage: scripts/ci/test-history.mjs owns which timing artifact the build job downloads. Shard execution is unchanged.
• Contribution scope fit and linked maintainer decision: not applicable.
• CLI and MCP/tool-catalog contract: none.
• Provider, bridge, target-format, or platform compatibility: none.
• Evidence, artifact, provenance, or reconstruction contract: none. The new artifacts are CI scheduling weights, not target 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.

Evidence and regression coverage

• Tests added or updated: tests/boundary/filesystem/ciTestHistory.test.ts covers full-tier selection, fast history that does not read the full artifact, pull-request history that is ignored instead of borrowed, a fast lookup that returns empty when only full-tier history exists, a missing tier that does not query, and failed fast candidates. ciTestReports.test.ts covers the publish condition and the tier-specific download name.
• Base reproduction or other evidence: GitHub Actions job timestamps for the runs in the summary, plus a local replay of the shipped sequencer on the test-results artifact from run 39552964873 and history artifact 12322235443 from run 39545047294. The 404s / 293–547s figures are that replay, not a hosted before/after.
• User-visible CLI/MCP output (if applicable): not applicable. No CLI or MCP behavior changes.
• Remaining proof gaps: this pull request's own CI has no test-timings-fast artifact yet, so its shards use Vitest's default assignment. Hosted wall-time after the first green default-branch publish is not measured yet.

For evidence-bearing changes:

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

Validation performed

• npm run test:focused -- tests/boundary/filesystem/ciTestHistory.test.ts tests/boundary/filesystem/ciTestReports.test.ts — 19 tests passed.
• npm run check:fast — typecheck and lint passed.
• node --experimental-strip-types replay of allocateByDuration / scheduleWall — stale weights 292.6–546.8s, fresh weights 404.4s on all eight shards.

Compatibility, safety, and release

• Breaking changes or migration steps: none for callers. Existing test-timings artifacts are no longer inputs. The first green default-branch run of each tier publishes the new artifact; until then, that tier has no duration history.
• Real Hopper/Ghidra, browser, or OS coverage: not applicable.
• Package or release metadata impact: none.
• Security, privacy, process, or containment review: history is still accepted only from a successful CI workflow on the default branch of this repository. Pull requests and other branches are not producers.

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.

  

---

_{🔄 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/5799 **Author:** [@morluto](https://github.com/morluto) **Created:** 10/21/2026 **Status:** ✅ Merged **Merged:** 10/21/2026 **Merged by:** [@morluto](https://github.com/morluto) **Base:** `main` ← **Head:** `cursor/ci-fast-timing-history-f42a` --- ### 📝 Commits (3) - [`f13d94c`](https://github.com/morluto/rea/commit/f13d94c0a00668272a93b895da3d0ee702c50a4c) perf(ci): pack each test tier from its own timing history - [`df96a74`](https://github.com/morluto/rea/commit/df96a747efe80c0f0323909a5003378c90385859) perf(ci): drop the shared timing-history fallback - [`46570bc`](https://github.com/morluto/rea/commit/46570bc4b03b7039ed356247e9c42c0d554bbc04) test(ci): look up fast history when only full timings exist ### 📊 Changes **5 files changed** (+298 additions, -89 deletions) <details> <summary>View changed files</summary> 📝 `.github/workflows/ci.yml` (+18 -4) 📝 `docs/testing.md` (+25 -8) 📝 `scripts/ci/test-history.mjs` (+89 -62) 📝 `tests/boundary/filesystem/ciTestHistory.test.ts` (+149 -13) 📝 `tests/boundary/filesystem/ciTestReports.test.ts` (+17 -2) </details> ### 📄 Description <!-- CURSOR_AGENT_PR_BODY_BEGIN --> ## Summary Fast built shards are still packed with the latest full-suite timing artifact. That artifact stayed stale across the compiled-CLI session reuse, so some shards finish several minutes before the slowest one. Each tier now publishes and downloads its own history, and the old shared `test-timings` artifact is no longer read. Human owner: @morluto. ## Problem and expected behavior On 2026-10-21, successful fast shard jobs still executed for about 5–10 minutes after runner queue. Run `39552964873` (eight built shards, after #5676, #5679, and #5784) ran its shard jobs for 319–591 seconds. The weights came from full history run `39545047294`, recorded before the later session-reuse commits. Replaying that fast run's file durations through `allocateByDuration` / `scheduleWall` (two workers, `process-boundary` after the main group): - Stale full-suite weights: 293–547 seconds of file time. - Weights from the same fast run: 404 seconds on every shard. Hosted shard execution of 319–591 seconds tracks that stale spread plus setup. Fresh fast weights should cut the slowest shard's file schedule by about 140 seconds. The first green default-branch run of a tier has no tier artifact yet, so it uses Vitest's own assignment and then publishes the new one. The following run packs with that artifact. Runner queue is separate and not fixed here. Across 108 successful shard jobs in 14 completed runs, queue was p50 198s, p95 435s, and max 988s (`39542179402`, shard 3/8). Cancelled main pushes in the same window had no jobs, so they were pending concurrency slots, not runners held by `cancel-in-progress`. Adding shards would ask for more runners while that queue is already the tail. ## Change and scope Default-branch push, schedule, and manual runs publish `test-timings-fast` or `test-timings-full` after a complete successful merge. Pull requests do not publish: the lookup reads one unpaginated artifact page. The build job downloads only the artifact for its tier. A tier with no qualifying artifact leaves history unset. There is no fallback to the previous `test-timings` artifact or to the other tier. Not included: shard-count changes, a higher Vitest worker cap, or cancelling in-progress main runs. Eight fast shards stay inside the existing ten-minute job budget, and `docs/testing.md` already records that four workers did not remove the long-file floor. No separate issue is linked. This continues the CI wall-time work in #5676, #5679, and #5784. Contribution scope: not applicable. This is CI history selection inside the existing test workflow. ## Contract and boundary impact - Semantic owner and earliest changed stage: `scripts/ci/test-history.mjs` owns which timing artifact the build job downloads. Shard execution is unchanged. - Contribution scope fit and linked maintainer decision: not applicable. - CLI and MCP/tool-catalog contract: none. - Provider, bridge, target-format, or platform compatibility: none. - Evidence, artifact, provenance, or reconstruction contract: none. The new artifacts are CI scheduling weights, not target 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. - [x] 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/filesystem/ciTestHistory.test.ts` covers full-tier selection, fast history that does not read the full artifact, pull-request history that is ignored instead of borrowed, a fast lookup that returns empty when only full-tier history exists, a missing tier that does not query, and failed fast candidates. `ciTestReports.test.ts` covers the publish condition and the tier-specific download name. - Base reproduction or other evidence: GitHub Actions job timestamps for the runs in the summary, plus a local replay of the shipped sequencer on the `test-results` artifact from run `39552964873` and history artifact `12322235443` from run `39545047294`. The 404s / 293–547s figures are that replay, not a hosted before/after. - User-visible CLI/MCP output (if applicable): not applicable. No CLI or MCP behavior changes. - Remaining proof gaps: this pull request's own CI has no `test-timings-fast` artifact yet, so its shards use Vitest's default assignment. Hosted wall-time after the first green default-branch publish is not measured yet. For evidence-bearing changes: - [x] Observed, derived, and inferred claims remain distinguishable. - [x] Artifact identity, source provenance, and failed attempts remain preserved. - [x] Unsupported, incomplete, unavailable, or uncertain outcomes remain visible. ## Validation performed - `npm run test:focused -- tests/boundary/filesystem/ciTestHistory.test.ts tests/boundary/filesystem/ciTestReports.test.ts` — 19 tests passed. - `npm run check:fast` — typecheck and lint passed. - `node --experimental-strip-types` replay of `allocateByDuration` / `scheduleWall` — stale weights 292.6–546.8s, fresh weights 404.4s on all eight shards. ## Compatibility, safety, and release - Breaking changes or migration steps: none for callers. Existing `test-timings` artifacts are no longer inputs. The first green default-branch run of each tier publishes the new artifact; until then, that tier has no duration history. - Real Hopper/Ghidra, browser, or OS coverage: not applicable. - Package or release metadata impact: none. - Security, privacy, process, or containment review: history is still accepted only from a successful CI workflow on the default branch of this repository. Pull requests and other branches are not producers. ## 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. - [x] 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-d3199c39-96f6-5d2c-8b1a-4bc227d7f42a?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-d3199c39-96f6-5d2c-8b1a-4bc227d7f42a&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> --- _{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

bsakaguchi 2026-11-01 21:45:09 +00:00

• closed this issue
• added the
  pull-request
  label

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

[PR #7070] [MERGED] fix(ghidra): accept stock language IDs with LEBE endianness or a slash #7622

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

No description provided.