@modusensus/dsh-mneme 0.10.1 → 0.11.0

package/test/client.test.js

@@ -35,14 +35,45 @@ test("status card: hasData counts the archive metric", () => {
   assert.match(m[0], /d\.archive\?\.total/, "hasData must count archive.total, not just runs/active rows");
 });
 
-// The memory entry lives at the sidebar foot, not in the settings modal: the
-// migration must register into `sidebar.footer.action` (the list slot the
-// sidebar shell renders beside Settings) and must not keep a `settings.section`
-// registration, or the entry would appear twice under different hosts.
-test("memory entry registers into the sidebar foot slot", () => {
+// The memory entry is a first-class host panel now: `sidebar.panellist` puts a
+// glyph into the host's own panel list (the host row owns the button, the click
+// and aria-current) and `main` puts the library into the center column, side by
+// side with the conversation — the centered sheet is no longer the primary
+// surface (#559 follow-up; baleen does the same).
+//
+// Both seats are gated on the host declaring them, so the old footer entry has
+// to survive as the fallback for hosts without the seat pair. This test locks
+// the pair AND the fallback: dropping either one strands a whole host family
+// (new hosts get a sheet on top of the conversation again, old hosts lose the
+// entry entirely).
+test("memory entry registers the host panel seats and keeps the footer fallback", () => {
+  assert.ok(
+    clientSource.includes('ctx.slots.inject("sidebar.panellist"'),
+    "client must inject into sidebar.panellist (the host panel list)"
+  );
+  assert.ok(
+    clientSource.includes('name: "sidebar.panellist"'),
+    "the sidebar seat must be registered under its real slot name"
+  );
+  // main 的 key 必须与侧栏 id 逐字相同：宿主 PanelRow 点一下就是
+  // layout.selectPanel(id)，它在 main 槽里按 options.key 找 entry，对不上直接抛。
+  // 两处改成同一个常量以外的任何写法（比如 main 用 "mneme"、侧栏用 "dsh-mneme"）
+  // 面板点了没反应且控制台报 "main panel ... is not registered"。
+  assert.ok(
+    clientSource.includes('key: "dsh-mneme"'),
+    "the main seat key must match the sidebar seat id verbatim"
+  );
+  assert.ok(
+    clientSource.includes('ctx.slots.spec("sidebar.panellist")'),
+    "the footer fallback must be gated on the host actually declaring the panel seat"
+  );
+  assert.ok(
+    clientSource.includes("dropFooterSeat()"),
+    "once the panel seat exists the footer entry must be torn down, or the sidebar shows two memory entries"
+  );
   assert.ok(
     clientSource.includes('ctx.slots.inject("sidebar.footer.action"'),
-    "client must inject into sidebar.footer.action"
+    "client must keep injecting into sidebar.footer.action as the old-host fallback"
   );
   assert.equal(
     clientSource.includes('"settings.section"'),
@@ -51,6 +82,153 @@ test("memory entry registers into the sidebar foot slot", () => {
   );
 });
 
+// chorography（仓库地志）第二个座位（M1）：与记忆面板同一个 panellist inject 块
+// 里注册，成对规则逐字相同——id 与 main 的 key 必须同为 "dsh-mneme-wiki"，否则
+// 宿主点面板行直接抛 "main panel … is not registered"（#562 在记忆座位上实测过
+// 的同一堵墙）。座位无条件注册（P11）：inject 同名二次注册的 cordis 语义没验证
+// 过，不赌；开关关时由内容层渲染空态（路由 409 disabled），生效走重启纪律。
+test("chorography wiki entry registers its own seat pair in the same panellist block", () => {
+  assert.ok(
+    clientSource.includes('id: "dsh-mneme-wiki"'),
+    "the wiki sidebar seat must use its own id"
+  );
+  assert.ok(
+    clientSource.includes('key: "dsh-mneme-wiki"'),
+    "the wiki main seat key must match the wiki sidebar id verbatim"
+  );
+  assert.ok(
+    clientSource.includes("h(WikiMainPanel, { t })"),
+    "the wiki main seat must render WikiMainPanel"
+  );
+  assert.ok(
+    clientSource.includes('phase: "disabled"'),
+    "with chorographyEnabled off the wiki page must render the disabled empty state (409 from /choro/repos)"
+  );
+  // wiki 座位与记忆座位的清理在同一把扫帚下：漏一个就留下一个挂着的 glyph，
+  // 宿主折叠该槽后指向一个死面板。
+  assert.ok(
+    /return \(\) => \{\s*disposeGlyph\(\);\s*disposeMain\(\);\s*disposeWikiGlyph\(\);\s*disposeWikiMain\(\);/.test(clientSource),
+    "the panellist cleanup must dispose both seat pairs"
+  );
+});
+
+// 上一条锁的是「代码里有没有这两套座位」，这条锁「装/卸真的按条件跑」。
+// 回归表现（都靠字符串锁抓不到）：
+//  · 新宿主上两套都装 → 侧栏两颗记忆入口；
+//  · 宿主先声明 panellist、后来撤掉/换形态 → 回落不装回来，入口整个消失；
+//  · 回落被重复装入 → footer 里叠两个按钮；
+//  · 卸载 panellist 座位时忘了连带卸 main → 侧栏没图标但 activePanelId 仍指向
+//    一个已死面板（宿主 retainMainPanels 会把它复位成会话，界面上看不出来，
+//    但用户的「回到记忆库」状态被悄悄清掉）。
+test("panel seats: the fallback mounts and unmounts with the host's declaration", () => {
+  // 匹配范围必须一直吃到最后一条 inject 的收尾：非贪婪到第一个 \n      });
+  // 会停在 panellist 那段的中途，footer 回落根本进不了沙箱，测出来的永远不会红。
+  const src = clientSource.match(/const hostHasPanelSeat = \(\) =>[\s\S]*?ctx\.slots\.inject\("sidebar\.footer\.action"[\s\S]*?\n      \}\);/);
+  assert.ok(src, "the seat block must be extractable verbatim");
+  const boot = new Function("ctx", "t", "h", `${src[0]}\n return { hostHasPanelSeat };`);
+  const makeCtx = (specFor) => {
+    const regs = [];
+    const ctx = {
+      slots: {
+        spec: (key) => specFor(key),
+        inject: (key, cb) => { ctx.injected.push({ key, cb }); return () => {}; },
+        register: (opts, comp) => {
+          const rec = { opts, comp, alive: true };
+          regs.push(rec);
+          return () => { rec.alive = false; };
+        }
+      },
+      injected: []
+    };
+    return { ctx, regs };
+  };
+  const alive = (regs, name) => regs.filter((r) => r.alive && r.opts.name === name).length;
+
+  // 宿主只在「那个槽已被声明」时才跑 inject 的回调，所以这里也只在对应的
+  // spec 存在时点火：一把全点会把新座位的注册塞进老宿主，测出来的就不是真行为。
+  const fire = (ctx, key) => ctx.injected.filter((i) => i.key === key).map((i) => i.cb());
+
+  // 新宿主：panellist 已声明。panellist + main 各两份（记忆 + chorography 两个
+  // 座位，M1），每对各自 id/key 逐字同名；footer 回落不装。
+  {
+    const { ctx, regs } = makeCtx((key) => (key === "sidebar.panellist" ? { kind: "list" } : undefined));
+    const api = boot(ctx, (k) => k, () => null);
+    assert.equal(api.hostHasPanelSeat(), true);
+    const disposes = fire(ctx, "sidebar.panellist");
+    fire(ctx, "sidebar.footer.action");
+    assert.equal(disposes.length, 1);
+    const ids = (name) => regs.filter((r) => r.alive && r.opts.name === name).map((r) => r.opts.id ?? r.opts.key).sort();
+    assert.equal(alive(regs, "sidebar.panellist"), 2, "memory + wiki glyphs");
+    assert.deepEqual(ids("sidebar.panellist"), ["dsh-mneme", "dsh-mneme-wiki"], "每对座位各自 id 逐字唯一");
+    assert.equal(alive(regs, "main"), 2, "memory + wiki pages");
+    assert.deepEqual(ids("main"), ["dsh-mneme", "dsh-mneme-wiki"], "main key 与侧栏 id 逐字同名");
+    assert.equal(alive(regs, "sidebar.footer.action"), 0, "the footer fallback must not mount on a host that has the seat");
+  }
+
+  // 老宿主：没有 panellist。回落必须装上，且只装一份。
+  {
+    const { ctx, regs } = makeCtx(() => undefined);
+    const api = boot(ctx, (k) => k, () => null);
+    assert.equal(api.hostHasPanelSeat(), false);
+    fire(ctx, "sidebar.footer.action");
+    assert.equal(alive(regs, "sidebar.panellist"), 0);
+    assert.equal(alive(regs, "main"), 0);
+    assert.equal(alive(regs, "sidebar.footer.action"), 1, "old hosts keep exactly one footer entry");
+  }
+
+  // 座位消失：卸载 panellist 之后回落必须自己装回来，否则那台宿主上没有入口。
+  // 真实顺序是「声明先没了（spec 变 undefined），再把 entry 的 disposer 跑掉」，
+  // 所以这里要让 spec 跟着一起变——判据读的是当下这次 spec()，不是启动时那次。
+  {
+    let declared = true;
+    const { ctx, regs } = makeCtx(() => (declared ? { kind: "list" } : undefined));
+    boot(ctx, (k) => k, () => null);
+    const disposes = fire(ctx, "sidebar.panellist");
+    assert.equal(alive(regs, "sidebar.footer.action"), 0);
+    declared = false;
+    disposes.forEach((d) => d());
+    assert.equal(alive(regs, "sidebar.panellist"), 0);
+    assert.equal(alive(regs, "main"), 0, "unmounting the seat must tear down the main panel too");
+    assert.equal(alive(regs, "sidebar.footer.action"), 1, "the fallback must come back when the seat disappears");
+  }
+});
+
+// 侧栏那颗 glyph 是「宿主面板行里的图标」，不是按钮：宿主 PanelRow 已经渲染
+// button + aria-label + Tooltip + aria-current，插件再套一层按钮就会出现两颗
+// 可聚焦元素（Tab 停两次，读屏报两次），而且我们这层的 onClick 还得自己去调
+// layout.selectPanel —— 那是宿主自己的活。
+// 主面板同理不自带「回到会话」：宿主 openSession / 新建会话都走 selectPanel(null)，
+// 用户点侧栏任何会话行就回去了（baleen 也不做这颗按钮）。
+function sliceComponent(name) {
+  const start = clientSource.indexOf("    function " + name + "(");
+  assert.notEqual(start, -1, name + " must exist as a component");
+  // 组件体到下一个「四空格缩进的 }」为止：与本文件 :3060 那条静态扫描同一套缩进约定。
+  const end = clientSource.indexOf("\n    }", start);
+  assert.notEqual(end, -1, name + " must be a plain function component");
+  return clientSource.slice(start, end + 7);
+}
+
+test("panel seats hand the host a glyph and a page, not a second button or a close affordance", () => {
+  const glyph = sliceComponent("SidebarPanelGlyph");
+  assert.equal(/h\("button"/.test(glyph), false,
+    "the sidebar glyph must not render its own button (the host panel row owns it)");
+  assert.ok(glyph.includes("mneme-paneliglyph"),
+    "the glyph needs its own root class to carry the conflict badge and the semantic color layer");
+  assert.ok(glyph.includes("h(ConflictBadge, { pending })"),
+    "the panel-list entry must keep the pending-conflict badge");
+
+  const main = sliceComponent("MnemeMainPanel");
+  assert.ok(main.includes("h(MemoryExplorer, { t })"),
+    "the center-column page must reuse the same MemoryExplorer");
+  assert.ok(main.includes('className: "mneme-panel"'),
+    "the page needs the fill container (the host main slot only gives min-width:0 + overflow:hidden)");
+  // 面板切换归宿主：PanelRow 点一下就是 layout.selectPanel(id)，openSession /
+  // 新建会话又都是 selectPanel(null)。插件自己再调一次会把用户的导航意图打断
+  // （宿主那边 selectPanel 还会 abort 当前 navigation）。
+  assert.equal(clientSource.includes("ctx.layout.selectPanel"), false,
+    "the plugin must never call layout.selectPanel — the host row and openSession already do");
+});
+
 // The tab era is over: the in-conversation memory tab fought the floating
 // composer and squeezed the session layout, so the library no longer
 // registers as a conversation view. The sidebar entry opens the centered
@@ -182,6 +360,32 @@ test("sidebar entry portals into the host panel list with footer fallback", () =
   );
 });
 
+// Issue #573：宿主 0.2.2 起把面板列表的「更多」行（PanelMoreMenu）也追加进同一个
+// nav.panelList，于是组尾不再是面板行。仍按「追加到组尾」落位时，入口会排到
+// 「更多」下面，菜单一展开就把入口盖住——用户看到的是「记忆入口不见了」。
+// 回归表现：入口掉到「更多」之后、或展开菜单后入口被遮。
+// 落位改成「插在『更多』之前」，判据与其余几处一致走 [class*=] 前缀，不写死
+// 宿主哈希类名；老宿主没有该行时必须原样退回追加组尾，不能整块不落位。
+test("sidebar entry lands above the host's More row, not below it", () => {
+  assert.ok(
+    clientSource.includes(`list.querySelector('[class*="moreAnchor"]')`),
+    "the More row must be located by class prefix like every other host class"
+  );
+  assert.ok(
+    clientSource.includes("list.insertBefore(created, more)"),
+    "the wide entry must insert before the More row so the expanded menu cannot cover it"
+  );
+  assert.ok(
+    clientSource.includes("created.nextElementSibling === more"),
+    "placement must stay idempotent against the More anchor so the observer never writes on steady state"
+  );
+  // 老宿主没有「更多」行：追加组尾的分支必须还在，否则那些宿主上入口根本不落位。
+  assert.ok(
+    clientSource.includes("created === list.lastElementChild"),
+    "hosts without a More row must keep the append-to-tail fallback"
+  );
+});
+
 // Issue #130: ecosystem plugins (task board, skill explorer, …) inject their
 // own entries right after the New-Session row, and late inserters land above
 // earlier ones — a fixed "before regionArea" slot degrades into the tail of
@@ -709,6 +913,45 @@ test("token flow: 7-day bars pad to a continuous week, heatmap uses its own 56-d
   );
 });
 
+// 8 周沉淀图（热力右侧那块空白）是第二条独立数据源，四处静默失效都会让图看着
+// 正常但结论错掉，所以照样锁形状：
+// ① 必须自带 days=56 请求——复用 days=7 的响应会让 8 根柱子只有 1 根有数据；
+// ② sinkStats 为 null（未到）与 {}（已知为空）必须分开，否则加载态先画 8 根
+//    零高柱子，再「长出来」，用户看到的是一次假抖动；
+// ③ 图例/柱体不能在三总量全 0 时照画——那等于把「最近没有东西进库」这句
+//    谎话说成事实；
+// ④ 两列并排必须带窄容器回落，否则 480px 侧栏里热力与沉淀互相压扁。
+test("consolidation chart: own 56-day window, null-vs-empty split, and a narrow-container fallback", () => {
+  assert.ok(
+    clientSource.includes("semantic/consolidation-stats?days=56"),
+    "the consolidation chart must issue its own days=56 request"
+  );
+  assert.ok(
+    /if \(!sinkStats\) return null;/.test(clientSource),
+    "an unloaded consolidation response must stay null, else the loading state paints 8 empty weeks"
+  );
+  assert.ok(
+    /sinkDays && !sinkError/.test(clientSource),
+    "labels/legend must be gated on a loaded, non-erroring response"
+  );
+  assert.ok(
+    /sinkAddedTotal \+ sinkMergedTotal \+ sinkArchivedTotal === 0/.test(clientSource),
+    "an all-zero window must render the empty state, not eight zero-height bars"
+  );
+  // 两列：热力按内容宽 auto，沉淀吃剩余；窄容器回落单列。
+  assert.ok(
+    clientSource.includes("grid-template-columns:auto minmax(0,1fr)"),
+    "the heat row and the consolidation chart must sit in two columns"
+  );
+  assert.ok(
+    clientSource.includes("@container (max-width:960px){.mneme-flowrow{grid-template-columns:minmax(0,1fr)}}"),
+    "two columns must collapse to one in a narrow container"
+  );
+  // 两根柱的语义色必须走语义层，不能直接拿宿主 label token 当填充色（#178）。
+  assert.ok(clientSource.includes(".mneme-sinkbar--added{background:var(--mneme-chart-3)}"));
+  assert.ok(clientSource.includes(".mneme-sinkbar--merged{background:var(--mneme-chart-2)}"));
+});
+
 // 巩固/睡眠模型路由 UI：下拉数据来自宿主侧已注册适配器（/llm-providers，
 // 云端插件侧端点），「测试连通性」走 POST /test-model 真实最小调用。旧后端
 // 端点 404 时必须回退纯文本输入——前端自门控，不挡旧版本。
@@ -1197,14 +1440,17 @@ test("conflict queue: empty-state explainer card", () => {
   }
 });
 
