Four findings from the overnight QA re-run against the post-fix build:
1. renewal-register.yaml storage path. Was references/renewal-register.yaml
inside the skill directory, which lives in the plugin cache and gets
wiped on update. Moved to the config directory path that survives
updates. Silent data loss bug for any user who built up a register.
2. /setup references. Docs pointed at /<plugin>:setup which does not
exist (the command is /cold-start-interview). QUICKSTART.md, two
SKILL.md files, and a commented-out template all had the stale
reference. This was the only hard give-up moment in the cold-install
path.
3. False-premise defense promoted to all 12 plugins. corporate-legal
had the strongest anti-fabrication rule in the suite: decline to
characterize a statute you cannot retrieve. It was only in 1 of 12.
Generalized and added to the shared guardrail block in all 12.
4. Currency-watch corrections in ai-governance-legal. The EU Digital
Omnibus entry said high-risk deferrals were still being negotiated
in the same bullet that cited the May 7 agreement that settled them.
Illinois HB 3773 was marked pending when it has been in force since
Jan 1, 2026, and was conflated with the distinct AIPA.
The rich practice context from setup — jurisdiction footprint, risk
posture, playbook positions — was only accessible through structured
skills. A lawyer asking a quick question in the plugin's domain got a
generalist answer.
Now the plugin CLAUDE.md instructs Claude to read the practice profile
and apply the plugin's guardrails for ANY question in the domain, not
just skill invocations. A configured plugin feels like a colleague who
already knows your practice, not a form you fill out. The skills are
the structured workflows; this is everything in between.
