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 #4839] [MERGED] fix(plist): keep negative-zero reals distinct from positive zero #6437

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

📋 Pull Request Information

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

Base: main ← Head: fix/plist-negative-zero-real

📝 Commits (2)

  • d16dfaf fix(plist): keep negative-zero reals distinct from positive zero
  • e3292a6 Merge upstream main into fix/plist-negative-zero-real

📊 Changes

10 files changed (+218 additions, -10 deletions)

View changed files

📝 docs/native-investigation.md (+6 -0)
📝 src/artifacts/apple/KeyedArchiveReader.ts (+13 -5)
📝 src/domain/apple/keyedArchive.ts (+1 -0)
📝 src/domain/apple/plistValue.test.ts (+23 -0)
📝 src/domain/apple/plistValue.ts (+26 -2)
📝 src/domain/propertyListXml.test.ts (+15 -0)
📝 src/domain/propertyListXml.ts (+3 -1)
📝 src/native/parsers/plist.test.ts (+25 -0)
📝 src/native/parsers/plist.ts (+19 -2)
📝 tests/acceptance/applications/keyedArchiveScalarKinds.test.ts (+87 -0)

📄 Description

Summary

Fixes #4834. Plist inspection reported a serialized negative-zero real as the JSON number 0 with status observed, the same as positive zero, and no limitation disclosed the lost sign. The shared plist projection now reports it as { "$plist_type": "real", "value": "-0" } with a counted limitation; positive zero and integer zero stay 0.

Thanks to @xu91102 for the precise report and for locating the projection boundary.

Problem and expected behavior

projectPlistValue passed finite numbers through unchanged. A -0 decoded from <real>-0.0</real>, or from a binary float64 0x8000000000000000, reached JSON serialization, which writes 0. A serialized IEEE value must not be reported as a different observed value.

Change and scope

  • projectPlistValue, which owns the JSON-safe plist scalar representation, wraps -0 as { "$plist_type": "real", "value": "-0" }, reports it through the existing generated-wrapper callback (so keyed archive objects stay scalar, and a lookalike dictionary stays dictionary), and counts it. The spelling follows the existing { "$plist_type": "real", "value": null } unknown real and the "-0" that SQLite inspection already uses for reals.
  • inspect_keyed_archive and the inspect_plist XML fallback add the count as a limitation through one shared helper. Interface Builder node attributes get the same value from the shared projection; as with non-finite reals there, no separate limitation.
  • The inspect_plist JSON path never runs the shared projection, so its JSON reviver applies the same wrapper and limitation when plutil JSON holds -0. A plist integer has no signed zero.
  • The XML decoder's fallback for mixed integer content (Number.parseInt) returned -0 for <integer>-0<!-- c --></integer>; it now returns 0, so the projection's rule that -0 is a real holds for every decoder. Exact integer literals already decode through BigInt, which has no signed zero.
  • Behavior note: a negative-zero real in a CF$UID position is a real, not a UID. Like a non-finite real there, it is now projected as a typed value inside an ordinary dictionary rather than read as a reference to object 0.
  • Scope: an ordinary fix within the existing read-only plist boundary; a maintainer scope decision is not applicable.

