docs: cite MESHBAY_DESIGN.md and a section instead of the merged notes

The per-feature design notes were merged into docs/MESHBAY_DESIGN.md and
deleted from the tree on 2026-09-11, but ~230 comments across the three
packages still named them — usually written `docs/musicbay.md §3.2`, as
though the file were still in docs/. A reader had to know §16 existed to
resolve any of them. They now name the section directly.

Every mapping comes from §16, the concordance, which already records where
each old section landed: musicbay -> §9.8, mediacenter -> §9.7 for the
Videos app and §6.5 where the subject is derived data, photos -> §9.9,
auth-confirm -> §3.6, refactoring-search -> §9.11, invite-pairing-v1 ->
§3.4, per-node-identity-v1 -> §3.2, captcha -> §7.7, chat-sender-keys ->
§4.5, apps/refactor-groups -> §9.1–§9.4, desktop-client-v1 per section.
Bare citations of the same documents (`draft-v6 §2.11`, `§4.8`, `§3.4`)
are retargeted too: those collide with real section numbers in the design
document, so leaving them would have been worse than the named form.

Four cases the concordance does not cover, each decided rather than guessed:

  Sub-item references into documents that no longer exist — mediacenter's
  `§3.3 row 4`, `§3.4b/c`, `apps.md §3b` — name rows and sub-items §9.7 and
  §9.2 do not reproduce. The module-level citation stays; the sub-item
  pointer is dropped.

  The V-findings keep their labels but lose the dead `§10.1/` prefix.
  §13.8 lists V1–V13 as per-application open items, which is not what the
  labels mean in these comments, so pointing them at §13.8 would have been
  a false citation.

  `apps.md §5`'s virtualization requirement has no counterpart anywhere in
  the design document. The requirement is stated in the comment itself, so
  the citation is dropped rather than aimed at a section that does not say
  it.

  Comments that attributed a *sentence* to an old note — musicbay's "several
  thousand files" example, its "what got measured" note, its measured
  ~11%/~26% cover-art figures, the "original no root, whole shared tree"
  call — state the fact without attribution now. §9.8 does not contain those
  sentences and citing it for them would have been wrong.

CLAUDE.md's "a reference to a document that no longer exists" row now says
the concordance is for git history and out-of-tree material; the code cites
sections directly.

Verified: 2851 passed, 4 skipped. The 12 errors in the run are the Firefox
leg of test_sticky_header.py's browser harness, which is broken at the
browser level on this machine — headless Firefox (snap) dies with
`[GFX1-]: RenderCompositorSWGL failed mapping default framebuffer`, renders
nothing, and the probe exits `{"error": "no measurement"}` after its full
90s wait. Chrome runs the same 12 assertions in 3.2s and passes. Nothing
here can affect it: every changed line in style.css is inside a comment.
Also checked: ast.parse on every changed .py, `node --check` on every
changed .js, the /* */ balance in style.css, and that no changed line
exceeds the width its file already used.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

1 files changed, 6 insertions, 6 deletions

diff --git a/packages/meshbay-hub/src/meshbay_hub/static/group-page.js b/packages/meshbay-hub/src/meshbay_hub/static/group-page.js
index 205fce2..9a86f2a 100644
--- a/packages/meshbay-hub/src/meshbay_hub/static/group-page.js
+++ b/packages/meshbay-hub/src/meshbay_hub/static/group-page.js
@@ -154,10 +154,10 @@ function GroupPage({ groupId, group, token, username, userId, userPrefs,
   // that). Null until the handshake ack arrives.
   const [scanSettings, setScanSettings] = useState(null);
   // TMDB on/off + whether a custom token is set, node-wide (not per-group) —
-  // docs/mediacenter.md §5.5. Null until the handshake ack arrives.
+  // docs/MESHBAY_DESIGN.md §9.7. Null until the handshake ack arrives.
   const [tmdbConfig, setTmdbConfig] = useState(null);
   // Which folders each app works over. One shape for all of them — a list,
-  // always, even where an app only wants one (docs/refactor-groups.md §1.6):
+  // always, even where an app only wants one (docs/MESHBAY_DESIGN.md §9.3):
   // Videos and Music were single values, which meant a library spread over two
   // drives could not be described at all. Empty means nothing configured yet,
   // which every app reads as "show nothing", never "the whole group index".
@@ -171,7 +171,7 @@ function GroupPage({ groupId, group, token, username, userId, userPrefs,
   // Whether members' cross-group Search lists this group. Not an app setting:
   // it is about the group as a whole, and it hides nothing from this page.
   const [searchListed, setSearchListed] = useState(true);
-  // MusicBrainz on/off (per-group) — docs/musicbay.md §3.2.
+  // MusicBrainz on/off (per-group) — docs/MESHBAY_DESIGN.md §9.8.
   const [musicbrainzConfig, setMusicbrainzConfig] = useState(null);
   // `op` rides through to the shell — 'replace', 'next' or 'append'
   // (docs/playlists.md §9.2). It has to be named here: a wrapper that takes
@@ -320,7 +320,7 @@ function GroupPage({ groupId, group, token, username, userId, userPrefs,
       setDeviceReady(false);
       gekRef.current = null;
       if (!session.bundleKey) session.bundleKey = await _loadBundleKey();
-      // Persisted (docs/auth-confirm.md §4.3) so a group joined in a later
+      // Persisted (docs/MESHBAY_DESIGN.md §3.6) so a group joined in a later
       // session still leaves a recovery-wrapped identity copy on its node.
       if (!session.recoveryKey) session.recoveryKey = await _loadRecoveryKey();
       if (!session.bundleKey && window.MeshBayKeys) {
@@ -669,7 +669,7 @@ function GroupPage({ groupId, group, token, username, userId, userPrefs,
   // the only unambiguous answer once a group can have several writable roots.
   // Chat has no folder to browse, so it needs one picked for it, and this is
   // the same rule the node applies when a client names no root at all. It
-  // becomes an operator-chosen directory in phase 2 (refactor-groups.md §1.7).
+  // becomes an operator-chosen directory in phase 2 (docs/MESHBAY_DESIGN.md §9.6).
   //
   const writableRoots = useMemo(
     () => nodeRoots.filter((r) => r.writable && r.available !== false),
@@ -735,7 +735,7 @@ function GroupPage({ groupId, group, token, username, userId, userPrefs,
   // rather than written out. Naming them here would mean adding an app
   // required editing this file, which is the one thing the plugin
   // architecture is supposed to have removed — and the reference app
-  // (docs/refactor-groups.md §4.1) is what made the difference visible.
+  // (docs/MESHBAY_DESIGN.md §9.4) is what made the difference visible.
   const perAppDirectories = useMemo(() => {
     const out = {};
     for (const app of APPS) out[`${app.key}Directories`] = appDirs(app.key);