fix(410): using-scribe states the retrieval reflex once, and the adapter stops restating it (#4039)

Step 7's live check (#4034 "a real session shows each topic stated once")
found nothing copied across surfaces, but found the owner repeating itself:
using-scribe said "rules are retrieved; ask before a consequential act; an
empty session is not an empty rulebook" in "Do this first", in reflex 2, and
twice more further down reflex 2.

- using-scribe: reflex 2 now holds the one full statement (how rules arrive,
  why that is the surface working, what silence means, when to ask). "Do this
  first" keeps the enter_project step and a short lead-in pointing at reflex
  2. "A retrieved rule outranks a default habit" and "Ask hardest where you
  feel most certain" stay, since each adds something.
- Adapter static context: "Lines injected beside your work" keeps only the
  Claude Code timing and leaves "never the whole set" to the skill. "Keep one
  copy" names CLAUDE.md and auto-memory and points at using-scribe, which
  already says to leave a client's settings as they are.
- The ownership registry's markers and statement for the topic still sit on
  using-scribe, and nothing else changed owner. Plugin version minted.

Sizes: using-scribe 18,823 -> 18,197 chars; scribe_static_context.md
1,797 -> 1,714.

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

plugin/hooks/scribe_static_context.md

@@ -10,15 +10,14 @@ shape-accounting) carry their arcs.
 
 What only Claude Code needs said:
 
-- **Keep one copy — in Scribe, not Claude Code's local memory.** The
-  operator's rules, plans and project notes go to Scribe, not also to
-  `CLAUDE.md` or auto-memory. Leave auto-memory at its default setting: you
-  replace its job by doing the work in Scribe, not by switching it off.
+- **Keep one copy — in Scribe, not Claude Code's local memory.** Claude
+  Code's local memory is `CLAUDE.md` and auto-memory: the operator's rules,
+  plans and project notes go to Scribe instead, and using-scribe says how
+  Scribe works alongside them.
 - **Lines injected beside your work are retrieval.** When the operator sends a
   message, and before a write or a command, Scribe may add rules, preferences,
   notes and prior art that resemble what you are doing. Open the ones that
-  apply. They are what matched, never the whole set — using-scribe says how to
-  ask for the rest.
+  apply; using-scribe says what a quiet turn means.
 - **Compact at clean seams.** Because work is recorded as you go, a compaction
   is safe once in-flight state is logged. After finishing a block of work in a
   long session, log it to Scribe, then tell the operator it's a good moment to