forge-alignlisted

# forge-align Fix the classic vibe-coding failure: five CRUD features, five dialects. Detection is delegated; judgment and the fix pipeline live here. The prevention side (specs that point at exemplars) lives in `forge-spec`/`forge-build`; this skill is the detection-and-repair side. ## Argument Text after the command scopes the check (e.g. `/forge-align the CRUD features` or `/forge-align src/features`). No argument → whole-codebase family discovery. ## Steps ### 1. Detect (delegated) Spawn the `forge-aligner` agent (sonnet-pinned, read-only) with the scope. It discovers feature families, compares siblings against the registered pattern (or the dominant member), and returns divergences by severity plus proposed patterns.md entries. Its reading stays out of this session. ### 2. Judge with the user Present the drift report. For each family, decide together: which pattern is canonical (the aligner's recommendation is a default, not a verdict — the user may prefer the minority version), which divergences are worth fixing, and which are accepted as-is (record a one-line lesson for accepted ones so they stop being flagged). ### 3. Register the patterns Write the approved entries into `context/patterns.md` (create from `${CLAUDE_PLUGIN_ROOT}/skills/forge-init/templates/context/patterns.md` if absent): pattern name, exemplar path, must-match bullets. Keep it within ~2 KB — pointers, not essays. This is the prevention half: from now on `forge-architect` writes specs that re