guildlisted

# Guild — Production-Readiness Panel (A smith submits the masterpiece to the guild; the masters judge the craft, the patrons judge whether it serves. Both must be satisfied.) Read `${CLAUDE_PLUGIN_ROOT}/references/creed.md`, `${CLAUDE_PLUGIN_ROOT}/references/dispatch.md`, and `${CLAUDE_PLUGIN_ROOT}/references/envelope.md` first. Log: `bash ${CLAUDE_PLUGIN_ROOT}/scripts/ledger.sh append guild <slug> panel STARTED -` This is smithy's most expensive operation (parallel opus reviewers). It runs ONCE per job (end of FORGE, before TEMPER) or on explicit request — never per task; per-task review stays with the solo `/smithy:inspect`. ## Checklist (create a todo per item) 1. Build the whole-job review package 2. Select personas by diff content; show the roster + cost note 3. Live target for UI-facing personas (run app, evidence dir) 4. Dispatch all selected personas IN PARALLEL (one message) 5. Synthesize: dedupe, verify evidence, tag craft/experience 6. Verdict written (md + json), ledger logged, findings routed ## 1. Build the packages — scoped per persona family Whole job, not one task: base = the job's base sha recorded at blueprint (STATE.md). Standalone: ask the user for the base ref. Build the FULL package plus SCOPED slices (a persona pays only for the diff it judges — every slice keeps the plan and the complete changed-file list, so cross-cutting context survives): ``` P=$SMITHY_MEM/jobs/<slug>; R=$P/reports review-package.sh build $P/plan.md $R/guild-pkg.md