You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Include interrupted stop reason on in-flight wait results
interrupt_agent flipped wait to interrupted while the run was still in flight, so wait JSON omitted stop_reason. Skywalker classifies interrupted-incomplete only on that field.
`clamped to a ${MAX_WAIT_TIMEOUT_MS}ms max. A timeout or parent-turn abort is NOT an error and never touches `+
467
471
`the workers — they keep running and remain waitable. Live wait status includes "queued" (waiting for a burst `+
468
472
`slot), "running", and "awaiting_director". interrupt_agent and close_agent unblock this wait immediately with `+
469
-
`status "interrupted". awaiting_director is not terminal: re-wait while still pending re-delivers the same question. `+
473
+
`status "interrupted". Terminal JSON includes stop_reason when the session recorded one `+
474
+
`(interrupted, cancelled, incomplete-report, and similar). awaiting_director is not terminal: re-wait while still pending re-delivers the same question. `+
470
475
`Answer with send_input (soft). Do not call this in a tight zero-progress loop: a timeout means the targets are still `+
471
476
`queued, running, or awaiting a director answer, not "try again right away" — do other work, reply to the operator, or change the brief. Calling again with the `+
472
477
`same targets is a real timed wait, not a spin, but wastes turns if nothing has changed.`,
0 commit comments