#6470 — a moment-mount proposal counts only a rule the session went and opened itself (not one a hook had just shown), over the last 3 acts in 90 s; a mounted rule gathers no signal; a proposal shows the action that reached its moment as its why; the line says it is co-occurrence, not a recommendation, and asks the reader to check it first.
#6471 — the end-of-turn shape check hears every definition a write made (up to 40 files per Bash call), while the prior-art query stays bounded at 4 files × 12 names.
Two fixes, both CI-green on dev (run 9902):
- **#6470** — a moment-mount proposal counts only a rule the session went and opened itself (not one a hook had just shown), over the last 3 acts in 90 s; a mounted rule gathers no signal; a proposal shows the action that reached its moment as its why; the line says it is co-occurrence, not a recommendation, and asks the reader to check it first.
- **#6471** — the end-of-turn shape check hears every definition a write made (up to 40 files per Bash call), while the prior-art query stays bounded at 4 files × 12 names.
Plugin 2026.10.26.2029.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
The write hooks recorded at most 12 definitions per write (alphabetical,
so test functions were the ones dropped) and the post-Bash hook stopped
after 4 files, so the Stop hook never asked about the rest. The caps
bound the prior-art query; the written ledger now gets the full list,
up to 40 files per Bash call, while the query stays at 4 files x 12 names.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Two fixes, both CI-green on dev (run 9902):
Plugin 2026.10.26.2029.
🤖 Generated with Claude Code