JesseandClaude Opus 5
74aea24d74
Submodule pinned to v0.7.3 (45580d8), `current.ts` at `0.7.3:0`, release notes rewritten in all five locales, README.md and instructions.md updated. No new version file and no migration: the outgoing 0.7.2:0's `up` is empty, which is `versions.md`'s common case, so `current.ts` bumps in place and `index.ts` is untouched. Two features, both about the end of a game. A game no longer stops dead when the timetable runs out — it enters a fourth state, `awaitingExtension`, and asks the table whether to play one more Day, unanimously in multiplayer with one refusal decisive. The official result is frozen at the original `config.days` and never rewritten, so playing on is explicitly an exhibition, and a §3.4 collision breach is neither extendable nor able to overwrite a recorded result. And the end of a game renders a full results screen in place of the raw `outcome.reason` enum the page used to print. GAMES IN PROGRESS SURVIVE THIS ONE, which is the opposite of the last release and is why the notes lead with it in every locale. No card data changed and the engine changes are additive, so every intent in a 0.7.2 save is still legal: the save replays intact and the game simply pauses on the new question at the end. Upstream proves it rather than asserting it — the suite replays the three recorded games in `public/replays`, all made under an older ruleset, and asserts every intent still applies. Anyone updating from 0.7.1 or earlier is still in the old boat, and both docs say so. README.md gains a short diagnosing note, since `awaitingExtension` is a state an administrator can meet and misread: such a game is persisted and listed as `active`, resumes on restart like any live game, and shows nobody to wait for — because a vote is not a turn. Verified: `npm run check` clean, prettier clean, `make x86` packs as v0.7.3:0. NOT verified: not installed on a box and not played. Extended play has never been exercised against a running service — upstream `TODO.md` #35. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01EAgJSmeV8zrMh55Mj85ESb
97 lines
8.2 KiB
TypeScript
97 lines
8.2 KiB
TypeScript
import { IMPOSSIBLE, VersionInfo } from '@start9labs/start-sdk'
|
|
|
|
export const current = VersionInfo.of({
|
|
// `<upstream>:<downstream>` — the upstream half tracks the bundled Station Master tag exactly
|
|
// (`versions.md`'s consistency checklist), so bumping the submodule pin and bumping this are one
|
|
// action. The downstream half moves only for packaging-only changes, and RESETS to `:0` when the
|
|
// upstream half moves — v0.7.0 ended on `:3` only because three test packs were played before it
|
|
// was released.
|
|
version: '0.7.3:0',
|
|
releaseNotes: {
|
|
en_US:
|
|
'Bundles Station Master v0.7.3. Games in progress carry over: unlike v0.7.2, neither the deck nor the ' +
|
|
'save format has changed. When the last Day on the timetable runs out, the game now asks instead of ' +
|
|
'stopping \u2014 you may play one more Day, and at the end of that Day it asks again. In a multiplayer ' +
|
|
'game every player has to agree, and a single refusal ends it. The result is settled at the ORIGINAL ' +
|
|
'length and never changes: in a five-Day game played on to eight, the winner is still whoever led at ' +
|
|
'the end of Day 5. A game that ends on too many collisions is final and is offered no extra Day. And ' +
|
|
'the end of a game now brings up a full results screen \u2014 why it ended, in plain words rather than an ' +
|
|
"internal code; who won; every player's Revenue; the rules the game was dealt under; and what the " +
|
|
'railroad actually did, from trains through the Division and loads made up and broken to passengers ' +
|
|
'carried, cars switched and trains lost.',
|
|
es_ES:
|
|
'Incluye Station Master v0.7.3. Las partidas en curso se conservan: a diferencia de la v0.7.2, no han ' +
|
|
'cambiado ni la baraja ni el formato de guardado. Cuando se agota el \u00faltimo D\u00eda del horario, la ' +
|
|
'partida ahora pregunta en vez de terminar: pod\u00e9is jugar un D\u00eda m\u00e1s, y al final de ese D\u00eda vuelve a ' +
|
|
'preguntar. En una partida multijugador deben estar de acuerdo todos los jugadores, y una sola ' +
|
|
'negativa la termina. El resultado se decide con la duraci\u00f3n ORIGINAL y no cambia nunca: en una ' +
|
|
'partida de cinco D\u00edas prolongada hasta ocho, gana quien iba en cabeza al final del D\u00eda 5. Una ' +
|
|
'partida que termina por exceso de colisiones es definitiva y no recibe ning\u00fan D\u00eda adicional. Y al ' +
|
|
'terminar aparece una pantalla de resultados completa: por qu\u00e9 termin\u00f3, explicado con palabras y no ' +
|
|
'con un c\u00f3digo interno; qui\u00e9n gana; los Ingresos de cada jugador; las reglas con las que se reparti\u00f3 ' +
|
|
'la partida; y lo que hizo realmente el ferrocarril, desde los trenes que cruzaron la Divisi\u00f3n y las ' +
|
|
'cargas formadas y deshechas hasta los pasajeros transportados, los vagones maniobrados y los trenes ' +
|
|
'perdidos.',
|
|
de_DE:
|
|
'Enth\u00e4lt Station Master v0.7.3. Laufende Partien bleiben erhalten: anders als bei v0.7.2 hat sich ' +
|
|
'weder am Deck noch am Speicherformat etwas ge\u00e4ndert. Wenn der letzte Tag des Fahrplans abgelaufen ' +
|
|
'ist, fragt das Spiel jetzt, statt einfach aufzuh\u00f6ren \u2014 ihr d\u00fcrft einen weiteren Tag spielen, und am ' +
|
|
'Ende dieses Tages fragt es erneut. In einer Mehrspielerpartie m\u00fcssen alle zustimmen, eine einzige ' +
|
|
'Ablehnung beendet sie. Das Ergebnis wird \u00fcber die URSPR\u00dcNGLICHE Spiell\u00e4nge entschieden und \u00e4ndert ' +
|
|
'sich nie: Wer eine F\u00fcnf-Tage-Partie auf acht Tage verl\u00e4ngert, sieht immer noch den Sieger vom Ende ' +
|
|
'des 5. Tages. Eine Partie, die an zu vielen Kollisionen endet, ist endg\u00fcltig und bekommt keinen ' +
|
|
'weiteren Tag. Und am Ende erscheint jetzt eine vollst\u00e4ndige Ergebnisanzeige: warum die Partie ' +
|
|
'endete, in Worten statt als interner Code; wer gewinnt; die Einnahmen jedes Spielers; die Regeln, ' +
|
|
'mit denen ausgeteilt wurde; und was die Eisenbahn tats\u00e4chlich geleistet hat, von Z\u00fcgen durch die ' +
|
|
'Division und gebildeten wie aufgel\u00f6sten Ladungen bis zu bef\u00f6rderten Fahrg\u00e4sten, rangierten Wagen und ' +
|
|
'verlorenen Z\u00fcgen.',
|
|
pl_PL:
|
|
'Zawiera Station Master v0.7.3. Trwaj\u0105ce partie zostaj\u0105 zachowane: w odr\u00f3\u017cnieniu od v0.7.2 nie ' +
|
|
'zmieni\u0142a si\u0119 ani talia, ani format zapisu. Gdy ko\u0144czy si\u0119 ostatni Dzie\u0144 rozk\u0142adu, gra teraz pyta, ' +
|
|
'zamiast po prostu si\u0119 sko\u0144czy\u0107: mo\u017cecie zagra\u0107 jeszcze jeden Dzie\u0144, a na jego koniec zapyta ' +
|
|
'ponownie. W grze wieloosobowej musz\u0105 zgodzi\u0107 si\u0119 wszyscy, a jedna odmowa ko\u0144czy parti\u0119. Wynik ' +
|
|
'rozstrzyga si\u0119 na PIERWOTNEJ d\u0142ugo\u015bci gry i nigdy si\u0119 nie zmienia: w pi\u0119ciodniowej partii ' +
|
|
'przed\u0142u\u017conej do o\u015bmiu Dni wygrywa ten, kto prowadzi\u0142 na koniec Dnia 5. Partia zako\u0144czona zbyt ' +
|
|
'wieloma kolizjami jest ostateczna i nie dostaje kolejnego Dnia. A na ko\u0144cu pojawia si\u0119 pe\u0142ny ekran ' +
|
|
'wynik\u00f3w: dlaczego partia si\u0119 sko\u0144czy\u0142a \u2014 s\u0142owami, nie wewn\u0119trznym kodem; kto wygrywa; Przych\u00f3d ' +
|
|
'ka\u017cdego gracza; zasady, wed\u0142ug kt\u00f3rych rozdano gr\u0119; i co kolej naprawd\u0119 zrobi\u0142a, od poci\u0105g\u00f3w przez ' +
|
|
'Dywizj\u0119 i \u0142adunk\u00f3w utworzonych oraz rozformowanych po przewiezionych pasa\u017cer\u00f3w, przetoczone wagony i ' +
|
|
'stracone poci\u0105gi.',
|
|
fr_FR:
|
|
'Inclut Station Master v0.7.3. Les parties en cours sont conserv\u00e9es : contrairement \u00e0 la v0.7.2, ni ' +
|
|
'le jeu de cartes ni le format de sauvegarde n\u2019ont chang\u00e9. Quand le dernier Jour de l\u2019horaire est ' +
|
|
'\u00e9coul\u00e9, la partie pose d\u00e9sormais la question au lieu de s\u2019arr\u00eater : vous pouvez jouer un Jour de ' +
|
|
'plus, et \u00e0 la fin de ce Jour elle repose la question. En multijoueur, tous les joueurs doivent \u00eatre ' +
|
|
'd\u2019accord, et un seul refus y met fin. Le r\u00e9sultat est \u00e9tabli sur la dur\u00e9e INITIALE et ne change ' +
|
|
'jamais : dans une partie de cinq Jours prolong\u00e9e jusqu\u2019\u00e0 huit, le vainqueur reste celui qui menait \u00e0 ' +
|
|
'la fin du Jour 5. Une partie qui se termine sur trop de collisions est d\u00e9finitive et ne se voit ' +
|
|
'proposer aucun Jour suppl\u00e9mentaire. Et la fin d\u2019une partie affiche maintenant un \u00e9cran de r\u00e9sultats ' +
|
|
'complet : pourquoi elle s\u2019est termin\u00e9e, en toutes lettres plut\u00f4t qu\u2019en code interne ; qui gagne ; ' +
|
|
'les Recettes de chaque joueur ; les r\u00e8gles avec lesquelles la partie a \u00e9t\u00e9 distribu\u00e9e ; et ce que le ' +
|
|
'chemin de fer a r\u00e9ellement fait, des trains ayant travers\u00e9 la Division et des chargements form\u00e9s et ' +
|
|
'd\u00e9faits aux voyageurs transport\u00e9s, wagons man\u0153uvr\u00e9s et trains perdus.',
|
|
},
|
|
migrations: {
|
|
/**
|
|
* NOTHING TO CARRY, AND THIS TIME NOTHING IS LOST EITHER.
|
|
*
|
|
* A migration moves DATA a previous version wrote. There is none to move: the package keeps its
|
|
* saved games as a seed plus the moves played, and nothing about their shape has changed.
|
|
*
|
|
* THE DIFFERENCE FROM v0.7.2, which is the thing worth writing down. That release emptied this
|
|
* same function for a much worse reason — the deck went from 206 cards to 121, so a card id
|
|
* recorded under v0.7.1 meant a different card or none, and every game in progress was declined
|
|
* on startup. v0.7.3 changes no card data and adds only new moves, so a v0.7.2 save replays
|
|
* intact: every intent in it is still legal, and the game simply pauses on the new
|
|
* "play one more Day?" question when its timetable runs out instead of finishing outright.
|
|
*
|
|
* Proven rather than assumed: the upstream suite replays the three recorded games in
|
|
* `public/replays`, all made under an older ruleset, and asserts every intent still applies
|
|
* (`test/harness.test.ts`). The release notes lead with it, since the last release's notes had
|
|
* to lead with the opposite.
|
|
*/
|
|
up: async ({ effects }) => {},
|
|
down: IMPOSSIBLE,
|
|
},
|
|
})
|