From 329e5c3e2e90aaf4538c71bc3fd176ded70eaa24 Mon Sep 17 00:00:00 2001
From: Tianyi Cui <53024+tianyicui@users.noreply.github.com>
Date: Sat, 20 Jun 2026 13:51:09 +0800
Subject: [PATCH] docs(session-persistence): state coordinator-contract role as
 current fact (review)
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

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).
---
 packages/session-persistence/tests/coordinator-contract.ts | 5 ++---
 1 file changed, 2 insertions(+), 3 deletions(-)

diff --git a/packages/session-persistence/tests/coordinator-contract.ts b/packages/session-persistence/tests/coordinator-contract.ts
index 7769e6f5ec..9f42eebd10 100644
--- a/packages/session-persistence/tests/coordinator-contract.ts
+++ b/packages/session-persistence/tests/coordinator-contract.ts
@@ -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
  */