0.13.3: Clearer error when a paused job is lost to a restart
If you restart Claude Desktop between pausing a job and continuing it, Orbit now tells you so — plainly. Previously both "an hour passed" and "you restarted" surfaced as the same generic "expired" error.
What shipped
•When orbit_continue_job can't find a token, it now distinguishes two cases: (a) the paused work was cleared by an Orbit restart (quitting Claude Desktop, reloading the extension, or a sleep/wake cycle), or (b) it genuinely aged out after an hour. The error message and Claude's follow-up offer now say which one happened.
•Technical: continuations are held in memory inside the local Orbit process and don't survive a restart. That's by design — the TTL is 1h and the state would be evicted anyway — but users shouldn't see "expired" when they only paused 5 minutes ago. The new classifier compares process uptime against the TTL to pick the accurate message.
•Added three unit tests covering both branches (fresh process, long-running process, exact-boundary case) so this stays correct.