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 #3159] [MERGED] fix(captures): admit schema-valid HAR numbers that evidence cannot publish exactly #5647

New issue
Closed
opened 2026-10-31 01:08:15 +00:00 by bsakaguchi · 0 comments
bsakaguchi commented 2026-10-31 01:08:15 +00:00
Owner
Copy link

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/3159
Author: @pablodiazjorge
Created: 10/14/2026
Status: ✅ Merged
Merged: 10/15/2026
Merged by: @baron

Base: main ← Head: fix/har-numeric-admission

📝 Commits (2)

  • 7fa4c40 fix(captures): admit schema-valid HAR numbers that evidence cannot publish exactly
  • c68d96c fix(captures): judge overflowing HAR integers by their lexeme

📊 Changes

2 files changed (+107 additions, -17 deletions)

View changed files

📝 src/browser/history/HarCapture.test.ts (+70 -7)
📝 src/browser/history/HarCapture.ts (+37 -10)

📄 Description

Summary

Fixes #3145. inspect-web-network-capture rejected a schema-valid HAR 1.2 capture when a numeric field could not be projected exactly as a JavaScript number, such as "time": 0.123456789012345678901 or "bodySize": 9007199254740993. The pinned HAR schema admits both. The validation copy reused the evidence projection, which publishes such numbers as null, so AJV saw null where the schema expects a number.

Problem and expected behavior

Smallest trigger: replace "time":1.25 with "time":0.123456789012345678901 in the historicalHar() fixture and run rea inspect-web-network-capture <file> har --json. Before this change: exit 1, invalid_format at /log/entries/0/time, HAR schema validation failed: type (must be number). Expected, as the issue states: admit the capture under the unchanged pinned schema, keep the exact producer lexeme in numeric_literals, and keep the unrepresentable published value explicitly unknown.

