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 #4572] fix(reference): keep the raw query and fragment on unresolved ESM paths #6314

New issue
Open
opened 2026-10-31 01:13:30 +00:00 by bsakaguchi · 0 comments
bsakaguchi commented 2026-10-31 01:13:30 +00:00
Owner
Copy link

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/4572
Author: @Ganesh2325
Created: 10/16/2026
Status: 🔄 Open

Base: main ← Head: fix/esm-import-url-suffix

📝 Commits (10+)

  • fab189f fix(reference): resolve query and fragment ESM imports to their pathname
  • 557fac3 Merge remote-tracking branch 'upstream/main' into fix/esm-import-url-suffix
  • f30475e fix(reference): interpret ESM URL components before inventory lookup
  • 4fda585 Merge remote-tracking branch 'upstream/main' into fix/esm-import-url-suffix
  • 21ba350 test(reference): leave encoded backslash ESM pathnames unresolved
  • adf85a7 Merge remote-tracking branch 'upstream/main' into fix/esm-import-url-suffix
  • cf394be refactor(reference): parse ESM specifiers once in importLookupPath
  • 5f5812c Merge remote-tracking branch 'upstream/main' into fix/esm-import-url-suffix
  • 0c42328 fix(reference): keep query and fragment text in unresolved ESM paths
  • 9d5fce1 Merge remote-tracking branch 'upstream/main' into fix/esm-import-url-suffix

📊 Changes

2 files changed (+125 additions, -6 deletions)

View changed files

📝 src/application/ReferenceSourceImportEntries.test.ts (+97 -0)
📝 src/application/ReferenceSourceImportEntries.ts (+28 -6)

📄 Description

Summary

Follows up #3916

Main already fixed #3916 in f2e5fd148: a relative ESM import with a query or fragment resolves to its URL pathname, and the declared spelling is kept separately in source_specifier. This PR no longer claims to close #3916. It is narrowed, as requested in the maintainer's review, to one remaining representation choice: the to of an unresolved source-import relationship keeps the raw ?query or #fragment after main's normalized pathname.

