fix(vscode): restore sessions after channel database regression

[marius-kilocode]

PR #11031 changed non-production CLI binaries to select a database from their installation channel. Its compatibility commit 6ecaaab48a removed the prior Kilo override that always selected the shared kilo.db.

Channel-specific databases are useful for standalone CLI development, but they break the VS Code development extension. The extension bundles a branch-channel binary while Agent Manager keeps shared worktree and session IDs in the main checkout's .kilo/agent-manager.json. After #11031, those IDs were restored from shared state but looked up in opencode-<channel>.db instead of the kilo.db where the sessions exist, causing valid sessions to fail with Session not found.

This restores the extension's previous compatibility behavior at its owned backend spawn boundary. Every extension-managed kilo serve process receives KILO_DISABLE_CHANNEL_DB=true, so the sidebar, editor tabs, and Agent Manager resolve the same persisted sessions across branches and worktrees. Standalone CLI development keeps channel isolation, production behavior remains unchanged, and no session state or Agent Manager metadata is migrated or rewritten.

[kilo-code-bot]

Code Review Summary

Status: No Issues Found | Recommendation: Merge

Files Reviewed (3 files)

• .changeset/share-vscode-session-database.md
• packages/kilo-vscode/src/services/cli-backend/server-manager.ts
• packages/kilo-vscode/tests/unit/server-manager-utils.test.ts

---

_{Reviewed by claude-4.6-sonnet-20260217 · 472,581 tokens}

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