docs(6205): rule_moment_judgments, retrieval_migration, repo_bindings, moments, logging, design_systems comments drop citations

retrieval_migration states what it lets a tuned floor do without quoting
the operator, and its order-of-operations refusal is described as enforced
rather than as history. logging states why raw date filters fail rather
than citing the two issues that found it. The rest drop milestone, step and
record citations; step references now name the code that does the job.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

src/scribe/services/design_systems.py

@@ -1,6 +1,6 @@
 """Design system + token persistence, and the guard on the parent chain.
 
-Access goes through `services/access.py` (rule #78), where reaching a system via
+Access goes through `services/access.py`, where reaching a system via
 a project you can see grants READ but never write — see
 `get_design_system_permission` for why that asymmetry exists.
 
@@ -92,7 +92,7 @@ async def create_design_system(
     which, per the ACL, means one they do not own.
 
     `starter_role_groups` seeds the system with named, VALUELESS token roles
-    (#2349) — the moment a role is missing is the moment a literal gets written
+    — the moment a role is missing is the moment a literal gets written
     instead, so the cheapest time to name them is now. Pass a list of group
     names to choose, `[]` for none, or None for none.
 
@@ -244,7 +244,7 @@ async def create_token(
 async def list_tokens(user_id: int, design_system_id: int) -> list[DesignToken]:
     """One system's OWN tokens — its override set, not its effective set.
 
-    Resolving the chain is step 2's job; this deliberately answers the narrower
+    Resolving the chain is `resolve_design_system`'s job; this deliberately answers the narrower
     question ("what does this system change?") that the model exists to make
     free.
     """