Overnight Planning No-Op Run Salvage When to use Use this when an unattended overnight planning or review wave appears to have run successfully but did not actually produce the expected artifacts. Typical signals: - Codex background process exits with code 0 - stdout/stderr logs are empty or missing - expected or files do not exist - no plan files or issue comments were materially updated This showed up in the 2026-04-22 workspace-hub tier-1 knowledge beef-up wave across 6 separate unattended Codex launches. Core lesson is not sufficient proof that unattended Codex accomplished the task. For…