Fill gaps from assistant conversations: estimated events and invalidation

[mintlify]

Summary

Resolves two recurring points of confusion surfaced by assistant conversations: an apparent contradiction about estimated events between raw_events and transport_events, and undocumented behavior where container milestone fields revert to null.

Changes

• raw_events reference: replaced the misleading "includes estimated future events: Yes/No" table row and added an "Estimated events" section explaining that raw_events flags estimates via attributes.estimated on any event type, while transport_events has only three normalized estimated.* event types (verified against the OpenAPI spec).
• transport_events reference: listed the three estimated event types and noted feeder, rail, and transshipment events exist only as actual milestones.
• Webhook event catalog: added a note that the estimated events listed are exhaustive, with a pointer to raw_events for other estimated milestones.
• Webhook payloads: documented that milestone fields such as pod_full_out_at can revert to null when the source transport event is invalidated, and how to investigate via the DataSync transport_events invalidation columns.

Context

Three assistant threads in the past week flagged the estimated-events contradiction; another asked why pod_full_out_at reverted to null with no docs explaining invalidation.

---

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

[mintlify]

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

Project	Status	Preview	Updated (UTC)
terminal49	🟢 Ready	View Preview	Aug 31, 2026, 4:11 PM

[greptile-apps]

PR author is in the excluded authors list.

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
api	Building	Preview	Aug 31, 2026 4:10pm