Problem and expected behavior

  • Smallest trigger: main.mjs holds import "./missing.mjs?v=1"; and no missing.mjs is inventoried.
  • On main: {"from_path":"main.mjs","to":"missing.mjs","source_specifier":"./missing.mjs?v=1","kind":"imports","resolution":"unresolved"}.
  • With this PR: {"from_path":"main.mjs","to":"missing.mjs?v=1","source_specifier":"./missing.mjs?v=1","kind":"imports","resolution":"unresolved"}.
  • Rationale: an unresolved edge names something the inventory does not contain, so its to stays faithful to what the source requested instead of silently dropping the query or fragment. The pathname part is still main's normalized, root-relative pathname, and source_specifier is unchanged.
  • Unchanged: resolved imports (./dep.mjs?v=1 still resolves to dep.mjs with resolution: "internal"), rejected escapes such as %2F (main's behavior, the raw specifier as to), the unresolved package-main target, and all CommonJS require paths.

Change and scope

Net diff against main: 2 files, +125/−6. Only src/application/ReferenceSourceImportEntries.ts and its test file change. The branch merged upstream main at 269630f4e (merge commit 9d5fce1dd, no rebase), taking main's resolver and tests, so the merged tree matched main. Commit a7edd1709 then adds only the behavior below.

  • importLookupPath, main's existing ESM parser, now also returns suffix: the raw ?query or #fragment, marker included (L398-L399, L432). The cut is made on the raw specifier at the first ? or # (L403-L406), the same boundary URL.parse uses, rather than read back from URL.search/URL.hash, which can re-encode characters.
  • resolveInternalSpecifier adds a small unresolvedAt helper (L464-L471) that appends that suffix to main's normalized pathname. It replaces main's three { to: normalized, resolution: "unresolved" } returns (L471, L520, L526). The suffix is empty for require lookups and for rejected ESM pathnames, so those to values are exactly main's.
  • Not included: anything about resolving the pathname itself, percent decoding, %5C handling, or source_specifier. Those are main's behavior from f2e5fd148 and are untouched.

Follow the contribution scope.
Unresolved scope, authority, side effects, or required verification block
integration. Link the required maintainer scope decision for new providers or
capabilities involving target execution, injection, mutation, or protection
recovery; ordinary fixes within existing boundaries may state "not applicable".
Draft PRs may leave the scope decision pending and the readiness and merge checklists
unchecked. Maintainers can help resolve open questions.

Contribution scope: an ordinary change within existing boundaries. A maintainer scope decision does not apply. Whether unresolved to should keep the raw suffix is the open representation decision the maintainer asked this PR to isolate.

Contract and boundary impact

  • Semantic owner and earliest changed stage: src/application/ReferenceSourceImportEntries.ts, when an ESM source-import relationship is left unresolved.
  • Contribution scope fit and linked maintainer decision: within the existing reference-source boundary; see the maintainer comment. Not applicable otherwise.
  • CLI and MCP/tool-catalog contract: no schema or flag change. Only the to string of an unresolved ESM relationship whose specifier contains a raw ? or # changes.
  • Provider, bridge, target-format, or platform compatibility: TypeScript-file imports also use source-import mode and get the same unresolved spelling.
  • Evidence, artifact, provenance, or reconstruction contract: an unresolved edge records the normalized pathname plus the raw query or fragment; source_specifier still records the declared spelling. Resolved edges are unchanged.
  • 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: 4 cases in src/application/ReferenceSourceImportEntries.test.ts, which uses main's existing cases unchanged:
  • Base reproduction or other evidence: on main, the same unresolved imports produce to without the suffix (for example missing.mjs for ./missing.mjs?v=1). The resolved control documents main's existing behavior, which this PR keeps.
  • User-visible CLI/MCP output (if applicable): the unresolved relationship becomes {"from_path":"main.mjs","to":"missing.mjs?v=1","source_specifier":"./missing.mjs?v=1","kind":"imports","resolution":"unresolved"}. Captured at the entry-parsing boundary; no end-to-end CLI output is captured.
  • Remaining proof gaps:
    • No MCP or real-provider run.
    • The full suite and check:pr were not run locally; CI on head a7edd17 covers them (see Validation performed).
    • Windows was not checked.

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

Local commands ran on Node 22.23.4 against head a7edd17. Each command exited 0.

  • npx vitest run src/application/ReferenceSourceImportEntries.test.ts: 18 passed.
  • npx vitest run over the reference-source set (src/application/ReferenceSourceImportEntries.test.ts, src/domain/referenceSourcePathIdentity.test.ts, src/application/ReferenceSourceImport, src/domain/referenceSource, src/reference/ReferenceSource, tests/boundary/filesystem/referenceSource, tests/boundary/cli/referenceSource): 42 files passed; 213 tests passed and 2 skipped.
  • npm run lint: 0 errors.
  • npm run typecheck: ok.
  • npm run build: ok.
  • Pre-push check:fast (typecheck and lint): ok.

CI on head a7edd17 (run 40547689573) passed: CI required, Static checks, Build package, Source tests, Portable tests, all eight test shards, Native package baseline (linux x64), Build bundled Windows x64 native controls, Classify changes and Greptile Review succeeded, and Conventional PR title and Validate author declaration passed. Deep static checks, Documentation and the optional capability lanes were skipped as untouched.

Compatibility, safety, and release

  • Breaking changes or migration steps: none to the schema or the CLI. The to of an unresolved ESM relationship with a raw ? or # gains that suffix compared with main. Resolved edges, rejected escapes and require edges are unchanged.
  • Real Hopper/Ghidra, browser, or OS coverage: not applicable to Hopper, Ghidra or browsers. Linux only; Windows was not checked.
  • Package or release metadata impact: none.
  • Security, privacy, process, or containment review: pure string handling over already-read source text. No new filesystem access, process launches or network access. The suffix is only appended to an unresolved to; it never affects inventory lookup or which file an edge targets.

Author readiness

Human owner: @Ganesh2325

  • 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 change was prepared with AI assistance.

🔄 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/4572 **Author:** [@Ganesh2325](https://github.com/Ganesh2325) **Created:** 10/16/2026 **Status:** 🔄 Open **Base:** `main` ← **Head:** `fix/esm-import-url-suffix` --- ### 📝 Commits (10+) - [`fab189f`](https://github.com/morluto/rea/commit/fab189f8b153e600a4e0af5da9e0715238477758) fix(reference): resolve query and fragment ESM imports to their pathname - [`557fac3`](https://github.com/morluto/rea/commit/557fac308b579972b0e77c33cf34c93dddab3e9d) Merge remote-tracking branch 'upstream/main' into fix/esm-import-url-suffix - [`f30475e`](https://github.com/morluto/rea/commit/f30475ed0e73002583960e6ddb6c4f4b19669f31) fix(reference): interpret ESM URL components before inventory lookup - [`4fda585`](https://github.com/morluto/rea/commit/4fda585aa3a7c27f3a6b8236ae417a46308ded21) Merge remote-tracking branch 'upstream/main' into fix/esm-import-url-suffix - [`21ba350`](https://github.com/morluto/rea/commit/21ba350fac57c44ad2b3958d0d73ab605113efef) test(reference): leave encoded backslash ESM pathnames unresolved - [`adf85a7`](https://github.com/morluto/rea/commit/adf85a7ed3290f4c07f7151577ce1430ee399c65) Merge remote-tracking branch 'upstream/main' into fix/esm-import-url-suffix - [`cf394be`](https://github.com/morluto/rea/commit/cf394be39cbdc282e58c87377eb610d31b311f28) refactor(reference): parse ESM specifiers once in importLookupPath - [`5f5812c`](https://github.com/morluto/rea/commit/5f5812cba069ebb06df3b3f2465abce9759c03b8) Merge remote-tracking branch 'upstream/main' into fix/esm-import-url-suffix - [`0c42328`](https://github.com/morluto/rea/commit/0c423282a23c02749f684df712e0bd7185499c11) fix(reference): keep query and fragment text in unresolved ESM paths - [`9d5fce1`](https://github.com/morluto/rea/commit/9d5fce1ddbe06e5d1fa82b48989944fa1193b3ed) Merge remote-tracking branch 'upstream/main' into fix/esm-import-url-suffix ### 📊 Changes **2 files changed** (+125 additions, -6 deletions) <details> <summary>View changed files</summary> 📝 `src/application/ReferenceSourceImportEntries.test.ts` (+97 -0) 📝 `src/application/ReferenceSourceImportEntries.ts` (+28 -6) </details> ### 📄 Description ## Summary Follows up #3916 Main already fixed #3916 in `f2e5fd148`: a relative ESM import with a query or fragment resolves to its URL pathname, and the declared spelling is kept separately in `source_specifier`. This PR no longer claims to close #3916. It is narrowed, as requested in [the maintainer's review](https://github.com/morluto/rea/pull/4572#issuecomment-6427907872), to one remaining representation choice: the `to` of an **unresolved** `source-import` relationship keeps the raw `?query` or `#fragment` after main's normalized pathname. ## Problem and expected behavior - Smallest trigger: `main.mjs` holds `import "./missing.mjs?v=1";` and no `missing.mjs` is inventoried. - On main: `{"from_path":"main.mjs","to":"missing.mjs","source_specifier":"./missing.mjs?v=1","kind":"imports","resolution":"unresolved"}`. - With this PR: `{"from_path":"main.mjs","to":"missing.mjs?v=1","source_specifier":"./missing.mjs?v=1","kind":"imports","resolution":"unresolved"}`. - Rationale: an unresolved edge names something the inventory does not contain, so its `to` stays faithful to what the source requested instead of silently dropping the query or fragment. The pathname part is still main's normalized, root-relative pathname, and `source_specifier` is unchanged. - Unchanged: resolved imports (`./dep.mjs?v=1` still resolves to `dep.mjs` with `resolution: "internal"`), rejected escapes such as `%2F` (main's behavior, the raw specifier as `to`), the unresolved package-main target, and all CommonJS `require` paths. ## Change and scope Net diff against `main`: 2 files, +125/−6. Only `src/application/ReferenceSourceImportEntries.ts` and its test file change. The branch merged upstream `main` at `269630f4e` (merge commit `9d5fce1dd`, no rebase), taking main's resolver and tests, so the merged tree matched `main`. Commit `a7edd1709` then adds only the behavior below. - [`importLookupPath`](https://github.com/morluto/rea/blob/a7edd17093919857af72cf5a0ffbcb97ae75807e/src/application/ReferenceSourceImportEntries.ts#L391-L435), main's existing ESM parser, now also returns `suffix`: the raw `?query` or `#fragment`, marker included ([L398-L399](https://github.com/morluto/rea/blob/a7edd17093919857af72cf5a0ffbcb97ae75807e/src/application/ReferenceSourceImportEntries.ts#L398-L399), [L432](https://github.com/morluto/rea/blob/a7edd17093919857af72cf5a0ffbcb97ae75807e/src/application/ReferenceSourceImportEntries.ts#L432)). The cut is made on the raw specifier at the first `?` or `#` ([L403-L406](https://github.com/morluto/rea/blob/a7edd17093919857af72cf5a0ffbcb97ae75807e/src/application/ReferenceSourceImportEntries.ts#L403-L406)), the same boundary `URL.parse` uses, rather than read back from `URL.search`/`URL.hash`, which can re-encode characters. - [`resolveInternalSpecifier`](https://github.com/morluto/rea/blob/a7edd17093919857af72cf5a0ffbcb97ae75807e/src/application/ReferenceSourceImportEntries.ts#L437-L539) adds a small `unresolvedAt` helper ([L464-L471](https://github.com/morluto/rea/blob/a7edd17093919857af72cf5a0ffbcb97ae75807e/src/application/ReferenceSourceImportEntries.ts#L464-L471)) that appends that suffix to main's normalized pathname. It replaces main's three `{ to: normalized, resolution: "unresolved" }` returns ([L471](https://github.com/morluto/rea/blob/a7edd17093919857af72cf5a0ffbcb97ae75807e/src/application/ReferenceSourceImportEntries.ts#L471), [L520](https://github.com/morluto/rea/blob/a7edd17093919857af72cf5a0ffbcb97ae75807e/src/application/ReferenceSourceImportEntries.ts#L520), [L526](https://github.com/morluto/rea/blob/a7edd17093919857af72cf5a0ffbcb97ae75807e/src/application/ReferenceSourceImportEntries.ts#L526)). The suffix is empty for `require` lookups and for rejected ESM pathnames, so those `to` values are exactly main's. - Not included: anything about resolving the pathname itself, percent decoding, `%5C` handling, or `source_specifier`. Those are main's behavior from `f2e5fd148` and are untouched. Follow the [contribution scope](https://github.com/morluto/rea/blob/main/CONTRIBUTING.md#contribution-scope). Unresolved scope, authority, side effects, or required verification block integration. Link the required maintainer scope decision for new providers or capabilities involving target execution, injection, mutation, or protection recovery; ordinary fixes within existing boundaries may state "not applicable". Draft PRs may leave the scope decision pending and the readiness and merge checklists unchecked. Maintainers can help resolve open questions. Contribution scope: an ordinary change within existing boundaries. A maintainer scope decision does not apply. Whether unresolved `to` should keep the raw suffix is the open representation decision the maintainer asked this PR to isolate. ## Contract and boundary impact - Semantic owner and earliest changed stage: `src/application/ReferenceSourceImportEntries.ts`, when an ESM `source-import` relationship is left unresolved. - Contribution scope fit and linked maintainer decision: within the existing reference-source boundary; see the [maintainer comment](https://github.com/morluto/rea/pull/4572#issuecomment-6427907872). Not applicable otherwise. - CLI and MCP/tool-catalog contract: no schema or flag change. Only the `to` string of an unresolved ESM relationship whose specifier contains a raw `?` or `#` changes. - Provider, bridge, target-format, or platform compatibility: TypeScript-file `import`s also use `source-import` mode and get the same unresolved spelling. - Evidence, artifact, provenance, or reconstruction contract: an unresolved edge records the normalized pathname plus the raw query or fragment; `source_specifier` still records the declared spelling. Resolved edges are unchanged. - 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. - [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: 4 cases in `src/application/ReferenceSourceImportEntries.test.ts`, which uses main's existing cases unchanged: - [`keeps the raw query on an unresolved ESM pathname`](https://github.com/morluto/rea/blob/a7edd17093919857af72cf5a0ffbcb97ae75807e/src/application/ReferenceSourceImportEntries.test.ts#L660-L684): `./missing.mjs?v=1` → `to: "missing.mjs?v=1"`, and `./missing.mjs?v=1/..` → `to: "missing.mjs?v=1/.."` (the suffix is not dot-normalized), each with the original `source_specifier`. - [`keeps the raw fragment on an unresolved ESM pathname`](https://github.com/morluto/rea/blob/a7edd17093919857af72cf5a0ffbcb97ae75807e/src/application/ReferenceSourceImportEntries.test.ts#L686-L698): `./missing.mjs#a/../b` → `to: "missing.mjs#a/../b"`. - [`keeps the raw query when an unresolved ESM import is in a subdirectory`](https://github.com/morluto/rea/blob/a7edd17093919857af72cf5a0ffbcb97ae75807e/src/application/ReferenceSourceImportEntries.test.ts#L700-L721): `pkg/main.mjs` importing `./missing.mjs?v=1/..` → `to: "pkg/missing.mjs?v=1/.."`, and `main.mjs` importing `./pkg/missing.mjs?v=1` → `to: "pkg/missing.mjs?v=1"`. - [`leaves a resolved ESM query on the inventoried pathname`](https://github.com/morluto/rea/blob/a7edd17093919857af72cf5a0ffbcb97ae75807e/src/application/ReferenceSourceImportEntries.test.ts#L723-L738): control; `./dep.mjs?v=1` with `dep.mjs` inventoried still resolves to `to: "dep.mjs"`, `resolution: "internal"`. - Base reproduction or other evidence: on `main`, the same unresolved imports produce `to` without the suffix (for example `missing.mjs` for `./missing.mjs?v=1`). The resolved control documents main's existing behavior, which this PR keeps. - User-visible CLI/MCP output (if applicable): the unresolved relationship becomes `{"from_path":"main.mjs","to":"missing.mjs?v=1","source_specifier":"./missing.mjs?v=1","kind":"imports","resolution":"unresolved"}`. Captured at the entry-parsing boundary; no end-to-end CLI output is captured. - Remaining proof gaps: - No MCP or real-provider run. - The full suite and `check:pr` were not run locally; CI on head `a7edd17` covers them (see Validation performed). - Windows was not checked. 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 Local commands ran on Node 22.23.4 against head `a7edd17`. Each command exited 0. - `npx vitest run src/application/ReferenceSourceImportEntries.test.ts`: 18 passed. - `npx vitest run` over the reference-source set (`src/application/ReferenceSourceImportEntries.test.ts`, `src/domain/referenceSourcePathIdentity.test.ts`, `src/application/ReferenceSourceImport`, `src/domain/referenceSource`, `src/reference/ReferenceSource`, `tests/boundary/filesystem/referenceSource`, `tests/boundary/cli/referenceSource`): 42 files passed; 213 tests passed and 2 skipped. - `npm run lint`: 0 errors. - `npm run typecheck`: ok. - `npm run build`: ok. - Pre-push `check:fast` (typecheck and lint): ok. CI on head `a7edd17` ([run 40547689573](https://github.com/morluto/rea/actions/runs/40547689573)) passed: `CI required`, `Static checks`, `Build package`, `Source tests`, `Portable tests`, all eight test shards, `Native package baseline (linux x64)`, `Build bundled Windows x64 native controls`, `Classify changes` and `Greptile Review` succeeded, and `Conventional PR title` and `Validate author declaration` passed. `Deep static checks`, `Documentation` and the optional capability lanes were skipped as untouched. ## Compatibility, safety, and release - Breaking changes or migration steps: none to the schema or the CLI. The `to` of an unresolved ESM relationship with a raw `?` or `#` gains that suffix compared with main. Resolved edges, rejected escapes and `require` edges are unchanged. - Real Hopper/Ghidra, browser, or OS coverage: not applicable to Hopper, Ghidra or browsers. Linux only; Windows was not checked. - Package or release metadata impact: none. - Security, privacy, process, or containment review: pure string handling over already-read source text. No new filesystem access, process launches or network access. The suffix is only appended to an unresolved `to`; it never affects inventory lookup or which file an edge targets. ## Author readiness Human owner: @Ganesh2325 - [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 - [ ] 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 change was prepared with AI assistance. --- <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#6314
No description provided.