docs(plugin): reference files point at each other in words, not links - one level deep (milestone 458 step 8, #4926)
CI & Build / Python lint (push) Successful in 3s
CI & Build / Plugin hooks (push) Successful in 14s
CI & Build / TypeScript typecheck (push) Successful in 56s
CI & Build / integration (push) Successful in 59s
CI & Build / Python tests (push) Successful in 2m11s
CI & Build / Build & push image (push) Successful in 41s

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
2026-10-05 16:44:22 -04:00
co-authored by Claude Opus 5.5
parent a72a422534
commit 8afd6da8af
2 changed files with 4 additions and 4 deletions
@@ -22,8 +22,8 @@ did not arrive, the action did not reach the moment on this install — offer
does not apply — is a mount or a mapping that is wrong: take the moment off
the rule, or `unmap_action` the action that reached it. Each of these
changes what the operator's sessions receive, so offer it in one line and make
it on their yes. [moments.md](moments.md) has the
detail. A rule about a subject missed its WHAT, and the rest of this page is
it on their yes. The skill's moments
reference has the detail. A rule about a subject missed its WHAT, and the rest of this page is
for that.
**Take it to the record first and the dial second.** A rule's `when_to_apply`
+2 -2
View File
@@ -62,5 +62,5 @@ 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
proposes, and only the operator's yes mounts. Writing a NEW rule is different
— its moments are part of writing it, and
[writing-records.md](writing-records.md) says how.
— its moments are part of writing it, and the
skill's guide to writing records says how.