schedule-agent-worklisted

# Schedule Agent Work Choose scheduling only after the work has a bounded input, write scope, validation, escalation boundary, and result-delivery route. ## Choose The Smallest Durable Shape - Use an in-run worker for a short dependency-free result the coordinator needs before continuing. - Use a native scheduled task for periodic or trigger-based work where the host can show status and deliver a result to Gale. - Use CI or `codex exec` for deterministic repository jobs with structured output and explicit sandboxing. - Use a queue or board for retries, dependencies, multiple roles, durable comments, artifacts, or human decisions. - Use an application service only when application code must own state, tools, approvals, tracing, and deployment. ## Required Schedule Contract Define the trigger/cadence, owner, input snapshot, write authority, idempotency or duplicate policy, timeout/retry limit, no-op/rollback behavior, escalation trigger, status surface, artifact retention, and route that delivers the final report to Gale and the coordinator. ## Deferred Remote Work When an agent reaches an external CI, review, release, deployment, or provider gate, use a host-native future wakeup rather than leaving a terminal, watcher, or polling loop alive. Schedule every agent-created recheck at least five minutes after the observation that caused it. A shorter operation is allowed only for one bounded, command-local re-read; it must not become a repeated polling loop. For