feat(cli): filesmith command line and Claude skill (#30)

[Maxaubert]

Closes #30.

What

• filesmith command bundled with the app and on the per-user PATH: convert, compress, resize, upscale, removebg, generate, pdf <tool>, plus formats, doctor, setup, skill. Verb-first, option names and values mirror the app, --dry-run everywhere, --json NDJSON events (schema v1), exit codes 0/1/2/130, never overwrites.
• Runs the installed Filesmith.exe in Node mode (ELECTRON_RUN_AS_NODE) behind filesmith.cmd and an sh shim, so it works while the app is open and its jobs never reach the app.
• AI tools never download from a job: filesmith setup <tool> is the only command that downloads (progress with bytes, ETA and heartbeats; cross-process locks).
• Claude Code skill in resources/skill/filesmith, installed by filesmith skill install or Settings > CLAUDE.
• User and agent reference: docs/cli.md. Version 0.6.0.

Engine changes outside src/cli

EngineEnv provider (no electron imports in the engine), shared boot, dry-run output planners, readiness checks and allowDownload, explicit rembg install with a pinned model folder (fixes the always-false removebg ready flag), cross-process install locks, atomic state writes, comfy-live.json, GenerateOptions.outDir, per-user PATH in the installer.

Atomic outputs (app and CLI): every tool now writes name (tag).filesmith-part.ext (folders: base.filesmith-part) next to the reserved placeholder and renames it onto the final name only on success (src/main/atomicOutput.ts). A failed or canceled job removes both. Reservation, collision names and dry-run predictions are unchanged; the rename only ever replaces our own untouched empty placeholder, otherwise the output takes the next free name. Covers convert, compress, resize, PDF tools (files and folders), archives, upscale, removebg, generate.

For the owner

• Settings > CLAUDE screenshot (O9): docs/mockups/cli-settings-skill.png
• Deviations from the spec, all listed in the plan: entry file name, planners in one module, no new renderer UI for removebg setup, hidden-file rule, setup remove --permanent above 5 GB, two additive event fields, LibreOffice checked at run time, bare filesmith prints help, README left as logo and badges (docs/cli.md instead).
• Ctrl+C in the installed build: fixed in this PR. Root cause: Filesmith.exe is a GUI-subsystem program; Electron attaches it to the terminal's console after libuv has registered its console control handler, and in that process the handler is never called, so Windows' default handler ends it at once (0xC000013A). Reproduced with a 6-line script under plain electron.exe (node.exe: handler runs; electron.exe: killed), and the same loss reproduces in pythonw when a handler is registered before AttachConsole (after it: works). No JavaScript can register a handler again. Fix: under Electron the CLI reads \\.\CONIN$ in raw mode, where the Ctrl+C key arrives as byte 0x03 instead of a signal (src/cli/consoleCtrlC.ts). Side effect: cmd never sees the Ctrl+C, so the "Terminate batch job (Y/N)?" prompt (spec O3) is gone and exit 130 passes through.
• What still ends the process at once: Ctrl+Break, closing the window, taskkill /F, programmatic GenerateConsoleCtrlEvent. For those a small detached watchdog (src/cli/watchdog.ts, started with the first output of a run, Electron runtime only) stops the tools the run left running (pid plus image-name check) and removes its part files and placeholders. No summary or exit 130 in those cases.
• Remaining limit (documented in docs/cli.md): with stdout redirected in cmd or PowerShell (> file, | findstr), Windows starts Filesmith.exe without a console, so a Ctrl+C key never reaches it and the run completes (cmd then asks "Terminate batch job"). A native console launcher (O3) would close this; not done here.
• Unsigned, like every release so far.

Verification

• npm test: 84 files, 817 passed, 1 skipped (new: test/atomic-output.test.ts, test/atomic-tools-live.test.ts with real ffmpeg/magick/mutool/7-Zip: a canceled video compress, a failing convert, resize, split-pages cancel and a corrupt archive extract leave nothing; successes leave exactly the final file with unchanged collision names; test/cli-watchdog.test.ts). npm run typecheck, npm run lint, npx prettier --check ., npm run build: all pass.
• npm run test:e2e (with dist/win-unpacked built from this commit): 68 passed, 1 skipped (the opt-in visual capture). The two GPU tests that failed earlier (upscale: Real-ESRGAN 2x ..., generate: one 512px image ...) passed in this run. App workflows (convert, compress, PDF folders, archives, upscale, removebg, generate) still report the final path in their done events.
• New e2e: e2e/cli-packed.spec.ts › Ctrl+C in a console cancels cleanly runs the packed cmd shim in a new minimized console (e2e/ctrlc-console.ps1), writes a Ctrl+C key record into the console input during a 1080p h265 compress, and checks exit 130, 1 canceled on screen, no "Terminate batch job", no new ffmpeg.exe and only the source left. e2e/cli.spec.ts › a CLI killed outright ... runs the CLI under Electron, taskkill /Fs it mid-encode (ffmpeg orphaned) and checks the watchdog stops ffmpeg and removes the part and the placeholder. Packed spec 4/4, CLI spec 17/17.
• Installed Filesmith-Setup-x64-0.6.0.exe silently (/S), exe 0.6.0, app relaunched and left open. Hands-on against the INSTALLED shims, app open, 1080p compress --codec h265, each in a fresh real console, interrupt ~8 s in:
  • Ctrl+C key record, filesmith.cmd ... --json: canceled event, summary with canceled: 1, exitCode: 130, process exit 130 after 0.4-0.6 s, no ffmpeg.exe left, folder holds only the source (the .filesmith-part.mp4 and the placeholder were there during the run).
  • Ctrl+C key record, human output, cmd shim and sh shim: stop long video.mp4, 1 file: 0 ok, 0 skipped, 0 failed, 1 canceled, exit 130, no ffmpeg, only the source.
  • GenerateConsoleCtrlEvent(CTRL_BREAK) (cmd and sh shims) and GenerateConsoleCtrlEvent(CTRL_C) (cmd): Filesmith.exe ends at once (0xC000013A via sh; cmd then waits on its prompt), no ffmpeg left, and the watchdog removed the part file and placeholder: only the source remains.
  • stdout redirected to a file (cmd shim) plus a console Ctrl+C: not delivered, the job completed with done and exit 0, then cmd's prompt. This is the documented limit above.
• Ctrl+C was not pressed on a physical keyboard; the key record written with WriteConsoleInputW is what a key press puts in the console input, and in raw mode the console delivers it as 0x03 rather than a signal.
• Earlier checks, unchanged by this round: shims from cmd, PowerShell 5.1/7 and Git Bash; filesmith skill install / status; silent uninstall/reinstall PATH handling.

🤖 Generated with Claude Code