Pin moves to v0.6.0, package version to 0.6.0:0.
README and instructions.md both promised the opposite of what now happens
and had to be rewritten: an update keeps games in progress unless the rules
actually changed, and a game that genuinely cannot replay is named in the
log rather than described as a version mismatch.
Verified on phoenix.local by doing the thing the release is about. A game
(MAIL-4571) was created on the installed 0.5.6:0, then this build was
installed over it. All four saved games on the volume came back:
Resuming 4 saved game(s)…
Resumed HOPPER-4607 — 37 intents replayed. (written under 0.5.2)
Resumed TRESTLE-5109 — 5 intents replayed. (written under 0.5.3)
Resumed TENDER-8092 — 38 intents replayed. (written under 0.5.5)
Resumed MAIL-4571 — 0 intents replayed. (written under 0.5.6)
The first three had been refused on every boot since the release that
stranded them. They were never damaged, only unreachable, and replaying
them is all it took to get them back — which is the clearest evidence that
the version comparison was answering the wrong question. All four now show
in Games in Progress with the correct Day, Stage and waiting-on player.
Jesse
e84c640067