[GH-ISSUE #6225] [Bug] inspect-analysis-view help omits supported Rust, IL2CPP, model and GPU Evidence #3789

Closed
opened 2026-10-31 00:44:03 +00:00 by bsakaguchi · 1 comment
Owner

Originally created by @coygeek on GitHub (Oct 22, 2026).
Original GitHub issue: https://github.com/morluto/rea/issues/6225

Before submitting

  • I searched the open and closed issues for a related report.
  • I removed credentials, tokens, private paths, and sensitive target data.

Area

CLI

Observed behavior

node scripts/rea.mjs inspect-analysis-view --help exits 0 and enumerates accepted completed Evidence families without Rust, IL2CPP metadata, model artifacts or GPU code objects. The omission reproduced in 2/2 help requests. A separate complete-inline model metadata view succeeded through the public CLI, so at least that omitted family is directly confirmed working.

Reproduction

With the baseline below and its locked dependencies already available, run npm run build:cached, then:

node scripts/rea.mjs inspect-analysis-view --help

The opening description ends in Dart AOT, web network capture or pcap Evidence JSON; none of the four families appears. Verification built once and ran this help command twice. It did not install dependencies.

Expected behavior

The help should accurately describe the completed Evidence inputs the command supports. Accurate general wording is sufficient; an exhaustive list is not required. The CLI guide says the CLI uses the same application workflows and Evidence contracts as MCP. The canonical tool description names Rust embedded dependencies and the IL2CPP, model and GPU parent operations. The IL2CPP guide explicitly shows the CLI analysis-view workflow.

Impact and scope

P3 wording and capability-discovery defect: CLI help understates accepted inputs. A direct model metadata view worked, and the provider guides describe these inputs. No incorrect analysis result or blocked analysis caused by this wording was observed. Completed Rust, IL2CPP and GPU projection behavior was source-checked, not runtime-replayed.

REA version

Source commit c465ff5a81 (main)

Runtime and platform

Node.js v26.12.0; macOS 27.0.1; arm64. The repository pins Node.js 24.18.0; verification used the different runtime recorded here.

Target and artifact context

No target is needed for the help reproduction. The supplementary positive control used a 52-byte safetensors file containing only {"__metadata__":{"purpose":"help-verifier"}} after its eight-byte little-endian header-length prefix. No tensor data, model execution or external service was involved.

Interface

CLI

Earliest failure stage

Transport or result projection

Relevant output or evidence

Observed help output, exit 0, empty stderr, in both runs:

rea inspect-analysis-view — Project a selected view of completed Go build metadata, binary-layout, JavaScript application, native function/inventory, artifact-inventory, desktop-directory, WASM, Mach-O, Interface Builder, EVM, managed, Android package, Dart AOT, web network capture or pcap Evidence JSON

The supplementary model control ran node scripts/rea.mjs inspect-model-artifact sample.safetensors --json, then supplied that complete Evidence inline to inspect-analysis-view with view: {"kind":"model-artifact","collection":"metadata","offset":0,"limit":1}. Both calls exited 0. The view returned parent_operation: inspect_model_artifact and one metadata row with key purpose, value help-verifier, and exhausted 1/1 coverage. Those displayed fixture names are neutral; verification used disposable isolated paths.

Four additional CLI requests used an unavailable retained parent ID and the view shapes rust/packages, il2cpp-metadata/types, model-artifact/metadata and gpu-code-objects/targets with offset 0 and limit 1. Each reached evidence_integrity_mismatch; an invalid view-kind control returned invalid_request. These probes demonstrate input acceptance, not successful completed views.

Typed outcome or recovery expected

Preserve the working model metadata view and rejection of invalid view kinds. Correct the help description without implying that arbitrary Evidence operations are supported.

Analysis or suspected cause

Source-derived: the CLI registration stores the incomplete description independently of the MCP description. The same CLI validates the common input and calls the shared application service. The retained projector map includes all four omitted parent operations. The named omissions are examples, not an exhaustive inventory of every supported parent missing from help.

Additional context

Related #3194 is closed and concerned web-capture help; the currently observed CLI description already names web network capture and pcap. Open #5733 requests pcap additions to the MCP opening parent list and unsupported-parent guidance. Those changes would not update the independently stored CLI description reported here. A broader shared-description refactor could cover both, but is not an implemented fix or required by that issue.

Open and closed issue/PR searches covered the command and help, CLI parent lists, the CLI source filename, and Rust/IL2CPP/model/GPU terms; no duplicate was found. Fetched upstream main at 34fd7bdf7d has no changes since the baseline to the three cited implementation files. This is a source freshness check, not a current-main runtime replay. Prepared with AI assistance.

Originally created by @coygeek on GitHub (Oct 22, 2026). Original GitHub issue: https://github.com/morluto/rea/issues/6225 ### Before submitting - [x] I searched the open and closed issues for a related report. - [x] I removed credentials, tokens, private paths, and sensitive target data. ### Area CLI ### Observed behavior `node scripts/rea.mjs inspect-analysis-view --help` exits 0 and enumerates accepted completed Evidence families without Rust, IL2CPP metadata, model artifacts or GPU code objects. The omission reproduced in 2/2 help requests. A separate complete-inline model metadata view succeeded through the public CLI, so at least that omitted family is directly confirmed working. ### Reproduction With the baseline below and its locked dependencies already available, run `npm run build:cached`, then: ```sh node scripts/rea.mjs inspect-analysis-view --help ``` The opening description ends in `Dart AOT, web network capture or pcap Evidence JSON`; none of the four families appears. Verification built once and ran this help command twice. It did not install dependencies. ### Expected behavior The help should accurately describe the completed Evidence inputs the command supports. Accurate general wording is sufficient; an exhaustive list is not required. The [CLI guide](https://github.com/morluto/rea/blob/c465ff5a814b8e1a386fc547cbcd94df5c35f086/docs/cli.md#L3) says the CLI uses the same application workflows and Evidence contracts as MCP. The [canonical tool description](https://github.com/morluto/rea/blob/c465ff5a814b8e1a386fc547cbcd94df5c35f086/src/contracts/analysisViewToolContracts.ts#L20) names Rust embedded dependencies and the IL2CPP, model and GPU parent operations. The [IL2CPP guide](https://github.com/morluto/rea/blob/c465ff5a814b8e1a386fc547cbcd94df5c35f086/docs/il2cpp-metadata.md#L125) explicitly shows the CLI analysis-view workflow. ### Impact and scope P3 wording and capability-discovery defect: CLI help understates accepted inputs. A direct model metadata view worked, and the provider guides describe these inputs. No incorrect analysis result or blocked analysis caused by this wording was observed. Completed Rust, IL2CPP and GPU projection behavior was source-checked, not runtime-replayed. ### REA version Source commit c465ff5a814b8e1a386fc547cbcd94df5c35f086 (main) ### Runtime and platform Node.js v26.12.0; macOS 27.0.1; arm64. The repository pins Node.js 24.18.0; verification used the different runtime recorded here. ### Target and artifact context No target is needed for the help reproduction. The supplementary positive control used a 52-byte safetensors file containing only `{"__metadata__":{"purpose":"help-verifier"}}` after its eight-byte little-endian header-length prefix. No tensor data, model execution or external service was involved. ### Interface CLI ### Earliest failure stage Transport or result projection ### Relevant output or evidence Observed help output, exit 0, empty stderr, in both runs: ```text rea inspect-analysis-view — Project a selected view of completed Go build metadata, binary-layout, JavaScript application, native function/inventory, artifact-inventory, desktop-directory, WASM, Mach-O, Interface Builder, EVM, managed, Android package, Dart AOT, web network capture or pcap Evidence JSON ``` The supplementary model control ran `node scripts/rea.mjs inspect-model-artifact sample.safetensors --json`, then supplied that complete Evidence inline to `inspect-analysis-view` with `view: {"kind":"model-artifact","collection":"metadata","offset":0,"limit":1}`. Both calls exited 0. The view returned `parent_operation: inspect_model_artifact` and one metadata row with key `purpose`, value `help-verifier`, and exhausted 1/1 coverage. Those displayed fixture names are neutral; verification used disposable isolated paths. Four additional CLI requests used an unavailable retained parent ID and the view shapes `rust/packages`, `il2cpp-metadata/types`, `model-artifact/metadata` and `gpu-code-objects/targets` with offset 0 and limit 1. Each reached `evidence_integrity_mismatch`; an invalid view-kind control returned `invalid_request`. These probes demonstrate input acceptance, not successful completed views. ### Typed outcome or recovery expected Preserve the working model metadata view and rejection of invalid view kinds. Correct the help description without implying that arbitrary Evidence operations are supported. ### Analysis or suspected cause Source-derived: the [CLI registration](https://github.com/morluto/rea/blob/c465ff5a814b8e1a386fc547cbcd94df5c35f086/src/cli/analysisViewCommands.ts#L82) stores the incomplete description independently of the MCP description. The same CLI validates the common input and calls the shared application service. The [retained projector map](https://github.com/morluto/rea/blob/c465ff5a814b8e1a386fc547cbcd94df5c35f086/src/domain/analysisView/analysisView.ts#L1034) includes all four omitted parent operations. The named omissions are examples, not an exhaustive inventory of every supported parent missing from help. ### Additional context Related #3194 is closed and concerned web-capture help; the currently observed CLI description already names web network capture and pcap. Open #5733 requests pcap additions to the MCP opening parent list and unsupported-parent guidance. Those changes would not update the independently stored CLI description reported here. A broader shared-description refactor could cover both, but is not an implemented fix or required by that issue. Open and closed issue/PR searches covered the command and help, CLI parent lists, the CLI source filename, and Rust/IL2CPP/model/GPU terms; no duplicate was found. Fetched upstream main at 34fd7bdf7d7aeec83d0380254ca9e0f7149c98ef has no changes since the baseline to the three cited implementation files. This is a source freshness check, not a current-main runtime replay. Prepared with AI assistance.
Author
Owner

@morluto commented on GitHub (Oct 23, 2026):

Fixed on main in github.com/morluto/rea@dab18c1a3f. CLI help now says “Project a selected view of completed Evidence JSON for a supported analysis operation”, replacing the incomplete parent enumeration. The issue explicitly accepts accurate general wording; no runtime projection defect is alleged.

Verified against the full issue and current source. The published tree also retains passing docs:check and docs:build receipts. This closes the documentation/help/CI-configuration scope; no new provider runtime verification is claimed.

<!-- gh-comment-id:6376065383 --> @morluto commented on GitHub (Oct 23, 2026): Fixed on main in https://github.com/morluto/rea/commit/dab18c1a3fc27909f8d74ee04cf5abda6d33713e. CLI help now says “Project a selected view of completed Evidence JSON for a supported analysis operation”, replacing the incomplete parent enumeration. The issue explicitly accepts accurate general wording; no runtime projection defect is alleged. Verified against the full issue and current source. The published tree also retains passing docs:check and docs:build receipts. This closes the documentation/help/CI-configuration scope; no new provider runtime verification is claimed.
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#3789
No description provided.