night-shiftlisted

# night-shift Run the computer while the human sleeps, but keep the loop bounded, auditable, and reversible. `night-shift` is an unattended analysis skill. It fans out read-only workers across recently active repositories, captures findings, synthesizes architectural leverage, and produces a morning HTML report. It is not a license to edit production code or burn unlimited model quota. ## Core Contract Every run must have: - a time box; - a worker cap; - a repo cap; - a provider fallback policy; - a failure ledger; - a self-contained HTML report; - no writes to production code unless the user explicitly starts a follow-up AOSwarm execution phase. ## AOSwarm SDLC Use AOSwarm as the SDLC shape: 1. Scout swarm: read-only workers inspect independent repos or domains. 2. Synthesis lead: one agent clusters findings, identifies themes, and writes the morning report. 3. Human gate: the user reviews the report and chooses follow-up work. 4. Execution swarm: approved code-changing work is dispatched through `ao spawn` or `ao batch-spawn`, one PR/MR per task. 5. Verification: merged only after normal repo verification and review gates. The nightly phase is phases 1 and 2 only. Phases 3 to 5 require explicit human approval. The bundled nightly runner uses direct read-only CLI scouts (`claude`, `codex`, `gemini`) for phases 1 and 2 so it can collect local Markdown artifacts deterministically. Use `ao spawn` / `ao batch-spawn` for phase 4 code-changing execution after the human g