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 #5022] fix(publish-mcp): retry and classify registry read failures #6740

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

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/5022
Author: @Rintu62
Created: 10/18/2026
Status: 🔄 Open

Base: main ← Head: fix/registry-read-hardening

📝 Commits (5)

  • f27df51 fix(publish-mcp): retry and classify registry read failures
  • fb8419a Merge remote-tracking branch 'upstream/main' into fix/registry-read-hardening
  • b806d3e fix(publish-mcp): cancel failed response bodies and keep summary best-effort
  • 917569f test(publish-mcp): use the shared temp directory helper
  • 9c7b2ea Merge remote-tracking branch 'upstream/main' into fix/registry-read-hardening

📊 Changes

3 files changed (+227 additions, -10 deletions)

View changed files

📝 .github/actions/publish-mcp/registry-state.d.mts (+14 -0)
📝 .github/actions/publish-mcp/registry-state.mjs (+76 -9)
📝 tests/boundary/filesystem/mcpRegistryPublication.test.ts (+137 -1)

📄 Description

Summary

Fixes #4998.

Before publishing, the workflow checks whether this version already exists in the MCP Registry. That check (registry-state.mjs) gave up on the first timeout, so one slow response blocked the whole publish. It now retries twice for temporary failures. If it still fails, the job fails exactly like before, and the failure type is written to the job summary.

Problem and expected behavior

In #4998 the registry's /v0.1/ping returned 200, but the listing request timed out after 30 s and the job stopped before authentication. A short blip shouldn't be enough to stop a release, and the job output should say whether it was a timeout, a 5xx or a 404.

The safety rule stays the same: if the lookup can't finish, the result is unknown and the job fails. A failed read is never treated as "not published".

Change and scope

  • Added a small readPage helper around the existing request and JSON parse. It retries twice (waits 5 s, then 15 s) on timeouts, network errors and 5xx. It does not retry 404 or other 4xx.
  • Before a retry, the failed response body is cancelled so the connection is not left busy.
  • If the last retry fails, the original error is thrown again, so registryPublicationState can't return "absent" unless every page was read.
  • Added classifyReadFailure. When the script runs as the action step, a failure writes the kind (timeout, network_error, server_error, not_found, http_error, other) to GITHUB_STEP_SUMMARY and then rethrows. Writing the summary is best effort: if that write fails, the original registry error is still the one that is thrown.
  • registryPublicationState takes an optional third argument (retryDelaysMs, sleep) so tests don't wait for real delays. Types are updated in registry-state.d.mts.

I didn't change action.yml, authentication, the publish step, the 30 s timeout or the metadata comparison. This doesn't fix the registry problem itself, it only makes the job handle it better.

This is a routine fix inside existing boundaries, so a maintainer scope decision doesn't apply. See the contribution scope.

Contract and boundary impact

  • Semantic owner and earliest changed stage: .github/actions/publish-mcp/registry-state.mjs, the version lookup before authentication.
  • Contribution scope fit and linked maintainer decision: routine fix, not applicable.
  • CLI and MCP/tool-catalog contract: none, this is a release workflow helper.
  • Provider, bridge, target-format, or platform compatibility: none.
  • Evidence, artifact, provenance, or reconstruction contract: not applicable.
  • Target selection, authority, upstream behavior, and cleanup details: not applicable, no target is touched. It only reads the public registry listing.
  • Generated metadata, package, or installation impact: none, no generated files changed.

Expected effects:

  • 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 script reads server.json as before. The network call is the existing registry GET, now retried. On failure it appends a short note to the GITHUB_STEP_SUMMARY file.

