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

@@ -845,7 +845,7 @@ async def mark_note_verified(
     So a failed check leaves `verified_at` untouched and the note stays at the
     top of the sweep until someone actually deals with it.
 
-    Write access, not read (rules 47/78): stamping is a mutation, and an
+    Write access, not read: stamping is a mutation, and an
     editor-share holder may make it while a viewer may not.
 
     Returns None when the note is not found, not writable, or carries no