[AksharP5]

An older recording's upload page could lose its Retry and Download controls when another recording started. It could also show the other recording's share link.

Ignore status updates that do not match the video ID in the page URL. The shared renderer covers broadcasts, storage updates and polling; matching-recording progress and completion continue normally. Intentional navigation by the service worker is unchanged.

Page for failed recording A	Before	After
Recording B starts or publishes storage updates	A's error and recovery controls are replaced	A's error, Retry and Download remain visible
B completes	A's page can show B's link and redirect	Update ignored
A uploads and completes	Shows A's progress and link	Same result

Three regressions fail on the baseline and pass with the fix; the matching-recording control passes in both. All 43 extension tests pass using the repository HTML and actual upload module with Chrome boundary fixtures. Explicit jsdom test dependencies reuse existing locked versions; no resolved package versions changed.

Package typecheck and all production builds pass. Independent GPT-6 Astra HIGH review passed all 43 tests plus seven additional identity/retry probes, reproduced baseline failures, and verified the frozen install. Tests do not mount a Chrome extension or perform live uploads. Reloading an old A page after global state has already moved to B does not restore historical progress; this patch prevents it from displaying B's state.

Closes #3498.

Confidence Score: 5/5

The PR appears safe to merge; no actionable issues were found.

Summary

The upload page now ignores status updates for other recordings.

• Each upload page shows updates only for its recording.

_{Reviews (2) · Last reviewed commit: "Merge branch 'main' into upload-page-ide..." · Reviewed by Greptile}

[vercel]

@AksharP5 is attempting to deploy a commit to the Cap Software Inc Team on Vercel.

A member of the Team first needs to authorize it.

[richiemcilroy]

hey @greptileai, please re-review the PR