Local runners keep one canonical execution record
Local runner leases now stay associated with one execution record, bounded evidence and attention writes recover from a durable outbox, and resolved human attention resumes the retained thread only after version checks.
Local runners now keep each issue turn associated with one canonical execution record. The execution tracks the lease, bounded progress, evidence, and any human-attention boundary without changing the existing notification or verified GitHub resume contracts.
Recovery keeps the same operation
Before a runner writes execution state, evidence, or attention, it records a bounded private operation in its local journal. After a restart, the runner reads the exact execution identity and replays the same idempotent request when the server has not already applied it. A changed state or ambiguous readback stays fenced for review.
Human attention resumes the retained thread
A retained local thread is eligible to resume only when its canonical attention item is resolved, the execution is waiting, and both stored versions match. The new claim carries the exact execution, source lease, attention item, host, and thread identities. An open, ambiguous, or mismatched item blocks intake and leaves the existing record for reconciliation.