fix(cli): handle SQLite lock errors

[marius-kilocode]

Multiple Kilo processes can share the global SQLite database, so transient writer contention can surface as SQLITE_BUSY after the database busy timeout. The local CLI hosts the server in the same process, and the generic defect logger currently writes the complete Effect cause to the terminal.

Classify SQLite lock timeouts as transient database-busy failures, return a concise retryable response for synchronous prompts, and publish the same concise message for asynchronous prompts. Other server defects retain the existing detailed diagnostics.

[kilo-code-bot]

Code Review Summary

Status: No Issues Found | Recommendation: Merge

Files Reviewed (5 files)

• .changeset/quiet-sqlite-lock-errors.md
• packages/opencode/src/kilocode/database/sqlite-error.ts
• packages/opencode/src/server/routes/instance/httpapi/handlers/session.ts
• packages/opencode/src/server/routes/instance/httpapi/middleware/error.ts
• packages/opencode/test/kilocode/database/sqlite-error.test.ts

---

_{Reviewed by kimi-k3 · Input: 139K · Output: 13.3K · Cached: 617K}

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