feat(guidance): an operator's ruling lives on the System it governs, and code is read as behaviour, not intent (milestone 444 steps 1-2, #4754 #4755)

A Librarian session contradicted a decision the operator had made 13 days
earlier. The ruling ("retry, then replace, never give up on a book") was
kept only as a quote in a work log, beside a session's reading of it that
capped replacements at 3. Three later sessions built on the reading, and one
carried the cap into an option as a "known cost", which the operator then
approved without being asked about it.

- writing-records.md: "A ruling goes on the System it governs". What a
  ruling is (the operator decided it; a later change could undo it), how it
  differs from a rule, and where it goes: a Rulings section at the end of
  the System description, one line each with who, when and the source
  record. Written the turn the operator decides; holds what is in force,
  not history; a charter line that contradicts a ruling is fixed in the
  same edit.
- using-scribe SKILL.md: reflex 1 says code tells you what a thing does,
  not what was wanted, and a limit read from code is unconfirmed until a
  System's Rulings says otherwise. Reflex 9 points to the ruling section.
- reporting-back: an option that carries existing behaviour says whose call
  it was (the operator's ruling, or a past session's never confirmed); one
  that contradicts a ruling is a Conflict.
- create_system / update_system docstrings: the Rulings section, and that
  description replaces the whole text.
- test_guidance_ownership: three topics pinned to their owners.
- Plugin version minted.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

plugin/skills/using-scribe/SKILL.md

@@ -52,6 +52,12 @@ Two constraints on *how* that's achieved:
    re-deriving it or opening a duplicate. When a project is in scope, pass its
    `project_id` so results stay scoped.
 
+   **Code tells you what a thing does, not what was wanted.** A limit, a
+   default or a fallback found by reading the work is a past session's choice
+   until a record says the operator made it. Before presenting one as a
+   safeguard or a known cost, read the `Rulings` on the System it belongs to;
+   when none speaks to it, call it unconfirmed rather than settled.
+
 2. **Rules are binding, and they reach you by retrieval.** No call loads the
    operator's rules and no standing set is handed to a session. A rule arrives
    when what you are about to do resembles what it is about — a command, the
@@ -227,6 +233,13 @@ Two constraints on *how* that's achieved:
    re-measurement, a reversed decision), pass the old id in `supersedes` so the
    stale record is demoted and labelled rather than left competing.
 
+   **What the operator decided an area must do is a ruling, and it lives on
+   that System** — a `Rulings` section in its description, written the turn
+   they decide. A quote in a work log reaches the next session only if a
+   search happens to match it; the description arrives with every record
+   filed there. [writing-records.md](writing-records.md) has the two tests and
+   the form.
+
 10. **A note that asserts a fact about someone else's software can carry its
    own check** (`verify_with`, `expires_when`), swept by
    `notes_due_for_verification`. Most notes should not: read
@@ -264,7 +277,8 @@ moment rather than on every turn:
   (`decide_project_inception` when `enter_project` returns `inception`).
 - [writing-records.md](writing-records.md) — before writing a rule, preference
   or lesson (where it goes, its `when_to_apply`, what already covers the
-  moment), and before giving a note a check.
+  moment), when the operator decides how an area must behave (a ruling), and
+  before giving a note a check.
 - [missed-retrieval.md](missed-retrieval.md) — a rule that missed the moment it
   governed, or keeps arriving where it doesn't apply.