docs(session-persistence): state coordinator-contract role as current fact (review)

Reword the suite's module doc to describe what it IS — each scenario lives
here once and runs per backend through the fixture — rather than narrating
that the scenarios were previously duplicated in the per-backend specs. Per
the repo doc-current-state convention (no process/history in comments).
This commit is contained in:
Tianyi Cui
2026-06-20 13:51:09 +08:00
parent 301a3d1233
commit 329e5c3e2e
@@ -20,9 +20,8 @@
* write path — never the storage primitives directly — so it runs unchanged for
* every backend (memory / jsonl / sqlite).
*
* Each scenario here was previously DUPLICATED in `jsonl.spec.ts` and
* `sqlite.spec.ts`; it now lives once and runs once per backend through the
* fixture. The per-backend specs keep ONLY their storage-mechanics tests.
* Each scenario lives here once and runs once per backend through the fixture;
* the per-backend specs keep ONLY their storage-mechanics tests.
*
* @module @deepseek-ai/dsh-session-persistence/tests/coordinator-contract
*/