Investigation: does the ai-config plugin already carry the hooks? (no) + headless support

[d-morrison]

A. The plugin ships zero working hooks — schema mismatch.
The ai-config plugin root is the repo root (marketplace.json -> source: "./"),
so Claude Code auto-detects hooks/hooks.json. But that file is in the bespoke
install-hooks.py schema, incompatible with the plugin-hooks schema:

• top-level hooks must be an OBJECT keyed by event ({"UserPromptSubmit":[{"hooks":[...]}]});
  ours is an ARRAY.
• entries must be {"type":"command","command":"..."}; ours are {"script","event","why"}.
• plugin commands use "${CLAUDE_PLUGIN_ROOT}"/...; install-hooks.py emits $HOME/.claude/....

Consequence: enabling the plugin loads none of the 11 hooks, and the malformed file at the
auto-detected location may register a plugin load error for marketplace consumers (unverified).

B. Headless yes, cloud/web unconfirmed.
Plugin hooks appear to run in -p headless mode (the Setup event fires there; only plugin
monitors are documented as interactive-only). Whether the web/cloud harness auto-enables
marketplace plugins and runs their hooks is not documented — needs a live test.

Bonus findings

1. This repo's own cloud sandbox loads ai-config via bootstrap symlinks + committed
   .claude/settings.json, NOT /plugin install (install-hooks.py reports registered=0,
   no ~/.claude/settings.json). So option 2 mainly helps other repos.
2. Stop-guard blast radius has a built-in answer: defaultEnabled: false in plugin.json
   (Claude Code >= 2.1.154) ships the hooks opt-in.

Net: option 2 is a real conversion, not a switch-flip — reformat hooks/hooks.json to the
native schema with ${CLAUDE_PLUGIN_ROOT}, and rewrite or retire install-hooks.py (the two
schemas can't share one filename; duplicating them breaks DRY). The why/_note metadata has
no home in the native schema.

---

Generated by Claude Code