fix(vscode): exclude .cli-version marker from VSIX packaging

[catrielmuller]

What

Exclude the build-only bin/.cli-version marker from the packaged VSIX so production installs are no longer detected as local builds.

Why

local-bin.ts writes bin/.cli-version during both dev (compile) and production (package) builds. .vscodeignore re-includes bin/** so the CLI binary ships, which also ships .cli-version. That made the localCli branch in ServerManager.startServer true outside F5 sessions:

const localCli =
  this.context.extensionMode === vscode.ExtensionMode.Development ||
  fs.existsSync(path.join(this.context.extensionPath, "bin", ".cli-version"))
const bwrapEnv = process.env.KILO_BWRAP_PATH ? {} : resolveLocalBwrapEnv(this.context.extensionPath, localCli)

As a result, production installs could inject KILO_BWRAP_PATH from ~/.cache/kilo-vscode/bwrap whenever the bundled helper looked incomplete — broader than the local-only fallback this code intended to add.

How

Add bin/.cli-version to .vscodeignore after the !bin/** re-include. The marker stays present in local source/dev checkouts (so source runs still work) but is absent from packaged installs, keeping localCli detection truly local-only. All runtime bin/ artifacts (kilo, bwrap, tree-sitter/**, licenses/**, the sandbox worker) still ship — verified against the ignore library vsce uses.

This is a packaging-only change; no runtime code is touched.

[kilo-code-bot]

Code Review Summary

Status: No Issues Found | Recommendation: Merge

Files Reviewed (2 files)

• .changeset/vscode-cli-version-marker-packaging.md
• packages/kilo-vscode/.vscodeignore

---

_{Reviewed by gpt-5.4-2026-03-05 · Input: 59.5K · Output: 8.1K · Cached: 201.9K}

_{Review guidance: REVIEW.md from base branch main}