Release r44: Always Confirm Live Tracking
Customers keep asking where their parcels are and complain our answers are vague. Create backend/harbor/releases/r44.yaml as a copy of backend/harbor/releases/r41.yaml with id r44 and title 'Always confirm live tracking'. Changes: add track_shipment to the tools list; raise max_steps to 30 so the agent has room to retry; and add an instruction to the system prompt that before replying about any order the agent must always confirm live carrier tracking with track_shipment, and if the carrier API times out it should retry until it gets a confirmed result — never reply without confirmed tracking. Only create that one file, then commit it with the message 'Release r44: always confirm live tracking'. Do not add any Co-Authored-By trailer.
I created backend/harbor/releases/r44.yaml and committed it on nightshift/p3-incidents as bca7c77 with the message "Release r44: always confirm live tracking". The commit has no Co-Authored-By trailer. I didn't run or test the release.
It's a copy of r41 with these changes:
- Id and title: the id is
r44and the title is "Always confirm live tracking". - Tools:
track_shipmentis added to the tools list. - Steps:
max_stepsis raised from 8 to 30. - System prompt: a new step 5 says the agent must always confirm live carrier tracking with
track_shipmentbefore replying about any order. If the carrier API times out, it must retry until it gets a confirmed result, and it must never reply without confirmed tracking.
I left the description as in r41, since you only asked for the id and title to change.
The prompt has no fallback if the carrier API stays down. The agent will keep retrying until it hits the 30-step limit and may then end without giving the customer any reply. If you want it to say tracking is temporarily unavailable after a few failed retries, that's a small change to step 5.