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, 8 insertions, 8 deletions

diff --git a/packages/meshbay-common/src/meshbay_common/protocol.py b/packages/meshbay-common/src/meshbay_common/protocol.py
index c3cb099..c444711 100644
--- a/packages/meshbay-common/src/meshbay_common/protocol.py
+++ b/packages/meshbay-common/src/meshbay_common/protocol.py
@@ -69,11 +69,11 @@ class MNP:
     # never once invoked. A live handler on both transports, plaintext media,
     # and no client: removed rather than repaired.
     #
-    # Not a Double Ratchet message, and never was — `first-review.md` C1
-    # rejected exactly that for groups. Since MNP 2.0 it is AES-256-GCM under a
+    # Not a Double Ratchet message, and never was — finding C1
+    # (`docs/MESHBAY_DESIGN.md` §13.1) rejected exactly that for groups. Since MNP 2.0 it is AES-256-GCM under a
     # per-device subkey of the group's chat epoch key, signed over the
     # ciphertext with the sending device's pinned Ed25519 key. There is no
-    # plaintext form on the wire (`chatbox.py`, docs/chat-sender-keys.md);
+    # plaintext form on the wire (`chatbox.py`, docs/MESHBAY_DESIGN.md §4.5);
     # `format` distinguishes a *stored* pre-2.0 row, which is still served.
     CHAT_MESSAGE    = "chat_msg"         # one chat message, sealed and signed
     CHAT_ATTACHMENT = "chat_attach"      # attachment metadata
@@ -136,7 +136,7 @@ class MNP:
     GEK_BUNDLE_RESP      = "gek_bundle_resp"       # node → client: wrapped GEK bundle
     KEYPAIR_BUNDLE_STORE = "keypair_bundle_store"  # client → node: store encrypted keypair bundle
     #   optional `bundle_enc_recovery` (MNP 0.14): a second copy wrapped under the
-    #   account's recovery key (docs/auth-confirm.md §4.3)
+    #   account's recovery key (docs/MESHBAY_DESIGN.md §3.6)
     KEYPAIR_BUNDLE_FETCH = "keypair_bundle_fetch"  # client → node: request own keypair bundle
     KEYPAIR_BUNDLE_RESP  = "keypair_bundle_resp"   # node → client: encrypted keypair bundle
     #   carries `bundle_enc_recovery` too when the node has one stored
@@ -178,9 +178,9 @@ class MNP:
     TMDB_OVERRIDE_ACK     = "tmdb_override_ack"
     TMDB_REMATCH          = "tmdb_rematch"           # operator → node: drop one file's match
     TMDB_REMATCH_ACK      = "tmdb_rematch_ack"
-    # Music app (docs/musicbay.md). Contact is derived from the owner's hub
-    # email at login — no config/ack pair needed. Only the per-group toggle
-    # remains.
+    # Music app (docs/MESHBAY_DESIGN.md §9.8). Contact is derived from the
+    # owner's hub email at login — no config/ack pair needed. Only the
+    # per-group toggle remains.
     MUSICBRAINZ_ENABLED = "musicbrainz_enabled"          # operator → node: enable/disable
     MUSICBRAINZ_ENABLED_ACK = "musicbrainz_enabled_ack"  # node → this group: new enabled state
     MUSIC_META_REQ = "music_meta_req"                    # client → node: metadata for a path
@@ -268,7 +268,7 @@ class MNP:
     # below, which is the operator's view of the whole node: this is scoped to
     # one group and answers any member of it, because the point is that a member
     # verifies another member's device *for themselves* rather than trusting the
-    # node's `sender_id` (Tier 2, docs/desktop-client-v1.md §4.8).
+    # node's `sender_id` (Tier 2, docs/MESHBAY_DESIGN.md §3.3).
     GROUP_ROSTER_REQ     = "group_roster_req"
     GROUP_ROSTER_RESP    = "group_roster_resp"
     ROSTER_READ          = "roster_read"            # operator → node: list pinned identities + members