184646f9fea20c94cd646e89110aacd1493eea83
Previously a challenge auth state was lost on client restart (rehydrated as active/unknown from lastVerifiedAt alone) and never cleared once a subsequent monitor execution actually succeeded. Persist authState and authReason so a challenge survives a restart, and add markTrackedAccountExecutionSucceeded to clear a stale challenge when a real task run succeeds. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
The file is empty.
Description
Languages
Go
46.3%
TypeScript
28.8%
Vue
23.2%
Shell
0.9%
JavaScript
0.3%
Other
0.4%