sw: v43 -> v44, so the deployed build actually reaches a browser

The last deploy shipped new engine code under an unchanged service-worker version. sw.js was byte-identical between the two deploys, so no browser ever saw a new worker, no install fired, APP_CACHE kept its name, and every returning client went on being served the previous app shell cache-first.

• The visible symptom was a wall of 404s for found/.mp3 — the pre-diet filenames, requested by the stale shell, against a server that now holds only found/.64.mp3.

• This is what the comment on VERSION has always said to do.

▶ Play it: Rail Replacement Rapture — a bed-heavy genre where the found-sound layer carries the room https://stellate.app/?genre=transitwave&seed=3163&path=749.12536,768.12569,730.12569&xdur=13.122

61a6994 https://github.com/aboard-io/stellate/commit/61a699435187be41feb2780fcf77f57d3a12c98c