GitHub Actions (scheduler)

Role in Ship: the scheduler — deterministic clock, retries, concurrency, and workflow_dispatch for humans when the board is messy.

• Cron — one serious job per slot where possible; separate SDLC cadence from self-heal / diagnostics so failures are interpretable.
• Secrets & variables — GitHub holds credentials; mirror only what agents need into approved runtime envs (never paste keys into prompts).
• Artifacts — logs and reports from each run are part of the evidence trail alongside tracker comments and PRs.

• Workflows call small Node entrypoints (pick, launch, verify) that stay boring and testable; heavy reasoning stays in prompts executed by the agent runtime.
• Keep idempotent picks: the same slot should not fight itself (concurrency groups, single-flight labels).

• Tools — capability map — why scheduler is one of five capabilities.
• Delivery, quality & release — release policy vs schedule.
• Examples → ElMundi — sample workflow filenames and minutes (reference only).