docs: PDO at-most-once placeholder-resend (whatsapp-rust#841)

[jlucaso1]

Summary

Documents the changes from oxidezap/whatsapp-rust#841 — the PDO placeholder-resend at-most-once fix.

• New changelog entry changelog/2026-06-11-pdo-once-per-message.mdx — explains the bug (PDO storm from cloned-Signal-state peer), the three fixes (memo cache, skip migration retry decrypt, log-level adjustments), and the breaking-change migration steps for CacheConfig / MemoryDiagnostics.
• api/bot.mdx — adds pdo_requested row (24h TTL, 512 entries) to the Available Caches timed-caches table.
• api/client.mdx — adds pdo_requested: u64 row to the MemoryDiagnostics fields table.
• docs.json — registers the new changelog page at the top of the changelog navigation.

Test plan

• Verify the new changelog page renders correctly in Mintlify preview
• Confirm pdo_requested row appears in both the Bot cache table and the Client MemoryDiagnostics table
• Check all internal links are valid

https://claude.ai/code/session_01WKYLKo6cHgMPzFrFekXheR

---

Generated by Claude Code

---

Summary by cubic

Documents the at-most-once PDO placeholder-resend fix in whatsapp-rust (#841). Adds a changelog entry and updates caches/diagnostics docs to include the pdo_requested memo, plus navigation in docs.json.

• Migration
  • CacheConfig adds pdo_requested (24h TTL, 512). Update struct literals that don’t use ..Default::default().
  • MemoryDiagnostics adds pdo_requested: u64. Update exhaustive matches/constructors.

^{Written for commit 8d1212c. Summary will update on new commits.}

[mintlify]

Preview deployment for your docs. Learn more about Mintlify Previews.

Project	Status	Preview	Updated (UTC)
whatsapp-rust	🟢 Ready	View Preview	Jun 11, 2026, 5:48 AM

💡 Tip: Enable Workflows to automatically generate PRs for you.

[coderabbitai]

Warning

Review limit reached

@jlucaso1, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 38 minutes and 48 seconds. Learn how PR review limits work.

Your organization has reached its usage spending cap. Adjust your spending cap in the billing tab.

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 6fd173de-bb1c-4c38-8ef3-f754035fcdc0

📥 Commits

Reviewing files that changed from the base of the PR and between 64284d5 and 8d1212c.

📒 Files selected for processing (4)

• api/bot.mdx
• api/client.mdx
• changelog/2026-06-11-pdo-once-per-message.mdx
• docs.json

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch claude/eager-cerf-gywxy3

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[cubic-dev-ai]

No issues found across 4 files

_{Re-trigger cubic}