Sb/3a5a words initiative

.github/workflows/ci.yml

@@ -1,12 +1,13 @@
 name: CI Tests
 
 on:
-  # Runs tests whenever someone opens or updates a Pull Request targeting 'main' or
-  # 'dev' — the integration branch that publishes development images.
+  # Runs tests whenever someone opens or updates a Pull Request, whatever branch it targets.
+  #
+  # This used to be limited to 'main' and 'dev', so a long-running feature branch that takes
+  # its pieces as PRs of its own (feature/system-builder, with sb/* pieces merged into it)
+  # was never tested until the final merge to main. Every PR is a change about to land
+  # somewhere, so every PR gets the suites.
   pull_request:
-    branches:
-      - main
-      - dev
 
   # Runs tests when code is merged or pushed directly to 'main'.
   #

CHANGELOG.md

@@ -5,6 +5,111 @@ Format follows [Keep a Changelog](https://keepachangelog.com/en/1.0.0/).
 
 ---
 
+## [Unreleased]
+
+### Changed
+
+- **Each game system has its own bank.** A character's money now belongs to the game it was
+  earned in: starting a new campaign on another system opens fresh accounts, and switching
+  back finds the old money exactly where it was. On the first start after updating, every
+  player's current balance, debt and bonuses are copied into each system they have a
+  character in, so nothing looks different in any existing game. A full copy of the
+  database is saved beside it first (when the disk has room), and the old bank records are
+  kept untouched.
+
+- **Each game system keeps its own token health.** A token's HP, armor and injuries now belong
+  to the game being played: switching systems puts one game's values away and brings the
+  other's back, and a character who has never been in that game starts fresh. On the first
+  start after updating, every token's current values are saved for each system it could be
+  shown in, so switching looks exactly as it does today for anyone with a character there.
+
+- **The game system picker is a searchable list.** The row of system buttons in the admin
+  panel's GAME tab is now one dropdown: the built-in systems first, then any the GM has made,
+  with a search box and arrow keys. Choosing a different system now asks first, since it
+  changes the game for everyone online.
+
+- **The heart monitor's beat follows how hurt someone is.** Its color always changed as a
+  character was hurt; now its rhythm does too. It stays steady over half health, beats twice as
+  fast at half or less, and turns fast, uneven and weak at a quarter or less, before the
+  flatline. It still shows no numbers, in the HEALTH folder and on the stream overlay alike. With
+  reduced motion turned on in the system settings, the trace holds still but keeps its shape.
+
+### Security
+
+- **Players can no longer use the GM's tools.** A player's own login worked as a key to the GM's
+  side of the server: with the right request, a signed-in player could delete buildings, edit the
+  map, read GM notes, approve accounts, reset passwords, set anyone's bank balance, give themselves
+  editor rights, or post in chat as anyone. Only the GM, and players the GM has granted editing
+  rights, can now do those things. Nothing a player normally does changes: their sheet, portrait,
+  chat, shops and bank all work as before, and granting, revoking and giving back editor rights
+  work as before.
+
+- **Editor rights go only to the player receiving them.** Granting editor rights, or approving an
+  edit request, used to send the new editor's key to every connected player, and any of them
+  could copy it. It now reaches only the player being promoted. Approving, denying and ending an
+  edit request were also open to anyone: a player could approve their own request. Those buttons
+  now work only for the GM and granted editors, as they appear in the admin panel.
+
+### Under the hood
+
+- **A custom system's words reach the initiative tracker and the dice log.** START, JOIN and END
+  INITIATIVE, the INIT score, the turn counter and the dice log's "rolled INITIATIVE" lines use the
+  words a custom system's GM chose for initiative and the turn. The built-in systems keep their
+  wording exactly, ROUND and PASS included. The first tracker's 1d20 roll window, which nothing
+  had opened since players began joining from the tracker itself in July, was removed.
+
+- **A custom system's words reach the shops and the bank button.** The shop's messages, receipt
+  and refusals, the steps for stocking an empty shop, and the SHOP, VIEW_BANK and SHOP_CATALOGUES
+  buttons use the words a custom system's GM chose for shops, money, the bank, the GM and
+  characters: a game that calls its shops MERCHANTS says "NOTHING HERE THIS MERCHANT WOULD BUY".
+  A term the system did not rename keeps today's text, and the built-in systems are unchanged.
+  Custom systems get shops of their own in a later piece.
+
+- **A custom system's words show on the sheet, the token window and the HEALTH folder.** When the
+  GM who built a custom system gives hit points, the character, the GM or initiative a name of
+  their own, those places use it: a game that calls hit points VIGOR shows VIGOR where HIT_POINTS
+  was. A term it did not rename keeps today's text. Nothing changes for the built-in systems, and
+  no custom system can be made yet.
+
+- **Custom game systems can rename the app's words.** A system's own words for terms such as HP,
+  credits, level and GM now reach every window, ready for the windows to use them. Nothing on
+  screen changes yet, and the built-in systems keep their wording exactly.
+
+- **Custom game systems can be shared as files.** A published system exports as one readable
+  `.citysys` file, and installs on another server after a preview that changes nothing: as a new
+  system, an update, or a second copy beside it. It is never merged, and a file never carries
+  characters. Deleting a custom system now hides it instead, so reinstalling its file brings it
+  back with every character played in it.
+
+- **Custom game systems choose how health works.** Creating one asks how its core works: the
+  health model (one pool, two tracks, damage types, harm levels, a wound count, hit locations, or
+  none), how characters advance, its common dice and its unit of distance. Each health model
+  takes damage by its own rules and has its own HEALTH folder, and other players still see a
+  description, never a number. The built-in systems' health is unchanged.
+
+- **Custom game systems can keep fields for the GM, and give NPCs their own stat blocks.** A
+  player sees a GM-only field, such as XP or an awarded item, but cannot change it, including by
+  uploading a sheet. NPCs can have a shorter layout and power tiers for GENERATE_SHEET.
+
+- **A published custom game system can run the game.** It appears in the game system picker
+  beside the built-in ones, players' sheets are drawn from its own layout by the same sheet
+  window, and its derived values are worked out on every save. Players' browsers receive the
+  sheet's layout and wording, never its formulas. There is no editor for building one yet.
+
+- **Custom game systems can be stored.** Each one keeps a draft the GM edits and a published
+  copy a game would run. A draft can be saved half-built, but it cannot be published until
+  its problems are fixed, and the system a game is running cannot be deleted. Only the main
+  admin can reach any of it, and nothing in the game uses these yet.
+
+- **The first piece of the system builder.** An engine that works out a sheet's derived
+  values (modifiers, saves, maximums) from a written description instead of code, with a
+  safe formula language that can only do arithmetic. It is not switched on for anything:
+  every sheet is still worked out exactly as before. It is proven by restating CWN's and
+  Shadowrun's derived values as data and checking the results match the existing code on
+  thousands of generated sheets.
+
+---
+
 ## [1.14.4] - 2026-09-29
 
 NPC sheets and hidden faces stay with the GM.