GitHub Issue Execution Resume after compaction or tool-call ceiling When resuming an issue from preserved todos/context compaction, first rehydrate live GitHub issue + repo/artifact state before continuing. Treat restored todos as hints, not proof. If an expected plan/artifact path is missing, pivot to issue comments and repo search as source of truth. See . This is the canonical execution route for approved GitHub issue work. Use it only after planning is complete and the issue is approved. Route summary Canonical path: Issue - Plan - User approves - TDD implementation - adversarial review -…