Log a finished swim before the mandatory update

[SamiPr0]

Problem

The mandatory update screen replaced the whole app and came before everything else. Someone who finished a swim, and opened PoolTrack for the first time after a new release was published, saw "Update required" instead of the screen to log how far they swam, and could not log it until the update was downloaded and installed (slow on a pool's weak signal).

Fix

A swim waiting for its distance (the cancel window or the log screen) now comes before the update. The distance is stored with the entry, so the update is offered as soon as it is logged. Only a signed-in account has swims, so signed-out users still get the update first. While it is not yet known whether a swim is waiting, nothing is shown, so the update never flashes up for a moment first.

The order is decided by a small pure function, appGate in AppGate.kt, with a test for every combination; PoolTrackApp just follows it.

Notes

• The update check still only runs at startup, so nothing changes about when an update is found.
• Checked on an emulator that the app still starts normally. The swim-then-update path itself is covered by the unit tests, not exercised end to end.
• This only takes effect for users who have installed a build containing it, so it ships with the next release (it would need a version bump).

🤖 Generated with Claude Code