docs(6206): settings, projects, api routes and three models drop citations; four capitalised services stragglers

- api.py's build-version docstring states why a channel name is not a build
  id, without the dated incident.
- rule_version states why rules need a history, without the rule that was
  rescoped and the date.
- Capitalised "Rule N" / "Milestone N" citations the earlier lowercase grep
  missed, in reply_shapes, supersession, services/family and models/family.

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

src/scribe/services/family.py

@@ -449,7 +449,7 @@ async def _open_ledger(session, user_id: int, note_id: int) -> int:
     )).scalars().all())
     opened = 0
     for pid in sorted(project_ids - answered):
-        # Rule 78: a promotion reaches only the projects its promoter could
+        # A promotion reaches only the projects its promoter could
         # have written an answer into themselves.
         if await access.can_write_project(user_id, pid):
             session.add(FamilyAdoption(project_id=pid, idea_id=note_id, status="unassessed"))

src/scribe/services/reply_shapes.py

@@ -3,11 +3,11 @@
 WHY THIS EXISTS
 
 A reply is where the person the work is for finds out what happened, and they
-were not there while it was done. Milestone 409 wrote the shapes that make a
-reply readable to them — conclusion first, the shortest reply that carries the
-answer, where the work stands — and put them in one bundled skill. A skill
-arrives only when the agent decides to load it, so in a long session the shape
-faded out of context exactly when replies were getting longer.
+were not there while it was done. The shapes make a reply readable to them —
+conclusion first, the shortest reply that carries the answer, where the work
+stands. A skill arrives only when the agent decides to load it, so in a long
+session a shape held in a skill fades out of context exactly when replies get
+longer.
 
 So the shapes are product content held here, on the server, and delivered by
 the moments they belong to rather than by the agent remembering to ask:

src/scribe/services/supersession.py

@@ -82,7 +82,7 @@ async def set_supersedes(
     silent drop, because it is the one case where the caller might reasonably
     believe they succeeded and be wrong in a way that matters — demoting someone
     else's record out of their retrieval is damage you cannot see from the
-    outside. Rule #47.
+    outside.
     """
     if not await access.can_write_note(user_id, note_id):
         return None