[liususan091219]

Summary

#791 migrated voice + phone session logging to conversation.sqlite but left discord-voice still writing per-session JSONL (discord-voice-*.jsonl) plus discord-voice-metrics.jsonl. This finishes that migration — the piece #791 left undone.

• discord-voice-server.ts now calls recordConversation / recordSession from src/conversation-store.ts (which already declares 'discord-voice' as a session source).
• The two JSONL writers and the now-unused logLine / LOG_PATH helper are removed.

Net: +8 −28, one file. No behaviour change beyond the logging sink.

Closes #792.

Test plan

• tsc --noEmit passes
• Verified on Lucy's machine — discord-voice sessions record turns into conversation.sqlite; no new discord-voice-*.jsonl written

🤖 Generated with Claude Code

[liususan091219]

Pushed b413a60 addressing the review:

1. Reload-safety — discord-voice now also writes turns to logs/conversation.log alongside the conversation.sqlite write (mirroring the phone path). import-conversation-log.py --reload rebuilds the sqlite conversation table from conversation.log, so the text-log copy keeps discord-voice rows recoverable after a reload.
2. Channel diagnostics — guild + channel id are now encoded into the session id (discord_voice_<guild>_<channel>_<ts>), so channel-level info survives into the sessions table even though recordSession has no guild/channel field.
3. Docs — SKILL.md updated; the stale "metrics land in JSONL" line now describes the conversation.sqlite + conversation.log sinks.

On the tsc point: confirmed tsconfig.json only includes src/, so the standard tsc --noEmit doesn't cover this skills/ file — verified the change with a targeted tsc run on the file directly instead. (Adding skills/ to the typecheck scope is worth a separate follow-up.)

[liususan091219]

Pushed d3be3c8 for the re-review:

1. --reload guard — added discord-voice-server.ts to _LIVE_WRITER_PATTERNS in both import-conversation-log.py and import-session-metrics.py. discord-voice is now a live conversation.sqlite writer, so --reload's live-writer guard must detect it. (Added to the session-metrics importer too — discord-voice's recordSession writes the sessions table on the same race.)
2. Write order — conversation.log is now written before the conversation.sqlite mirror in the turn loop, so a turn never exists in sqlite without its log line.