dsh: support session format v4 (DSH 0.2.0-rc.2 writes v4; every session is skipped)

[Aprilpl]

First of all, thank you for building and maintaining CodeBurn — the attention to detail shows, and it's a tool I open every day.

What happened

The dsh provider supports session formats v0–v3 (SUPPORTED_SESSION_FORMAT_VERSIONS in src/providers/dsh.ts), but current DSH (@deepseek-ai/dsh 0.2.0-rc.2) writes format v4 (session.v4.jsonl.zstd). Every session is skipped whole, so DSH contributes no usage anywhere and its tab doesn't even show up.

codeburn doctor stderr, verbatim:

codeburn: skipping DSH sessions written in session format version 4; upgrade codeburn.

doctor's verdict for the provider:

DeepSeek Harness: ERRORS (43 sessions skipped: unreadable or unsupported format; 0 sessions readable; 0 sampled parse failures)

The probe root itself is found (~/.dsh/sessions (exists)), so discovery works — the logs are just declined by version. Requesting the semantic reader update for v4 that docs/providers/dsh.md itself prescribes for format bumps.

What you expected

v4 logs to be parsed like v0–v3, with DSH usage counted in overview / daily / models / sessions like any other provider.

Output of codeburn --version

0.9.25

OS

macOS 15.7.2

Provider involved

DeepSeek Harness (dsh) — @deepseek-ai/dsh@0.2.0-rc.2 (npm global install), Node v22.21.1, default DSH_HOME (~/.dsh). All 43 session logs (~19 MB) are session.v4.jsonl.zstd; nothing at v0–v3 remains.

Steps to reproduce

1. Install DSH 0.2.0-rc.2 and use it — sessions land as ~/.dsh/sessions/<encoded-cwd>/<session-id>/session.v4.jsonl.zstd.
2. Run codeburn doctor (or any command).
3. stderr shows the version-4 skip notice; doctor reports all 43 sessions skipped, 0 readable; DSH usage stays empty everywhere.

Redacted JSONL or SQLite snippet

Session header (first line) of a v4 log, id/cwd redacted:

{"type":"session","version":4,"id":"<uuid>","createdAt":1790753880505,"cwd":"<redacted>","isSeeded":false,"delegationDepth":0,"agentPreset":"standard"}

The same logs read fine through the host's own sessionPersistence service (the path the community billing plugin uses), so the data is valid — CodeBurn declines it only on the version check.

DEBUG=1 output

DEBUG=1 codeburn doctor shows the same dsh-relevant lines as a normal run — the stderr notice above and the ERRORS verdict; no additional detail.

(Happy to share sanitized v4 logs if that helps.)

[ozymandiashh]

I hit this with the same 0.2.0-rc.2 install and opened #1612 — it admits v4 after verifying the reader's consumption surface against the official sessionFormatCatalog (recovery: 'strict', validation: 'current', @deepseek-ai/dsh-session-format-catalog@0.2.0-rc.2): seq coordinates, assistant/message usage placement, tagged end-seed inheritance, and retry slots are unchanged, so the semantic update ends up small. Fixtures validated with the same catalog, and a real 0.2.0-rc.2 log parses to totals that match the catalog artifact exactly. Happy to adjust if the maintainers see a gap.