Cline rules

1# SDK Adapter
2 
3The VSCode extension runs on the Cline SDK (`@cline/core`, `@cline/llms`,
4`@cline/shared`) through an adapter layer in `apps/vscode/src/sdk/`. The
5webview still talks gRPC; the adapter translates between gRPC handlers and SDK
6calls. See `apps/vscode/src/dev/debug-harness/README.md` for the debug harness.
7 
8## Conventions
9 
101. **Look up SDK APIs, don't guess.** Use `kb_search(name="sdk", query="...")`
11   before implementing against an SDK surface.
122. **Reference the pre-SDK implementation when replacing a module.** Add a
13   `// Replaces classic src/core/... (see origin/main)` header and use
14   `kb_search(name="cline", commit="origin/main")` or
15   `git show origin/main:path` to consult the prior implementation.
163. **Single entry point.** There is one codepath — the SDK adapter. No
17   `CLINE_SDK` env flag.
184. **Use `{appBaseUrl}`**, never hardcode `app.cline.bot`.
195. **Avoid `as` casts.** Use explicit conversion functions with tests. The
20   branded types in `apps/vscode/src/sdk/model-catalog/contracts.ts` exist so
21   casts are unnecessary outside parse/compute boundaries.
22 
23## Debug harness
24 
25- **Dismiss the Kanban/promo overlay** before any debug harness interaction.
26- **Use the command palette** to navigate tabs in the debug harness.
27