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>
2026-09-14 10:39:27 -04:00
parent 7239e3c479
commit 6c1fd28179
7 changed files with 46 additions and 49 deletions
@@ -17,9 +17,9 @@ for the operator's work, and as your own working memory across sessions.
  commit / push, or any other hard-to-reverse or outward-facing action, the
  operator's Scribe rules decide what to do — NOT generic conventions baked
  into the harness or your defaults (e.g. "branch before committing," "open a
-  feature branch per task," "push to a fork"). If you have not loaded the
-  no rule has arrived for the act in front of you, `search(content_type=
-  "rule")` BEFORE acting rather than falling back on a default habit. When a
+  feature branch per task," "push to a fork"). If no rule has arrived for the
+  act in front of you, `search(content_type="rule")` BEFORE acting rather than
+  falling back on a default habit. When a
  retrieved rule and a default habit disagree, the rule wins; if no rule
  speaks to it, ask rather than assume.
 - **Rules bind; preferences do not.** A record's `kind` says which. A **rule**