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

@@ -1,6 +1,6 @@
-"""One APScheduler job bridged into the asyncio loop — the shape the four
+"""One APScheduler job bridged into the asyncio loop — the shape the
 *_scheduler modules (recurrence spawn, auto-pin scan, trash purge, DB
-maintenance) each used to carry a private copy of.
+maintenance) share instead of each carrying a private copy.
 
 APScheduler's BackgroundScheduler fires from a worker thread; the work is
 async and must run on the app's loop, so the fire is bridged with