Keep going

Purpose

After an interruption — a rate limit, a crash, a disconnect, or just a long gap — work started off the main thread may be paused, dead, or silently finished, and the main task's position is easy to misremember. The same recovery also applies live, mid-session, when off-thread work looks stalled and someone asks you to check on it. This skill recovers or verifies the off-thread work from its real state, reconciles the main thread, and continues. Scope is general: the recovery is the same whatever caused the interruption, so the cause is not diagnosed here.

Two failure modes this skill exists to prevent: summarizing and stalling once a usage limit has lifted instead of continuing, and killing live-but-slow work on a hunch instead of on evidence.