Evidence and regression coverage

  • Tests added or updated: 6 new tests in tests/boundary/filesystem/mcpRegistryPublication.test.ts (retry then success with delays 5000 and 15000, all attempts time out and the error is rethrown after 3 calls, no retry on 404, failure classification, failed response body is cancelled before the retry, original error is kept when the job summary can't be written). The last one runs the script in a temp directory from createTestTempDirectory. The existing 503 test now passes { sleep: noSleep } so it doesn't wait for real delays.
  • Base reproduction or other evidence: I didn't run the new tests against the base revision. Reading the base code, it makes one request per page and throws on the first failure, so the retry tests would not pass there.
  • User-visible CLI/MCP output: none. The only visible change is the failure note in the CI job summary, which I haven't seen in a real run.
  • Remaining proof gaps: no real registry run and no real timeout reproduction (the tests use a mocked request). I ran the tests locally on Windows only. I didn't run npm run check or npm run verify:test-temp-hygiene, and 23 tests in releaseWorkflow.test.ts are skipped on my machine. I haven't checked whether mcpRegistryPublication.test.ts ran in the CI shards.

Validation performed

  • npx vitest run tests/boundary/filesystem/mcpRegistryPublication.test.ts — 9 passed, exit 0
  • npx vitest run tests/boundary/filesystem/releaseRecovery.test.ts tests/boundary/filesystem/releaseWorkflow.test.ts — 17 passed, 23 skipped, exit 0 (same result without my changes)
  • npx turbo run typecheck lint --force — 2 successful, exit 0
  • npm run test:focused -- <test file> — didn't run: exits 1 on Windows because native/windows/build/manifest.json is missing, before any test starts. I used npx vitest run directly instead.
  • GitHub Actions CI run #12934 on this PR: Static checks, Source tests, Build package, the native package baselines and the Windows capability lane passed. Portable tests failed: Test shard (3/5) has 2 failing tests in tests/boundary/mcp/nativeUiFinalizationMcp.test.ts ("retains native UI reports over MCP when its deadline expires during close", both cleanup variants), where cancelled / cleanup_incomplete was expected and provider_timeout was received. This PR only changes the three files listed above, and nothing in the diff touches native UI finalization code. I did not run that test locally, so I can't say for certain that the failure is unrelated. I can't re-run workflows from my fork.

Compatibility, safety, and release

  • Breaking changes or migration steps: none. The existing error message (Registry lookup failed: HTTP <status>) is unchanged and the new parameter is optional.
  • Real Hopper/Ghidra, browser, or OS coverage: not applicable, I only ran checks on Windows.
  • Package or release metadata impact: none expected.
  • Security, privacy, process, or containment review: only the GET read is retried. Authentication and publish are untouched, and a persistent failure still fails the job before them. Worst case per page is about 110 s (3 x 30 s + 5 s + 15 s).

Author readiness

Human owner: @Rintu62

  • 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/5022 **Author:** [@Rintu62](https://github.com/Rintu62) **Created:** 10/18/2026 **Status:** 🔄 Open **Base:** `main` ← **Head:** `fix/registry-read-hardening` --- ### 📝 Commits (5) - [`f27df51`](https://github.com/morluto/rea/commit/f27df51f323a07fb00d88895a9e2b5438a48d488) fix(publish-mcp): retry and classify registry read failures - [`fb8419a`](https://github.com/morluto/rea/commit/fb8419a4da7b4e2cc09909dcd4118a78838b4000) Merge remote-tracking branch 'upstream/main' into fix/registry-read-hardening - [`b806d3e`](https://github.com/morluto/rea/commit/b806d3e689a062eb2f81c6eb94646b5eadb99fe0) fix(publish-mcp): cancel failed response bodies and keep summary best-effort - [`917569f`](https://github.com/morluto/rea/commit/917569fd04b2cd68af9a66b21de6193f14d8aa49) test(publish-mcp): use the shared temp directory helper - [`9c7b2ea`](https://github.com/morluto/rea/commit/9c7b2ea971b955da4419f0c17e4e38c3af251367) Merge remote-tracking branch 'upstream/main' into fix/registry-read-hardening ### 📊 Changes **3 files changed** (+227 additions, -10 deletions) <details> <summary>View changed files</summary> 📝 `.github/actions/publish-mcp/registry-state.d.mts` (+14 -0) 📝 `.github/actions/publish-mcp/registry-state.mjs` (+76 -9) 📝 `tests/boundary/filesystem/mcpRegistryPublication.test.ts` (+137 -1) </details> ### 📄 Description ## Summary Fixes #4998. Before publishing, the workflow checks whether this version already exists in the MCP Registry. That check (`registry-state.mjs`) gave up on the first timeout, so one slow response blocked the whole publish. It now retries twice for temporary failures. If it still fails, the job fails exactly like before, and the failure type is written to the job summary. ## Problem and expected behavior In #4998 the registry's `/v0.1/ping` returned 200, but the listing request timed out after 30 s and the job stopped before authentication. A short blip shouldn't be enough to stop a release, and the job output should say whether it was a timeout, a 5xx or a 404. The safety rule stays the same: if the lookup can't finish, the result is unknown and the job fails. A failed read is never treated as "not published". ## Change and scope - Added a small `readPage` helper around the existing request and JSON parse. It retries twice (waits 5 s, then 15 s) on timeouts, network errors and 5xx. It does not retry 404 or other 4xx. - Before a retry, the failed response body is cancelled so the connection is not left busy. - If the last retry fails, the original error is thrown again, so `registryPublicationState` can't return `"absent"` unless every page was read. - Added `classifyReadFailure`. When the script runs as the action step, a failure writes the kind (`timeout`, `network_error`, `server_error`, `not_found`, `http_error`, `other`) to `GITHUB_STEP_SUMMARY` and then rethrows. Writing the summary is best effort: if that write fails, the original registry error is still the one that is thrown. - `registryPublicationState` takes an optional third argument (`retryDelaysMs`, `sleep`) so tests don't wait for real delays. Types are updated in `registry-state.d.mts`. I didn't change `action.yml`, authentication, the publish step, the 30 s timeout or the metadata comparison. This doesn't fix the registry problem itself, it only makes the job handle it better. This is a routine fix inside existing boundaries, so a maintainer scope decision doesn't apply. See the [contribution scope](https://github.com/morluto/rea/blob/main/CONTRIBUTING.md#contribution-scope). ## Contract and boundary impact - Semantic owner and earliest changed stage: `.github/actions/publish-mcp/registry-state.mjs`, the version lookup before authentication. - Contribution scope fit and linked maintainer decision: routine fix, not applicable. - CLI and MCP/tool-catalog contract: none, this is a release workflow helper. - Provider, bridge, target-format, or platform compatibility: none. - Evidence, artifact, provenance, or reconstruction contract: not applicable. - Target selection, authority, upstream behavior, and cleanup details: not applicable, no target is touched. It only reads the public registry listing. - Generated metadata, package, or installation impact: none, no generated files changed. Expected effects: - [x] Read existing files or captured data. - [ ] Launch or attach to a process. - [ ] Inject instrumentation or run scripts/code. - [x] Change process memory, registers, files, or configuration. - [x] 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 script reads `server.json` as before. The network call is the existing registry GET, now retried. On failure it appends a short note to the `GITHUB_STEP_SUMMARY` file. ## Evidence and regression coverage - Tests added or updated: 6 new tests in `tests/boundary/filesystem/mcpRegistryPublication.test.ts` (retry then success with delays 5000 and 15000, all attempts time out and the error is rethrown after 3 calls, no retry on 404, failure classification, failed response body is cancelled before the retry, original error is kept when the job summary can't be written). The last one runs the script in a temp directory from `createTestTempDirectory`. The existing 503 test now passes `{ sleep: noSleep }` so it doesn't wait for real delays. - Base reproduction or other evidence: I didn't run the new tests against the base revision. Reading the base code, it makes one request per page and throws on the first failure, so the retry tests would not pass there. - User-visible CLI/MCP output: none. The only visible change is the failure note in the CI job summary, which I haven't seen in a real run. - Remaining proof gaps: no real registry run and no real timeout reproduction (the tests use a mocked `request`). I ran the tests locally on Windows only. I didn't run `npm run check` or `npm run verify:test-temp-hygiene`, and 23 tests in `releaseWorkflow.test.ts` are skipped on my machine. I haven't checked whether `mcpRegistryPublication.test.ts` ran in the CI shards. ## Validation performed - `npx vitest run tests/boundary/filesystem/mcpRegistryPublication.test.ts` — 9 passed, exit 0 - `npx vitest run tests/boundary/filesystem/releaseRecovery.test.ts tests/boundary/filesystem/releaseWorkflow.test.ts` — 17 passed, 23 skipped, exit 0 (same result without my changes) - `npx turbo run typecheck lint --force` — 2 successful, exit 0 - `npm run test:focused -- <test file>` — didn't run: exits 1 on Windows because `native/windows/build/manifest.json` is missing, before any test starts. I used `npx vitest run` directly instead. - GitHub Actions CI run #12934 on this PR: Static checks, Source tests, Build package, the native package baselines and the Windows capability lane passed. Portable tests failed: `Test shard (3/5)` has 2 failing tests in `tests/boundary/mcp/nativeUiFinalizationMcp.test.ts` ("retains native UI reports over MCP when its deadline expires during close", both cleanup variants), where `cancelled` / `cleanup_incomplete` was expected and `provider_timeout` was received. This PR only changes the three files listed above, and nothing in the diff touches native UI finalization code. I did not run that test locally, so I can't say for certain that the failure is unrelated. I can't re-run workflows from my fork. ## Compatibility, safety, and release - Breaking changes or migration steps: none. The existing error message (`Registry lookup failed: HTTP <status>`) is unchanged and the new parameter is optional. - Real Hopper/Ghidra, browser, or OS coverage: not applicable, I only ran checks on Windows. - Package or release metadata impact: none expected. - Security, privacy, process, or containment review: only the GET read is retried. Authentication and publish are untouched, and a persistent failure still fails the job before them. Worst case per page is about 110 s (3 x 30 s + 5 s + 15 s). ## Author readiness Human owner: @Rintu62 - [ ] 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. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
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#6740
No description provided.