Contract and boundary impact

  • Semantic owner and earliest changed stage: projectPlistValue in src/domain/apple/plistValue.ts, before consumers classify the JSON tree; the plutil JSON decode boundary in src/native/parsers/plist.ts.
  • Contribution scope fit and linked maintainer decision: existing boundary; not applicable.
  • CLI and MCP/tool-catalog contract: only negative-zero real values change, from the number 0 to the typed object above, with one new limitation line. Result schemas already carry JSON values; no catalog change.
  • Provider, bridge, target-format, or platform compatibility: none; decoding only.
  • Evidence, artifact, provenance, or reconstruction contract: reported values now match the serialized bytes; archive digests and input files are unchanged.
  • Target selection, authority, upstream behavior, and cleanup details: not applicable.
  • Generated metadata, 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:
    • tests/acceptance/applications/keyedArchiveScalarKinds.test.ts: XML and binary keyed archives with -0.0, 0.0 and 1.25 reals through the public CLI and MCP (equal results), checking the wrapper, scalar/observed, positive zero, the serialized JSON and the limitation.
    • src/domain/apple/plistValue.test.ts: projection and count; only the generated wrapper reaches the callback.
    • src/native/parsers/plist.test.ts: the inspect_plist JSON and XML parsers with -0.0, -0, 0.0, <integer>-0</integer> and 1.25; no limitation for positive zero.
    • src/domain/propertyListXml.test.ts: a signed integer zero, exact or with mixed content, decodes as 0; the real keeps its sign.
  • Base reproduction: the same tests on unpatched main 63c65a224: both new acceptance cases and the new projection, parser and XML decoder tests fail (the existing date test also fails there, only because of the new count field). All pass with the change.
  • User-visible CLI output: the issue's XML fixture through the compiled source CLI, inspect-keyed-archive <file> --json, object 1:
    • before: {"id":1,"kind":"scalar","status":"observed","value":0} (other fields omitted), no limitation;
    • after: "value":{"$plist_type":"real","value":"-0"}, kind scalar, status observed, plus 1 negative-zero real value(s) are reported as { "$plist_type": "real", "value": "-0" } because a JSON number cannot carry the sign of zero.
    • The binary form of the same archive gives the same results; the 0.0 and 1.25 controls are unchanged before and after.
  • Remaining proof gaps:
    • The macOS plutil path of inspect_plist was not run (no macOS host); its darwin-only CLI tests skip here. Whether plutil -convert json writes -0 for a negative-zero real is unverified, so the JSON parser is covered with literal JSON input.
    • No Foundation-generated archive (that needs macOS); the binary fixtures are plist@5 output with a patched float64.
    • Interface Builder was not exercised with a negative-zero attribute.
    • npm run docs:check was not run; it needs the built runtime, which build:cached cannot produce on this host without the 6.5.0 Windows native artifact.

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 Pro 10.0.26300, Node 24.18.0, on main 63c65a224:

  • npx vitest run src/domain/apple/plistValue.test.ts src/domain/propertyListXml.test.ts src/native/parsers/plist.test.ts tests/acceptance/applications/keyedArchiveScalarKinds.test.ts: 4 files, 37 tests passed.
  • npx vitest run on the 40 tracked files matching src/domain/apple/*.test.ts, src/artifacts/apple/*.test.ts, src/domain/propertyList*.test.ts, src/native/parsers/plist*.test.ts, tests/boundary/filesystem/keyedArchive*.test.ts, tests/boundary/filesystem/nativeArtifactGoldens.test.ts, tests/acceptance/applications/keyedArchive*.test.ts, tests/**/*nterfaceBuilder*.test.ts and tests/**/*[Pp]list*.test.ts: 489 passed, 52 skipped (macOS-only), 2 failed. Both failures are AppleAssetCatalogAnalysis.test.ts cases that cannot create symlinks on Windows without developer mode (EPERM); they fail the same way on unpatched main.
  • npm run check:fast: typecheck and lint pass.
  • npx oxfmt --check on the changed files: pass.
  • npm run compile, then the CLI runs above with and without the change. npm run build:cached needs the 6.5.0 Windows native artifact, which this host does not have.

