#152 chore: bump version to 0.0.49

Release bump. Everything below is already merged to main; v0.0.48 was tagged before it landed.

Windows compatibility (the four that just merged)

• #148 — npm self-upgrade spawning: PATH resolved case-insensitively on win32, npm re-entered through node/npm-cli.js, shims launched via a System32-pinned cmd.exe
• #149 — compute exec through npm's PowerShell shim, which eats the first bare --
• #150 — CLI errors exit cleanly instead of tripping a libuv assertion
• #151 — the test-windows CI lane, so this class of bug fails a check rather than a user

Also unreleased since v0.0.48

• #141 — one live source of truth for latest; the report quotes what is on disk
• #142 — stop promising a nixpacks lane insta deploy <dir> does not have
• #147 — region-aware compute set-domain/check-domain

package-lock.json was left at 0.0.47 by an earlier bump; npm version resyncs it, so this clears that drift too.

npm run typecheck clean, npm test 627/627.

---

Summary by cubic

Bumps insta to 0.0.49 so fixes merged since the v0.0.48 tag ship in a release; the diff only changes version numbers. This also resyncs package-lock.json, which an earlier bump had left at 0.0.47.

Included since v0.0.48

• Windows compatibility: npm self-upgrade spawning works on win32, compute exec goes through the PowerShell shim, CLI errors exit cleanly instead of tripping a libuv assertion, and a windows CI lane now guards these.
• Upgrade checks read latest from disk instead of a second source, insta deploy no longer promises a nixpacks lane, and compute set-domain/check-domain are region-aware.