docs(webhooks): drop poll and avatar content arms — not officially supported

[Yan Xue (yanxue06)]

What

Removes the poll / poll_option and avatar content arms from the public webhook wire-spec documentation.

Why

Product decision: neither polling nor avatars are officially supported yet, so the public docs shouldn't list them as first-class content types. The runtime serializer in spectrum-webhook continues to handle both arms — only the customer-facing docs change. A poll- or avatar-shaped payload that does reach a customer endpoint falls through the documented SerializedUnknownContent tail, which matches the "not yet supported" framing.

What changed

• Dropped the poll and poll_option accordion blocks from the per-arm wire reference in docs-src/webhooks/events.mdx.vel
• Dropped the avatar accordion block from the same per-arm wire reference
• Removed avatar from the byte-bearing-arms warning callout (now attachment / voice / contact.photo only)
• Prose updates: arm count + forward-compat enumeration

Out of scope

Several SDK pages (spectrum-ts/content.mdx, spectrum-ts/providers/imessage.mdx, advanced-kits/imessage/polls.mdx, etc.) still publicly document the poll(...) and avatar(...) content builders. That's a separate follow-up if the "not officially supported" framing should extend to SDK how-to pages.

Test plan

• pnpm docs:generate — clean
• pnpm typecheck:docs — clean
• pnpm lint — clean
• rg -i 'poll|avatar' docs-src/webhooks/ webhooks/ — only verb-sense matches remain (you poll, you wait in overview)

Split out of #60 — that PR stays focused on the per-arm wire-spec sync.

Made with Cursor

---

^{Need help on this PR? Tag @codesmith with what you need. Autofix is disabled.}

[coderabbitai]

Warning

Review limit reached

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

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

Your organization has run out of usage credits. Purchase more 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: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 3b9d47a1-9d10-4049-a00f-04d7c10db442

📥 Commits

Reviewing files that changed from the base of the PR and between fde8af9 and 02d46ee.

📒 Files selected for processing (1)

• docs-src/webhooks/events.mdx.vel

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch docs/drop-unsupported-content-arms

---

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

[Copilot]

Copilot encountered an error and was unable to review this pull request. You can try again by re-requesting a review.