Compatibility, safety, and release

  • Breaking changes or migration steps: none intended. A consumer reading these values as numbers sees a typed object only for negative-zero reals, as it already does for non-finite reals.
  • Real Hopper/Ghidra, browser, or OS coverage: not applicable to the change; Windows only, the macOS plutil path was not run.
  • Package or release metadata impact: none.
  • Security, privacy, process, or containment review: none; read-only decoding of caller-selected files.

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/4839 **Author:** [@pablodiazjorge](https://github.com/pablodiazjorge) **Created:** 10/17/2026 **Status:** ✅ Merged **Merged:** 10/17/2026 **Merged by:** [@morluto](https://github.com/morluto) **Base:** `main` ← **Head:** `fix/plist-negative-zero-real` --- ### 📝 Commits (2) - [`d16dfaf`](https://github.com/morluto/rea/commit/d16dfaff7347fb132b9fcff5df271a77bd8c65b2) fix(plist): keep negative-zero reals distinct from positive zero - [`e3292a6`](https://github.com/morluto/rea/commit/e3292a68c79ce4f3510a0f23519d7dd6da2033c7) Merge upstream main into fix/plist-negative-zero-real ### 📊 Changes **10 files changed** (+218 additions, -10 deletions) <details> <summary>View changed files</summary> 📝 `docs/native-investigation.md` (+6 -0) 📝 `src/artifacts/apple/KeyedArchiveReader.ts` (+13 -5) 📝 `src/domain/apple/keyedArchive.ts` (+1 -0) 📝 `src/domain/apple/plistValue.test.ts` (+23 -0) 📝 `src/domain/apple/plistValue.ts` (+26 -2) 📝 `src/domain/propertyListXml.test.ts` (+15 -0) 📝 `src/domain/propertyListXml.ts` (+3 -1) 📝 `src/native/parsers/plist.test.ts` (+25 -0) 📝 `src/native/parsers/plist.ts` (+19 -2) 📝 `tests/acceptance/applications/keyedArchiveScalarKinds.test.ts` (+87 -0) </details> ### 📄 Description ## Summary Fixes #4834. Plist inspection reported a serialized negative-zero real as the JSON number `0` with status `observed`, the same as positive zero, and no limitation disclosed the lost sign. The shared plist projection now reports it as `{ "$plist_type": "real", "value": "-0" }` with a counted limitation; positive zero and integer zero stay `0`. Thanks to @xu91102 for the precise report and for locating the projection boundary. ## Problem and expected behavior `projectPlistValue` passed finite numbers through unchanged. A `-0` decoded from `<real>-0.0</real>`, or from a binary float64 `0x8000000000000000`, reached JSON serialization, which writes `0`. A serialized IEEE value must not be reported as a different observed value. ## Change and scope - `projectPlistValue`, which owns the JSON-safe plist scalar representation, wraps `-0` as `{ "$plist_type": "real", "value": "-0" }`, reports it through the existing generated-wrapper callback (so keyed archive objects stay `scalar`, and a lookalike dictionary stays `dictionary`), and counts it. The spelling follows the existing `{ "$plist_type": "real", "value": null }` unknown real and the `"-0"` that SQLite inspection already uses for reals. - `inspect_keyed_archive` and the `inspect_plist` XML fallback add the count as a limitation through one shared helper. Interface Builder node attributes get the same value from the shared projection; as with non-finite reals there, no separate limitation. - The `inspect_plist` JSON path never runs the shared projection, so its JSON reviver applies the same wrapper and limitation when plutil JSON holds `-0`. A plist integer has no signed zero. - The XML decoder's fallback for mixed integer content (`Number.parseInt`) returned `-0` for `<integer>-0<!-- c --></integer>`; it now returns `0`, so the projection's rule that `-0` is a real holds for every decoder. Exact integer literals already decode through BigInt, which has no signed zero. - Behavior note: a negative-zero real in a `CF$UID` position is a real, not a UID. Like a non-finite real there, it is now projected as a typed value inside an ordinary dictionary rather than read as a reference to object 0. - Scope: an ordinary fix within the existing read-only plist boundary; a maintainer scope decision is not applicable. ## Contract and boundary impact - Semantic owner and earliest changed stage: `projectPlistValue` in `src/domain/apple/plistValue.ts`, before consumers classify the JSON tree; the plutil JSON decode boundary in `src/native/parsers/plist.ts`. - Contribution scope fit and linked maintainer decision: existing boundary; not applicable. - CLI and MCP/tool-catalog contract: only negative-zero real values change, from the number `0` to the typed object above, with one new limitation line. Result schemas already carry JSON values; no catalog change. - Provider, bridge, target-format, or platform compatibility: none; decoding only. - Evidence, artifact, provenance, or reconstruction contract: reported values now match the serialized bytes; archive digests and input files are unchanged. - Target selection, authority, upstream behavior, and cleanup details: not applicable. - Generated metadata, 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: - `tests/acceptance/applications/keyedArchiveScalarKinds.test.ts`: XML and binary keyed archives with `-0.0`, `0.0` and `1.25` reals through the public CLI and MCP (equal results), checking the wrapper, `scalar`/`observed`, positive zero, the serialized JSON and the limitation. - `src/domain/apple/plistValue.test.ts`: projection and count; only the generated wrapper reaches the callback. - `src/native/parsers/plist.test.ts`: the `inspect_plist` JSON and XML parsers with `-0.0`, `-0`, `0.0`, `<integer>-0</integer>` and `1.25`; no limitation for positive zero. - `src/domain/propertyListXml.test.ts`: a signed integer zero, exact or with mixed content, decodes as `0`; the real keeps its sign. - Base reproduction: the same tests on unpatched main `63c65a224`: both new acceptance cases and the new projection, parser and XML decoder tests fail (the existing date test also fails there, only because of the new count field). All pass with the change. - User-visible CLI output: the issue's XML fixture through the compiled source CLI, `inspect-keyed-archive <file> --json`, object 1: - before: `{"id":1,"kind":"scalar","status":"observed","value":0}` (other fields omitted), no limitation; - after: `"value":{"$plist_type":"real","value":"-0"}`, `kind` `scalar`, `status` `observed`, plus `1 negative-zero real value(s) are reported as { "$plist_type": "real", "value": "-0" } because a JSON number cannot carry the sign of zero.` - The binary form of the same archive gives the same results; the `0.0` and `1.25` controls are unchanged before and after. - Remaining proof gaps: - The macOS `plutil` path of `inspect_plist` was not run (no macOS host); its darwin-only CLI tests skip here. Whether `plutil -convert json` writes `-0` for a negative-zero real is unverified, so the JSON parser is covered with literal JSON input. - No Foundation-generated archive (that needs macOS); the binary fixtures are plist@5 output with a patched float64. - Interface Builder was not exercised with a negative-zero attribute. - `npm run docs:check` was not run; it needs the built runtime, which `build:cached` cannot produce on this host without the 6.5.0 Windows native artifact. 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 Pro 10.0.26300, Node 24.18.0, on main `63c65a224`: - `npx vitest run src/domain/apple/plistValue.test.ts src/domain/propertyListXml.test.ts src/native/parsers/plist.test.ts tests/acceptance/applications/keyedArchiveScalarKinds.test.ts`: 4 files, 37 tests passed. - `npx vitest run` on the 40 tracked files matching `src/domain/apple/*.test.ts`, `src/artifacts/apple/*.test.ts`, `src/domain/propertyList*.test.ts`, `src/native/parsers/plist*.test.ts`, `tests/boundary/filesystem/keyedArchive*.test.ts`, `tests/boundary/filesystem/nativeArtifactGoldens.test.ts`, `tests/acceptance/applications/keyedArchive*.test.ts`, `tests/**/*nterfaceBuilder*.test.ts` and `tests/**/*[Pp]list*.test.ts`: 489 passed, 52 skipped (macOS-only), 2 failed. Both failures are `AppleAssetCatalogAnalysis.test.ts` cases that cannot create symlinks on Windows without developer mode (`EPERM`); they fail the same way on unpatched main. - `npm run check:fast`: typecheck and lint pass. - `npx oxfmt --check` on the changed files: pass. - `npm run compile`, then the CLI runs above with and without the change. `npm run build:cached` needs the 6.5.0 Windows native artifact, which this host does not have. ## Compatibility, safety, and release - Breaking changes or migration steps: none intended. A consumer reading these values as numbers sees a typed object only for negative-zero reals, as it already does for non-finite reals. - Real Hopper/Ghidra, browser, or OS coverage: not applicable to the change; Windows only, the macOS `plutil` path was not run. - Package or release metadata impact: none. - Security, privacy, process, or containment review: none; read-only decoding of caller-selected files. ## 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:14:27 +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#6437
No description provided.