- runbook: how executor binaries are resolved (bins or PATH) and what that
assumes on oregon (no codex installed) and win10; cancellation and
max_progress_rounds in the item lifecycle; secrets scrubbed from children.
- design: blocked-by ordering is a TODO (not read by the scheduler); failure
classification, success-when-tagged, one-time immediate rebuild, retries
outside the thread-round budget, ID-based new-comment filter.
- executor contract: how core reads ExecResult, kill used for cancel, Windows
quoting assumptions, codex exec resume without -C/-s.
jj.wang