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

@@ -1,7 +1,7 @@
 """The report-shape check: does a reply that closed a task carry the completion
 sections, and what is it sent back with when it does not.
 
-WHY THIS EXISTS (milestone 409 step 5)
+WHY THIS EXISTS
 
 Everything that helps an agent write a readable completion report arrives
 BEFORE the reply is written. The Stop hook is the one moment the finished reply
@@ -13,13 +13,10 @@ exists, so a reply that closed a task is checked for the completion sections
   - OWNING THE WORDS the agent is sent back with, so every client's hook says
     the same thing (plugin/PACKAGING.md: hooks carry timing and transport).
 
-ONE END-OF-TURN REQUEST (milestone 500 step 4). This used to be a Stop hook of
-its own that checked the sections in shell and reported here; the reply-moment
-check sent the same reply to `/reply-rules` a moment later. The hook now sends
-the reply once, with the ids of the tasks the turn closed, and the section
-check runs here beside the reply hold. The patterns are the ones the shell
-used, matched on the words that carry the meaning rather than exact headings,
-so a shape's wording can change without breaking this.
+ONE END-OF-TURN REQUEST. The Stop hook sends the reply once, with the ids of
+the tasks the turn closed, and the section check runs here beside the reply
+hold. The patterns match the words that carry the meaning rather than exact
+headings, so a shape's wording can change without breaking this.
 
 app_logs rather than a table of its own: one small event with a JSON detail is
 what that table holds, it already has retention and an admin viewer, and