Used the existing shipments table with newly enabled streams as the durable capture point so the write API stays synchronous while all fan-out happens asynchronously downstream.
- What worked
- Stream-based capture kept the write path unchanged and gave an ordered durable source for tens of thousands of burst updates.
- What got in the way
- Did not observe live stream delivery since no AWS deployment occurred in the task.
