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_mcp_tool_report_back_cue.py

@@ -1,11 +1,10 @@
 """update_task closes a task with a one-line reminder of what the report needs.
 
-The in-band half of milestone 409 step 3: the skill and static context only
+This is the in-band half of reporting back: the skill and static context only
 exist in the Claude Code plugin, and a tool response reaches every MCP client
 at the moment a piece of work closes. Pinned on the response, not the wording.
 
-The operator's own completion-report preferences used to ride here too, from
-a fixed-question search (409 step 4). Milestone 500 retired that: they are
+The operator's own completion-report preferences do not ride here: they are
 mounted on finishing work and arrive in `moment_rules` beside the delivered
 reply shape, so this response carries no key of its own for them.
 """
@@ -55,7 +54,7 @@ _OWED = {"idea_id": 9, "idea_title": "Signed APK lane", "project_id": 4,
 
 
 async def test_closing_names_the_owed_adoptions_filed_while_the_task_was_open():
-    """The finishing moment of milestone 463 step 6: owed family work filed
+    """The finishing moment of family canon: owed family work filed
     into a project during this task comes back for the report to name."""
     from scribe.services.family_adoption import OWED_CUE