docs(plugin): the instruction surfaces teach moments - reading a line that arrived at one, correcting a misfire, and giving a new rule its moments (milestone 458 step 8, #4926)

Until now only the tool arguments knew moments existed. The guidance
surfaces described rules as reached by resemblance alone:

- using-scribe: a short reflex paragraph and a new reference file,
  moments.md. It covers reading "at <moment>, reached by <action>", the
  reply held once at reply.report, map_action / unmap_action offered in
  one line, and the step 7 proposal line answered with judge_rule_moments.
- writing-records: asks WHEN a rule applies as well as what it is about.
  A rule, preference or process about a point in the work gets
  moments=[...] as it is written, and the trigger stays as the net.
- missed-retrieval: a missed WHEN is mounted or mapped, not reworded. A
  misfire is unmounted or unmapped.
- _INSTRUCTIONS: one clause (list_moments; mount rules about WHEN),
  1594 of 1600 chars.
- static context: injected lines include the rules mounted on a moment
  that was reached.
- test_guidance_ownership: three owned topics, so the text cannot quietly
  drop out.

Plugin minted.

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

plugin/skills/using-scribe/writing-records.md

@@ -1,13 +1,15 @@
 # Writing a rule, a lesson, or a note that asserts a fact
 
 Part of the using-scribe skill. Read it before `create_rule`,
-`create_project_rule`, `create_preference` or `create_lesson`; when a lesson
+`create_project_rule`, `create_preference`, `create_process` or
+`create_lesson`; when a lesson
 arrives that names the situation you are actually in; when the operator
 decides how some area of the work must behave; and before filling
 `verify_with` or `expires_when` on a note.
 
 ## Contents
 - Where a new rule goes — its home, its trigger, what already covers the moment
+- When it applies — the moments a rule, a preference or a process is for
 - A ruling goes on the System it governs
 - A lesson grows each time it proves itself
 - A lesson names the rule it is an instance of
@@ -39,6 +41,22 @@ with no trigger is not a quiet rule, it is an unreachable one. Write the moment
 in the words a session actually produces — the command, the error, the
 half-formed ask — not the category it belongs to.
 
+**Then ask WHEN it applies, as well as what it is about.** A trigger is
+matched by resemblance, and a rule about a point in the work — finishing,
+delivering, verifying, reporting, asking — resembles nothing said at that
+point. Give such a rule its moments as you write it: `list_moments` names
+them, and `moments=[...]` on `create_rule`, `create_project_rule` or
+`create_preference` mounts it, so it arrives whenever an action reaches one.
+Keep the trigger anyway: it is the net for the moments nobody mapped. A rule
+about a subject — a library, a file, a style — has no moment; it is reached
+by meaning, and leaving `moments` empty is the answer, not an omission. A rule
+often has both: a point in the work, and the words a session uses at it.
+
+A stored **process** says the same about itself: `create_process(moments=…)`
+names the moments the procedure is for, so loading it reaches them and the
+rules mounted there arrive with it. A rule that only applies inside one
+procedure mounts on that procedure's own moment, `skill.<name>`.
+
 **Before writing one, ask what already covers that moment.**
 `what_might_apply("the moment you are about to write a record for")` — fifty
 candidates and no bar, so an existing record cannot hide under a threshold the