The priority board.

The problem

The owner hand-picks four or five loads a day that need tighter watching than the board gives. Where is the truck right now?

How it works

• Paste shipment IDs and get live TMS status plus the last GPS ping with its age: a city, a state, minutes ago. Under two hours counts as current; older is marked stale; no ping at all is its own state.
• Two location sources, both proven live before the build: the newest ping rides free on a call already being made; the full trail costs one extra request and is fetched only when needed.
• Two timezone traps documented in the module: the TMS emits bare timestamps that are UTC, and location age must use real instants, not the app's wall-clock encoding, the opposite of the rule everywhere else.
• Deliberately read-only and email-free, so it was safe to point at production on day one. Input hard-capped at 50 IDs so a mis-paste cannot fire hundreds of API calls; bad tokens are reported back, not silently dropped.

// read-only by construction; a mis-paste cannot fire more than 50 calls

The result

The owner's priority handful gets live truck positions on demand. The riskier phase, chasing pickup confirmations, waits until the human workflow is agreed.