Change and scope

  • src/browser/history/HarCapture.ts: the validation copy (projectHar(..., false)) now carries each JSON number as its nearest double, and the evidence projection is unchanged: the lexeme stays in numeric_literals and the published value stays null when it is not exactly representable. When rounding or overflow erases a fractional part (for example 9007199254740993.5, 1e-400, or a fraction too large for a double, which becomes Infinity), the copy carries a non-integer instead, so the schema's integer type is judged by the lexeme and not by the double. The number branch moved into a small projectNumber helper inside projectHar, which keeps the visitor under the complexity limit.
  • src/browser/history/HarCapture.test.ts: the second half of keeps unsafe extension numeric lexemes and rejects unsafe mandatory schema numbers (from #992) asserted the rejection this issue reports; it now asserts that a mandatory bodySize of 9007199254740993 is admitted with its lexeme retained and null published. New cases cover a high-precision time and 1e400, and five non-integer lexemes in an integer field that rounding or overflow would turn into integers, which are still rejected.

Not included: the other capture formats. qlog validates its own frames and does not go through this projection. The numeric redaction proposed in #2872 is already on main (CaptureRedaction.number, through f6905719c); this change leaves it as it is and only changes what the validation copy carries.

Contribution scope: not applicable (input admission within an existing decoder).

Contract and boundary impact

  • Semantic owner and earliest changed stage: the HAR decoder's schema validation copy.
  • Contribution scope fit and linked maintainer decision: not applicable.
  • CLI and MCP/tool-catalog contract: no schema change; valid HAR captures that were refused with invalid_format are now admitted.
  • Provider, bridge, target-format, or platform compatibility: HAR only; no platform-specific code.
  • Evidence, artifact, provenance, or reconstruction contract: unchanged; unrepresentable numbers keep their exact lexeme in numeric_literals and null in reported.
  • Target selection, authority, upstream behavior, and cleanup details (if applicable): none.
  • Generated metadata (docs/public/product-catalog.json), package, or installation impact: none.

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.

Evidence and regression coverage

  • Tests added or updated: src/browser/history/HarCapture.test.ts (one updated, eight new cases).
  • Base reproduction or other evidence: on 767fe0f0c without the change, the compiled CLI refuses the time case with type (must be number) at /log/entries/0/time and the bodySize case with type (must be integer) at /log/entries/0/response/bodySize, both with exit 1, as in the issue. The updated and new admission tests fail there for the same reason.
  • User-visible CLI/MCP output (if applicable): with the change, both cases exit 0; the record keeps {"pointer":"/time","producer_type":"json-number","literal":"0.123456789012345678901"} and reports "time": null; bodySize of 9007199254740993.5 still fails with invalid_format, HAR schema validation failed: type (must be integer).
  • Remaining proof gaps: macOS and Linux not run locally; the change has no platform-specific code.

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

Windows 11 x64 (10.0.26300), Node 24.18.0, npm 11.16.0, branch based on 767fe0f0c, Windows native addon built from that commit.

  • npx vitest run src/browser/history/HarCapture.test.ts — 53 passed.
  • npx vitest run on the 20 test files that reference HAR capture decoding (unit, boundary, CLI, MCP, acceptance and conformance) — 307 passed, 9 skipped.
  • npm run build:cached, then node scripts/rea.mjs inspect-web-network-capture <file> har --json on the unchanged fixture, the high-precision time, the unsafe bodySize, the non-integer bodySize and an overflowing fractional bodySize — exit 0, 0, 0, 1 and 1 (the last two with type (must be integer)); the same files on 767fe0f0c without the change — exit 1 for time and the unsafe bodySize.
  • A standalone check of the validation number against the pinned AJV 8.20.0 for 19 lexemes (including 1.0, 100e-2, -0, 1e400, 1.5e400, 1e-400, 9007199254740993.5 and a 310-digit fraction) — every number/integer result matches JSON Schema draft-06.
  • npm run check:fast — passed.
  • npx tsc --noEmit — passed.
  • npx oxfmt --check and npx oxlint on the two files — passed; no new lint warnings.

Compatibility, safety, and release

  • Breaking changes or migration steps: none; captures that were refused are now admitted, and every evidence field keeps its meaning.
  • Real Hopper/Ghidra, browser, or OS coverage: native Windows with the compiled CLI; no provider involved.
  • Package or release metadata impact: none.
  • Security, privacy, process, or containment review: the validation copy is internal and never published; redaction runs only in the evidence projection, as before.

Author readiness

Human owner: @pablodiazjorge

  • 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/3159 **Author:** [@pablodiazjorge](https://github.com/pablodiazjorge) **Created:** 10/14/2026 **Status:** ✅ Merged **Merged:** 10/15/2026 **Merged by:** [@baron](https://github.com/baron) **Base:** `main` ← **Head:** `fix/har-numeric-admission` --- ### 📝 Commits (2) - [`7fa4c40`](https://github.com/morluto/rea/commit/7fa4c40d487280ec69f18b3c3afd18a951df5737) fix(captures): admit schema-valid HAR numbers that evidence cannot publish exactly - [`c68d96c`](https://github.com/morluto/rea/commit/c68d96c94fd24a0dd6d0cff6cdacb3be626309fa) fix(captures): judge overflowing HAR integers by their lexeme ### 📊 Changes **2 files changed** (+107 additions, -17 deletions) <details> <summary>View changed files</summary> 📝 `src/browser/history/HarCapture.test.ts` (+70 -7) 📝 `src/browser/history/HarCapture.ts` (+37 -10) </details> ### 📄 Description ## Summary Fixes #3145. `inspect-web-network-capture` rejected a schema-valid HAR 1.2 capture when a numeric field could not be projected exactly as a JavaScript number, such as `"time": 0.123456789012345678901` or `"bodySize": 9007199254740993`. The pinned HAR schema admits both. The validation copy reused the evidence projection, which publishes such numbers as `null`, so AJV saw `null` where the schema expects a number. ## Problem and expected behavior Smallest trigger: replace `"time":1.25` with `"time":0.123456789012345678901` in the `historicalHar()` fixture and run `rea inspect-web-network-capture <file> har --json`. Before this change: exit 1, `invalid_format` at `/log/entries/0/time`, `HAR schema validation failed: type (must be number).` Expected, as the issue states: admit the capture under the unchanged pinned schema, keep the exact producer lexeme in `numeric_literals`, and keep the unrepresentable published value explicitly unknown. ## Change and scope - `src/browser/history/HarCapture.ts`: the validation copy (`projectHar(..., false)`) now carries each JSON number as its nearest double, and the evidence projection is unchanged: the lexeme stays in `numeric_literals` and the published value stays `null` when it is not exactly representable. When rounding or overflow erases a fractional part (for example `9007199254740993.5`, `1e-400`, or a fraction too large for a double, which becomes `Infinity`), the copy carries a non-integer instead, so the schema's `integer` type is judged by the lexeme and not by the double. The number branch moved into a small `projectNumber` helper inside `projectHar`, which keeps the visitor under the complexity limit. - `src/browser/history/HarCapture.test.ts`: the second half of `keeps unsafe extension numeric lexemes and rejects unsafe mandatory schema numbers` (from #992) asserted the rejection this issue reports; it now asserts that a mandatory `bodySize` of `9007199254740993` is admitted with its lexeme retained and `null` published. New cases cover a high-precision `time` and `1e400`, and five non-integer lexemes in an integer field that rounding or overflow would turn into integers, which are still rejected. Not included: the other capture formats. qlog validates its own frames and does not go through this projection. The numeric redaction proposed in #2872 is already on `main` (`CaptureRedaction.number`, through `f6905719c`); this change leaves it as it is and only changes what the validation copy carries. Contribution scope: not applicable (input admission within an existing decoder). ## Contract and boundary impact - Semantic owner and earliest changed stage: the HAR decoder's schema validation copy. - Contribution scope fit and linked maintainer decision: not applicable. - CLI and MCP/tool-catalog contract: no schema change; valid HAR captures that were refused with `invalid_format` are now admitted. - Provider, bridge, target-format, or platform compatibility: HAR only; no platform-specific code. - Evidence, artifact, provenance, or reconstruction contract: unchanged; unrepresentable numbers keep their exact lexeme in `numeric_literals` and `null` in `reported`. - Target selection, authority, upstream behavior, and cleanup details (if applicable): none. - Generated metadata (`docs/public/product-catalog.json`), package, or installation impact: none. Expected effects: - [x] Read existing files or captured data. - [ ] Launch or attach to a process. - [ ] Inject instrumentation or run scripts/code. - [ ] Change process memory, registers, files, or configuration. - [ ] Contact network services. - [ ] Recover protected code or work around protections. - [ ] Documentation or usability only; no target interaction. - [ ] Not sure yet; investigation or maintainer guidance needed. ## Evidence and regression coverage - Tests added or updated: `src/browser/history/HarCapture.test.ts` (one updated, eight new cases). - Base reproduction or other evidence: on `767fe0f0c` without the change, the compiled CLI refuses the `time` case with `type (must be number)` at `/log/entries/0/time` and the `bodySize` case with `type (must be integer)` at `/log/entries/0/response/bodySize`, both with exit 1, as in the issue. The updated and new admission tests fail there for the same reason. - User-visible CLI/MCP output (if applicable): with the change, both cases exit 0; the record keeps `{"pointer":"/time","producer_type":"json-number","literal":"0.123456789012345678901"}` and reports `"time": null`; `bodySize` of `9007199254740993.5` still fails with `invalid_format`, `HAR schema validation failed: type (must be integer).` - Remaining proof gaps: macOS and Linux not run locally; the change has no platform-specific code. 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 Windows 11 x64 (10.0.26300), Node 24.18.0, npm 11.16.0, branch based on `767fe0f0c`, Windows native addon built from that commit. - `npx vitest run src/browser/history/HarCapture.test.ts` — 53 passed. - `npx vitest run` on the 20 test files that reference HAR capture decoding (unit, boundary, CLI, MCP, acceptance and conformance) — 307 passed, 9 skipped. - `npm run build:cached`, then `node scripts/rea.mjs inspect-web-network-capture <file> har --json` on the unchanged fixture, the high-precision `time`, the unsafe `bodySize`, the non-integer `bodySize` and an overflowing fractional `bodySize` — exit 0, 0, 0, 1 and 1 (the last two with `type (must be integer)`); the same files on `767fe0f0c` without the change — exit 1 for `time` and the unsafe `bodySize`. - A standalone check of the validation number against the pinned AJV 8.20.0 for 19 lexemes (including `1.0`, `100e-2`, `-0`, `1e400`, `1.5e400`, `1e-400`, `9007199254740993.5` and a 310-digit fraction) — every `number`/`integer` result matches JSON Schema draft-06. - `npm run check:fast` — passed. - `npx tsc --noEmit` — passed. - `npx oxfmt --check` and `npx oxlint` on the two files — passed; no new lint warnings. ## Compatibility, safety, and release - Breaking changes or migration steps: none; captures that were refused are now admitted, and every evidence field keeps its meaning. - Real Hopper/Ghidra, browser, or OS coverage: native Windows with the compiled CLI; no provider involved. - Package or release metadata impact: none. - Security, privacy, process, or containment review: the validation copy is internal and never published; redaction runs only in the evidence projection, as before. ## Author readiness Human owner: @pablodiazjorge - [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. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
bsakaguchi 2026-10-31 01:08:15 +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#5647
No description provided.