key (too_small) on plain minified JS directory #373

New issue

Closed

opened 2026-10-15 18:24:24 +00:00 by bsakaguchi · 1 comment

bsakaguchi commented

2026-10-15 18:24:24 +00:00

Owner

Originally created by @Th3-W6rst on GitHub (Oct 7, 2026).
Original GitHub issue: https://github.com/morluto/rea/issues/1009

Environment

rea 4.1.0 (npm global), Ubuntu 26.04, Node 22.22.1
rea doctor --client opencode --json reports healthy for the JS-application scope (no engine configured)

Command

rea analyze-javascript-application /tmp/8bp_js --json

Directory contains three plain JavaScript files only (no package.json, no node_modules):

application.js (1,230,582 bytes — minified bundle, very long lines)
game.js (318,230 bytes — Emscripten loader; 65536-char lines)
game-data.js (6,456 bytes)

Result (exit 1)

{
  "error": "JavaScript application analysis failed",
  "code": "unreadable_output",
  "category": "execution_failure",
  "message": "Analysis returned an unreadable result. Retry once; if it continues, run `rea doctor`.",
  "retryable": false,
  "remediation": { "action": "Analysis returned an unreadable result. Retry once; if it continues, run `rea doctor`." },
  "details": {
    "operation": "analyze_javascript_application",
    "reason": "Result schema rejected 2 issues at /identity/key (too_small)"
  }
}

Notes

Reproduces consistently (multiple runs), also on a reduced directory containing only game.js + game-data.js (the two loader files).
The failure looks like internal result-schema validation on /identity/key (too_small), not an input error reported by the provider.
rea doctor shows no issue for this scope; retry does not change the result.
Related family: #746 (different target, generic unreadable_output).

Happy to provide the exact files (public web-game assets) or a reduced repro privately if useful.

Originally created by @Th3-W6rst on GitHub (Oct 7, 2026). Original GitHub issue: https://github.com/morluto/rea/issues/1009 **Environment** - rea 4.1.0 (npm global), Ubuntu 26.04, Node 22.22.1 - `rea doctor --client opencode --json` reports healthy for the JS-application scope (no engine configured) **Command** ``` rea analyze-javascript-application /tmp/8bp_js --json ``` Directory contains three plain JavaScript files only (no package.json, no node_modules): - `application.js` (1,230,582 bytes — minified bundle, very long lines) - `game.js` (318,230 bytes — Emscripten loader; 65536-char lines) - `game-data.js` (6,456 bytes) **Result (exit 1)** ```json { "error": "JavaScript application analysis failed", "code": "unreadable_output", "category": "execution_failure", "message": "Analysis returned an unreadable result. Retry once; if it continues, run `rea doctor`.", "retryable": false, "remediation": { "action": "Analysis returned an unreadable result. Retry once; if it continues, run `rea doctor`." }, "details": { "operation": "analyze_javascript_application", "reason": "Result schema rejected 2 issues at /identity/key (too_small)" } } ``` **Notes** - Reproduces consistently (multiple runs), also on a reduced directory containing only `game.js` + `game-data.js` (the two loader files). - The failure looks like internal result-schema validation on `/identity/key` (`too_small`), not an input error reported by the provider. - `rea doctor` shows no issue for this scope; retry does not change the result. - Related family: #746 (different target, generic `unreadable_output`). Happy to provide the exact files (public web-game assets) or a reduced repro privately if useful.

bsakaguchi

2026-10-15 18:24:24 +00:00

closed this issue
added the
area: mcp

enhancement
labels

bsakaguchi commented

2026-10-15 18:24:25 +00:00

Author

Owner

@N0zoM1z0 commented on GitHub (Oct 7, 2026):

Verified: this validation failure is fixed in the published 5.0.0 package.

I installed 4.1.0 and 5.0.0 in separate temporary directories and ran the same reduced two-file loader, with no package.json, empty endpoint/worker strings, and a 65,536-character literal on a long line:

4.1.0: exit 1, reproducing Result schema rejected 2 issues at /identity/key (too_small).
5.0.0: exit 0, returning complete Evidence and preserving both empty identity keys.

The underlying correction landed in #839. The same reduced fixture also succeeds on Windows with Node 22.19.0. These checks reproduce the reported schema constraint; the original game assets were not supplied.

Upgrade the global CLI and rerun your analysis:

npm install -g rea-agents@5.0.0
rea --version
rea analyze-javascript-application /path/to/js-directory --json

rea --version should report 5.0.0. You can also run the published version without changing the global installation:

npx --yes --package rea-agents@5.0.0 rea analyze-javascript-application /path/to/js-directory --json

Retrying the same 4.1.0 installation or rerunning doctor will not repair this schema mismatch; upgrading is the applicable recovery. A long-line/plain-directory regression is prepared to preserve this behavior.

@N0zoM1z0 commented on GitHub (Oct 7, 2026): Verified: this validation failure is fixed in the published **5.0.0** package. I installed 4.1.0 and 5.0.0 in separate temporary directories and ran the same reduced two-file loader, with no package.json, empty endpoint/worker strings, and a 65,536-character literal on a long line: - **4.1.0:** exit 1, reproducing `Result schema rejected 2 issues at /identity/key (too_small)`. - **5.0.0:** exit 0, returning complete Evidence and preserving both empty identity keys. The underlying correction landed in #839. The same reduced fixture also succeeds on Windows with Node 22.19.0. These checks reproduce the reported schema constraint; the original game assets were not supplied. Upgrade the global CLI and rerun your analysis: ```sh npm install -g rea-agents@5.0.0 rea --version rea analyze-javascript-application /path/to/js-directory --json ``` `rea --version` should report `5.0.0`. You can also run the published version without changing the global installation: ```sh npx --yes --package rea-agents@5.0.0 rea analyze-javascript-application /path/to/js-directory --json ``` Retrying the same 4.1.0 installation or rerunning doctor will not repair this schema mismatch; upgrading is the applicable recovery. A long-line/plain-directory regression is prepared to preserve this behavior.

bsakaguchi referenced this issue

2026-10-16 21:13:04 +00:00

[PR #433] [MERGED] feat: add runtime reconstruction roadmap workflows #1982

bsakaguchi added

enhancement

and removed

enhancement

labels

2026-10-31 00:29:06 +00:00