[PR #3339] test(javascript): cover missing package-manifest companions staying unknown #5718

Open
opened 2026-10-31 01:08:54 +00:00 by bsakaguchi · 0 comments
Owner

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/3339
Author: @VarunGore36
Created: 10/14/2026
Status: 🔄 Open

Base: main ← Head: fix/3213-missing-manifest-unavailable


📝 Commits (1)

  • 0b6e7db test(javascript): cover missing package-manifest companions staying unknown

📊 Changes

1 file changed (+76 additions, -1 deletions)

View changed files

📝 tests/boundary/filesystem/javascript-applications/javascriptApplicationService.test.ts (+76 -1)

📄 Description

Summary

Related to #3213. Follow-up boundary coverage for the manifest aspect fixed on main: a directory require whose package manifest was inventoried without acquirable bytes must stay unknown instead of resolving to an index file.

Problem and expected behavior

Trigger: pack an app with an unpacked pkg/package.json, remove the companion, analyze the ASAR, require("./pkg") with a present pkg/index.js.

  • Wrong outcome: edge reports resolved_path "pkg/index.js", resolution_status "resolved".
  • Expected: edge reports resolved_path null, resolution_status "unavailable", with an unavailable limitation on the edge evidence. Coverage is partial.

Change and scope

Test-only. Adds a boundary regression in tests/boundary/filesystem/javascript-applications/javascriptApplicationService.test.ts that builds the ASAR, removes the companion, and asserts unavailable with null resolved path, no pkg/index.js resolution, partial coverage, and an unavailable edge evidence limitation. No source changes; the behavior under test is provided by main.

Contribution scope fit and linked maintainer decision: ordinary test coverage within existing boundaries; not applicable.

Contract and boundary impact

  • Semantic owner and earliest changed stage: none (test-only).
  • CLI and MCP/tool-catalog contract: none.
  • Provider, bridge, target-format, or platform compatibility: none.
  • Evidence, artifact, provenance, or reconstruction contract: none.
  • 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: the new boundary regression described above.
  • Base reproduction: the same scenario failed before the main-branch fix (edge resolved to pkg/index.js); it passes with the fix in place.
  • User-visible CLI/MCP output: none (no behavior change in this PR).
  • Remaining proof gaps: MCP path not executed (same validated application service; source-derived). Only Linux x64 exercised.

For evidence-bearing changes:

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

Validation performed

  • npm run test:focused -- tests/boundary/filesystem/javascript-applications/javascriptApplicationService.test.ts — 13 passed.
  • npm run check:fast (typecheck + lint) — green.
  • git diff --check — clean.
  • Real Hopper/Ghidra, browser, or OS coverage beyond Linux x64: unavailable.

Compatibility, safety, and release

  • Breaking changes or migration steps: none.
  • Real Hopper/Ghidra, browser, or OS coverage: none; JavaScript analysis worker exercised via boundary tests on Linux x64.
  • Package or release metadata impact: none.
  • Security, privacy, process, or containment review: none; no target execution, no new I/O.

Author readiness

Human owner:

  • 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/3339 **Author:** [@VarunGore36](https://github.com/VarunGore36) **Created:** 10/14/2026 **Status:** 🔄 Open **Base:** `main` ← **Head:** `fix/3213-missing-manifest-unavailable` --- ### 📝 Commits (1) - [`0b6e7db`](https://github.com/morluto/rea/commit/0b6e7db2003bd590fef601c08d25ab7d276f9d51) test(javascript): cover missing package-manifest companions staying unknown ### 📊 Changes **1 file changed** (+76 additions, -1 deletions) <details> <summary>View changed files</summary> 📝 `tests/boundary/filesystem/javascript-applications/javascriptApplicationService.test.ts` (+76 -1) </details> ### 📄 Description ## Summary Related to #3213. Follow-up boundary coverage for the manifest aspect fixed on main: a directory require whose package manifest was inventoried without acquirable bytes must stay unknown instead of resolving to an index file. ## Problem and expected behavior Trigger: pack an app with an unpacked pkg/package.json, remove the companion, analyze the ASAR, require("./pkg") with a present pkg/index.js. - Wrong outcome: edge reports resolved_path "pkg/index.js", resolution_status "resolved". - Expected: edge reports resolved_path null, resolution_status "unavailable", with an unavailable limitation on the edge evidence. Coverage is partial. ## Change and scope Test-only. Adds a boundary regression in tests/boundary/filesystem/javascript-applications/javascriptApplicationService.test.ts that builds the ASAR, removes the companion, and asserts unavailable with null resolved path, no pkg/index.js resolution, partial coverage, and an unavailable edge evidence limitation. No source changes; the behavior under test is provided by main. Contribution scope fit and linked maintainer decision: ordinary test coverage within existing boundaries; not applicable. ## Contract and boundary impact - Semantic owner and earliest changed stage: none (test-only). - CLI and MCP/tool-catalog contract: none. - Provider, bridge, target-format, or platform compatibility: none. - Evidence, artifact, provenance, or reconstruction contract: none. - 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: the new boundary regression described above. - Base reproduction: the same scenario failed before the main-branch fix (edge resolved to pkg/index.js); it passes with the fix in place. - User-visible CLI/MCP output: none (no behavior change in this PR). - Remaining proof gaps: MCP path not executed (same validated application service; source-derived). Only Linux x64 exercised. For evidence-bearing changes: - [x] Observed, derived, and inferred claims remain distinguishable. - [x] Artifact identity, source provenance, and failed attempts remain preserved. - [x] Unsupported, incomplete, unavailable, or uncertain outcomes remain visible. ## Validation performed - `npm run test:focused -- tests/boundary/filesystem/javascript-applications/javascriptApplicationService.test.ts` — 13 passed. - `npm run check:fast` (typecheck + lint) — green. - `git diff --check` — clean. - Real Hopper/Ghidra, browser, or OS coverage beyond Linux x64: unavailable. ## Compatibility, safety, and release - Breaking changes or migration steps: none. - Real Hopper/Ghidra, browser, or OS coverage: none; JavaScript analysis worker exercised via boundary tests on Linux x64. - Package or release metadata impact: none. - Security, privacy, process, or containment review: none; no target execution, no new I/O. ## Author readiness Human owner: - [ ] I reviewed the final diff and relevant existing code, understand the change and its edge cases, and take responsibility for the complete PR, including AI-assisted work. - [ ] I checked the evidence above, confirmed it supports the current change, and recorded meaningful validation gaps. - [ ] I declare this PR ready for initial maintainer review. ## Before merge - [ ] This PR addresses a concrete problem or an agreed enhancement. - [ ] Material scope and authority questions are resolved, and any required maintainer scope decision covers the final diff. - [ ] The PR has one focused outcome and the title follows `type(scope): outcome`. - [ ] Related issue is linked, or the reason for not linking one is stated above. - [ ] Tests cover changed observable behavior and meaningful failure paths. - [ ] Owning docs, contracts, and generated metadata are updated where needed. - [ ] User-visible CLI/MCP changes include representative output. - [ ] I checked the final diff for secrets, unrelated cleanup, and unsupported claims. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
Sign in to join this conversation.
No milestone
No project
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#5718
No description provided.