docs: regenerate the skill-triggers block

[EdbertChan]

Summary

Every PR's preflight was failing on a generated docs block that had fallen behind the skills on disk.

Regenerating the block clears that failure, for any PR, whether or not it touches skills.

Nothing else changes.

Review Claim

docs/skill-triggers.md holds the current output of scripts/check_skill_trigger_policy.py --write, so that gate passes.

Review Lane

docs

Review Unit

docs

Safety Invariant

One generated file, written by the repo's own --write flag. No skill, script, or hook changes.

Slice Rationale

Repo debt found while writing an unrelated rule. It lands on its own so the rule's PR does not carry a docs file, and so any other PR blocked by the same gate is unblocked by one merge.

Non-goals

• No change to the checker or to any skill's triggers.
• No hand edits inside the generated block.

Test Plan

Test Plan

• Before, on a clean checkout of main at 329c844: python3 scripts/check_skill_trigger_policy.py printed fail docs/skill-triggers.md: generated block is stale; run python3 scripts/check_skill_trigger_policy.py --write, exit 1
• After --write on this branch: ok skill trigger policy, exit 0
• The diff is two lines in the generated block and nothing else: docs/skill-triggers.md | 4 ++--

Revert Plan

Revert Plan

• Safe to revert? Yes.
• Revert command: git revert <merge-sha>
• Post-revert steps: None. The gate goes back to failing on main.
• Data migration? No

🤖 Generated with Claude Code

https://claude.ai/code/session_01Gnua5cuAAF1ey1b7zRqJCC

---

Note

Low Risk
Single generated docs file sync; no runtime, auth, or policy script changes in this diff.

Overview
Refreshes the generated inventory in docs/skill-triggers.md via check_skill_trigger_policy.py --write so the preflight gate stops reporting a stale block.

The only inventory delta is phrase-judge joining the auto-fire list (count 21 → 22). No checker, skill frontmatter, or hand edits inside the block—docs catch up to skills already on disk.

^{Reviewed by Cursor Bugbot for commit 24add77. Bugbot is set up for automated code reviews on this repo. Configure here.}

[cursor]

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: serverGenReqId_544d4ea2-6a6b-47f1-8706-531b11de8a04)

[mergify]

Queued — the merge queue status continues in this comment ↓.

[EdbertChan]

@Mergifyio queue

[mergify]

Merge Queue Status

• ✅ Entered queue — 2026-09-12 01:17 UTC · Rule: admin-bypass · triggered by @EdbertChan with the @mergifyio queue command
• ✅ Checks passed · on draft merge queue: checking #458 on main (94593f3), stacked on #446 and #457 #461
• ✅ Merged — 2026-09-12 01:24 UTC · at 0abdc943cc25cf5654e6a62fff8a2a2fa9c4e9fa · squash

This pull request spent 7 minutes 3 seconds in the queue, including 5 minutes 51 seconds running CI.

Required conditions to merge

• check-success = lint
• check-success = test