zanmaicreate-expertlisted

# create-expert Add an expert so the roster stays consistent and the spec is not a generic stub. Two things have broken this before: a spec drafted from model knowledge that reads like every other AI agent, and a contract added to one list but not the others so the next setup crashes or the expert dispatches nowhere. This procedure closes both. This is the one way an expert is built, whether Stan adds it for the user or it ships with Zanmai. Same procedure, same shape, same budget. That shared discipline is what lets Zanmai grow itself without bloating: an expert added the disciplined way stays lean by construction. ## When to use - The user needs a capability no current expert covers, and Steve could name it in one sentence. - Not for a one-off task an existing expert can do. Not for renaming or removing an expert. ## The procedure ### 1. Name the need One sentence: what this expert does that no current expert does. Steve settles it with the user before dispatch. If the sentence cannot be finished, the role is not defined yet. ### 2. Research the role (before any drafting) Steve dispatches Reed for a role-research pass: how an excellent version of this role operates day to day, its core competencies, the anti-patterns a mediocre version falls into, the real deliverables, the boundaries it holds, and name candidates. This is the step that prevents a generic spec, a contract written from model knowledge alone mirrors every other AI agent. Stan drafts from this research,