fix(javascript): classify application input selection failures by cause

analyze_javascript_application reported every input-selection problem as
an artifact fault:

- a missing input path: "Artifact could not be read or written", with no
  path or reason;
- an unreadable selected directory: the same generic io failure;
- a regular file that is neither a directory nor an .asar, and a
  --artifact-format that contradicts the selection: "Artifact is invalid
  or has changed. Get a fresh copy and try again."

Report a missing path as an invalid input_path, an unreadable selection
as access_denied, a non-directory non-.asar file as unsupported_target
with the accepted inputs as remediation, and a contradicting format as an
invalid format with the observed kind as expected value. Failures inside
a selected artifact keep their existing classification.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

src/application/javascript/JavaScriptApplicationService.test.ts

@@ -76,7 +76,7 @@ describe("JavaScript application failure diagnostics", () => {
     expect(JSON.parse(JSON.stringify(projection))).toEqual(projection);
   });
 
-  it("keeps filesystem failures distinct from engine failures", async () => {
+  it("reports a missing selection as invalid input, not an engine failure", async () => {
     const root = await createTestTempDirectory("rea-js-missing-");
     const result = await analyzeJavaScriptApplication({
       input_path: join(root, "missing"),
@@ -84,8 +84,11 @@ describe("JavaScript application failure diagnostics", () => {
     });
     if (result.ok) throw new Error("Expected missing artifact failure");
     expect(projectAnalysisError(result.error)).toMatchObject({
-      code: "artifact_operation_failed",
-      details: { operation: "analyze_javascript_application", reason: "io" },
+      code: "invalid_request",
+      details: {
+        operation: "analyze_javascript_application",
+        issues: [{ path: ["input_path"], reason: "invalid_value" }],
+      },
     });
   });