fix(cli): validate selected local paths before resolution

Reuse the nonempty NUL-free local path contract before normalization in artifact commands, auxiliary inputs, and output destinations. Empty selections now fail at parsing instead of selecting the working directory; explicit relative paths preserve their target.

Public CLI checks cover primary and auxiliary empty paths, exact relative-file digest, explicit current-directory selection, symlink parent semantics, and environment export inputs. Correct the desktop fixture to assert the existing CLI validation envelope.

src/cli/evmCommands.ts

@@ -4,6 +4,7 @@ import { logCliCommand } from "../cliLogging.js";
 import type { Logger } from "pino";
 import type { CliInstance } from "./types.js";
 import { withCommandCancellation } from "./commandCancellation.js";
+import { localPathStringSchema } from "../domain/localPath.js";
 import { absoluteCallerPath } from "../filesystem/callerPath.js";
 import { finishAnalysisCommand } from "./finishAnalysisCommand.js";
 import { inspectEvmInterfaceInputSchema } from "../domain/evm/evmInterface.js";
@@ -18,7 +19,7 @@ export const registerEvmCommands = (
   cli.command(evmInterfaceModule.cliCommand, {
     description: "Infer interface candidates from explicit local EVM bytecode",
     args: z.object({
-      path: z.string().describe("Local bytecode carrier"),
+      path: localPathStringSchema.describe("Local bytecode carrier"),
       encoding: z
         .enum(["raw", "hex"])
         .describe("Selected carrier representation"),