Fix legacy WhatsApp interaction projection

[0thernet]

Problem

Supported legacy wacli migrations can store short system JIDs and participant fields that contradict the recorded message direction. The body-free WhatsApp interaction projection previously rejected the complete page, blocking the admitted PeopleBlade refresh.

Change

• Map bounded one-digit legacy system JIDs to GhostGet's existing unsupported sentinel.
• Normalize only exact outgoing DM/group chat IDs and exact session-proved incoming owner aliases.
• Keep unrelated participants and contradictory group senders fail-closed.
• Release GhostGet as 0.18.66 and refresh its package budget, install references, README, docs, website build data, and launch kit.

Validation

• Focused WhatsApp helper and protocol suite: 58 passed, 0 failed, 333 assertions.
• bun run check:static: 168 passed, 0 failed, 57,999 assertions.
• bun run typecheck.
• bun run check:cost-surfaces.
• Two npm pack --ignore-scripts runs were byte-identical: 625 files, 12,143,979 packed bytes, 24,057,665 unpacked bytes, SHA-256 935cb39bc9c6514a0a629d07d81348656ea1c15e981c4e95d97763c9fb140bc8.
• The full local aggregate reached the clean-consumer package smoke, but that sandbox cannot resolve the pinned external dependencies; Required CI will run the networked package-install path.

[vercel]

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

Project	Deployment	Actions	Updated
ghostget	Ready	Preview	Oct 1, 2026 7:03am UTC