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/text.py

@@ -25,7 +25,7 @@ def elide(text: str, budget: int) -> tuple[str, bool]:
 
     This is the fallback, not the goal. Where the system knows WHICH span of a
     record is the relevant one — a semantic search knows exactly that, and
-    stores it (#4243) — show that span and say so. Reach for this only when
+    stores it — show that span and say so. Reach for this only when
     nothing identifies a better part than "all of it".
     """
     if budget <= 0 or len(text) <= budget:
@@ -41,11 +41,9 @@ def elide(text: str, budget: int) -> tuple[str, bool]:
 # What a search result shows a reader, as one decision made in one place.
 #
 # Every door onto a semantic search faces the same question — which span of a
-# record do I show someone deciding whether to open it? — and each used to
-# answer it separately with a bare head cut of a different length: 240
-# characters in the MCP search, 200 in the web's knowledge search. Both showed
+# record do I show someone deciding whether to open it? A bare head cut shows
 # the document's OPENING, which is not the span that matched and not the span
-# the ranking was built on.
+# the ranking was built on, and a cut per door gives each a different answer.
 #
 # Doors keep their own field names (the web UI renders `snippet`, the MCP
 # surface returns `excerpt`), because renaming a field a frontend consumes is