feat(moments): a mount that keeps arriving where it does not apply proposes its own removal (milestone 458 step 7b, #4955)

The open-after-moment signal proposes a mount; nothing proposed taking one
off, so a wrong mount was noise at every occurrence until someone happened
to notice. rule_misfired(rule_id, moment, why, reached_by) records a report
against a MOUNTED pair, counted per distinct day (the MCP door carries no
session id) on a new rule_moment_judgments.misfire column (migration 0119,
backup v24). At three days the response carries a line asking the agent to
offer the operator the fix - reject takes the rule off, unmap_action stops
the action reaching the moment, confirm keeps the mount and stops the
asking - and Settings > Moments lists it as an unmount proposal with the
reasons and the actions that reached it. A re-mount clears the count.

Taught in moments.md, missed-retrieval.md and the reply hold's wording.

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

tests/test_guidance_ownership.py

@@ -195,6 +195,9 @@ TOPICS: tuple[Topic, ...] = (
     Topic("a new rule about when gets its moments as it is written", U,
           ("moments=[...]", "create_process(moments="),
           "then ask when it applies, as well as what it is about"),
+    Topic("a mount that arrives where it does not apply is reported, and reports become the offer", U,
+          ("rule_misfired",),
+          "a rule you read and set aside leaves no trace anyone else can see"),
     Topic("a missed when is mounted or mapped, not reworded", U,
           ("update_rule(moments=",),
           "first ask whether it missed a when or a what"),