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

@@ -138,8 +138,7 @@ async def spawn_recurring_tasks() -> int:
                 recurrence_rule=task.recurrence_rule,
             )
             # No explicit embed here: create_note calls embed_note itself, so
-            # the spawn path stopped being a second copy of the embedding rule
-            # the moment that moved into the service (#2056, #280).
+            # the spawn path is not a second copy of the embedding rule.
         except Exception:
             logger.exception("Failed to spawn recurring task %d", task.id)
             continue