feat(admin): recognition — awards, mentorship, contributions

Summary

Recognition workflows: award nomination → review → approval, mentorship pair management, community contribution logging. Schema landed in Phase 3 (daa677b).

Requirements

• Brainstorming → spec under docs/superpowers/specs/.
• /admin/awards — manage the awards vocabulary (tier, accent, description) — staff+.
• /admin/awards/:slug/nominations — nomination intake + review workflow — super_admin (lifetime tier) or staff (other tiers).
• User awards CRUD: add / revoke entries on user_awards with citation text.
• /admin/mentorship — match mentor / mentee pairs, manage active pairings, capture privacy preferences (partner names visible only when partnerIsPublic).
• /admin/contributions — log community contributions (newsletters, tutorials, guides, etc.) for badge calculation.
• All recognition writes flow through audit middleware so the trail of "who awarded what to whom" is complete.

Context

Foundation must ship first (#1956). Schema: awards, user_awards, mentorship_pairings, community_contributions, plus the award_tier, award_accent, contribution_kind enums.

Implementation Notes

• Policy: canManageRecognition is staff+. Lifetime-tier awards may need an additional gate or a board-quorum-style approval (defer the decision to brainstorm).
• Existing badge engine (packages/api/src/lib/badges.ts) is computed-on-read, so recognition data flows automatically into dossiers once admin writes land.

Start by confirming foundation issue #1956 and reviewing the Phase 3 recognition schema plus packages/api/src/lib/badges.ts. Draft the required spec under docs/superpowers/specs/, resolve the lifetime-tier approval decision, then define the awards, nominations, mentorship, and contributions workflows with audit coverage; done means the listed admin flows and recognition writes are complete.