Epic: module authoring in separate repositories — last-mile delivery kit

[Max-Levitskiy]

Priority: P2 · Design: docs/superpowers/specs/2026-09-09-plugin-first-standards-engine-design.md

Modules are the opinionated tier and live outside this repo. Authoring one today means
reverse-engineering the engine (see docs/beads-module-handoff.md §2), committing every
iteration so git ls-remote can see it, and hand-writing checks in every consumer. This
epic gives module authors a scaffold, a test harness, and CI they can call from their
own repo — generic for any module, not only dev-standards.

Issues

• wvr module new scaffold, module authoring guide, and self-describing manifest #83 — wvr module new scaffold + module authoring guide + .wt/weaver/manifest.yaml
• wvr module test: before/after fixture harness for external module repos + reusable CI workflow #84 — wvr module test: before/after fixture harness for external module repos + reusable CI workflow

First consumer (tracked in Web-tree/webtree-dev-standards-k8s)

• Web-tree/webtree-dev-standards-k8s#82 — rule catalog and decisions for the dev-standards module
• Web-tree/webtree-dev-standards-k8s#83 — weaver-module/ v0 built only from plugin types
• Web-tree/webtree-dev-standards-k8s#84 — self-dogfood: weaver.yaml + CI gate in the standards repo

Done when

A new module repo (or subdirectory) scaffolded with wvr module new has a passing
wvr module test in its own CI, and a consumer adopts it with wvr module add.