-// 状态卡待处理高亮 + 侧边栏入口 badge（挂 portal 与回退两个按钮）。
-test("conflict queue: actionable status card and sidebar entry badge", () => {
+// 状态卡待处理高亮 + 三个入口的 badge：宿主面板行图标（SidebarPanelGlyph）、
+// 老宿主的 portal 入口（SidebarTopEntry）、footer 回退按钮（SidebarFallbackTrigger）。
+// 三个都吃同一个模块级计数，所以这里锁的是「一个都没漏接」——漏一个的那台宿主
+// 上红点就不出现，而抽屉里仍然显示有待裁决冲突。
+test("conflict queue: actionable status card and every sidebar entry badge", () => {
   assert.ok(clientSource.includes('"mneme-conflict-jump"'), "pending>0 card must carry the highlight class");
   assert.ok(clientSource.includes("mneme-statuscard--actionable"), "highlight CSS must exist");
-  assert.ok((clientSource.match(/h\(ConflictBadge, \{ pending \}\)/g) || []).length === 2,
-    "badge must be wired into both entry buttons");
-  assert.ok((clientSource.match(/= useConflictBadgeCount\(\);/g) || []).length === 2,
-    "both entry components must subscribe to the shared badge count");
+  assert.equal((clientSource.match(/h\(ConflictBadge, \{ pending \}\)/g) || []).length, 3,
+    "badge must be wired into the panel-list glyph and both legacy entry surfaces");
+  assert.equal((clientSource.match(/= useConflictBadgeCount\(\);/g) || []).length, 3,
+    "all three entry components must subscribe to the shared badge count");
   assert.ok(clientSource.includes('"/api/dsh-mneme/dream-status"'), "badge must reuse the dream-status endpoint");
 });
 
@@ -1413,7 +1659,7 @@ test("panel can create a memory by hand: menu entry wired to the dialog", () =>
   // 入口在「更多操作」菜单里，且菜单项真的调用 setCreateOpen(true)——只断言文案
   // 存在的话，把 onClick 摘掉测试照样绿。
   assert.ok(clientSource.includes('"memory.explorer.newMemory"'), "menu entry label must exist");
-  assert.ok(/role: "menuitem", onClick: \(\) => \{ setCreateOpen\(true\); setMenuOpen\(false\); \}/.test(clientSource),
+  assert.ok(/role: "menuitem", (?:disabled: bootstrapBusy, )?onClick: \(\) => \{ setCreateOpen\(true\); setMenuOpen\(false\); \}/.test(clientSource),
     "the menu item must actually open the create dialog");
   assert.ok(clientSource.includes("const [createOpen, setCreateOpen] = useState(false)"),
     "the dialog needs its own open state");
@@ -2211,9 +2457,8 @@ test("update-check status names match the backend classify contract verbatim", (
     "the backend must register the version-check route");
 });
 
-// 画像提取草稿（#497）面板面：路由对齐、四种结局各有自己的话、以及「采用」必须把草稿
-// 文本直接交给保存。最后一条防的是一个具体陷阱——保存函数带默认参数时，把函数本身当
-// onClick 处理器会把 click 事件当成要存的文本存进去。
+// 画像提取草稿（#497）面板面：路由对齐、四种结局各有自己的话、按钮坐在哪张卡上、
+// 以及草稿**只出副本**（2026-11-04 改口径：不再把草稿写进画像字段）。
 test("profile extraction ships its button, distinct outcomes and correct save wiring", () => {
   const apiSource = readFileSync(join(root, "src/api.js"), "utf8");
   assert.ok(clientSource.includes('apiFetch("/api/dsh-mneme/profile/extract"'),
@@ -2235,7 +2480,10 @@ test("profile extraction ships its button, distinct outcomes and correct save wi
     "memory.settings.profileDraftTitle",
     "memory.settings.profileDraftRows",
     "memory.settings.profileDraftTruncated",
-    "memory.settings.profileDraftApply",
+    "memory.settings.profileDraftCopy",
+    "memory.settings.profileDraftCopied",
+    "memory.settings.profileDraftCopyHint",
+    "memory.settings.profileDraftCopyFailed",
     "memory.settings.profileDraftDiscard",
     "memory.features.profileExtractEnabled",
     "memory.features.profileExtractEnabled.hint"
@@ -2246,8 +2494,40 @@ test("profile extraction ships its button, distinct outcomes and correct save wi
   assert.ok(/group\.enhance[\s\S]{0,700}"profileExtractEnabled"/.test(clientSource),
     "FEATURE_GROUPS group.enhance must carry profileExtractEnabled");
 
-  // 采用草稿：显式传文本；保存按钮也不能把 click 事件当参数传进去。
-  assert.ok(clientSource.includes("if (await saveProfile(text))"), "applying a draft must commit state only after a verified save");
+  // 位置锁（2026-11-04）：提取按钮属于「Agent 眼中的你」卡，不属于「用户画像」卡。
+  // 此前没有任何用例锁位置——整块 UI 搬走测试也不会红，这正是它被放错地方却一直绿的原因。
+  // 锁法：三处锚点的先后顺序 + 两张卡标题之间不许出现 profileExtract。
+  const profileCardIdx = clientSource.indexOf('h("div", { className: "mneme-set-title" }, t("memory.settings.profile"))');
+  const personaViewIdx = clientSource.indexOf('h("div", { className: "mneme-set-title" }, t("memory.settings.personaView"))');
+  const extractButtonIdx = clientSource.indexOf('t("memory.settings.profileExtract")');
+  assert.ok(profileCardIdx > 0 && personaViewIdx > profileCardIdx && extractButtonIdx > personaViewIdx,
+    "the extract button must render inside the persona-view card, which comes after the user-profile card");
+  assert.ok(!clientSource.slice(profileCardIdx, personaViewIdx).includes("profileExtract"),
+    "the user-profile card must not carry any extract UI");
+
+  // 只出副本（2026-11-04 桉桉定的口径）：草稿不许再走落库路径。此前 applyProfileDraft 会
+  // 直接 PUT /profile —— 把用户手写的那份覆盖掉，且没有撤销。
+  assert.ok(clientSource.includes("function copyProfileDraft()"), "the draft action must be a copy, not a save");
+  assert.ok(!clientSource.includes("if (await saveProfile(text))"), "a draft must never be committed to the profile field");
+  assert.ok(clientSource.includes("copyProfileDraftFallback(text)"),
+    "the draft action must copy the draft text, with a fallback when the clipboard API is unavailable");
+  // 复制是这条路径唯一的产出：静默失败等于让用户以为复制成功、粘贴时拿到旧文本。
+  assert.ok(clientSource.includes('t("memory.settings.profileDraftCopyFailed")'),
+    "a failed copy must say so instead of silently doing nothing");
+  // 光 announce() 不够：那个 live region 是 1px 裁剪元素，只有屏幕阅读器读得到。
+  // 视力正常的用户看到按钮文字不变、页面不变，会以为复制成功，粘贴时拿到旧内容。
+  assert.ok(clientSource.includes("const [profileDraftCopyFailed, setProfileDraftCopyFailed] = react.useState(false)"),
+    "the failed copy needs its own state, not just an announce() to a hidden live region");
+  assert.ok(clientSource.includes("setProfileDraftCopyFailed(true)"),
+    "the failure branch must flip the visible state");
+  const copyFailedIdx = clientSource.indexOf("profileDraftCopyFailed ? h(\"span\"");
+  assert.ok(copyFailedIdx > 0, "the failure must render as visible text near the copy button, not only in the live region");
+  assert.ok(clientSource.slice(copyFailedIdx, copyFailedIdx + 220).includes('role: "alert"'),
+    "the visible failure text should announce itself to assistive tech too");
+  // 颜色走语义层：宿主 label-tertiary 这类低对比层当正文色会掉到 AA 以下（#178）。
+  assert.ok(clientSource.slice(copyFailedIdx, copyFailedIdx + 220).includes('style: { color: "var(--mneme-danger)" }'),
+    "the failure text must use the --mneme-danger semantic layer, not a raw host token");
+  // 采用路径没了之后，保存按钮仍不能把 click 事件当参数传进去（保存函数带默认参数）。
   assert.ok(!clientSource.includes("onClick: saveProfile }"), "the save button must not receive the click event as its value argument");
   // apiFetch 是 fetch 的薄壳：非 2xx 不抛。画像这条以前没判 res.ok（同页的 persona
   // 一直判），于是服务端 403/413 时界面照样闪「画像已保存」。
@@ -2258,6 +2538,58 @@ test("profile extraction ships its button, distinct outcomes and correct save wi
   assert.ok(clientSource.includes('"no-route" ? "noroute"'), "no-route must map to its own panel outcome, not the generic failure");
 });
 
+// 复制的竞态（CodeRabbit #559 第二轮）：剪贴板是异步的，回调属于哪一份草稿必须能认出来。
+// 复制 A 还没落地时又提取出草稿 B，A 的回调就会在 B 上打勾或报错——B 一个字都没被复制过，
+// 而「已复制」会挂 1.5 秒，于是同一屏上可能出现「已复制」和「复制没成功」两句相反的话。
+test("profile draft copy ticket keeps stale copy callbacks off a newer draft", () => {
+  const copySrc = clientSource.slice(
+    clientSource.indexOf("function copyProfileDraft("),
+    clientSource.indexOf("function copyProfileDraft(") + 2000
+  );
+  assert.ok(clientSource.includes("const profileCopyTicket = react.useRef(0)"),
+    "each copy attempt needs a ticket so a stale clipboard callback can be told apart");
+  assert.ok(copySrc.includes("const ticket = ++profileCopyTicket.current"),
+    "every attempt must take a fresh ticket before the async clipboard call");
+  assert.ok(copySrc.includes("const current = () => ticket === profileCopyTicket.current"),
+    "the callback must compare its ticket against the live one");
+  // 成功与失败两条回调都要判票：只判一条，另一条照样会污染新草稿。
+  assert.equal((copySrc.match(/if \(\(?!current\(\)\)\) return;/g) || []).length >= 2 ||
+    (copySrc.match(/if \(!current\(\)\) return;/g) || []).length >= 2, true,
+    "both the success and failure callbacks must drop themselves when their ticket is stale");
+  // 失败必须撤掉「已复制」：成功态能挂 1.5 秒，这期间重试失败会同时显示两句相反的话。
+  const failSrc = copySrc.slice(copySrc.indexOf("const failed = () =>"));
+  assert.ok(failSrc.slice(0, 200).includes("setProfileDraftCopied(false)"),
+    "a failed retry must clear the lingering copied state instead of showing both messages");
+  // 换草稿（重新提取 / 丢弃）都要让旧票作废，并清掉旧提示。
+  const extractSrc = clientSource.slice(clientSource.indexOf("async function extractProfileDraft("));
+  assert.ok(extractSrc.slice(0, 400).includes("profileCopyTicket.current += 1"),
+    "starting a new extraction must invalidate the previous copy attempt");
+  const discardSrc = clientSource.slice(clientSource.indexOf('t("memory.settings.profileDraftDiscard")') - 400);
+  assert.ok(discardSrc.slice(0, 400).includes("profileCopyTicket.current += 1") &&
+    discardSrc.slice(0, 400).includes("setProfileDraftCopyFailed(false)"),
+    "discarding the draft must clear both the ticket and the error text it left behind");
+});
+
+// 实体总数读不到时不许拿切片长度冒充（CodeRabbit #559 第二轮）：路由回落时把
+// entities.length 写进 total，面板再把它当全库数显示，等于把「这次取回多少」说成
+// 「全库有多少」——那正是这条路由原来「永远 500」的错法换个方向复发。
+test("entity card shows an unknown total instead of passing a slice off as the library", () => {
+  for (const key of ["memory.status.entitiesUnknown"]) {
+    const occurrences = clientSource.split(`"${key}"`).length - 1;
+    assert.ok(occurrences >= 2, `i18n key ${key} must exist in both zh and en (got ${occurrences})`);
+  }
+  const cardSrc = clientSource.slice(
+    clientSource.indexOf("function EntitiesStatusCard("),
+    clientSource.indexOf("function EntitiesStatusCard(") + 2600
+  );
+  assert.ok(cardSrc.includes("j.totalExact === true"),
+    "the card must gate the big number on the backend's exactness flag");
+  assert.ok(cardSrc.includes('state.totalKnown === false ? "—"'),
+    "an inexact total must render as unknown, not as a plausible-looking number");
+  assert.ok(cardSrc.includes('t("memory.status.entitiesUnknown")'),
+    "the card must say why the total is missing, not just blank it out");
+});
+
 // Issue #521：degraded 轮的跳过明细必须能在面板上看见。此前 skipped 只落库，
 // 响应里没有聚合，status: degraded + applied: 3 从外面看完全是健康轮的样子——
 // 一整类动作 100% 被拦要自己写 SQL 才看得出，那个 bug 跑了一整天才被发现。
@@ -2714,6 +3046,256 @@ test("entity graph surfaces the passive-confirmation review surface (issue #24)"
 //   · 现有用例——它们读的是源码字符串，从不执行组件。
 // 所以这里不锁某一个名字，而是把**每个组件里「调了 setter 却没有声明」**这件事整体扫一遍，
 // 才对得起「别再有人把 state 放进隔壁组件」这个意图。
+test("panel exposes the bootstrap entry and the config-key coverage card (issue #386)", () => {
+  // 第 6 条：从目录引导。后端从 #220 就在，缺的是面板入口——所以锁四件事：
+  // 菜单项存在、弹层真的挂在菜单上、请求打的是新路由、错误分码显示。
+  assert.ok(
+    /setBootstrapOpen\(true\); setMenuOpen\(false\)/.test(clientSource),
+    "the overflow menu needs a bootstrap item that opens its dialog"
+  );
+  assert.ok(
+    /bootstrapOpen && h\(BootstrapDialog, \{/.test(clientSource),
+    "the dialog must actually be mounted, not just declared"
+  );
+  // 菜单按钮的 onClick 里必须也关掉它，否则点「⋯」会留下上一个弹层。但它现在带一个
+  // 条件：引导请求在飞时不关（否则等于绕过弹层里那两道 busy 禁用的锁，评审
+  // #4452245292）。所以这里锁的是「有条件地关」，不是无条件关。
+  assert.ok(
+    /setImportOpen\(false\);\s*\n\s*\/\/[\s\S]{0,200}?if \(!bootstrapBusy\) setBootstrapOpen\(false\);/.test(clientSource),
+    "the overflow toggle must close the bootstrap dialog when it is not busy"
+  );
+  // 父组件必须真的把这个标志接下来，否则上面那句恒为真（undefined → !undefined）。
+  assert.ok(
+    /const \[bootstrapBusy, setBootstrapBusy\] = useState\(false\)/.test(clientSource),
+    "the parent needs a bootstrapBusy flag for the guard above to mean anything"
+  );
+  assert.ok(
+    /onBusyChange: reportBootstrapBusy/.test(clientSource),
+    "the dialog must report its busy state up, or the guard reads a stale false"
+  );
+  // 这个转发函数必须同步调外层、且身份稳定：走 useEffect 转报的话要等渲染提交后
+  // 才跑，中间那一拍外层读到 false（#4452539705 的老毛病）；而若每渲染新建一个，
+  // BootstrapDialog 的卸载 effect（依赖 [onBusyChange]）会在父组件每次重渲染时
+  // 先跑 cleanup 调一次 onBusyChange(false)——而父组件正是在置 busy 之后重渲染的。
+  assert.ok(
+    /const reportBootstrapBusy = useCallback\(\(v\) => \{[\s\S]{0,200}?setBootstrapBusy\(v\);[\s\S]{0,200}?onBusyChange\(v\);/.test(clientSource),
+    "the forwarder must set both levels synchronously and keep a stable identity"
+  );
+  // 会挂弹层的菜单项在忙碌时必须禁用（评审 #4452539738）：新建 / 导入 / 引导 / 分享 /
+  // 接收共五处，加上「⋯」按钮自己（见下），再加上四个视图标签（评审 #4453639221，
+  // 源码里那一处在 `.map` 里，一处覆盖四个）。数个数而不是逐个锁字符串——少一处就
+  // 等于留了一条绕过弹层的路，而这条路的代价是用户看不到自己那次引导的结果。
+  assert.equal(
+    clientSource.split("disabled: bootstrapBusy").length - 1,
+    7,
+    "every dialog-mounting menu item, the overflow toggle and the view tabs must be disabled while bootstrap is busy"
+  );
+  // 视图标签离开 memory 会连 `.mneme-xtools` 与其中的 BootstrapDialog 一起卸载
+  // （评审 #4453639221）。两道锁都要有：`disabled` 是第一道，onClick 走 leaveMemory
+  // 是第二道——将来有人给标签换一种可点的实现时，函数里的判断还在。
+  assert.ok(
+    /disabled: bootstrapBusy,[\s\S]{0,300}?onClick: \(\) => leaveMemory\(s\.key\)/.test(clientSource),
+    "view tabs must route through leaveMemory, not setView directly"
+  );
+  assert.ok(
+    /const leaveMemory = \(key\) => \{[\s\S]{0,120}?if \(bootstrapBusy\) return;[\s\S]{0,80}?setView\(key\);/.test(clientSource),
+    "leaveMemory must refuse to switch views while a bootstrap request is in flight"
+  );
+  // 视图标签不是唯一的出口：记忆视图里那个实体 chip（`openGraphFor`）也把 view 切到
+  // "entity"，同样会把 BootstrapDialog 一起卸掉。这条是变异自证抓出来的——四个变异体
+  // 里只有它活下来，说明我先前只锁了标签、漏了这条真实的旁路。
+  assert.ok(
+    /const openGraphFor = \(name\) => \{[\s\S]{0,120}?if \(bootstrapBusy\) return;/.test(clientSource),
+    "the entity chip's graph jump must also refuse to leave memory while bootstrap is busy"
+  );
+  // 「⋯」按钮自己也要禁用（评审 #4453225585）：菜单与引导弹层共用同一个绝对定位锚点、
+  // 同一层 z-index，弹层排在菜单之后渲染，会把菜单顶上那两项导出盖住——它们没有
+  // disabled，却点不到。上一轮我以为「导出项不挂弹层所以照旧可点」就没事了，那是错的：
+  // 可点的是菜单项本身，但它被遮住了。不开菜单，才不存在「可点但被遮住」。
+  assert.ok(
+    /title: t\("memory\.explorer\.more"\),[\s\S]{0,600}?disabled: bootstrapBusy,[\s\S]{0,200}?onClick: \(\) => \{\s*\n\s*setMenuOpen\(!menuOpen\);/.test(clientSource),
+    "the overflow toggle must be disabled while bootstrap is busy, so the dialog never covers its items"
+  );
+  const bsIdx = clientSource.indexOf("function BootstrapDialog");
+  // 切到下一个弹层为止，而不是给一个拍脑袋的字符数：这轮改动静悄悄把窗口撑破了，
+  // 断言于是在一个截断的片段上做，失败信息还指着「输入框没禁用」这种不存在的毛病。
+  const bsEnd = clientSource.indexOf("// --- 分享包弹层 ---", bsIdx);
+  const bsBody = clientSource.slice(bsIdx, bsEnd > bsIdx ? bsEnd : bsIdx + 4200);
+  assert.ok(bsIdx > 0, "BootstrapDialog must exist");
+  // 忙碌状态必须**同步**报上去（评审 #4452539705）：只靠上面那个 useEffect 的话，
+  // 它要等这次渲染提交后才跑，中间那一拍父组件的 bootstrapBusy 还是 false，此时点
+  // 「⋯」仍会把弹层卸掉，请求的成功或失败就再没有地方显示。
+  assert.ok(
+    /setBusy\(true\);[\s\S]{0,400}?onBusyChange\(true\);/.test(bsBody),
+    "busy must be reported up synchronously, not only through the effect"
+  );
+  assert.ok(
+    /apiFetch\("\/api\/dsh-mneme\/bootstrap"/.test(bsBody),
+    "the dialog must POST to the bootstrap route"
+  );
+  assert.ok(
+    /JSON\.stringify\(\{ dir \}\)/.test(bsBody),
+    "the request body carries the raw dir string"
+  );
+  // 请求在飞时锁住三处：输入框、取消、提交。少了输入框那一处，用户改成 B 之后回来的
+  // 提示会贴在 B 旁边、而它讲的是 A 的结果（评审 #4452245279）。断言从 `type: "text"`
+  // 一路看到 `onChange`，而不是只说「附近有个 disabled: busy」——后者底下的按钮也能满足。
+  assert.ok(
+    /type: "text",[\s\S]{0,400}?disabled: busy,[\s\S]{0,400}?onChange: \(e\) => \{ setDir/.test(bsBody),
+    "the dir input must be disabled while the request is in flight"
+  );
+  // 成功路径不再复位 busy（900ms 提示期间按钮不该重新变得可点），且定时器句柄要能清：
+  // 否则第二次提交的结果会写进已经卸载的组件（评审 #4452245256）。断言窗口只取
+  // 「setMsg…到 setTimeout」之间——再往后就是 catch 里的网络错误兜底，那一处复位是对的。
+  const doneIdx = bsBody.indexOf("memory.explorer.bootstrapDone");
+  const timerIdx = bsBody.indexOf("timerRef.current = setTimeout(");
+  assert.ok(timerIdx > doneIdx, "the success branch must schedule its close through the stored ref");
+  const successTail = bsBody.slice(doneIdx, timerIdx);
+  assert.ok(!/setBusy\(false\)/.test(successTail), "the success path must not re-enable the button");
+  assert.ok(/clearTimeout\(timerRef\.current\)/.test(bsBody), "the stored timer must actually be cleared on unmount");
+  // 刷新必须同步调、不能排进定时器（评审 #4452539711）：切视图会卸载本组件并把
+  // timerRef 清掉，若刷新也挂在那 900ms 后面，它就静默丢了——库已经写进去了，
+  // 列表却还是旧的。而这条路径上用户刚看到「新建 N 条」，最容易立刻去翻列表。
+  const importedIdx = bsBody.indexOf("onImported();");
+  assert.ok(importedIdx > 0, "the success path must refresh the list");
+  assert.ok(
+    importedIdx < timerIdx,
+    "onImported must run synchronously, not inside the close timer"
+  );
+  assert.ok(
+    !/setTimeout\(\(\)\s*=>\s*\{?\s*onImported/.test(bsBody),
+    "the refresh must not be deferred into the close timer"
+  );
+  // 错误按服务端的码分开说（missing-dir / dir-not-found / not-a-directory /
+  // bootstrap-unavailable），不能一律「引导失败」——三种情况下用户该做的事不同。
+  assert.ok(
+    /"memory\.explorer\.bootstrapErr\." \+ String\(code/.test(bsBody),
+    "error codes must be mapped to distinct messages"
+  );
+  for (const key of [
+    "memory.explorer.bootstrap",
+    "memory.explorer.bootstrapTitle",
+    "memory.explorer.bootstrapHint",
+    "memory.explorer.bootstrapConfirm",
+    "memory.explorer.bootstrapDone",
+    "memory.explorer.bootstrapNoDir",
+    "memory.explorer.bootstrapFailed",
+    "memory.explorer.bootstrapErr.missing-dir",
+    "memory.explorer.bootstrapErr.dir-not-found",
+    "memory.explorer.bootstrapErr.not-a-directory",
+    "memory.explorer.bootstrapErr.bootstrap-unavailable"
+  ]) {
+    assert.ok(
+      clientSource.split(`"${key}"`).length - 1 >= 2,
+      `i18n key ${key} must exist in both dictionaries`
+    );
+  }
+
+  // 第 7 条：配置键覆盖面只读卡。
+  const ckIdx = clientSource.indexOf("function ConfigKeysCard");
+  assert.ok(ckIdx > 0, "ConfigKeysCard must exist");
+  const ckBody = clientSource.slice(ckIdx, ckIdx + 2900);
+  assert.ok(/apiFetch\("\/api\/dsh-mneme\/config-keys"\)/.test(ckBody), "the card must read the new route");
+  // 取数失败与「真的没有只读键」必须分开说，否则失败会被读成「清单是空的」。
+  assert.ok(
+    !/state\.failed \|\| !counts\s*\?\s*null/.test(ckBody),
+    "a failed fetch must not collapse into an empty list"
+  );
+  assert.ok(/memory\.settings\.configKeys\.loadFailed/.test(ckBody), "the failed branch needs its own copy");
+  // 摘要里的三类数字都必须来自服务端算好的桶：只填 {file} 会让「schema − panel」与
+  // 展开后「只能改文件」那段对不上（评审 #4452245244）。
+  assert.ok(
+    /\.replace\("\{undefaulted\}", String\(counts\.undefaulted\)\)/.test(ckBody),
+    "the summary must report the undefaulted bucket too, not make the reader subtract"
+  );
+  // 只列键名，不渲染任何值。
+  assert.ok(/className: "mneme-keychip"/.test(ckBody), "keys render as chips");
+  assert.ok(!/\.value/.test(ckBody.replace(/display:\s*"flex"[\s\S]{0,80}/g, "")), "the card must not render any key value");
+  for (const key of [
+    "memory.settings.configKeys.title",
+    "memory.settings.configKeys.desc",
+    "memory.settings.configKeys.summary",
+    "memory.settings.configKeys.fileOnlyHead",
+    "memory.settings.configKeys.undefaultedHead",
+    "memory.settings.configKeys.undefaultedHint",
+    "memory.settings.configKeys.show",
+    "memory.settings.configKeys.hide",
+    "memory.settings.configKeys.loadFailed"
+  ]) {
+    assert.ok(
+      clientSource.split(`"${key}"`).length - 1 >= 2,
+      `i18n key ${key} must exist in both dictionaries`
+    );
+  }
+  // 卡片要真的挂到设置页上（connect 组尾、help 组头之前），不是写了没插。
+  const mountIdx = clientSource.indexOf("h(ConfigKeysCard, { t })");
+  const helpIdx = clientSource.indexOf('groupHead("help")');
+  assert.ok(mountIdx > 0, "ConfigKeysCard must be mounted in the settings page");
+  assert.ok(mountIdx < helpIdx, "the card belongs to the end of the connect group, before the help section");
+  // 引导成功只递增 reloadKey；搜索态的列表走 remoteItems 那条 effect，它若不吃
+  // reloadKey，搜索词不变就永远看不到新导入的行（评审 #4452245305）。
+  assert.ok(
+    /\}, \[query, semantic, searchTopK, reloadKey\]\);/.test(clientSource),
+    "the search effect must re-run after an import/bootstrap bumps reloadKey"
+  );
+});
+
+test("the memory overlay refuses to close while a library request is in flight (issue #386)", () => {
+  // 引导请求在飞时，Esc / 背板 / ✕ 三条关闭路径都必须在。少一处，弹层连同
+  // MemoryExplorer 一起卸载，POST 还在飞——回来那句「新建几条、并入几条」就没有
+  // 地方显示，用户会以为没成功，而库其实已经写进去了（评审 #4453225573）。
+  const ovIdx = clientSource.indexOf("function MemoryOverlay");
+  assert.ok(ovIdx > 0, "MemoryOverlay must exist");
+  // 切到下一个模块级定义为止：给字符数会在下一次改动里被悄悄撑破。
+  const ovEnd = clientSource.indexOf("const EXPLORER_TYPES", ovIdx);
+  const ovBody = clientSource.slice(ovIdx, ovEnd > ovIdx ? ovEnd : ovIdx + 2600);
+
+  // 忙碌标志必须从 Explorer 上得来：MemoryOverlay 自己不知道有没有请求在飞。
+  assert.ok(
+    /useState\(false\)/.test(ovBody) && /explorerBusy/.test(ovBody),
+    "the overlay needs its own busy flag"
+  );
+  assert.ok(
+    /h\(MemoryExplorer, \{ t, onBusyChange: setExplorerBusy \}\)/.test(ovBody),
+    "the explorer must report its busy state up to the overlay"
+  );
+  // 用 ref 读、不把 busy 列进那个 effect 的依赖：effect 每次重跑都会
+  // closeBtnRef.current.focus()，请求一起一落就把正在输目录的用户踢出输入框。
+  assert.ok(
+    /const explorerBusyRef = useRef\(false\)/.test(ovBody),
+    "the guard must read through a ref, so busy changes do not re-run the focus effect"
+  );
+  assert.ok(
+    /explorerBusyRef\.current = explorerBusy/.test(ovBody),
+    "the ref must track the state"
+  );
+  assert.ok(
+    !/\[open, explorerBusy\]/.test(ovBody),
+    "explorerBusy must stay out of the focus effect's deps"
+  );
+
+  // 三条关闭路径逐一检查：Esc、背板、✕ 都走同一个守卫。
+  assert.equal(
+    ovBody.split("if (!explorerBusyRef.current) setOpen(false);").length - 1,
+    3,
+    "all three close paths (Escape, backdrop, ✕) must guard on the busy ref"
+  );
+  assert.ok(
+    /if \(e\.key === "Escape"\) \{ if \(!explorerBusyRef\.current\) setOpen\(false\); return; \}/.test(ovBody),
+    "Escape must not close the overlay while a request is in flight"
+  );
+  // ✕ 用 aria-disabled 而不是真的 disabled：真 disabled 会把焦点从按钮上拿走，
+  // 而 #178 的 Tab 环拿 closeBtnRef 当入口，焦点落空就出不去。
+  assert.ok(
+    /"aria-disabled": String\(explorerBusy\)/.test(ovBody),
+    "the close button must announce the blocked state"
+  );
+  assert.ok(
+    !/className: "mneme-footbtn",\s*\n\s*ref: closeBtnRef,\s*\n\s*disabled: /.test(ovBody),
+    "the close button must not be hard-disabled — that would break the #178 focus ring"
+  );
+});
+
 test("every client component declares the setters it calls (issue #553)", () => {
   // 浏览器/宿主全局，不是 React state，不该被要求声明
   const GLOBALS = new Set([
@@ -2776,3 +3358,57 @@ test("every client component declares the setters it calls (issue #553)", () =>
     "a setter must be declared in the component that calls it — a state hook placed in the "
     + "neighbouring component compiles fine but throws ReferenceError at render time (#553)");
 });
+
+// --- 实体页计数口径（#562 真机验证发现） ---
+// 实体页左侧栏此前固定显示「500 个实体」：它拿 `entities.length` 当总数，而那份列表
+// 是 `/entities?limit=500` 取回的最新 500 个。库里一万六千个实体被截成一个看起来正常
+// 的数字，用户据此判断「实体太少」——#559 只修了状态页那张卡，实体页这一处漏了。
+// 本用例锁四件事，防的回归各不相同：
+//   ① 总数来源必须是后端回的 `total`+  `totalExact`，不是切片长度；
+//   ② 全库数读不到时（老宿主 / 计数失败）退回切片长度而不是显示空白；
+//   ③ 列表本身仍只有 500 条，必须在界面上说清「总数是全库、列表是最近 N 个」，
+//      否则数字对了而列表还是 500 行，同一处观感错位只是换了个方向；
+//   ④ 那句说明走 i18n（中英各一条），不能硬编码中文。
+test("the entity rail counts the whole library, not the newest slice", () => {
+  const start = clientSource.indexOf("function EntityPanel(");
+  assert.ok(start > 0, "EntityPanel must exist");
+  const nextFn = clientSource.indexOf("\n    function ", start + 10);
+  assert.ok(nextFn > start, "EntityPanel must be followed by another module-level function");
+  const body = clientSource.slice(start, nextFn);
+
+  // ① 总数取自 totalExact 守门的 total。
+  assert.ok(
+    body.includes("setEntityTotal(j.totalExact === true && typeof j.total === \"number\" ? j.total : null)"),
+    "the rail total must come from the backend's total/totalExact, not the slice length"
+  );
+
+  // ② 计数行用全库数，读不到才退回切片长度。
+  assert.ok(
+    body.includes('t("memory.entities.count").replace("{n}", String(entityTotal !== null ? entityTotal : entities.length))'),
+    "the rail count must print the whole-library total with a slice-length fallback"
+  );
+  assert.ok(
+    !body.includes('t("memory.entities.count").replace("{n}", String(entities.length))'),
+    "printing entities.length directly is the \"always 500\" bug this test exists to prevent"
+  );
+
+  // ③ 列表只列最近 N 个这件事必须写出来（且只在真有截断时写）。
+  assert.ok(
+    /entityTotal !== null && entityTotal > entities\.length[\s\S]{0,200}memory\.entities\.countSampled/.test(body),
+    "a truncated list must say so instead of letting one number stand for both"
+  );
+  assert.ok(
+    body.includes('t("memory.entities.countSampled").replace("{shown}", String(entities.length))'),
+    "the notice must name how many entities the list actually shows"
+  );
+
+  // ④ 文案双语齐备，样式走语义色层。
+  for (const key of ["memory.entities.countSampled"]) {
+    const defined = clientSource.split(`"${key}":`).length - 1;
+    assert.equal(defined, 2, `i18n key ${key} must be defined exactly once in zh and once in en (got ${defined})`);
+  }
+  assert.ok(
+    clientSource.includes(".mneme-xcountnote{") && /color:var\(--mneme-fg-dim\)/.test(clientSource.slice(clientSource.indexOf(".mneme-xcountnote{"))),
+    "the notice needs its own dim style on the semantic colour layer"
+  );
+});