fix(#4022): instruction surfaces stop describing the always-on tier milestone 394 removed

Skill bodies and tool docstrings still taught the deleted model: using-scribe
said always-on rules "arrive whether or not you ask" and that SessionStart may
inject a rule index; create_project, decide_project_inception and enter_project
said an undecided project gets "every always-on rulebook"; create_rule pointed
standards at "the always-on one"; the verification sweeps and
retrieval_telemetry listed always-on paths and a live preload.

Every passage now describes the current model: every rule is retrieved, a
rulebook binds only by subscription, an undecided project inherits nothing,
and the preload survives only in telemetry rows older than 394.

Also repairs three sentences left half-replaced by the 394 edits: the static
context's "If you have not loaded the no rule has arrived", create_rule's
"an A subscribed rulebook", and create_project's doubled
subscribe_rulebooks entry. Plugin version minted.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

src/scribe/mcp/tools/search.py

@@ -280,19 +280,20 @@ It is an UPPER BOUND per surface: a pull records the door it came
 
     `surfaced` VS `ambient` IS THE READING THAT MATTERS HERE. `surfaced` counts
     rules a ranker chose — today only the write-path arm — and those are claims
-    a pull can settle. `ambient` counts BULK DELIVERIES: the SessionStart
-    preload and the `rules_payload` surfaces
-    (`enter_project`, `get_project`, `get_milestone`, `start_planning`,
-    `get_task`), which hand over the whole applicable set at once with nobody
-    choosing anything. A large `ambient` says the resident set is big and
-    arrives often — never that it is useful, and never that it is read.
+    a pull can settle. `ambient` counts BULK DELIVERIES: the `rules_payload`
+    surfaces (`enter_project`, `get_project`, `get_milestone`,
+    `start_planning`, `get_task`), which hand over the whole applicable set at
+    once with nobody choosing anything — plus, in rows older than milestone
+    394, the SessionStart preload it removed. A large `ambient` says a bulk set
+    is big and arrives often — never that it is useful, and never that it is
+    read.
 
     `pull_through` therefore divides by `surfaced` alone. Fold the preload in
-    and growing the always-on set would depress the arm's measured precision
-    while trimming it would flatter it, for reasons having nothing to do with
-    the arm. To judge the PRELOAD instead, compare `ambient` against pulls of
-    those same rules over time: a resident set surfaced thousands of times and
-    opened never is the dead-weight signal, one tier up.
+    and growing a bulk set would depress the arm's measured precision while
+    trimming it would flatter it, for reasons having nothing to do with the
+    arm. To judge a BULK surface instead, compare `ambient` against pulls of
+    those same rules over time: a set surfaced thousands of times and opened
+    never is the dead-weight signal, one level up.
 
     Read it against `sources["write_path_rule"]`. That arm was once believed
     never to decline — the reading that scoped #3311 — but it was the arm's