docs(6209): task document, query scrubbing, note pipeline, lesson door, live body, ledger clear, rule usage

Seven more test files: docstrings and comments state the property and its
reason, the SQL-twin note states why `\m` and not `\b` without the install
it broke, and fixture provenance says "real near-miss queries" rather than
naming the spike that collected them.

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

tests/test_services_rule_usage.py

@@ -1,4 +1,4 @@
-"""Rule usage telemetry — the parts that need no database (milestone 333 step 1).
+"""Rule usage telemetry — the parts that need no database.
 
 The round trip lives in `test_integration_backup_rule_usage_roundtrip.py`.
 What is here is the payload building and the zero shape: cheap, and the half
@@ -143,10 +143,10 @@ def test_the_model_serialises_the_fields_the_ratio_needs():
     assert row["created_at"] is None
 
 
-# ─── the readout (milestone 333 step 5) ──────────────────────────────────────
-# Integration: a real GROUP BY over a real table. Step 1 unit-tested the WRITE
-# path and the zero shape and left the aggregate uncovered, which only became
-# load-bearing when the rule list started rendering it.
+# ─── the readout ─────────────────────────────────────────────────────────────
+# Integration: a real GROUP BY over a real table. The unit tests above cover
+# the WRITE path and the zero shape; the aggregate the rule list renders needs
+# a real database.
 
 
 @pytest.mark.integration
@@ -212,7 +212,7 @@ async def test_usage_for_rules_on_an_empty_id_list_asks_the_database_nothing(
 @pytest.mark.integration
 @pytest.mark.asyncio
 async def test_a_preloaded_rule_does_not_read_as_a_ranked_surfacing(_dispose_engine):
-    """The split that makes the always-on set judgeable (#3473).
+    """The split that makes the always-on set judgeable.
 
     A resident rule is delivered every session by a surface that chose
     nothing. Counting those as `surfaced_count` would rank the always-on set
@@ -262,12 +262,11 @@ async def test_a_preloaded_rule_does_not_read_as_a_ranked_surfacing(_dispose_eng
             await s.commit()
 
 
-# ── the outcome stream (#4212, milestone 419) ─────────────────────────────
+# ── the outcome stream ────────────────────────────────────────────────────
 #
-# What these guard is a distinction, not a payload. Before this existed, a
-# rule read and obeyed and a rule read and ignored left byte-identical
-# telemetry, so the readout could not name the failure the whole milestone
-# was opened on. The tests that matter most below are the ones asserting
+# What these guard is a distinction, not a payload. Without outcomes, a rule
+# read and obeyed and a rule read and ignored leave byte-identical telemetry,
+# so the readout cannot name the failure. The tests that matter most below are the ones asserting
 # that a REASONLESS DEPARTURE IS NEVER WRITTEN, and that an unacted rule is
 # a state in its own right rather than the absence of one.
 
@@ -301,7 +300,7 @@ def test_a_departure_with_no_reason_is_never_written(captured, reason):
     miss, so writing one would collapse the two states this table exists to
     separate — silently, in the readout, where nobody would see it happen.
     Dropped and reported, never stored: telemetry that lies is worse than
-    telemetry that is absent (#2663)."""
+    telemetry that is absent."""
     rule_usage.record_rule_outcome(
         user_id=7, rule_id=156, outcome=DEPARTED,
         source="mcp_rule_outcome", detail=reason or "",
@@ -357,10 +356,9 @@ def test_a_rule_opened_and_departed_from_is_departed():
 
 
 def test_a_rule_opened_and_never_acted_on_is_unacted() -> None:
-    """THE STATE THAT DID NOT EXIST, and the reason for the milestone. Not
-    "no data": the rule was surfaced, deliberately opened, and then left no
-    trace of having mattered. Until now that was arithmetically identical to
-    compliance, which is why nothing could report it."""
+    """THE UNACTED STATE. Not "no data": the rule was surfaced, deliberately
+    opened, and then left no trace of having mattered. Without this state it
+    is arithmetically identical to compliance, and nothing can report it."""
     assert rule_usage.outcome_state(
         _usage(surfaced_count=4, pull_count=2)
     ) == rule_usage.UNACTED
@@ -389,5 +387,5 @@ def test_a_departure_outranks_an_application():
 def test_the_state_reads_the_aggregate_the_readout_already_returns():
     """`outcome_state` takes `usage_for_rules`' own shape, so the badge, the
     readout and any later session summary cannot disagree about what
-    "followed" means — the drift #3246 found across the rules system."""
+    "followed" means."""
     assert rule_usage.outcome_state(rule_usage.empty_rule_usage()) == rule_usage.UNREAD