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/rulebooks.py

@@ -308,13 +308,12 @@ async def create_rule(
     and let the answer stand; re-raising a declined proposal argues a rule
     into existence, which is the thing this whole loop exists to prevent.
 
-    A rulebook rule is shared by every project that gets the rulebook: an
-    A subscribed rulebook binds the
-    projects that opt in. So a rulebook rule must read as a general standard —
+    A rulebook rule is shared by every project subscribed to the rulebook, so
+    it must read as a general standard —
     never pin it to one project's files, paths, or quirks. For a rule that
     applies to a single project only, use create_project_rule instead (no
     rulebook+topic ceremony). If it's a standard a CATEGORY of projects shares,
-    put it in a themed subscribed rulebook, not the always-on one.
+    put it in a rulebook for that category and subscribe those projects to it.
 
     Write it general WITHOUT hedging for the exceptions. A project that needs
     to strengthen, narrow or replace this rule writes its own and links it
@@ -1048,8 +1047,8 @@ async def rules_due_for_verification(
         never_only: only rules nobody has ever verified.
 
     NOT filterable by project, deliberately: a project reaches rules through
-    project scope, subscriptions, always-on rulebooks and exclusions, and a
-    filter that missed one of those paths would UNDER-report — which is the
+    project scope and rulebook subscriptions, and a filter that missed one of
+    those paths would UNDER-report — which is the
     exact failure this whole surface exists to prevent. Read the whole list.
     """
     uid = current_user_id()