@modusensus/dsh-mneme 0.6.9 → 0.6.10

package/{dsh-mneme/test → test}/client.test.js

@@ -1,368 +1,368 @@
-import test from "node:test";
-import assert from "node:assert/strict";
-import { readFileSync, existsSync } from "node:fs";
-import { fileURLToPath } from "node:url";
-import { dirname, join } from "node:path";
-
-const root = join(dirname(fileURLToPath(import.meta.url)), "..");
-const clientSource = readFileSync(join(root, "lib/client.js"), "utf8");
-const pkg = JSON.parse(readFileSync(join(root, "package.json"), "utf8"));
-
-// The Web client bundle registers itself via __ModuleLoader__.load. DSH
-// resolves the bundle by plugin package name, so the registered id must match
-// package.json `name` exactly (a mismatch surfaces as "loaded without
-// registering '@modusensus/dsh-mneme'" in the DSH client).
-test("client bundle registers under the package name", () => {
-  const match = clientSource.match(/__ModuleLoader__\.load\(\{\s*id:\s*"([^"]+)"/);
-  assert.ok(match, "client bundle must call __ModuleLoader__.load with an id");
-  assert.equal(match[1], pkg.name, "registered id must equal package.json name");
-});
-
-// client.js is hand-authored under lib/ only (no src/ counterpart), so the
-// src->lib sync must never prune it.
-test("client bundle is lib-only with no src counterpart", () => {
-  assert.equal(existsSync(join(root, "src/client.js")), false, "src/ must not contain client.js");
-  assert.equal(existsSync(join(root, "lib/client.js")), true, "lib/client.js must exist");
-});
-
-// 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", () => {
-  assert.ok(
-    clientSource.includes('ctx.slots.inject("sidebar.footer.action"'),
-    "client must inject into sidebar.footer.action"
-  );
-  assert.equal(
-    clientSource.includes('"settings.section"'),
-    false,
-    "the old settings.section registration must be gone"
-  );
-});
-
-// The drawer era is over as the PRIMARY surface: the sidebar entry must
-// activate the main-area memory library tab first. The one sanctioned
-// exception is the hero screen — the host hides the whole tab ring while a
-// session is blank, so activation legitimately fails there and the same
-// click falls back to a full-viewport overlay (same MemoryExplorer, not the
-// old 420px side drawer). A dialog role stays banned either way.
-test("tab-first activation with hero-screen overlay fallback", () => {
-  assert.equal(
-    clientSource.includes("role: \"dialog\""),
-    false,
-    "no dialog surface should remain"
-  );
-  assert.ok(
-    clientSource.includes("activateExplorerTab(t(\"memory.view.label\"))"),
-    "the sidebar trigger must activate the memory library tab by its label"
-  );
-  assert.ok(
-    clientSource.includes("activateExplorerTab(t(\"memory.view.label\")).then((ok) => { if (!ok) setOpen(true); })"),
-    "a failed tab activation must open the fallback overlay"
-  );
-  assert.ok(
-    /if \(!tab\) \{ resolve\(false\); return; \}/.test(clientSource),
-    "activation must resolve false when the tab ring is absent (hero screen)"
-  );
-  assert.ok(
-    /aria-selected.*true/.test(clientSource),
-    "activation is only confirmed once the host marks the tab selected"
-  );
-});
-
-// The fallback overlay reuses the full MemoryExplorer (three columns, graph,
-// settings) at viewport size — not the old side drawer — and closes on Esc
-// or the close button.
-test("hero fallback overlay is a full-viewport MemoryExplorer with a close affordance", () => {
-  assert.ok(
-    clientSource.includes('.mneme-overlay{position:fixed;inset:0'),
-    "the overlay must cover the full viewport"
-  );
-  assert.ok(
-    clientSource.includes('h(MemoryExplorer, { t })'),
-    "the overlay renders the same MemoryExplorer component as the tab"
-  );
-  assert.ok(
-    clientSource.includes('e.key === "Escape"'),
-    "Esc must close the overlay"
-  );
-  assert.ok(
-    clientSource.includes('"memory.overlay.close"'),
-    "the overlay ships a localized close label in both dictionaries"
-  );
-});
-
-// The sidebar hands each footer action only its column state: a wide row
-// (icon + label) when expanded, a bare rail icon when collapsed.
-test("trigger renders a wide row or a rail icon from the wide flag", () => {
-  assert.ok(
-    /wide \? "mneme-trigger" : "mneme-trigger mneme-rail"/.test(clientSource),
-    "trigger must branch on the wide flag"
-  );
-  assert.ok(
-    /wide && h\("span", \{ className: "mneme-trigger-label" \}/.test(clientSource),
-    "the label span must render only when wide"
-  );
-});
-
-// The full-width memory browser lives in the conversation view ring beside
-// Chat / Trajectory, so the client must inject into `conversation.view` with
-// a stable entry id (the active view is persisted by that id).
-test("explorer registers into the conversation view ring", () => {
-  assert.ok(
-    clientSource.includes('ctx.slots.inject("conversation.view"'),
-    "client must inject into conversation.view"
-  );
-  assert.ok(
-    clientSource.includes('id: "dsh-mneme-memory"'),
-    "the view entry needs a stable, unique id"
-  );
-  assert.ok(
-    clientSource.includes('"memory.view.label"'),
-    "the tab label must come from the memory.view.label dictionary key"
-  );
-});
-
-// The graph toggle must not read as "share": the primitives share icon is
-// banned and a custom node-graph glyph takes its place.
-test("graph toggle uses a node-graph glyph, not the share icon", () => {
-  assert.equal(
-    clientSource.includes("IconShareOutline16"),
-    false,
-    "IconShareOutline16 reads as share and must not appear"
-  );
-  assert.ok(
-    clientSource.includes("GraphNodesIcon"),
-    "the custom node-graph icon must back the graph toggle"
-  );
-});
-
-// Every memory feature lives in the main-area library now: the explorer
-// hosts three sub-views (browse / graph / settings) switched by tabs whose
-// labels come from dedicated dictionary keys.
-test("explorer hosts browse, graph and settings sub-views", () => {
-  for (const key of ["tabMemory", "tabGraph", "tabSettings"]) {
-    assert.ok(
-      clientSource.includes(`"memory.explorer.${key}"`),
-      `sub-view labels must come from memory.explorer.${key}`
-    );
-  }
-  assert.ok(
-    clientSource.includes('h(GraphPanel, { t, focusEntity: graphFocus, onJumpMemory: jumpToMemory })'),
-    "the graph panel must be embedded as a sub-view"
-  );
-  assert.ok(
-    clientSource.includes('h(SettingsContent, { t })'),
-    "the settings forms must be embedded as a sub-view"
-  );
-});
-
-// The graph panel jumps back into the browser: related-memory rows and the
-// edge source button must land on the browse tab with the target selected.
-test("graph jump lands on the selected memory in the browser", () => {
-  assert.ok(
-    /onClick: \(\) => onJumpMemory && onJumpMemory\(m\)/.test(clientSource),
-    "related-memory rows must jump via onJumpMemory(m)"
-  );
-  assert.ok(
-    clientSource.includes("onJumpMemory({ id: selected.edge.memory_id })"),
-    "the edge source button must jump to the origin memory by id"
-  );
-  assert.ok(
-    /const jumpToMemory = \(target\) => \{/.test(clientSource),
-    "jumpToMemory must reset filters and select the target"
-  );
-});
-
-// "entity:" in the browser search is the graph entry grammar: it must offer
-// a jump chip instead of filtering the list.
-test("entity: search grammar offers a graph jump", () => {
-  assert.ok(
-    clientSource.includes('query.trim().startsWith("entity:")'),
-    "the entity: prefix must be recognized"
-  );
-  assert.ok(
-    /onClick: \(\) => openGraphFor\(entityQuery\)/.test(clientSource),
-    "the jump chip must switch to the graph sub-view"
-  );
-});
-
-// The explorer is a three-pane layout: types with counts, a month→day time
-// tree, and a detail pane rendering the untruncated content.
-test("explorer lays out types, timeline, and full-text detail", () => {
-  assert.ok(
-    clientSource.includes('className: "mneme-xmain"'),
-    "the three-column grid must be present"
-  );
-  assert.ok(
-    clientSource.includes('className: "mneme-xdcontent"'),
-    "the detail pane must render the full content"
-  );
-  assert.ok(
-    /toLocaleDateString\(undefined, \{ year: "numeric", month: "long" \}\)/.test(clientSource),
-    "month groups must format via the host locale, not hardcoded strings"
-  );
-});
-
-// The library page must read as a first-party view: the chrome resolves to
-// the host's design tokens (layer-1 canvas, brand-blue active states) and
-// the boxed-panel / pill-chip patterns of the drawer era must stay gone.
-test("explorer chrome aligns with the host design system", () => {
-  assert.ok(
-    clientSource.includes("background:var(--dsw-alias-bg-layer-1)"),
-    "the page canvas must sit on the host bg-layer-1 token"
-  );
-  assert.ok(
-    /\.mneme-vtab\.mneme-active::after/.test(clientSource),
-    "active sub-tabs use the host underline treatment"
-  );
-  assert.ok(
-    clientSource.includes(".mneme-vtab.mneme-active{color:var(--dsw-alias-state-business-primary)}"),
-    "active sub-tab text must turn the host brand blue"
-  );
-  assert.equal(
-    /\.mneme-xmain\{[^}]*border:1px/.test(clientSource),
-    false,
-    "the three-column layout must not wrap itself in a boxed panel"
-  );
-  assert.equal(
-    clientSource.includes("border-radius:999px"),
-    false,
-    "pill chips belong to the drawer era and must stay gone"
-  );
-});
-
-// The v0.6.1 wiki-link feature: the detail pane mounts a BacklinksPanel that
-// fetches the two read-only link endpoints by the selected memory id and
-// renders back/forward rows, each jumping back into the browser.
-test("detail pane mounts a BacklinksPanel backed by the two link endpoints", () => {
-  assert.ok(
-    clientSource.includes("h(BacklinksPanel, { memory: selected, t, onJump: jumpToMemory })"),
-    "the detail pane must mount BacklinksPanel after the actions row"
-  );
-  assert.ok(
-    clientSource.includes("/api/dsh-mneme/wikilinks/backlinks?id="),
-    "BacklinksPanel must fetch the backlinks endpoint by memory id"
-  );
-  assert.ok(
-    clientSource.includes("/api/dsh-mneme/wikilinks/forward?id="),
-    "BacklinksPanel must fetch the forward-links endpoint by memory id"
-  );
-});
-
-// Detail content turns [[target]] / [[display|target]] into clickable links:
-// the display text survives, the target title is kept for hover, and a click
-// resolves the title through the resolve endpoint before jumping.
-test("detail content renders wiki-links and resolves them on click", () => {
-  assert.ok(
-    clientSource.includes('className: "mneme-wikilink"'),
-    "inline [[target]] links must use the .mneme-wikilink style"
-  );
-  assert.ok(
-    clientSource.includes("/api/dsh-mneme/wikilinks/resolve?title="),
-    "clicking a wiki-link must resolve the title via the resolve endpoint"
-  );
-  assert.ok(
-    clientSource.includes('className: "mneme-backlinks"'),
-    "the panel must render inside a .mneme-backlinks block"
-  );
-});
-
-// v0.6.2 tag system: the detail pane renders tags as clickable chips wired to
-// the memory/tags endpoints, and a tag: query always goes server-side.
-test("detail pane renders editable tag chips backed by the tags endpoint", () => {
-  assert.ok(
-    clientSource.includes("/api/dsh-mneme/memory/tags?id="),
-    "the panel must fetch the selected memory's tags via the GET endpoint"
-  );
-  assert.ok(
-    clientSource.includes('method: "POST"'),
-    "adding/removing a tag must POST to the tags endpoint"
-  );
-  assert.ok(
-    clientSource.includes("onClick: () => onTagClick(tag)"),
-    "a tag chip click must trigger a tag: search"
-  );
-  assert.ok(
-    clientSource.includes("tagManual"),
-    "the panel must read the manualTagEnabled gate to hide editing"
-  );
-});
-
-test("tag: queries run server-side regardless of the semantic toggle", () => {
-  assert.ok(
-    clientSource.includes('(!semantic && !q.startsWith("tag:"))'),
-    "tag: must bypass the semantic toggle and use the search endpoint"
-  );
-  assert.ok(
-    clientSource.includes('setQuery(`tag:${tag}`)'),
-    "a tag chip click must set the query to tag:<tag>"
-  );
-});
-
-test("tag UI ships localized labels in both dictionaries", () => {
-  for (const key of ["tagAdd", "tagRemove", "tagPlaceholder", "tagsEmpty"]) {
-    assert.ok(
-      clientSource.includes(`"memory.explorer.${key}"`),
-      `memory.explorer.${key} key must exist`
-    );
-  }
-});
-
-// v0.6.3 directory view: a tag-folder tree backed by the directory endpoint.
-// Folders accordion via data-expanded controlled by MemoryExplorer-lifted
-// state; a memory entry click jumps back into the browser via onJump.
-test("directory sub-view mounts DirectoryPanel backed by the directory endpoint", () => {
-  assert.ok(
-    clientSource.includes("h(DirectoryPanel, { t, onJump: jumpToMemory, collapsed: dirCollapsed, setCollapsed: setDirCollapsed })"),
-    "the directory panel must be embedded as a sub-view with lifted collapse state"
-  );
-  assert.ok(
-    clientSource.includes("/api/dsh-mneme/directory"),
-    "DirectoryPanel must fetch the directory endpoint"
-  );
-  assert.ok(
-    clientSource.includes('className: "mneme-directory"'),
-    "the directory panel must render inside the .mneme-directory block"
-  );
-});
-
-test("directory folders accordion via data-expanded driven by MemoryExplorer state", () => {
-  assert.ok(
-    clientSource.includes('"data-expanded": String(open)'),
-    "folder expansion must be driven by the data-expanded attribute"
-  );
-  assert.ok(
-    clientSource.includes("const [dirCollapsed, setDirCollapsed] = useState({})"),
-    "collapse state must live in MemoryExplorer so tab switches keep it"
-  );
-  assert.ok(
-    clientSource.includes('"aria-expanded": String(open)'),
-    "folder headers must announce their expanded state"
-  );
-});
-
-test("directory entry click jumps to the memory detail via onJump", () => {
-  assert.ok(
-    clientSource.includes("onClick: () => onJump(m)"),
-    "clicking a memory entry must call onJump with the memory"
-  );
-  assert.ok(
-    clientSource.includes("formatDate(m.updated_at || m.created_at)"),
-    "entries must render a timestamp via formatDate"
-  );
-  assert.ok(
-    clientSource.includes("memory.directory.untagged"),
-    "untagged memories must be bucketed under a labeled fallback folder"
-  );
-});
-
-test("directory ships localized labels in both dictionaries", () => {
-  for (const key of ["memory.explorer.tabDirectory", "memory.directory.untagged", "memory.directory.loading", "memory.directory.empty"]) {
-    assert.ok(
-      clientSource.includes(`"${key}"`),
-      `${key} key must exist`
-    );
-  }
-});
+import test from "node:test";
+import assert from "node:assert/strict";
+import { readFileSync, existsSync } from "node:fs";
+import { fileURLToPath } from "node:url";
+import { dirname, join } from "node:path";
+
+const root = join(dirname(fileURLToPath(import.meta.url)), "..");
+const clientSource = readFileSync(join(root, "lib/client.js"), "utf8");
+const pkg = JSON.parse(readFileSync(join(root, "package.json"), "utf8"));
+
+// The Web client bundle registers itself via __ModuleLoader__.load. DSH
+// resolves the bundle by plugin package name, so the registered id must match
+// package.json `name` exactly (a mismatch surfaces as "loaded without
+// registering '@modusensus/dsh-mneme'" in the DSH client).
+test("client bundle registers under the package name", () => {
+  const match = clientSource.match(/__ModuleLoader__\.load\(\{\s*id:\s*"([^"]+)"/);
+  assert.ok(match, "client bundle must call __ModuleLoader__.load with an id");
+  assert.equal(match[1], pkg.name, "registered id must equal package.json name");
+});
+
+// client.js is hand-authored under lib/ only (no src/ counterpart), so the
+// src->lib sync must never prune it.
+test("client bundle is lib-only with no src counterpart", () => {
+  assert.equal(existsSync(join(root, "src/client.js")), false, "src/ must not contain client.js");
+  assert.equal(existsSync(join(root, "lib/client.js")), true, "lib/client.js must exist");
+});
+
+// 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", () => {
+  assert.ok(
+    clientSource.includes('ctx.slots.inject("sidebar.footer.action"'),
+    "client must inject into sidebar.footer.action"
+  );
+  assert.equal(
+    clientSource.includes('"settings.section"'),
+    false,
+    "the old settings.section registration must be gone"
+  );
+});
+
+// The drawer era is over as the PRIMARY surface: the sidebar entry must
+// activate the main-area memory library tab first. The one sanctioned
+// exception is the hero screen — the host hides the whole tab ring while a
+// session is blank, so activation legitimately fails there and the same
+// click falls back to a full-viewport overlay (same MemoryExplorer, not the
+// old 420px side drawer). A dialog role stays banned either way.
+test("tab-first activation with hero-screen overlay fallback", () => {
+  assert.equal(
+    clientSource.includes("role: \"dialog\""),
+    false,
+    "no dialog surface should remain"
+  );
+  assert.ok(
+    clientSource.includes("activateExplorerTab(t(\"memory.view.label\"))"),
+    "the sidebar trigger must activate the memory library tab by its label"
+  );
+  assert.ok(
+    clientSource.includes("activateExplorerTab(t(\"memory.view.label\")).then((ok) => { if (!ok) setOpen(true); })"),
+    "a failed tab activation must open the fallback overlay"
+  );
+  assert.ok(
+    /if \(!tab\) \{ resolve\(false\); return; \}/.test(clientSource),
+    "activation must resolve false when the tab ring is absent (hero screen)"
+  );
+  assert.ok(
+    /aria-selected.*true/.test(clientSource),
+    "activation is only confirmed once the host marks the tab selected"
+  );
+});
+
+// The fallback overlay reuses the full MemoryExplorer (three columns, graph,
+// settings) at viewport size — not the old side drawer — and closes on Esc
+// or the close button.
+test("hero fallback overlay is a full-viewport MemoryExplorer with a close affordance", () => {
+  assert.ok(
+    clientSource.includes('.mneme-overlay{position:fixed;inset:0'),
+    "the overlay must cover the full viewport"
+  );
+  assert.ok(
+    clientSource.includes('h(MemoryExplorer, { t })'),
+    "the overlay renders the same MemoryExplorer component as the tab"
+  );
+  assert.ok(
+    clientSource.includes('e.key === "Escape"'),
+    "Esc must close the overlay"
+  );
+  assert.ok(
+    clientSource.includes('"memory.overlay.close"'),
+    "the overlay ships a localized close label in both dictionaries"
+  );
+});
+
+// The sidebar hands each footer action only its column state: a wide row
+// (icon + label) when expanded, a bare rail icon when collapsed.
+test("trigger renders a wide row or a rail icon from the wide flag", () => {
+  assert.ok(
+    /wide \? "mneme-trigger" : "mneme-trigger mneme-rail"/.test(clientSource),
+    "trigger must branch on the wide flag"
+  );
+  assert.ok(
+    /wide && h\("span", \{ className: "mneme-trigger-label" \}/.test(clientSource),
+    "the label span must render only when wide"
+  );
+});
+
+// The full-width memory browser lives in the conversation view ring beside
+// Chat / Trajectory, so the client must inject into `conversation.view` with
+// a stable entry id (the active view is persisted by that id).
+test("explorer registers into the conversation view ring", () => {
+  assert.ok(
+    clientSource.includes('ctx.slots.inject("conversation.view"'),
+    "client must inject into conversation.view"
+  );
+  assert.ok(
+    clientSource.includes('id: "dsh-mneme-memory"'),
+    "the view entry needs a stable, unique id"
+  );
+  assert.ok(
+    clientSource.includes('"memory.view.label"'),
+    "the tab label must come from the memory.view.label dictionary key"
+  );
+});
+
+// The graph toggle must not read as "share": the primitives share icon is
+// banned and a custom node-graph glyph takes its place.
+test("graph toggle uses a node-graph glyph, not the share icon", () => {
+  assert.equal(
+    clientSource.includes("IconShareOutline16"),
+    false,
+    "IconShareOutline16 reads as share and must not appear"
+  );
+  assert.ok(
+    clientSource.includes("GraphNodesIcon"),
+    "the custom node-graph icon must back the graph toggle"
+  );
+});
+
+// Every memory feature lives in the main-area library now: the explorer
+// hosts three sub-views (browse / graph / settings) switched by tabs whose
+// labels come from dedicated dictionary keys.
+test("explorer hosts browse, graph and settings sub-views", () => {
+  for (const key of ["tabMemory", "tabGraph", "tabSettings"]) {
+    assert.ok(
+      clientSource.includes(`"memory.explorer.${key}"`),
+      `sub-view labels must come from memory.explorer.${key}`
+    );
+  }
+  assert.ok(
+    clientSource.includes('h(GraphPanel, { t, focusEntity: graphFocus, onJumpMemory: jumpToMemory })'),
+    "the graph panel must be embedded as a sub-view"
+  );
+  assert.ok(
+    clientSource.includes('h(SettingsContent, { t })'),
+    "the settings forms must be embedded as a sub-view"
+  );
+});
+
+// The graph panel jumps back into the browser: related-memory rows and the
+// edge source button must land on the browse tab with the target selected.
+test("graph jump lands on the selected memory in the browser", () => {
+  assert.ok(
+    /onClick: \(\) => onJumpMemory && onJumpMemory\(m\)/.test(clientSource),
+    "related-memory rows must jump via onJumpMemory(m)"
+  );
+  assert.ok(
+    clientSource.includes("onJumpMemory({ id: selected.edge.memory_id })"),
+    "the edge source button must jump to the origin memory by id"
+  );
+  assert.ok(
+    /const jumpToMemory = \(target\) => \{/.test(clientSource),
+    "jumpToMemory must reset filters and select the target"
+  );
+});
+
+// "entity:" in the browser search is the graph entry grammar: it must offer
+// a jump chip instead of filtering the list.
+test("entity: search grammar offers a graph jump", () => {
+  assert.ok(
+    clientSource.includes('query.trim().startsWith("entity:")'),
+    "the entity: prefix must be recognized"
+  );
+  assert.ok(
+    /onClick: \(\) => openGraphFor\(entityQuery\)/.test(clientSource),
+    "the jump chip must switch to the graph sub-view"
+  );
+});
+
+// The explorer is a three-pane layout: types with counts, a month→day time
+// tree, and a detail pane rendering the untruncated content.
+test("explorer lays out types, timeline, and full-text detail", () => {
+  assert.ok(
+    clientSource.includes('className: "mneme-xmain"'),
+    "the three-column grid must be present"
+  );
+  assert.ok(
+    clientSource.includes('className: "mneme-xdcontent"'),
+    "the detail pane must render the full content"
+  );
+  assert.ok(
+    /toLocaleDateString\(undefined, \{ year: "numeric", month: "long" \}\)/.test(clientSource),
+    "month groups must format via the host locale, not hardcoded strings"
+  );
+});
+
+// The library page must read as a first-party view: the chrome resolves to
+// the host's design tokens (layer-1 canvas, brand-blue active states) and
+// the boxed-panel / pill-chip patterns of the drawer era must stay gone.
+test("explorer chrome aligns with the host design system", () => {
+  assert.ok(
+    clientSource.includes("background:var(--dsw-alias-bg-layer-1)"),
+    "the page canvas must sit on the host bg-layer-1 token"
+  );
+  assert.ok(
+    /\.mneme-vtab\.mneme-active::after/.test(clientSource),
+    "active sub-tabs use the host underline treatment"
+  );
+  assert.ok(
+    clientSource.includes(".mneme-vtab.mneme-active{color:var(--dsw-alias-state-business-primary)}"),
+    "active sub-tab text must turn the host brand blue"
+  );
+  assert.equal(
+    /\.mneme-xmain\{[^}]*border:1px/.test(clientSource),
+    false,
+    "the three-column layout must not wrap itself in a boxed panel"
+  );
+  assert.equal(
+    clientSource.includes("border-radius:999px"),
+    false,
+    "pill chips belong to the drawer era and must stay gone"
+  );
+});
+
+// The v0.6.1 wiki-link feature: the detail pane mounts a BacklinksPanel that
+// fetches the two read-only link endpoints by the selected memory id and
+// renders back/forward rows, each jumping back into the browser.
+test("detail pane mounts a BacklinksPanel backed by the two link endpoints", () => {
+  assert.ok(
+    clientSource.includes("h(BacklinksPanel, { memory: selected, t, onJump: jumpToMemory })"),
+    "the detail pane must mount BacklinksPanel after the actions row"
+  );
+  assert.ok(
+    clientSource.includes("/api/dsh-mneme/wikilinks/backlinks?id="),
+    "BacklinksPanel must fetch the backlinks endpoint by memory id"
+  );
+  assert.ok(
+    clientSource.includes("/api/dsh-mneme/wikilinks/forward?id="),
+    "BacklinksPanel must fetch the forward-links endpoint by memory id"
+  );
+});
+
+// Detail content turns [[target]] / [[display|target]] into clickable links:
+// the display text survives, the target title is kept for hover, and a click
+// resolves the title through the resolve endpoint before jumping.
+test("detail content renders wiki-links and resolves them on click", () => {
+  assert.ok(
+    clientSource.includes('className: "mneme-wikilink"'),
+    "inline [[target]] links must use the .mneme-wikilink style"
+  );
+  assert.ok(
+    clientSource.includes("/api/dsh-mneme/wikilinks/resolve?title="),
+    "clicking a wiki-link must resolve the title via the resolve endpoint"
+  );
+  assert.ok(
+    clientSource.includes('className: "mneme-backlinks"'),
+    "the panel must render inside a .mneme-backlinks block"
+  );
+});
+
+// v0.6.2 tag system: the detail pane renders tags as clickable chips wired to
+// the memory/tags endpoints, and a tag: query always goes server-side.
+test("detail pane renders editable tag chips backed by the tags endpoint", () => {
+  assert.ok(
+    clientSource.includes("/api/dsh-mneme/memory/tags?id="),
+    "the panel must fetch the selected memory's tags via the GET endpoint"
+  );
+  assert.ok(
+    clientSource.includes('method: "POST"'),
+    "adding/removing a tag must POST to the tags endpoint"
+  );
+  assert.ok(
+    clientSource.includes("onClick: () => onTagClick(tag)"),
+    "a tag chip click must trigger a tag: search"
+  );
+  assert.ok(
+    clientSource.includes("tagManual"),
+    "the panel must read the manualTagEnabled gate to hide editing"
+  );
+});
+
+test("tag: queries run server-side regardless of the semantic toggle", () => {
+  assert.ok(
+    clientSource.includes('(!semantic && !q.startsWith("tag:"))'),
+    "tag: must bypass the semantic toggle and use the search endpoint"
+  );
+  assert.ok(
+    clientSource.includes('setQuery(`tag:${tag}`)'),
+    "a tag chip click must set the query to tag:<tag>"
+  );
+});
+
+test("tag UI ships localized labels in both dictionaries", () => {
+  for (const key of ["tagAdd", "tagRemove", "tagPlaceholder", "tagsEmpty"]) {
+    assert.ok(
+      clientSource.includes(`"memory.explorer.${key}"`),
+      `memory.explorer.${key} key must exist`
+    );
+  }
+});
+
+// v0.6.3 directory view: a tag-folder tree backed by the directory endpoint.
+// Folders accordion via data-expanded controlled by MemoryExplorer-lifted
+// state; a memory entry click jumps back into the browser via onJump.
+test("directory sub-view mounts DirectoryPanel backed by the directory endpoint", () => {
+  assert.ok(
+    clientSource.includes("h(DirectoryPanel, { t, onJump: jumpToMemory, collapsed: dirCollapsed, setCollapsed: setDirCollapsed })"),
+    "the directory panel must be embedded as a sub-view with lifted collapse state"
+  );
+  assert.ok(
+    clientSource.includes("/api/dsh-mneme/directory"),
+    "DirectoryPanel must fetch the directory endpoint"
+  );
+  assert.ok(
+    clientSource.includes('className: "mneme-directory"'),
+    "the directory panel must render inside the .mneme-directory block"
+  );
+});
+
+test("directory folders accordion via data-expanded driven by MemoryExplorer state", () => {
+  assert.ok(
+    clientSource.includes('"data-expanded": String(open)'),
+    "folder expansion must be driven by the data-expanded attribute"
+  );
+  assert.ok(
+    clientSource.includes("const [dirCollapsed, setDirCollapsed] = useState({})"),
+    "collapse state must live in MemoryExplorer so tab switches keep it"
+  );
+  assert.ok(
+    clientSource.includes('"aria-expanded": String(open)'),
+    "folder headers must announce their expanded state"
+  );
+});
+
+test("directory entry click jumps to the memory detail via onJump", () => {
+  assert.ok(
+    clientSource.includes("onClick: () => onJump(m)"),
+    "clicking a memory entry must call onJump with the memory"
+  );
+  assert.ok(
+    clientSource.includes("formatDate(m.updated_at || m.created_at)"),
+    "entries must render a timestamp via formatDate"
+  );
+  assert.ok(
+    clientSource.includes("memory.directory.untagged"),
+    "untagged memories must be bucketed under a labeled fallback folder"
+  );
+});
+
+test("directory ships localized labels in both dictionaries", () => {
+  for (const key of ["memory.explorer.tabDirectory", "memory.directory.untagged", "memory.directory.loading", "memory.directory.empty"]) {
+    assert.ok(
+      clientSource.includes(`"${key}"`),
+      `${key} key must exist`
+    );
+  }
+});