[1.1.1] — 2026-04-30 — Manifest Schema Fix
Patch release. Fixes plugin manifest validation failure that prevented installation
under recent Claude Code releases. No skill or audit-pipeline behavior changes.
Fixed
.claude-plugin/plugin.json— removed string-typed asset fields (skills,
commands,hooks,agents) that triggeredagents: Invalid inputvalidator
errors. Components are now auto-discovered from their standard directories
(skills/,commands/,hooks/,agents/), matching the official greeter and
full-featured plugin examples and aligning withvalidationforge/
superpowers-developing-for-claude-codepatterns. Addshomepage,repository,
andauthor.urlfor marketplace metadata completeness.hooks/hooks.json— converted from a flat{name,event,matcher,command}
array (which Claude Code's hooks loader rejects) to the canonical event-keyed
schema documented at
references/plugin-structure.md:218-249:
{"hooks": {"<EventName>": [{"matcher": "<re>", "hooks": [{"type": "command", "command": "..."}]}]}}. All five hook commands now use${CLAUDE_PLUGIN_ROOT}
so they resolve from the plugin install dir instead of the user's CWD..claude-plugin/marketplace.json— version bumped to 1.1.1.
Why this happened
The 1.1.0 manifest was carried over from an older internal plugin draft that
predated the current plugin.json schema. The old form embedded asset directory
paths as strings; the current schema only accepts arrays of file paths (per
episodic-memory@1.0.15) or relies on auto-discovery (per the official greeter).
Strict validation in newer Claude Code releases surfaces the mismatch as
agents: Invalid input. The fix is purely structural — the underlying hooks,
commands, agents, and skills are unchanged.
Frozen invariants (unchanged from 1.1.0)
full-ui-experience-auditandui-experience-auditskills remain at 14/14
detection across WAM 9/9 + synth-2 5/5. No skill content was modified.- Cycle cap = 2. WAM-class needs cycle-2 reach; synth-2-class needs cycle-1.
- Iron Rule (RL-1): no mocks, no fixtures, no test files in audits.
- RL-2: every PASS verdict must cite a specific evidence file path.