Add Qoder IDE conversation adapter #307

Goal

Index local Qoder IDE conversations so they are searchable, resumable where the tool supports it, and counted in usage reports where it records tokens.

What is known

• Split from Add Qoder session adapter (CLI and IDE) #279, which covers the Qoder CLI (qodercli) source added in feat(adapters): add Qoder session adapter #305. The IDE stores conversations separately from the CLI transcripts under ~/.qoder/projects.
• IDE conversation history is reportedly under ~/.qoder/cache/projects/.../conversation-history/*.jsonl, with metadata in the IDE's state.vscdb (third-party reverse engineering, not documented). The China edition (formerly Tongyi Lingma) may use separate directories.
• For vendor models, Qoder CLI writes zero token counts to disk; whether the IDE records real token counts is unknown.

Prior art in other session readers:

• agentsview qoder.go
• agentsview qoder_paths.go

Done when

• recall sync indexes real Qoder IDE conversations: user and assistant messages, working directory, and timestamps; tool calls as session events where the source records them; token usage only where the source records real token counts.
• IDE conversations do not duplicate sessions already indexed by the qoder CLI source.
• The change is checked against at least one real session produced by installing the Qoder IDE locally and running a short task that reads a file, runs a shell command, and edits a file. The PR says what could not be verified.

Constraints

• One PR for this source. Follow src/adapters/AGENTS.md and the adapter guide in DEVELOPMENT.md; make check must pass.
• The storage details above come from other open-source session readers and have not been verified against Recall. Treat them as leads; the real files decide.