feat: add Kilo CLI provider

[metapeka]

Summary

Adds a new provider for Kilo CLI — the command-line agent (kilo serve, kilo run, kilo TUI). This is separate from the existing kilo-code provider.

Kilo CLI vs KiloCode (existing provider)

CodeBurn already has a kilo-code provider, but it reads from the VS Code extension only:

	kilo-code (existing)	kilo-cli (this PR)
Product	VS Code extension	CLI tool (kilo)
Storage	globalStorage/kilocode.kilo-code/tasks/ → ui_messages.json	~/.local/share/kilo/kilo*.db (SQLite)
Format	JSON task files	SQLite (same schema as OpenCode)
Data	Cline-family task entries	Session/message/part tables

They are completely different data sources with different formats — one does not cover the other.

Changes

• New file: src/providers/kilo-cli.ts — reads sessions from ~/.local/share/kilo/kilo*.db
• Updated: src/providers/index.ts — registered with lazy loading (needs better-sqlite3)

Details

• Same SQLite schema as OpenCode (Kilo CLI is a fork of OpenCode)
• Supports KILO_DATA_HOME env var for custom data directory
• Usage: codeburn report --provider kilo-cli

[Qodo-Free-For-OSS]

Hi, kilo-cli discovers DBs under ~/.local/share/kilo or KILO_DATA_HOME, but does not honor XDG_DATA_HOME like other sqlite providers do, so non-default XDG setups won’t be discovered unless users set KILO_DATA_HOME explicitly.

Severity: informational | Category: maintainability

How to fix: Check XDG_DATA_HOME too

Agent prompt to fix - you can give this to your LLM of choice:

Issue description

The new Kilo CLI provider does not consult XDG_DATA_HOME, which is the standard way to relocate ~/.local/share. This makes discovery inconsistent with other sqlite providers.

Fix Focus Areas

• src/providers/kilo-cli.ts[71-77]
  • Update base dir resolution to include process.env['XDG_DATA_HOME'] (while keeping dataDir and KILO_DATA_HOME overrides).
  • Keep the existing default fallback to ~/.local/share for users without env overrides.

---

Found by Qodo code review. FYI, Qodo is free for open-source.