The Tab That Has Been Open Since Tuesday
Decide what you would build from the brief alone. Everything below it is available, but the exercise stops working if you open it first.
After each deploy, a trickle of errors arrives from clients calling removed endpoints and requesting chunk filenames that no longer exist. Design the deployment and client behaviour so this stops.
Adding a version check that reloads the page as soon as it detects a new build, which eliminates the entire class of error in one small change and is easy to justify. It also reloads a tab in the middle of a half-completed form, discards an in-progress upload, and — because deploys often come in bursts — can reload the same user repeatedly within an hour. Worse, if the check runs on an interval and the deploy is gradual behind a load balancer, clients can flap between versions and reload in a loop. The staleness detection is right; making the remedy automatic and unconditional turns a rare error into a frequent interruption.