feat: add transparent sequential Beeper messaging export

[0thernet]

Summary

• add a pinned, read-only Beeper Desktop provider for contacts, bounded messaging reads, and local Message Like Me export
• enumerate connected accounts and run the official Beeper CLI export sequentially, with visible redacted progress and cumulative counts
• validate and retain each private raw shard until a complete seven-file bundle is atomically published, with durable recovery and global admission
• preserve the current Bluesky, Threads, Reddit, profile-read, video, package, skill, and provider-attestation behavior from latest main

Safety boundary

• accepts only the pinned official Beeper CLI 0.6.2 executable and fixed read-only JSON/export commands
• exposes no send, raw request, browser, media download, pairing, presence, or background-sync surface
• bounds records, serialized bytes, participant occurrences, per-chat input, raw working data, connected accounts, and progress output
• keeps provider coordinates and message content out of logs, Git fixtures, and diagnostics

Verification

• clean transplant based on current main commit d54cf1f; no current provider files or behavior reverted
• focused Beeper, provider-registry, and recovery suite: 140 tests, 9,970 assertions, zero failures
• exact full release gate: 2,751 primary tests passed with one intentional skip; 18 serialized Omni tests passed
• typecheck, website tests/build, package install smoke, standalone smoke, generated catalog parity, and durable contract inventory passed

Supersedes #27, whose stale branch conflicts with current main and contains historical merge-tree regressions.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
wrench	Ready	Preview	Aug 22, 2026 11:04pm