wip(394): steps 6+7 — backend path and instruction surfaces

src/scribe/services/rule_usage.py

@@ -46,7 +46,7 @@ AMBIENT VS RANKED. The note twin splits ranked surfacings from ambient ones
 because `enter_project` and the skill sync put records in front of the agent
 without choosing them, and counting those as surfacings makes recency read as
 popularity (#2477). Rules have exactly that shape: the SessionStart preload,
-`list_always_on_rules`, and every `rules_payload` surface hand over the whole
+and every `rules_payload` surface hand over the whole
 applicable set at once, chosen by nobody.
 
 Until 2026-09-03 those bulk surfaces emitted nothing, and this module said so —
@@ -184,8 +184,8 @@ def record_rule_surfaced(
 def record_rule_pulled(*, user_id: int | None, rule_id: int, source: str) -> None:
     """Fire-and-forget: record that a rule was opened in full.
 
-    A PULL is somebody choosing to open one record. `list_always_on_rules` and
-    `enter_project` are NOT pulls — they are bulk resident loads that hand over
+    A PULL is somebody choosing to open one record. `enter_project` is NOT a
+    pull — they are bulk resident loads that hand over
     every applicable rule at once, and counting them would swamp the signal
     with the very ambient delivery the ratio exists to distinguish from.
     """