chore(docs): Update alert JSON structure

[leggetter]

No description provided.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
outpost-docs	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jun 4, 2025 0:24am
outpost-website	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jun 4, 2025 0:24am

[Copilot]

Pull Request Overview

This PR updates the example JSON schema in the alerts documentation to reflect the new alert payload structure.

• Renamed the topic field and updated the example timestamp precision
• Introduced an event object and replaced response with delivery_response
• Adjusted failure metrics, the will_disable flag, and placeholder sections for destination

Comments suppressed due to low confidence (3)

docs/pages/features/alerts.mdx:34

• The status field is now an integer (400) whereas the previous example used a string ("500"). Consider standardizing the type or calling out this change in the docs to avoid confusion.

"status": 400

docs/pages/features/alerts.mdx:33

• [nitpick] Showing the response body as a raw JSON string can be hard to read. Consider presenting it as an inline object or noting explicitly that this is a stringified payload.

"body": "{\"success\":false,...}"

docs/pages/features/alerts.mdx:31

• [nitpick] Using an empty object for destination doesn't illustrate its expected shape. It may help to provide a realistic example or reference the DestinationObject schema.

"destination": {}