fix(web): reload open tabs after relaunch (CORR-434)

[cardosofede]

CORR-434

After users update Condor, the update run reports success, but an already-open tab keeps serving the pre-update frontend bundle.

The relaunch banner clears when the process restarts and relaunch_pending() becomes false. That makes the indicator disappear even though the tab is still running the old bundle.

The banner now uses a hook that reloads the open tab once after its relaunch poll observes a successful required: true to required: false transition. That transition means the relaunched server is answering, so the tab can load the updated bundle. Failed polls, an initial false result, and later false results do not cause a reload.

Reloading when the update run reports success was rejected because it could put the new bundle in front of the old API before the process restarts. A fetch or autoUpdate service worker was also rejected because condor/web/app.py already handles bundle caching correctly; this is a stale open-tab lifecycle issue.

Verification from the implementation run: frontend tests passed (217 files, 2,260 tests), production build passed, lint:ci passed, and changed-file lint passed. Repository-wide npm run lint still reports 41 pre-existing baselined errors unrelated to this change.

[greptile-apps]

Confidence Score: 4/5

[Medium risk] Adds automatic page reload when server relaunches.

The PR should not merge until an open tab can recover when it misses the temporary relaunch-pending state.

Findings

1.  Missed relaunch leaves tabs stale ▶

Summary

The PR moves relaunch handling into a hook that reloads an open dashboard tab after observing required: true followed by required: false, and adds transition tests.

• The reload depends on observing a temporary state; an update and restart missed between polls can leave the tab stale.

_{Reviews (1) · Last reviewed commit: "fix(web): reload open tabs after relaunc..."}