ecosystem: pattern marketplace — patina-community-packs repo + `patina pattern install <pack>`

[devswha]

Why it matters

custom/patterns/ exists but is gitignored — no community visibility into what people build. A curated community-packs repo surfaces contributions and grows the catalog without bottlenecking on the maintainer.

Acceptance criteria

• New repo devswha/patina-community-packs with one starter pack (e.g. en-corporate-bizspeak)
• Pack metadata pack.yaml: name, version, language, patterns, compatibility, author, license
• CLI commands: patina pattern install <name>, patina pattern list, patina pattern remove <name>
• Documented in docs/PATTERNS.md § Community Packs
• v1 trust model: GitHub-URL curl, no central registry / no signing (parity with install.sh)

[devswha]

Wave 4 triage: this stays open.

Concrete blocker: a pattern marketplace needs ecosystem governance before code: a community-pack repository, trust/signing or review policy, pack metadata rules, and CLI install/update semantics. This should not be squeezed into the current core-repo docs wave.