0a89d657f0
Two symptoms reported after a successful resume: 1. Banner stays visible even though the report finished — because the historical 'error' log entry still lives in agent_log.jsonl, and every fetch from line 0 re-flipped reportStatus to 'failed'. 2. Polling dies mid-resume — stopPolling() was called when the error entry was re-read, killing the timers before the resume_start / report_complete entries landed. Fixes: - On 'resume_start': reset reportStatus back to 'generating' so the banner clears as soon as the resume kicks in. - On 'report_complete': force reportStatus='completed', clear reportError. Belt-and-suspenders even if an older error entry is re-read later. - Remove stopPolling() from the error handlers (both agent-log and progress-poll). The polling naturally stops on report_complete; if a real terminal failure never resumes, the component unmounts when the user navigates away. Better to waste a few extra polls than to soft-lock the UI during a legitimate resume. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| public | ||
| src | ||
| .gitignore | ||
| index.html | ||
| package-lock.json | ||
| package.json | ||
| vite.config.js | ||