[Fermionic-Lyu]

Release insta 0.1.27 with the Windows spaced-shim fix from #385 and the private-service source-deploy fix from #383. Only the package and lockfile version fields change; dependencies and runtime code are unchanged.

Validation: typecheck, build, and the full local suite pass (2259 tests, one Windows-only skip). The Windows fix already passed real Windows CI in #385; this PR also runs the repository's Linux and Windows gates.

After approval and merge, tag the merged release commit as v0.1.27 to trigger all five native binaries, checksums, and npm OIDC publishing. No manual workflow dispatch.

---

Summary by cubic

Releases insta 0.1.27, shipping the Windows spaced-shim fix from #385 and the private-service source-deploy fix from #383. Only the package.json and package-lock.json version fields change; dependencies and runtime code are untouched.

After merge, tag the release commit as v0.1.27 to trigger the native binary builds, checksums, and npm OIDC publishing.

^{Written for commit 52fe39f. Summary will update on new commits.}

[agent-zhang-beihai]

Reviewed by Wang Miao

This PR bumps the insta CLI from 0.1.26 to 0.1.27 in package.json and both version fields of package-lock.json. I found no problems, and I'm approving it.

I checked three things. No hardcoded 0.1.26 remains anywhere in the repo. The CLI reads its version at runtime in src/version.ts, from package.json or from the INSTA_CLI_VERSION value baked into the binary at build time, so the bump reaches both builds. And the change is the same shape as the 0.1.26 release commit: the same two files, +3/-3.

[cubic-dev-ai]

No issues found across 2 files

_{View guided diff | Turn on auto-fix | Re-trigger cubic}

[agent-zhang-beihai]

Reviewed by Yang Dong

This advances the CLI release from 0.1.26 to 0.1.27, consistently updating the package manifest and lockfile in the established release shape. The change is correct as submitted.

APPROVE — no findings.

[jwfing]

LGTM - approved.