docs(6209): the remaining test files — lessons, reply moment and shape, retrieval specs and scopes, rule doors and judgments, services, snippets, search scope; five tests renamed to their property

Docstrings, section headers and assertion messages drop the record number,
milestone or step that introduced the behaviour, and incident accounts are
restated as the present-tense failure shape. A dead pointer to a design doc
that is not in the repo is removed.

Renamed to the property they check:
  test_the_old_shape_would_be_caught -> test_a_rank_then_scope_query_is_caught
  test_a_ledger_repeat_no_longer_produces_that_case_at_all -> test_a_ledger_repeat_is_counted_not_withheld
  test_the_header_no_longer_promises_once_per_session -> test_the_header_explains_the_seen_marker
  test_the_portal_case_no_longer_stamps_one_canon_onto_a_whole_file -> test_one_canon_is_not_stamped_onto_a_whole_file
  test_the_repos_own_prose_no_longer_defines_with -> test_the_repos_own_prose_does_not_define_with
  test_the_original_regression_create_note_with_content -> test_the_real_server_refuses_content_on_create_note

Fixture and example ids stay: "note 5" in a supersession chain, "rule 156"
in an illustrative question, `#2275` as the hex-versus-citation case,
`#3244` as the example of a bare number, fixed dates in date-filter tests.

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

tests/test_recurrence.py

@@ -1,11 +1,10 @@
 """Tests for task lifecycle timestamps and recurrence logic.
 
-The note stand-ins come from `fake_note`, not a bare MagicMock. These four
-predated that helper and broke the moment `update_note` started reading a
-column they did not set (milestone 317): a fresh MagicMock is truthy on every
-attribute, so `verify_with` read as "this record carries a check" and the
-guard refused the write. That is note 2109's lesson, and the reason fake_note
-exists — a stand-in has to be able to say NO.
+The note stand-ins come from `fake_note`, not a bare MagicMock. A fresh
+MagicMock is truthy on every attribute, so once `update_note` reads a column
+the stand-in did not set, `verify_with` reads as "this record carries a check"
+and the guard refuses the write. That is the reason fake_note exists — a
+stand-in has to be able to say NO.
 """
 from datetime import date, datetime, timezone
 from unittest.mock import AsyncMock, MagicMock, patch