hookify: example rule files lack the hookify. filename prefix, so copied examples silently never load

plugins/hookify/core/config_loader.py discovers rules with the glob .claude/hookify.*.local.md (line 210), and the writing-rules skill documents the hookify. prefix as mandatory, listing danger.local.md (missing hookify prefix) under bad names (SKILL.md lines 286-298).

The plugin's own examples ship without the prefix:

plugins/hookify/examples/console-log-warning.local.md
plugins/hookify/examples/dangerous-rm.local.md
plugins/hookify/examples/require-tests-stop.local.md
plugins/hookify/examples/sensitive-files-warning.local.md

The docs (help.md, list.md, SKILL.md lines 324-327) point users at examples/ with no rename instruction. A file copied verbatim into .claude/ is silently dead: the glob never matches it, no error is shown, and the rule never fires. This matches hookify's known silent-failure pattern.

Verified by copying each example into a scratch project's .claude/ and running the real load_rules(): all four are invisible to the loader; after renaming with the prefix, all four are discovered (three active, require-tests-stop correctly parsed but inactive since it ships enabled: false). Happy to open a PR renaming the examples and updating the filename references.