Fix spec: FAIL does not trigger retries, only RETRY does

The test criteria incorrectly said FAIL outcomes should be retried.
The pseudocode (Section 3.5) and the C reference implementation both
return immediately on FAIL. Only RETRY status triggers the retry loop.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This commit is contained in:
Bryan Helmkamp 2026-02-23 16:19:10 -05:00
parent 9f9b461971
commit 74a6b219cc

View file

@ -1861,7 +1861,7 @@ This section defines how to validate that an implementation of this spec is comp
### 11.5 Retry Logic
- [ ] Nodes with `max_retries > 0` are retried on RETRY or FAIL outcomes
- [ ] Nodes with `max_retries > 0` are retried on RETRY outcomes (FAIL returns immediately)
- [ ] Retry count is tracked per-node and respects the configured limit
- [ ] Backoff between retries works (constant, linear, or exponential as configured)
- [ ] Jitter is applied to backoff delays when configured