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

@@ -92,11 +92,10 @@ async def log_error(
 def parse_filter_datetime(value: str | None, *, end_of_day: bool = False) -> datetime | None:
     """An ISO date/datetime from a query string as an AWARE UTC datetime.
 
-    The admin log filters arrive as raw `request.args` strings and used to be
-    compared straight against `AppLog.created_at`. asyncpg binds a str as
-    VARCHAR and Postgres has no `timestamptz >= text` operator, so supplying
-    either date filter raised — the same defect as #1727 in notifications, in a
-    second place (#2254).
+    The admin log filters arrive as raw `request.args` strings. Compared
+    straight against `AppLog.created_at`, they fail: asyncpg binds a str as
+    VARCHAR and Postgres has no `timestamptz >= text` operator, so either date
+    filter would raise.
 
     Returns None for anything unparseable: a malformed filter should narrow
     nothing rather than 500 the log viewer.