Teach the agent skill the registered-block authoring workflow

[noeltock]

Problem

The source generator remains deterministic, but the calling model must know how to interpret a design, produce the plan, show the preview, ask for confirmation, complete the write, and run proof. Without that workflow, agents will keep jumping straight to hand-authored plugin code or use the page-content converter for the wrong artifact. Closes #9.

Solution

The original must-fix blockers are resolved. End-to-end success coverage remains advisable.

⚠️ Verification files modified

• package.json

• Assumed in scope: package.json — the implementation requires this verification change despite the path not being named.

Testing & verification

• Local run — npm run typecheck → pass.
• Local run — npm run test → pass.
• Local run — npm run build → pass.

QA evidence

QA: blocked — app never became ready
Evidence on factory host: /Users/birdnest/factory/worktrees/block-runner/qa-20260903055401-41077

Risk / rollout

Small, targeted change — see the diff for the affected paths.

Advisory notes from review

• BR-004 · Regression coverage now exercises activation, preview, confirmation, destination, and plugin integration, but it does not build a real archive or complete a passing full proof run.

---

Built by 🪺 Rookery · flight #41 · 1h43m · 4 passes · gpt-5.6-terra·xhigh