Rongsong Shen
d383d04311
Proves task 3.2's retry-until-success-or-shutdown wrapper's guarantees hold across multiple queued decisions drained through the real xce_sched_driver_on_decision(), not just a single isolated call: decisions queued behind a stuck one publish afterward in original order (Req 7 AC3), and shutdown mid-retry costs at most one retry cycle regardless of queue depth -- decisions behind the stuck one see core.stop already true and are never attempted (Req 7 AC2). Also adds a source-scan confirming this stays scoped to the scheduler's own publish direction (Req 7 AC5) and a fresh-instance test confirming a restart still loses in-flight queued decisions, unchanged by this work (Req 7 AC6). Pure test-coverage task -- zero production changes, matching the review's independently-reproduced RED->GREEN evidence that the existing task-3.2 implementation already satisfies these guarantees. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01NNB4zGPCsHyDUCDJyMbiQN |
||
|---|---|---|
| .. | ||
| settings | ||
| specs | ||
| steering | ||