fix: rename downloaded binary to avoid Windows UAC installer-detection

[kenhia]

Problem

On Windows, npx atv-starterkit@latest init (and --guided) does nothing and exits with code 1 and no output.

Root cause

The npm package downloads a Go binary named atv-installer.exe and runs it via execFileSync in npm/bin/cli.js. Windows UAC has an installer-detection heuristic that automatically flags any executable whose filename contains install (also setup, update, patch) as an installer requiring administrator elevation. Launched non-elevated, Windows refuses to start it:

The requested operation requires elevation

cli.js catches the thrown error and does process.exit(err.status || 1) without re-printing the message, so the user just sees a silent exit 1.

Proof

Running the downloaded binary directly returns The requested operation requires elevation. Copying the exact same bytes to a name without install (e.g. atv-tool.exe) runs perfectly with no elevation. Only the filename differs.

Fix

Rename the downloaded binary atv-installer → atv-inst-tool (verified locally to not trigger the heuristic):

• .goreleaser.yml — project_name + builds[].binary
• npm/install.js — BINARY_NAME
• npm/bin/cli.js — BINARY_NAME
• .gitignore, npm/.gitignore — ignore the new artifact name
• npm/README.md — doc reference

Testing

• go build + ran the full npm wrapper (node npm/bin/cli.js init) end-to-end on Windows → scaffolded all files, exit 0, no elevation error.
• go test ./... passes except a pre-existing TestDogfoodPromptParity failure that also fails on clean main (unrelated to this change).

Note for maintainers

install.js fetches the latest release and downloads <BINARY_NAME>_<ver>_<os>_<arch>. This change must ship together with a new GitHub release built from the updated goreleaser config, so the published archive name matches the new atv-inst-tool name.