docs(6209): lesson links, design roles, version readout and endpoint, timestamp filters, settings defaults, opened ledger, surfaces

Eight more test files state their properties without issue, milestone and
rule numbers or dated regressions. The version tests describe what folding
the channel into the version breaks instead of the date it did; the surface
registry and settings-defaults tests state that floors move rather than
quoting the decision that made them move.

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

tests/test_settings_defaults_agree.py

@@ -1,4 +1,4 @@
-"""The Settings UI shows the default the server actually uses (#3927).
+"""The Settings UI shows the default the server actually uses.
 
 WHY THIS EXISTS
 
@@ -17,8 +17,7 @@ WHAT THIS PINS
 
 The RELATIONSHIP, never the number: for each threshold, the Vue ref's initial
 string equals the Python default. Retuning either stays free as long as both
-move — which is the point, because these are tuning values and #3853 moved one
-of them the day this was written.
+move — which is the point, because these are tuning values and they move.
 
 The Vue side is read from SOURCE, because that file cannot be imported at all.
 The Python side is read from source for a loose constant and IMPORTED for a
@@ -42,7 +41,7 @@ ROOT = pathlib.Path(__file__).resolve().parents[1]
 _SERVICES = ROOT / "src" / "scribe" / "services"
 _VUE = ROOT / "frontend" / "src" / "views" / "SettingsView.vue"
 
-# THE SIX RETRIEVAL FLOORS now live in one registry (#4102), so their side of
+# THE SIX RETRIEVAL FLOORS live in one registry, so their side of
 # the pairing is a SURFACE NAME rather than a module constant. That is strictly
 # better for this guard: the surface name is also the telemetry source, so a row
 # here names the same arm the readout does, and a floor that moved cannot be
@@ -62,7 +61,7 @@ _SURFACE_PAIRS = (
 # exist on both sides, so a rename fails loudly rather than silently dropping
 # that threshold from the check.
 _CONSTANT_PAIRS = (
-    # The plan gate (milestone 415): it blocks a create, so a form showing a
+    # The plan gate: it blocks a create, so a form showing a
     # looser bar than the one in force would be the more misleading drift. Not
     # a push surface, so it has no registry entry and keeps the older shape.
     ("dedup.py", "PLAN_MATCH_DEFAULT_THRESHOLD", "kbPlanMatchThreshold"),
@@ -87,7 +86,7 @@ def _vue_default(ref_name: str) -> float:
     assert m, (
         f"{ref_name} is no longer a `ref(\"<number>\")` in SettingsView.vue. "
         f"If the control was renamed, update _PAIRS; if it was removed, the "
-        f"setting has lost its UI and that is the thing to fix (rule 25)."
+        f"setting has lost its UI and that is the thing to fix."
     )
     return float(m.group(1))
 
@@ -112,7 +111,7 @@ def test_the_form_shows_the_floor_the_surface_uses(surface, ref_name):
 
 
 def test_every_tunable_surface_has_a_control():
-    """Rule 25/27: a number an operator may need different has a UI or it is
+    """A number an operator may need different has a UI or it is
     not shipped. Derived from the registry, so a seventh surface arrives here
     as a failure rather than as a setting only the model can reach."""
     from scribe.services.retrieval_surfaces import surface_names