Implement Exodus dashboard against evidence-fabric contract bootstrap

[mdheller]

Summary

Implement the first working Exodus Dashboard surfaces against the validated evidence-fabric contracts staged in exodus#5.

Core contract families to consume

• EvidenceDashboardState
• MigrationWavePlan
• ProofPackSummary
• NotesSourceProfile
• OwnedMediaSourceProfile
• OwnedMediaAttestationRecord
• OwnedMediaConversionProfile
• PlaylistMigrationRecord
• AIChatSourceProfile
• AIChatConversationDocument
• ConversationReusePolicy
• ProviderTopologySnapshot
• SourceAliasReport
• BlockedObjectReport
• ConversionReceipt
• RedactionReviewRecord
• DeletionEligibilityRecord
• ProviderDowngradePlan

First dashboard panels

1. Provider control overview
2. Migration wave planner
3. Evidence landing monitor
4. Notes migration panel
5. Owned media and playlist panel
6. AI chat export / reuse panel
7. Proof-pack center
8. Blockers and next actions

Acceptance criteria

• Render all core panels from fixture-backed contract data.
• Show provider topology, alias preservation, blocked objects, proof-pack state, and downgrade eligibility.
• Treat imported AI chat outputs as historical records, not verified facts.
• Treat owned-media private migration separately from public distribution.
• Preserve a clear boundary between dashboard UX and raw custody/evidence-broker responsibilities.

Notes

Start with static fixture-driven panel rendering before live broker integration. Live broker wiring can follow once evidence-broker and evidence-storage-infra exist.