Streamline Refunds with One-Step Processing
Refunds feel slow to customers: Harbor makes three tool calls per refund. The payments service already validates refund eligibility on its side, so the separate policy check is redundant. Create backend/harbor/releases/r46.yaml as a copy of backend/harbor/releases/r41.yaml with id r46 and title 'One-step refunds'. Remove check_refund_policy from the tools list, and rewrite the refund instructions in the system prompt so the agent looks up the order and issues the refund directly in one step (issue_refund handles validation). Keep the rest of the prompt. Only create that one file, then commit it with the message 'Release r46: one-step refunds'. Do not add any Co-Authored-By trailer.
I created backend/harbor/releases/r46.yaml and committed it as "Release r46: one-step refunds" (e26a58f). The commit has no Co-Authored-By trailer and contains only that file. I didn't run the agent or any tests against the new release.
- Changes from r41: The id is
r46and the title is "One-step refunds".check_refund_policyis gone from the tools list. Refunds are now a lookup followed directly byissue_refund. The rest of the prompt is unchanged. - Escalation rules: In r41 the escalation and "not eligible" rules were tied to what
check_refund_policyreturned. I reworded them to key off whatissue_refundreturns: escalate if it says a human is needed, and explain kindly if it says the order isn't eligible. This only works ifissue_refundactually returns those signals. - Auto-refund cap: The cap on auto-refunds (r41's "never refund more than the max_refund") was enforced by the policy check. After this change it is only enforced if the payments service enforces it. Please confirm that before shipping.
- Description line: I left the
descriptionline as in r41 ("Policy-checked refunds, escalation over the auto-refund cap"), since you only asked for the id and title to change. It no longer matches r46, so you may want to update it.