Bitter Frontier What agents just made possible, where the bottleneck moved, and what deserves attention.

Finding / deepseek-harness

2026-08-20-deepseek-harness-library-latest-still-frozen-sqlite-schema-17-has-no-migration

At SHA 141eb6fe (dsh-v0.1.0-rc.8), session-persistence-sqlite SCHEMA_VERSION is 17. At the parent pin 99f6f02 (rc.7) it is 15. A mismatch throws; the tree says the prerelease package supplies no migration. Default compositions still use JSONL; SQLite is opt-in.

npm library latest tags on the subagent packages remain 0.0.1-rc.1 (2026-08-10). That version has no dsh.bundle field. Window-close next was 0.1.0-rc.8. The CLI entry package is the one whose latest moved with rc.8. PyPI deepseek-harness-sdk published 0.1.0rc7 on 2026-08-18 and has no 0.1.0rc8.

Channel: preview-or-beta. Half: defect.

Operator consequence: pin @deepseek-ai/[email protected] (and the Codex twin). Bare latest is not a Profile Bundle. Do not open an rc.7 SQLite session database with rc.8.

Receipt

Finding metadata

Confidence
high

Run: 2026-08-20-brief-2026-08-17_2026-08-20-frontier-v0

Finding ID: 2026-08-20-deepseek-harness-library-latest-still-frozen-sqlite-schema-17-has-no-migration

Source links

Primary links, including exact changelog lines when available.

  1. DeepSeek Harness
    tagged commit file2026-08-20-deepseek-harness-library-latest-still-frozen-sqlite-schema-17-has-no-migrationdeepseek-ai/deepseek-harness / packages/session/session-persistence-sqlite/src/schema.tsgithub release2026-08-20-deepseek-harness-library-latest-still-frozen-sqlite-schema-17-has-no-migrationdeepseek-ai/deepseek-harness / dsh-v0.1.0-rc.8