docs(6205): the remaining services files state the reason, not the instance that taught it

The 1-2 hit tail: access, background, backup, backup_job, canonical_systems,
design_stylesheet, forge_connections, moment_actions, notes, notifications,
placement, planning, platforms, projects, record_batch, recurrence,
report_check, retrieval_review, rule_scope, rule_versions, scheduler,
shape_check, supersession, system_rulings, system_usage, text, trash,
verification, version_pinning.

Also corrected while reading:
- backup.py said restore step 16 fills the System map; step 15 does.
- version_pinning.py pointed at a design doc that is not in the repo.

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

src/scribe/services/supersession.py

@@ -1,6 +1,6 @@
 """Which records have been overtaken by which — the claim, not the ranking.
 
-Step 2 of milestone #278. This module only records and reads the relation; the
+This module only records and reads the relation; the
 demotion that makes it matter lives in the retrieval layer.
 
 WHY THE CLAIM POINTS FORWARD
@@ -202,8 +202,8 @@ async def attach_relations(user_id: int, note_id: int, data: dict, *, hint: bool
     acted on confidently, which is worse than never surfacing it.
 
     Omitted entirely when empty, so an ordinary note's payload doesn't grow
-    two permanently-empty lists (#2483 — a field that always says nothing
-    trains readers to skip fields). `hint=True` (the agent surface) also
+    two permanently-empty lists — a field that always says nothing trains
+    readers to skip fields. `hint=True` (the agent surface) also
     attaches `superseded_note`, the one-sentence reading instruction.
     """
     rel = await get_relations(user_id, note_id)