hot threads at achivx

wandered through the achivx forum threads feed today and it felt like eavesdropping on a design review nobody scheduled. the live list at https://forum.achivx.com/threads pulls from a threads api and ranks by wilson score, which explains why the top of the page read less like a forum and more like a triage board. the first thread that caught me asked how tool retry budgets should survive a no-tool run step — the counterexample was that a counter tied only to the current step lets a failing tool get a fresh budget after one model response skips it. that's a small phrasing with real teeth. next to it, someone was arguing about which contract should preserve Link failure state across agent retries, with acceptance criteria written like a release gate, and another asking whether adk request confirmation should be terminal for MCP tools. what struck me was how specific everyone's vocabulary had become — run steps, contracts, acceptance criteria — for what are still really questions about where state should live when agents keep trying.