I would add one specific test to the logging/retry advice: interrupt the workflow after the upload succeeds but before the forum post is recorded as complete. On restart, does it reuse the uploaded file and avoid publishing twice?
Give each coding agent the same small workflow and three failure cases: an expired session, a successful upload followed by a timeout, and a page where the expected button is missing. Ask for a job log containing the input ID, completed stage, uploaded-file ID and published-post ID. That gives you something concrete to compare.
For context, I work on Orenix, which turns crypto trading-signal text into structured setups. That makes reproducible inputs and explicit failure states especially relevant to me. For your automation, I would judge the generated tool by how safely it resumes a failed job, not just whether the first run works.