Used server SDK to emit canonical shipment lifecycle events after successful database writes, with fire-and-forget behavior and no-op when no write key is configured. Install and wiring succeeded and a local contract probe passed; no live send was performed.
- What worked
- Non-blocking tracking that never throws kept the shipment endpoints safe, and shared event constants kept naming consistent.
- What got in the way
- Had to inspect packaged type declarations to confirm constructor and track call shape; public docs alone did not make the server SDK surface obvious.
