feat(moments): mount the corpus by proposal - a pass and an open-after-moment signal, both stopping at the operator (milestone 458 step 7, #4925)

A rule written before moments existed is mounted on nothing. Step 7 records,
per (rule, moment), whether it belongs there and who said so:

- rule_moment_judgments (migration 0118, backup v23): suggested / confirmed /
  rejected, from a pass, the signal, or an edit. Moment "" is "no moment fits".
- The pass: rules_to_mount lists unjudged rules; propose_rule_moments records
  suggestions that mount nothing; rule_moment_proposals and
  judge_rule_moments put them to the operator. A confirm mounts, a reject is
  kept so the pair is never proposed again. Same service behind REST and a
  "Waiting on you" panel in Settings > Moments.
- Edits are judgments: set_rule_moments, the one mount write path, confirms
  what was added and rejects what was removed in the same transaction.
- The signal: scribe_moment.sh keeps a per-session acts ledger; when a rule
  is opened, scribe_record_opened.sh sends the last three minutes of it to
  /api/plugin/rule-opened. The acts resolve through the install's mappings;
  work.run and work.change are not evidence. Counted per distinct session
  with lesson_rules' evidence model, and once due the open returns one line
  asking the reader to offer the mount.
- scribe_session_end.sh removes the session's scribe-moment files.

Plugin 2026.10.05.2003.

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

plugin/hooks/scribe_record_opened.sh

@@ -33,6 +33,10 @@
 # claim it supports is only ever "you opened this, pull it again if you no
 # longer hold it", which stays true in every case and carries its own remedy.
 #
+# SINCE MILESTONE 458 STEP 7 it also reports the open, with the calls that
+# came just before it, so the server can learn which moments a rule belongs
+# on (below). Silent on outage, like every arm that fires per call.
+#
 # EXIT 0, ALWAYS. This decorates a ledger; a bookkeeping failure must never
 # turn a successful tool call into a hook error. Worst case the id is missed
 # and the reader is offered a rule it already read — the cost of a wrong guess
@@ -68,4 +72,35 @@ safe_sid=$(printf '%s' "$session_id" | tr -c 'A-Za-z0-9._-' '_')
 # Stamped and append-only, exactly like the naming ledger — so the same reader
 # (`scribe_rules_live`) ages both, and the last entry for an id wins.
 printf '%s\n' "$rule_id" | scribe_rules_append "$state_dir/${safe_sid}.opened.ids"
+
+# ── What came just before the open (milestone 458 step 7) ─────────────────
+#
+# scribe_moment.sh writes every call to `scribe-moment/<sid>.acts`. The ones
+# from the last three minutes go to the server with this rule's id: a rule
+# opened just after a moment fired is evidence it belongs on that moment, and
+# once that repeats across sessions the server answers with one line asking
+# the reader to offer the operator the mount. Nothing is mounted by this.
+command -v curl >/dev/null 2>&1 || exit 0
+scribe_config || exit 0
+acts_file="${TMPDIR:-/tmp}/scribe-moment/${safe_sid}.acts"
+[ -f "$acts_file" ] || exit 0
+now=$(date +%s 2>/dev/null) || exit 0
+acts=$(awk -F '\t' -v since=$((now - 180)) \
+  '$1 + 0 >= since { sub(/^[^\t]*\t/, ""); print }' "$acts_file" 2>/dev/null \
+  | tail -n 30 | paste -sd ',' - 2>/dev/null)
+[ -n "$acts" ] || exit 0
+
+sid_esc=$(printf '%s' "$session_id" | scribe_json_escape) || exit 0
+event_cwd=$(scribe_json_pick "$event_flat" '.cwd')
+scope=$(scribe_scope_query "${event_cwd:-${CLAUDE_PROJECT_DIR:-$PWD}}")
+body=$(printf '{"rule_id":%s,"session_id":"%s","acts":[%s]}' "$rule_id" "$sid_esc" "$acts" \
+  | curl -fsS --max-time 3 \
+    -H "Authorization: Bearer ${token}" \
+    -H "Content-Type: application/json" \
+    --data-binary @- \
+    "${url%/}/api/plugin/rule-opened${scope:+?$scope}" 2>/dev/null) || exit 0
+
+context=$(scribe_json_pick "$(printf '%s' "$body" | scribe_json_flat)" '.context')
+[ -n "$context" ] || exit 0
+scribe_json_out PostToolUse "$context"
 exit 0