fix(6470): a moment proposal counts only opens no hook explained, and asks the reader to judge it

The signal counted every get_rule open against every moment from the
previous three minutes, so a rule a search arm had just shown was
proposed for whatever moment happened to fire. All nine pending signal
proposals were wrong.

- The hook skips an open of a rule a hook named this session, and sends
  the last three acts from 90 seconds instead of 30 from 180.
- A rule already mounted anywhere gathers no signal evidence.
- A signal pair keeps the actions that reached its moment and shows them
  as its why.
- The proposal line says it is co-occurrence, not a recommendation, and
  asks the reader to check the rule against the moment before offering
  it; moments.md says the same.

Plugin 2026.10.26.2029.

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

plugin/skills/using-grimoire/moments.md

@@ -73,12 +73,16 @@ than a mount is fixed through its trigger instead.
 
 ## When a line proposes a mount
 
-A rule that keeps being opened just after the same moment, across several
-sessions, probably belongs on that moment. A line says so, naming the rule,
-the moment and how often. It is a question for the operator, not a change you
-make: offer it in one line, and record their answer with
-`judge_rule_moments` — `confirm` mounts the rule, `reject` with their reason
-stops the question being asked again.
+A rule that sessions keep going and opening just after the same moment —
+without a hook having shown it to them first — may belong on that moment. A
+line says so, naming the rule, the moment, the action that reached it and how
+often. That is co-occurrence, not a recommendation, so judge it before it
+reaches the operator: read the rule's trigger against what the moment means
+(`list_moments`). Offer it only when the rule governs that point in the work
+whatever the work is about, as a question with your reason; a rule about a
+subject (a library, a file, a style) is reached by meaning, and the line is
+left alone. Record their answer with `judge_rule_moments` — `confirm` mounts
+the rule, `reject` with their reason stops the question being asked again.
 
 The same tool answers proposals from a pass over the rules
 (`rules_to_mount`, `propose_rule_moments`, `rule_moment_proposals`): a pass