## **v5.5.0** — Live Is Life (2026-10-30)

### Release

- Version 5.5.0 (maintainer: a new capability, the Live View; Docker-only is parked, a possible 6.0.0): `APP_VERSION` and `CHALKER_VERSION`, Chalker cache busters (`chalker.js?v=35`, `chalker-v132`), release pages `releases/index.html` and `releases/v5.5.0.html`, `sitemap.xml`, `Docs/ReleaseNotes/RELEASE-NOTES-v5.5.0.md`. `llms.txt` (the upload marker, the live copy and the Live View, the import gate, and the "no spectator view" line), `automatic-backup.html` (a failed upload no longer "will not succeed"; new sections When an Upload Fails and Live View) and `rest-api.html` (live.php) are updated; the help covers Config, Analytics and the completing-and-correcting page.
- The design behind it is in `Docs/HUB-DIRECTION.md`: one-way data flow for now (the club's Tournament Manager writes, the server and Analytics only display), and the debt test the Live View passed.

### Upload failure marker

- **A failed automatic upload is no longer silent** (found when the 2026-10-26 tournament never reached the server; the likely cause was a poor connection at the club: the upload at the end of a tournament is fire-and-forget and a failure only reached the console). The outcome of every upload to the remote server is kept per tournament in its own key, `uploadStatus_<tournamentId>` (the tournament and its export are unchanged; no key means "nothing known", so tournaments from before this behave as they did). A finished tournament whose upload failed shows **Not uploaded to <server>: <reason>** with **Upload now** on Setup's current tournament, and a **Not uploaded** chip in the bracket page's status line. A successful upload shows "Uploaded to <server> at <time>" on Setup.
- **The reason is the real one:** the relay could not reach the server ("Could not resolve host"), this computer's server did not answer or has no relay (the page opened as a file), the server failed, or it refused (wrong API key: "Check the API key under Global Settings → Remote backup", a host not allowed, too large).
- **It mends itself when it can.** Network, relay and server failures are tried again while the page is open: after 30 s, 1 min, 2 min, then every 5 minutes, at once when the browser reports it is online again, and when the page is opened with a failure waiting. A refusal is not retried; it waits for someone to fix the cause, and **Upload now** tries it at once and tells you what happened. Repeating is safe: the upload overwrites the same file.
- **Setup's tournament list tags the tournaments that never made it:** a finished tournament whose upload failed carries an amber **Not uploaded** tag on its row (hover: the reason), so anyone can find it, load it and press **Upload now**, also after another tournament has been created. The tag goes when the upload succeeds, and does not show for a record about a remote that is no longer the configured one.
- **Only for the remote server.** The local server is this computer's own, and not having one is normal when the page is opened as a file. A status about an address that is no longer the configured remote is ignored. Deleting a tournament forgets its status. The retry follows the loaded tournament only: one that is not loaded is retried when it is loaded again, and the tag on its row says which one that is (Docs/HUB-DIRECTION.md, step 1).
- Tested in the browser against two local containers (the club's with the working tree, a remote with an API key): the remote down (the real 502 from the relay, chip and note, retry scheduled), the remote started (retry succeeded on its own, chip gone), a wrong key (refused, plain message, no retry), the key fixed and Upload now (uploaded, note updated), the page reloaded with a failure waiting (note shown, retry resumed), the `online` event, and the remote setting removed (notice hidden).
- Files changed: `js/tournament-management.js` (`uploadToServer()`, the upload status and retry functions, `updateTournamentStatus()`, `renderSetupCurrent()`, the delete), `tournament.html`, `css/setup-page.css`, `css/bracket-view.css`, `js/dynamic-help-system.js`, `Docs/HUB-DIRECTION.md`.

### Live View

- **A tournament being played can be watched, read-only, from Analytics** (maintainer's idea, 2026-10-30: the normal bracket page and the leaderboard, going away when the tournament is over and Analytics has it). `js/live-view.js`, `css/analytics-page.css`, `css/bracket-view.css`.
- **Watch opens a list of the matches, the same on a phone and a desktop** (maintainer, 2026-10-30: the list is the default, always, with the bracket one tap away): **Live now** (with the lane), **Up next** and **Results**, newest first, each result with what it recorded ("Cat 2–1 Ben · Cat 1× 180"), under the tournament's name, date, format and how many matches are played. One column, built for a phone; matches still waiting for earlier results are only counted. **Bracket** opens the normal bracket page (read-only); there the back button reads "⬅ List" and returns to the list, and the list's own back button leaves to Analytics. **Leaderboard** opens from either. The list redraws by itself when a result or a start arrives (tested: a result and a started match on lane 1 moved into place within the poll).
- **"Live now"** at the top of the Analytics page, one line per live tournament ("ViewerCup · 2 of 14 matches played") with **Watch**; shown only while a live copy exists, refreshed when Analytics is opened and every 30 s while it is showing. A tournament this Tournament Manager is running itself is left out. `api/live.php`'s list now carries `matches` and `played` for it.
- **The bracket** (from the list's Bracket button) is the normal bracket page with the live copy, in memory, read-only: no Edit, Undo or Match Controls, only "⬅ Analytics" and the Leaderboard in the header (also in analytics mode, where the operator controls are hidden). It asks the server every 8 s (an `ETag` keeps an unchanged answer empty; paused while the tab is hidden) and redraws when something changed; the badge says "● LIVE · updated 21:14", or "Offline · last updated …". Selecting a finished match shows what it recorded ("Hal 2× 180, 3× ton"). The Leaderboard opens as usual, with "click a player to edit statistics" hidden.
- **When the tournament is over** (the live copy is gone because the final backup succeeded) the page says "This tournament has finished. See it in Analytics"; the button leaves, and Analytics takes the finished tournament in as it loads.
- **Nothing is stored and nothing of the viewer's own changes.** The live copy goes into the page's tournament, players and matches, tagged `_analyticsPreview` so nothing saves; the viewer's own tournament is put back when they leave; `localStorage` is not written (the saved page is set to Analytics, so a reload lands there). The club's point values are put into `config.points` only for the moment the leaderboard is calculated (the view toggles save the whole config, so they must never be left in it): a viewer's own value of 7 per 180 was used by nobody and put back, the club's 1 gave the points.
- **Removable:** with `js/live-view.js` deleted, the Analytics strip never shows and nothing else changes (the hooks in `main.js`, `bracket-view.js` and `bracket-rendering.js` check that `LiveView` exists).
- Tested in the browser (a club container in full mode producing the live copy, a remote in analytics mode as the member): the strip, Watch, the badge, the trimmed header, the bracket and a match's achievements, the leaderboard with the club's points, updates arriving by themselves, the hand-over at the end (live list empty, the finished tournament in the normal list, "This tournament has finished", See it in Analytics: imported, strip gone), and the viewer's own tournament restored.
- **The end is told truthfully** (found by the maintainer from a screenshot: "This tournament has finished" above "Up next · 1" and "10 of 14 played"). The live copy also goes when a tournament is reset or deleted, so its absence says nothing about finishing, and the last frame is stale. When the live copy is gone the page now asks the server's normal list: if the finished tournament is there it loads it and shows the true final results ("14 of 14 played", every result with what it recorded, the Grand Final first) under "This tournament has finished. See it in Analytics"; if not it says "This tournament is no longer live", drops the Live now and Up next groups and shows only the results "as of 21:14", with a "Back to Analytics" button. Tested both: a tournament played to the end, and one that was reset while watched.
- Not tested: a real phone (a narrow window only).
- Files changed: `js/live-view.js`, `css/live-view.css`, `api/live.php`, `js/main.js`, `js/bracket-view.js`, `js/bracket-rendering.js`, `tournament.html`, `css/analytics-page.css`, `css/bracket-view.css`, `js/dynamic-help-system.js`, `Docs/REST_API.md`, `Docs/HUB-DIRECTION.md`.

### Live copy: statistics and per-match achievements

- **The live snapshot now carries what a leaderboard needs:** each player's statistics (180s, tons, high outs, short legs, lollipops), the club's point values (`config.points`, since a viewer's own browser has its own), and for each completed match what it recorded (`achievements`, as `{ p1, p2 }`, read from the match's transaction; the history itself is still not sent). 7 KB for an 8-player double elimination with 14 matches. The setting's text says statistics are included.
- **Spike (nothing shipped): the snapshot draws the normal bracket page and the leaderboard.** Loaded in memory on the remote test container (no storage written, the member's own current tournament untouched): all 14 cards, the backside and finals, done and ready matches; the leaderboard's points, 180s, tons, high outs and legs won and lost match what the club's own leaderboard would show. A viewer needs, in memory only, `paid` set on the players (the status line counts it; payment is not sent) and the snapshot's point values in `config.points`.
- **Still to do for a viewer:** switch off "click a player to edit statistics" and the Match Controls entry in it, show a match's achievements when it is selected (the data is in the snapshot), poll and redraw, and the "Live now" strip on Analytics.
- Files changed: `js/live-upload.js`, `tournament.html` (the setting's text).

### Analytics import gate

- **Analytics no longer imports a tournament that is still being played.** `_autoImportFromDisk()` (`js/newton-history.js`) imported every tournament in the server's list once, by id, whatever its status, and recorded it as finished; so an in-progress tournament uploaded by hand (Backup to server offers the active one) was imported into every member's browser as completed, and the final upload then skipped as already there. It now skips anything whose status is not `completed` (files with no status, from before the field, are imported as before), in the list and in the file.
- Tested: a completed and an in-progress tournament on a server, Analytics opened: only the completed one imported.

### Live copy while a tournament is played

- **A slim copy of the tournament on the server after every change, off by default** (Global Settings → Server → **Live copy while it is played**; Docs/HUB-DIRECTION.md, step 3). `js/live-upload.js` sends it from `saveTournamentOnly()` (debounced 1.5 s) to `api/live.php` on this computer's own server and, through the relay with the key, on the remote one. Each send replaces the one before, so a dropped one is mended by the next; nothing is queued. Nothing is sent before the bracket is drawn.
- **The snapshot:** the format and status, the players (name, id, placement) and each match's state, score, lane and referee; no transaction history, no statistics, no payment: 1.6 KB for four players. The fields are whitelisted, since the copy is public.
- **Kept out of Analytics by construction:** it is stored in `tournaments/live/<id>.json`, a subfolder the tournament list never reads (as `registry/` and `corrections/`). When the finished tournament's backup succeeds, the live copy on that server is removed (the final copy is authoritative); a failed backup leaves it, showing the finished state. A reset or deleted tournament's goes too, an older revision arriving late is ignored, and a live copy not written to for three days is removed.
- **The setting says what it does:** anyone who can open the server can read a live copy, as with everything else there. No viewer yet: the data is there for one (the debt test in `Docs/HUB-DIRECTION.md`).
- Removable: with the setting off, or `js/live-upload.js` deleted, nothing changes.
- Tested in the browser against two local containers (club and remote with an API key): nothing sent before the draw; after the draw, a started match and a result on both servers; the live copy gone and the final in the normal list when the backup succeeded; reset removed both; endpoint: key required, a stale write ignored, a path-traversal id refused, `ETag` and `304`, never in the tournament list.
- Files changed: `api/live.php`, `js/live-upload.js`, `js/tournament-management.js` (the hooks), `js/results-config.js`, `js/types.js`, `tournament.html`, `js/newton-history.js`, `Docs/REST_API.md`, `Docs/HUB-DIRECTION.md`.

## **v5.4.8** — Non, je ne regrette rien (2026-10-23)

### Release

- Version 5.4.8: `APP_VERSION` and `CHALKER_VERSION`, Chalker cache busters (`chalker.js?v=34`, `chalker-v131`), release pages `releases/index.html` and `releases/v5.4.8.html`, `sitemap.xml`, `Docs/ReleaseNotes/RELEASE-NOTES-v5.4.8.md`. `llms.txt` and the help (bracket page, Completing & Correcting Matches) mention Edit match.

### Analytics register: match achievements at tournament end

- **Found while checking that an edit reaches Analytics:** at the end of a tournament `reconcileMatchAchievements()` reads each match's achievements as `{ p1, p2 }`, but match completion (by hand and from the Chalker) stored them as `{ [playerId]: delta }`. It saw nothing recorded, took each player's whole tournament totals as unattributed, and added them to that player's last match under `p1`/`p2` beside the real entry: the last match then showed the player's whole tournament, and its per-match achievement points were summed over both. The last match's record was also re-saved as `live` among `final` ones (`saveMatch()` forced the status).
- **Fixed in three parts.** (1) `completeMatch()` and the edit's register save store `{ p1, p2 }` (new `NewtonDB.slotAchievements()`); the transaction keeps its per-id map, so undo is untouched. (2) Reconcile reads either shape and writes records that were stored per id back as `{ p1, p2 }`, so a tournament played partly before this change reconciles correctly; only stats nobody recorded in a match (entered outside the dialogs) go to the player's last match. (3) `saveMatch()` keeps a status the caller passes (reconcile passes `final`).
- **Not repaired:** tournaments already finalized keep their inflated last-match entries (maintainer: leave the recompute).
- Tested in the browser: a 4-player single elimination played to the end with an edit on the way and two tons entered outside any dialog: every record `{ p1, p2 }` and `final`, the edited match with its new score and achievements, the winner's last match with only its own ton, the outside tons on the other finalist's last match alone.
- Files changed: `js/newton-db.js` (`slotAchievements()`, `saveMatch()`, `reconcileMatchAchievements()`), `js/clean-match-progression.js` (`completeMatch()`), `js/bracket-rendering.js` (`_saveEditedMatchToRegister()`).

### Edit match

### Edit match

- **A completed match can be edited, not only undone** (raised 2026-10-19: several matches were reported incompletely, and achievements, legs won and winners all had to be corrected; achievements entered by hand were tied to no match). **Edit match** sits beside **Undo match** in the bracket's selection bar and opens the Confirm Winner dialog filled in with the recorded result ("Edit: A beats B", **Save changes**). Rules (maintainer): legs won and achievements can always be edited, locked stages included; the winner only when `isMatchUndoable()` allows it (no downstream match played or live, no locked stage), so the winner rule is the undo rule, from one function. Never in a read-only tournament, for walkovers, or for matches reported from the Chalker (QR or network): their leg-by-leg detail in the register would contradict an edit, so those are corrected with undo and replay.
- **Winner unchanged:** the match's `COMPLETE_MATCH` transaction is rewritten in place (additive `editedAt`) and `finalScore` replaced, so history keeps one transaction per match and undo is untouched; the register record gets the new legs and achievements and keeps its `completedAt`. **Winner changed:** the existing undo, then `completeMatch()` for the other player; the transaction carries `editedAt` and `originalWinner`.
- **Achievements are tied to the match:** the dialog's baseline is the players' stats without what the match recorded, so it opens showing "Achievements for this match", and changes become the transaction's new delta. Cancel and Esc restore the stats to how they were when the dialog opened.
- `undoManualTransaction()` now returns the promise of its register deletes (before: nothing), so a winner change writes the new result only after the old record is gone. `rollbackAchievements()` uses a new `subtractAchievementStats()` that the edit shares.
- **Swiss:** the dialog names what locks the winner ("round 2 has started (R2-3 is played) and was drawn from round 1's results"): the next round is drawn from every result of the round, so one played match in it locks them all (the undo rule). Found when the maintainer asked why a round 1 match whose own next matches were unplayed was locked.
- Tested in the browser (8-player double elimination, hand-completed matches with achievements): score and achievements edit, Cancel restoring the stats, Esc, a winner change (the next match and the backside placement follow, one transaction left, `originalWinner` kept, register record updated), the locked winner (note shown, no Change winner button, score still editable, a direct winner change refused), QR, read-only and not-completed matches not editable. Detail in `Docs/EDIT-MATCH.md`.
- Files changed: `js/bracket-rendering.js`, `js/clean-match-progression.js` (`showWinnerConfirmation()`), `js/bracket-view.js`, `js/dynamic-help-system.js`, `Docs/EDIT-MATCH.md`, `Docs/UNDO.md`.

## **v5.4.7** — Urgent PHP Security Release (2026-10-22)

### Release

- Version 5.4.7: `APP_VERSION` and `CHALKER_VERSION`, Chalker cache busters (`chalker.js?v=33`, `chalker-v130`), release pages `releases/index.html` and `releases/v5.4.7.html`, `sitemap.xml`, `Docs/ReleaseNotes/RELEASE-NOTES-v5.4.7.md`. A security release: no application code changed.

### Docker image: PHP security fixes (CVE-2026-109618, CVE-2026-109619)

- **PHP published an out-of-band security release on 2026-10-21** for two critical remote code execution flaws in its core (CVSS 9.2 each), fixed in 8.5.12, 8.4.27, 8.3.36 and **8.2.35**. Remote code execution was confirmed on PHP-FPM, which the Docker image uses. Earlier releases of the image were built on an older 8.2.x.
- **The image is rebuilt on PHP 8.2.35.** `docker/Dockerfile` keeps the floating `php:8.2-fpm-alpine` tag, which carries the fix; a comment says 8.2.35 is the minimum. The publish workflow (`.github/workflows/docker-hub-publish.yml`) now builds with `pull: true`, so the newest base image is taken on every build and a cached layer cannot keep an old PHP.
- **Anyone running the Docker image should pull the new `:latest` and recreate the container** (`docker compose pull && docker compose up -d`). The Chalker app and the single-file tournament page are static and do not run PHP.
- PHP 8.2 is security-supported until the end of 2026; moving the image to PHP 8.4 is planned as a separate release.
- Files changed: `docker/Dockerfile`, `.github/workflows/docker-hub-publish.yml`.

## **v5.4.6** — Peek-a-Boo (2026-10-12)

### Release

- Version 5.4.6: `APP_VERSION` and `CHALKER_VERSION`, Chalker cache busters (`chalker.js?v=32`, `chalker-v129`), release pages `releases/index.html` and `releases/v5.4.6.html`, `sitemap.xml`, `Docs/ReleaseNotes/RELEASE-NOTES-v5.4.6.md`. The help (bracket page) and `llms.txt` (Match Controls) mention the drawer: the strip, the ← Bracket pill and Esc.

### Undo in a completed Swiss, Round Robin or Cup and Plate tournament

- **Undoing a match in a completed tournament left it completed** in Swiss (found by the maintainer: after undoing the final and the bronze final, Match Controls still showed the podium), in Round Robin with one group (any group match), and in Cup and Plate (the Plate's final or bronze final, when one of them was played last). The undo reset the status only for a fixed list of final matches: double elimination's grand final, single elimination's final, and Round Robin's cup finals and bronze finals.
- **Now any undo in a completed Swiss, Round Robin or Cup and Plate tournament takes it back to active** and clears the placings, as the finals did. These formats are over when a check finds everything played, so replaying the match completes the tournament again with fresh placings. Double and single elimination keep their rule: their completion leaves out the bronze final, so undoing it must keep the tournament completed.
- Only when the status is reset changes; how matches are rolled back is untouched.
- Tested in the browser: a completed Swiss (undo the final and the bronze final: active, Match Controls shows them ready; replay: completed, top four placed, the podium back) and a completed one-group double round robin (undo the last match: active; replay: completed).
- Files changed: `js/bracket-rendering.js` (`undoManualTransaction()`).

### Bracket page: Match Controls as a drawer over the bracket

- **First-time users didn't find the bracket** (the maintainer let friends try the Tournament Manager): the page starts on Match Controls, which filled the frame, and nothing said a bracket was behind it; when Match Controls was a dialog, the bracket around it had made that obvious. They also didn't tell the bracket page from the other pages.
- **Match Controls is now a drawer from the right,** over the bracket: a strip of the bracket stays visible on its left, lightly dimmed (16% of the width, 140–260px), and the drawer has a shadow on its left edge. Clicking the strip, or the orange **← Bracket** pill (a thin black border and a thin white ring around it, so it stands out from the dimmed bracket) at the top of the strip beside the drawer's edge, shows the bracket; on hover the pill says "Click or press ←", so the arrow key is discovered too. (A dark pill in the middle of the strip, beside a round ×, was tried first: it blended into the bracket's cards. The accent colour and the top, where the eye comes down from the tabs, make it found at once; one control instead of two.) **Esc closes Match Controls** and shows the bracket as it was left (the bracket's own Esc, which clears the selection, doesn't run then); not while typing, choosing in a list or a dialog is open, nor when the Esc just closed a dialog (the Leaderboard opened over Match Controls closed both at once: the dialogs' Esc handler in `main.js` runs first and marks the key handled, so both Esc handlers on the bracket page now skip a handled key; the bracket's selection no longer clears when Esc closes a dialog either). The Bracket | Match Controls tabs and the arrow keys work as before; the Console still fills the frame.
- **The finished tournament's Leaderboard button in Match Controls is gone** (maintainer): the header's Leaderboard shows above the drawer, so it was a second way to the same place. Tournament Analytics and Export tournament stay.
- **The bracket page stands apart:** its surround is a deeper warm shade (`#e4e0d9`), and the other pages are lighter, near white (`--nt-bg` in `css/design-tokens.css`: `#fbfaf8`, was `#f4f3f1`; also Match Controls' sheet and the Console). The shade alone, against the old page colour, was too subtle to notice (maintainer); a darker bracket page would have cost the header's contrast.
- Tested in the browser: a running 32-player double elimination (round 1 visible in the strip), a finished Cup and Plate's podium (the pill clear of the sheet's heading), before the draw; clicking the strip or the pill shows the bracket; Esc closes Match Controls with the bracket's selection kept, does nothing while a list has focus, and on the bracket still clears the selection.
- Files changed: `css/bracket-view.css`, `css/design-tokens.css`, `tournament.html`, `js/bracket-rendering.js` (`_bvSetView()`: `bv-on-controls`; the Esc handler; `_mcCompletedHTML()`), `js/bracket-view.js` (its Esc skips a handled key), `Docs/BRACKET-REDESIGN.md`.

## **v5.4.5** — Look Sharp! (2026-10-11)

### Release

- Version 5.4.5: `APP_VERSION` and `CHALKER_VERSION`, Chalker cache busters (`chalker.js?v=31`, `chalker-v128`), release pages `releases/index.html` and `releases/v5.4.5.html`, `sitemap.xml`, `Docs/ReleaseNotes/RELEASE-NOTES-v5.4.5.md`; `llms.txt` and the help reviewed (no changes needed beyond this version's own).

### Bracket: loser drops bend halfway

- **A selected match's loser drop bent in the gap just before its target column**, where the backside's own winner lines fork into the next round: the dashed line climbed on top of those forks and was hard to follow (noticed by the maintainer looking for a screenshot). It now bends as near halfway as it can, an S or Z: out horizontally, down or up in the column gap nearest the middle, and horizontally into the player row it fills. A gap qualifies only if the bend crosses no card and runs along no other line; with the finals in the middle that is usually the open space beside the finals.
- Where no gap qualifies, the late bend stays: drops into the backside's outer column (their last leg would cross the next column's cards; their gap has no forks), all drops with the finals on the right, and one drop in 32-player brackets. If the late bend's gap has a fork in it, the bend now sits beside the fork, nearer the target card, instead of on it.
- To know where the forks run, the winner lines are drawn before the loser lines, and the vertical runs of the always-drawn lines are recorded. Only drawing changes: `bracket-view.js` never touches tournament data or the progression tables.
- Tested in the browser: every loser drop in double elimination brackets of 8, 16 and 32 (finals in the middle and on the right) and with qualifiers (40): none crosses a card or runs along a line; 2 of 6, 6 of 14 and 13 of 30 bend near the middle with the finals in the middle. Single elimination, Cup and Plate, Round Robin and Swiss draw as before.
- **A new bracket screenshot** (`Screenshots/tournament-bracket-zoom.png`, by the maintainer) for the landing page's bracket step and the README: a selected match, its loser's drop bending beside the finals. Alt texts say so (it said Follow).
- Files changed: `js/bracket-view.js`, `Docs/BRACKET-REDESIGN.md`, `Screenshots/tournament-bracket-zoom.png`, `landing.html`, `landing-page.php`, `README.md`.

### Docker documentation: port 2020

- **The documented host port was 8080**, but `docker-compose.yml` (and the SSL compose) publish `2020:2020`, so following the quick start led to a page that wasn't there. 2020 is the port by design ("Double 20", double tops; maintainer). Every `8080` in the current docs is now 2020: `http://localhost:2020`, `docker run -p 2020:2020`, the reverse-proxy and localhost-only examples, the troubleshooting steps.
- **`NEWTON_HOST_PORT` removed from the docs:** the quick start's variables table and its "Port already in use" tip used it, but no compose file reads it. The tip now says to change the host port in `docker-compose.yml` (`"9000:2020"`). `docker/README.md`'s own tip still said `8080:80`, from before the internal port was 2020.
- The quick start says "the Tournament Manager is running" instead of "NewTon is running".
- Files changed: `docker-quickstart.html`, `DOCKER-QUICKSTART.md`, `docker/README.md`, `rest-api.html`, `Docs/REST_API.md`, `api/README.md`, `llms.txt`.

### The headline everywhere, and a new share image

- **README and `llms.txt`** led with the old tagline, "The Offline Authority in Darts." Both now lead with the website's headline, "Run the whole darts night. Offline.", and the hero's line under it.
- **The README is rewritten** (maintainer: it had "been suffering from just being accumulated", as the landing page had). It follows the website: the headline, the share image and one line of links (try, download, Docker, guide, release notes, changelog); the three cards (the middle one now "Chalk. Send. Done.", results over your own network or by QR code, instead of "Scan. Score. Done."); How a night runs in seven steps, the bracket third, with the bracket and Match Controls screenshots; Pick your format as a table with each format's line and player range (it said "single and double-elimination" only); the features grouped by the night (before the draw, during, after the final, built to last); Getting started as the website's three ways; Technical details; Credits and the licensing split, unchanged. Gone: the traffic-light colour legend, Use cases, and features described as they were before the bracket redesign (Magic Zoom, click-to-select winners). The Docker snippet now says `http://localhost:2020`, the port `docker-compose.yml` maps (it said 8080).
- **`llms.txt` names the software NewTon DC Tournament Manager** throughout: the About line said "NewTon DC is a web application", and "NewTon" stood for the software in four more places. About now says the club makes it, and Tips for AI Services starts with the naming rule. Its use case mentions network results as well as QR.
- **A new share image**, `Screenshots/newton-share.png` (1200×630): the landing page's hero, condensed (the wordmark, the headline, the new hero bracket and the Chalker on ink with the dartboard, newtondarts.com). It replaces the retro poster as `og:image`, `twitter:image` and the structured data's `screenshot` in both landing files, and as the README's image. Its source is `Docs/mockups/share-image.html`, captured with headless Chrome at 1200×630 (the command is in its head), so it can be redone when the hero changes. The poster files stay.
- Files changed: `README.md` (rewritten), `llms.txt`, `landing.html`, `landing-page.php`, `Screenshots/newton-share.png` (new), `Docs/mockups/share-image.html` (new), `Docs/PARKING-LOT.md`.

### Landing page: a new hero image, not clickable

- **The hero's bracket is a new screenshot**, `Screenshots/hero-se.jpg` (1400 px, by the maintainer): an 8-player single elimination bracket with the final in the middle, a semifinal live. The old one was a crop of a 32-player bracket, too small to read at hero size; the bracket step below now shows the whole double elimination bracket, so the two show different formats.
- **Neither hero image opens the lightbox** any more (maintainer): the hero is a picture of the product, and the timeline right below is the gallery. `lightbox-trigger`, `data-full` and the zoom cursor removed.
- **The Chalker card hangs lower** (the stage's bottom padding 40 → 80 px), so it no longer covers the bracket's lower left quarterfinal; the new image is wider, so the window is shorter.
- Tested in the browser: desktop, 820 px and 375 px (no horizontal scroll; the Chalker card is hidden on phones, as before).
- Files changed: `landing.html`, `landing-page.php`, `css/home.css`, `Screenshots/hero-se.jpg` (new).

### Landing page: the bracket in How a night runs

- **The bracket gets its own step**, step 3 "All night long" (between the draw and Match Controls; the later steps become 4–7): "The bracket, centre stage." The night's timeline went from the draw straight to Match Controls, leaving out what the room watches all night. A featured step, unlike the others: full width with a red number, the text beside four features (Follow a player, click a match, finals in the middle or on the right, every format drawn its own way), and the full bracket screenshot below (`tournament-bracket-zoom.png`, the whole bracket with Follow on; the hero keeps its crop). Requested by the maintainer ("the jewel, what everything runs around").
- Tested in the browser: desktop width and 375 px (no horizontal scroll).
- Files changed: `landing.html`, `landing-page.php`, `css/home.css`.

## **v5.4.4** — Run the whole darts night. Offline. (2026-10-11)

### Release

- Version 5.4.4: `APP_VERSION` and `CHALKER_VERSION`, Chalker cache busters (`chalker.js?v=30`, `chalker-v127`), release pages `releases/index.html` and `releases/v5.4.4.html`, `sitemap.xml`, `Docs/ReleaseNotes/RELEASE-NOTES-v5.4.4.md`; `llms.txt` (the Dashboard's top 10 and Latest tournaments) and the help reviewed; the release template's font preload is Inter (`releases/README.md`). The font preload in the existing versioned release pages was changed with the restyle (Manrope → Inter), the only change to them.

### The format, wherever tournaments are listed

- **Tournament Setup's tournaments list** has a **Format** column (after Date), **the Load tournament dialog** a Format line, and **Analytics' Dashboard** a Format column in Latest tournaments (wide screens, as the Register's). Names as the Register already had them: Double elim., Single elim., Cup & Plate, Round robin, Swiss. A tournament not yet drawn shows "—" in the list and "Not drawn yet" in the dialog: the format is set by the draw, and an absent format would otherwise read as double elimination. Requested by the maintainer.
- **The draw dialog** named Cup and Plate "Single Elimination" (in its title and Format line; only the size, "16 + Plate of 8", told them apart); it now says Cup and Plate.
- **One name per format:** each entry in `TOURNAMENT_FORMATS` has a `short` name, read through `formatShortName(format, plate)` (results-config.js); the Register's Format column and a tournament's facts in Analytics use it instead of their own spelled-out copies. The Server tab of the list is unchanged (the server's list has no format).
- Tested in the browser: the list (Swiss, Round robin, Single elim., Cup & Plate, "—" for undrawn), the Load dialog (Cup & Plate, Not drawn yet), the draw dialog (Cup and Plate with the Plate picked, Single Elimination without), the Dashboard.
- Files changed: `js/results-config.js`, `js/tournament-management.js` (`savedFormatName()`), `js/newton-history.js`, `js/clean-match-progression.js` (`showBracketConfirmation()`), `tournament.html`, `css/setup-page.css`, `js/dynamic-help-system.js`.

### Design System page: the new design; Architecture page: up to date

- **The Design System page** documented the old design (browns, oranges and teal, Manrope, the old landing page's cards). Rebuilt to document the new one, still drawn with the site's own stylesheets (it now loads `css/home.css` as well as `css/landing.css`), so it shows the design as it is: the wordmark on ink with the dartboard; the palette (fourteen colours, each with its role); the type scale (Insignia display, section and card headings; Inter label, lead and body; Cascadia Code); buttons on ink and on paper; a format card, a trust card and the dark Get started card; a step of the night; the documentation components (contents, code, terminal, steps, table); the footer. `css/design-system.css` is rewritten to lay these out only. Swatches use classes, not inline styles (the server's `style-src 'self'`).
- **The Architecture page** still described the app before the formats: a single `MATCH_PROGRESSION` table, "4 to 32" participants, and storage keys that are not the real ones. Now: the two tables (`DE_MATCH_PROGRESSION`, `SE_MATCH_PROGRESSION`); a new "Every format, from the same tables" (qualifiers, Cup and Plate, the cups and Swiss's top four merged in by `getProgressionTable()`, group and Swiss rounds progressing no one); the real keys (`dartsTournaments`, `currentTournament`, `tournament_{id}_history`, `dartsConfig`); the limits (48 players with qualifiers, a 64-slot table needed beyond; Round Robin 3–32, Swiss 4–48). The approach it describes is unchanged.
- Tested in the browser: the Design System page at desktop width and 375 px.
- Files changed: `design-system.html`, `css/design-system.css`, `architecture.html`.

### The documentation and release pages: the landing page's look

- **Every page that shares `css/landing.css`** (user guide, Architecture, Docker quickstart, automatic backup, privacy, REST API, QR protocol, QR generator, licenses, the releases page and all 68 versioned release pages) now has the new landing page's look, with **no change to any page's content or markup**: the stylesheet is rewritten with the pages' own class names.
  - The back link at the top is a dark bar that stays at the top, the full name in Insignia.
  - Headings in Insignia, text in Inter, code in Cascadia Code (all three already in `fonts/`); Contents as a white card with a small red label; links in the dartboard red.
  - Code blocks and terminals on warm ink (the terminal's dots in the board's red, amber and green); tables and the Quick Start steps as white cards; inline code wraps on a phone instead of widening the page.
  - Release pages: the Download button is red, the page's main action.
  - The footer is a dark band, as on the landing page.
- `css/landing.css` loses the old landing page's sections (header, hero, formats, get started, story cards, showcase), now in `css/home.css`; it goes from 1435 to about 670 lines. The QR generator's own rules keep their layout in the new colours.
- The pages preloaded Manrope, which they no longer use; the preload is now Inter (77 pages; `tournament.html` still uses Manrope and is unchanged).
- Tested in the browser: the user guide, Docker quickstart, REST API, the releases page, QR generator and Design System at desktop width; twelve pages (two of them old release pages) at 375 px without sideways scrolling.
- Files changed: `css/landing.css`, the font preload in every page that uses it (`*.html`, `releases/*.html`).

### Landing page: a fresh design

- **A new landing page**, designed from scratch for visitors interested in the software (mockup `Docs/mockups/landing-redesign.html`, approved by the maintainer). Dark, warm and high-contrast, with the dartboard's red and green as the only colours, Insignia for the wordmark and every heading, Inter for text. From the top:
  - **A navigation bar** that stays at the top: the wordmark **NewTon DC Tournament Manager** (NewTon DC is the club; the software has the full name), How it works, Formats, Built to last, **Download**, and a red Launch button.
  - **The hero, in two columns:** "Run the whole darts night. *Offline.*", what it covers, **Launch Tournament Manager** and **Download** (the releases page), No account · No subscription · No cloud, and "Scoring at the board? Open the Chalker". On the right the bracket in a window frame with the Chalker over its corner, in front of a dartboard drawn in CSS (dark segments, a faint red and green doubles ring).
  - **"From the door to the podium.":** the screenshots as a numbered night, in the order it happens: doors open (Player Registration), the draw, on the boards (Match Controls), at the oche (Chalker), the final (Tournament complete), the morning after (Analytics).
  - **Pick Your Format** on dark, the pictograms recoloured for it, the lead line kept.
  - **"Built for the room, not the cloud.":** works offline, yours not theirs, never loses a result (How it's built), free and open source (GitHub).
  - **"Ready when you are.":** Try it now (Launch, the Chalker), Download (the latest release), Self-host (Docker quickstart); then User Guide, How it's built, Release notes, GitHub.
  - **The footer:** the links, "No popups? No cookies!" and the 42.
- Left out: the poster and the tagline "The Offline Authority in Darts" (its message is the headline's "Offline"); the story cards (their points are in the night and in Built to last); the qualifiers note.
- **Its own stylesheet, `css/home.css`:** `css/landing.css` is shared by the documentation and release pages (about 80), which keep it unchanged until they are restyled. No inline styles or scripts (the server's `style-src 'self'`); the lightbox is `js/lightbox.js` as before. The search tags carry over with the full name and the new message (title, description, Open Graph, Twitter, structured data; 3–48 players); the share image is still the poster. `landing-page.php` is the same page with its server parts (redirect, GitHub URL, base URL, canonical tag; the Chalker at `chalker/`).
- Tested in the browser: every local link, image and font loads; the lightbox opens and closes; desktop, 768 px, 390 px and 375 px wide without sideways scrolling.
- Files changed: `landing.html`, `landing-page.php`, `css/home.css` (new), `Docs/mockups/landing-redesign.html` (new), `llms.txt`.

### Landing page: See It in Action in the night's order

- The cards now follow a night: Bracket, Chalker, Player Registration, The Draw, **Match Controls** (moved from third, after the Chalker, to after The Draw), Analytics, Tournament Complete. The maintainer's order.
- Files changed: `landing.html`, `landing-page.php` (the same).

### Swiss's pictogram: the top four's semifinals

- The Swiss pictogram drew the last round's outer two matches straight into the final (the middle two connected to nothing) and a line running out of the final into nothing. Redrawn: three round columns (no lines: the next opponent comes from the table), a gap (the table picks the top four), then two semifinals bracketed into the final, as the finish is played. Spotted by the maintainer on the landing page.
- Files changed: `js/results-config.js` (Swiss's `pic`), `landing.html`, `landing-page.php` (the same copy).

### Landing page: Pick Your Format's lead line

- Under the heading, a lead line sets the feel instead of a note under the cards: **"Small night or full house, there's one for it."** (larger, "full house" in the accent). The note it replaces ("Above 32, qualifiers decide the last places, up to 48. Seeding from your own results keeps the best players apart.") went into detail the cards already give (their player ranges), and the Draw card on the same page already speaks of seeding. The maintainer's choice of the options discussed (a lead under the heading, rather than the line as the heading).
- Files changed: `landing.html`, `landing-page.php` (the same), `css/landing.css` (`.formats-lead` replaces `.formats-note`).

### Landing page: the format pictograms in Pick Your Format

- Each card in **Pick Your Format** now opens with its format's pictogram, the same SVG as on Match Controls' Pick a format cards, on a tinted band, larger (up to 168 px wide). The SVGs are copied as they are from `TOURNAMENT_FORMATS` (`pic`, without the fixed size) and recoloured in `landing.css` by their fills to the page's warm palette, the final in the orange accent; the cards get the page's hover border. Requested by the maintainer: the page looked a little bland, and showing off the formats matters.
- **Swiss's line** is now "Your results pick your opponent." (was "Same record, new opponent.", which said too much in too few words), on the landing page and the Swiss card in Pick a format.
- Files changed: `landing.html`, `landing-page.php` (the same), `css/landing.css`, `js/results-config.js` (Swiss's `line`), `Docs/mockups/swiss.html`, `Docs/PARKING-LOT.md`.

### Analytics: a fuller top 10 on the Dashboard

- **The Leaderboard's top 10** on the Dashboard had Played, 1st and Points only; it now also shows **W–L** (matches, after 1st), **Attendance** and **Achievements** (the points from taking part and from achievements; the rest of Points is placement points). Under the point mode and layers in use, as Points. The three new columns are for wide screens only (`an-wide-only`), as Latest tournaments' Format. Requested by the maintainer ("it looks kinda sparse").
- The split is computed in `_computePlayerRows()` from the same functions as Points (`calculateAchievementPoints()`, `calculatePoints()` without placement), so the parts can't disagree with the total.
- Tested in the browser: attendance 5 + 1st 15 = 20, the layout at 1450 px wide.
- Files changed: `js/newton-history.js`.

## **v5.4.3** — Swiss Precision (2026-10-10)

### Landing page: the draw's new screenshot and copy, and Swiss in Pick Your Format

- **The draw card** in See It in Action, with the maintainer's new screenshots of Pick a format: labelled **The Draw** (was Shuffle & Draw), still "Pick a Format. Draw. Play.", and a text that names no formats, so new ones don't need it changed: "A card for every format, each showing what it means for tonight's players. Pick one and draw. Seeding from your own results keeps the best players apart; otherwise it's a fair random draw." The alt text likewise.
- **Pick Your Format** gets a fifth card, **Swiss** ("Same record, new opponent."), wrapping 3 + 2 as designed; Round Robin's says "played once or twice". The feature list and keywords name Cup and Plate and Swiss.
- Files changed: `landing.html`, `landing-page.php` (the same), `Screenshots/th-tournament-setup.jpg`, `Screenshots/tournament-setup.png` (the maintainer's; committed with `e417384`).

### Match Controls: lanes keep their place

- The lanes board's top line listed only the free lanes, so the row changed as matches started and finished, and a quick click could land on the wrong lane. Now it lists **every lane in use, in order** (labelled Lanes): a free lane starts Next up there, as before; a busy lane stays in its place, dimmed and not clickable, its tooltip naming the match on it ("R2-1 is being played on lane 1"). One helper for both lane boards (`_mcLaneChips()`), the brackets' and Round Robin's. Requested by the maintainer after picking the wrong lane.
- Files changed: `js/bracket-rendering.js`, `css/match-controls.css` (`.mc-lanechip.mc-busy`).

### A new tournament format: Swiss

- **Swiss** (Docs/SWISS.md; mockup `Docs/mockups/swiss.html`): a fixed number of rounds, nobody knocked out. Each round pairs players with the same record who haven't met (Monrad: the table 1st v 2nd, 3rd v 4th, skipping rematches, backtracking when a skip leaves no pairing; the fewest rematches only if none is possible). Round 1 at random, or with seeding ticked the ranked players top half against bottom half. An odd number gives one bye a round (a win, no legs) to the lowest-placed player who hasn't had one. The table: wins, opponents' wins (Buchholz), leg difference, legs won, draw order. 4 to 48 players.
- **Rounds** (by players: 2 for 4, 3 for 5–8, 4 for 9–16, 5 for 17–32, 6 for 33–48; or a fixed number, never more than players − 1) and **Finish** (**Semifinals and final** for the top four, 1st v 4th and 2nd v 3rd with a bronze final, the default; or **The table decides**): chosen on the Swiss card at the draw, starting from Global Settings → Swiss. Placings: the top four from the knockout, everyone else from the table in the shared places. **Match lengths of its own** (Swiss: rounds, semifinal, bronze final, final; 3, 3, 5, 5). Referees: suggestions only.
- **Rounds draw themselves:** the last result of a round draws the next (a `DRAW_SWISS_ROUND` transaction), and after the last round the top four (`DRAW_SWISS_KNOCKOUT`). Undoing a result of the round just finished takes that draw back (its matches and transaction, shown in the undo dialog) as long as none of its matches has started; once one has, the earlier rounds are locked.
- **The three foundations, additions only:** Swiss rounds are in no progression table (like group matches); the top four is `SE_MATCH_PROGRESSION[4]` with its IDs renamed (`K-SF1`, `K-SF2`, `K-B`, `K-F`) returned by `getProgressionTable()`; results are ordinary `COMPLETE_MATCH` transactions.
- **Where it shows:** a Swiss card in Pick a format (a pictogram of rounds into a final; "Tonight: 4 rounds, then the top 4"; matches tonight); Match Controls' queue ("Round 3 of 4", "Top four") and the table in the right column (won–lost, opponents' wins, leg difference, the top four marked, the round's bye); the bracket page with each round as a column of its matches (byes under their round, "Drawn when round 2 is played"), then the top four with lines; a Swiss panel and Swiss match lengths in Global Settings; Analytics names it Swiss.
- **Tested in the browser:** 9 players, 4 rounds and the top four played to the end (each round drawn as the last result came in, no rematches, four different byes, 1st v 4th and 2nd v 3rd, placings 1–4 from the knockout and the rest from the table in shared places); 8 players: undoing a round 1 result took round 2 back, re-entering it drew round 2 again, and starting a round 2 match locked round 1; the Match Controls and bracket views. Found in the maintainer's test: the bracket view only counted itself active for a field size with a double elimination table (8, 16, 32), so 12 players showed "No bracket generated yet"; `isActive()` now accepts Swiss at any size, as Round Robin. The selection bar also named Swiss matches as backside rounds; it uses `Swiss.roundName()`. **Selecting a Swiss match lights up both players' matches across the rounds** (there are no lines between Swiss rounds: the next opponent comes from the table), and the layout keeps room for the top four from the start, so Fit all takes it in before it's drawn.
- Files changed: `js/swiss.js` (new), `js/clean-match-progression.js` (`drawSwiss()`, `drawSwissRound()`, `drawSwissKnockout()`, `swissAfterResult()`, `getProgressionTable()`, completion, rankings, the draw and winner dialogs), `js/bracket-rendering.js` (Pick a format, the queue, the table, undo: `takeBackSwissStage()`, the lock), `js/bracket-view.js` (`layoutSwiss()`), `js/results-config.js` (the format, settings, match lengths), `js/config-page.js`, `js/seeding.js`, `js/main.js`, `js/tournament-management.js` (save, export, load, reset), `js/newton-history.js`, `tournament.html`, `css/match-controls.css`, `js/dynamic-help-system.js`, `userguide.html`, `Docs/SWISS.md`, `Docs/PARKING-LOT.md`.

### Round Robin: with Top half, the fewest groups, odd or even

- The groups were always an even number (the fewest even number that fits Largest group), which makes sense with **Top two**: the group winners and runners-up pair off cleanly in the A cup. With **Top half** (the default) the cups are split from one ranking across the groups, so the even number only cost matches: 12 players drew 4 groups of 3 (12 group matches, 2 each) instead of 3 groups of 4 (18, 3 each), with the same cups of 6 and 6. Now the even number applies with Top two only; with Top half the draw makes the fewest groups that fit (9 players: 3 groups of 3; 10: 3, 3, 4; 20: 5 groups of 4). Tested: 12 players with Top half drew 3 groups of 4, played to the cups (6 and 6).
- Files changed: `js/groups.js` (`groupCount()`), `tournament.html` (Structure and Largest group texts), `js/dynamic-help-system.js`, `Docs/GROUPS-AND-CUPS.md`.

### Round Robin: a double round robin for one group

- **Play each other: Once / Twice** (Round Robin, one group): Twice is a double round robin. The draw makes the one group's schedule twice: the whole first round robin, then the return round in the same order with player 1 and player 2 swapped and the same planned referees. Match numbers continue (4 players: A-1 to A-6, then A-7 to A-12), the return matches are marked (`returnRound`) and named "Round robin · return round", and Match Controls' queue says "Return round". Both meetings count in the table, head-to-head included; the table decides the placings, as in one group.
- **At the draw** it's an option on the Round Robin card when Structure is One group ("Tonight: One group of 4, twice"; matches tonight and per player doubled), for that draw only; **Global Settings → Round Robin → Play each other** decides how it starts (shown for one group; **Once** by default, `config.roundRobin.meetings`, absent = 1). 3 to 8 players, as one group. The tournament keeps it (`groups.settings.meetings`) and its format reads "Round robin, one group, twice".
- **Tested in the browser:** 4 players, Twice at the draw (Global Settings still Once): 12 matches, A-7 the return of A-1 with the players swapped, played to the end with all 4 placed.
- Files changed: `js/groups.js` (`meetings` in the settings and the draw choice, the round and format names), `js/clean-match-progression.js` (`drawGroups()`), `js/bracket-rendering.js` (the Round Robin card's option and estimates, the queue's Return round), `js/results-config.js`, `js/config-page.js`, `tournament.html`, `js/dynamic-help-system.js`, `userguide.html`, `Docs/GROUPS-AND-CUPS.md`, `Docs/PARKING-LOT.md`.

### Match Controls before the draw: pick a format, then draw

- **Pick a format** replaces Shuffle & Draw's stack of buttons and moves into the main column, under Players: a card for every format (Double Elimination, Single Elimination, Cup and Plate, Round Robin), each with its line and what it means for tonight's paid players ("16-player bracket · 4 byes", "Cup of 16 · Plate of 8", "4 groups of 3"). The picked card opens its description, a few bests, three facts (player range, **roughly how many matches tonight**, matches per player) and its options; **one Draw button** draws it ("Draw Cup and Plate →"), with a summary beside it. It opens on the **format of the last tournament drawn in this browser** (if it fits tonight), else the first offered one that fits.
- **Formats not offered** (Global Settings → Formats to offer) are still shown, greyed out and locked: "Not offered: Global Settings → Formats to offer". A format that doesn't fit tonight's field can still be picked (its options may make it fit) and says why on the card and the Draw button.
- **Cup and Plate is its own format**: a card at the draw and an entry in Formats to offer, drawn as single elimination with a Plate (`TOURNAMENT_FORMATS` entry `CP`: `draw: 'SE'`, `plate: true`). The Play a Plate switch on single elimination's card and the Offer Play a Plate setting are gone; a config saved with Offer Play a Plate off starts with Cup and Plate unticked (`loadConfiguration()`). Setup and the finished view name it Cup and Plate.
- **Round Robin's Structure and To the A cup can be chosen at the draw**, for that draw only (`Groups.setDrawChoice()`); Global Settings decide how they start and stay as they are. The tournament records what it was drawn with, as before.
- **Settings for this tournament follow the picked format** (its match lengths: double or single elimination's, the Plate's, Round Robin's group and cup lengths); it always showed double elimination's. **Seeding** applies to every format and its panel follows the picked format; with seeding off in Global Settings, the panel says the draw is random.
- **A pictogram on each card**, in the style of Global Settings' Finals position pictures (grey lines and boxes, the final dark; 96×44): Double Elimination as the real bracket with the finals in the middle (frontside left into the grand final, backside right, lighter, into the backside final below it), Single Elimination as a plain tree, Cup and Plate as the Cup and a lighter half-size Plate back to back with the finals facing, Round Robin as two group tables feeding an A and a B cup, each a small knockout. The picked card's final turns orange; a locked card fades it.
- The formats list (`TOURNAMENT_FORMATS`) carries each card's text (`line`, `about`, `bests`) and its pictogram (`pic`), so a new format brings its own description and picture. Mockup: `Docs/mockups/match-controls-setup.html`.
- **Tested in the browser:** 12 players; the default pick (the last tournament's format); Round Robin switched to one group (the card and the button say "At most 8 players in one group") and back; Round Robin drawn with Top two for this draw while Global Settings keep Top half; a saved config with Offer Play a Plate off (Cup and Plate locked, with the reason); drawing Cup and Plate (a Plate of 8) and then plain single elimination (no Plate).
- Files changed: `js/bracket-rendering.js` (`_mcSetupHTML()` and its helpers, the finished view's format name), `js/results-config.js` (`TOURNAMENT_FORMATS`, the Offer Play a Plate fold-in), `js/groups.js` (`setDrawChoice()`), `js/plate.js` (`offered()`), `js/seeding.js` (`html(formatId)`), `js/tournament-management.js` (Setup's format name), `tournament.html`, `css/match-controls.css`, `js/dynamic-help-system.js`, `userguide.html`, `Docs/CUP-AND-PLATE.md`, `Docs/mockups/match-controls-setup.html`.

### GitHub Actions: off Node.js 20

- Both Docker workflows used actions targeting Node.js 20, which GitHub has deprecated (each build warned that they were forced onto Node.js 24). Moved to the current majors, all on Node.js 24: `actions/checkout@v7`, `docker/setup-qemu-action@v4`, `docker/setup-buildx-action@v4`, `docker/login-action@v4`, `docker/metadata-action@v6`, `docker/build-push-action@v7`. The workflows only use inputs that are unchanged in these versions (the removed ones were deprecated inputs and environment variables they never used). Build Push v6+ adds a build summary to each run's page and a build record file to the run.
- **The image digest is printed again:** the GitHub Container Registry workflow's last step reads the digest from a step called `build`, which didn't exist, so it always printed empty; the build step now has `id: build`.
- Files changed: `.github/workflows/docker-build.yml`, `.github/workflows/docker-hub-publish.yml`, `Docs/PARKING-LOT.md`.

### Release

- Version 5.4.3, "Swiss Precision": Swiss, Pick a format with pictograms (Cup and Plate as its own format), the double round robin, Round Robin's fewer groups with Top half, the lanes row keeping its place, and the landing page. The first release built with the GitHub Actions on Node.js 24 (to confirm on this release's Docker build). The Chalker is unchanged; its version and caches are bumped with the app's (`CHALKER_VERSION`, `chalker.js?v=29`, service worker cache `chalker-v126`).
- Files changed: `js/main.js` (`APP_VERSION` → `5.4.3`), `chalker/js/chalker.js` (`CHALKER_VERSION` → `5.4.3`), `chalker/index.html`, `chalker/sw.js`, `llms.txt` (Swiss, Pick a format, the double round robin, Cup and Plate's own card, the odd group count; Swiss off the do-not-invent list, the parked formats on it), `sitemap.xml`, `releases/index.html`, `releases/v5.4.3.html`, `Docs/ReleaseNotes/RELEASE-NOTES-v5.4.3.md`. The help was reviewed with each change.

## **v5.4.2** — All the Dishes Rattle in the Cupboards (2026-10-09)

### Landing page: Pick Your Format, and Chalk. Send. Done.

- **"Pick Your Format."**, a new section between the hero's Launch/Open buttons and Get Started: a card for each format (Double Elimination, Single Elimination, Cup and Plate, Round Robin) with a short line and its player range, and a note on qualifiers and seeding. The cards sit in centred rows that wrap, so new formats fit as they arrive: up to 4 across; 5 or 6 go 3 to a row, 7 or more 4 to a row again (`:has()`; older browsers wrap 4 + 1, still centred); 2 + 2 on a tablet, one per row on a phone.
- **"Chalk. Send. Done."** replaces "Scan. Score. Done.": matches go out and results come back by QR code or over your own network.
- Files changed: `landing.html`, `landing-page.php` (the same hero and section), `css/landing.css` (`.formats`, `.format-cards`, `.format-card`).

### Reset: never a completed tournament, and an unfinished one leaves the Analytics register clean

- **A completed tournament can't be reset** (maintainer, 2026-10-09). Its results are final, and Reset threw them all away; the link is gone from Tournament Setup for a completed tournament, and `showResetTournamentModal()` and `confirmReset()` refuse one anyway. To correct a result after completion: Developer Console → Toggle Read-Only, then undo the match.
- **Reset clears an unfinished tournament's Analytics record.** The register keeps a hidden "live" record of every match as it is played, and Reset left it alone, so after a reset and a new draw, a match that became a walkover (never recorded) kept its old result: two matches from an earlier draw, with players no longer in the tournament, showed up in Analytics when the tournament completed. Reset now deletes the tournament's record and matches from the register (`NewtonDB.deleteTournament()`) when the record isn't final; a final record is never touched. Undo already cleaned up after itself; Reset didn't, since the register was added.
- Files changed: `js/tournament-management.js` (`renderSetupCurrent()`, `showResetTournamentModal()`, `confirmReset()`), `js/dynamic-help-system.js`.

### Cup and Plate in Analytics: "Cup & Plate"

- Analytics named a Cup and Plate night "Single elim.", since the register only stores the format id (`SE`). The tournament record now also keeps `plate` (when finalized, and when imported into the register), and Analytics says **Cup & Plate** in the tournament list, the tournament's facts and the import dialog. Plate matches were always recorded like any other (their achievements, matches and legs count); walkovers, as in every format, are not.
- Files changed: `js/clean-match-progression.js` (finalize), `js/newton-db.js` (`backfillTournament()`), `js/newton-history.js`.

### Cup and Plate: single elimination where the round 1 losers play a second knockout

- **Play a Plate**, a switch on single elimination's card in Shuffle & Draw (from 5 players: a Cup of 8 or more). It always starts off; **Offer Play a Plate** in Global Settings (on by default, `config.ui.offerPlate`) leaves it out of the draw for clubs that never play one. Design and decisions: `Docs/CUP-AND-PLATE.md`; mockup `Docs/mockups/cup-and-plate.html`.
- **The Plate** is a single elimination of half the Cup's size (8 → 4, 16 → 8, 32 → 16) with its own bronze final, for the Cup's round 1 losers at fixed places, as round 1 losers drop to the backside: the losers of round 1 match 1 and 2 meet in P-QF1 (or P-SF1, P-R1-1), and so on, so a Plate match can start as soon as its two round 1 matches are played. A bye's Plate place is a walkover (auto-advanced as on the backside); a qualifier loser is not qualified and never goes to the Plate. Match lengths as single elimination's, by the Plate's own rounds. Bronze finals are always played, in the Cup and the Plate (a switch was considered and dropped: it would change the points and touch how every single elimination tournament ends).
- **The three foundations, additions only:** `getProgressionTable()` merges the Plate in after any qualifiers: each Cup round 1 entry gains a loser path into the Plate, and the Plate's own table is `SE_MATCH_PROGRESSION[size]` with its IDs renamed by `cupMatchId('P', …)`. The tables themselves are unchanged; advancing, walkovers, undo (a round 1 result can be undone until its Plate match starts) and the bracket's "Loser FS-1-3" work as they are.
- **The end:** with a Plate the tournament completes when every match is played (the Cup's final and bronze final and the Plate's), whichever comes last; 1st and 2nd come from the Cup's final. **Placings:** the Plate orders the round 1 losers in the shared places, like the B cup (8 players: its finalists 5th–6th, its bronze pair 7th–8th; 16: its semifinalists 9th–12th, its first round's losers 13th–16th); its final and bronze final decide the Plate, and the finished view names the **Plate winner**.
- **Bracket view: back to back** (`layoutPlate()`): the Cup as single elimination with the finals on the right, the Plate mirrored from the right, each of its rounds level with the Cup's next round, so the two finals face each other in the middle, with the club name between them and nothing joining them. "Cup ▶" and "◀ Plate", the Plate shaded like the backside, its bronze final tied to its final as the Cup's is. Round 1 losers' lines run round under the bracket into the Plate (on selection). Always back to back with a Plate; the Finals toggle is hidden. Qualifiers stay outside the Cup's round 1.
- **Match Controls:** "Cup · Round 1", "Plate · Quarterfinal" in one queue, each Plate round after the Cup's round of the same number. Winner dialog and match history: "moves to P-QF1", "wins the Plate". The draw dialog says "16 + Plate of 8".
- **Tested in the browser:** 16 players to the end (the Cup final played with 8 Plate matches left, and the tournament waited for the Plate; 1st and 2nd from the Cup; placings 1–4, 5th–8th, 9th–12th, 13th–16th; Plate winner on the finished view); 12 players (4 byes, their Plate places walkovers); undo of a round 1 result (its loser out of the Plate again); 8 players (a Plate of 4); 4 players (no Plate even with the switch on); 40 players with qualifiers and a Plate of 16; save and reload; the switch on the draw card.
- Files changed: `js/plate.js` (new), `js/clean-match-progression.js` (`getProgressionTable()`, the draw, completion, `calculateAllRankings()`, the draw dialog, the winner dialog), `js/bracket-view.js` (`layoutPlate()`, labels, lines, the finals toggle), `js/bracket-rendering.js` (the switch, queue, round names and order, the Plate winner), `js/groups.js` (`placeTier` exported), `js/main.js`, `js/tournament-management.js` (save, export, load, reset), `js/results-config.js` (`offerPlate`), `tournament.html`, `css/match-controls.css`, `js/dynamic-help-system.js`, `userguide.html`, `Docs/CUP-AND-PLATE.md`, `Docs/PARKING-LOT.md`.

### Release

- Version 5.4.2, "All the Dishes Rattle in the Cupboards": Cup and Plate, Reset only for unfinished tournaments (clearing their Analytics record), Cup & Plate in Analytics, and the landing page's formats section. The Chalker is unchanged; its version and caches are bumped with the app's (`CHALKER_VERSION`, `chalker.js?v=28`, service worker cache `chalker-v125`).
- Files changed: `js/main.js` (`APP_VERSION` → `5.4.2`), `chalker/js/chalker.js` (`CHALKER_VERSION` → `5.4.2`), `chalker/index.html`, `chalker/sw.js`, `llms.txt` (Cup and Plate; off the do-not-invent list, with optional bronze finals on it; a completed tournament can't be reset), `sitemap.xml`, `releases/index.html`, `releases/v5.4.2.html`, `Docs/ReleaseNotes/RELEASE-NOTES-v5.4.2.md`. The help was reviewed with the Cup and Plate work.

## **v5.4.1** — Under Pressure (2026-10-09)

### Round Robin: without a B cup, the A cup takes the top two of each group

- Top half is there to keep the B cup from being tiny, so it now only applies when the B cup is played. With **Play the B cup** off at Draw the cups, the A cup takes the group winners and runners-up whatever To the A cup says, and the rest are placed after it by their group results. Before, Top half without a B cup shrank the A cup to half the field (12 players in 4 groups of 3: an A cup of 6 with 2 byes, instead of all 8 winners and runners-up; the maintainer: no top-two player should miss the knockout when there is only one cup).
- Draw the cups shows it as the switch is flipped (the A field changes, and the note says why), and the draw uses the same fields: `Groups.cupFields(playB)`, called with the switch by `drawCups()` and `_mcDrawCupsHTML()`. Tested: 12 players, Top half: 6/6 with the B cup, 8 and 4 (not played) without; drawn and played to the end, 9th–12th for the thirds.
- Files changed: `js/groups.js` (`cupFields()`), `js/clean-match-progression.js` (`drawCups()`), `js/bracket-rendering.js` (`_mcDrawCupsHTML()`), `tournament.html` (To the A cup), `js/dynamic-help-system.js`, `Docs/GROUPS-AND-CUPS.md`.

### Tournament Setup: the next step's two buttons are the same size

- The dark main button in the Next step bar was 40px with 15px text, the button beside it the standard 36px with 14px, so the pair didn't line up. Both are now 40px with 15px text; the dark colour alone marks the main step (also in the Completed state, where neither is dark).
- Files changed: `css/setup-page.css` (`.st-next .st-btn`).

### Match Controls: a live match without a lane has a plain amber border

- A live tile without a lane had a grey border with a thick amber stripe inside its top edge, which curved into a "lip" at the rounded corners. The stripe is gone; the tile has a 2px amber border all round (the border plus a 1px inset shadow, so nothing inside moves), and the orange "No lane" label carries the warning.
- Files changed: `css/match-controls.css` (`.mc-lane.mc-nolane`).

### Qualifiers: double and single elimination for 33 to 48 players

- **Up to 48 players** in double and single elimination. The bracket stays a 32-player bracket; the players above 32 make it in through **qualifiers**, a round 0 before round 1: one qualifier for each player above 32 (40 players: 8 qualifiers, 24 straight in; 48: 16, one in every round 1 match). Requested by other users of the software. Design and decisions: `Docs/QUALIFIERS.md`; mockup `Docs/mockups/qualifiers.html`. 64 players is a possible future option.
- **The draw** reuses the bye layout as it is: the straight-in players are drawn into 32 places by `createOptimizedBracketV2()` (random or seeded), which leaves one gap per round 1 match where byes would go (opposite the best seeds first), and each gap becomes the place of a qualifier's winner. Who plays a qualifier: drawn at random, never a seed; with seeding **All**, the lowest-ranked (the unranked first, then up from the bottom). Qualifiers are numbered Q1… from the top of the bracket, numbered before the bracket's matches, and played at the format's regular rounds length.
- **The three foundations, additions only:** `getProgressionTable()` merges the qualifier entries (Qn → its round 1 place, no loser path) in front of the 32-player table, which is unchanged, so advancing, undo (a qualifier can be undone until its round 1 match starts) and the bracket's "Winner Qn" work as they are. A qualifier result is an ordinary `COMPLETE_MATCH`.
- **A qualifier only decides who gets to play:** the loser is not qualified, placed shared **33rd–48th** and marked (`tournament.notQualified`); nothing in a qualifier counts, for the winner either: score only in the winner dialog and from the Chalker (no achievements, no raw legs), never in the register, and the tournament's leg counts skip it. The tournament result still goes to Analytics, so a non-qualified player counts as attending.
- **Also for qualifier losers** (Global Settings → Points, under Taking part; on by default): whether a player who loses a qualifier gets the Taking part points. `calculatePoints()` (the one points formula) takes it into account; Analytics reads `notQualified` from the register, and Custom point mode applies the current setting to earlier tournaments too.
- **Bracket view:** a Qualifiers column one step outward from round 1, each qualifier level with the match it feeds (both outer edges with single elimination's finals in the middle). **Double elimination with qualifiers is always drawn with the finals in the middle**: with them on the right the backside sits straight beside round 1, where the qualifiers go; the Finals toggle shows it.
- **Match Controls:** Qualifiers first in the queue (each unblocks a round 1 match) and in Next up; qualifier losers show in the referee list's losers, free for referee duty; Shuffle & Draw says "Draw 32 + 8 qualifiers"; the add-player row stays until 48. Player Registration says how many qualifiers decide the last places. Match history says "not qualified (33rd)".
- **Tested in the browser:** 40-player double elimination and 44- and 48-player single elimination, both finals positions; who plays the qualifiers in each seeding mode; undo (blocked once the round 1 match is live, "Winner Q1" back after); a whole 40-player double elimination played to the end (placings 1st to 33rd, the register final with 40 attending, 8 not qualified and no qualifier matches); Taking part on and off; save and reload.
- **The web pages say 48:** the landing pages (keywords, the feature list, which now also names Round Robin and Qualifiers, and the Shuffle & Draw card: "up to 48 with qualifiers"), the `tournament.html` description, README (a Qualifiers line; live rankings to 48th) and `llms.txt` (DE and SE 4–48, a Qualifiers line, Largest group in the Round Robin line, and "more than 48 players" in place of "more than 32 players or qualifiers" on the do-not-invent list). The in-app help and the user guide already did.
- Files changed: `js/qualifiers.js` (new), `js/clean-match-progression.js` (`getProgressionTable()`, `calculateBracketSize()`, the draw, the confirmation dialog, `calculateAllRankings()`, the register skip, the winner dialog), `js/bracket-view.js` (the Qualifiers column, the finals rule, the toggle), `js/bracket-rendering.js` (queue, round names, Shuffle & Draw), `js/results-config.js` (limits, 33rd, the setting, `calculatePoints()`, leg counts), `js/newton-history.js`, `js/newton-db.js`, `js/qr-bridge.js`, `js/main.js`, `js/player-management.js`, `js/tournament-management.js` (save, export, load, reset), `tournament.html`, `css/styles.css`, `js/dynamic-help-system.js`, `userguide.html`, `landing.html`, `landing-page.php`, `README.md`, `llms.txt`, `Docs/QUALIFIERS.md`, `Docs/PARKING-LOT.md`.

### Round Robin: Largest group and the cups' own match lengths

- **Largest group** (Global Settings → Round Robin): 4 (the default, as before), 5 or 6. The draw makes the smallest even number of groups that keeps every group at that size or less, so a larger limit means fewer, longer groups: 10 players are 3, 3, 2, 2 at 4, and two groups of 5 at 5 or 6 (no more A cup of 8 and B cup of 2 with top two); 20 players are four groups of 5. Groups of 5 and 6 use the circle-method schedule One group already had (in a group of 5 the player sitting the round out referees). The cup fields now take every group place, not just 1st–4th (`cupFields()`), so 5th and 6th go to the B cup with top two, or into the ranking with top half; Draw the cups names them "5th", "6th". At 6, top two with 25 or more players can make a B cup of more than 16, drawn in the 32-player single elimination table (tested: 30 players, A cup 12 in 16, B cup 18 in 32). Each tournament keeps the largest group it was drawn with (`tournament.groups.settings.maxGroup`; absent = 4).
- **The cups get their own match lengths** (Global Settings → Match length → Groups and cups): **Cup rounds** (every round before the semifinals), **Cup semifinal**, **Cup bronze final** and **Cup final**, the same for the A and the B cup, taken when the cups are drawn. Defaults 3, 3, 5, 5, as single elimination. The cups used the single elimination lengths before, so a saved config without the new fields keeps them (cup rounds from the SE quarterfinal, the rest from the SE semifinal, bronze final and final); a normal single elimination night and the cups can now differ (e.g. a Bo7 cup final).
- Both are in the Reset all config preview, with their Global Settings names.
- Files changed: `js/results-config.js` (defaults, the old-config fallback, form load/save, Reset to defaults, `CONFIG_LABELS`), `js/clean-match-progression.js` (`drawCups()` lengths; `roundRobinSchedule()` comment), `js/groups.js` (`maxGroup` in the settings and snapshot, `groupCount()`, `cupFields()`), `js/bracket-rendering.js` (place names at Draw the cups), `tournament.html` (Largest group, four cup steppers), `js/dynamic-help-system.js`, `userguide.html`, `Docs/GROUPS-AND-CUPS.md`, `Docs/PARKING-LOT.md`.

### Release

- Version 5.4.1, "Under Pressure": qualifiers for 33 to 48 players in double and single elimination, and three Round Robin improvements (Largest group, the cups' own match lengths, the top two of each group without a B cup). The Chalker is unchanged; its version and caches are bumped with the app's (`CHALKER_VERSION`, `chalker.js?v=27`, service worker cache `chalker-v124`).
- Files changed: `js/main.js` (`APP_VERSION` → `5.4.1`), `chalker/js/chalker.js` (`CHALKER_VERSION` → `5.4.1`), `chalker/index.html`, `chalker/sw.js`, `sitemap.xml`, `releases/index.html`, `releases/v5.4.1.html`, `Docs/ReleaseNotes/RELEASE-NOTES-v5.4.1.md`. `llms.txt` (reviewed: DE/SE 4–48, Qualifiers and Largest group came with the qualifier work; now also the A cup's top two without a B cup and the cups' own match lengths), and the help (reviewed with the same work).

## **v5.4.0** — Just Around the Corner (2026-10-08)

### The bracket always shows the current tournament

- **The old tournament's groups stayed on the bracket page.** With a Round Robin in its group stage, creating a new tournament and opening the bracket showed the old tournament's group cards. The cards are drawn in their own panel, which `clearBracket()` doesn't reach, and showing the Bracket tab didn't redraw it. Creating, resetting, loading or importing a tournament without a draw never redrew the bracket. Now the bracket is redrawn whenever the Bracket tab shows (`renderBracket()` in `showBracketView()`), so it always shows the current tournament, by whatever path it became current. The same tournament redrawn keeps its zoom, selection and Follow.
- Files changed: `js/bracket-rendering.js` (`showBracketView()`).

### Landing page: new screenshots and copy

- **See It in Action has new screenshots and new copy throughout**, matching the app as it is now: Bracket (every round on one page, the three formats), Chalker App (**Scan It or Send It.**: QR and network handover side by side), Match Controls, Player Registration (who's here, who's paid; the draw waits for everyone), **Shuffle & Draw** (formats, seeding and fair byes; it takes over the Fair Draw card's message), **Analytics** (new; replaces Fair Draw), and Tournament Complete (the podium for the club chat).
- **Lighter thumbnails:** 1000px JPGs, about 430 KB together instead of 1.3 MB; the full-size images stay PNG for the lightbox.
- **Old screenshots removed** (the earlier gallery's images and some unused ones); the poster artwork moves to `Screenshots/posters/`; `backup.png` stays (Automatic Backup uses it). The commented-out Quick Start image is gone from both landing pages.
- Files changed: `landing.html`, `landing-page.php` (the same gallery for the Docker landing page), `Screenshots/`.

### Bracket page header: a frame at both ends, tools in line

- The tournament name and date get the clock's divider, mirrored (a line to their right), so the header is framed at both ends.
- The bracket tools (Finals, Fit all, zoom) were pinned to the top of the header and are smaller than the view buttons, so their tops lined up but their centres didn't. They now get the top row's height and are centred in it, on the same line as Bracket, Match Controls and Leaderboard.
- Files changed: `css/bracket-view.css`.

### Match Controls keeps the page header up to date

- The header's counts (players, live, ready) were only filled in when the bracket was drawn, so adding, removing or marking players paid in Match Controls, or starting and finishing matches there, left them behind. Match Controls now refreshes the header each time it redraws (`BracketView.updateHeader()` in `showCommandCenterModal()`).
- Files changed: `js/bracket-rendering.js`.

### Match Controls: the free lanes and Next up come first

- The Free line (the free lanes and Next up) moved from under the live matches to straight under the Lanes heading, in every format. It used to move down the page as matches started; now it stays in the same place all night, and starting the next match is the first thing on the page.
- Files changed: `js/bracket-rendering.js` (the lanes panel in `_mcActiveHTML()` and `_mcGroupsHTML()`), `css/match-controls.css` (`.mc-free`: the divider below it).

### Round Robin: every group keeps its place in Up next

- A group with nothing left to start used to disappear from Up next, and a column whose groups were all finished only said "These groups are done.", without saying which. Now every group keeps its heading: a finished group says "All 3 played", in a lighter grey, with nothing under it; a group whose last matches are live keeps the normal colour (it isn't done) and says "2 of 3 played · 1 live". Any group with a live match says so in its heading. The groups stay in place all night, and what's done can be read at a glance (the results stay in the group tables on the right).
- Files changed: `js/bracket-rendering.js` (`_mcGroupsHTML()`), `css/match-controls.css` (`.mc-qround.mc-qdone`).

### Round Robin: level only when the group is finished

- Players were marked **level** (with ▲ to decide) while their group still had matches to play, often two players who hadn't met yet, whose match would settle it. Now `Groups.standings()` marks players level only once the group has played every match, so the tables on both pages, ▲ and the warning at Draw the cups follow from one place. After a finished group, two players can't be level (their match decides); only a three-way cycle with identical legs can, and ▲ appears for it at Draw the cups. With one group the tournament completes on the last match, so the group seed decides such a tie.
- Files changed: `js/groups.js` (`standings()`), `js/dynamic-help-system.js`, `Docs/GROUPS-AND-CUPS.md`, `Docs/PARKING-LOT.md`.

### New defaults in Global Settings

- **Round Robin:** Groups and cups, **Top half** to the A cup, Allow group rematches, Play the B cup (Top half is the new one; the A and B cups come out the same size).
- **Seeding: Available** (was Off): Shuffle & Draw offers seeding, unticked, so nothing changes unless the operator ticks it.
- **Chalker handover: None** (was QR code) for new installs and Reset to defaults. A config saved before the Handover setting existed has always meant QR code, so `loadConfiguration()` keeps it QR code (additive-only schema: an absent field keeps its old meaning); a config that has it keeps its choice.
- Settings already saved are unchanged; the defaults apply to new installs, Reset to defaults, and settings a saved config doesn't have yet (Round Robin, which is new; Seeding for a config from before v5.3.1).
- Files changed: `js/results-config.js` (`DEFAULT_CONFIG`, `loadConfiguration()`, the Round Robin apply/save fallbacks), `js/groups.js` (`configSettings()`), `js/dynamic-help-system.js`, `js/types.js`, `Docs/GROUPS-AND-CUPS.md`.

### Reset all config: brings the settings back, keeps the server connection

- **The server connection survives a reset.** Reset all config (Developer Console) and Reset to defaults used to set everything to `DEFAULT_CONFIG`, the server section too: the Analytics server's address and API key were wiped, and a new server ID was made on reload (so the Chalker's QR codes carried a new identity). Both now use `defaultConfigKeepingConnection()`, which keeps `remoteUrl`, `remoteApiKey`, `remoteVerified` and `serverId`; they can still be changed by hand in Global Settings. The reset is a way to bring the settings back to sensible values, not a factory reset.
- **The preview lists every setting that would change.** It was a hand-written list that had fallen behind (no single elimination or group match lengths, Game, Short leg, Require a lane, Hidden formats, New players are paid, Finals position, Chalker, Seeding, Round Robin, or server settings). `configChangesOnReset()` now walks `DEFAULT_CONFIG`, so a new setting is always included, and shows only what changes, by section, with the Global Settings names (`CONFIG_LABELS`; a setting without a name shows its key). Nothing to change says so.
- Files changed: `js/results-config.js` (`SERVER_CONNECTION_KEYS`, `defaultConfigKeepingConnection()`, `CONFIG_LABELS`, `configChangesOnReset()`, `resetConfigToDefaults()`), `js/analytics.js` (`commandResetAllConfig()`, `executeResetAllConfig()`).

### Round Robin: one group, Top half, and its own settings

- **The format is called Round Robin**, with its own panel in Global Settings → Tournaments while it is offered (review note 9): **Structure**, Groups and cups (6–32 players) or **One group** (3–8 players: everybody plays everybody, the table decides the placings, no cups); **To the A cup**, Top two of each group or **Top half** (everyone ranked across the groups and split into two cups of the same size, so 10 players play two cups of five instead of eight and two; note 2); **Play the B cup** on or off to start with. A tournament keeps the structure and cup entry it was drawn with (`tournament.groups.settings`, additive).
- **One group:** a fixed order for five to eight players from `roundRobinSchedule()` beside the group tables (circle method; every pair once; referee from the group, never twice in a row, duties even or within one), planned referees and waits as in the groups, placings from the table when the last match is played. Match Controls shows the next six matches and the table; the bracket page shows the one group (no Cups).
- **Group rematches in cup round 1** (a setting, from last night's list): **Allow** (the default, the mirror draw as it falls) or **Avoid**: each seed gets the nearest opponent from another group, as close to the mirror as possible (`Groups.avoidRematches()`); the Draw the cups step says so. Tested: 16 players, 2 rematches per draw with Allow, none with Avoid; 32 players none.
- **Play the B cup is a switch** in the Draw the cups bar, as in the mockup (note 3).
- The Shuffle & Draw card, the draw dialog, the Setup facts and Analytics follow the structure ("Draw one group of 6", "Round robin, one group").
- Files changed: `js/clean-match-progression.js` (`roundRobinSchedule()`, the limits in `generateCleanBracket()`, the dialog), `js/groups.js` (`configSettings()`, `settings()`, `isSingle()`, `limits()`, `formatName()`, one group in the draw, completion and placings, Top half in `cupFields()`), `js/results-config.js` (`roundRobin` defaults, apply/save, the registry name), `js/config-page.js`, `tournament.html`, `js/bracket-rendering.js`, `js/bracket-view.js`, `js/tournament-management.js`, `js/newton-history.js`, `css/match-controls.css`, `css/bracket-view.css`, `js/dynamic-help-system.js`, `Docs/GROUPS-AND-CUPS.md`.

### Groups and Cups: after the first review

- **Referees are a plan until the match is live** (review notes 1, 6): in this format a referee chosen for a match that hasn't started no longer blocks other matches, so swapping referees between two group matches can't lock them both. Start checks that a referee chosen beforehand is free.
- **Matches wait for their referee** (note 4): Match Controls holds a ready match while one of its players referees an earlier match in the group or cup first ("Ken referees A-QF1 first"), or while its planned referee isn't known yet ("its referee is the loser of A-QF1"), with Start disabled; choosing another referee releases it. The bracket and the group cards show it as Waits/Waiting. Next up only suggests matches that can start.
- **Plans never point at a walkover** (note 7): a two-player B cup's final has no planned referee (so it is Ready), and its empty bronze final reads "Not played".
- **Everyone is placed** (note 8): after the A and B cups' finals and bronze finals, the A cup's other losers (latest round first), then the B cup's, each round by group results, then anyone in no cup, on shared places (9th–12th, 13th–16th …). A B cup too small to fill 7th–8th leaves those places to the best A cup quarterfinal losers. Cup losers are now struck through in the bracket, like eliminated players in the other formats.
- **The Ready label and Bo chip on bracket cards were cut off** ("READ", in every format) since the Groups and Cups build: the group card's match row class `.bv-grow` had the same name as the card's spacer. Renamed to `.bv-gmatch`. The header's ready count leaves out matches that wait.
- Files changed: `js/groups.js` (`holdFor()`, `realCounts()`, `planCupReferees()`, `placements()`), `css/bracket-view.css`, `js/bracket-rendering.js` (live-only referee conflicts for this format, Match Controls rows), `js/clean-match-progression.js` (start check), `js/bracket-view.js`, `css/match-controls.css`, `js/dynamic-help-system.js`, `Docs/GROUPS-AND-CUPS.md`.

### A new tournament format: Round Robin (groups and cups)

- **Groups and Cups**, a third card under Shuffle & Draw (it can be hidden in Global Settings like the others): everybody plays everybody in groups, then an A cup and a B cup. Built for the weekly nights (15–32 players) and the December season final. Design: `Docs/GROUPS-AND-CUPS.md`; mockup: `Docs/mockups/group-night.html`.
- **The groups:** the smallest even number of groups that keeps every group at four or fewer (6–8 players: 2 groups, 9–16: 4, 17–24: 6, 25–32: 8). Players go in in snake order, by ranking when seeding is on (every ranked player; the unranked at random after them), otherwise at random. Each group plays in a fixed order with a planned referee from the group (group of 4: 1v4 r2, 2v3 r4, 2v4 r1, 1v3 r2, 3v4 r1, 1v2 r3; group of 3: each referees once; group of 2: no referee). Group matches have their own match length (Global Settings → Match length → Groups and cups, default Bo3).
- **The table:** wins, leg difference, legs won, then head-to-head (a mini-table between the players still level, so three-way ties too). Players level after that are marked **level**, and the operator decides with **▲** in Match Controls' group tables; untouched, the group seed decides.
- **Draw the cups:** when the last group match is played, Match Controls shows both seeded fields (group winners, then runners-up; the B cup: thirds, then fourths; ranked across groups per match by win rate, then leg difference, then legs won), a **Play the B cup** switch (on; the B cup needs two players) and **Draw the cups**. Each cup is the existing single elimination with bronze, seeded "All" with the existing `placeSeededPlayers()` (top seed v bottom seed, byes to the best seeds), always drawn with the final in the middle.
- **Placings:** A cup final 1st/2nd, bronze final 3rd/4th; B cup final pair 5th–6th, bronze pair 7th–8th; without a B cup, the A cup's quarterfinal losers 5th–8th by group results (best two 5th–6th). The tournament completes when the last cup final is played.
- **Referees:** planned and filled in when a match starts if the planned player is free; always changeable. Cups, round 1: bye winners first, then the players of the bottom matches, for the top half; the bottom half by the losers of the top half (QF1/QF2 refereed by QF4's players, QF3/QF4 by the losers of QF1/QF2). Later rounds: a loser from the round before; the final: the bronze final's loser. A player can no longer start a match while playing another one (only possible in a group stage).
- **Bracket page:** a **Groups | Cups** switch instead of Finals position. Groups: a card per group with its table (top two marked for the A cup) and its matches with referee and state; a match not yet played opens Match Controls, a played one has **Undo** while it can be undone. Cups: both cups, A above B, with lines, hover, selection, Follow and Undo as in any bracket.
- **Match Controls:** the group stage queue by group (each group's next two matches in their fixed order, with the planned referee chosen), Next up preferring a match whose players and referee are free, and the group tables on the right; then Draw the cups; then the A and B cups side by side, with **Undo the cup draw…**.
- **The three foundations, additions only:** `GROUP_SCHEDULES` beside the DE and SE tables; group matches are in no progression table (they move no one). The cups are `SE_MATCH_PROGRESSION[size]` with renamed IDs (`cupMatchId()`: `FS-2-1` → `A-SF1`; `A-QF1`, `A-B` bronze, `A-F` final, `A-R1-3` in a 16-player cup), joined by `cupsProgressionTable()`; `getProgressionTable()` returns that for this format. A new **`DRAW_CUPS`** transaction. Group matches are locked once the cups are drawn; the cup draw can be undone (`undoCupDraw()`) while no cup match has been started or has a result entered by hand or by the Chalker, which removes the cup matches, their transactions and the draw. Cup matches undo as single elimination does.
- **Stored data, additive:** `tournament.format: 'GROUPS'`, `tournament.groups`, `tournament.cups`, match `side: 'group'|'cup'`, `group`, `cup`, `seId`, `plannedReferee`, `config.legs.groupMatches`. Carried by save, load, import, export and the Analytics preview. `tournament.bracket` holds the group draw, so every "is it drawn?" check works unchanged.
- **Tested in the browser:** complete nights for 6, 7, 9, 10, 11, 13, 15, 16, 17, 18, 23, 25 and 32 players (with and without walkovers in the cups, without a B cup), the cup draw and its undo, undo in the groups and in the cups, a three-way tie and the operator's decision, reload, export and import; double and single elimination regression runs (8–32 players) complete as before.
- Files changed: `js/groups.js` (new), `js/clean-match-progression.js` (`GROUP_SCHEDULES`, `cupMatchId()`, `cupsProgressionTable()`, `getProgressionTable()`, `drawGroups()`, `drawCups()`, `afterDraw()`, completion and rankings for the format, the start checks), `js/bracket-rendering.js` (undo: `isGroupMatchLocked()`, `canUndoCupDraw()`, `undoCupDraw()`; the cup final's gate; Match Controls for the format), `js/bracket-view.js` (`layoutCups()`, the groups page, Groups | Cups), `js/results-config.js` (the format, `groupMatches`), `js/seeding.js` (`forGroups()`), `js/tournament-management.js`, `js/main.js`, `js/newton-history.js` (format labels), `js/dynamic-help-system.js`, `js/types.js`, `tournament.html`, `css/bracket-view.css`, `css/match-controls.css`, `Docs/GROUPS-AND-CUPS.md` (new).

### Undo: undone matches leave the Analytics register again

- **Since v5.1.6, every undo stopped at its last step** with an error (`rolledBackMatchIds.map is not a function`): the list of undone matches is a `Set`, which has no `map()`. The tournament itself was already saved by then, so undo looked fine, but the undone matches were never deleted from the match register, so Analytics could keep counting results that had been undone. Found while testing Groups and Cups; separate commit (`567c35f`) so it can go to `main` on its own.
- Files changed: `js/bracket-rendering.js` (`undoManualTransaction()`).

### Single elimination: finals in the middle

- **The Finals Right | Middle switch now works for single elimination.** In the middle, the bracket is drawn as two halves facing each other: the top half of round 1 from the left, the bottom half from the right, each down to its semifinal, and the final in the middle, level with the semifinals, with the bronze final under it (joined by a dashed line). It is the same single elimination with the same rules; only the drawing differs, so history, undo and everything else are untouched. One setting for both formats (Global Settings → Bracket, or the bracket header). This is the first step towards the season final's A and B cups.
- **The switch shows the right button pressed** for single elimination: it read the layout's name instead of the setting.
- **New pictures for Finals position** in Global Settings → Bracket: format-neutral, showing only where the final goes. **Right:** rounds narrow left to right into the final at the right edge. **Middle:** both sides narrow into the final in the centre. The final is drawn in the dark button colour; the backside shading, which only fits double elimination, is gone.
- Files changed: `js/bracket-view.js` (`layoutSEMiddle()`, `finalsVariant()`, labels and the dashed line, the header toggle), `tournament.html`, `js/dynamic-help-system.js`, `Docs/BRACKET-REDESIGN.md`.

### Release

- Version 5.4.0, "Just Around the Corner": the first format that isn't a knockout, Round Robin (groups and cups, or one group), built on the groundwork of the last releases (one layout per format, the formats registry, seeding, single elimination with the final in the middle). The Chalker is unchanged; its version and caches are bumped with the app's (`CHALKER_VERSION`, `chalker.js?v=26`, service worker cache `chalker-v123`).
- Files changed: `js/main.js` (`APP_VERSION` → `5.4.0`), `chalker/js/chalker.js` (`CHALKER_VERSION` → `5.4.0`), `chalker/index.html`, `chalker/sw.js`, `llms.txt` (Round Robin, single elimination finals in the middle, the new defaults; Round Robin off the "do not invent" list, Swiss, doubles, Cup and Plate and qualifiers on it), `sitemap.xml`, `releases/index.html`, `releases/v5.4.0.html`, `Docs/ReleaseNotes/RELEASE-NOTES-v5.4.0.md`, `js/dynamic-help-system.js` (help review: Top half named as the default, the format called Round Robin in the header help).

## **v5.3.2** — Don't You (Forget About Me) (2026-10-07)

### Match Controls: before the draw

- **Shuffle & Draw is above Seeding** in Match Controls before the draw: the draw buttons come first, the seeding choices under them. Seeding still applies when you draw.
- **Unpaid players can be removed from Match Controls**, with a **×** on their chip, as on Player Registration (the same `removePlayer()`). Paid chips have no ×: mark the player unpaid first, so one stray click can't remove someone who has paid.
- **The draw card no longer promises what it won't do.** It said "Only paid players go into the bracket", then refused the draw with an alert when someone was unpaid. A draw with an unpaid player in the list must never happen: a real player who wasn't marked paid would be left out of the bracket. So while anyone is unpaid, the draw buttons are disabled and say so ("2 players unpaid"), and the note says what to do (mark paid, or remove a player who isn't playing). The refusal in `generateCleanBracket()` stays as the safety net.
- **"Draw an 8-player bracket"**, not "a 8-player", on the draw buttons and in the Seeding panel.
- Files changed: `js/bracket-rendering.js`, `js/seeding.js`, `css/match-controls.css`, `js/dynamic-help-system.js`.

### Setup: the New tournament form stays open when it's the thing to do

- **Completed, or nothing loaded:** the New tournament form is always open, under the heading **Start a new tournament**, with no +/− toggle. Folding it away there removed the one thing the page points at and left no dark button, for a saving of one row. In New and Active it is still the quiet **+ New tournament** bar that opens on request. This also removes the "folded while framed" case (and its CSS rule).
- Files changed: `tournament.html`, `css/setup-page.css`, `js/tournament-management.js` (`syncSetupNew()`), `js/dynamic-help-system.js`, `Docs/PARKING-LOT.md` (item done).

### Setup: one thing to look at

- **Setup has a focal point.** The current tournament is the first thing on the page, and its next step holds the one dark button. **New tournament** is a quiet line under it (**+ New tournament**, with **import a tournament file** beside it) that opens the form when you need it. Once the tournament is **Completed**, the next job is a new one: the form moves to the top and **Create tournament** becomes the dark button, and the recap card below it has plain buttons (Open in Analytics, or Add to Analytics), so there is still one dark button. With nothing loaded, which only happens before a first tournament is created, it looks the same. **One rule marks the focus: the panel to act on is framed** (a mid-grey ring around its border, so it never changes size): the current tournament while it is New or Active, the New tournament form when it is Completed or nothing is loaded. The dark button inside it is the action. The other panel stays plain. Setup only. The form only opens or closes when the state changes, so a redraw never closes it while you type.
- **A flatter current tournament card.** The tinted status band across the top is gone from Setup: the status and its fact (the bracket isn't drawn yet, 12 of 30 matches completed, won by Anna) are on the first line, beside a coloured pill. The four bordered figures are one line of facts (6 players, all paid · 16-player bracket · 2 live now), with a slim progress bar while the tournament is active. The next step sits open on the card under a line, instead of in a box of its own. The status band stays on Player Registration.
- **No more jumping to Player Registration.** Creating a tournament, loading one from the list and importing one used to switch to Player Registration by themselves (an import after 1.5 seconds, which also hid its own success message). Setup stays open instead, and the current tournament card shows the next step, with **Register players →** one click away. An import's message now stays on screen. Setup's Match history used to catch up when you came back to the page, so it now refreshes with the current tournament (`updateTournamentStatus()` redraws it).
- Files changed: `tournament.html`, `css/setup-page.css`, `js/tournament-management.js` (the three `showPage('registration')` calls removed; `currentTournamentStatusFact()`, `syncSetupNew()`, `setSetupNewOpen()`, `toggleSetupNew()`), `js/dynamic-help-system.js`, `Docs/IMPORT_EXPORT.md`.

### One background behind the pages

- **The faint grey frame around the redesigned pages is gone.** The window's background (`#f1f5f5`, a cool grey) differed slightly from the redesigned pages' own (`--nt-bg`, `#f4f3f1`, a warm grey), so a thin strip of the cooler grey showed around Setup, Registration, Analytics and Global Settings. The window now uses the same token; the bracket page, Match Controls and the dialogs look as before. Pages that load `styles.css` without the design tokens (older release pages) keep the old grey through the variable's fallback.
- Files changed: `css/styles.css`.

### Release

- Version 5.3.2, "Don't You (Forget About Me)". The Chalker is unchanged; its version and caches are bumped with the app's (`CHALKER_VERSION`, `chalker.js?v=25`, service worker cache `chalker-v122`).
- Files changed: `js/main.js` (`APP_VERSION` → `5.3.2`), `chalker/js/chalker.js` (`CHALKER_VERSION` → `5.3.2`), `chalker/index.html`, `chalker/sw.js`, `llms.txt` (Setup by state, never a draw with an unpaid player), `sitemap.xml`, `releases/index.html`, `releases/v5.3.2.html`, `Docs/ReleaseNotes/RELEASE-NOTES-v5.3.2.md`, `Docs/PARKING-LOT.md` (the season final's decisions; the SE middle layout as the first formats step).

## **v5.3.1** — Sowing the Seeds of Love (2026-10-06)

### No clock on an analytics-only instance

- **The clock is hidden on an analytics-only instance**, in the app header and in the bracket header: nobody runs a tournament there, so there is nothing to time. Full mode is unchanged.
- Files changed: `css/styles.css`.

### Seeding the draw

- **Shuffle & Draw can keep the best players apart.** A new **Seeding** panel in Match Controls, shown before the draw, ranks the players on earlier tournaments with the same name and seeds the best of them; everyone else is still drawn at random. Seed 1 and 2 go at the top and bottom of the bracket, seeds 3-4 in the two middle quarters, seeds 5-8 in the remaining eighths, and so on, so seeds never meet in round 1.
- **How much is seeded follows the bracket size:** **1/8** puts a seed in a quarter of the round 1 matches, **1/4** in half of them, **1/2** in every one (the rest drawn at random), and **All** seeds every ranked player, with the top seed meeting the bottom seed, the second seed the second-last and so on. In an 8, 16 or 32 player bracket that is 2 / 4 / 8 seeds for 1/4, and 4 / 8 / 16 for 1/2. Fewer than two seeds means no seeding.
- **Byes go to the best seeds,** in rank order (no setting). In All that follows from the mirror draw: the missing lowest seeds are the byes, so they fall to the top seeds. Players with no ranking are never seeded (in All they take the places left over, at random) and only get a bye if there are more byes than seeds.
- **The panel says who is seeded:** how many of the players, which fraction of the bracket, the seeds with their points, who has no ranking, and how many byes the best seeds get.
- **The ranking is a mini-lens.** It is the Leaderboard's points (its point mode and layers) over the tournaments in this browser. The name word is taken from the active tournament's name: numbers, dates and words like "week", "uke" and "Final" are dropped, and the longest word left is used, so "Måndagscup", "Måndagscup week 43", "NewTon Måndagscup" and "Måndagscup Final" are the same cup. Tournaments with "Final" in the name never count, so a Final is ranked on the season's cups. The period is the current half-year, or the previous one while the current has no tournament of the cup (the first match of a season). The word, the period and the amount seeded can be changed per draw, and tournaments can be ticked by hand, so a name that matches nothing can still be seeded by choosing the tournaments. No match or no history gives a random draw, and the panel says so.
- **Settings:** Global Settings → Tournaments → **Seeding**: *Use seeding* Off / Available / On (default Off: nothing changes for a club that doesn't want it), and *Seeded players* 1/8, 1/4, 1/2 or All (default 1/4). Both are new optional settings (absent means off), so older settings read as before.
- **The draw keeps a record:** `tournament.seeding` (the amount seeded, who was seeded with rank and points, the name word, the period and the tournaments used), absent for a random draw. It is kept in saved tournaments and in exports, and read back by every way of loading one.
- **Built to be reused:** `js/seeding.js` decides who the seeds are and knows nothing about brackets; where they go is one function beside the shuffle (`placeSeededPlayers()`), used only when there are seeds. Without seeds the draw is exactly the code it was. A group draw can take the same list later.
- Files changed: new `js/seeding.js`; `js/clean-match-progression.js` (`placeSeededPlayers()`, an optional `seeding` for `createOptimizedBracketV2()`, the record kept at the draw), `js/newton-history.js` (`seedingTournaments()`, `seedingRanking()`, `seedingPlayerKey()`, `halfYear()` made public), `js/bracket-rendering.js`, `js/results-config.js`, `js/main.js`, `js/tournament-management.js`, `js/types.js`, `js/dynamic-help-system.js`, `tournament.html`, `css/match-controls.css`.

### Remote backup: a verified key is locked

- **Once Test connection finds the API key accepted, the server address and the key are locked** in Global Settings → Remote backup, with a note "Verified. The address and key are locked, so they can't be changed by accident." **Change…** asks first, then clears the key and unlocks both; Test connection locks them again. Until a key has been verified the fields stay editable, and a failed test never locks or unlocks anything. The lock is part of the form like any other change: it takes effect with **Save changes**, and **Discard** puts it back.
- **Stored as `server.remoteVerified`**, a new optional flag (absent means not verified, so older settings read as before). It is only kept while an address and key are present, and is left out of exported tournament files with the key.
- Files changed: `tournament.html`, `css/config-page.css`, `js/config-page.js`, `js/results-config.js`, `js/tournament-management.js`, `js/types.js`, `js/dynamic-help-system.js`.

### Help buttons work on an analytics-only instance

- **The Help buttons in Analytics and Custom Settings now open the help.** The help system had been switched off in analytics mode back when Analytics had no help topics of its own; the topics came later, but the switch stayed. F1, Esc and Ctrl+H work there too. The first-run welcome guide is for the Tournament Manager, so it is still not shown on an analytics-only instance.
- Files changed: `tournament.html`, `js/dynamic-help-system.js`.

### Bracket header on an analytics-only instance

- **The status line no longer runs into the Finals buttons** when a bracket is viewed on an analytics-only instance. The header's top row takes its height from the centre group (the tabs and Leaderboard), as the left and right groups span both rows; with those buttons hidden in analytics mode the row collapsed, and the status row rose into the tools. The centre group now keeps the tabs' height (38px) when empty. Full mode is unchanged.
- Files changed: `css/bracket-view.css`.

### Analytics: Finishes chart fits its frame

- **The Finishes chart no longer spills out of its frame**, which showed full screen: the Winner band climbed over the player chips and the 17th+ band ran over the month labels. The bands were spaced as five gaps with each band a gap tall, so the outer two stuck out by half a gap, a tenth of the chart's height. The six bands now share the plot equally, each tier's mark in the middle of its band.
- Files changed: `js/newton-charts.js`.

### Release

- Version 5.3.1, "Sowing the Seeds of Love". The Chalker is unchanged, but its version and caches are bumped with the app's (`CHALKER_VERSION`, `chalker.js?v=24`, service worker cache `chalker-v121`).
- Files changed: `js/main.js` (`APP_VERSION` → `5.3.1`), `chalker/js/chalker.js` (`CHALKER_VERSION` → `5.3.1`), `chalker/index.html`, `chalker/sw.js`, `llms.txt` (seeding, the locked backup key), `sitemap.xml`, `releases/index.html`, `releases/v5.3.1.html`, `Docs/ReleaseNotes/RELEASE-NOTES-v5.3.1.md`.

## **v5.3.0** — A View to a Kill (2026-10-04)

### Custom Settings on an analytics-only instance

- **On an analytics-only instance, Global Settings is called Custom Settings and shows only the Points.** Members use it to try other point values and see them in Analytics with **Custom**; the description says so, and that the values are kept in their browser only and the club's results don't change. The Club panel, the section list and the section heading are hidden there; the full app is unchanged. The names switch with two small classes in `css/components.css` (`.nt-in-full`, `.nt-in-analytics`), so both versions sit side by side in the markup.
- **"Today's values" is gone from the Custom points**, as it was unclear where they came from: the panel's choice reads **From Global Settings** (**From Custom Settings** on an analytics-only instance), and the button **Custom: Global Settings values** (**Custom: custom values**).
- Files changed: `tournament.html`, `css/components.css`, `css/config-page.css`, `js/newton-history.js`, `js/dynamic-help-system.js`, `llms.txt`.

### Analytics → Players: at most six ticked

- **The Players list opens on the best player in the Lens** (or everyone sharing the top points, at most six), instead of ticking everyone.
- **At most six players can be ticked,** the most the charts compare. With six ticked, the other boxes are greyed out ("Compare up to six players: untick one to swap"). The note "N players are ticked; the charts show the six highest ranked" is gone, as it can't happen any more.
- **The box at the top ticks the six best players** in the Lens (it shows ticked when exactly they are), or unticks everyone.
- **The selection lasts for the visit,** like the Lens: it is no longer saved in the browser (the value older versions saved, `newton_analytics_playerSelection`, is cleared with the old Lens values). Players who drop out when the Lens changes are unticked; with nobody left, the best player is ticked again.
- Files changed: `js/newton-history.js` (`_bestPlayers()`; the save and restore of the selection removed), `tournament.html` (the list's hint), `js/dynamic-help-system.js`.

### Analytics: Finishes chart draws lines

- **The Finishes chart (Analytics → Players) draws a line through each player's finishes**, with the marks on top, like the Average chart. It showed marks only, which made a player's run hard to follow, especially when comparing. A tournament a player missed is bridged, as on the other charts; the hollow marks on the axis still show which. The card's sparkline was already a line.
- Files changed: `js/newton-charts.js`.

### Analytics instance: no Match Controls from a selected match

- **On an analytics-only instance, the bracket's selection bar no longer offers Match Controls.** Clicking a match in a tournament opened from Analytics showed the bar with a Match Controls button, which opened Match Controls for the tournament. The header's tabs were already hidden there; the bar's button now is too (`.mode-analytics`, as for the header). Follow and the rest of the bar are unchanged.
- Files changed: `css/bracket-view.css`.

### No stray focus ring

- **A clicked button no longer turns up with a thin blue border.** A clicked button keeps the focus, and the browser draws its focus ring as soon as a key is pressed: an arrow to switch tabs, Esc to close a dialog opened from it, + / −. A key now releases a button's focus first, on every page. Tab, Enter, Space and the modifier keys are left alone, so keyboard use is unchanged.
- Files changed: `js/main.js`.

### Tournament status at a glance

- **Setup's current tournament and Registration's next step have a status band across the top**, tinted by status: grey **New** · the bracket isn't drawn yet; orange **Active** · 12 of 30 matches completed; green **Completed** · won by (the winner). One helper, `currentTournamentStatusBand()`, draws it for both. The small status pill on Setup is gone. (A coloured heading with a 4px top edge was tried first; the maintainer preferred the band.)
- **"Setup" is now "New" wherever the status is shown** (the tournament list, the Load, Delete, Import, Export, Reset and Analytics import dialogs): `tournamentStatusLabel()` maps the stored `setup` to New. The stored status is unchanged.
- Files changed: `js/tournament-management.js` (`currentTournamentStatusBand()`), `js/player-management.js` (`renderRegistrationNext()`), `tournament.html`, `css/setup-page.css` (`.st-band`), `css/registration-page.css`, `js/dynamic-help-system.js`.

### Developer Console: a tab on the bracket page

- **The Developer Console is the third tab, Console**, next to Bracket | Match Controls, shown when the Developer Console is enabled in Global Settings. It replaces the Console link and the dialog. Like Match Controls it is a layer over the bracket; the bracket's tools and legend hide while it shows. The page never starts on it, and turning the console off in Global Settings hides the tab (and leaves it if it was showing).
- **Redesigned in the new design language** (`css/dev-console.css`), decided without a mockup while the maintainer was away:
  - **Left:** a panel with the status figures as items, each with its live value and a coloured dot for health (instead of ✅ ⚠️ 🔴): Overview, Transactions, Matches, Players, Lanes, Storage. Then the commands, grouped **Inspect** (Transaction history, Transaction log, Validate everything, QR payload inspector), **Repair** (Re-render bracket, Recalculate rankings, Refresh all dropdowns) and **Change** (Toggle read-only, Late registration in amber, Reset all config in red). The item showing is highlighted; a sub-view (the pruning preview) counts as its parent. "Updated hh:mm:ss · every 2 seconds" at the bottom.
  - **Right:** the current view in a white panel, over **Console output** (collapsed; opens to up to 40% of the height, with the line count, Copy and Clear).
  - The views' repeated inline styles became classes (`dc-title`, `dc-box`, `dc-boxhead`, `dc-lines`, `dc-link`, `dc-btn`, `dc-input`); rounded boxes, the app's fonts and buttons. The eleven "← Back to Overview" links are gone, as the left panel is always there. What each view shows, and every command, is unchanged.
- **It runs only while its tab shows:** `startDeveloperConsole()` (capture `console.log`, draw, refresh every 2 seconds) and `stopDeveloperConsole()` replace `openAnalyticsModal()` / `closeAnalyticsModal()`; `showBracketView()` calls them, and so does leaving the page. The scroll listeners are added once.
- The late registration hints (Player Registration) and the help point to the Console tab.
- **Match progression is removed** (the view, its filters and Progression Code): the bracket shows progression far better. About 430 lines. The Progression Integrity check in Validate everything stays. `getMatchProgressionText()` in `bracket-rendering.js`, left over from the old bracket cards with no callers, went with it.
- Files changed: `css/dev-console.css` (new), `tournament.html` (the view replaces `#analyticsModal`; tab; stylesheet link), `js/analytics.js`, `js/bracket-rendering.js` (`showBracketView()` knows three views), `js/bracket-view.js` (the tab follows the setting), `js/main.js`, `js/player-management.js`, `js/results-config.js`, `js/dynamic-help-system.js`, `css/bracket-view.css`, `css/styles.css` (old console rules removed), `Docs/BRACKET-REDESIGN.md`, `Docs/DIALOGS.md`.

### Match Controls in the bracket's frame

- **Match Controls is no longer a dialog**: it shares the Tournament Bracket page's frame, switched with the tabs **Bracket | Match Controls** in the header (mockup: frame-views.html, approved 2026-10-04). It is a layer over the bracket, so the bracket keeps its camera underneath. The results-waiting badge (network handover) moved onto the Match Controls tab.
- On Match Controls, the bracket's tools (Finals, Fit all, zoom) and the colour legend are hidden; the clock and the status line stay.
- **Leaderboard** beside the tabs has the tabs' height and text size, so it no longer looks like a stray, smaller tab.
- Match Controls' own header and footer are gone. **Scan QR results** is in the Lanes heading (QR handover, while matches are live); Leaderboard is the header's button; Close is the Bracket tab.
- **"Open Match Controls with the bracket" is now "Start on Match Controls"** (Global Settings, same stored setting `config.ui.autoOpenMatchControls`, on by default): the page opens on Match Controls, or on the bracket when off. A tournament opened from Analytics for viewing still opens on the bracket.
- **The left and right arrow keys switch between Bracket and Match Controls** (not the Console, and nothing while it shows). Not while typing or choosing in a list, with a dialog open, or in analytics-only mode.
- The bracket's selection bar **Match Controls** switches to Match Controls and flashes that match's tile or queue row (`showBracketView('controls', id)`).
- The layer keeps the id `matchCommandCenterModal` and `style.display = 'block'`, so every existing "redraw Match Controls if open" check works unchanged, including those in `clean-match-progression.js` (not touched). Two checks that didn't fit are fixed: `qr-bridge.js` looked for Match Controls on the dialog stack, and the tournament reset in `tournament-management.js` only accepted `display: flex` (so it never refreshed).
- When the last dialog closes, `popDialog()` redraws Match Controls if it is showing. As a dialog, Match Controls was restored by the stack after the winner dialog, a QR result and so on, and that restore was its redraw; this keeps it (e.g. a finished match leaves the lanes board straight away).
- **Fix:** after a reload on the bracket page, Start on Match Controls was ignored. The page is restored before the tournament loads, so the start view saw no tournament and chose the bracket (the old auto-open had a 100 ms delay that hid this). `showBracketStartView()` in `main.js` makes the choice, from `showPage()` and once more at startup after the tournament has loaded.
- Decided: the start view applies every time the page is opened, as the auto-open did. Match Controls' links (Player Registration, Global Settings, Tournament Analytics) no longer pop a dialog first.
- Files changed: `tournament.html`, `css/bracket-view.css`, `css/match-controls.css`, `js/bracket-rendering.js` (`showBracketView()`, `_bvSetView()`), `js/bracket-view.js`, `js/main.js`, `js/qr-bridge.js`, `js/tournament-management.js`, `js/results-config.js`, `js/dynamic-help-system.js`, `js/types.js`, `Docs/BRACKET-REDESIGN.md`.

### Global Settings: Test connection

- **Remote backup has a Test connection button**, next to the API key. It tests the address and key as they are in the form (saved or not), through this computer's relay, the way a backup travels, and says what it found: connected and the key accepted; the key wrong or missing; the server doesn't ask for a key (with a nudge to set one); it can't be reached (with the reason); it asks for a web-server login; or it is an older version that can't be checked.
- **New `api/key-check.php`:** says whether the instance asks for an API key and whether the `X-API-Key` header matches. Writes nothing.
- Checked against real containers: right key, wrong key, no key, a server without a key, an unknown host, an older server, no address.
- Files changed: `api/key-check.php` (new), `js/tournament-management.js` (`testRemoteConnection()`), `tournament.html`, `css/config-page.css`, `js/dynamic-help-system.js`, `Docs/REST_API.md`.

### Match Controls redesign

- **Match Controls is rebuilt around the dartboards** (mockup: https://claude.ai/artifact/KKXAavLSXz6QDqm7xEbHoZ), in the new design language (`css/match-controls.css`). Same functions and rules as before: lanes, referees and their conflicts, Start/Stop, the winner dialog, QR and network handover, undo.
  - **Header:** the tournament, Live / Ready / Played / Free lanes (Players / Paid / Unpaid before the draw), the clock and ×.
  - **Lanes:** one tile per live match, in lane order: the players as big **Wins** buttons, the match number, best of, **time on the board** (from the match's Start in the history; updates with the clock), the lane and referee (both still changeable while live), the round, the handover (QR, Transfer, or the pulsing **Result ✓**) and Stop. A live match without a lane gets a **No lane** tile (Transfer needs a lane).
  - **Free lanes collapse into one line**, with the next ready match without a referee conflict: click a free lane to put that match on it and start it (`startMatchOnLane()`, using `updateMatchLane` and the usual Start handler). Lanes not in use are listed.
  - **Ready to start:** a compact queue by round, frontside and backside side by side (one column in single elimination), each row with Lane, Referee and Start; a referee conflict is written on the row and blocks Start, as before.
  - **Referees:** live matches without a referee first, then recent losers, recent winners and who refereed recently (`getRefereeSuggestions()`, unchanged). Redrawn after every action.
  - **Before the draw:** the players as chips to mark paid, an Add field (the player database, via `addPlayer()`), a compact summary of the points, match lengths and lanes, and Shuffle &amp; Draw per format.
  - **Finished:** the podium and, always under it, three headline highlights (Most 180s, Shortest leg, Highest out) with everyone who shares the best, or "None tonight", and a slate plaque at the foot with the club name (in Insignia), the tournament and the date (the panel's small name and date are gone; both columns share a height); on the right, first **4th, 5th–6th and 7th–8th** (the places after the podium that still score placement points), then the night's awards, one per row so there is never a gap however many there are: Most points, Most matches won, Backside run, Best average (from the Chalker matches in the register), Most tons, Lollipops and Busiest lane, each left out when there is no data; then **the night in numbers**, always the same six: Bracket (format and size), Total points, Matches played, Short legs, 180s, High outs; Tournament Analytics, Export and Leaderboard centred at the foot. Dropped before release at the maintainer's request: the longest and quickest match, whitewashes, deciders, busiest referee, a Debut award (replaced by the places 4th–8th), and a Season leader award (a half-year includes tournaments outside the club's season; see Docs/PARKING-LOT.md, "A Season concept").
- The lane and referee dropdowns say **No lane** / **No referee** instead of "No" / "None".
- **Fix:** the old finished view's "Most Achievement Points" always said "None": its helper `calculateAchievementPoints(player)` was shadowed by the points function of the same name in `results-config.js`. The new view uses `calculatePlayerPoints()`.
- About 1,100 lines of old Match Controls code (`createMatchCard`, the old `showCommandCenterModal`, `populateRefereeSuggestions`, the celebration functions, `updateTournamentConfigDisplay`) and about 620 lines of its CSS are gone.
- Files changed: `css/match-controls.css` (new), `js/bracket-rendering.js`, `js/lane-management.js` (No lane), `tournament.html` (Match Controls markup, stylesheet link), `css/styles.css`, `js/dynamic-help-system.js`, `js/types.js`.

### Analytics: As played | Custom

- **The points controls are two buttons: As played | Custom.** As played (the default) scores each tournament as it was played: its own point values, placement and attendance included. Custom opens a small panel: point values (today's from Global Settings, or as played) and whether placement and attendance points count. The button then says what is custom ("Custom: today's values, no attendance"); the choice is kept for the visit. It replaces Original | Current and the Ranking and Attendance switches ("Ranking" is now "Placement points").
- The focus ring on the strip's button groups is drawn inside the button, so the group's edge no longer clips it to an orange sliver.
- Files changed: `tournament.html`, `js/newton-history.js` (`_setPoints()` and the panel replace `switchPointMode()` and `toggleLayer()`), `css/analytics-page.css`, `js/dynamic-help-system.js`, `llms.txt`.

### No more pop-up hints

- **The orange pop-up hints are gone**: "Need more paid players. Press F1…", "Tournament created!", "Bracket generated!", "N matches ready to start", "Many matches are live…", "Tournament completed!" and the rest. The pages show the same things (Registration's next step, the bracket, Match Controls), and anything that blocks an action still says so in its own dialog. Help is still on F1 and the Help buttons.
- `showHelpHint()`, `suggestHelp()`, `triggerContextualHelp()` and the `onTournamentCreated` / `onBracketGenerated` / `onFirstMatchCompleted` hooks are removed from `dynamic-help-system.js`. Their callers elsewhere (including `clean-match-progression.js`, unchanged) check that they exist first, so they now do nothing.
- Files changed: `js/dynamic-help-system.js`.

### Player database

- **A global player database in Player Registration** (mockup: https://claude.ai/artifact/XpVNb6RwbahYizDRmQow1m). Every player has a permanent ID, a **short name** (what the bracket, Match Controls, the Chalker and the Leaderboard show; unique), and a first and last name. It replaces the saved-players list.
  - **Tonight** tab: tonight's players (short name, full name under it), and **Add from the database** with a search over short, first, last and previous names (Enter adds the first match, or offers to create the player), the most active players first. **+ New player** suggests the short name from the first name, with the last name's initial when it is taken.
  - **Player database** tab: every player with their names, previous names, finished tournaments played and last played. **Edit** renames (the old short name is kept as a previous name, so older results still find the player); **Merge…** joins duplicates (one keeps its details; the other's ID and names stay with it); **Archive** hides a player from the pick list. **Players who have been in Analytics can't be deleted**, only archived; players who never played a match can.
  - **First run:** the saved players, and the names in saved tournaments and the Analytics register, become database players (short name = the name; first and last empty to fill in), with a notice saying how many. Not on an analytics-only instance.
- **Tournament players carry the database ID** as `registryId` (additive; their own `id`, used by the bracket, the history and undo, is unchanged). Players in a tournament from before the database are linked by name when it is loaded before the draw.
- **Analytics follows the ID:** each tournament in the register records which database player each tournament player is (`registryIds`, at finalization and import). Analytics groups by it, merged IDs included, and links older tournaments by name (short or previous name). It shows the current short name everywhere (Leaderboard, Players, Dashboard, winners, match lists and match detail) and the full name in the profile.
- **The database travels with tournaments:** exports and uploads carry it (`playerDatabase`, with full names; the `playerList` of short names stays for older versions). Importing a tournament file **adds** its players by ID instead of replacing the saved-players list. The server keeps the newest uploaded copy in `tournaments/registry/player-database.json`, which an analytics-only instance reads (`instanceMode` in the page tells it apart under `?tm`).
- Match Controls' add-player field and late registration (Developer Console) take players from the database too (found by name, or created).
- **Merge guard:** two players who played in the same tournament are two people, so Merge refuses them and names the tournaments (`usage()` now also records which tournaments each player was in).
- Files changed: `js/player-registry.js` (new), `js/player-management.js`, `js/newton-history.js`, `js/newton-db.js`, `js/tournament-management.js`, `js/analytics.js`, `js/main.js`, `js/types.js`, `js/dynamic-help-system.js`, `css/registration-page.css`, `tournament.html`, `api/upload-tournament.php`, `Docs/REST_API.md`, `llms.txt`.

### Player charts

- **A player's progression, as charts** (Analytics → Players; mockup: https://claude.ai/artifact/VqxXWoFhDpuUpMc1hMhZd7). The profile gains their last 10 finishes, and six cards with a sparkline and a one-line verdict ("▲ 2 places in 10", "10.4 last 5, ▼ average 12.8"). A card opens its chart:
  - **Position**: place in the standings after each tournament, by points so far (ranked as the Leaderboard ranks), with the top 16 shaded.
  - **Points**: points each tournament, and the form line (the average of the last 5 played).
  - **Finishes**: each tournament's finish on bands (Winner, Final, Top 4, Top 8, Top 16, 17th+).
  - **Average**: three-dart average each tournament, with the worst-to-best match spread; tournaments without Chalker matches are shaded.
  - **Matches**: won and lost each tournament.
  - **Highlights**: 180s, high outs and short legs on one time axis.
- **Comparing:** "+ Compare with" adds up to five more players, each in its own colour, and "The field" adds the median of everyone who played (Points and Average). With several players, Points shows the form lines and Matches the win rate over each player's last 5 tournaments. **Full screen** shows the same chart, measure and players on the whole screen (Esc closes it).
- **Ticking several players** now compares them on these charts instead of in a table (the six highest ranked when more are ticked).
- Everything follows the Lens and the Points controls. Hover or tap a tournament for its figures. Phones: cards two to a row, charts to the screen's width.
- **Under the hood:** `js/newton-charts.js` (new) draws the charts as plain SVG and never changes data. The figures come from `_computePlayerRows()`, whose per-tournament history now also carries the three-dart average and the worst and best match (checked: the Leaderboard's averages are unchanged), via `_buildChartData()` (tournaments in date order, results per tournament, standings after each, the field).
- Files changed: `js/newton-charts.js` (new), `js/newton-history.js`, `css/analytics-page.css`, `tournament.html` (script), `js/dynamic-help-system.js`, `llms.txt`, `Docs/PARKING-LOT.md`.

### Analytics opens on the current half-year

- **The Lens starts every visit on the current half-year** (H2 2026 = 1 July to 31 December), or on the previous half-year while the current one has no tournaments yet, or on everything if both are empty. Every tournament in it is ticked. What a visitor changes lasts until they leave the page; **nothing about the Lens is remembered between visits any more** (it used to be saved in the browser, so a member could be left looking at an old selection). Show all still shows every tournament.
- Setup's **Open in Analytics** still opens on just that tournament: it now sets the Lens directly for the visit (`scopeTo()`), with no date range, instead of going through the saved selection.
- The Lens values older versions saved (`newton_analytics_scope`, `_textFilter`, `_dateFilter`) are cleared on the first visit.
- Files changed: `js/newton-history.js` (`_initLens()`, `scopeTo()` new; the Lens save/restore functions removed), `js/dynamic-help-system.js`, `llms.txt`.

### Tournament Setup: New tournament on top

- **The New tournament form is now one row at the top of Setup** (title, name, date, Create tournament, with Import tournament under it), and the current tournament is full width under it. Before, the form sat to the right of the current tournament and was easy to miss. Tournaments and Match history are unchanged.
- **Tournaments and Match history now end at the same line.** Both panels take the row's height and each list fills its panel (scrolling past 470px as before). They used to size to their own contents, so their bottoms differed.
- Files changed: `tournament.html` (order of the two panels), `css/setup-page.css`, `js/dynamic-help-system.js` (Setup overview).

## **v5.2.1** — Open Bar, Locked Cellar (2026-10-04)

### API key for writes

- **`NEWTON_API_KEY`** (new, optional): when set, every API request that changes something needs the `X-API-Key` header to match: Upload, Delete, Relay, and saving corrections (`POST api/corrections.php`). Reading never does: the page, List Tournaments, the files in `/tournaments/`, and reading corrections. A missing or wrong key gets 401. Unset means no key, as before. Compared with `hash_equals()` in `require_api_key()` (`api/api-check.php`).
  - Purpose: a public analytics-only instance that members open without a login, which only the club's backups can write to. Until now the whole site had to sit behind a proxy login to keep strangers from uploading or deleting.
- **`?tm` works as before:** with the correct `NEWTON_TM_PASSWORD`, `tournament.html` hands the instance's key to the page (`NEWTON_CONFIG.apiKey`), and the page's own writes (corrections, delete, Backup to server, shared upload) send it via `apiWriteHeaders()`. Only behind a password: with an open `?tm` the key is never handed out.
- **Global Settings → Server & backup → Remote backup:** **API key** replaces Username and Password. The relay sends it to the remote server as `X-API-Key` instead of basic auth. The remote username and password are removed from the saved settings the next time they're saved; nothing needs migrating.
- **Server credentials stay out of tournament files.** Tournament exports and uploads carried a full copy of the settings, including the remote username and password; on a public instance those files are readable by anyone. The copy now leaves out the API key and the old username and password (`configForExport()` / `withoutServerCredentials()` in `results-config.js`), as does the config snapshot in the Analytics register (`newton-db.js`). **Tournament files uploaded before v5.2.1 may still contain the old remote username and password**: retire those credentials when switching to the API key.
- **Network handover is off on analytics-only instances:** with `NEWTON_MODE=analytics`, the handover endpoints answer 403. They are for the club's own network.
- CORS allows the `X-API-Key` header on the write endpoints.
- Docs: DOCKER-QUICKSTART.md (analytics-only section, environment table, Security), `Docs/REST_API.md` (new Authentication section, Relay, settings), `api/README.md`, `Docs/NETWORK-LAYER.md`, the compose files, `automatic-backup.html`, `docker-quickstart.html`, `rest-api.html`, `llms.txt`, and the in-app help.
- Files changed: `api/api-check.php`, `api/upload-tournament.php`, `api/delete-tournament.php`, `api/relay.php`, `api/corrections.php`, `licensed/api/v1/_common.php`, `tournament.html` (`?tm` key hand-over, Remote backup API key field), `js/tournament-management.js` (`apiWriteHeaders()` new), `js/newton-history.js`, `js/results-config.js`, `js/newton-db.js`, `js/types.js`, `js/dynamic-help-system.js`, `js/main.js` and `chalker/js/chalker.js` (version), `chalker/index.html` and `chalker/sw.js` (cache).

## **v5.2.0** — New Flights, Same Arrows (2026-10-04)

### App header and footer

- **The app header and footer use the new design language**, as agreed in v5.1.10 for the redesign of the remaining pages (Docs/BRACKET-REDESIGN.md, "App header"). The header runs the full width: white, with one hairline underneath. It has a 40px round logo, the club name in Inter, and the tournament name and date. The clock is the same as the bracket header's. The name, date and clock are centred vertically in the whole header, as on the bracket page. The page links are plain text, with the current page bold and underlined in ink. The footer is full width with a hairline above, and on short pages it sits at the bottom of the window. This is done as one stylesheet over the existing markup, with no markup or script changes, so it can be removed in one line.
- **The header title is set in Insignia Regular** (20px), the club's display face, instead of Inter bold. It was tried and kept; Insignia has only a regular weight, so the title is not bolded.
- **Two shared page widths** in `css/design-tokens.css`: `--nt-page-max` (1520px, forms and short lists) and `--nt-page-wide` (1840px, table-heavy pages), for a full-screen browser of at least 1920px. Setup, Registration and Global Settings use the first.
- Files changed: `css/app-header.css` (new), `tournament.html` (stylesheet link), `css/design-tokens.css`, `css/setup-page.css`, `css/config-page.css`, `Docs/BRACKET-REDESIGN.md`.

### Tournament Setup redesign

- **The Setup page is rebuilt in the new design language** (mockup: https://claude.ai/artifact/Urawx3Mei3FK7SisBE22gd).
  - **Current tournament** comes first: name, date, format, a status pill (Setup / Active / Completed) and four figures. The figures are players (and how many have paid), bracket size, matches completed (with a progress bar), and the matches being played now with their lanes (the winner, once completed).
  - **Next step** changes with the status: Register players / Open bracket / Open in Analytics. The last becomes "Add to Analytics" when a completed tournament isn't in the Analytics registry.
  - Export, Backup to server and Reset tournament moved into this panel as quiet links, since they act on the loaded tournament.
  - **New tournament** is its own form, with Import tournament under it.
- **Tournaments is one scrolling table**, newest first. "Show All / Show Less" and the separate Shared / My Tournaments lists are gone. When a server answers, "This computer" and "Server" are two tabs; the Server tab lists the shared tournaments with Import / Re-import and ×. The loaded tournament is marked "Loaded" and has no Load or × button, so the "can't delete the active tournament" alert can no longer be reached. Storage is a small meter in the table header, still opening the storage dialog.
- **Match history** is one entry per match: the winner in green, "beat", the loser and the score (winner's legs first), then lane, referee and where both players went ("Ida to FS-2-2, Siri to BS-1-2", "out (7th-8th)", "wins the tournament"). Walkovers between two empty slots (no one moves on) are left out; the bracket still shows them. The match number is a tag showing the side: frontside outlined, backside grey, grand final dark. It follows the tournament's format: single elimination previously showed no progression, and its bronze final reads "takes 3rd place" / "takes 4th place".
- **Fix: the tournament list could show stale data.** `loadRecentTournaments()` overlaps itself, because each call waits for the server check. An earlier call that finished late overwrote the list with what it had read before a save. Only the latest call renders now. The table no longer waits for the Analytics registry (IndexedDB) either: it is drawn first, and the Analytics column is filled in when the registry answers.
- Reset tournament now refreshes the Setup page (status, match history, tournament list).
- In-app help for Setup rewritten for the new page.
- About 440 lines of old Setup CSS removed from `styles.css` (Setup layout, Recent Tournaments, match history cards, storage link, Analytics labels, plus unused `.tournament-item` / `.match-result-item` rules).
- Files changed: `css/setup-page.css` (new), `tournament.html` (Setup markup, stylesheet link), `js/tournament-management.js` (`renderSetupCurrent()` new; `loadRecentTournaments()`, `updateStorageIndicator()`, `updateTournamentStatus()`, `showImportStatus()`, `confirmReset()`, `loadSharedTournaments()`; `toggleSharedTournamentView()` / `toggleLocalTournamentView()` removed), `js/main.js` (`updateMatchHistory()`, `getPlayerProgressionForDisplay()`, `showPage()`), `js/dynamic-help-system.js`, `css/styles.css`.

### One points formula

- **Points are calculated in one place.** Participation + placement + achievements was written out separately in `calculatePlayerPoints()` (Registration, the Leaderboard dialog, exports) and three times in Analytics (the Leaderboard, the Dashboard's Points total, and per-match achievement points in the Register). Now `calculatePoints(stats, placement, pointValues, include)` and `calculateAchievementPoints(stats, pointValues)` in `results-config.js` do it, with `PLACEMENT_POINT_KEYS` for placement → point setting. Analytics passes its Ranking / Attendance layers as `include`, and its point mode (Original / Current) as `pointValues`; `calculatePlayerPoints()` stays as the Global Settings wrapper.
- No visible change: checked against the old code on 20,000 random players and tournaments, with identical results. Two edge cases now behave consistently: a missing point value counts as 0 instead of making the total `NaN`, and the Dashboard's Points total is the sum of the players' points (it previously also counted any placement entry without a matching player).
- Files changed: `js/results-config.js`, `js/newton-history.js` (`_achPoints()` and `_placementKeys` removed).

### One Leaderboard look

- **The Leaderboard dialog** (Leaderboard in the bracket header and Match Controls) **now looks the same as the Registration Leaderboard.** Both were already filled by `updateResultsTable()` with the same rows; only the styling differed.
  - The table style moved from `css/registration-page.css` (`.rg-lb`) to a new `css/components.css` as `.nt-leaderboard`, used by both.
  - The dialog is rebuilt on the `.dlg` pattern ("Leaderboard", the table edge to edge, Close), with no exports. Clicking a player still opens the statistics editor.
  - The dialog stack no longer shows `statisticsModal` as `flex` (a leftover from the old box's centring, which stretched the new dialog to the window height); it is `block` like every other dialog.
- The old `.results-table` CSS (dark header, stripes) and the dialog's old box rule are removed from `styles.css`; nothing else used them.
- Files changed: `css/components.css` (new), `css/registration-page.css`, `css/styles.css`, `tournament.html`, `js/main.js` (`pushDialog`), `js/results-config.js` (empty row).

### Player Registration redesign

- **The Registration page is rebuilt in the new design language** (mockup: https://claude.ai/artifact/TnxY3JWiqVPWJ7CpoPUXAU). It behaves the same way; the registration process itself will be reworked later.
- **Next step strip:** Players / Paid / Unpaid counts, then what to do now.
  - Before the draw: "Draw the bracket" with Open bracket. The button is disabled below the formats' minimum of paid players or above their maximum; the limits are read from `TOURNAMENT_FORMATS` via `getVisibleFormats()`.
  - After the draw: the matches still to play.
  - With no tournament loaded: Go to Setup.
- **The "Need N more paid players" / "You now have enough players" pop-ups are gone** (`showHelpHint` calls in `addPlayer()` and `togglePaid()`); the next step shows the same thing all the time.
- **Players** are rows in as many columns as fit (three at 1920px; more after the draw, when rows show names only), with a Paid / Unpaid pill. Clicking a row toggles paid, and × removes an unpaid player, as before. The name field and Add player sit at the top of the list. After the draw the list is locked: rows have no click or ×, so the "tournament in progress" warning can't be reached from it. "Player arrived late?" sits under it.
- **Saved players** shows only the saved names not in the tournament, as chips: click a name to add the player, × to delete the name from the list. The separate "In Tournament" list is gone (the Players list shows them), and with it `removePlayerFromTournament()`. A paid player is now removed by marking them unpaid first.
- **Payment QR** has its own panel, hidden when `images/payment.png` is missing.
- **After the draw the Leaderboard takes the wide column**, with Export CSV / JSON in its header. Clicking a row still opens the statistics dialog.
- **Fix: reloading the Registration page during a tournament showed the pre-draw layout.** The page was restored before the tournament had loaded; `autoLoadCurrentTournament()` now redoes the layout and the saved players once it has.
- **Fix: "Player arrived late?" told you to click the version number** in the bracket's lower-right corner, which went with the CAD box in v5.1.10. It now points to the Console link in the bracket header.
- In-app help for Registration rewritten. About 430 lines of old Registration CSS removed from `styles.css` (layout, player cards, saved-player items, `.scrollable-column`, `.two-column-container`, `.btn-small`), keeping the `.results-table` styles the statistics dialog uses.
- Files changed: `css/registration-page.css` (new), `tournament.html` (Registration markup, late-registration text, stylesheet link), `js/player-management.js` (`renderRegistrationNext()` new; `updateRegistrationPageLayout()`, `renderPlayerList()`, `updatePlayersDisplay()`, `updatePlayerCount()`, `addPlayer()`, `togglePaid()`, `showLateRegInfoModal()`; `removePlayerFromTournament()` removed), `js/dynamic-help-system.js`, `js/analytics.js` (comment), `css/styles.css`.

### Analytics: new content

- **Dashboard:** under the tiles, the Leaderboard's top 10 (click a player to open their profile) and the latest ten tournaments with their winner (click one to open it in the Register).
- **Player profile:** one ticked player now shows their Leaderboard figures (points, played, matches, legs, average, best out, best leg, 180s, high outs, short legs), their rank in the lens, how often they finished 1st to 7th–8th, and every tournament they played with their placing, 180s, match W–L and points (click one to open it). Comparing several players shows the same figures side by side; click one to see them alone.
- **Winner** column in the Register's tournament list, and Winner in an opened tournament's facts.
- **Leaderboard:** Points and Played come right after the player's name.
- **One set of player figures:** the Leaderboard's per-player calculation is now `_computePlayerRows()`, used by the Leaderboard, the Dashboard's top 10 and the Players list and profile. The Players list had its own count of tournaments and W–L; it now uses the same rows, so all views agree. The rows also carry one entry per tournament (placing, stats, points, W–L), which the profile lists.
- Files changed: `js/newton-history.js` (`_computePlayerRows()`, `_dashboardPanels()`, `_renderProfile()`, `_winnerName()` new), `css/analytics-page.css`, `js/dynamic-help-system.js`.

### Analytics redesign

- **The Analytics page is rebuilt in the new design language**, at the wide page width (mockup: https://claude.ai/artifact/3L3xkvRYMGJLcXyCGCatdZ). It shows the same things; new content (Dashboard top 10 and latest tournaments, a fuller player profile, a Winner column, Points and Played next to the name) follows separately.
- **One strip for the controls:** the view buttons (Dashboard / Leaderboard / Players / Register) and Points (Original / Current, Ranking, Attendance) on the first row; on the second, how many tournaments are counted and why ("23 of 24 tournaments · 1 unticked"), and the Lens. The strip turns orange when not everything is counted. "Choose tournaments" opens the Register's tournament list.
- **The Lens moved out of Register → Tournaments to the strip**, so it is visible and works from every view (name, from / to, the half-year buttons, now labelled "H2 2026", and Show all, formerly Reset). The tick boxes for single tournaments stay in the Register. The ticks are now set up before any view draws (`_ensureChecked()`), so the Lens works before the Register has been opened, and changing it redraws the view on screen (`_refreshActiveView()`).
- **Dashboard:** the seven numbers as tiles, still clickable.
- **Leaderboard:** the Leaderboard look, with group headings (Placements, Achievements, Total, Best, Matches, Legs). A line under the 16th player marks the top 16 while the table is in points order (it used to tint the top 16 rows whatever the order). Export CSV / JSON in the panel header.
- **Players:** the list shows Played and W–L; unticked players are dimmed. One ticked player shows a profile, several a comparison.
- **Register:** Tournaments / Matches tabs and a path back from an opened tournament or match. Tables show the match number as a side tag (as in Match History), the winner in bold, and Chalker / Manual as a pill. An opened tournament shows Format, Players, Matches and Points.
- **Match detail** (Analytics, and the match dialog opened from Match History): the match number, length and how it was scored, then a large score line, the achievements table, and the legs for Chalker matches. The match dialog is rebuilt on the `.dlg` pattern.
- **Phones:** Analytics is the page club members open on their phones (the analytics-only instance), so it has a phone layout below 700px: the controls stack, the tiles go two to a row, columns that don't fit are left out (Format, Matches, Date, Type, the buttons), and the Leaderboard scrolls sideways with rank and name kept in view. The app header and footer run edge to edge with the page links scrolling sideways, and Global Settings (Club and Points) fits a phone as it was.
- **NewtonTable** (only Analytics uses it): optional column groups (`group`), a class for heading and cells (`columnClass`), a scroll box around the table, and the new look in `css/components.css`. Pagination stays, with Rows 10 / 25 / 50 / All as a segmented control. The Players list no longer hides its page controls (with more than 25 players the rest could not be reached).
- **One match-number tag:** `matchIdTag()` in `main.js` makes the side tag for Match History and Analytics; its style moved from `setup-page.css` to `.nt-id` in `components.css`.
- In-app help for Analytics updated (where the Lens is, Show all, the top-16 line, the Players tick boxes).
- About 740 lines of old Analytics CSS removed from `styles.css`, including a narrow-screen block that also changed `.container`, `.page` and `.nav` on every page below 1120px.
- Files changed: `css/analytics-page.css` (new), `css/components.css`, `css/app-header.css`, `css/setup-page.css`, `css/styles.css`, `tournament.html` (Analytics markup, match dialog, stylesheet link), `js/newton-history.js`, `js/newton-table.js`, `js/main.js` (`matchIdTag()`), `js/dynamic-help-system.js`.

## **v5.1.10** — Straight Down the Middle (2026-10-04)

### New bracket view

- **The bracket is drawn by a new bracket view** (double elimination first; single elimination below). The layout is derived from the progression table instead of being written out per bracket size, so 8, 16 and 32 players share one set of rules and one card. Fit all shows the whole bracket on one page and is the furthest you can zoom out; scroll (or pinch) zooms at the cursor and dragging pans, and the bracket can't be dragged off-screen. Hovering a match magnifies it when zoomed out, or shows where its winner and loser go when zoomed in. Clicking a match selects it and highlights its lines, with markers pointing to connected matches that are off-screen; **Follow** traces a player through the bracket. The finals can sit on the right, as before, or in the middle (**Finals: Right | Middle**, remembered in the global config as `ui.bracketFinals`; missing means right). The same setting is in Global Settings → Bracket as **Finals position**; changing it in either place changes it in both.
- **The bracket page has a header instead of floating buttons.** On the left, the tournament name (large) and date with links to Setup, Registration, Config and Analytics (plus Console when the Developer Console is enabled in Config); in the centre, Match Controls and Leaderboard; on the right, the Finals toggle, Fit all and zoom, and a large clock spanning both rows (the bracket runs full screen, so the OS clock isn't visible). Below, centred, a status line (players, matches, played, walkovers, live, ready) and a legend. The CAD info box and the bottom watermark line are gone from the bracket page, as is the hover status text in the bottom centre.
- **Cards have no controls.** Lane, referee, start and winner are handled in Match Controls. **Undo** moved from clicking the winner on the card to an **Undo match** button in the selection bar. It appears only when the match can be undone, next to a **Match Controls** button that is always the rightmost in the bar; the eligibility check and the undo itself are unchanged (`isMatchUndoable()`, `handleSurgicalUndo()`).
- **Club name in the bracket:** the club name from Config is shown large on the side labels' line, top left with the finals on the right, and centred on the edge of the backside's shaded area with them in the middle.
- **Fix: zooming the bracket above 100% made the whole page flicker.** The zoom layer was kept as one GPU layer (`will-change: transform`); at high zoom a large bracket outgrew the graphics memory and Chrome kept redrawing the page. It is now painted normally (only the visible part is drawn, and text stays sharp at every zoom), and the bracket area is paint-contained.
- **Selection bar round names match the bracket's headers** ("Frontside final", "Semifinal", "Bronze final"…), instead of Match Controls' wording (which called the frontside final "Frontside Semifinal").
- **Long tournament names are cut short with …** before the status line; hovering the name shows it in full.
- **Labels:** FRONTSIDE and BACKSIDE are larger and centred over each side's first round, with FINALS just above the grand final in both layouts; round and finals headers are larger and bolder ("3rd place" now sits under the backside final), centred over their column, each the same distance above the topmost match of its round; the signature is centred under round 1 with the finals on the right (left-aligned at the bracket's edge with them in the middle).
- **Round 1 losers:** with the finals on the right, the lines from frontside round 1 to backside round 1 are always drawn, mirroring the frontside forks (the gap between the two halves now equals the gap between rounds). Other loser lines appear when a match is selected.
- **Finals on the right:** the grand final is level with the frontside final (a straight line between them) and the backside final sits directly below it. The frontside final feeds both finals: the winner's line runs straight on to the grand final, the loser's line drops from the bottom of the card into the backside final, always drawn. The line from the last backside match leaves from its left side (the backside runs right to left), goes round under the bracket and up the right side, with a T-junction into the backside final, and continues into the grand final from the right, so the two halves meet there from both sides. The backside's shaded area extends to take in that line where it runs alongside and under the backside.
- **Finals in the middle:** the grand final is now on top and the backside final below, matching the finals on the right. The frontside final is level with the grand final and the backside's last match level with the backside final, so both feed in with straight lines. The frontside final's loser line drops from the bottom of the card into the backside final, always drawn, as with the finals on the right.
- **Line colour:** all lines are the same grey, except fainter into a match that has no players assigned yet.
- **"Enable Developer Analytics" is now "Enable Developer Console"** in Config, matching what it opens; the Developer Console is reached from the Console link in the bracket header (the version number it used to hang off was in the CAD box, which is gone). Help text updated to match.
- **In-app help for the Tournament page rewritten** for the new bracket: the header, moving around (drag, scroll or pinch, Fit all, hover), selecting a match (lines, Follow, Undo match, Match Controls), the colour legend, and running matches from Match Controls. The Config help mentions the new finals position setting.
- **Single elimination uses the new bracket view too**, with its own layout: rounds up to the semifinals, then the **Bronze final** level with the top semifinal and the **Final** midway between the semifinals. The semifinal winners fork straight after the semifinals and run under the Bronze final to the Final; a dashed line joins the Bronze final to that line, and "3rd place" sits under it. Rounds are labelled Round 1…, Quarterfinals, Semifinals. Everything else (cards, selection, Follow, Undo match, camera, header) is shared; the Finals toggle is hidden. The classic renderer has been removed (see below).
- **Results waiting are counted on the Match Controls button.** When a result arrives from a Chalker over the network, the header's Match Controls button shows an orange count ("1 result") until it is accepted there; the match's card shows RESULT. This replaces a "Result received" message that showed in the bottom-centre status area, which went with the CAD box.
- **A read-only tournament says so in the selection bar** ("Read only", on every match) instead of a message when undo was refused.
- **The classic bracket renderer is removed:** `js/bracket-lines.js` (about 1,900 lines) and the per-size card, layout, title and line functions, the old zoom/pan and default views, the CAD box updater (`updateTournamentWatermark()`) and the bottom-centre status messages (`updateStatusCenter()`) — about 3,600 lines in all. `renderBracket()` now always hands over to the bracket view; `zoomIn()`, `zoomOut()` and `resetZoom()` remain as the header's entry points. The network layer's two status messages are now skipped (it already checked the function exists): the results count replaces one, and the other confirmed a send that happens in Match Controls.
- **Lane and referee dropdown code for the old bracket cards is removed** from `js/lane-management.js` and `js/bracket-rendering.js`: the bracket halves of `refreshAllLaneDropdowns()` / `refreshAllRefereeDropdowns()` (the Match Controls halves stay), `refreshLaneDropdown()` and `refreshRefereeDropdown()` (no callers left), the duplicate copies of the referee refresh functions (one copy now, in `lane-management.js`), and `updateMatchLaneWithValidation()`, which nothing called.
- **Fix: changing a lane in Match Controls now updates the lane shown on the match in the bracket.** `updateMatchLane()` deliberately skipped redrawing the bracket, because the old card had its own lane dropdown that was refreshed instead; the new card shows the lane as a label, so it needs the redraw.
- **Fix: refusing a referee in Match Controls now resets Match Controls' dropdown.** It used to reset only the old bracket card's dropdown, so Match Controls kept showing the refused name until it redrew.
- **The classic bracket CSS is removed** from `css/styles.css` (about 650 lines: classic cards, floating buttons, CAD box, watermarks, the unused `glow` animation). The bracket page's frame rules (`.bracket-container`, `.bracket-viewport`, `.bracket-canvas`) now live only in `css/bracket-view.css`, set once instead of overridden. `css/styles.new.css` (3,238 lines), which no page loaded, is deleted.

  Files changed: `js/bracket-view.js` (new), `css/bracket-view.css` (new), `js/bracket-rendering.js` (`renderBracket()`, `renderCleanBracket()` hand double elimination to the new view; zoom, pan and drag functions defer to it), `tournament.html` (bracket page header replaces the floating controls and watermarks; new stylesheet and script), `js/tournament-management.js` (`updateClock()` also feeds the bracket header clock), `js/main.js` (`showPage()` refreshes the bracket header on entry; old bracket controls no longer initialised), `js/bracket-lines.js` (removed), `css/styles.css` (classic bracket rules removed), `css/styles.new.css` (removed, unused), `js/lane-management.js` (old card dropdown code removed), `js/clean-match-progression.js` (`updateMatchLane()` redraws the bracket), `js/dynamic-help-system.js` and `js/analytics.js` (Developer Console wording), `js/results-config.js` (finals position setting), `Docs/BRACKET-REDESIGN.md`

### Global Settings redesigned

- **The Config page is rebuilt in the bracket's design language.** Settings are grouped by what you're doing (Club, Tournaments, Match day, Bracket, Chalker, Server & backup, Developer), with a section list on the left and one setting per row: what it does on the left, the control on the right. On/off settings are switches; small choices are segmented buttons (Game 301 | 501 | 701 | Other, Handover QR code | Network | None); match lengths are − Bo3 + steppers in a Double / Single elimination grid; points are a Placing table and an Achievements table; lanes not in use are clickable lane numbers instead of a comma-separated list; the finals position shows small pictures of the two layouts. Labels and descriptions are rewritten in plain language.
- **One save for the whole page.** The seven Save buttons and their "saved" alerts are gone. Any change brings up a bar, "N unsaved changes · Discard · Save changes", and the section list marks the sections that changed. Reset to defaults fills in the defaults and leaves saving to the bar. An empty club name or an out-of-range starting score is refused in the bar, and nothing is saved.
- **Leaving with unsaved changes asks first:** Stay, Discard and continue, or Save and continue. Closing or reloading the tab gets the browser's own warning.
- **Stored settings are unchanged**, and every input keeps its id: the steppers and buttons write into hidden fields with the original ids, so `applyConfigToUI()` and the save functions work as before. Each save function takes `{ silent: true }`, and `saveAllSettings()` runs them all.
- **Fix:** saving lane settings no longer switches off "require a lane before starting", which has no control on the page and used to be reset to off on every save.
- **Shared design tokens:** the colours and fonts of the new design language now live in `css/design-tokens.css`, used by both the bracket and Global Settings.
- In-app help for Global Settings rewritten for the new page.

  Files changed: `css/design-tokens.css` (new), `css/config-page.css` (new), `js/config-page.js` (new), `tournament.html` (Global Settings markup, stylesheets, script), `js/results-config.js` (silent saves, `saveAllSettings()`, resets fill the form only, format cards), `js/main.js` (`showPage()` asks before leaving unsaved settings and fills the form on entry), `css/styles.css` (old Config styles removed), `css/bracket-view.css` (tokens from `design-tokens.css`), `js/dynamic-help-system.js`

## **v5.1.9** — Every Chalker Needs an Eraser (2026-09-27)

### Analytics: achievement corrections (Docker only)

- **A tournament's achievements can now be corrected after the fact, from Analytics.** Under `?tm`, each tournament in Register → Tournaments has an **Edit** button. Pick a player and add or remove 180s, tons, lollipops, high outs and short legs; **Reset Player** goes back to what was recorded. The modal shows the recorded values alongside, so it's always clear what has been changed.

  Correcting a finished tournament had turned out to be nearly impossible. Achievements reach Analytics as a one-time snapshot: each browser pulls a tournament from disk into its own register once and never reads it again. Editing the file, deleting and re-uploading it, or editing an exported register all failed somewhere along that chain — often in a browser nobody was looking at.

  Corrections go around the chain instead of through it. They are stored on the server as the *difference* from what was recorded, one record per player per tournament, and applied every time Analytics loads its tournaments. The recorded tournament and each browser's register are never modified, so the upload → pull flow is unchanged, and a tournament that is deleted and pulled again keeps its corrections. Because they are applied at the one point every view loads from, the Dashboard, Leaderboard and Players views, the tournament points and both point modes all include them. Match-level views keep showing what was recorded on the night.

  Counts can't go below zero, and high outs and short legs use the same ranges as the tournament's own statistics editor (101–170, 9–21 darts). Corrections are always applied and carry no marker. There is no reason field — the Edit modal is the record.

  Docker only: without the server there is nowhere shared to keep them, so the button only appears when the corrections API answers, and never on the public Analytics page.

  Files changed: `api/corrections.php` (new), `js/newton-history.js` (`_loadAllTournaments()` applies corrections; new corrections section and Edit action), `tournament.html` (Correct achievements modal), `docker/entrypoint.sh` (creates `tournaments/corrections/` owned by www-data), `js/dynamic-help-system.js`, `api/README.md`, `DOCKER-QUICKSTART.md`

### Fixes

- **Undo now clears lane and referee assignments on downstream matches that hadn't started.** If the winner or loser of a match had been placed in a next-round match, and that match already had a lane or referee assigned, undoing the first match left those assignments in place. The referee stayed marked as assigned and the lane as in use, until someone found the match and cleared them by hand.

  Undo already removed those assignment transactions from history; it just didn't clear the same fields on the live match objects, so the two disagreed. They are now cleared together. (A live or completed downstream match blocks undo in the first place, so only matches still waiting for players are affected.)

  Files changed: `js/bracket-rendering.js` (`undoManualTransaction()`)

## **v5.1.8** — Off the Wire (2026-09-13)

### Fixes

- **The welcome help shown on a first run works again.** Opening the app with nothing stored — a fresh install, or a new browser — pops a first-time guide after a couple of seconds. It was displaying "Overview: undefined" and none of its actual content. The same applied to the "Common Issues" button inside the help window: that content had never been able to render either.

  The cause was a shape mismatch. Every help topic is stored as a title, an overview and a set of sections, and the renderer expects exactly that. The scenarios topic — which holds both the welcome guide and the common-issues list — had instead been written with its two entries at the top level, so the renderer found no title, no overview, and no sections to draw. It now has the same shape as every other topic, and both are reachable.

  It went unnoticed because until recently something else was covering it. The help system used to watch the whole page for changes, and any change at all — including the clock ticking over — made it redraw itself with the current page's help. The broken welcome was replaced within seconds of appearing. That watcher was removed in v5.1.6 as wasteful, which it was; it was also, accidentally, hiding this.

- **The Handover setting now says that Network needs Docker.** It is listed as "Network (experimental, Docker only)", and the description explains why: the feature needs the small web server that ships with the container, so it does nothing if you opened `tournament.html` directly or are using the hosted version.

### In-app help caught up with Analytics

- **The built-in help now explains the Analytics page.** It had been describing only the Register — the tournament and match records — because that is all Analytics was when the help was written. Everything added since, which is most of what people actually use it for, went undocumented: the Dashboard, the Leaderboard and what its columns mean, the Players view, and the two controls that change every number on the page.
- **The Lens is explained properly**, including the part that is easy to miss: you set it under Register → Tournaments, but it governs the Dashboard, Leaderboard and Players as well. The help now says so, and points at the indicator in the page header as the first thing to check when a figure looks wrong.
- **Point modes and layers are explained** — Original scores each tournament with the values in force on the night, Current rescores everything with today's values, and the Ranking and Attendance toggles switch whole categories of points on and off. With the reassurance that none of it changes a stored result.
- **Automatic backup has help for the first time.** Uploading a completed tournament to the server without anyone remembering to do it is one of the better reasons to run the container, and it was not mentioned anywhere in the app.

### Analytics: the maintenance URL can be password-protected

- **`NEWTON_TM_PASSWORD` gates the `?tm` maintenance URL.** An analytics-only instance hides tournament management, and appending `?tm` brings the full Tournament Manager back for that browser — which is how a shared instance gets maintained. It was unauthenticated, so anyone who knew the parameter could use it. Setting the new environment variable requires `?tm=<password>` instead.

  **A wrong or missing password loads the ordinary Analytics page** — no error, no prompt, no hint that a maintenance mode exists at all. A login prompt would announce the door and invite a try; this way nothing is advertised.

  Leave the variable unset and nothing changes: bare `?tm` keeps working exactly as before, so no existing deployment is affected.

  Worth being plain about the limits: this is one shared password in an environment variable, not user accounts, and it appears in the server's access log and in browser history. It stops a curious club member. It is not protection against someone determined, and an instance reachable beyond people you broadly trust still wants a password at the web server.

### Docker: tournament storage was not writable on Linux

- **Uploading a tournament and network match handover both failed with a server error on Linux deployments.** The container writes both into `tournaments/`, which the documented compose file supplies as a bind mount. When that host directory does not already exist, Docker creates it as **root** — and the web server runs as `www-data`, which then cannot write to it. Every upload and every match transfer returned a 500. Stack managers such as Dockge make this the default case, since they create the stack directory themselves.

  It hid well: macOS and Windows Docker use a file-sharing layer that ignores the ownership mismatch, so the same setup works there. Only real Linux deployments were affected, and only if anyone tried to use the features.

  The container now checks at startup whether the web server can actually write to `tournaments/` and corrects the ownership if not, logging that it did so. A directory that is already set up correctly is left untouched. If the correction is impossible, it now says so loudly in the log with the command to fix it, rather than failing silently at request time hours later.
- **Network handover state directory.** `tournaments/network/` is likewise created at startup, as root and after the volume is mounted — the only moment both are true. The endpoints still create it themselves when missing, so non-Docker deployments are unaffected.
- **A failed transfer now tells you what went wrong.** The endpoints have always answered with a readable explanation — `{"ok":false,"error":"..."}` — even on a 500, and both clients were throwing it away and reporting a bare failure. The Tournament Manager now shows the server's own words, and the Chalker logs them. The directory error also names the exact path and the user it was running as, which is the part that depends on the deployment rather than the code.
- **Verified against a real container**, not a stub: the image was built, the clients were driven against it, and a match was dispatched to a lane, collected, scored, returned, reviewed and cleared. The failure mode was reproduced first, then fixed, then re-tested.

### Files changed

- `js/dynamic-help-system.js` — the `scenarios` help topic now has the `title`/`overview`/`sections` shape the renderer requires, so the first-run guide and Common Issues both display; new Analytics sections (views, lens, points, leaderboard, players) and a Server & Automatic Backup section under Config
- `tournament.html` — Handover's Network option labelled "Docker only" with an explanation; `?tm` honours `NEWTON_TM_PASSWORD` when set (constant-time comparison, silent fallback to the configured mode)
- `DOCKER-QUICKSTART.md`, `docker/docker-compose.yml` — the new variable, and a section on maintaining an analytics-only instance
- `docker/entrypoint.sh` — ensures `tournaments/` is writable by the web server (correcting ownership only when it is not), creates and chowns `tournaments/network/`, and warns in the log with a fix command if either is impossible
- `licensed/api/v1/_common.php` — directory and write errors name the resolved path and effective uid
- `licensed/js/network-tm.js` — `post()` preserves the server's error text; dispatch failures show it
- `licensed/js/network-chalker.js` — `post()` logs the server's error text instead of discarding it

---

## **v5.1.8-beta.1** — Behind the Bar (2026-09-07)

### Analytics safety

- **Export Register, Import Register and Import Tournament are hidden in analytics-only mode.** A shared Analytics instance is now something a whole club can browse, and one of those buttons — Import Register — replaces the stored match history for everyone who uses it. They were sitting in plain sight at the top of the page, next to the scope selector, with nothing but a file picker between a curious member and everybody's season. They are maintenance tools and they now behave like it: absent from the shared view, and still available to the maintainer on the same instance via the `?tm` escape hatch, which forces full mode. Deleting a tournament was already gated behind a separate server setting and is unchanged. Nothing is removed from the normal Tournament Manager — this affects the analytics-only deployment (`NEWTON_MODE=analytics`) only.
- No new setting was needed: `?tm` already forces full mode and is already the maintainer's route into a shared instance. **To be clear about what this is and is not** — `?tm` is not authenticated, so anyone who knows the parameter can still reach these tools. This removes the accident, not the possibility. Gating `?tm` itself is a separate job.

### Known issue

- **Network handover still does not work.** Transferring a match to a lane returns HTTP 500. The endpoints in `licensed/api/v1/` have never been parsed by a PHP interpreter — run `php -l` over them first. The feature remains off by default.

### Files changed

- `tournament.html` — the three maintenance controls carry `analytics-maintenance-tool`
- `css/styles.css` — `.mode-analytics .analytics-maintenance-tool { display: none; }`

---

## **v5.1.7** — Know Your Format (2026-09-07)

### Known issue

- **Network handover does not work.** Transferring a match to a lane returns HTTP 500. The endpoints in `licensed/api/v1/` have never been parsed by a PHP interpreter — run `php -l` over them first. The feature remains off by default (Handover: QR code) and nothing else in this release depends on it. Sharing a version number with `v5.1.7-beta.1` does not mean that beta has graduated.

### Tournament formats

- **You can hide the formats your club never plays.** Under Config → User Interface, "Tournament formats to offer" controls which formats appear on the Shuffle & Draw screen. A club that only plays double elimination can hide single elimination, and the wrong one can no longer be picked by accident on tournament night — which is exactly how a season opener ended up briefly in the wrong format, despite the confirmation dialog naming it twice. Preventing the choice beats warning about it.
  - **Existing tournaments are untouched.** Hiding a format only affects the screen where a new tournament is started. A tournament already created in a hidden format still opens, renders, undoes and exports exactly as before.
  - **At least one format always remains.** The last ticked box cannot be unticked.
  - **Formats added in future releases appear by default**, rather than staying invisible until found in Settings. The setting records what you have hidden, not what you have chosen — so a new format shows up for everyone, and clubs who want it gone can hide it too.
- **One list defines the formats.** Their names, descriptions and player limits were written into the tournament screen's markup; the Config checkboxes would have been a second copy of the same list. Both are now built from a single definition, so the two cannot disagree about which formats exist. It covers presentation only — a new format still needs its own progression tables and rendering, which stay where they belong.

### Fixes

- **The Status Panel shows the real player and match counts again.** During a live 14-player tournament the panel reported 9 players and 0 matches. It had been reading the tournament object's own `players`/`matches` arrays, which look authoritative but are never actually updated: they are created empty with the tournament and only ever re-pointed at the live arrays when a tournament is loaded from storage. Three ordinary actions break that link for good — generating a bracket, removing a player, and creating a tournament — after which those copies are frozen at whatever they last held, while the real roster and bracket carry on without them. Everything else in the app, including everything saved to disk, uses the live arrays; only the panel did not. It does now. This is a regression introduced in v5.1.6, where the panel was changed to read the in-memory tournament instead of re-reading storage on every save — the storage record was being written from the live arrays, so it had always been correct. A reload was enough to make the panel right again, which is why it was hard to catch.
- **A knocked-out player is struck through only in the match that eliminated them.** The same frozen copy was consulted when deciding where to show the strikethrough, so the check found no matches to compare against and marked every match a player had lost. In double elimination that meant a player who lost once on the frontside and again on the backside appeared eliminated in both. Display only — no scores, standings or stored data were affected.

---

## **v5.1.7-beta.1** — Look, No Camera (2026-09-06)

### Network handover (experimental)

Matches can be sent to a Chalker across the local network instead of being carried by QR code. **Experimental, and not yet tested on real hardware.** Nothing changes unless you choose it: the new setting defaults to QR, and with the default selected the app behaves exactly as it did.

The network code lives in `licensed/`, which is **not open source** — see `licensed/LICENSE.md`. It is free to use, with no key and no subscription, under a grant that is revocable for future releases. Everything else in the project remains BSD 3-Clause, and both apps work fully with that directory deleted.

- **New Config setting: Handover — QR code / Network / None.** QR is the default and unchanged. Network hides every QR affordance and offers a Transfer button on a started match in Match Controls. None hides both, for clubs entering results by hand. Configs saved before this setting existed default to QR.
- **Sending a match.** Assign the match a lane, start it, and press Transfer. It goes to whichever Chalker is serving that lane. Nothing else changes about how you run the tournament.
- **Receiving a result.** When a Chalker finishes, the match card shows a result is waiting. **It is never applied on its own** — you accept it, and accepting opens the same review you already know from scanning a result QR, lollipop counters and all. A result that is not accepted stays waiting, so there is nothing to lose by leaving it.
- **Fixing a wrong result.** Corrections are made on the Chalker, which owns the scoring and can undo back across legs, and the corrected result replaces the waiting one. The Tournament Manager never edits machine-recorded scoring — a record either comes from the Chalker or is declared by hand, never a mix of the two.
- **Why polling rather than a live connection.** A phone sleeps, gets backgrounded, and roams between access points all evening. A connection has to survive all of that; a request that simply happens again in a few seconds does not. There is no connection to lose and nothing to reconnect.
- **No new dependencies and no broker.** The endpoints are plain PHP served by the container's existing web server, and the state lives in the volume it already mounts.

Groundwork that came with it: the Tournament Manager's assignment payload is now built independently of the QR code that used to render it, so one definition of a match assignment serves both ways of sending it. The Chalker's result side already worked that way. No change to what either produces — the payload was verified byte-identical to the previous code across every combination of lane, referee, missing settings and awkward names.

### Chalker

- **The install banner can be dismissed again, and Install is never a dead end.** Its two buttons were the only inline `onclick` handlers left anywhere in the Chalker — everything else is wired with `addEventListener` — which made them the only thing in the app a strict Content-Security-Policy would silently disable. Where that applied, the banner sat permanently across the bottom keypad row with both buttons inert. They are now wired like every other control. Two further faults in the same few lines: the banner markup sits *after* the scripts, so the buttons are not in the DOM when `chalker.js` runs (the listeners now wait for `DOMContentLoaded`), and `installApp()` returned silently when the browser's deferred install prompt was missing or stale — the button genuinely did nothing. It now closes the banner and remembers the dismissal instead.

### Files changed

- `licensed/` — new, separately licensed directory: `LICENSE.md`, `README.md`, `api/v1/{_common,assign,result,heartbeat,lanes}.php`, `js/network-chalker.js`, `js/network-tm.js`
- `LICENSE` — scope note naming the `licensed/` carve-out
- `README.md` — "Licensing split" section
- `js/qr-bridge.js` — new `buildAssignmentPayload(matchId)`, split out of `openMatchQR()`, which now derives its subtitle's referee name from `signed.ref`; `applyQRResult()` clears the network mailbox once a result has been applied
- `js/results-config.js` — new `config.chalker.handover` (default `'qr'`), `getChalkerHandover()`, the `transferMatchToDevice()` guard, and load/save wiring
- `js/bracket-rendering.js` — match card shows Result / QR / Transfer according to the handover setting and whether a result is waiting; bracket card marks a waiting result; Match Controls' scan button hidden outside QR mode
- `js/clean-match-progression.js` — winner dialog's Scan Results QR button hidden outside QR mode
- `chalker/js/chalker.js` — new `NewtonChalkerBridge`, the narrow surface the optional network client uses; install-banner listeners wired on `DOMContentLoaded`; `installApp()` no longer returns silently without a deferred prompt; new `hideInstallBanner()`
- `chalker/index.html` — install-banner buttons use ids instead of inline `onclick`; Network Mode modal no longer claims a licence is required; loads the optional network client
- `tournament.html` — Handover dropdown in the Config → Chalker section; loads the optional network client
- `css/styles.css` — styling for a result waiting to be accepted
- `Docs/NETWORK-LAYER.md` — rewritten for the LAN-only, REST-first proof of concept; the superseded design is retained as an appendix with a note on what it got wrong

### Not yet verified

The PHP endpoints have never been run — there is no PHP interpreter on the development machine — and neither client has run in a browser or over a real network. The clients are tested against stubbed endpoints, which verifies them against the intended contract rather than against the actual server. Run `php -l` over `licensed/api/v1/` and play one match end to end before relying on any of it.

## **v5.1.6** — One Throw, One Score (2026-09-06)

**Completes the code-improvement plan** (`Docs/CODE-IMPROVEMENT-PLAN.md`) — Phases 1–6 are now done. This release carries the end of Phase 4 (analytics bracket-preview isolation 4.3, NewtonMatchDB write-path atomicity 4.6; the remaining 4.10 schema-version item was reviewed and declined, see below) and the whole of Phase 6 — performance (6.1–6.5) and consolidation (6.7–6.21).

No new features. The theme is doing the same work once instead of repeatedly: `completeMatch()` persists once rather than 2–4 times (127 → 63 saves across a full 32-player tournament), `renderBracket()` parses the transaction history once rather than per card (~63 → 1), Analytics fetches match lists concurrently and caches them (48 → 12 reads; point-mode/layer toggles 48 → 0), and a whole-body MutationObserver is gone. Every change was verified by differential testing against the pre-change file — full tournaments replayed in both formats at every bracket size, state compared after each completion — with the details recorded per item in the plan doc.

Visible changes: the 16-player bracket font fix, the Short Leg Threshold reaching the Chalker, F1 help matching the page after a reload, and Analytics reflecting corrections to a finalized tournament without a reload.

**Two documented declines**, both reopenable with evidence: 6.1 part B (`checkRefereeConflict`'s O(n²) scan — pure in-memory, unmeasured payoff) and the `renderLeaderboard` split inside 6.11 (measured overlap was ~20 lines of a 292-line function; the plan's own rule is "split when touched, not as a dedicated pass").

### Analytics / History

- **Previewing a bracket no longer forgets the tournament you were editing.** In analytics-only mode (`NEWTON_MODE=analytics`), the "Bracket" preview writes the fetched tournament into the shared `currentTournament` pointer in order to render it. Two problems followed — both only reachable when the analytics box is *also* used to edit completed tournaments through the `?tm` escape hatch (same origin, shared localStorage):
  - The "back to Analytics" button did `localStorage.removeItem('currentTournament')`, silently deactivating whatever tournament you had open. On the next `?tm` reload it was gone from the pointer — its data was safe in `dartsTournaments`, but you had to reopen it from Recent Tournaments.
  - Reloading *while previewing* was worse: `autoLoadCurrentTournament()` rebuilt the tournament object without the `_analyticsPreview` guard flag, so the next save persisted the read-only preview into `dartsTournaments` as a phantom "real" tournament.

  The fix keeps the preview read-only and self-contained. `viewBracket()` now stashes the real active tournament (if any) under a transient `_preAnalyticsPreviewTournament` key before overwriting the pointer — skipped when the prior value is itself a preview, so chaining preview→preview can't turn an intermediate preview into the stash. A new `exitAnalyticsBracketPreview()` restores that stash on exit (or clears the pointer when nothing was active, preserving prior behavior), and the Analytics back button now calls it instead of blindly deleting `currentTournament`. `autoLoadCurrentTournament()` now carries `_analyticsPreview` across a reload, so the no-persist guard survives. Net effect: a `?tm` edit session survives a preview round-trip *and* a mid-preview reload instead of being booted out — the fix improves the edit workflow rather than merely protecting it.

### Match register (NewtonMatchDB)

Three IndexedDB write paths were made atomic and faster. None change the public API or any caller.

- **Re-completing a match can't lose the record to a race.** `saveMatch()` checked for an existing `(tournamentId, matchId)` record in one transaction and wrote in a *separate* one. Two near-simultaneous saves could both see "no existing" and both `add()`, the second colliding on the unique index and silently dropping the re-completion. The lookup and the write now share **one** transaction; because IndexedDB serializes overlapping read-write transactions, the second save sees the first's record and updates it in place.
- **Deleting a tournament is all-or-nothing.** `deleteTournament()` opened a fresh transaction per match in a loop, so a mid-loop failure could leave a half-deleted tournament (some matches gone, meta still present). It now deletes every match (via the `tournamentId` index cursor) and the tournament-meta record in a **single** transaction that aborts as a whole on any failure.
- **Importing a register dump is one transaction, not two per match.** `importAll()` did a lookup and a write in separate transactions for *each* match record — slow on large dumps and non-atomic. It now processes the whole match batch in one transaction, and de-dupes the incoming records by `(tournamentId, matchId)` first so a malformed dump with a duplicate can't abort the batch on the unique index (well-formed exports never contain duplicates).

All three now reject on transaction abort so a failure surfaces to the caller instead of hanging.

### Bracket rendering (Phase 6 cleanup)

- **Fixed the "BS-FINAL" label font on 16-player brackets.** The indicator's font-family was misspelled `'Ïnter'` (with a diacritic) in the 16-player code path, so that label silently fell back to the default sans-serif instead of Inter. Fixed while de-duplicating.
- **Consolidated duplicated bracket-line code.** The three byte-identical "BS-FINAL indicator" builders (8/16/32-player) are now one `createBSFinalIndicator`, and the three identical nested `createLoserFeedLine` copies are now one shared module-level helper (with a z-index parameter for the 32-player layout, which stacks its feed lines above the straight progression lines). About 199 fewer lines — and the font typo can no longer silently reappear in one copy.
- **Removed bracket-geometry debug logging.** Deleted ~27 developer `console.log`s that narrated internal layout math on every bracket render (coordinate dumps, `🔧 Creating…`, `🎯 Rendering…`). Operational logging elsewhere — lifecycle, save/load confirmations, ranking calculation, and the `processAutoAdvancements` infinite-loop guards — is intentionally kept as observability (there is no automated test suite), and every `console.warn`/`console.error` is untouched.
- **One source for the default bracket view.** The per-format, per-size default zoom + pan values were duplicated in two places (the initial render in `renderBracket()` and the Reset-zoom button in `resetZoom()`), and only one copy carried the "needs tuning" notes — a drift waiting to happen. Extracted `getDefaultView(format, bracketSize)`; both call sites use it. No behavior change (the two copies held identical values).
- **32-player backside background uses the shared builder.** The faint gradient box behind the backside bracket was drawn via a shared `createBacksideBackground()` for 8- and 16-player brackets, but the 32-player renderer inlined its own copy of the same logic. It now calls the shared function (which already had a matching 32-player branch) like the other sizes. No visual change.
- **32-player backside placement labels follow the rendered match positions.** For 8- and 16-player brackets, the elimination-place labels above the backside bracket read the match Y positions from the render pass; the 32-player labels instead recomputed those positions with a parallel copy of the geometry — correct today, but liable to silently drift out of alignment if the 32-player layout ever changed. The 32-player renderer now records each round's first-match Y as it draws it, and the labels read those values — so labels can no longer desync from the matches. No visual change (per-round label positions verified numerically identical).

### Tournament export (Phase 6 cleanup)

- **De-duplicated the export path and fixed a blob-URL leak.** `exportTournament()` was re-assembling the entire export payload (history load, pruning, player-list snapshot, the full object shape) instead of using the shared `buildTournamentPayload()` that the server-upload paths already use — so the two could silently drift. It now calls the shared builder, and it releases the download's object URL with `URL.revokeObjectURL()` (previously the blob was retained for the page's lifetime on every export).
- **Export filenames are sanitized.** Filesystem-hostile characters in a tournament name (`< > : " / \ | ? *` and control characters) are now replaced with `-` when building the filename, so a name like `Spring/Fall: Cup` produces a valid download instead of a broken or path-traversing one. Sanitization is deterministic (re-uploading the same tournament still overwrites its file) and normal names are unchanged.

### Analytics internals (Phase 6 cleanup)

- **One source for the achievement-points formula.** The calculation (180s + tons + high outs + short legs, each times its configured point value) was copy-pasted in five places across the Leaderboard, the tournament-points computation, the Matches tab, and the match-detail views. It's now a single `_achPoints(stats, p)` helper. No behavior change — the numbers are identical — but a future change to the point rules (or a new achievement type) is now a one-line edit instead of five that can drift apart.
- **One source for decoding Chalker visit scores.** The base64 decoding of a leg's per-visit scores was inlined twice in the analytics views (the three-dart-average aggregation and the match-detail leg table) instead of using the existing `NewtonStats.decodeVisits()`. Both now call it, so the encoded-visit format is defined in exactly one place. No behavior change (round-trip decode verified identical).

### Performance (Phase 6)

- **One definition of how player names are matched.** Analytics identifies players by name — each tournament stores its own player ids, so there is nothing stable to join on across tournaments. That means every view has to agree on exactly how a name is tidied up before comparing it, or the same person can appear twice, or a player's record can differ between two screens. That tidying was written out by hand in twenty places. It is now defined once. Alongside it, the Leaderboard and the Players tab had identical copies of the match win/loss count — they now share one, so those two screens cannot drift into reporting different records for the same player. No change to any figure on screen.

- **Completing a match saves once instead of two to four times.** Recording a result touched the saved tournament repeatedly in a row: once for the result, again after recalculating live rankings, again if the match set a placement (the Backside Final's 3rd place, or a Single Elimination bronze match's 3rd/4th), and again if it finished the tournament. Each of those rewrote the entire tournament — every player, every match — and redrew the status panel and results table with it. It all happens in one go now: the result, the rankings and any placement are worked out first, then written once. Playing a full 32-player double-elimination tournament went from 127 saves to 63. Nothing about the results changes — verified by replaying whole tournaments in both formats at every bracket size, including byes, and comparing the complete state after every single match.
- **Removed a dead "reopen Match Controls" path.** After a completion, the code could schedule the Match Controls panel to reopen half a second later, on top of the refresh it had already scheduled — but the flag that triggered it was never switched on anywhere in the app, so the branch could never run. Deleted, along with the two leftover places that reset the unused flag.

- **The help system stopped watching the entire page for changes.** To notice which page you were on, it ran a MutationObserver over the whole document — every element, every class attribute — so it woke up on *every* DOM change the app made: each bracket render, each clock tick, each table repaint, and asked "which page is active?" each time. The app already knows when it changes page, so it now simply says so. No observer remains in the codebase.
- **F1 help matches the page you're on after a reload.** The app restores your last page when it loads, but the old page-detection was only installed half a second later and never saw that first transition — so reloading straight onto, say, the Tournament page and pressing F1 gave you Setup help until you navigated somewhere else. Fixed as a side effect of the change above.

- **Analytics loads its data in parallel, and stops reloading it when nothing changed.** The Dashboard, Leaderboard, Players and Matches views each walked the finalized tournaments one at a time, waiting for one tournament's matches to come back from the database before asking for the next. They now request them all at once. On top of that, the loaded matches are kept for reuse: flipping the point mode (Original/Current) or toggling the Ranking and Attendance layers only changes how the numbers are *multiplied*, not which matches exist — but every toggle used to re-read everything from the database anyway. Those toggles now do no database reads at all. With a dozen tournaments loaded, rendering the four views drops from 48 reads to 12, and a toggle drops from 48 to none. Same numbers on screen, noticeably less waiting.
- **Analytics notices when you edit a finished tournament.** Analytics keeps the finalized tournaments it has loaded in memory, but nothing told it to let go of them when a match in one of those tournaments was undone or re-entered — something possible through the maintenance workflow for correcting a completed tournament. Analytics could therefore keep showing pre-edit results until the page was reloaded. Completing and undoing a match now clear that cached copy once the change has been written, so returning to Analytics shows the corrected data.

- **Drawing the bracket reads the match history once instead of once per match.** Every match card asks whether its result can still be undone, and that check re-read and re-parsed the tournament's entire transaction log out of localStorage — about 63 full parses per redraw on a 32-player bracket, repeated after every lane assignment, referee change and completed match. The history is now parsed a single time per redraw and shared by all the cards. Same undo indicators, same behavior; the bracket just stops doing the same expensive work sixty-odd times in a row.

- **The status panel no longer re-parses the whole tournament on every save.** `updateTournamentWatermark()` runs after each `saveTournament()` — and it began by re-reading the `currentTournament` record back out of localStorage and `JSON.parse`-ing the entire tournament, purely to display a name, a few counts and a status. It now reads the in-memory tournament object, which is the same data: every writer of that localStorage record serializes it *from* the in-memory object, so the stored copy can never be newer. One full parse of the tournament blob is gone from every save (and every bracket render), and the panel is now consistent with the header's Active Tournament display, which already read the in-memory object. No visible change.

### Undo internals (Phase 6 cleanup)

- **One source for "what's blocking this undo?".** Two separate places worked out whether a completed match could still be undone: one answering yes/no (which decides whether a winner's name is clickable to undo it), the other producing the wording you see on hover and in Match Controls — *"Cannot Undo, blocked by FS-3-1 (live)"*. Both walked the progression table the same way, and they had to be kept in step by hand: when QR completions were added, the same fix had to be made twice, and it was missed in one of them (fixed in v5.1.5). They now share a single `getUndoBlockingMatches()` that returns the blocking matches; one caller checks whether the list is empty, the other turns it into the sentence. Each keeps its own separate rules — read-only tournaments, walkovers, and matches with no undoable result — since those differ. No behavior change: the two implementations were verified equivalent before the merge, and the merged version was checked against the old one across 1,200 randomized tournament states in both formats at every bracket size (32,400 comparisons, no differences).

### Dead code removal (Phase 6)

- **Removed an unused duplicate of the excluded-lanes parser.** `parseExcludedLanes()` in `lane-management.js` was byte-identical to `parseExcludedLanesString()` in `results-config.js` but had no callers anywhere in the codebase. Deleted it; the live `parseExcludedLanesString()` (with its one caller) is unchanged.
- **One source for the developer-mode check.** The same "is developer mode on?" block was inlined three times (twice in the watermark render, once in the late-registration info modal), and each re-parsed the `dartsConfig` localStorage value instead of reading the loaded in-memory config. Extracted a single `isDeveloperMode()` that reads `config.ui.developerMode` — one definition, and it honors the single-source-of-truth principle.
- **One source for the results-table player sort.** The "paid players, ranked first then alphabetical" sort was copy-pasted in three results functions (the results table, the JSON export, and the CSV export). Extracted `getSortedPaidPlayers()`; all three call it. Identical ordering, no behavior change.
- **Referee assign/clear share one path.** Assigning a referee and clearing one duplicated ~45 lines of near-identical follow-up work (record the change, save, re-render, refresh Match Controls). They're one shared tail now, with each case only setting the referee and its history description. Also removed a redundant dropdown refresh that the bracket re-render already covers.

### Chalker

- **The Short Leg Threshold setting now actually reaches the Chalker.** The Config page's "Short Leg Threshold (darts)" lives under the CHALKER section, but until now the Chalker never received it — it judged short legs with its own built-in table while the Tournament Manager awarded the achievement using the configured value, so the on-screen "Short Leg" badge could disagree with what you were actually credited. The threshold is now sent to the Chalker with the rest of the match setup (alongside x01 format and max rounds), so the badge and the award always agree. Standalone Chalker matches (started on the device, not assigned from a tournament) keep using the sensible built-in table, and older QR codes without the new field fall back to it too.

### Design decision — additive-only localStorage schema (4.10 declined)

Item 4.10 proposed adding a `schemaVersion` marker to the localStorage records. Declined: the stored schema is **additive-only** (every change so far adds an optional field with a sensible default when absent), and additive changes are handled by idempotent "missing → default" adaptation at read time, which is skip-proof regardless of how many versions a record predates — so no version marker or migration ladder is needed. A marker only pays off for a *destructive/ambiguous* change (rename a field; change a value's meaning), which the app avoids. This is now a standing principle in `CLAUDE.md` (Development Principles → Data Integrity). Export files keep `exportVersion` because they arrive from any vintage; localStorage evolves in lockstep with the app and does not.

### Files changed

- `js/clean-match-progression.js` — Phase 6: `completeMatch()` persists once at the end of the success path instead of 2–4 times (6.2), with the `isTournamentFinal` computation moved inside the following `try` so a throw can't skip the save; dead `window.commandCenterWasOpen` reopen branch + both clear-the-flag blocks removed (6.2); NewtonDB match + meta writes now invalidate the Analytics cache once both land (6.5)
- `js/newton-history.js` — Phase 6: new `_playerKey(name)` (single definition of the player-name normalization, replacing 20 inline copies) + `_tallyMatchWinLoss(matches, playerMap)` shared by the Leaderboard and Players tab (6.11); `viewBracket()` stashes the prior real `currentTournament` into `_preAnalyticsPreviewTournament` before overwriting (skips re-stashing when the prior is already a preview); Phase 6: new `_matchesByTournament` cache + `_loadMatchesFor()` (`Promise.all`, input order preserved) replacing the four sequential `for … await` match fetches in `renderDashboard`/`renderPlayersTab`/`renderLeaderboard`/`renderAllMatches`, cleared by `_invalidateCache()` (6.5); extracted `_achPoints(stats, p)` helper, replacing 5 duplicated achievement-points formulas; replaced 2 inline base64 visit decodes with `NewtonStats.decodeVisits()`
- `js/main.js` — Phase 6: `showPage()` now calls `setHelpPage(pageId)` (6.4); new `exitAnalyticsBracketPreview()` (stash-restore on preview exit); `autoLoadCurrentTournament()` now copies `_analyticsPreview` so the no-persist guard survives a reload
- `tournament.html` — Analytics back button calls `exitAnalyticsBracketPreview()` instead of `localStorage.removeItem('currentTournament')`; Phase 6: Config CHALKER blurb now notes the short-leg threshold is sent
- `js/newton-db.js` — `saveMatch` single-transaction upsert (TOCTOU fix); `deleteTournament` single cross-store transaction with cursor delete; `importAll` single-transaction batched match upsert with `(tournamentId, matchId)` de-dupe; all three reject on `tx.onabort`
- `js/bracket-lines.js` — Phase 6: three BS-FINAL indicators → one `createBSFinalIndicator`; three nested `createLoserFeedLine` → one module-level helper (z-index parameter); `'Ïnter'`→`'Inter'` font fix; removed 20 bracket-geometry debug logs
- `js/bracket-rendering.js` — Phase 6: undo's `NewtonDB.deleteMatch` calls now invalidate the Analytics cache once the deletes land (6.5); new `getUndoBlockingMatches(matchId, history)` helper, replacing the duplicated downstream-blocking scan in `isMatchUndoable()` and `getDetailedMatchState()` (6.8); new render-pass `_renderPassHistory` memo (primed in `renderBracket()`, cleared in a `finally`) so `isMatchUndoable()` reuses one parsed history per redraw instead of re-reading localStorage per card (6.1 part A); removed the 6 per-render `🎯 Rendering N-player` logs and 1 stray `populateRefereeSuggestions` log; extracted `getDefaultView()` replacing the duplicated zoom/pan defaults in `renderBracket()`/`resetZoom()`; `render32PlayerBacksideMatches` now calls the shared `createBacksideBackground()` instead of an inline copy, and captures each backside round's first-match Y into `positions` for the placement labels; `createBacksidePlacementLabels` case 32 reads those instead of recomputing; `updateMatchReferee` clear/assign paths merged into one shared tail (redundant `refreshAllRefereeDropdowns()` calls dropped)
- `js/tournament-management.js` — Phase 6: `exportTournament()` now reuses `buildTournamentPayload()` (removes a duplicated payload builder) + adds `URL.revokeObjectURL`; filename sanitized at source in `buildTournamentPayload()`
- `js/dynamic-help-system.js` — Phase 6 (6.4): whole-body MutationObserver removed; new `setHelpPage(pageId)` called from `showPage()`
- `js/lane-management.js` — Phase 6: removed the unused duplicate `parseExcludedLanes()`
- `js/results-config.js` — Phase 6: new `isDeveloperMode()` helper (reads in-memory `config`); new `getSortedPaidPlayers()` helper replacing 3 duplicated results sorts
- `js/player-management.js` — Phase 6: late-reg modal uses `isDeveloperMode()` instead of an inline localStorage-parsing IIFE
- `js/tournament-management.js` (watermark) — Phase 6: both developer-mode checks use `isDeveloperMode()` instead of inline IIFEs; `updateTournamentWatermark()` reads the in-memory `tournament` instead of re-reading and re-parsing `currentTournament` from localStorage (6.3), with JSDoc added
- `js/qr-bridge.js` — Phase 6 (6.20): assignment payload now carries `slt` (short-leg threshold); (6.21) note that the QR-detect helpers intentionally differ from the Chalker's
- `chalker/js/chalker.js` — Phase 6 (6.20): `getShortLegThreshold()` helper prefers the assigned threshold, falls back to the built-in table; reads `slt` from the QR payload; (6.21) divergence note
- `chalker/sw.js` — cache bumped to `chalker-v110`
- `chalker/index.html` — `chalker.js?v=13`
- `CLAUDE.md` — added the additive-only localStorage schema-evolution principle (Data Integrity)
- `Docs/CODE-IMPROVEMENT-PLAN.md` — Phase 4 complete (4.3/4.6 done, 4.2 corrected, 4.10 closed); Phase 6 in progress (6.1 part A, 6.2, 6.3, 6.4, 6.5, 6.6, 6.7, 6.8, 6.9, 6.10, 6.11, 6.12–6.20 done; 6.21 closed; 6.1 part B + the renderLeaderboard split declined)

### Migration

No data migration required. The `_preAnalyticsPreviewTournament` key is transient — written and cleared within a preview session, and only ever read when exiting a preview; a value left behind by a hard-closed tab mid-preview is inert and gets reclaimed on the next preview exit. The NewtonMatchDB changes are behavioral only — the schema (stores, indexes, `DB_VERSION`) is unchanged.

---

## **v5.1.5** — Undo the Undone (2026-07-04)

A code-quality release. A full review of the codebase (four parallel deep reviews covering the bracket core, app/state layer, analytics/history/DB, and QR/Chalker/API — plan and findings in `Docs/CODE-IMPROVEMENT-PLAN.md`) produced a six-phase improvement plan. This release ships Phase 1 (correctness bug fixes, ~25 items), Phase 2 (REST API hardening), Phase 3 (the HTML-escaping sweep — XSS hardening plus the apostrophe-in-names bug), Phase 5 (dead code removal, ~950 lines), and most of Phase 4 (persistence & data-integrity hardening — guarded registry reads, storage-full handling, render-race tokens, and import crash-prevention). No new features; the only visible change beyond the fixes is a restyle of the Storage Space dialog.

### Transaction & undo integrity

- **Transaction IDs are now guaranteed unique.** All five mint sites previously used `` `tx_${Date.now()}` ``; `processAutoAdvancements()` completes walkover chains synchronously, so several transactions could share one ID within the same millisecond. Undo looks transactions up by ID — a duplicate could silently strip an *unrelated* match's transaction from history while its board state stayed completed. New shared helper `generateTransactionId()` (timestamp + monotonic counter) in `clean-match-progression.js`, used everywhere.
- **Undo gates now respect QR completions downstream.** The downstream-blocking checks in `isMatchUndoable()` and `getDetailedMatchState()` only blocked on `MANUAL` completions — undoing an upstream match would destroy a Chalker-recorded QR result (legs, averages, achievements) with no warning. All four checks now treat QR like MANUAL.
- **Undo cleans up NewtonDB for consequential matches.** `undoManualTransaction()` deleted the IndexedDB match record only for the target match; rolled-back downstream matches left orphaned records that Analytics kept counting. All rolled-back matches are now deleted from the register.
- **Undo confirmation modal fallback no longer bypasses confirmation.** If the modal elements were missing, the fallback executed the destructive undo directly; it now logs and aborts.
- **Winner-confirmation input listeners no longer leak.** `showWinnerConfirmation()` added anonymous input listeners on every open but removed a function that was never attached; handlers accumulated all session, each closing over a stale match. Named handler, stored on the modal, removed on cleanup and re-open.

### Transaction pruning (export + Developer Console)

- **Pruning matches strictly on `matchId`.** All four pruning sites (three in `analytics.js`, one in the export path) grouped transactions with a `description.includes(matchId)` fallback — `FS-1-1` is a substring of descriptions for `FS-1-10`…`FS-1-16`, so a completed match could claim (and prune) transactions belonging to other, including live, matches: lane/referee assignments and START_MATCH entries. The substring fallback is gone.
- **Transactions without an identifier are skipped** instead of collapsing to an `undefined` key that matched — and dropped — every other id-less transaction.

### Import / export

- **Saved Players are restored on import again.** Import wrote the snapshot to the legacy `savedPlayers` localStorage key; the app reads `playerList`. The feature was silently broken.
- **Old-format detection works on the overwrite path.** `window.isOldFormatImport` was only set by the confirm modal; re-importing over an existing tournament used a stale or undefined flag, which could restore incompatible pre-v4.0 snapshot history (or skip valid v4.0 history).
- **Removed a stale export that threw on every page load.** `window.generateResultsCSV = generateResultsCSV` referenced a deleted function — an uncaught ReferenceError that aborted the remaining `window.*` assignments in `results-config.js`.

### Analytics / History

- **Match detail points use the match's own tournament.** The Points column was computed from whichever tournament was last opened via the register (`_activeTournament`) — wrong `configSnapshot` in Original point mode when opening from the flat Matches tab. The detail builder now receives the match's own tournament record.
- **Cancelled imports no longer fire later.** The Analytics import confirm handler was only removed on click; dismissing the modal left it attached, and confirming a second file imported both. Stale handlers are now replaced on re-wire.
- **Tiebreak legs no longer corrupt three-dart averages.** Legs with `cd === 0` (tiebreak) were credited with a full 501 scored plus three invented checkout darts; they're now excluded, consistent with `extractAchievements()`.

### Chalker

- **Cross-leg undo restores both players' scores.** `restoreFromVisit()` only restored the undone player's score when stepping back into a previous leg; the opponent kept the new leg's starting score, corrupting subsequent bust/checkout validation. `undoLastVisit()` now recalculates both scores from the visit log.
- **Tiebreak and edited-checkout wins reach match history.** Only `completeLeg()` routed through `onMatchComplete()`; the other two completion paths skipped `saveMatchToHistory()`/`clearCurrentMatch()` entirely — no history entry, no Result QR from history, stale `current_match`. Both now route through `onMatchComplete()` (which also gives them the same stay-on-scoreboard behavior as normal wins).
- **Offline PWA actually boots offline.** The page loads `js/chalker.js?v=N` but the service worker cached the unversioned path, and `caches.match()` never matches query-stringed requests — the main script always hit the network. Fixed with `ignoreSearch: true`; the QR scanner libraries (`jsQR.js`, `qr-scanner.umd.min.js`, worker files) are now in `CACHE_FILES` so QR match assignment works offline; `cache.addAll` failures are logged instead of silently failing the install. Cache bumped to `chalker-v109`, script to `?v=12`.
- **Edit-mode "empty Enter deletes the last visit" is reachable** — `handleEnter()` returned early on an empty buffer before the delete branch could run.
- **Tiebreak cancel no longer strands input in an invisible row** — on a full board there is no new-entry cell, so cancel now enters edit mode on the last recorded visit. Undoing out of a tiebreak leg clears the `tiebreak` flag so a leg later won normally isn't misreported.
- **Rematch uses the active match config, not the form.** After a QR-assigned match the form held older manual values; rematch now rebuilds from `state.config`, stripping the QR identity fields (`matchId`/`tournamentId`/`serverId`) so a casual rematch isn't reported as the tournament match.

### Smaller fixes

- `requireLaneForStart` is actually enforced — it warned and continued; it now blocks the start *before* the state change (no stray START_MATCH transaction).
- `stats.shortLegs` initialized as an array at player creation (was `0`, patched lazily elsewhere); `snapshotPlayerStats()` guards legacy numeric values with `Array.isArray()` instead of throwing mid-`toggleActive`.
- Bo1 matches: loser legs max is `0`, not `2` (`match.legs - 1 || 2` falsy-zero bug).
- `advancePlayer()` returns `false` when a destination match lookup fails instead of reporting success.
- Watermark match count excludes walkovers via `isWalkoverMatch()` (the old `player1 !== 'BYE'` compared objects to a string — always true).
- QR result payloads are validated (`Array.isArray(payload.legs)`) *before* the scanner is torn down — a malformed payload previously left the user with no modal and no error.
- Club logo candidates load sequentially in priority order (parallel loading let the last-to-load win).
- `api/upload-tournament.php` reports `overwritten` correctly (`file_exists()` was checked after the write, so it was always true).
- `loadSpecificTournament()` no longer dereferences before its null check; `debugBracketGeneration()` returns after its guard.

### REST API hardening (Phase 2)

Robustness fixes only — the documented security model (no built-in auth; deployers protect exposed instances) is unchanged, and CORS behavior is untouched.

- **The API kill switch actually kills.** `NEWTON_API_ENABLED` was only honored as the exact string `false`; `FALSE`, `0`, `off`, and `no` (any case) now all disable the API. Unset still means enabled (opt-out model preserved).
- **Upload limits.** `upload-tournament.php` rejects payloads over 10 MB (413) before decoding, and requires the data to minimally look like a tournament export (`id`, `name`, `players` array) — no more arbitrary JSON hosted under `/tournaments/`.
- **Optional relay allowlist.** New `NEWTON_RELAY_ALLOWLIST` env var (comma-separated hostnames): when set, `relay.php` only forwards to those hosts; when unset, behavior is unchanged. Documented in DOCKER-QUICKSTART.md and commented examples in both compose files. `CURLOPT_FOLLOWLOCATION` deliberately left enabled — disabling it would break relaying through http→https redirects.

### HTML-escaping sweep (Phase 3)

Every user-, import-, and QR-derived string that reaches the DOM is now HTML-escaped, and identifiers are no longer passed through inline `onclick` strings. This closes a systemic pattern flagged independently by all four reviews, with three consequences:

- **It broke on legal names today.** A player named `O'Brien` produced a `SyntaxError` in generated handlers like `onclick="addPlayerFromList('O'Brien')"` — registration cards, history checkboxes, and delete buttons all failed on an apostrophe.
- **Stored XSS.** Imported tournament JSON and scanned QR payloads are barely validated, so a crafted player/tournament name (or QR field) could execute script in the app context.
- **HTML-escaping inside a JS string is a false fix.** Several sites wrapped names in an escaper *inside* an `onclick` string; the browser HTML-decodes the attribute before the JS parser sees it, so the escaping evaporated.

The fix, applied uniformly:

- **One canonical `escapeHtml()`** in `main.js` (window-exported), quote-safe so it is valid in both element text and quoted attributes. The Chalker, being a standalone app, carries an identical copy. The weaker `textContent`-based private copy in `analytics.js` (which didn't escape quotes) was removed.
- **Identifiers no longer travel in inline handler strings.** Handlers that carried a name or id were converted to either a per-render numeric-index lookup with one delegated listener, or `data-*` attributes (where HTML-escaping *is* correct, since the value is read via `getAttribute`, never evaluated). `NewtonTable` row clicks now dispatch by integer index into the data array — one change that hardened every table at once and removed its flawed `_escAttr` (which escaped `'` but not `"`). Analytics/History cell buttons use `data-*` attributes with a shared capture-phase delegated listener, so `stopPropagation` still suppresses the row click.

Coverage spans registration and player lists; tournament status, Recent Tournaments (including the server-supplied filename), import messages, and the bracket watermark; match cards, the command center, and referee dropdowns/suggestions across the bracket; the two bracket headers (club + tournament name); the Analytics tables and Developer Console; and the QR result preview, the QR Payload Inspector (which renders deliberately *unverified* scanned payloads), and the Chalker's match-assignment confirm, leg breakdown, and history.

One extra vector was caught during verification: the QR Inspector's JSON-parse-failure branch dumped the raw scanned string into `innerHTML` by string concatenation (missed by the initial template-interpolation sweep) — now escaped. Numeric-id inline handlers (e.g. `openStatsModal(${player.id})`) were left as-is by design; guaranteeing those ids are numeric against crafted imports belongs to a later persistence-validation pass.

### Dead code removal (Phase 5, ~950 lines)

Every deletion re-verified caller-free by grep at delete time (including `onclick` strings in HTML). Highlights:

- **The dead parallel undo implementation** (`undoTransaction`, `undoTransactions`, `clearPlayerFromDownstream`, `hasWalkoverPlayer`, plus orphaned `getUndoneTransactions`/`saveUndoneTransactions`/`clearTournamentCompletionState`) — depended on `beforeState`, which transactions no longer carry, so it *threw if invoked*, and it was window-exported: one console call away from corrupting a live tournament.
- **The dead redo system** (`getRedoableMatches`, `handleRedoClick`, commented UI block, the always-empty `${redoButton}` template slot) — same `beforeState` dependency.
- **`rebuildBracketFromHistory()`** (~185 lines, zero callers) — and corrected `undoManualTransaction()`'s JSDoc, which falsely claimed undo used it.
- The misleading singular `processAutoAdvancement()` (picked the *opposite* winner from the live plural version), `getDownstreamMatches()`, `handleBracketGenerationError()`, `showingAllTournaments`/`toggleTournamentView`, `safeSaveTournament()`, `updateLaneConfiguration()` + `saveConfiguration()` (and their window exports), the dead `config.lanes` bootstrap in lane-management.js, the duplicate window-export block in clean-match-progression.js (strict subset of the surviving one), `.cc-modal-content` scroll no-ops (selector matches nothing), unreachable bracket-size fallbacks, `zoomAnimationFrame`, and invisible placeholder/zero-sized line elements plus the dead `finalsX` parameter in bracket-lines.js.
- **One review finding was rejected during implementation:** `buildMatchSourcesLookup()` (analytics.js) has a live caller in `showMatchProgression`'s "Fed by" line — kept.

### Persistence & data-integrity hardening (Phase 4)

Phase 4's error-state fixes. Deferred to v5.1.6+ by choice: analytics-preview isolation (4.3 — reassessed as a low-priority analytics-only-mode edge), NewtonDB write atomicity (4.6), and the schema-version design item (4.10).

- **A corrupt tournaments registry no longer bricks the app.** New `readTournamentsRegistry()` helper parses `dartsTournaments` inside a try/catch and returns an empty array (with a one-time warning) instead of throwing — one bad value previously broke loading, deletion, and the Recent Tournaments list at once, with `loadRecentTournaments()` failing as a silent unhandled rejection that left the panel blank. Applied to the six read-only sites. The two read-modify-write-back sites (`saveTournamentOnly`, import) kept their plain parses, now covered by the 4.2 save wrap below — a corrupt value there throws and aborts loudly rather than a `[]`-returning reader overwriting the other saved tournaments. `getPlayerList()` is guarded the same way.
- **Player-list import can't brick Registration.** Imported names are filtered to non-empty strings before use; a single number or object in the file previously threw at `name.toLowerCase()` on every subsequent render, breaking the page until localStorage was hand-edited.
- **Server ID generation works over plain HTTP.** `crypto.randomUUID()` is undefined in non-secure contexts (self-hosted `http://<lan-ip>` is a supported deployment); it now falls back to `crypto.getRandomValues()`, so QR payload identity survives HTTP deployments instead of crashing config load.
- **Analytics register tabs show an error instead of a blank panel.** `renderTournamentList()` and `renderAllMatches()` now mirror the dashboard's try/catch-with-placeholder on a DB read failure.
- **Analytics can't paint stale data on rapid toggles.** Each of the three point-mode-sensitive views (dashboard, leaderboard, players) now carries a per-view generation token: a render captures it at entry and bails before painting if a newer render of the same view has started. Rapidly toggling point mode / layers / scope can no longer let a slower, older render win the repaint.
- **Malformed tournament imports fail cleanly instead of crashing at render.** `validateTournamentData` now rejects the crash-inducing shapes — a non-string player name (crashes `name.toLowerCase()`), a match without a string `id` (crashes `id.startsWith('BS-')`) or with a non-object player slot, or non-numeric `placements` — and coerces `completed` to boolean. Scope deliberately stops at crash-prevention: deeper *semantic* validation (are the match ids real bracket slots?) and an export tamper-CRC were considered and declined, because the data is browser-local with no system of record and no auth/secrets — a tampered import only ever affects the importer's own copy (rationale in the plan's Appendix A.3).
- **Running out of storage no longer loses a match silently.** localStorage has a ~10 MB cap; a long-lived instance that never prunes can fill it, and a `QuotaExceededError` mid-save previously threw into the match-completion flow — the completed match lost on reload, no message. Two contained pieces: a **pre-emptive gate** blocks creating or importing a tournament when storage is ≥90% full, with a clear "free up space" message (and the reassurance that deleting a finalized tournament keeps its stats in Analytics); and a **loud-fail wrap** around `saveTournamentOnly()` that, on a quota error *or* a corrupt registry, alerts once and aborts without a partial/overwriting write instead of throwing. The write order (list first) means the most likely failure leaves both keys untouched and consistent. Deliberately *not* done: the original write-reordering / caller-contract surgery — the gate makes a mid-save quota failure rare enough that the 5-line wrap is a sufficient backstop.

### Interface

- **Storage Space dialog restyled to the new landscape dialog system.** Migrated from the old `.modal-content` layout to the `.dlg dlg--wide` component — metrics in a left sidebar, usage bar + guidance in the main column — matching the Reset/Delete dialogs. Reused the existing dialog classes (no new CSS), and removed ~60 lines of orphaned `storage-*` chrome CSS left behind by the migration.

### Files changed

- `js/clean-match-progression.js` — `generateTransactionId()` helper + all mint sites; `advancePlayer()` failure return; `snapshotPlayerStats()` guard; Bo1 loser max; winner-confirmation listener fix; dead undo cluster / singular auto-advance / duplicate export block removed
- `js/bracket-rendering.js` — QR-aware undo gates (4 sites); NewtonDB cleanup of rolled-back matches; undo modal fallback; redo system / `rebuildBracketFromHistory` / unreachable fallbacks / dead else removed; JSDoc corrected; Phase 3 name escaping (match cards, command center, referee dropdowns/suggestions, paid-fee lists)
- `js/tournament-management.js` — strict-matchId export pruning; `playerList` restore key; `isOldFormatImport` on overwrite path; watermark walkover filter; debug-log-before-null-check; `showingAllTournaments`/`toggleTournamentView` removed; new `readTournamentsRegistry()` guarded reader (6 read-only sites); Phase 3: escaped tournament status / Recent Tournaments / import messages / watermark, `loadRecentTournaments` delegated listener (server filename + ids out of onclick); Phase 4.4: deeper `validateTournamentData` crash-prevention (string player names, match shape, numeric placements); Phase 4.2: `storageGateBlocks()` gate at create/import + loud-fail try/catch on `saveTournamentOnly`; Storage Space dialog rebuilt as `.dlg--wide`
- `css/styles.css` — removed ~60 lines of orphaned `storage-*` dialog chrome CSS (after the Storage Space restyle)
- `js/analytics.js` — strict-matchId pruning (3 sites) + id-less transaction handling; Phase 3: removed the private non-quote-safe `escapeHtml` (now uses the canonical one), escaped Developer Console views + `showCommandFeedback`
- `js/newton-table.js` — Phase 3: row clicks dispatch by integer index into the data array (removed `_rowId`-in-onclick and the flawed `_escAttr`) — hardens every table at once
- `js/newton-history.js` — match detail tournament record; import confirm handler cleanup; tiebreak legs excluded from averages; register-tab render error placeholders (`renderTournamentList`/`renderAllMatches`); Phase 3: cell action buttons moved to `data-*` + a shared capture-phase delegated listener (`_wireTableActions`), cell escaping; Phase 4.8: per-view render-race tokens in `renderDashboard`/`renderLeaderboard`/`renderPlayersTab`
- `js/results-config.js` — stale `generateResultsCSV` export removed; dead `saveConfiguration()` removed; `crypto.randomUUID` HTTP fallback for server-ID generation; Phase 3: results-table player-name escaping
- `js/lane-management.js` — `requireLaneForStart` pre-start enforcement; dead bootstrap + `updateLaneConfiguration()` removed; Phase 3: referee `<option>` name escaping
- `js/player-management.js` — `shortLegs: []` init (2 sites); dead `safeSaveTournament()` removed; `getPlayerList()` corrupt-data guard; player-list import string filter; Phase 3: `renderPlayerList` per-render index + delegated listener (the O'Brien fix), name escaping
- `js/qr-bridge.js` — result payload leg validation before scanner teardown; Phase 3: escaped the QR result preview and QR Payload Inspector payload fields, including the raw-string JSON-parse-failure branch
- `js/main.js` — sequential logo loading; Phase 3: canonical quote-safe `escapeHtml()` (window-exported); match-history delegated listener + heading/name escaping
- `js/bracket-lines.js` — invisible placeholders, zero-sized divs, dead `bronzeX` branches, dead `finalsX` parameter removed; Phase 3: escaped the bracket headers (club + tournament name)
- `js/types.js` — stale `rebuildBracketFromHistory` doc line removed
- `chalker/js/chalker.js` — cross-leg undo recalculation; tiebreak/edit-checkout history routing; edit-mode delete; tiebreak cancel/undo; rematch from `state.config`; Phase 3: own `escapeHtml()` + escaped the QR-confirm modal, leg-breakdown headers, leg status, and match history
- `chalker/sw.js` — `ignoreSearch`, scanner libs cached, `addAll` error logging, `chalker-v109`
- `chalker/index.html` — `chalker.js?v=12`
- `api/upload-tournament.php` — `wasOverwritten` captured before write; 10 MB payload cap; tournament shape check
- `api/api-check.php` — normalized `NEWTON_API_ENABLED` kill switch
- `api/relay.php` — opt-in `NEWTON_RELAY_ALLOWLIST` host restriction
- `api/README.md`, `DOCKER-QUICKSTART.md`, `docker/docker-compose.yml`, `docker/docker-compose-ssl.yml` — new env var documented
- `Docs/CODE-IMPROVEMENT-PLAN.md` — new: full review findings and the six-phase plan (Phases 1, 2, 3, 5 and most of Phase 4 shipped — 4.1–4.2, 4.4, 4.5, 4.7–4.9; 4.3/4.6/4.10 deferred; Phase 6 → v5.1.6)

### Migration

No data migration required. The Chalker service-worker cache bump (`chalker-v109`) refreshes installed PWAs automatically on next online launch. Legacy `savedPlayers` localStorage keys are simply no longer written; existing ones are inert.

---

## **v5.1.4** — Pocket Chalker (2026-06-01)

### Chalker — PWA install banner

- **Install prompt** — a banner slides up from the bottom when the browser offers PWA installation: "Install NewTon Chalker for offline use." One tap triggers the native install dialog. Dismiss (✕) hides it permanently. Never shown again after install or dismissal (`chalker_install_dismissed` in localStorage). Never shown inside a TWA (Play Store install).
- **Styling** — dark theme (`--bg-dark`), blue accent border (`--accent-primary`), Manrope font. Respects safe area insets for notch/home bar.
- **CSP-clean** — all logic in `chalker.js`, all styling in `chalker.css`. No inline scripts or styles.

### Files changed

- `chalker/index.html` — install banner markup
- `chalker/js/chalker.js` — `beforeinstallprompt` capture, `installApp()`, `dismissInstall()`, `appinstalled` listener
- `chalker/styles/chalker.css` — `.install-banner`, `.install-btn`, `.install-dismiss` styles

---

## **v5.1.3** — Cannot Operate on Soup (2026-05-29)

Small polish on top of v5.1.2: trimmed a redundant helper line from the Confirm Winner dialog, restructured the Late Arrival info dialog so the actual instructions get visual focus, introduced a reusable `.dlg__note` panel component to the dialog system, and fixed a JSON-LD signal on the landing page that was letting Google (and AI services) treat the GitHub repo as the canonical home of the project instead of `newtondarts.com`.

### Confirm Winner — redundant helper removed

- **Dropped the italic "Winner must have more legs than loser" small-text** from the Final Score row. The same message is already raised dynamically by the form validator when the leg counts are inverted, so the static helper was pure redundancy. Cleaner row layout, one fewer line for the eye to parse.

### Late Arrival info dialog — focus on the actual instructions

- **First paragraph now adapts to the Developer Console setting.** When Developer Console is already enabled in Global Settings, the lead-in collapses to "To register a late arrival, open the **Developer Console** by clicking the version number in the lower-right corner of the Tournament Bracket." When Dev Console is disabled, the original two-step instruction (enable, then open) is shown. Operators who've already opted in no longer have to skip past instructions for a setting they've already configured. `showLateRegInfoModal()` reads `ui.developerMode` from `dartsConfig` (same pattern used elsewhere in `tournament-management.js`) and swaps the paragraph text before pushing the dialog.
- **The two action paragraphs ("use the Late Arrival command" + "the new player will be placed...") are now wrapped in a `.dlg__note` framed panel.** Single shared frame, white background, soft elevation shadow, 1px border, 8px radius — the actual operator steps get visual focus rather than dissolving into a wall of muted prose.
- **Text inside `.dlg__note` is darker than the default `.dlg__desc`** — overridden to the dialog body color `#2a2f3a` (from the muted `#6b7280` helper gray). The frame draws attention to the content inside it; the text needs to read as primary, not as helper prose.
- **New italic caption below the framed panel** — *"The Developer Console is for changes made after a tournament has started — outside the normal workflow."* Explains *why* this operation lives in the Developer Console rather than the main UI, in one line. Stays muted (default `.dlg__desc` gray) so it reads as an aside rather than competing with the framed instructions.

### New dialog component — `.dlg__note`

A small reusable building block added to the dialog system. White background (same as the dialog itself), 1px `#ecedf1` border, 8px radius, 14px/16px padding, and a soft elevation shadow (`0 1px 2px rgba(20,25,35,0.04), 0 4px 12px rgba(20,25,35,0.06)`). Stacked children get automatic 10px vertical spacing via `.dlg__note > * + *`. Scoped color override `.dlg__note .dlg__desc { color: #2a2f3a; }` so framed content reads as primary text. Currently used only by `lateRegInfoModal`; available to any future dialog that needs to group a procedure or callout inside its body.

### SEO / discoverability — JSON-LD canonical signal

- **Added explicit `url` and `codeRepository` to the `SoftwareApplication` JSON-LD** on both `landing.html` (static) and `landing-page.php` (the Docker-served variant). `url` now points at `https://newtondarts.com/` (the canonical site) and `codeRepository` points at `https://github.com/skrodahl/NewTon` (the source). Schema.org's `SoftwareApplication` inherits `codeRepository` from `CreativeWork`, so the GitHub link has a proper home that doesn't compete with the canonical URL signal. The PHP variant additionally fixed a latent bug: `"url"` was previously pointing at `$githubUrl` (the GitHub repo) — actively telling Google the canonical home was on github.com. That has been corrected to `$baseUrl` (with the same conditional-emission pattern used by the existing `og:url` and `<link rel="canonical">` fragments, so the field is omitted entirely when `NEWTON_BASE_URL` is unset rather than emitting an empty string).
- **Why it matters.** The schema was previously silent on `url`. With no explicit signal in the structured data, Google (and AI services that consume the same signals) fell back to link structure, backlinks, and domain authority — all of which favor GitHub by a wide margin. Result: search results and AI summaries kept pointing at `github.com/skrodahl/NewTon` as the project's home rather than at `newtondarts.com`. The HTML-level `<link rel="canonical">` was already correct; the JSON-LD now reinforces it instead of being silent.
- **The existing schema was already clean in other respects** — `offers` block correctly wraps price/currency, `license` is already an SPDX URL (`https://opensource.org/licenses/BSD-3-Clause`). The two new properties were the only meaningful addition needed. Validate with [Rich Results Test](https://search.google.com/test/rich-results) and [Schema Markup Validator](https://validator.schema.org/) after deploy.
- **Realistic expectations.** The structured-data fix tells Google what the canonical URL *should* be; it doesn't override GitHub's domain authority or backlink profile overnight. Correction will be gradual as Google re-indexes and as more references to `newtondarts.com` accumulate.

### Footer easter egg

A small `42` now trails the cheeky "No popups? No cookies!" line in the landing-page footer. Muted brown (`#c9b8a4`), monospaced, no underline, 70% opacity — sits at the edge of attention. On hover it firms up to the standard footer-link brown. Clickable; where it goes is left as an exercise for the reader, with bonus points for anyone who has *The Long Dark Tea-Time of the Soul* within arm's reach. New `.footer-egg` CSS class added next to `.footer-cheeky` in `css/landing.css`; identical markup added to both `landing.html` and `landing-page.php`.

### Documentation

- **`Docs/DIALOGS.md`** — new "The `.dlg__note` panel" section between Buttons and Helpers, with anatomy, when-to-use guidance, and the text-color rationale. Migrated-dialogs table entry for Late Registration Info now reads `default + .dlg__note` so the use of the new component is discoverable from the index.

### Files changed

- `tournament.html` — removed the "Winner must have more legs than loser" `<small>` from the Confirm Winner Final Score row; added `id="lateRegInfoFirstPara"` to the late-arrival lead paragraph; wrapped the two action paragraphs in `<div class="dlg__note">`; added italic caption paragraph below the framed panel
- `js/player-management.js` — `showLateRegInfoModal()` reads `ui.developerMode` from `dartsConfig` and swaps the first paragraph's `innerHTML` between the two predefined static strings before pushing the dialog
- `css/styles.css` — new `.dlg__note`, `.dlg__note > * + *`, and `.dlg__note .dlg__desc` rules added next to `.dlg__desc`
- `landing.html` — `SoftwareApplication` JSON-LD gains `url` (`https://newtondarts.com/`) and `codeRepository` (`https://github.com/skrodahl/NewTon`) properties; footer gains the `42` easter-egg link
- `landing-page.php` — JSON-LD `"url"` corrected from `$githubUrl` to a conditional `$jsonLdUrl` (uses `$baseUrl` when set); new `"codeRepository"` field added; footer gains the `42` easter-egg link
- `css/landing.css` — new `.footer-egg` and `.footer-egg:hover` rules added next to `.footer-cheeky`
- `Docs/DIALOGS.md` — new `.dlg__note` panel section; migrated-dialogs table entry updated for `lateRegInfoModal`

### Migration

No data migration required. CSS-only additions and a single conditional in `showLateRegInfoModal()`; all other dialogs are unaffected.

---

## **v5.1.2** — The Polished Press (2026-05-26)

Tactile press feedback on every button across the app, a new dialog system (`.dlg`) that unifies eleven confirmation/warning/info modals around a small set of shared layouts, a redesigned Tournament Complete celebration with an Olympic tiered podium and decorative garlands, a fix to a long-standing match-achievement attribution bug, and a small Registration-page bug fix.

### Button press feedback

- **Press effect across all buttons** — `transform: translate(1.5px, 1.5px)` on `:active` for `.btn`, `.nav-btn`, `.zoom-btn`, `.help-btn`, `.cc-match-action-btn`, `.achievement-export-btn`, `.tournament-create-button`, `.analytics-reset-btn`, `.analytics-back-btn`, `.close`. Every click now feels tactile rather than flat.
- **Analytics selector buttons excluded by design** — `.analytics-point-btn` and `.analytics-layer-btn` carry their own "active" indicator and don't inherit `.btn`, so they naturally opt out.
- **Removed `!important` from `.help-btn:hover`** — was blocking the unified `:active` rule. Hover now behaves consistently without overrides.
- **Removed obsolete `.celebration-export-btn:active` rule** — `translateY(0)` reset is no longer meaningful with the new shared press effect.

### New dialog system (`.dlg`)

A second modal pattern that sits inside the existing `.modal` backdrop and preserves `pushDialog`/`popDialog` infrastructure. Buttons inside dialogs use the standard `.btn` classes — no separate dialog button styles.

- **Base components:** `.dlg`, `.dlg__title`, `.dlg__desc`, `.dlg__label`, `.dlg__input`, `.dlg__foot` (white card, 10px corner radius, soft shadow, right-aligned footer with subtle top border).
- **Title separator** — `.dlg__title` carries `border-bottom: 1px solid #ecedf1` + `padding-bottom: 14px`, mirroring the footer's `border-top`. Every dialog gets a consistent header / body / footer rhythm automatically; no markup change needed in individual dialogs.
- **Split layout:** `.dlg--split` modifier with `.dlg__grid`, `.dlg__sidebar`, `.dlg__sidebar-label`, `.dlg__sidebar-value`, `.dlg__main` — metadata sidebar on the left, action area on the right.
- **Wide modifier:** `.dlg--wide` adds ~20% width (880px from 720px). For dialogs with three-button footers or richer body content. Stackable with `.dlg--split`.
- **Sidebar widened** — `.dlg__grid` left column 220px → 260px (+18%). System-wide. Improves readability of longer values ("Frontside Round 1") and accommodates sidebar buttons (winner-confirm Edit Statistics).
- **Intent pills:** `.dlg__pill` (amber) and `.dlg__pill--danger` (red) — small uppercase badges at the top of the main area. Pills can be omitted entirely (additive actions, info dialogs) or toggled conditionally (e.g. shown only for legacy-format imports).

### Dialog migrations

Eleven dialogs migrated. Most use `.dlg--split` with the standard tournament-metadata sidebar; some use match metadata instead (when the dialog is about a specific match rather than the tournament); one uses the default single-column layout (pure info); one uses `.dlg--split + .dlg--wide` (winner-confirm needs the extra room for its form and three-button footer).

- **Reset Tournament Confirmation** — amber "Destructive" pill, sidebar shows Name / Tournament Status / Progress / Players. Confirmation input retained with the tournament name shown as placeholder. Markup down from ~47 lines of inline-styled boxes to ~22 lines.
- **Delete Tournament Confirmation** — red "Destructive" pill, sidebar shows Name / Date / Tournament Status / Players. A second paragraph explicitly notes that the tournament's Analytics record is preserved and remains available for review.
- **Import Tournament Overwrite** — amber "Destructive" pill, sidebar shows Name / Date / Tournament Status. "Alternative: rename the imported file to keep both" kept as a secondary paragraph.
- **Tournament In Progress Warning** — amber "Warning" pill, sidebar shows live tournament state (Name / Tournament Status / Progress / Players). Body trimmed from 3 colored tip boxes to 2 paragraphs.
- **Import Tournament Confirmation** — amber "Old format" pill, conditionally shown only for legacy exports. Sidebar shows Name / Date / Tournament Status / Progress / Players. Description condenses the old "Data Safety Guaranteed" box into one sentence; the verbose "What will be imported" list is gone (redundant with file context). Button text toggles "Import Tournament" / "Import Anyway" based on format.
- **Load Tournament Confirmation** — no pill (load is non-destructive). Sidebar shows the tournament being loaded (Name / Date / Tournament Status / Progress / Players). Description varies — when an active tournament exists it names it inline ("Your current tournament *X* will be saved automatically and replaced..."), otherwise reads as a clean "The selected tournament will become active." Replaces the old dual-section layout that duplicated metadata.
- **Undo Match Confirmation** — split layout with *match metadata* sidebar (Match / Bracket / Players) instead of tournament metadata. Amber "Destructive" pill. Body refactored to build DOM via `createElement` / `textContent` rather than `innerHTML` interpolation — **closed a pre-existing XSS hole** where player names were being inserted into HTML via template literals. New helpers `_buildUndoMatchCard()`, `_buildUndoAchievementsSection()`, and `_bracketLabel()` (shared with winner-confirm). The old `createUndoModalContent()` HTML-string builder (~80 lines) deleted entirely.
- **Analytics — Delete Tournament** (`historyDeleteTournamentModal`) — split layout, red "Destructive" pill, sidebar shows Name / Date / Tournament Status (hardcoded "Completed" since Analytics history only contains finalized tournaments). Confirmation input retained with the tournament name in the placeholder.
- **Late Registration Info** — pure info, **uses the default (non-split) layout** — first dialog to do so. No pill, no sidebar. Title + three description paragraphs walking the operator through enabling the Developer Console → opening it → using the "Late Arrival" command. Single "Got it" button.
- **Export Tournament Results** — split layout, standard 5-field tournament sidebar. Conditional amber "Incomplete" pill + warning paragraph (toggled together) for tournaments without finalized rankings. Description condensed to a one-line "Save as {format}: {filename}" with format and filename bold-emphasized. Dropped the verbose "What will be included" list, the separate "Export Details" box, and the "Tournament Complete" reassurance box.
- **Confirm Match Winner** — most involved migration. Uses **split + `.dlg--wide`** (3-button footer + leg-score form needs the extra room). Sidebar carries match metadata (Match / Bracket) plus an "Edit Statistics" section with the two player names as full `.btn` buttons — clicking either opens the stats modal. Dynamic title reads *"{winner} beats {loser}"*. Body shows a Match Progression block (small uppercase header + colored progression lines: green winner, red loser, plain text without tick/bullet markers) and the existing leg-score form. Three-button footer: Cancel / Scan Results QR / Confirm Winner. Body content refactored from `innerHTML` template-literal interpolation (player names XSS hole) to `createElement` / `textContent` throughout. New `_buildWinnerProgressionBlock()` helper. All form validation, snapshot/restore, button wiring, and Enter-key handling preserved unchanged.

### Unified Tournament Status across all sidebars

- **New helper `tournamentStatusLabel(t)`** in `js/tournament-management.js` — returns `Setup` / `Active` / `Completed` for any tournament-shaped object (current, saved in localStorage, or imported file). Prefers the explicit `status` field; falls back to deriving from `bracket + matches` state for older tournaments and old-format imports.
- **Tournament Status now displayed in every dialog's sidebar** that uses `.dlg--split` and is about a tournament (not a specific match). Delete's previous "Setup / Bracket Generated / In Progress" scheme was unified to the same labels as everything else for consistency.

### Tournament Complete celebration — Olympic tiered podium

The Tournament Complete view inside Match Controls now uses an Olympic-style tiered podium:

- **Three tiered colored blocks** under three white cards: gold (160px, center, tallest), silver (120px, left), bronze (88px, right). Block surfaces use metallic gradients matching the medals.
- **Drop shadow on each block** gives them physical depth.
- **20px gap** between podium columns lets each column read as its own piece while the composition still reads as one object.
- **CSS-only metallic medal discs** sit on each card — gold/silver/bronze radial gradients with the rank number inside. Replaces the previous emoji medals (🥇🥈🥉).
- **Uppercase rank labels** — CHAMPION / SILVER / BRONZE — match the sidebar-label style used elsewhere in the dialog system.
- **Decorative SVG garlands** — four wavy strands (muted red / cream / green / black) sweep across the background behind the podium, giving the celebration view a sense of occasion without resorting to emoji.
- **Tournament Highlights row** sits cleanly below the podium — three side-by-side cards on a single white background. No heading (the row's contents speak for themselves).
- **All decorative emojis removed** — title goes from "🏆 X Complete! 🏆" to "X Complete!", the highlights heading is gone entirely.
- **Buttons untouched** — the Tournament Analytics button keeps `.btn` styling and the unified press effect.

### Documentation

- **New `Docs/DIALOGS.md`** — comprehensive reference for the `.dlg` system. When to use which pattern, anatomy, visual structure rules (the title + footer separator pair), the two layouts plus the `.dlg--wide` modifier, sidebar conventions (including the tournament-metadata-vs-match-metadata distinction), the intent pill system with all variants, button rules, helpers, XSS safety, dialog stack integration. Includes the live migration status table and an 8-step migration checklist for the next dialog. Updated through the session as each new dialog was migrated.

### Bug fix — match achievement attribution

A latent bug in the achievement snapshot/diff: the baseline was captured when the Confirm Winner modal opened, which was a loose moment in the lifecycle. If the dialog was opened previously for the same match (and exited via an abnormal path) or if other matches were completed between opens, the snapshot could capture player stats at the wrong instant. The diff at confirm-time would then record achievements from earlier matches onto the current match's transaction — and undoing the current match would incorrectly revert those earlier achievements too.

The fix anchors the snapshot to the **Start Match** event instead:

- New field: `match.preMatchSnapshot = { [player1Id]: snap, [player2Id]: snap }`
- Recorded in `toggleActive()` when the match becomes active. Overwritten on every Start (Esc/Cancel having already rolled back any pending stats from a previous winner-confirm session).
- `showWinnerConfirmation` reads the anchored snapshot via the existing `_completionSnapshot` global — now a pointer into `match.preMatchSnapshot` rather than a session-scoped copy.
- `handleConfirm` and `handleCancel` no longer null the pointer — the snapshot lives on the match object for the next attempt (and stays after completion as audit data).
- Fallback: if a match was started before this lands and has no snapshot, `showWinnerConfirmation` takes one at dialog open — same behavior as the previous approach, so existing in-progress tournaments keep working without migration.

Result: every `COMPLETE_MATCH` transaction's `achievements` field correctly reflects only the achievements added between **this match's** Start and Confirm — no leakage between matches, no contamination across dialog re-opens. Undo now reverts exactly the right set per match.

A follow-up will close the remaining gap: stats added via the bare `openStatsModal` (Results table, Command Center) outside any winner-confirm flow are still untracked per-match. The plan is to attribute them to the player's last completed match transaction. Deferred — see `Docs/UNDO.md` for the rationale.

### Bug fix — late-reg button visibility

- **"Player arrived late?" button now appears immediately when navigating to Registration mid-session**, not only after a reload. `showPage('registration')` was calling `renderPlayerList()` (the saved-players list) and `updateRegistrationPageLayout()` but not `updatePlayersDisplay()` — the function that renders the tournament-players list AND the late-reg button container. Now called as part of the registration page activation.

### Cleanup

- Removed `#resetConfirmationInput` from the `border-radius: 0` cascade selector — the new `.dlg__input` uses rounded corners by design.
- Removed orphaned banner CSS (`.dlg__banner`, `.dlg__banner-dot`, `.dlg__banner-title`, `.dlg__banner--danger`) — used briefly during the Tournament-in-Progress migration before that dialog was converted to split layout for consistency.
- Removed orphaned `.celebration-export-btn` and `.celebration-actions` styles — both classes had CSS defined but were not referenced anywhere in HTML or JS. Also dropped `.celebration-export-btn:active` from the press-effect selector list.
- Renamed `_undoBracketLabel` → `_bracketLabel` — now shared between undo and winner-confirm dialogs.
- Deleted `createUndoModalContent()` (~80 lines of HTML-string building) — replaced by safe DOM construction.
- Removed orphaned `.clickable-player-name` CSS — used briefly during the winner-dialog migration before the sidebar names became proper `.btn` buttons.
- Removed orphaned `.winner-hint` CSS — used briefly during the winner-dialog migration for the "💡 Click player names" hint, before the hint was removed entirely (the sidebar label "Edit Statistics" is self-explanatory).

### Files changed

- `css/styles.css` — unified `:active` press-effect rule; removed `!important` from `.help-btn:hover`; new `.dlg` system (base + `--split` + `--wide` + pills, title separator, 260px sidebar); removed `#resetConfirmationInput` from border-radius cascade; removed banner classes; rewrote tournament-celebration / podium / highlights styles for the Olympic tiered podium with garlands; new `.winner-progression*` and `.winner-stats-stack` classes; removed orphaned `.celebration-export-btn`, `.celebration-actions`, `.clickable-player-name`, `.winner-hint`
- `tournament.html` — replaced eleven modal markups with `.dlg` structure (Reset, Delete, Import Overwrite, Tournament In Progress, Import Confirmation, Load Tournament, Undo Match, Analytics Delete, Late Reg Info, Export, Winner Confirm); rewrote `#tournamentCelebration` for the Olympic podium with inline SVG garlands
- `js/tournament-management.js` — new `tournamentStatusLabel()` helper; `showResetTournamentModal()`, `showDeleteTournamentModal()`, `showImportOverwriteModal()`, `showImportConfirmModal()`, `showLoadTournamentModal()` updated for new sidebar values and all use the helper; conditional pill toggle in import-confirm
- `js/clean-match-progression.js` — `showTournamentProgressWarning()` populates new sidebar fields via the helper; `showWinnerConfirmation()` refactored for safe DOM building (sidebar populated via `textContent`, body built via `createElement`, dynamic title, new `_buildWinnerProgressionBlock()` helper, Edit Statistics buttons wired in sidebar); achievement snapshot anchored to `toggleActive()` (Start Match) via new `match.preMatchSnapshot`; `showWinnerConfirmation`/`handleConfirm`/`handleCancel` read from the anchored snapshot instead of taking a fresh one at dialog open; `_completionSnapshot` global is now a pointer into the match's snapshot rather than a session-scoped copy
- `js/bracket-rendering.js` — `updateCelebrationSubtitle()` drops emojis from the dynamically-set title; `showUndoConfirmationModal()` refactored for safe DOM (new `_buildUndoMatchCard()`, `_buildUndoAchievementsSection()`, `_bracketLabel()` helpers); `handleSurgicalUndo()` updated to pass structured params; old `createUndoModalContent()` deleted
- `js/newton-history.js` — `promptDeleteTournament()` updated for new sidebar IDs (separate name and date, placeholder pattern instead of dynamic prompt `innerHTML`)
- `js/results-config.js` — `showExportConfirmModal()` trimmed: new sidebar IDs, conditional pill + warning toggle, dropped the verbose "what will be included" list builder
- `js/main.js` — `showPage('registration')` now calls `updatePlayersDisplay()` so the late-reg button reflects current tournament state on every navigation
- `Docs/DIALOGS.md` — new
- `Docs/UNDO.md` — updated: replaced the "Planned — Match-Anchored Snapshot" section with implementation notes; reframed the "Completion Modal — Snapshot & Diff" section around the new Start-Match anchor; the manual-entry gap remains in "What This Does Not Solve" (deferred follow-up)

### Migration

No data migration required. Visual/interaction polish only — all functionality, dialogs, and data flows preserved. The remaining 11 modals continue to use the existing `.modal-content` pattern and can be migrated incrementally; `matchCommandCenterModal` (Match Controls) and the Developer Console are intentionally excluded from the `.dlg` rollout — they're content-dense custom layouts.

---

## **v5.1.1** — Somewhat Simpler Selfhosting (2026-05-20)

Docker release. No tournament-app changes. The container's mDNS code never worked reliably on a typical Linux host (avahi conflict) and has been removed entirely. `.local` resolution is now documented as a host-side concern.

### Docker — mDNS removed from container

- **Container avahi/dbus removed** — `avahi`, `avahi-tools`, and `dbus` packages dropped from the Dockerfile. The container no longer attempts to start its own avahi-daemon. mDNS broadcasting belongs to the host OS, not the container.
- **Reason:** with `network_mode: host`, the container's avahi conflicted with the host's avahi (most desktop Linux distros). With port mapping, the container couldn't broadcast at all. There was no configuration where the in-container avahi reliably worked.

### Docker — environment variables

- **`SSL_HOSTNAME` (new)** — replaces `MDNS_HOSTNAME`. Controls the Subject Alternative Name on the auto-generated SSL certificate. The old name still works as a fallback (`HOSTNAME="${SSL_HOSTNAME:-${MDNS_HOSTNAME:-newtondarts}}"`) so existing compose files keep functioning.
- **`HTTP_PORT` (new)** — configurable HTTP listening port (default `2020`). Mirrors the existing `HTTPS_PORT`. Useful for `network_mode: host` deployments avoiding privileged ports.

### Docker — compose cleanup

- **`docker-compose-ssl-mdns.yml` removed** — host-networking variant is no longer needed for mDNS (since mDNS isn't a container concern). Users on this file should switch to `docker-compose-ssl.yml` (port-mapped) or `docker-compose.yml` (minimal).
- **`docker-compose.yml` switched to port mapping** — `network_mode: host` removed from the default compose. Added port mapping `2020:2020` and commented SSL options.
- **`docker-compose-ssl.yml`** — added commented `HTTP_PORT`, `SSL_HOSTNAME` options and a pointer to `Docs/MDNS.md`.

### Docker — nginx templates parameterized

- **`nginx-http.conf`, `nginx-ssl.conf`** — `listen 2020;` replaced with `listen ${HTTP_PORT};`. Entrypoint expands both `${HTTP_PORT}` and `${HTTPS_PORT}` via `envsubst` for both HTTP and HTTPS modes.

### Documentation

- **`Docs/MDNS.md` (new)** — platform-by-platform mDNS setup. macOS (Bonjour built in), Windows (install Bonjour), Linux (avahi-daemon + `allow-interfaces` to exclude Docker bridges). Troubleshooting section covers avahi advertising Docker bridge IPs, HSTS port-change browser cache, and client-side `.local` compatibility (iOS/Android/Windows/Linux).
- **`DOCKER-QUICKSTART.md`** — "Mac / Windows" section renamed to "SSL (All Platforms)". "Linux — SSL + mDNS" section removed. New "LAN Access via `<hostname>.local`" subsection points to `Docs/MDNS.md`. Env var table updated: removed `MDNS_HOSTNAME` (deprecated note in `SSL_HOSTNAME` row), added `HTTP_PORT`. Troubleshooting `https://newtondarts.local Not Reachable` section rewritten.
- **`docker-quickstart.html`** — same edits as the markdown for parity.
- **`llms.txt`** — Docker SSL section updated. Listed `HTTP_PORT`/`HTTPS_PORT`/`SSL_HOSTNAME`, removed `MDNS_HOSTNAME` description, added pointer to `Docs/MDNS.md`. Compose file list updated to reflect removal of `docker-compose-ssl-mdns.yml`.

### Docker — entrypoint cleanup

- **`entrypoint.sh`** — avahi/dbus startup block (lines 8–42 in the previous version) removed entirely. New `HTTP_PORT` variable, renamed `HOSTNAME` derivation to use `SSL_HOSTNAME` with `MDNS_HOSTNAME` fallback. Comment in HTTP-mode branch references `${HTTP_PORT}` instead of hardcoded 2020.

### Third-party licenses

- **`THIRD-PARTY-LICENSES.md` was missing from the Docker image** — `.dockerignore` excluded `*.md`, including the license file. A compliance gap for the bundled MIT (qrcode-generator, QrScanner) and Apache 2.0 (jsQR) libraries.
- **Fix:** new `third-party-licenses.html` ships in the container (HTML isn't `.dockerignore`d), linked from the landing-page footer (`landing.html` and `landing-page.php`) alongside Privacy.
- The markdown stays in the repo as the canonical source.

### Release process

- **`releases/README.md`** — Step 6 expanded to cover both the chalker.js cache buster (`?v=N` query string) *and* the service worker `CACHE_NAME` in `chalker/sw.js`. Both must bump together — without the SW bump, installed PWAs keep serving stale code from offline storage.

### Migration

No migration required for the tournament app. Existing Docker deployments using `MDNS_HOSTNAME` continue to work via the entrypoint fallback. Users on `docker-compose-ssl-mdns.yml` should switch to `docker-compose-ssl.yml` or `docker-compose.yml`; `network_mode: host` is no longer required for `.local` access (the host's avahi/Bonjour handles the broadcast).

### Files changed

- `docker/entrypoint.sh` — removed avahi/dbus startup; added `HTTP_PORT`; `SSL_HOSTNAME` with `MDNS_HOSTNAME` fallback; envsubst expanded to handle both modes
- `docker/Dockerfile` — removed `avahi`, `avahi-tools`, `dbus` packages
- `docker/nginx-ssl.conf` — `listen ${HTTP_PORT};` for the redirect listener
- `docker/nginx-http.conf` — `listen ${HTTP_PORT};` for the main listener
- `docker/docker-compose.yml` — switched from `network_mode: host` to port mapping; removed `MDNS_HOSTNAME` ref; added commented SSL/port options
- `docker/docker-compose-ssl.yml` — added commented `HTTP_PORT`/`SSL_HOSTNAME` options; pointer to `Docs/MDNS.md`
- `docker/docker-compose-ssl-mdns.yml` — **deleted**
- `Docs/MDNS.md` — new
- `DOCKER-QUICKSTART.md` — Linux section removed; LAN access pointer added; env var table updated; troubleshooting rewritten
- `docker-quickstart.html` — parallel edits to the markdown
- `llms.txt` — Docker SSL section updated
- `third-party-licenses.html` — new
- `landing.html` — footer link `THIRD-PARTY-LICENSES.md` → `third-party-licenses.html`
- `landing-page.php` — same footer link update
- `releases/README.md` — Step 6 expanded to cover service worker `CACHE_NAME` bump
- `js/main.js` — `APP_VERSION` → `5.1.1`
- `chalker/js/chalker.js` — `CHALKER_VERSION` → `5.1.1`
- `chalker/index.html` — chalker.js cache buster `?v=8` → `?v=9`
- `chalker/sw.js` — `CACHE_NAME` → `chalker-v106`
- `releases/index.html`, `releases/v5.1.1.html` — release notes
- `sitemap.xml` — `v5.1.1.html` entry

---

## **v5.1.0** — Burgerboy85-rgb to Throw (2026-04-23)

### Analytics — Players Tab

- **Player list** — checkbox + player name. All selected by default. Header checkbox toggles all. Scrollable (70vh desktop, 40vh mobile). No pagination.
- **Split layout** — player list on the left (300px), profile/comparison panel on the right. Stacked on mobile (<1120px).
- **Selection-driven profile panel**:
  - All/multiple selected → comparison table (Player, Played, W/L)
  - One selected → individual profile card
  - None selected → placeholder
- **Cross-view navigation** — Leaderboard row click and Dashboard card click navigate to Players tab with that player focused. Works even if Players tab hasn't rendered yet (pending focus mechanism).
- **Dashboard drill-through** — 180s → Players tab, Highest Checkout → player profile, Shortest Leg → player profile.
- **Player selection persisted** — selection saved to localStorage (`newton_analytics_playerSelection`), restored on reload with stale name filtering.
- **Row click toggles checkbox** — click anywhere on a player list row to toggle selection. Hover effect on all tables.
- **Comparison table via NewtonTable** — sortable, consistent hover and styling.

### Analytics — Leaderboard Export

- **CSV and JSON export** — Export CSV and Export JSON buttons on the Leaderboard. Respects scope, point mode, and layers — what you see is what you export.
- **Shared CSV utility** (`newton-csv.js`) — `NewtonCSV.exportCSV()` and `NewtonCSV.downloadFile()`. Used by both leaderboard export and tournament results export. Refactored `results-config.js` to use the shared utility.

### Documentation

- **Documentation index** — all doc pages listed at the bottom of the User Guide with descriptions.

### Analytics — cache invalidation on finalization

- **New tournament appears without reload** — `NewtonHistory.invalidateCache()` called after tournament finalization completes (after placements and achievement reconciliation). The Analytics tab picks up the new tournament on next navigation without requiring a page reload.

### Navigation — remember active page

- **Page persists across reloads** — the active page is saved to `newton_activePage` in localStorage on every navigation. On reload, the app restores the last visited page instead of always returning to Tournament Setup.

### Global Settings — documentation links

- **Server Settings** header and **Automatically backup tournaments on completion** checkbox now have ℹ️ icons linking to `docker-quickstart.html` and `automatic-backup.html` respectively. Opens in a new tab. Links point to local files — works on both Docker and file-based deployments.

### Referee Suggestions — lane info

- **Lane shown in all suggestion categories** — Recent Losers, Recent Winners, and Recent Assignments now display the lane number when assigned (e.g. `Nick (FS-R1 · Lane 3)`). Helps operators identify who is already at the right board — especially useful for "loser marks" workflows.
- Inspired by [@burgerboy85-rgb](https://github.com/burgerboy85-rgb) — [Discussion #6](https://github.com/skrodahl/NewTon/discussions/6)

### Known issues

- Comparison table does not go full width below 1022px

### Files changed

- `tournament.html` — Players tab split layout, Leaderboard export buttons, `newton-csv.js` script tag
- `js/newton-history.js` — `renderPlayersTab()`, `renderProfilePanel()`, `focusPlayer()`, `togglePlayer()`, `toggleAllPlayers()`, `exportLeaderboardCSV()`, `exportLeaderboardJSON()`, player selection persistence, dirty-flag wiring, dashboard card targets
- `js/newton-csv.js` — new shared CSV/download utility
- `js/results-config.js` — refactored to use `NewtonCSV` for CSV export and file download
- `js/main.js` — save/restore active page via `newton_activePage` in localStorage
- `js/clean-match-progression.js` — `NewtonHistory.invalidateCache()` after finalization chain
- `js/bracket-rendering.js` — lane info added to Recent Losers, Recent Winners, and Recent Assignments in referee suggestions
- `css/styles.css` — `.players-split` flex layout, `.players-list-panel` scroll, `#playersTableContainer` hidden pagination, `.analytics-export-btn`, responsive stacking at 1120px
- `userguide.html` — Documentation index section, Automatic Backup links

---

## **v5.0.15-beta.2** — Offline at the Oche (2026-04-21)

### Documentation

- **Automatic Backup page** — new doc page (`automatic-backup.html`) covering local backup on tournament completion, remote backup to an Analytics instance, the venue-to-cloud workflow, Analytics Mode, and manual fallback. Includes Server Settings screenshot.
- **Cross-links** — userguide.html and docker-quickstart.html link to the new Automatic Backup page.

### Docker

- **Analytics Mode unlock** — undocumented `?tm=1` query parameter unlocks the full TM interface when in Analytics Mode. Enables retroactive achievement corrections.

### Files changed

- `automatic-backup.html` — new documentation page
- `Screenshots/backup.png` — Server Settings screenshot
- `tournament.html` — `?tm=1` query parameter overrides `NEWTON_MODE=analytics`; body class uses `$appMode` variable instead of raw `getenv()`
- `userguide.html` — links to Automatic Backup page
- `docker-quickstart.html` — link to Automatic Backup page
- `releases/README.md` — beta release process, cache buster step, version format note

---

## **v5.0.15-beta.1** — Ka-ZXing! (2026-04-20)

### Chalker — QR Decoder

- **QrScanner (ZXing) replaces jsQR as primary decoder** — the image capture path on iOS/iPadOS now uses QrScanner, a ZXing-based decoder that handles perspective distortion, glare, and screen reflections. jsQR consistently failed on iPad photos of QR codes on screens; QrScanner succeeds even at steep angles and poor lighting.
- **1500px downscale** — all captured photos are downscaled to max 1500px before decoding. Faster and more reliable than full-resolution processing.
- **BarcodeDetector removed from image capture path** — confirmed unavailable on iOS Safari (iPadOS 26). Removed dead code; BarcodeDetector remains in the TM's live camera scanner where it works.
- **"Not set" for missing lane/referee** — the QR confirmation modal now shows "Not set" instead of "undefined" when lane or referee are not assigned.

### Layout

- **Responsive breakpoint** — moved from 1024px to 1120px, covering tablets in portrait mode (e.g. iPad Air at 1080px).
- **Denser desktop tables** — `history-table` cell padding halved from `14px 12px` to `7px 6px`, header padding from `10px 12px` to `5px 6px`, badge cells from `14px 12px` to `7px 6px`. Shows 24 players on a desktop screen.
- **Sticky header fix** — removed `overflow-x: hidden` from `.page` below 1120px, which was creating a scroll container that broke `position: sticky` on table headers.
- **Scope indicator preserved** — the Analytics scope pill was hidden below 1120px because it sat inside `.history-actions` which was set to `display: none`. Fixed by hiding only the `.btn` children instead of the container.

### Files changed

- `chalker/js/chalker.js` — QrScanner as primary decoder in `decodeImageQR()`, 1500px downscale, BarcodeDetector removed from image path, "Not set" for missing lane/ref, version bump to 5.0.15-b.1
- `chalker/index.html` — added `qr-scanner.umd.min.js` script tag
- `chalker/js/qr-scanner.umd.min.js` — QrScanner/ZXing UMD build (~16KB)
- `chalker/js/qr-scanner-worker.min.js` — QrScanner Web Worker (~44KB)
- `chalker/qr-scanner-worker.min.js` — duplicate worker at page root (dynamic import path resolution)
- `Docs/QR.md` — updated decoder chain, library table, reliability notes
- `css/styles.css` — breakpoint 1024px → 1120px (all three media queries); desktop `history-table` td/th/badge padding halved; `.page` overflow-x removed from responsive block; `.history-actions .btn` hidden instead of `.history-actions`

---

## **v5.0.14** — Narrowing the Scope (2026-04-19)

### Navigation

- **Nav underline replaced** — the sliding `::after` pseudo-element (positioned by JavaScript) replaced with per-button `border-bottom`, matching the Analytics tab pattern. Fixes broken underline position when nav wraps to two lines. `updateNavUnderline()` function and resize listener removed.
- **Analytics button on bracket** — added to the bracket nav panel after Config. Navigates to the Analytics tab without leaving the bracket first.

### Mobile Layout (< 1120px)

- **Reduced padding** — container, page, config sections, and Analytics header all tightened for narrow screens.
- **Denser tables** — smaller cell padding, font size, and row spacing across all tables.
- **Compact player names** — 12px instead of 15px in table cells.
- **Header** — smaller title font (1.5rem), hidden clock, reduced padding/gap.
- **Analytics** — description and import/export buttons hidden.
- **Global Settings** — narrower number inputs, compact buttons with nowrap.

### Files changed

- `css/styles.css` — nav underline: removed `.nav::after` sliding indicator, added `border-bottom` on `.nav-btn` and `.nav-btn.active`; `@media (max-width: 1024px)` rules: container/page padding, header title/clock/padding, table density, player name font size override, Analytics description/buttons hidden, config section padding, config button sizing/nowrap
- `js/main.js` — removed `updateNavUnderline()` function, init call, and resize listener
- `tournament.html` — Analytics button added to `.bracket-controls-middle-left`

---

## **v5.0.14-beta.3** — I Can See Clearly Now (2026-04-17)

### QR Scanning

- **Larger QR on TM** — assignment QR cell size increased from 6px to 8px per module. Renders ~360-424px instead of ~270-318px — more pixels per module for the camera to capture.
- **Full-resolution decode on Chalker** — `decodeImageQR()` now tries full resolution first, then retries at 2000px if that fails. Beta.2's 1000px cap crushed QR module detail on iPhone 48MP photos.

### Docs

- **Release notes reorganised** — 86 files moved from `Docs/` to `Docs/ReleaseNotes/`.

### Contributors

- [@burgerboy85-rgb](https://github.com/burgerboy85-rgb) — iPhone 16 Pro Max + iPad Pro testing on iOS 26.4, identified the decode failure pattern

### Files changed

- `js/qr-bridge.js` — QR cell size 6 → 8 in `createSvgTag()`
- `chalker/js/chalker.js` — `decodeImageQR()` two-pass strategy: full resolution first, 2000px fallback
- `Docs/QR.md` — updated decode strategy documentation
- `Docs/ReleaseNotes/` — all release notes moved from `Docs/`
- `releases/README.md` — added pointer to `Docs/ReleaseNotes/`
- `CHANGELOG.md` — updated release notes path reference

---

## **v5.0.14-beta.2** — Picture This (2026-04-17)

### iOS QR Scanning — Fixes

- **Image loading fix** — replaced `URL.createObjectURL()` with `FileReader.readAsDataURL()` for iOS HEIF/HEIC compatibility. Beta.1 failed with "Could not load image" on iPhone 16 Pro Max.
- **User gesture fix** — replaced programmatic `fileInput.click()` with a styled "Take Photo" label button. iOS requires a direct user gesture to trigger file inputs; the programmatic approach failed silently, exposing the raw file input.

### Analytics

- **Date column nowrap** — tournament register date no longer wraps to two lines.
- **Match detail header** — redesigned: match ID and result as the headline (18px), tournament name (bold) · date · time on a single line below.

### Contributors

- [@burgerboy85-rgb](https://github.com/burgerboy85-rgb) — iOS testing on iPhone 16 Pro Max (iOS 26.4.1), identified both beta.1 failures

### Files changed

- `chalker/js/chalker.js` — `decodeImageQR()` switched to `FileReader.readAsDataURL()`; `startImageCapture()` uses label button; `stopQRScanner()` resets label visibility
- `chalker/index.html` — added `<label id="qr-image-label">` styled as "Take Photo" button
- `js/newton-history.js` — match detail header redesign; date column `nowrap`
- `Docs/QR.md` — updated implementation details and beta.1 lessons learned

---

## **v5.0.14-beta.1** — No Score... (2026-04-16)

*Beta — untested on iOS hardware. Feedback welcome via [GitHub discussion #4](https://github.com/skrodahl/NewTon/discussions/4).*

### iOS QR Scanning (Chalker)

- **Image capture for iOS/iPadOS** — on iOS devices, the Chalker uses native image capture (`capture="environment"`) instead of `getUserMedia`, which WebKit restricts. The user takes a photo of the assignment QR; jsQR decodes it client-side. Desktop/Android unchanged.
- **Platform detection** — `isIOS()` detects iPadOS 13+ (reports as "Macintosh") via `navigator.maxTouchPoints`.

### x01 Format

- **Expanded presets** — x01 format dropdown now offers 101 through 1001 in steps of 100 (previously 101, 201, 301, 501). Both TM Global Settings and Chalker manual setup.
- **Custom score** — "Custom score" checkbox reveals a number input (2–1001) for non-standard starting scores. TM shows an amber warning about QR payload size.

### Contributors

- [@burgerboy85-rgb](https://github.com/burgerboy85-rgb) — iOS QR workflow design, x01 format request

### Files changed

- `chalker/js/chalker.js` — `isIOS()`, `startImageCapture()`, `decodeImageQR()`, custom score toggle, updated `startQRScanner()` branching
- `chalker/index.html` — hidden file input, canvas, jsQR script tag, custom score checkbox
- `chalker/js/jsQR.js` — jsQR library copied from TM
- `js/results-config.js` — `initX01Toggle()`, custom score load/save/reset
- `tournament.html` — x01 presets expanded, custom score checkbox and warning
- `Docs/QR.md` — iOS image capture section updated from planned to implemented

---

## **v5.0.13** — The Pointy End (2026-04-16)

### Export / Import

- **Config in exports** — tournament JSON exports (v4.1) now include the full Global Settings (point values, match lengths). Previously this was lost, meaning imported tournaments inherited whatever settings happened to be active at import time.
- **Import respects config** — Analytics import uses the config from the JSON when available. Falls back to current Global Settings for older (pre-4.1) exports.
- **Import warning** — when importing a pre-4.1 export, the confirmation modal shows an amber warning explaining that current Global Settings will be used.

### Analytics

- **Reset button warm accent** — the Lens Reset button lights up with an amber border and warm tint when a filter is active, providing a clear visual cue that the view is scoped.
- **Leaderboard empty cells** — zero-value cells render as blank instead of em-dashes, reducing visual noise and letting actual numbers stand out. Points badge shows 0 explicitly.

### Files changed

- `js/tournament-management.js` — `config` field added to export payload, export version bumped to 4.1
- `js/newton-history.js` — import prefers `t.config` from JSON; import warning toggle; leaderboard empty cells; reset button `.has-filter` class
- `css/styles.css` — `.analytics-reset-btn.has-filter` warm accent styles
- `tournament.html` — `analyticsResetBtn` id on Reset button; `analyticsImportWarning` div in import modal

---

## **v5.0.12** — Clear Sight Lines (2026-04-16)

### Header

- **Active Tournament label** — replaced absolute-positioning hack with proper flex layout. Wide viewports show tournament name and date stacked next to the clock. Narrow viewports (below 1024px) show a centered row with full "Active Tournament:" prefix. Fixes overlap that blocked nav buttons at mid-range widths.

### Analytics

- **Table redesign** — dark header bar (`#1f2937`) with white uppercase labels, sticky on scroll. Rows float as rounded cards with `border-spacing`, subtle shadows, and visible alternating stripes (`#eef0f4`). Hover lifts rows with stronger shadow. Top-16 leaderboard rows use stronger green tones.
- **Badge cells** — Rank (#) and Points columns in the Leaderboard render as badge cells: rounded, tinted inner `<div>` with margin, creating real visual separation from the surrounding row. Works across white, striped, and green rows.
- **Typography** — player names, tournament names, and match tournament links render at 15px bold. Match scores render bold at 15px. Tournament name column expands to fill available width, pushing data columns to the right edge.
- **Pagination buttons** — rows-per-page and page navigation buttons match the Lens preset button style.

### Tournament Leaderboard

- **Visual refresh** — Player Registration leaderboard and statistics modal adopt the same table styling: dark header, row separation, rounded corners, alternating stripes. Compact `8px` padding. Player names and points at 15px bold.
- **Layout fix** — removed legacy hidden column that caused horizontal overflow on all pages.

### Files changed

- `css/styles.css` — table redesign, header layout: dual-layout tournament status, badge cell styles, pagination button styles
- `js/tournament-management.js` — `updateTournamentStatus()` populates both wide and narrow header elements
- `js/newton-history.js` — badge cell class on rank/points columns, 15px bold names/results, tournament column width
- `js/newton-table.js` — `cellClass` support for column config, removed wrapping overflow div
- `js/results-config.js` — removed hidden empty column from leaderboard rows
- `tournament.html` — Active Tournament label moved to `.header-right` with narrow duplicate; removed hidden empty column

---

## **v5.0.11** — (2026-04-15)

### Analytics

- **Import confirmation modal** — replaces the plain confirm() dialog with a styled modal showing tournament name, date, player count, match count, format, and a list of what will be imported.
- **Delete modal shows date** — tournament name now includes the date in parentheses for disambiguation. Confirmation prompt shows the exact name to type.
- **Import Register in analytics mode** — no longer hidden. Register import is safe (merge, not overwrite) and enables full Analytics without requiring tournament JSONs on disk.
- **Half-year presets** — two buttons in the Lens bar for quick date scoping: current half-year and previous half-year. Labels auto-compute from today's date (e.g. 2026H1, 2025H2).
- **Leaderboard sort direction** — first click on a column header now sorts descending (highest first) for all numeric columns. Exception: Best Leg sorts ascending (fewest darts first). Player name sorts alphabetically. Powered by `defaultDir` property on NewtonTable columns.
- **Matches dashboard card** — the Matches stat card links to a flat all-matches view showing every completed match across the current scope, with columns for Match, Player 1, Player 2, Result, Points, Tournament, Date, and Type. Winners bolded.
- **Register sub-tabs with breadcrumb navigation** — the Register view has two sub-tabs: Tournaments and Matches. Drilling into a tournament or match extends the tab bar into a breadcrumb trail: `Tournaments / Måndagscup (2026-03-09) / FS-4-1`. Each segment is clickable. Tournament date shown for disambiguation. Replaces the old back-button navigation.
- **Match detail header** — shows date and match ID (`2026-03-09 · **FS-4-1**`) instead of full timestamp.

### Bugfix

- **Match detail lookup** — fixed stale closure where clicking a match in the per-tournament match list would fail with "Match record not found" after viewing more than one tournament in the same session. The table's row click handler captured the tournament ID from the first call, ignoring subsequent tournaments.

### Files changed

- `tournament.html` — register sub-tabs, breadcrumb bar, import confirmation modal
- `js/newton-history.js` — matches view, breadcrumb navigation, `switchRegisterTab()`, match detail bugfix, half-year presets, import modal, leaderboard sort direction
- `css/styles.css` — breadcrumb styles, sub-tab styles

---

## **v5.0.10** — The Full Picture (2026-04-15)

### Analytics-only mode

- **NEWTON_MODE=analytics** — Docker environment variable. Hides Tournament Setup, Player Registration, Tournament Bracket, and Chalker tabs. Shows only Analytics and a limited Global Settings (Branding + Point Values). Header set by PHP — no flash.
- **CSS-driven mode system** — PHP sets `<body class="mode-analytics">`, CSS handles all visibility. No JavaScript display:none, no flash on load. Clean platform for future modes.
- **Read-only bracket view** — in analytics mode, "Bracket" button on tournament list and "View Bracket" in match list loads the tournament JSON from disk via API. Renders bracket read-only using `currentTournament` with `_analyticsPreview` guard — `saveTournamentOnly()` skips analytics previews. Bracket ID matching via tournament ID (with name+date fallback). "Back to Analytics" clears `currentTournament` and globals.
- **Import Register hidden** — analytics mode hides the Import Register button. Data comes exclusively from disk (shared tournaments).
- **Delete buttons respect settings** — Analytics register delete button only shown when "Allow deleting tournaments" is enabled in Server Settings. In analytics mode, Server Settings is inaccessible, so deletion is impossible by design.
- **Help system disabled** — `initializeHelpSystem()` and `suggestHelp()` skip in analytics mode. No "No active tournament" notifications.
- **Font preloading** — Insignia and Manrope fonts preloaded in tournament.html, eliminating font swap flash on load.
- **Auto-navigate to Analytics** — CSS hides Setup page and shows Analytics immediately; JS confirms via `showPage('history')`.

### Docker Environment Variables

| Variable | Values | Default | Description |
|---|---|---|---|
| `NEWTON_MODE` | `full`, `analytics` | `full` | App mode. `analytics` hides tournament management tabs, shows only Analytics and limited Global Settings. |
| `NEWTON_LANDING_PAGE` | `true`, `false` | — | Enables the landing page at `/`. Existing variable. |
| `NEWTON_DEMO_MODE` | `true`, `false` | `false` | Shows demo banner. Existing variable. |
| `NEWTON_GITHUB_URL` | URL | `https://github.com/skrodahl/NewTon` | GitHub link in UI. Existing variable. |
| `NEWTON_BASE_URL` | URL | — | Base URL for canonical/OG tags. Existing variable. |

### Global Settings

- **Server Settings separated** — Server ID, auto-backup, shared tournament delete, and remote backup settings moved from the User Interface section into their own "Server Settings" pane. Cleaner separation of concerns.
- **"Allow deleting tournaments"** — renamed from "Allow deleting shared tournaments". Now also controls delete button visibility in the Analytics register.

### Analytics

- **Dashboard entry point** — clicking "Analytics" on a tournament (from Recent Tournaments or the podium) now always opens the Dashboard tab, not the last visited tab.
- **Import Tournament button** — in the Analytics header. Import a single tournament JSON file directly into the Analytics register. Works without the API — direct file to IndexedDB. Available in both full and analytics mode.
- **Shared backfill function** — `NewtonDB.backfillTournament(t, config)` extracted to newton-db.js. Single source of truth for importing tournament data into IndexedDB. Used by file import, localStorage backfill ("+ Analytics"), and auto-import from disk.
- **Auto-import from disk** — on every Analytics load, checks for shared tournaments on disk not yet in IndexedDB and imports them silently. One API call + ID checks. New tournaments appear selected.

### Chalker

- **Unlimited darts per leg** — new "Unlimited" option in Max Rounds (both Global Settings and Chalker). Uses value `100` (300 darts) — no special-case logic needed, all existing code works unchanged. QR payload stays within comfortable scanning limits. QR confirm display shows "Unlimited" for values >= 100.

---

## **v5.0.9** — Leader of the Pack (2026-04-14)

### UI

- **Rounded corners on buttons** — `border-radius: 6px` on `.btn`, `.btn-small`, `.player-list-item-actions button`, and `.cc-match-action-btn` globally. Buttons now visually distinct from input fields and panels, which remain flat.
- **Reset filter button** — clears text filter, resets date range, checks all tournaments, and resets scope to all.
- **Register "View →" buttons removed** — row click already navigates to the tournament. Delete button stays. Cleaner table, more space for data columns.
- **Date/time separator** — match timestamps now use middot separator: `2026-03-09 · 21:13`.

### Analytics

- **Unique player count fixed** — Dashboard "Players" card now deduplicates by lowercase trimmed name across tournaments instead of per-tournament player IDs. Drops inflated counts to actual unique players.
- **Points column in Register** — tournament list and match list both show achievement points. Tournament list includes ranking and attendance layers when toggled on.
- **Point mode toggle wired** — Original uses the frozen configSnapshot per tournament; Current uses today's Global Settings. Switching updates all views in real time, including match list and match detail.
- **Ranking and Attendance toggles** — two independent layer buttons alongside the Original/Current toggle. Ranking adds placement points (1st, 2nd, 3rd...). Attendance adds participation points per player. Both on by default — toggle off to drill down to pure achievement points. Tournament-level only; match views show achievement points.
- **Tournament Analytics button on podium** — one click from the celebration screen to Analytics scoped to the just-completed tournament.
- **Placements stored at finalization** — `tournament.placements` now written to IndexedDB at tournament close, enabling ranking point computation in Analytics.
- **Total Points dashboard card** — sums all points across scoped tournaments, respects point mode and layers. Clicks through to the Leaderboard.
- **Leaderboard** — cross-tournament player rankings with full stat breakdown: placement counts (1st through 7-8th), 180s, high outs, short legs, best checkout, best leg (fewest darts), three-dart average (Chalker matches only), matches won/lost, legs won/lost. All columns sortable. Rank and Points columns shaded. Top 16 players highlighted with muted green background (survives reordering). Respects point mode (Original/Current), Ranking, and Attendance toggles. Player dedup by lowercase trimmed name.

### Migration

- Tournaments imported into Analytics before this version do not have placement data in IndexedDB. To enable ranking points for these tournaments: delete from the Analytics register, then re-add via "+ Analytics" in Recent Tournaments.

---

## **v5.0.8** — Choose Your Lens (2026-04-13)

### Landing page

- **Chalker card closer** — "No shouting results across the room." Replaces "No walking results across the room." — more honest.
- **Setup card closer** — "Same steps, same setup, every week." Replaces "No configuration rabbit holes." — communicates consistency over snark.

### Analytics

- **Subtitle rewritten** — "Analytics lets you explore your tournament history. It never alters the underlying results." Replaces the placeholder text. Sets expectation and builds trust.
- **Register column reorder** — Format moved to last position. Tournament, Date, Players, Matches are the primary columns; Format is metadata.
- **Scope selector** — tournament selection that drives all analytics views. Three composable filters narrow the dataset: text filter (AND keyword match on tournament names), date range (inclusive from/to pickers), and per-tournament checkboxes. Each filter only narrows — they never widen. The scope is the intersection of all active filters.
- **Scope indicator** — green pill in the Analytics header shows "Viewing: N of M tournaments" with selection tags. Clickable to navigate to Register. Header checkbox in the tournament table toggles all visible rows.
- **Text filter** — instant keyword filtering on tournament names. Space-separated terms use AND logic. Controls table visibility; checkboxes set scope within the visible set. Persisted across reloads.
- **Date range filter** — from/to date pickers. Inclusive on both ends. Prefilled with the earliest and latest tournament dates in the register. Persisted across reloads.
- **Scope persistence** — scope, text filter, and date range all saved to localStorage. Stale tournament IDs are filtered out on restore.
- **Dashboard respects scope** — all stat cards (tournaments, matches, players, 180s, highest checkout, shortest leg) compute from the scoped tournament set.
- **Dirty flag recompute** — changing scope marks inactive views dirty; they recompute on next switch (lazy).
- **openAnalyticsForTournament() wired** — clicking "Analytics" on a tournament in My Tournaments sets the scope to that single tournament.
- **Cache invalidation** — import and delete operations reset the tournament cache and scope.

---

## **v5.0.7** — The Offline Authority in Darts (2026-04-13)

### Landing page

- **New hero messaging** — "The Offline Authority in Darts" tagline with three-beat subtitle: "Runs locally. Syncs across devices. Builds your venue's stats over time."
- **Story cards** — three bare-text cards between the hero and launch buttons: "Yours. Not theirs." / "Scan. Score. Done." / "Every match remembered."
- **In Action cards rewritten** — new titles, tighter body text, and italic closer lines for every card. Consistent voice: cheeky, confident, practical.
- **Meta tags updated** — description, Schema.org, Open Graph, and Twitter Card all carry the new messaging.

### Documentation

- **llms.txt** — full refresh: new messaging, Analytics section, Server Backup section, updated privacy model, expanded architecture notes and AI tips.
- **architecture.html** — updated Offline-First section (IndexedDB, opt-in server backup); updated single-user limitation (acknowledges shared tournaments).
- **Design system** — feature card restyled (left border accent replaces gradient stripe); dark card and bare card variants added.
- **REST API docs** — relay endpoint, backup modal, auto-backup, Global Settings config table added to both `Docs/REST_API.md` and `rest-api.html`.

---

## **v5.0.6** — Because Backups Shouldn't Be Homework (2026-04-12)

### Server backup

- **Automatic backup on tournament completion** — opt-in via Global Settings. When enabled, the tournament JSON is automatically saved to the local server's `/tournaments/` directory at finalization. Backed up tournaments are available from any computer connecting to the server.
- **Remote backup** — configurable remote server URL with optional basic auth credentials in Global Settings. When configured, auto-backup sends to both the local server and the remote server. Remote upload uses `api/relay.php` — PHP forwards the request server-side, bypassing CORS/preflight issues with authenticated endpoints.
- **"Backup to Server" button** — replaces the old "Upload to Server" file picker. Opens a modal with source choice (Active tournament / From file) and destination info. Uploads to all configured destinations (local + remote).
- **`api/relay.php`** — new endpoint. Accepts a remote URL, optional credentials, and a tournament payload. Forwards via PHP curl with basic auth. Validates URL, passes through the remote server's response.
- **Global Settings — Server section** — Server ID (read-only display), auto-backup checkbox, remote server URL, username, and password fields. All persisted in `config.server`.

### Shared Tournaments

- **Collapsed by default** — Shared Tournaments section starts collapsed with a count header ("Shared Tournaments (13)"). Click "Show All" to expand, "Collapse" to close. My Tournaments stays front and centre.
- **Import / Re-import labels** — tournaments not in localStorage show "Import", tournaments already present show "Re-import".

### Navigation

- **Tab reorder** — Analytics now comes before Global Settings in the navigation bar. Flow: Tournament Setup → Player Registration → Tournament Bracket → Analytics → Global Settings → Chalker.

### Analytics — polish

- **Date format** — all dates in Analytics now use YYYY-MM-DD, consistent with the rest of the app. Match detail timestamps show YYYY-MM-DD HH:MM.
- **Format label** — match list header spells out "Double Elimination" / "Single Elimination" instead of "DE" / "SE". Tournament table keeps the compact abbreviation.
- **Backfill format field** — backfilled matches now include the best-of value from the localStorage match object, enabling the "Best of N" badge on match details.
- **Match detail badges** — "Best of N" and "Manual/Chalker" type badges right-aligned in match header.

### Files changed

- `api/relay.php` — new relay endpoint for remote server uploads
- `js/tournament-management.js` — `buildTournamentPayload()`, `uploadToServer()`, `autoUploadTournament()`, `showUploadModal()`, shared tournament collapse
- `js/clean-match-progression.js` — auto-backup hook at tournament finalization
- `js/results-config.js` — new `config.server` fields
- `js/newton-history.js` — YYYY-MM-DD date formatting, format label expansion
- `tournament.html` — Backup to Server modal, Server Settings UI, nav reorder
- `css/styles.css` — modal ESC support

---

## **v5.0.5** — Read Between the Lines (2026-04-11)

### Analytics — table utility (`newton-table.js`)

- **Reusable sortable/paginated table component**: `NewtonTable.create()` accepts column definitions (key, label, width, align, sortable, render, sortValue), data array, and callbacks. Handles sorting, pagination, and rendering. Every future tabular view gets these features for free.
- **Sortable columns**: click header to sort ascending, click again to reverse. Visual indicator (▲/▼) on active column.
- **Pagination**: rows-per-page selector (10 / 25 / 50 / All) with Prev/Next navigation. Both sort preference and rows-per-page persist to localStorage per table.
- **Column widths**: optional `width` property constrains compact columns (Format, Players, Matches, Result, Type, Date).
- **Applied to Register**: tournament list and match list both use `NewtonTable`. Hardcoded `<table>` elements replaced by container divs populated by the utility.
- **Tournament match count**: `matchCount` field written at finalization and backfill; self-healing on render (computed and persisted if missing). Displayed as a new "Matches" column on the tournament list.

### Analytics — match list and detail improvements

- **Match list columns**: Player 1 and Player 2 with winner bolded; separate "Result" column showing P1–P2 score. Replaces the old combined "Result" column. Fixed widths on Match (130px), Result (80px), Type (90px), Date (110px).
- **Match detail title**: two-line layout — match ID (small, muted, uppercase) above player names (large, bold).
- **Match detail result**: P1 score P2 format — winner bold, loser muted, score in monospace. Replaces "Winner wins X–Y".
- **Match detail stats table**: horizontal leaderboard-style table replaces the old vertical achievements section. Always shown with all columns (Player, Short Legs, High Outs, 180s, Tons), dashes for empty values. Winner bolded. Points column deferred until point mode computation is ready.
- **Match detail badges**: "Best of N" and "Manual/Chalker" badges right-aligned in match header. Type badge moved from left to right.
- **Backfill format fix**: backfilled matches now include the `format` field (x01 format and best-of) read from the localStorage match object. Previously wrote `null`.

### Files changed

- `js/newton-table.js` — new reusable sortable/paginated table component
- `js/newton-history.js` — tournament and match tables use `NewtonTable`; match detail redesign; match count self-healing
- `js/newton-db.js` — `matchCount` written at finalization
- `js/tournament-management.js` — `matchCount` and `format` written at backfill
- `css/styles.css` — `NewtonTable` sort header and pagination styles; match detail title styles
- `tournament.html` — hardcoded table elements replaced by container divs; `newton-table.js` script tag

---

## **v5.0.4** — No Tournament Left Behind (2026-04-10)

### Tournament Setup — Analytics integration

- **Analytics labels**: each completed tournament in "My Tournaments" shows its Analytics status — green "Analytics" label (click to view in Analytics tab) or muted "+ Analytics" label (click to backfill into the registry with confirmation dialog). Active/in-progress tournaments show no label.
- **Backfill to Analytics**: clicking "+ Analytics" imports the tournament meta, all completed non-walkover matches, and per-player achievements into IndexedDB. One click to add historical tournaments to the registry.
- **Backfill per-match achievements**: transaction history snapshots are diffed to derive per-match achievement deltas (180s, high outs, short legs, tons, lollipops) for backfilled tournaments. Even manually scored v4 tournaments get per-match attribution.
- **Player count**: each tournament now shows the player count (e.g. "- 22p"), matching the Shared Tournaments display.
- **Setup page refresh**: navigating to Tournament Setup now refreshes the tournament list, ensuring Analytics labels reflect current state.

### Analytics — achievement reconciliation

- **Shared reconciliation** (`NewtonDB.reconcileMatchAchievements`): after all matches are saved, compares the sum of match-level achievement deltas against authoritative player totals (`tournamentAchievements`). Any remainder — achievements entered outside the match completion dialog — is attributed to the player's last match. Ensures match-level totals always equal tournament-level totals.
- **Used by both paths**: backfill (`addTournamentToAnalytics`) and live finalization (`completeMatch` → `finalizeTournament`) call the same reconciliation function.
- **Shared helpers** in `newton-db.js`: `normalizeStats`, `diffStats`, `hasAnyStats`, `addStats` — used by both backfill history diffing and the reconciliation function.
- **`.stats` wrapper fix**: backfill now writes `tournamentAchievements` in the same `{ name, stats: {...} }` shape as the finalize path — dashboard reads both consistently.

### Analytics — match display fix

- **Removed `status: 'final'` filter on match records**: the Register and Dashboard now show all matches for finalized tournaments regardless of match-level status. The tournament meta `status: 'final'` already gates visibility — filtering matches was redundant and prevented backfilled matches from appearing.
- **Timestamp display fix**: dates now handle both seconds and milliseconds timestamps via `tsToMs()` helper — older localStorage tournaments stored `completedAt` in milliseconds, newer ones in seconds.

### Demo banner

- **Fixed**: "Darts double elimination tournament software" changed to "Darts tournament software" — the banner predated Single Elimination support

### Files changed

- `js/newton-db.js` — shared achievement helpers (`normalizeStats`, `diffStats`, `hasAnyStats`, `addStats`) and `reconcileMatchAchievements()`
- `js/tournament-management.js` — `addTournamentToAnalytics()` with history diffing, delta computation, remainder reconciliation; Analytics labels on tournament list
- `js/clean-match-progression.js` — live finalization calls `reconcileMatchAchievements()`
- `js/newton-history.js` — `tsToMs()` helper; removed `status: 'final'` filter on match records
- `js/main.js` — Tournament Setup page refresh on navigation
- `tournament.html` — player count display in tournament list
- `css/styles.css` — Analytics label styles

---

## **v5.0.3** — The Numbers Start Talking (2026-04-10)

### Release notes

- **`unsafe-inline` wording** — changed "safe" to "acceptable" in v5.0.2 release notes (MD, HTML, index) to better reflect the nuanced security argument

### Tournament Manager — Analytics

- **Analytics control bar** — view tabs (Dashboard, Leaderboard, Players, Register) with green underline indicator; point mode toggle (Original, Current, Custom) as segmented button group
- **Dashboard** — six live stat cards computed from IndexedDB: Tournaments, Matches, Players, 180s, Highest Checkout, Shortest Leg. Cards with drill-down targets are clickable. Data sourced from tournament-level achievements (includes both manual and Chalker entries)
- **Page header** — subtitle added ("Match register and cross-tournament statistics"); Export/Import buttons moved below title for consistency with Tournament Setup and Player Registration
- **Page styling** — outer border and restyled header to match Global Settings
- **Register view** — removed redundant Status column from tournament table (only finalized tournaments are shown)

### Documentation

- **`Docs/ANALYTICS.md`** — new plan document: current state, data foundation (IndexedDB schema, config snapshot detail), architecture (command center, control surface, default views, what-if scenarios, graphs), design principles (immutable data, raw data over pre-computed summaries, no silos, composable/zoomable/connected/evolvable), phased roadmap, table behaviour (pagination, sortable columns, column visibility)

### Global Settings — Default paid

- **New setting**: "New players default to paid" checkbox in User Interface section. When enabled, players added to a tournament are already marked as paid. Removing a player requires toggling to unpaid first — a deliberate two-step safeguard against accidental deletion.
- `config.ui.defaultPaid` (default: `false`) — read by both `addPlayer()` and `addPlayerFromList()` in `player-management.js`.

### QR Code Generator — scan fix

- **Data placement bug**: QR codes with content long enough to use columns past the timing pattern (column 6) were unscannable. The direction calculation used a formula that produced non-integer values after the timing column skip, corrupting data placement for those columns. Fixed by replacing the computed index with a simple counter.

### Chalker

- **Leg averages wrapping** — removed `white-space: nowrap` from `.stats-table td.leg-avgs` so leg averages wrap on narrow phone screens instead of forcing horizontal scroll

---

## **v5.0.2** - Because Every Other One Wants Your Email (2026-04-09)

### QR Code Generator

- **New page**: `qr-generator.html` — standalone QR code generator with transparent background, custom colour, module size, quiet zone, and label with adjustable size. Download as PNG or copy to clipboard. Zero dependencies — built from scratch with Reed-Solomon error correction and Galois Field arithmetic.
- **CSP-clean**: All styles in `css/landing.css`, all JS in `js/qr-generator.js` — no inline code.
- **Linked** from `userguide.html` (Payment Tracking section), `docker-quickstart.html` (Customization section), and `sitemap.xml`.

### Privacy — Security Architecture

- **New section** in `Docs/PRIVACY.md` and `privacy.html`: documents why NewTon's architecture is inherently safe — no write surface, no persistence mechanism for attacks, CSP exfiltration prevention, and why `unsafe-inline` is a non-risk in a system with no database, no cookies, and no accounts.

### Release notes — tagline titles

- All 28 release notes HTML pages updated from `Release Notes vX.X.X — NewTon DC Tournament Manager` to `vX.X.X — {Tagline}`. Each release now shows its unique tagline in Google search results instead of identical boilerplate.

### Files changed

- `qr-generator.html` — new QR code generator page
- `js/qr-generator.js` — new QR engine and UI logic
- `css/landing.css` — QR generator styles
- `Docs/PRIVACY.md` / `privacy.html` — new Security Architecture section
- `userguide.html` — payment QR link to generator
- `docker-quickstart.html` — customization section link to generator
- `sitemap.xml` — `qr-generator.html` added
- All 28 `releases/*.html` files — `<title>` tags updated to tagline format

---

## **v5.0.1** — Game Shot, and the Match! (2026-03-31)

The complete TM ↔ Chalker loop: match assignments travel to the Chalker via QR, results travel back the same way. Analytics tab persists every Chalker match to IndexedDB. Docker HTTPS and mDNS built in. See [Docs/ReleaseNotes/RELEASE-NOTES-v5.0.1.md](Docs/ReleaseNotes/RELEASE-NOTES-v5.0.1.md) for the full story.

### Changes from beta.9 to stable

- **Analytics tab** — "History" tab label renamed to "Analytics" (`data-page` attribute and internal `id` unchanged)
- **User guide** — comprehensive accuracy review; QR workflow section renamed to "Chalker QR Workflow" and expanded with "Sending Results Back" subsection covering the Chalker → TM result QR flow
- **Landing page** — Chalker App and Match Controls card text updated to describe the full QR loop; screenshot alt texts updated to match current screenshots
- **Docker quickstart** — image tag updated from `5.0.1-beta.9` to `:latest` in all compose files; image tag callout note simplified

---

## **Docker Quick Start — full rewrite** (2026-03-31)

`docker-quickstart.html` and `DOCKER-QUICKSTART.md` rewritten around three self-contained setup options (Mac/Windows SSL, Linux SSL + mDNS, Behind a Reverse Proxy), each with a ready-to-use compose file. Docker Hub as primary image, GHCR commented as alternative. Beta image tag (`5.0.1-beta.9`) called out explicitly for the SSL setups. Environment variables moved to a reference table. `localhost only` binding explained with a compose example. `docker compose up -d` instruction added to each setup option.

---

## **Docker image cleanup** (2026-03-30)

`.dockerignore` optimized — reduced image size. `docker/` directory removed from the web root via `RUN rm -rf /var/www/html/docker` in the Dockerfile — build context still includes it (needed for `COPY` instructions), but it is not present in the final image.

---

## **v5.0.1-beta.9** - Scan Anything, Know Everything (2026-03-30)

### QR scanning — jsQR fallback for desktop browsers (Tournament Manager)

`BarcodeDetector` is unavailable on Windows Enterprise editions missing the Media Feature Pack. Added `jsQR` (v1.4.0, ~250KB, zero dependencies) as a fallback in the Tournament Manager (`js/qr-bridge.js`) — when `BarcodeDetector` is absent, video frames are decoded via canvas + jsQR. Error message changed from "Use Chrome or Edge" to a more accurate message. Library added to `lib/jsQR.js`.

The Chalker does not include this fallback — it runs exclusively on mobile and tablet devices where `BarcodeDetector` is always available on Chrome for Android and Safari for iOS.

### Result QR preview — explains why completion is unavailable

When a scanned result QR cannot be applied (wrong tournament, wrong server, match not live, match not found, already completed), the preview now shows a specific explanation above the Close button instead of silently offering only Close.

### Lollipop counter — conditional per player

The lollipop +/− counter in the QR result preview is now hidden entirely when no player had a visit scoring 3 (a lollipop is impossible without a score of 3). When only one player had a visit of 3, only that player's counter is shown — the other cell shows "—". Applies to both the normal result preview and the QR Payload Inspector.

### Release notes — inline styles removed

Download button inline `style` attributes (`margin`) replaced with CSS classes (`btn-download-top`, `btn-download-bottom`) across all 27 release notes files. Fixes margin being silently stripped by the strict CSP on the deployed site.

### Release notes — "Latest release" link

Five versioned release notes pages (`v5.0.0.html`, `v5.0.1-beta.4` through `beta.7`) were missing the "Latest release" link at the top of their Previous Releases list. Added.

### Demo banner — link order

`newtondarts.com` link moved before "View on GitHub" in the Docker demo site banner (`tournament.html`).

---

## **v5.0.1-beta.8-patch** - Default mDNS hostname changed to `newtondarts` (2026-03-29)

Default `MDNS_HOSTNAME` example changed from `newton` to `newtondarts` throughout `DOCKER-QUICKSTART.md` and `llms.txt`. Container reachable as `newtondarts.local` in the documented default configuration.

---

## **v5.0.1-beta.8** - History, Properly Kept (2026-03-29)

### Undo Dialog: Source Awareness

The undo confirmation now shows whether a match was completed via Chalker or Manual entry. Chalker matches show a green info line ("Achievements were recorded automatically from Chalker visit scores."). Manual matches show an amber warning. Source label also appears in the match score line: e.g. "Frank wins 1–0 (Chalker)".

### Tons Fix

`NewtonStats.extractAchievements()` used `if / else if` — a 180 was counted as a 180 but not as a ton. Fixed to two independent checks: any visit ≥ 100 increments `tons`, any visit of exactly 180 also increments `oneEighties`.

### QR Results Button — Placement and Visibility

Scan Results QR moved to footer of Confirm Match Winner dialog (amber glow). In Match Controls, moved to single bottom row (Leaderboard | Scan QR Results | Close); magnifying glass removed. Button hidden by default — only appears when tournament is active and live matches exist.

### History: Delete Tournament

Delete button added to each tournament row. Requires typing the exact tournament name in a confirmation modal before the delete button enables. All match records and tournament meta permanently removed.

### History: Import Fix

`importAll()` previously caused a ConstraintError on the `tournamentMatch` unique index when records for existing tournaments were already in the DB, silently rolling back the entire import. Rewritten as per-record upsert: look up each match by `(tournamentId, matchId)`, overwrite if found, add if new. Unrelated records untouched.

### Help System

Tournament bracket help updated with QR info. New History page help section (tournament list, match detail, export/import). History header ℹ️ icon added.

### Bug Fixes

- `deleteTournament()` called `.delete(meta.id)` — tournaments store uses `tournamentId` as keyPath. Fixed to `.delete(tournamentId)`.
- Import catch block crashed on null `tx.error`. Error display now null-safe.

---

## **v5.0.1-beta.7** - Secure by Default (2026-03-29)

### Docker SSL Support

Two supported paths: auto-generated self-signed cert (`SSL_ENABLED=true`, 30-year expiry with SAN), or real cert via reverse proxy. HTTPS port configurable via `HTTPS_PORT` (default: 443). Port 2020 redirects to HTTPS when SSL is active. Works on all platforms.

### mDNS — newton.local

Avahi (mDNS/Zeroconf) broadcasts the container on the LAN. Devices can reach it at `newton.local` (or a custom name via `MDNS_HOSTNAME`) without DNS configuration. Requires `network_mode: host` — Linux only (not supported on Docker Desktop for Mac/Windows).

### Docker Compose Files

Two new SSL compose files: `docker-compose-ssl.yml` (port mapping, all platforms) and `docker-compose-ssl-mdns.yml` (host networking + mDNS, Linux only).

### Bug Fixes

- `gettext` (provides `envsubst`) missing from Dockerfile — added to `apk add`
- nginx template files auto-loaded by nginx when placed in `http.d/` — moved to `/etc/nginx/`
- `ssl_session_cache` conflict with Alpine's base `nginx.conf` — removed from server block

---

## **v5.0.1-beta.6** - The Record Books Open (2026-03-28)

### NewtonMatchDB — Global Match Register

A new IndexedDB layer (`js/newton-db.js`) persists every non-walkover match completion across all tournaments. Write at completion, delete on undo, finalize at tournament close. Each record includes visit scores, achievements, first starter, format, and timestamps.

### History Tab

New **History** nav item with three-panel read-only view: tournament list (finalized only) → match list → match detail with visit scores and achievements. Export/import the full DB as JSON.

### Match Detail Modal — Setup Page

Non-walkover completed match cards in Tournament Setup → Match History are now clickable, opening an inline modal with full match detail.

### Tons Fix

`NewtonStats.extractAchievements()` now counts visits ≥ 100 as tons (including 180s). Label "Tons (100–179)" corrected to "Tons".

### QR Results Button Redesign

Moved to its own row above Leaderboard/Close in Match Controls footer, with orange live-match glow. Hidden when tournament is completed.

### Bug Fixes

- Match Controls not refreshing after QR completion (wrong dialog check)
- Match detail back button not wiring correctly (missing id)
- QR Results button shown after tournament completion
- QR Results button shown when no live matches

---

## **v5.0.1-beta.5** - The Loop Closes (2026-03-28)

### Complete match from result QR

Scanning a Chalker result QR for a live match now offers two completion buttons alongside the familiar score preview:

- **Score only** — declares the winner and updates the bracket; no achievements applied
- **Score + achievements** — extracts 180s, tons, high outs, and short legs automatically from the raw visit scores via `NewtonStats`, records them in the transaction, and applies them to both players' leaderboard stats

The completion buttons appear only when the scanned match is live in the current tournament. Completed, pending, or mismatched matches show Close only.

### NewtonStats — achievement extraction from raw visit scores

A new pure-function module (`js/newton-stats.js`) extracts achievements directly from the Chalker's base64-encoded visit score payload:

- **180s** — visit score exactly 180
- **Tons (100–179)** — visit score 100–179
- **High outs** — last visit of a won non-tiebreak leg with checkout score ≥ 101
- **Short legs** — won non-tiebreak legs completed within the Short Leg Threshold (configurable in Global Config → Chalker, default 21 darts)

### Lollipop counter

Lollipops cannot be auto-detected from scores alone (a score of 3 is ambiguous). The preview dialog includes a manual +/− counter per player, styled to match the Statistics modal.

### QR-completed matches are now undoable

QR completions (`completionType: 'QR'`) are now treated identically to manual completions for undo purposes. Previously they were blocked by a filter that only accepted `'MANUAL'` — fixed in both `isMatchUndoable()` and `getMatchCompletionState()`.

### Match length expanded to Bo1–Bo21

All match configuration selects (SE and DE, in both the TM and the Chalker) now offer odd-numbered best-of values from 1 to 21. The Chalker's win condition is purely `Math.ceil(bestOf / 2)` — no changes to game logic were required.

### Max Rounds shows dart count

The Max Rounds selector in Global Config → Chalker now labels each option with its dart equivalent: "13 (39 darts)".

### Files changed

- `js/newton-stats.js` — new module: `decodeVisits()`, `extractAchievements()`, `hasAny()`
- `js/qr-bridge.js` — `showResultQRPreview()` now checks match state and renders achievements section with lollipop counters; `applyQRResult()`, `applyAchievementsToPlayer()`, `qrIncrementLollipop()`, `qrDecrementLollipop()`; `handleQRInspectorPayload()` also offers completion when match is live
- `js/bracket-rendering.js` — `isMatchUndoable()` and `getMatchCompletionState()` accept `completionType === 'QR'`
- `js/results-config.js` — `shortLegThreshold: 21` in `DEFAULT_CONFIG.legs`; wired to `chalkerShortLegThreshold` input
- `tournament.html` — `chalkerShortLegThreshold` input in Chalker config; max rounds options with dart counts; Bo1–Bo21 for all match selects; `#qrResultPreviewActions` div; `newton-stats.js` script tag
- `chalker/index.html` — best-of select extended to Bo21

---

## **v5.0.1-beta.4** - Stats Don't Lie (2026-03-28)

### Achievements recorded in the match completion transaction

Every completed match now records exactly which achievements were entered during the completion session. When the Confirm Match Winner modal opens, a snapshot of both players' stats is taken. If the operator clicks a player name to enter achievements via the Statistics modal, the delta between snapshot and confirmed state is written to the `COMPLETE_MATCH` transaction's `achievements` field.

### Cancel & revert achievements

If achievements are added during a completion session and the operator cancels, the Cancel button updates to **"Cancel & revert achievements"** — making the consequence explicit. On cancel (including ESC), player stats are restored to their pre-session state. Nothing is committed until "Confirm Winner" is clicked.

### Undo match + achievements

The undo dialog now shows which achievements were recorded for the match being undone (when present). Two choices are offered:

- **Undo match** — resets bracket state only; achievements remain on the leaderboard
- **Undo match + achievements** — resets bracket state and removes exactly the recorded achievements from both players' stats

The unconditional warning about manually entered achievements remains, since achievements entered outside the completion session are never in the transaction.

### Live achievement summary in the completion modal

As achievements are entered during the session, a summary box appears in the completion modal showing what has been recorded for each player — before "Confirm Winner" is clicked. The summary updates each time the Statistics modal closes.

### Files changed

- `js/clean-match-progression.js` — `_completionSnapshot`; `snapshotPlayerStats()`, `diffPlayerStats()`, `restorePlayerStats()`, `renderCompletionAchievements()` helpers; `showWinnerConfirmation()` snapshots on open, restores on cancel, diffs on confirm, clears summary in cleanup; `openStatsModalFromConfirmation()` updates Cancel label and renders summary; `completeMatch()` accepts `achievements` param
- `js/bracket-rendering.js` — `rollbackAchievements()`; `showUndoConfirmationModal()` with `onConfirmWithAchievements`; `handleSurgicalUndo()` wired with achievements callback
- `tournament.html` — `#completionAchievementsSummary` container in `winnerConfirmModal`; "Undo match + achievements" button in `undoConfirmModal`
- `css/styles.css` — `.completion-achievements-box`, `.completion-achievements-title`, `.completion-achievement-row`
- `Docs/UNDO.md` — updated to reflect complete design

---

## **v5.0.1-beta.3** - The Eyes Have It (2026-03-27)

### Tournament Manager reads result QRs

The QR round-trip closes. The Tournament Manager can now scan a result QR generated by the Chalker. Two entry points:

- **Confirm Match Winner modal** — "Scan Result QR" button sits in the Final Score header row. Camera opens, BarcodeDetector scans, CRC verified, tournament and server IDs checked. On success: decoded result preview with visit scores per leg.
- **Match Controls footer** — "QR Results" button opens the same scanner without a pre-selected match. The match ID is resolved from the payload itself.

Both paths show the same result preview: match ID, format, winner, leg-by-leg visit scores (base64 decoded), and checkout darts per leg.

### QR Payload Inspector in Developer Console

A new **QR Payload Inspector** command scans any NewTon QR — assignment or result — and displays the full raw payload with a pass/fail check for every field: CRC, type, tournament ID, server ID, match found. The current TM's tournament ID and server ID are shown at the top for direct comparison. Never blocks on validation failures — always shows what arrived.

### Files changed

- `tournament.html` — Scan Result QR button in `winnerConfirmModal` Final Score header; `winnerConfirmModal` widened to 800px; QR Results button in Match Controls footer; `qrResultScanModal`; `qrResultPreviewModal`; QR Payload Inspector link in Developer Console Commands
- `js/qr-bridge.js` — `openResultQRScanner()`, `stopResultQRScanner()`, `handleResultQRPayload()`, `showResultScanError()`, `decodeVisitScores()`, `showResultQRPreview()`; `openQRInspector()`, `handleQRInspectorPayload()`
- `js/clean-match-progression.js` — `data-match-id` set on scan button in `showWinnerConfirmation()`
- `js/analytics.js` — restore function added to `analyticsModal` `pushDialog` call (fixes Dev Console return after sub-modals)
- `css/styles.css` — `.qr-result-header`, `.qr-result-match`, `.qr-result-winner`, `.qr-result-legs`, `.qr-visits`
- `docker/nginx.conf` — `camera=(self)` for `location ~ \.php$` (enables `getUserMedia` in Docker deployment)

---

## **v5.0.1-beta.2** - Nobody Leaves the Oche (2026-03-27)

### Chalker: scoreboard is now home

A winning checkout no longer transports you to the Match Complete stats screen. The scoreboard stays — showing the final state, with a green banner declaring the winner. The match is saved to history immediately. From the completed scoreboard:

- **STATS** — opens the full stats view (averages, score ranges, leg scoresheets)
- **NEW** — settings modal to start the next match (pre-populated with previous settings)
- **HISTORY** — browse previous matches; back returns to the scoreboard

### Stats screen: back arrow and Result QR

The stats screen now has a back arrow in the header, consistent with the history detail screen. For QR-assigned matches, a full-width **Result QR** button appears at the bottom — prominent and easy to find.

### Winning leg locked after commitment

Scores in the winning leg can no longer be edited after the checkout is confirmed. Consistent with how all completed legs behave — the checkout modal's Cancel button is the designed moment of regret.

### QR badge in match history

QR-assigned matches are marked with a **QR** badge in the history list.

### Files changed

- `chalker/js/chalker.js` — `onMatchComplete()` stays on scoreboard and saves to history; `completeLeg()` calls `onMatchComplete()`; `showEndScreen()` no longer saves to history; STATS key routes to `showEndScreen()` when match is complete; `startEditingVisit()` blocked when `matchComplete`; `historyBack()` calls `updateDisplay()` for completed matches; `updateIdleDisplay()` hides banner; QR badge in `renderHistoryList()`
- `chalker/index.html` — `#match-complete-banner`; end screen back arrow in header; Result QR as full-width bottom button; end screen action buttons (Rematch, New Match, History) removed
- `chalker/styles/chalker.css` — `.match-complete-banner`, `.btn-full`, `.qr-badge` styles
- `chalker/sw.js` — version bumped to `chalker-v105`

---

## **v5.0.1-beta.1** - The Round-Trip Begins (2026-03-26)

### Chalker generates result QR on Match Complete

When a match was started from a TM assignment QR, a **Result QR** button appears on the Match Complete screen. Tap it — a modal shows the signed result QR code. The TM operator scans it to record the result without typing anything.

The result payload carries raw visit scores (base64-encoded per player per leg), leg winners, checkout dart counts, and all match identification fields (`mid`, `tid`, `sid`) echoed back from the assignment. The TM derives all statistics from the raw scores.

Tiebreak legs are encoded correctly: `cd = 0` signals a tiebreak (no checkout visit); `legs[].w` records who won the deciding round.

For matches started manually (no QR), no Result QR button appears — the IDs needed for TM routing are only present in QR-assigned matches.

### Result QR also accessible from match history

QR-assigned matches retain the result QR in Chalker history. A **Result QR** button appears at the bottom of the match detail screen for any QR-assigned match — so a missed scan can always be recovered later.

### Canonical links added to all pages (SEO)

`<link rel="canonical">` tags added to all 25 HTML pages, pointing to `newtondarts.com` (no `www`). Fixes a Google indexing issue where `www.newtondarts.com` was being treated as the canonical origin. Directory URLs use a trailing slash (`https://newtondarts.com/releases/`). `releases/README.md` updated with canonical link instructions and template.

### Chalker info bar: lane suppressed when unassigned

When a QR-assigned match has no lane set in the TM, the Chalker info bar previously showed "Lane undefined". Now it shows nothing for lane — only `Leg N of M` and `Ref: name` when present.

### CSP fix: inline style removed from leg average highlight

Leg average highlighting for the first-throwing player used an inline `style` attribute, blocked by the server's `style-src 'self'` Content Security Policy. Replaced with a CSS class (`.leg-avg-first`).

### Landing page: poster hero and quickstart infographic

The hero image on `landing.html` / `landing-page.php` is replaced with the NewTon DC retro poster (`newton-poster-throw.jpg`) — calmer, stronger brand statement, consistent with OG/social card graphics.

A quickstart infographic (`quickstart.jpg`) is added to the Get Started section, above the User Guide card. Clicking it opens the lightbox for a full-size view. The magnifying glass badge appears on hover.

### User guide: download link points to releases page

The Download step in `userguide.html` now links to `/releases/` instead of the GitHub releases page.

### Files changed

- All 25 HTML pages — `<link rel="canonical">` added to each
- `releases/README.md` — canonical link instructions added as Step 3; HTML template updated
- `chalker/lib/qrcode-generator.js` — new file; QR generation library (copy from TM's `lib/`)
- `chalker/index.html` — Result QR button on end screen; `#result-qr-modal`; Result QR button in history detail; `qrcode-generator.js` script tag; "Tournament Manager" in place of "TM" in QR hint text
- `chalker/js/chalker.js` — `buildResultPayload()`, `showResultQRModal()`, `uint8ToBase64()`; show/hide Result QR button in end screen and history detail; lane undefined fix in `startMatchFromQR()`; inline style replaced with `.leg-avg-first` class
- `chalker/styles/chalker.css` — `.leg-avg-first` and `.result-qr-code` styles
- `chalker/sw.js` — version bumped to `chalker-v104`

---

## **v5.0.0** - The Revolution Will Be Scanned (2026-03-24)

### Referee shown everywhere

The referee name now appears in the QR modal subtitle (`Harry vs Bob · Lane 1 · 501 Bo3 · Ref: Charles`) and in the Chalker match info bar (`Lane 2 · Leg 1 of 3 · Ref: Anthony`) for QR-started matches.

### Chalker link in Tournament Manager nav

A **Chalker** link at the end of the TM navigation row opens the Chalker in a new tab. Works in both local file and served deployments (`chalker/index.html`).

### Footer link to newtondarts.com

"NewTon DC Tournament Manager" in the TM footer is now a link to [newtondarts.com](https://newtondarts.com), styled to match the surrounding text.

### Camera permission fix — Permissions-Policy header

The Chalker QR scanner was blocked by a `Permissions-Policy: camera=()` HTTP header set by the Docker nginx configuration. Fixed by changing `camera=()` to `camera=(self)` in the `/chalker/` location block.

Users running behind a reverse proxy (e.g. Nginx Proxy Manager) must also override the header at the proxy level — NPM sets its own `Permissions-Policy` that overrides the container's nginx headers. See the Docker Quick Start guide for the required NPM custom nginx snippet.

### Camera constraint: back camera preferred

`getUserMedia` constraint updated to `{ facingMode: { ideal: 'environment' } }` — prefers the back camera on mobile devices while falling back gracefully if unavailable. An earlier change to `{ video: true }` had caused the PWA to default to the front/selfie camera.

### Chalker info bar simplified

x01 format (e.g. `501`) removed from the match info bar — it's already shown in the large score display above. Info bar now reads `Lane 2 • Leg 1 of 3 • Ref: Anthony` for QR-started matches, and `Leg 1 of 3` for manually-started matches.

### QR — Lane & referee no longer required

The QR modal no longer blocks when lane or referee is unassigned. Both fields are included in the payload when present and omitted when not. The QR modal subtitle adapts dynamically — showing only the fields that are set. Decision documented in `Docs/QR.md`.

### Dynamic help system updated

Context-sensitive help (`dynamic-help-system.js`) updated for v5.0.0 features: QR button in Match Controls, Chalker nav link, Single Elimination round names in Match Format Config, Chalker settings (x01 Format, Max Rounds), and QR integration note in Lane/Referee section.

### User guide — Chalker QR Assignment section

New section in `userguide.html` between Running Matches and Results & Export. Covers generating the QR, scanning in the Chalker, the confirmation screen, configuration, and browser/camera requirements.

### Landing page — Chalker card rewritten and moved

Chalker showcase card rewritten to lead with the QR assignment flow instead of standalone features. Moved from position 7 (last) to position 2 (after Bracket View) in both `landing.html` and `landing-page.php`.

### llms.txt updated

QR payload description updated to reflect optional lane/referee fields.

### Files changed

- `js/main.js` — footer link to newtondarts.com
- `js/qr-bridge.js` — referee name in QR modal subtitle; lane/referee requirement removed; dynamic subtitle
- `js/dynamic-help-system.js` — QR button, Chalker nav link, SE rounds, Chalker settings, QR integration note
- `tournament.html` — Chalker nav link
- `landing.html` — Chalker card rewritten and moved to position 2; `chalker/` → `chalker/index.html`
- `landing-page.php` — same Chalker card changes as `landing.html`
- `userguide.html` — new Chalker QR Assignment section
- `llms.txt` — QR payload updated for optional lane/referee
- `css/styles.css` — `font-family: inherit` and `text-decoration: none` on `.nav-btn`; footer link styles
- `docker/nginx.conf` — `camera=()` → `camera=(self)` in `/chalker/` location block
- `chalker/js/chalker.js` — referee in match info bar; back camera preference; x01 removed from info bar
- `chalker/sw.js` — version bumped to `chalker-v101`
- `docker-quickstart.html` — NPM Permissions-Policy workaround documented
- `Docs/QR.md` — lane/referee requirements updated

---

## **v5.0.0-beta.2** - The Chalker Has Eyes Now (2026-03-24)

### Chalker QR scanning (Chalker ← TM)

The Chalker can now scan the assignment QR generated by the Tournament Manager. Tap QR in the "New Match?" dialog — the camera opens immediately, no extra steps. Scan the code, verify the details, and start.

### QR button in "New Match?" dialog

A new **QR** button sits between "New Match" and "Network" in the Chalker's New Match dialog. It appears whether or not a previous match exists.

### Camera → scan → confirm → start

- Camera opens immediately in a modal using the `BarcodeDetector` API
- Scans automatically — no shutter button
- CRC-32 signature verified on every scan (`newton-integrity.js`)
- On success: camera closes, confirmation screen shows player names, format, lane, and referee
- Operator confirms → starting player selection → match begins
- Lane shown in the match info bar throughout the match

### Error handling

- Wrong QR type (not an assignment payload): error shown in scan modal, camera stays open
- CRC mismatch: error shown, camera stays open — no corrupted data ever accepted
- Camera permission denied: clear message
- Unsupported browser (non-Chrome/Edge): "not supported" message instead of camera

### Files changed

- `js/main.js` — version bump to 5.0.0-beta.2
- `chalker/index.html` — QR button in settings modal; `#qr-scan-modal` and `#qr-confirm-modal` markup; `newton-integrity.js` script tag
- `chalker/js/chalker.js` — `handleQRModeFromModal`, `startQRScanner`, `stopQRScanner`, `handleQRPayload`, `showQRScanError`, `showQRConfirm`, `startMatchFromQR`, `cancelQRScan`, `cancelQRConfirm`; `isModalActive()` updated; event listeners wired
- `chalker/js/newton-integrity.js` — new file, identical copy of TM integrity module
- `chalker/styles/chalker.css` — `.qr-scan-modal-content`, `.qr-video`, `.qr-scan-hint`, `.qr-scan-error`, `.qr-confirm-details`
- `chalker/sw.js` — `newton-integrity.js` added to cache; version bumped to `chalker-v96`
- `Docs/QR.md` — decisions updated: QR and Network are separate buttons; QR workflow documented

---

## **v5.0.0-beta.1** - Your Boarding Pass for the Oche (2026-03-22)

### Major version — TM ↔ Chalker communication begins

v5.0.0 introduces the first step of direct communication between the Tournament Manager and the Chalker: QR-based match assignment. The TM generates a signed QR code for any live match; the Chalker scans it and receives everything it needs to start scoring. No typing, no mistakes.

### QR match assignment (TM → Chalker)

- **QR button on live match cards**: A "QR" button appears to the left of "Stop Match" on every live match card in Match Controls. Click it to display the Chalker assignment QR code.
- **Assignment payload**: QR encodes match ID, tournament ID, server ID, player names, x01 format, best-of legs, max rounds, lane, and referee — everything the Chalker needs to auto-populate.
- **CRC-32 integrity**: Every payload is signed with a CRC-32 checksum (`js/newton-integrity.js`). The Chalker will verify on scan; the same module will be reused for MQTT payloads in a future release.
- **Server ID**: A 12-character hex identifier is generated once per TM installation and persisted in global config. Identifies this TM instance in QR payloads and prevents cross-TM result injection.
- **Lane &amp; Referee required**: If either is not assigned, clicking QR shows a warning instead of a code — the Chalker needs both to function.
- **QR library**: `lib/qrcode-generator.js` — standalone, zero external dependencies, loaded on page start.

### Chalker settings in Global Config

- **x01 Format**: New dropdown in Match Configuration → Chalker section. Options: 101 / 201 / 301 / 501 (default: 501). Sent to Chalker via QR.
- **Max Rounds**: New dropdown. Range: 7–20 (default: 13). Sets the tiebreak threshold. Sent to Chalker via QR.
- Both fields reset correctly with "Reset to Defaults" and are included in Developer Console → Reset All Config.

### Match Controls UI

- **Lane dropdown**: Narrowed with dedicated `cc-lane-dropdown` class (58px) — lane numbers are 1–2 digits, no more wasted space.
- **Referee dropdown**: Narrowed with `cc-referee-dropdown` class (120px) — names are already truncated to 10 characters.

### Files changed

- `js/main.js` — version bump to 5.0.0-beta.1
- `js/newton-integrity.js` — new CRC-32 sign/verify module
- `js/qr-bridge.js` — new QR payload builder and modal display
- `lib/qrcode-generator.js` — new QR generation library
- `js/results-config.js` — `x01Format`, `maxRounds` in DEFAULT_CONFIG; server ID generation; Chalker section in `saveMatchConfiguration` and `resetMatchConfigToDefaults`
- `js/bracket-rendering.js` — QR button on live cards; `cc-lane-dropdown` and `cc-referee-dropdown` classes
- `tournament.html` — matchQRModal markup; script tags for new files; Chalker subsection in Match Configuration UI
- `css/styles.css` — `.cc-btn-qr`, `.cc-lane-dropdown`, `.cc-referee-dropdown`
- `Docs/QR.md` — updated with all v5.0.0 design decisions

---

## **v4.2.13** - A+ Security Headers. Yes, Really. (2026-03-20)

### CSP hardening — A+ on SecurityHeaders.com

- **Lightbox extracted**: Inline `<script>` block and all `onclick` handlers moved to external `js/lightbox.js`. Images use `data-full` attributes instead of inline event handlers. Zero inline JavaScript on the landing page and all doc pages.
- **Logo fallback**: Inline `onerror` handler on the logo `<img>` replaced with `addEventListener` in `js/lightbox.js`.
- **Footer inline style**: `style="color: #a89080;"` on the "No popups? No cookies!" footer text replaced with `.footer-cheeky` CSS class across all pages — landing, docs, and release notes.
- **Strict CSP for static pages**: `nginx.conf` now serves a strict Content-Security-Policy without `unsafe-inline` for the landing page, doc pages, and release notes. SecurityHeaders.com grades these pages **A+**.
- **Permissive CSP preserved**: Tournament Manager (`tournament.php`) and Chalker (`/chalker/`) retain `'unsafe-inline'` in their CSP — required due to 93+ inline event handlers and 266+ inline styles in the tournament app. These pages grade **A** on SecurityHeaders.com.
- **Files updated**: `landing.html`, `landing-page.php`, `userguide.html`, `privacy.html`, `architecture.html`, `docker-quickstart.html`, `rest-api.html`, all `releases/*.html`, `releases/README.md`, `css/landing.css`, `docker/nginx.conf`.

### Landing page routing — extracted from tournament.html

- **PHP switcher removed**: The one-line PHP router on line 1 of `tournament.html` has been removed. `tournament.html` is now a pure tournament app file with no landing page logic.
- **`landing-page.php` is now the entry point**: Serves as the Docker index. If `NEWTON_LANDING_PAGE=true`, renders the landing page. If the env var is not set, issues a 302 redirect to `/tournament.php` — tournament-only deployments go straight to the app.
- **`/tournament.html` URL**: nginx rewrites `/tournament.html` to `tournament.php` internally — the URL stays clean and is indexable by Google.
- **Files updated**: `tournament.html`, `landing-page.php`, `docker/nginx.conf`.

### Files changed

- `js/lightbox.js` — new external lightbox script
- `landing.html` — inline JS/styles removed, external script added
- `landing-page.php` — redirect logic added; same inline JS/style removals
- `tournament.html` — PHP landing page switcher removed
- `userguide.html`, `privacy.html`, `architecture.html`, `docker-quickstart.html`, `rest-api.html` — footer inline style replaced with class
- `releases/*.html` — footer inline style replaced with class (all versioned pages)
- `docker/nginx.conf` — differentiated CSP: strict default, permissive for PHP and Chalker; `landing-page.php` as primary index

---

## **v4.2.12** - Dedicated Domain: newtondarts.com (2026-03-19)

### Domain migration

- **New domain**: All URLs updated from `darts.skrodahl.net` to `newtondarts.com` across the entire project.
- **Files updated**: `README.md`, `llms.txt`, `sitemap.xml`, `robots.txt`, `landing.html`, `landing-page.php`, `docker-quickstart.html`, `privacy.html`.
- **Google Search Console**: Verification tag updated for the new domain in both `landing.html` and `landing-page.php`.

### Accessibility

- **Main landmark**: Added `<main>` element to `landing.html` and `landing-page.php` — resolves Lighthouse "Document does not have a main landmark" accessibility flag.

### Landing page — Download button

- **Points to `/releases/`**: "Download Latest Release" button now links to the release notes index instead of directly to GitHub, giving visitors context before downloading.

### Release notes pages

- **`releases/` folder**: Standalone HTML release notes pages for all v4.2.x releases, served at `newtondarts.com/releases/`. Each release gets a permanent versioned page (`v4.2.12.html` etc.) and `index.html` always shows the latest.
- **sitemap.xml**: All release notes pages indexed with `changefreq: never` (versioned) and `changefreq: weekly` (`/releases/`).
- **Mobile**: Get Started card buttons on landing page stack below text on small screens.

### Files changed

- `README.md` — all URLs updated to newtondarts.com
- `llms.txt` — all URLs updated to newtondarts.com
- `sitemap.xml` — all URLs updated to newtondarts.com, release notes pages added
- `robots.txt` — Sitemap URL updated to newtondarts.com
- `landing.html` / `landing-page.php` — Google Search Console tag updated, `<main>` landmark added, download button points to `/releases/`
- `css/landing.css` — mobile fix for wide Get Started cards, `.docs-content .btn-github` style
- `releases/` — new folder with `index.html` and versioned pages

---

## **v4.2.11** - Setup Actions UX, Lollipop Counter & App Name Consistency (2026-03-18)

### Lollipop counter 🍭

- **New stat counter**: "Lollipops (score of 3)" added to the player Statistics dialog, below Tons, with the same +/− button pattern.
- **Leaderboard display**: Players with one or more lollipops show a 🍭 icon right-aligned in the Player column. Two or more show 🍭 x{n} for extra effect. Single lollipop shows the icon only — no count.
- **Celebration page**: "Most Lollipops 🍭" added to Player Achievements, below Most Tons. Only displayed if at least one lollipop was awarded during the tournament.
- **Cosmetic only**: Not part of the points system. Not included in CSV export. Player names in exports remain clean and consistent across tournaments.
- **Backwards compatible**: Existing tournaments load without issues — missing `lollipops` field defaults to 0.
- **Documented**: Tips & Tricks section in `userguide.html` and `llms.txt` updated.

### Setup Actions panel (js/bracket-rendering.js)

- **Restructured layout**: Panel now has two clearly separated sections with named headers.
- **"Shuffle & Draw" section title**: Replaces the former "🔧 Tournament in setup mode" status message — more descriptive and action-oriented, positioned above the format cards.
- **"Navigation" section header**: Added above the Player Registration Page and Global Settings Page buttons, giving the panel clear visual hierarchy.
- **Descriptive text removed**: "Setup actions will help you configure the tournament." removed as redundant.
- **Emojis removed from section titles**: "Shuffle & Draw" and "Navigation" headers are plain text; the wrench icon in the main "Setup Actions" panel header is retained as the sole decorative element.
- **Panel header reverted**: `refereeHeader` restored to `Setup Actions` (had been temporarily changed to "Shuffle & Draw").

### App name consistency (HTML files)

- **Full name enforced**: References to "NewTon DC" and "NewTon" as the software name corrected to "NewTon DC Tournament Manager" across HTML files. Short-form "NewTon" retained where contextually appropriate (e.g. prose references, possessive use).

### Files changed

- `js/player-management.js` — `incrementLollipops()`, `decrementLollipops()`, `updateStatsCounters()` updated
- `js/results-config.js` — lollipop icon displayed in Leaderboard player name cell
- `js/types.js` — `lollipops` added to `PlayerStats` typedef
- `tournament.html` — lollipops +/- counter added to Statistics dialog
- `userguide.html` — lollipops tip added to Tips & Tricks section
- `llms.txt` — lollipop counter documented
- `js/bracket-rendering.js` — Setup Actions panel restructured, Most Lollipops added to celebration page

---

## **v4.2.10** - Doc Pages, User Guide & Architecture (2026-03-17)

### userguide.html

- **New page**: Comprehensive user guide. Sections: Quick Start (7 styled numbered steps), Tournament Formats (DE vs SE with guidance on when to use each), Configuration, Managing a Tournament (including Saved Players registry and payment tracking), Running Matches & Match Controls, Results & Export, Tips & Tricks (undo, late registration, offline use, data safety, self-hosting).
- **Quick Start styling**: Numbered step cards with orange Insignia circle badges and accent left border (`.docs-quickstart` in `css/landing.css`).
- **Quick Start title styling**: Step titles (Download, Open, Configure…) now render in burnt orange — only the first `<strong>` per step is targeted (`.docs-quickstart li > div > strong:first-child`), leaving inline bold text in dark brown.
- **Developer Console section**: New section added between Results & Export and Tips & Tricks — covers Statistics panel (Quick Overview, Transaction Health, Match State, Player Count, Lane Usage, localStorage Usage) and all Commands with descriptions.
- **Bracket View**: Covers navigation panel, pan & zoom (mouse drag, scroll wheel, +/− buttons, home reset), match status states, and status panel (bottom-right tournament summary).
- **Match Controls**: Full description of the command center — two-column Frontside/Backside layout, live matches sorted by lane, ready matches grouped by round, lane/referee conflict management, Referee Suggestions panel (Recent Losers / Recent Winners / Recent Assignments), and the note that all match actions can also be performed directly from the bracket.
- **Recording Results**: Describes the Confirm Match Winner dialog including Match Progression preview, optional leg score entry, and per-player Statistics dialog (short legs with dart count, high outs with score, 180s and tons with +/− counters).
- **Leaderboard**: Mid-tournament standings access and retroactive stat entry via player click.

### docker-quickstart.html

- **New page**: `DOCKER-QUICKSTART.md` converted to a standalone HTML page served directly from the Docker container. Sections: Quick Start (3 steps), Configuration (complete `docker-compose.yml` with persistent storage and env var reference), Reverse Proxy Setup, Security, Customization, Troubleshooting.
- **Landing page link updated**: "Docker Quickstart" button in the Get Started section now points to `docker-quickstart.html` instead of the GitHub markdown file.

### privacy.html

- **New page**: `Docs/PRIVACY.md` converted to a standalone HTML page. Sections: Overview, Browser LocalStorage, What NewTon Doesn't Do, Storage Architecture, Export Privacy, Demo Site Model, Self-Hosting & REST API, Offline Operation, FAQ, Summary.
- **Footer link updated**: Privacy link in the landing page footer now points to `privacy.html` instead of GitHub.

### rest-api.html

- **New page**: `Docs/REST_API.md` converted to a standalone HTML page. Sections: Overview, Architecture, Endpoints (List/Upload/Delete with request/response examples and error tables), CORS, Client Integration, Data Format, Security, Troubleshooting.
- **Linked** from both `docker-quickstart.html` and `privacy.html`.

### architecture.html

- **New page**: Design philosophy and internals behind NewTon's crash-proof architecture. Sections: Single Source of Truth (MATCH_PROGRESSION lookup tables), Transaction History & Undo (event sourcing, surgical undo, auto-recovery), Data Separation (tournament data, transaction history, and global config kept strictly isolated), Offline-First Persistence, Strengths, Known Limitations.
- **Linked** from the landing page Get Started section. Cross-linked to the Developer Console section in `userguide.html`, `privacy.html`, and `rest-api.html`.

### Docs page styling (css/landing.css)

- **Docs layout**: `.docs-content` centered column (760px), `.docs-back-link` fixed top-left in Insignia font, `.docs-toc` contents box, heading and prose styles for doc pages.
- **Terminal blocks**: `.terminal-wrap` / `.terminal-bar` — macOS-style traffic light dots (red/amber/green), dark background, soft green monospace text for bash commands.
- **Docs footer**: `.docs-footer` overrides footer width to match the 760px column.
- **Table styles**: `.docs-content table`, `th`, `td` — consistent warm-palette table styling for docs pages.
- **Quick Start steps**: `.docs-quickstart` — styled ordered list with CSS counter circles for `userguide.html`.

### Landing page — Get Started section

- **User Guide card added**: Third card spanning the full width of the Get Started section, with text left and "Read the Guide" button right (`.get-started-card--wide` in `css/landing.css`).
- **Architecture & Reliability card added**: Fourth card in the Get Started section linking to `architecture.html`.

### sitemap.xml

- **Five doc pages added**: `userguide.html` (0.8), `docker-quickstart.html` (0.8), `architecture.html` (0.7), `rest-api.html` (0.7), `privacy.html` (0.7) — all with `noindex` removed.
- **Priorities rebalanced**: Doc pages prioritised by search value rather than click depth — `chalker` 0.6, `/?launch` 0.4.

### Setup Actions — bracket format order

- **Double Elimination moved to top**: "Double Elimination Cup" card now appears above "Single Elimination Cup" in the Setup Actions panel, reflecting its status as the primary tournament format.

### Bing Webmaster Tools

- **Meta tag added**: `<meta name="msvalidate.01">` verification tag added to both `landing.html` and `landing-page.php`.

### SEO — Meta Descriptions

- **Meta descriptions added**: `<meta name="description">` added to all five pages missing it — `userguide.html`, `docker-quickstart.html`, `privacy.html`, `rest-api.html`, and `chalker/index.html`.

### Files changed

- `architecture.html` — new Architecture & Reliability page
- `userguide.html` — new user guide page
- `docker-quickstart.html` — new Docker quick start page
- `privacy.html` — new privacy architecture page
- `rest-api.html` — new REST API reference page
- `css/landing.css` — docs page styles, terminal blocks, table styles, `.docs-quickstart`, `.get-started-card--wide`
- `landing.html` — Bing meta tag, Docker Quickstart link, Privacy footer link, User Guide card, Architecture & Reliability card
- `landing-page.php` — same changes as `landing.html`
- `sitemap.xml` — five doc pages added, priorities rebalanced
- `chalker/index.html` — meta description added
- `js/bracket-rendering.js` — Double Elimination moved to top of Setup Actions

---

## **v4.2.9** - Landing Page Polish (2026-03-14)

### Landing Page — Screenshot Lightbox

- **Focused thumbnails**: All seven "See It in Action" showcase items now use cropped thumbnails (`th-*.jpg`) instead of full-page screenshots — images are legible at display size and clearly distinguishable from each other
- **Lightbox**: Clicking any thumbnail opens the full-size image in a dark overlay. Close with ESC, clicking the overlay, or the × button. Pure JS/CSS — zero dependencies, no external libraries
- **Zoom hint**: A small magnifying glass icon appears in the lower-right corner of each thumbnail on hover, signalling the image is expandable
- **landing-page.php**: All changes from `landing.html` applied — both files are in sync

### Landing Page — Chalker Showcase Card

- **New "See It in Action" item**: Added a seventh showcase card for the Chalker app — tablet scoring view with live scoresheet, per-visit scores, and running totals. Mentions live and post-match stats (averages, score ranges, high finishes) and the 1,000-match history.

### llms.txt

- **Typical Use Case section**: Added a concrete weekly pub tournament scenario illustrating how the persistent player registry, CSV export, and configurable point system work together for season standings
- **Key Features expanded**: Undo blocking note, "designed for season standings" qualifier on the point system, paid/unpaid tracking and optional payment QR, explicit non-power-of-two support, browser-restart survival note
- **Tips for AI Services**: Added bullet clarifying the point system is a primary use case for season standings, not incidental config

### Files changed

- `landing.html` — focused thumbnails, lightbox markup and script, Chalker showcase card
- `landing-page.php` — same changes as `landing.html`
- `css/landing.css` — lightbox styles, zoom hint overlay
- `Screenshots/th-*.jpg` — seven focused thumbnail images
- `llms.txt` — Typical Use Case section, expanded Key Features, expanded Tips for AI Services

---

## **v4.2.8** - Late Registration (Stages 2 & 3) (2026-03-13)

### Late Registration — Stage 2: Player Name Entry

- **Name input form**: After the eligibility check in Stage 1, the Dev Console now shows a "Register New Player" form — a text field for the player's name and a "Check & Confirm" button
- **Descriptive paragraph**: A short explanation is shown above the input field: the new player will be added to the tournament, must participate from the beginning, and will replace a randomly selected available walkover spot in Frontside Round 1
- **Name validation**: Empty names and names that only contain whitespace are rejected with an inline error — the form remains open for correction
- **Duplicate detection**: If the name matches an existing player (case-insensitive), the form rejects it with a clear message before any slot is selected
- **Re-validation at execution time**: Eligibility is re-checked at Step 2 execution — if all slots have become ineligible between Step 1 and Step 2 (e.g. a match went live in the meantime), registration is refused immediately
- **Random slot selection**: A slot is chosen randomly from the pool of eligible FS Round 1 BYE positions — guarantees fairness, consistent with the existing draw philosophy
- **Confirmation gate**: Before any data is written, Step 2 shows a confirmation screen: the selected match, the opponent the new player will face, and a text field asking the operator to type the player's name exactly to confirm. This prevents accidental registration.

### Late Registration — Stage 3: Placement & Audit

- **Player creation**: A new player object is created and appended to the players array — fully compatible with the existing player data structure (`id`, `name`, `paid: true`, `stats`, `placement: null`, `eliminated: false`)
- **Saved players list**: The new player is added to the global saved players list via `addToPlayerList()` — consistent with normal player registration
- **BYE walkover reversal**: The automatic walkover transaction for the selected slot is undone via the existing `undoManualTransaction()` mechanism — the bracket is restored to its pre-walkover state before the new player is placed
- **Slot placement**: The BYE placeholder in the selected match is replaced with the new player — player1 or player2, depending on which slot held the BYE
- **LATE_REGISTRATION transaction**: A transaction of type `LATE_REGISTRATION` is appended to the match history — records player name, player ID, match ID, opponent name, and timestamp. Provides a clear audit trail without enabling undo of the registration itself.
- **Bracket refresh**: `refreshTournamentUI()` is called after placement — the bracket re-renders immediately and the new player appears in their correct position
- **Success feedback**: The Dev Console shows a "Late Registration" success card with the player name and match placement

### Eligibility Text Reword

- **Clearer output**: The eligibility summary line was reworded from `"11 of 14 FS Round 1 BYE slots eligible for late registration"` to `"11 of 14 BYE slots are eligible for late registration in FS Round 1"` — more natural phrasing and easier to parse at a glance

### Bug Fix — Late Registration and Undo Not Persisting After Reload

- **Root cause**: `refreshTournamentUI()` attempted to save via `saveCurrentTournament()`, a function that was never defined. The `typeof` guard silently swallowed the failure, so every call to `refreshTournamentUI()` re-rendered the bracket without persisting match data to localStorage
- **Impact on Late Registration**: After registering a player, the modified match (with the new player replacing the BYE slot) was never saved. On reload, the old tournament data was restored but the BYE auto-advance transaction was already removed from history — leaving the tournament in an invalid state with the player missing from the bracket
- **Impact on regular undo**: The same missing save affected all undo operations — match rollbacks were not persisted to localStorage (history was saved correctly, but match state was not)
- **Fix 1**: `refreshTournamentUI()` now calls `saveTournament()` instead of the nonexistent `saveCurrentTournament()`
- **Fix 2**: `commandLateRegistrationStep3()` now explicitly calls `saveTournament()` immediately after placing the new player in the bracket slot, before recording the LATE_REGISTRATION transaction — guarantees persistence regardless of UI refresh behaviour

### "Tournament Already in Progress" Modal — Late Registration Pointer

- **Third block added**: The modal shown when clicking "Add Player" during an active tournament now includes an amber block — "🕐 Player arrived late?" — pointing the operator to the "Player arrived late?" button at the bottom of the Tournament Players list

### Player Registration Page — Late Arrival Hint

- **"Player arrived late?" button**: When a tournament is active, an amber button appears below the Tournament Players list on the Player Registration page — opens an informational dialog explaining the Late Registration feature and how to access it
- **Dialog content**: Describes what Late Registration does (random walkover placement, fully registered as paid) and directs the operator to enable the Developer Console in Global Settings, then open it via the version number in the lower-right corner of the Tournament Bracket
- **ESC and Got It**: Dialog uses the existing dialog stack — ESC and the "Got it" button both close it correctly

### Compatibility

- **Single Elimination**: Late Registration works in SE tournaments — `getProgressionTable()` returns the correct SE table, and FS Round 1 slot detection works identically for both formats. Tested successfully.

### Files changed

- `js/analytics.js` — Late Registration command (Stages 1-3)
- `js/player-management.js` — "Player arrived late?" button and info dialog
- `js/bracket-rendering.js` — `refreshTournamentUI` save fix
- `tournament.html` — Late Registration info modal, Late Registration pointer in "Tournament Already in Progress" modal

---

## **v4.2.7** - SEO & Landing Page Polish (2026-03-13)

### SEO
- **sitemap.xml**: New file added to repo root — lists landing page, Tournament Manager, and Chalker App URLs for Google indexing
- **robots.txt**: Added `Sitemap:` directive pointing to `https://darts.skrodahl.net/sitemap.xml`

### Landing Page
- **Meta description**: Shortened from 190 to 155 characters to fit within Google's display window
- **Font preloading**: Added `<link rel="preload">` hints for both custom fonts (Insignia and Manrope) — eliminates flash of unstyled text on load
- **font-display: block**: Switched from `swap` to `block` in `landing.css` — combined with preloading, ensures branded fonts appear from first render with no flicker
- **App buttons open in new tab**: "Launch Tournament Manager" and "Open Chalker App" buttons now open in a new tab, keeping the landing page open
- **Get Started section**: Two-card section added below the hero buttons — "Local Use" (download release, double-click `tournament.html`) and "Self-Hosted" (Docker quickstart link), with hover effects consistent with the rest of the page

### Files changed

- `sitemap.xml` — new file
- `robots.txt` — `Sitemap:` directive added
- `landing.html` — font preload hints, meta description, app button targets, Get Started section
- `landing-page.php` — same changes as `landing.html`
- `css/landing.css` — `font-display: block`, Get Started section styles

---

## **v4.2.6** - Undo Bug Fix & Late Registration (Stage 1) (2026-03-12)

### Late Registration — Stage 1 (Eligibility Checker)
- **New Dev Console command**: "Late Registration" (amber, after Toggle Read-Only) replaces the former "Bracket Editor" placeholder
- **Eligibility checker**: scans all FS Round 1 BYE slots and reports how many are eligible for late registration — a slot is eligible if neither its winner nor loser downstream match is live or manually completed
- **Player names in output**: blocking matches are shown with player names (e.g. `FS-2-4 (Frank vs Harry, live)`) for immediate clarity
- **Fairness warning**: if any slots are ineligible, warns that the draw cannot be fully fair and lists the blocking matches
- **Replay warning**: explicitly states that stopped or undone matches must be replayed from the beginning
- **Clear refusal**: if no eligible slots exist at all, the command refuses with a plain explanation
- **Warning status**: `showCommandFeedback` updated to support amber `'warning'` status alongside existing success/error

### Bug Fix
- **Undo blocked by live downstream matches**: The undo eligibility check (`isMatchUndoable`) previously only checked for completed downstream matches. It did not check for **live** downstream matches, meaning a match could be undone while a downstream match was actively in progress — potentially corrupting the live match's context. Both the winner's and loser's downstream destinations are now checked for live status (`match.active`) before allowing an undo.
- **Tooltip correctly reflects live blocking**: The bracket hover tooltip also had the same gap — it now shows `Cannot Undo, blocked by FS-2-4 (live)` when a downstream match is in progress, consistent with the undo eligibility logic.

### SEO
- **robots.txt**: Added to repo root — allows all crawling and signposts `/llms.txt` for AI services

### Files changed

- `js/bracket-rendering.js` — `isMatchUndoable()` and tooltip function updated with live downstream match checks
- `js/analytics.js` — `commandBracketEditor` renamed to `commandLateRegistration` and implemented as eligibility checker
- `tournament.html` — Dev Console menu entry renamed to "Late Registration"
- `robots.txt` — new file

---

## **v4.2.5** - Landing Page & Developer Console (2026-03-11)

### Landing Page
- **Hero image optimised**: Switched from `newton-cartoon.png` (2.1MB) to `newton-cartoon.jpg` (164KB) — 13× smaller, same visual quality
- **OG & Twitter Card image**: Changed to `newton-poster-throw.jpg` — cleaner, less busy image that reads well at thumbnail size
- **Lane & Referee Management card**: Rewritten to accurately describe conflict detection — players officiating a match are blocked from playing until free, players in a live match are excluded from referee selection, suggestions prioritise recent losers, winners, and referee history
- **Google Search Console**: Added site verification meta tag to both `landing.html` and `landing-page.php`

### Developer Console
- **Bracket Editor entry**: New amber-coloured menu item added after Toggle Read-Only — shows "here be dragons / upcoming feature" placeholder; no bracket logic wired up yet
- **Parking Lot**: Bracket Editor fully documented in `Docs/PARKING-LOT.md` with 6-step implementation plan

### Files changed

- `landing.html` / `landing-page.php` — hero image, OG/Twitter Card image, feature card text, Google Search Console tag
- `tournament.html` — Bracket Editor menu entry
- `js/analytics.js` — `commandBracketEditor()` stub
- `js/main.js` — version bumped

---

## **v4.2.4** - Single Elimination Match Lengths & Chalker Stats (2026-03-10)

### Global Config — Match Configuration
- **Single Elimination section**: Match Configuration in Global Config now has dedicated SE fields — Regular Rounds, Quarterfinal, Semifinal, Bronze Match, Final — each independently configurable
- **Double Elimination section**: Existing DE fields unchanged, now clearly labelled under their own heading
- **SE-first layout**: Single Elimination section appears above Double Elimination in both the config form and the config summary panel
- **Prominent headings**: Section headings use bold uppercase styling with a bottom border rule for clear visual separation
- **Correct SE leg assignment**: SE matches now use SE-specific config values instead of borrowing from DE fields — Quarterfinal and Semifinal resolved by round position, Bronze and Final by match ID
- **Default values**: SE Regular Rounds Bo3, Quarterfinal Bo3, Semifinal Bo3, Bronze Match Bo5, Final Bo5

### Chalker Scoring App — Live Stats
- **Leg average colour coding**: In the Leg Avgs row of Match Statistics, averages for legs the player started are shown in green (`var(--accent-success)`) — matching the existing leg-starter header colour. Legs not started remain unchanged. Gracefully falls back to plain text for older match records.

### Landing Page
- **Chalker button**: Added amber gold "Open Chalker App" button linking to `/chalker` — sits between Launch and GitHub buttons, completes the three-color retro palette

### LLMs
- **llms.txt tips section**: Added "Tips for AI Services" to prevent hallucinated features (Round Robin, drag-and-drop, multi-screen, indexedDB) and reinforce core design principles

### Files changed

- `js/results-config.js` — DEFAULT_CONFIG, `populateConfigPage()`, `saveMatchConfiguration()`, `resetMatchConfigToDefaults()` updated with SE leg fields
- `js/clean-match-progression.js` — `isSESemifinal()`, `isSEQuarterfinal()` added; SE leg assignment in `generateFrontsideMatches()` rewritten
- `tournament.html` — Match Configuration section split into SE/DE sub-sections; summary panel updated
- `js/bracket-rendering.js` — config summary display updated with SE rows
- `chalker/js/chalker.js` — `populateMatchStats()` leg averages loop updated with starter detection and colour coding
- `landing-page.php` / `landing.html` — Chalker App button added
- `llms.txt` — Tips for AI Services section added

---

## **v4.2.3** - Landing Page Redesign (2026-03-10)

### Landing Page — Retro Comic Theme
- **Hero image**: Nano Banana retro comic illustration added as a prominent hero element with rounded corners, dark border, and warm glow shadow
- **Complete color overhaul**: Warm parchment background (`#f5ebe0`), rich brown text (`#2b2118`), burnt orange accents (`#c0562a`), amber gold highlights (`#e8a44a`) — all derived from the hero image palette
- **Feature showcase**: Screenshots section replaced with alternating two-column showcase layout — each item has a category label, heading, description, and screenshot with hover zoom effect
- **New showcase card**: "Intelligent Seeding & BYE Handling" — fair draw algorithm and automatic BYE advancement
- **Highlight card updated**: Replaced `~60MB Docker Image Size` with `2 Tournament Formats`
- **Section dividers**: Gradient orange-to-gold horizontal rules between sections
- **Card styling**: Cream cards (`#fff8f0`) with warm borders and gradient top accent bars
- **Standalone test file**: `landing.html` added for local browser testing without Docker/PHP
- **PHP landing page synced**: `landing-page.php` updated with all new content, preserving env var plumbing
- **OG image updated**: Open Graph and Twitter Card image changed from bracket screenshot to hero cartoon — link previews now show the Nano Banana illustration on WhatsApp, Slack, Twitter, etc.
- **llms.txt**: Machine-readable project summary added for AI assistants, with `<link rel="llms">` meta tag on landing pages

### Files changed

- `css/landing.css` — complete rewrite: retro comic theme, showcase layout, responsive breakpoints
- `landing-page.php` — new design with hero image, showcase section, updated highlight cards
- `landing.html` — standalone test version (new file)

---

## **v4.2.2** - Landing Page Fix (2026-03-09)

### Landing Page
- **Fixed HTML leak**: Landing page content was visible when opening `tournament.html` directly in a browser (without PHP). Moved landing page to separate `landing-page.php` file, included via `<script><?php include ?></script>` pattern — browser treats PHP inside script tags as invalid JS and silently ignores it (same pattern used by demo banner)
- **Feature cards reorganized**: Added Chalker Scoring App card; removed Magic Zoom card; bracket visualization note added to Single & Double Elimination card
- **Highlight number cards**: Moved into hero section above the action buttons for better visual flow

---

## **v4.2.1** - Visual Polish (2026-03-08)

### Match Card Tweaks
- **Muted "Started" button**: Live match button color changed from bright orange (`#ff6b35`) to a warmer, less distracting muted orange (`#e09060`)
- **Subtle dropdown backgrounds**: Lane and referee dropdowns on ready/live match cards now use a light gray (`#e8e9ec`) instead of pure white, blending better with the card footer

### SEO & Landing Page
- **SEO meta tags**: Added `<meta name="description">` and `<meta name="keywords">` to tournament.html for search engine discoverability
- **Schema.org structured data**: JSON-LD `SoftwareApplication` markup on landing page — tells search engines the app category, price (free), license, browser requirements, feature list, and screenshot
- **Optional landing page**: Docker deployments can enable `NEWTON_LANDING_PAGE=true` to show a feature-rich page with descriptions, screenshots, and Open Graph / Twitter Card meta tags
  - Landing page embedded in tournament.html (becomes tournament.php in Docker) — no separate files needed
  - Centered header with logo and title in Insignia font, body text in Manrope — matching the tournament app
  - "Launch Tournament Manager" button uses `?launch` to enter the app
  - Supports `NEWTON_BASE_URL` and `NEWTON_GITHUB_URL` environment variables

### Eliminated Player Strikethrough (2026-03-03)

### Visual Polish
- **Eliminated player strikethrough**: Completed match cards now display the eliminated player's name in muted red with a slanted strikethrough line, making it immediately clear who has been knocked out
  - Muted red (`#b87070`) — the natural complementary colour to the green match card background, and intuitively signals elimination
  - Strikethrough appears only in the specific match where the player was eliminated — not in earlier matches they won or lost en route
  - Works correctly in both SE and DE:
    - **SE**: every round loser is eliminated immediately; strikethrough appears in that round's match card
    - **DE**: frontside losers who continue to the backside show no strikethrough until their backside elimination match
  - Walkover slots and match winners are never struck through
  - Implementation: `isPlayerEliminatedInMatch()` uses round-order comparison (`getMatchRoundOrder()`) to identify the player's final match; CSS `::after` pseudo-element renders the slanted line (`rotate(-10deg)`)

---

## **v4.2.0** - Single Elimination (continued — 2026-03-03)

### SE Visual Fixes
- **4-player SE staggered layout**: BRONZE and FINAL now render in separate columns — BRONZE at a mid-column position, FINAL at the rightmost column — mirroring the 8/16/32-player stagger pattern
- **4-player SEMIFINALS column label**: Was missing; now rendered above the Round 1 column
- **SE zoom/pan defaults**: 4P bracket centered correctly at zoom=0.8, pan x=−80 y=65

### SE Info Box (Match Hover)
- **Hover info box now appears in SE brackets**: `getMatchProgressionText()` was referencing `DE_MATCH_PROGRESSION` directly — fixed to use `getProgressionTable()`
- **"Leads to / Feeds from" removed for SE**: SE info box shows match ID and state only; visual bracket lines make progression self-evident. `getMatchProgressionText()` returns `line2: null` for SE; `updateStatusCenter()` updated to render when `line2` is absent

### SE Tournament Completion
- **`readOnly` now set immediately on SE tournament completion**: Was only applied at load time from `status === 'completed'`; now set in-memory at the moment completion is detected — preventing the completed tournament from appearing editable mid-session

### SE Undo System
- **`getConsequentialMatches()`**: Fixed to use `getProgressionTable()` instead of `DE_MATCH_PROGRESSION` — walkover cascade on undo now works correctly for SE
- **`undoManualTransaction()`**:
  - `isUndoingGrandFinal` renamed to `isUndoingFinal` and extended to cover SE terminal match via `isSEFinalMatch()`
  - Sets `tournament.readOnly = false` when the final match is undone, restoring the tournament to active
  - Fixed progression table lookup to use `getProgressionTable()`
- **`isMatchUndoable()` (hard-block enforcer)**: Fixed to use `getProgressionTable()` — SE matches with completed downstream matches now correctly block undo at render time (onclick handler not rendered)
- **`getDetailedMatchState()` (info box text)**: Same fix — now correctly reports "Cannot Undo, blocked by …" for SE matches with completed downstream matches
- Hard-block behaviour confirmed across all SE bracket sizes (4P–32P): matches are blocked one-by-one, never cascading — identical to DE

### Developer Console
- **"View Match Progression" hidden for SE**: The command is DE-specific (shows `DE_MATCH_PROGRESSION` tables); hidden when the console opens for an SE tournament

### Setup Actions UI
- **Format cards moved to top**: Single Elimination Cup and Double Elimination Cup cards now appear above the navigation buttons — primary action first
- **Format card background darkened**: `#fafafa` → `#f0f0f0` so cards stand out clearly against the white panel
- **Format card titles enlarged**: 14px → 17px for stronger visual hierarchy
- **Spacing between cards and navigation buttons**: 30px gap separates the bracket generation section from the Player Registration / Global Settings buttons

### Help System
- **Bracket Generation help**: Updated to describe SE and DE format cards; bracket size table now includes 4-player (SE only)
- **Match Format Configuration help**: Backside Final and Grand Final entries marked as "(DE only)"

---

## **v4.2.0** - Single Elimination Support (Foundation — 2026-02-23)

### New Features
- **Tournament format selection**: Operators now choose between Single Elimination Cup and Double Elimination Cup when generating a bracket
  - Two distinct format cards in Setup Actions with descriptions
  - SE: "Players are eliminated after one loss"
  - DE: "Players get a second chance through the backside"
  - Both formats require minimum 4 players; SE supports 4/8/16/32 brackets, DE supports 8/16/32
- **Bracket confirmation dialog** now shows the chosen format: "Generate 8-Player Single Elimination Bracket?" or "Generate 8-Player Double Elimination Bracket?"
- **`format` field** stored on tournament object at bracket generation time
  - Backward compatible: existing tournaments without the field are treated as DE
  - Persisted through save, load, export, and import
- **Bronze match** for SE brackets (4+ players): 3rd place match between semifinal losers
  - Always generated as a regular FS round (penultimate round, e.g., `FS-3-1` for 8-player)
  - Winner = 3rd, loser = 4th
  - **Gates the Final**: Final cannot start until Bronze is completed
- **Final gating**: SE Final shows as "Waiting" while Bronze is pending — enforced by `canMatchStart()` in bracket-rendering.js
- **SE round display names** in Match Controls: Final, Bronze Final, Semifinals, Quarterfinals, Round N — named from the end backwards
- **SE Match Controls layout**: Rolling two-column view — left column shows earliest ready round, right column shows upcoming rounds

### SE Bracket Generation & Completion
- **SE bracket generation works end-to-end**: `generateAllMatches()` skips backside and finals for SE; Bronze and Final are extra FS rounds added by `calculateCleanBracketStructure()`
- `createOptimizedBracketV2()` supports 4-player bracket size (SE-only)
- SE progression tables: semifinal losers route to Bronze round, semifinal winners route to Final round
- Match progression is fully format-aware — winners advance correctly, SF losers route to Bronze, earlier losers are eliminated
- **Tournament completion** detects final match via `{}` progression — Bronze excluded via `isSEBronzeMatch()` check
- 1st/2nd place set from final winner/loser; 3rd/4th from Bronze (SE) or BS-FINAL loser (DE)
- Undo of tournament-ending match is format-aware
- **SE rankings**: Placement derived from elimination round + bronze match results
  - R1 losers in 8-player → 5th-8th, bronze winner → 3rd, bronze loser → 4th, final loser → 2nd
  - Bronze is always played before Final (gated), so 3rd/4th are always resolved
  - Live rankings update after every match completion

### Technical Details
- Added `getFormat()` helper in tournament-management.js (returns 'DE' when field is absent)
- Added `calculateBracketSize(playerCount, format)` in clean-match-progression.js
- Added `getProgressionTable()` helper — returns SE or DE progression table based on tournament format
- All progression table lookups in clean-match-progression.js now use `getProgressionTable()` instead of hardcoded `DE_MATCH_PROGRESSION`
- Added `pendingFormat` flow: format cards → showBracketConfirmation → confirmBracketGeneration → tournament.format
- `format` field threaded through all 5 tournament object construction sites (create, load, import, save, export)
- Tournament typedef updated in types.js
- Added `isSEBronzeMatch()` and `isSEFinalMatch()` helpers for identifying SE special matches
- Bronze completion hook sets 3rd/4th place immediately (parallel to BS-FINAL hook)
- `canMatchStart()` enforces Final gating behind Bronze in SE
- SE_MATCH_PROGRESSION, calculateBracketSize, and getProgressionTable exposed via window for debugging
- Added `getSERoundDisplayName(round, bracketSize)` in clean-match-progression.js — single source of truth for SE round display names
- `getRoundDescription(match)` in bracket-rendering.js uses it for SE matches; DE path unchanged
- Match Controls SE layout: left column = earliest ready round, right = remaining rounds; live matches in left column only
- **SE bracket rendering** (Step 5): Visual bracket displayed for all 4 SE bracket sizes
  - `renderSEBracket()` called from `renderCleanBracket()` when `tournament.format === 'SE'` — DE path untouched
  - Size-specific functions: `render4/8/16/32PlayerSEMatches()` — same grid/coordinate system as DE, frontside-only
  - 4-player: 2 SFs aligned at Bronze/Final Y for clean horizontal connections to finals column
  - 8/16/32-player: SF positions mirror DE frontside semi positions (Y=335/665 for all sizes)
  - `create4/8/16/32PlayerSELines()` in bracket-lines.js: L-shaped progression lines through rounds, shared vertical spine at finalsX-40 branching to Bronze and Final
  - `createSEBracketLabels()`: tournament header (centered on bracket) + FINALS label (above finals column)
  - `createSEPlacementLabels()`: placement range labels above each round column where losers are eliminated
  - `createSEFinalsLines()`: reusable finals spine — both SFs connect to vertical spine, spine branches to Bronze and Final
  - Match badge shows "BRONZE" / "FINAL" for SE special matches (via `isSEBronzeMatch()` / `isSEFinalMatch()`)
  - SE zoom/pan defaults per bracket size (tunable): 4P zoom=0.8, 8P zoom=0.65, 16P zoom=0.45, 32P zoom=0.33
  - `resetZoom()` updated with SE-specific defaults
- **Remaining work**: SE polish (referee round labels, match card IDs, leaderboard tier labels)

---

# 2026-02-09

## **v4.1.21** - Bracket Generation Confirmation

### Enhancements
- **Bracket generation confirmation dialog**: Generates bracket only after explicit review
  - Shows bracket size, player count, and bye count
  - Displays all registered players as read-only cards in 4-column grid
  - Cancel is the default action (Enter cancels, prevents accidental generation)
  - Warning: "Make sure all players are registered before proceeding."
  - Prevents the common mistake of forgetting to add a player before starting
- **Visual polish for Match Controls panels**:
  - Subtle box-shadow on Tournament Setup and Referee Suggestion cards
  - Referee suggestions: larger font, bolder names, more padding
  - Color-coded left borders on suggestion categories (losers, winners, assignments)

### Technical Details
- Added `bracketConfirmModal` to tournament.html
- Split `generateCleanBracket()` into validation + confirmation + execution
- Added `showBracketConfirmation()` and `confirmBracketGeneration()` functions
- Reuses `.player-list-item.in-tournament` styling with subtle box-shadow
- Uses `pushDialog`/`popDialog` stack with Esc support

---

# 2025-01-17

## **v4.1.20** - Chalker First 9 Average Fix

### Bug Fixes
- **First 9 Average calculation**: Now correctly averages first 9 darts across all legs
  - Previously only used first leg's data (showed 167.0 instead of 101.6 in multi-leg matches)
  - Now includes first 3 visits from every leg played
  - Works correctly for variable match lengths (2-leg, 3-leg, etc.)
  - Applies to Match Complete, History Detail, and Live Stats views

### Technical Details
- Removed erroneous `.slice(0, 3)` that limited calculation to first leg only
- `first9Scores` array now properly averaged across all collected visits
- Service worker cache version bumped to v89

---

# 2025-01-14

## **v4.1.19** - Chalker Network Mode Foundation

### Chalker Enhancements
- **Dynamic leg indicator**: Info bar now shows "Leg X of Y" instead of static "Best of Y"
  - Example: "501 • Leg 1 of 3" → "501 • Leg 2 of 3"
  - Shows match progress at a glance without checking the leg score
- **Larger dart symbol**: Dart column header (➹) increased to 1rem for better visibility
  - Uses `line-height: 1` to prevent row height increase
- **Network mode foundation**: Prepared infrastructure for future tournament integration
  - Removed lane selection from local mode (lane is for network device identification)
  - Added "Network" button to NEW menu for future licensed network mode
  - Network modal with lane selection (1-20) and license notice
  - Network waiting state with "Lane X • Waiting..." info bar
  - Deep blue header (#1e3a5f) distinguishes network mode from local mode
  - Lane selection persisted in IndexedDB settings
- **Improved NEW button flow**: Better confirmation handling
  - Active match: Shows confirmation dialog before presenting options
  - Idle state: Shows options directly (no Rematch option when idle)
- **Idle screen hint**: Info bar shows "Tap NEW to start" when no match is active

### Technical Details
- Removed lane dropdown from config modal
- Added Network button, modal, and waiting state logic
- Added `.network-mode` CSS class for blue header styling
- Changed info bar from `Best of ${bestOf}` to `Leg ${legs.length} of ${bestOf}`
- Added `font-size: 1rem; line-height: 1` to `.chalk-table thead th:nth-child(3)`
- Service worker cache version bumped to v88

---

## **v4.1.18** - Chalker Info Bar & UI Polish

### Chalker Enhancements
- **Dynamic leg indicator**: Info bar now shows "Leg X of Y" instead of static "Best of Y"
  - Example: "Lane 3 • 501 • Leg 1 of 3" → "Lane 3 • 501 • Leg 2 of 3"
  - Shows match progress at a glance without checking the leg score
- **Larger dart symbol**: Dart column header (➹) increased to 1rem for better visibility
  - Uses `line-height: 1` to prevent row height increase

### Chalker Polish
- **Action row padding**: Balanced vertical padding around NEW/HISTORY/STATS buttons

### Technical Details
- Changed info bar from `Best of ${bestOf}` to `Leg ${legs.length} of ${bestOf}`
- Added `font-size: 1rem; line-height: 1` to `.chalk-table thead th:nth-child(3)`
- Service worker cache version bumped to v80

---

# 2025-01-13

## **v4.1.17** - Chalker Info Bar Redesign

### Chalker Enhancements
- **Centered info bar**: Match info now displayed as a single centered line
  - Format: "Lane 5 • 501 • Best of 3" (or "501 • Best of 3" without lane)
  - Cleaner visual hierarchy: Big scores → Medium info → Small chalkboard
- **Dart column symbol**: Changed header from "#" to "➹" (dart arrow)

### Technical Details
- Simplified `.match-info-bar` from 3-cell flexbox to single centered text
- Updated `updateDisplay()` to build info string with bullet separators
- Service worker cache version bumped to v76

---

## **v4.1.16** - Chalker Lane Dropdown & Chalkboard Info

### Chalker Enhancements
- **Lane dropdown**: Lane input changed from free-text to dropdown (1-20)
  - Options: "No lane" (default), Lane 1-20
  - Prevents invalid lane entries
- **Chalkboard info cells**: Row 0 now displays lane and match format
  - Left cell shows lane name (e.g., "Lane 5")
  - Right cell shows best-of format (e.g., "Bo3")
  - Same gray styling as other header cells

### Cleanup
- **Removed Double-In toggle**: Was stored but never used in game logic
  - Can't validate double-in without individual dart values
  - Simplifies config form

### Bug Fixes
- **Table border rendering fix**: Fixed disappearing borders at certain browser widths
  - Changed from `border-collapse: collapse` to `border-collapse: separate`
  - One-sided borders prevent subpixel rendering issues in Chrome/Edge

### Technical Details
- Lane stored as "Lane X" format string, extracted on settings load
- Added `.col-info` CSS class for info cells
- Service worker cache version bumped to v63

---

# 2025-01-11

## **v4.1.15** - Chalker Tiebreak Warning & Bust Validation

### Chalker Enhancements
- **Tiebreak warning gradient**: Last 3 rows before tiebreak display with escalating amber background
  - Visual cue that the leg is approaching round limit
  - Dart count column gets progressively bolder (500 → 600 → 700)
- **Bust score rejection**: Scores exceeding remaining are now rejected instead of silently becoming 0
  - Consistent with other invalid score handling (>180, illegal scores, leaving 1)
  - To record a bust, explicitly enter 0

### Documentation
- Added `chalker/README.md` with feature overview and PWA installation guide

### Technical Details
- Added `.tiebreak-warning-1/2/3` CSS classes with escalating opacity and font-weight
- Changed bust handling from `recordVisit(0)` to `return` (reject)
- Service worker cache version bumped to v58

---

## **v4.1.14** - Chalker Edit Validation Fix & Delete Last Visit

### Bug Fixes
- **Edit validation fix**: Editing previous scores can no longer create invalid game states
  - Rejects edits that would make subsequent visits result in negative remaining (bust)
  - Rejects edits that would leave remaining of 1 (impossible finish)
  - Rejects edits that would create unprocessed checkouts (remaining = 0)

### Chalker Enhancements
- **Delete last visit**: Submit empty edit to delete the most recent visit
  - Tap the last score, press OK without entering digits
  - Visit is removed and player's turn is restored
  - Only works on the very last visit in the current leg

### Technical Details
- Added validation loop in `submitEditedScore()` to simulate subsequent visits
- Added empty input handling to delete last visit
- Service worker cache version bumped to v55

---

## **v4.1.13** - Chalker 140+ Stats

### Chalker Enhancements
- **140+ score tracking**: Stats now show three tiers of high scores
  - Tons (100+): All scores 100 and above (cumulative)
  - 140+: All scores 140 and above (cumulative, includes 180s)
  - 180s: Maximum scores only
- Displayed on Live Stats, Match Complete, and History Detail screens

### Technical Details
- Added `ton40s` counter to `calculateStats()` function
- Added 140+ row to all three stats tables in HTML
- Service worker cache version bumped to v53

---

## **v4.1.12** - Chalker Responsive Layout Fix

### Chalker Enhancements
- **Unified responsive layout**: Removed problematic 768-1023px portrait media query
  - All screen sizes now use the same base styles
  - Fixes broken layout on laptop browsers in portrait window orientation
  - Phone and tablet devices unaffected (they already worked correctly)
- **Optimized chalkboard font size**: Reduced from 2.25rem to 1.9rem
  - Better fit for ton rings without clipping
  - Maintains readability across all device sizes
- **Larger keypad buttons**: Increased vertical padding from 8px to 10px
  - Improved touch targets for easier tapping

### Technical Details
- Removed ~200 lines of tablet-specific CSS scaling rules
- Only remaining media query: landscape rotation for horizontal phone orientation
- Service worker cache version bumped to v52

---

## **v4.1.11** - Chalker Ton Ring Styling

### Chalker Enhancements
- **Ton ring on chalkboard**: Ton scores (100+) now display with a black oval ring around the number
  - Follows traditional darts chalking convention
  - Tight oval fit around just the digits (not the entire cell)
  - Maintains existing color coding (blue for 100-179, green for 180s)

### Technical Details
- Updated `renderChalkboard()` to wrap ton scores in `<span>` elements
- Added CSS for `.chalk-table .col-scored.ton span` with border styling
- Service worker cache version bumped to v47

---

## **v4.1.10** - Chalker Live Stats & Best-Of Indicator

### Chalker Enhancements
- **Live Stats screen**: New STATS button (replaced SETTINGS) shows real-time match statistics
  - Same layout as Match Complete and History Detail screens
  - Full statistics table: tons, 180s, short legs, high outs, first 9 avg, match avg, leg averages
  - Completed leg scoresheets with color coding (tons=blue, 180s=gold, checkouts=green)
  - Current leg in progress with "In Progress" badge and yellow highlight border
  - Current remaining scores shown at bottom of in-progress leg
  - Back button returns to scoring screen
- **Best-of indicator on chalkboard**: First row center cell now shows match length (e.g., "Bo3", "Bo5")
  - Replaces empty dart count cell in row 0
  - Styled distinctly from other numbers (smaller, secondary color)

### Technical Details
- Added Live Stats screen HTML with stats table and legs container
- Added `showLiveStats()` and `renderLiveStatsScoresheets()` functions
- Added CSS for `.in-progress-badge`, `.leg-in-progress`, `.current-remaining`
- Added `.col-bestof` styling for best-of indicator
- Updated `renderChalkboard()` to show `Bo${bestOf}` in first row
- Service worker cache version bumped to v44

---

# 2025-01-09

## **v4.1.9** - Chalker Edit Checkout Bug Fix & Touch Improvements

### Bug Fixes
- **Edit-after-opponent-entry checkout**: Fixed bug where editing a previous score to create a checkout after the opponent had already entered a visit would leave orphaned visit data and fail to advance to the next leg
  - Orphaned visits after the edited checkout are now removed
  - UI correctly advances to the next leg
  - Statistics and dart counts calculate correctly

### Improvements
- **Disable double-tap zoom on iOS**: Added `touch-action: manipulation` to prevent accidental zoom when tapping quickly on the keypad

### Technical Details
- Added `visits.splice()` in `completeEditCheckout()` to remove orphaned visits
- Changed to call `startNewLeg()` + `updateDisplay()` instead of just `updateDisplay()`
- Added `saveCurrentMatch()` call to persist state
- Service worker cache version bumped to v34

---

## **v4.1.8** - Chalker End Screen Unification

### Chalker Enhancements
- **Unified Match Complete screen**: End-of-match screen now matches History Detail format
  - Same stats table with tons, 180s, short legs, high outs, first 9 avg, match avg, and leg averages
  - Full leg-by-leg scoresheets with color coding (tons=blue, 180s=gold, short legs=purple, checkouts=green)
  - Consistent layout between viewing completed matches and finishing a match
- **History button on end screen**: Quick navigation to match history from Match Complete screen
- **24-hour time format**: Timestamps now display in 24H format instead of AM/PM
- **Dynamic short leg indicator**: Short leg threshold now varies by game variant using lookup table
  - 501: 21 darts, 301: 15 darts, 701: 27 darts, etc.

### Technical Details
- Replaced old end screen HTML with `history-detail-content` structure
- Added `renderEndScreenLegScoresheets()` function reusing history detail logic
- Changed `toLocaleTimeString()` calls to use `hour12: false`
- Short leg detection now uses `SHORT_LEG_THRESHOLDS[config.startingScore]`
- Added `.btn-tertiary` CSS class for History button
- Removed obsolete CSS (`.result-display`, `.match-players`, old `.winner-name`)
- Service worker cache version bumped to v29

---

## **v4.1.7** - Chalker Legibility & Bug Fixes

### Chalker Enhancements
- **System font for scores**: Scores now use native system fonts instead of Cascadia Code monospace
  - San Francisco on iOS, Roboto on Android, Segoe UI on Windows
  - Much cleaner and more legible at a distance
  - Tabular numerals keep digits aligned
- **Larger tablet keypad**: Increased button height on tablets for easier tapping

### Bug Fixes
- **Tie-break display fix**: Selecting a tie-break winner now correctly updates the display and starts the new leg
- **Tablet styles portrait-only**: Tablet scaling now only applies in portrait orientation, fixing oversized UI on desktop browsers

### Technical Details
- Added `--font-scores` CSS variable with system font stack
- Applied `font-variant-numeric: tabular-nums` for aligned digits
- Increased tablet keypad vertical padding from `--spacing-md` to `--spacing-xl`
- Added `updateDisplay()` call after tie-break winner selection
- Changed tablet media query to `(min-width: 768px) and (orientation: portrait)`

---

## **v4.1.5** - Chalker Viewport-Based Row Heights

### Chalker Enhancements
- **Viewport-based chalkboard rows**: Row heights now use `vh` units instead of fixed pixels
  - Rows automatically scale to show ~7-8 rounds on any screen size
  - Phones and tablets now display the same number of visible rows
  - Eliminates the "too many rows visible" problem on larger screens

### Technical Details
- Changed `.chalk-table td` height from fixed `44px`/`80px` to `6vh`
- Removed tablet-specific height override (no longer needed)
- Font sizes still scale via media query for readability

---

## **v4.1.4** - Chalker Tablet Scaling

### Chalker Enhancements
- **Tablet-optimized interface**: Responsive scaling for screens 768px and wider (~1.8x from phone)
  - Score anchors: 3rem → 5.5rem
  - Chalkboard cells: 44px → 80px height, 2.75rem fonts
  - Keypad buttons: 1.125rem → 2.25rem with larger touch targets
  - Form inputs, modals, and buttons all scaled up
  - Increased spacing throughout (8-56px vs 4-32px)

### Technical Details
- Added `@media screen and (min-width: 768px)` breakpoint
- CSS custom properties (spacing) scaled ~1.8x for tablets
- All screens affected: config, scoring, modals, end-of-match stats

---

# 2025-01-08

## **v4.1.3** - Chalker PWA (Progressive Web App)

### Chalker Enhancements
- **PWA Support**: Chalker can now be installed as a standalone app on mobile devices and desktops
  - Works fully offline after first visit
  - Add to home screen for native app-like experience
  - No browser chrome in standalone mode (clean, full-screen interface)
  - Portrait orientation locked
  - Dark theme status bar (#1a1a1a)

- **Self-Contained App Structure**: Chalker moved to dedicated `/chalker/` subfolder
  - Clean URL: `https://your-domain/chalker/`
  - All assets (JS, CSS, fonts, icons) contained within subfolder
  - Completely independent from Tournament Manager

### PWA Components
- **manifest.json**: App metadata for installation (name, icons, display mode, orientation)
- **sw.js**: Service worker with cache-first strategy for offline functionality
- **Icons**: 192×192 and 512×512 PNG icons generated from NewTon logo

### Technical Details
- Service worker caches: index.html, chalker.js, chalker.css, both fonts, both icons, manifest.json
- Cache versioning via `CACHE_NAME` constant (bump to force update)
- `skipWaiting()` and `clients.claim()` for immediate activation
- Apple-specific meta tags for iOS home screen support

### File Structure Change
```
Before: /chalker.html, /js/chalker.js, /styles/chalker.css
After:  /chalker/index.html, /chalker/js/chalker.js, /chalker/styles/chalker.css
        + /chalker/manifest.json, /chalker/sw.js, /chalker/fonts/, /chalker/images/
```

---

## **v4.1.2** - Chalker Mobile Display Improvements

### Chalker Enhancements
- **Two-line result display**: End-of-match result now shows on two lines for better mobile readability
  - Line 1: "Player 1 vs Player 2" with winner highlighted in green
  - Line 2: Final leg score (e.g., "2 - 1")
- **Per-leg stats reorganization**: Each stat now displays on its own line for clearer reading
  - Average (bold)
  - Darts count (highlighted if short leg)
  - Checkout score (highlighted if 101+)
  - 180s count
  - Tons count

### Technical Details
- Restructured result display HTML with `.match-players` container
- Added `.leg-stat-detail` CSS class for individual stat lines
- Updated `buildPlayerStats()` function to generate separate line elements

---

## **v4.1.1** - Chalker Stats Improvements

### Chalker Enhancements
- **Format-specific short leg thresholds**: Short legs now use correct dart thresholds based on starting score format (101: 4, 201: 8, 301: 13, 401: 17, 501: 21, 601: 25, 701: 29, 801: 34, 901: 38, 1001: 42)
- **Dynamic short legs label**: End-of-match stats screen now shows format-specific threshold (e.g., "Short Legs (≤21)" for 501)
- **Improved per-leg stats display**: Reorganized leg stats with better visual hierarchy
  - Line 1: Average (bold, primary stat)
  - Line 2: Checkout info showing darts and checkout score (e.g., "15 darts, 107 out")
  - Line 3: Scoring achievements (e.g., "1 × 180, 4 tons")
- **Compact keypad**: Reduced keypad height for better phone display
- **Chalkboard row overflow fix**: Reduced font size and row height to prevent 3-digit scores with cursor from wrapping

### Technical Details
- Added `SHORT_LEG_THRESHOLDS` constant mapping starting scores to dart thresholds
- Added `id="short-legs-label"` to HTML for dynamic label updates
- New CSS classes: `.leg-stat-avg`, `.leg-stat-checkout`, `.leg-stat-scoring` for visual hierarchy

---

# 2025-01-07

## **v4.1.0** - NewTon Chalker App & Bracket Enhancements

### Tournament Manager Improvements
- **Backside Match Source Visibility**: Hovering over backside matches now shows which matches feed into them
  - Status bar displays "Fed by FS-X-X, FS-X-X" between match state and destination
  - Extracted reusable `buildMatchSourcesLookup()` function in analytics.js
  - Helps referees and organizers track player progression through losers bracket
- **Status Bar Styling**: Floating tooltip now has slight offset from bottom edge for cleaner appearance

### New Feature: Companion Scoring App
- **NewTon Chalker**: Tablet-optimized x01 dart scoring application for referees/chalkers
  - Standalone companion app to the main Tournament Manager
  - Designed for portrait tablet use at dartboards
  - Fully offline - no server or internet required

### Chalker Features
- **Match Configuration**
  - Player names entry
  - Starting score selection (101-1001)
  - Best-of legs (1-11)
  - Max rounds configuration (7-20 rounds / 21-60 darts)
  - Double-in toggle option

- **Scoring Interface**
  - Large, readable score display with active player highlight (green tint)
  - Leg starter indicated by green player name in header (alternates each leg)
  - Centered leg score display in header
  - Chalkboard-style ledger with continuous grid lines (HTML table)
  - Inline score input directly in chalkboard cells with blinking cursor
  - Excel-like editing: tap any recorded score to edit (pre-populates existing value)
  - Auto-scroll to keep active input row visible
  - Touch-friendly numpad with DEL and OK buttons
  - Tons (100+) highlighted in blue, 180s in green
  - Grey background on dart count column for visual separation

- **Match Flow**
  - Automatic player turn alternation
  - Checkout detection with dart count prompt (1/2/3 darts)
  - Leg win tracking with automatic new leg start
  - Match completion detection based on best-of setting

- **End-of-Match Statistics**
  - Winner/loser display with final leg score
  - Tons (100+) count per player
  - 180s count per player
  - Short legs (≤21 darts) count
  - High checkouts (101+) count
  - First 9 dart average per player
  - Overall match average per player
  - Per-leg averages breakdown

- **Match Management**
  - Menu with Rematch and New Match options
  - Confirmation dialogs to prevent accidental data loss
  - Edit mode for correcting previously entered scores

### Technical Details
- **Files added**:
  - `chalker.html` - Main HTML structure with semantic table for chalkboard
  - `styles/chalker.css` - Tablet-optimized styling with CSS variables
  - `js/chalker.js` - Complete scoring logic and state management
- **Architecture**: Self-contained IIFE with clean state management
- **Styling**: Reuses NewTon font stack (Manrope, Cascadia Code)

---

# 2025-11-21

## **v4.0.16** - Header Clock

### New Features
- **Added clock to main header**
  - Clock displayed in upper right corner, aligned with title/logo
  - The clock is useful, since the app often runs in full-screen which hides the system clock
  - Styled identically to Match Controls clock (border, shadow, monospace font)
  - Visible on all pages (Setup, Registration, Tournament, Config)
  - Updates every 10 seconds to catch minute changes
  - **Files modified**: `tournament.html`, `css/styles.css`, `js/tournament-management.js`

---

# 2025-11-19

## **v4.0.15** - JSDoc Type Definitions & Function Annotations

### Developer Experience
- **Added comprehensive JSDoc type definitions for all core data structures**
  - **New file**: `js/types.js` - Centralized type definitions for IDE support
  - **Core types defined**:
    - `Player` - All properties including stats, placement, eliminated, isBye
    - `PlayerStats` - shortLegs, highOuts, tons, oneEighties
    - `Match` - Complete with 16+ properties including finalScore
    - `Tournament` - Full structure with placements map
    - `Config` - All 5 sub-configs (Points, Legs, Lanes, UI, Server)
    - `Transaction` - Complete undo/history system types
    - `MatchProgression` - Lookup table structure
  - **Supporting types**: MatchState, TournamentStatus, TransactionType, CompletionType, MatchSide
  - **Global variable documentation**: @global tags for tournament, players, matches, config
  - **MATCH_PROGRESSION constant**: Documented with @global, @constant, @type, @example tags
  - **Prioritized TODO list**: Documents which functions to annotate incrementally
  - **Files added**: `js/types.js`
  - **Files modified**: `tournament.html` (added types.js to script loading)

- **Added JSDoc annotations to Priority 1 core progression functions**
  - **advancePlayer()** - Parameters, return type, example with winner/loser flow
  - **completeMatch()** - All 5 parameters documented with types and defaults
  - **calculateAllRankings()** - Description of ranking logic by bracket size
  - **processAutoAdvancements()** - Walkover handling and rebuild protection notes
  - **generateCleanBracket()** - Validation rules, bracket sizing, usage example
  - **Files modified**: `js/clean-match-progression.js`

- **Added JSDoc annotations to Priority 2 tournament management functions**
  - **createTournament()** - Entry point for new tournaments, state initialization
  - **saveTournament()** - Debounced wrapper with UI updates
  - **saveTournamentOnly()** - Core save logic, config separation
  - **loadSpecificTournament()** - Entry point showing confirmation modal
  - **continueLoadProcess()** - Actual loading into global state
  - **exportTournament()** - Export format, history pruning, file download
  - **importTournament()** - File handling, JSON parsing, format support
  - **Updated types.js TODO**: Corrected function names to match actual implementation
  - **Files modified**: `js/tournament-management.js`, `js/types.js`

- **Added JSDoc annotations to Priority 3 player management functions**
  - **addPlayer()** - Creates player from form input, validation, auto-adds to Saved Players
  - **removePlayer()** - Removes player by ID, blocked during active tournament
  - **togglePaid()** - Toggles payment status, help hints for bracket readiness
  - **Updated types.js TODO**: Corrected function signatures to match actual implementation
  - **Files modified**: `js/player-management.js`, `js/types.js`

- **Added JSDoc annotations to Priority 4 match state functions**
  - **getMatchState()** - Returns match state (pending/ready/live/completed) for UI rendering
  - **showMatchCommandCenter()** - Opens modal with live and ready matches, referee suggestions
  - **populateRefereeSuggestions()** - Populates referee panel with losers, winners, recent assignments
  - **Updated types.js TODO**: Corrected Priority 5 function names to match actual implementation
  - **Files modified**: `js/bracket-rendering.js`, `js/types.js`

- **Added JSDoc annotations to Priority 5 history/undo system functions**
  - **isMatchUndoable()** - Checks if match can be safely undone without breaking integrity
  - **getConsequentialMatches()** - Finds all matches affected by undoing a transaction
  - **handleSurgicalUndo()** - Entry point showing confirmation modal with affected matches
  - **undoManualTransaction()** - Performs surgical undo by removing transaction and rebuilding
  - **rebuildBracketFromHistory()** - Rebuilds entire bracket state from transaction history
  - **Files modified**: `js/bracket-rendering.js`

- **Benefits**:
  - ✅ IDE autocomplete for all properties
  - ✅ Full hover documentation in VSCode for types and functions
  - ✅ Parameter descriptions visible on function calls
  - ✅ Return types and examples in tooltips
  - ✅ Types reference defined typedefs (e.g., `Player`, `CompletionType`)
  - ✅ Type checking and error detection
  - ✅ Self-documenting codebase
  - ✅ Easier onboarding for contributors

- **Motivation**: Implements Gemini code review suggestion to "make implicit contracts explicit"

- **Code Review Documentation**:
  - See `Docs/CodeReview/JSDOC-ANNOTATIONS-REVIEW.md` for JSDoc implementation analysis
  - See `Docs/CodeReview/SINGLE-SOURCE-OF-TRUTH.md` for architectural analysis
  - See `Docs/CodeReview/FUNCTION-REUSE-ANALYSIS.md` for reuse patterns and metrics
  - See `Docs/CodeReview/REVIEW-VERDICT.md` for overall code quality assessment

---

# 2025-11-17

## **v4.0.14** - Match Controls Configuration Display Fix

### Bug Fixes
- **Fixed tournament configuration display showing in active and completed tournament states**
  - **Issue**: Tournament configuration settings were visible in Match Controls during active and completed tournament states, not just setup mode
  - **Root cause**: The `updateTournamentConfigDisplay()` function was only called in the `'setup'` case but always set `display: 'block'`. Once shown, the configuration was never hidden when tournament status changed
  - **Fix**: Added explicit hide logic in both `'completed'` and `'active'` cases to ensure configuration display only appears during setup mode
  - **Behavior**:
    - **Setup mode**: Configuration display shows tournament settings (point values, match configuration, lanes)
    - **Active mode**: Configuration display hidden, referee suggestions shown
    - **Completed mode**: Configuration display hidden, tournament achievements shown
  - **Impact**:
    - ✅ Configuration settings only visible when relevant (setup mode)
    - ✅ Cleaner Match Controls interface during active tournaments
    - ✅ Consistent state-driven UI behavior across tournament lifecycle
  - **Files modified**: `js/bracket-rendering.js` (lines 3510-3511, 3520-3521)

---

## **v4.0.13** - Results Table Column Width Adjustments

### UI Improvements
- **Adjusted results table column widths to prevent text wrapping**
  - **Issue**: "Rank" column text was splitting over two lines, and "Legs Lost" column header had unwanted line breaks
  - **Changes**:
    - **Rank column**: Increased width from 5% to 9% (prevents "Rank" from wrapping)
    - **Player Name column**: Decreased width from 25% to 24% (compensate for rank increase)
    - **Points column**: Decreased width from 10% to 9% (balance layout)
  - **Impact**:
    - ✅ Cleaner table presentation with no text wrapping
    - ✅ Improved readability of leaderboard
    - ✅ Better column balance across different screen sizes
  - **Files modified**: `css/styles.css` (lines 2927, 2933, 2941)

---

## **v4.0.12** - Referee Conflict Indicator Fix & Tournament Configuration Display

### Features
- **Added tournament configuration display in Match Controls**
  - **Motivation**: Tournament operators frequently need to reference configuration settings during setup and active tournaments without navigating away from Match Controls
  - **Location**: Displays in main Match Controls panel below participant list during setup mode
  - **Layout**: 4-column grid layout for optimal space usage
    - **Column 1 (17%)**: Point Values - Participation and placement points (1st through 7th-8th)
    - **Column 2 (20%)**: Achievement Points - High Out, Short Leg, 180, Ton (no header for visual continuity)
    - **Column 3 (35%)**: Match Configuration - Regular Rounds, FS/BS Semifinals, BS Final, Grand Final
    - **Column 4 (23%)**: Lanes - Available range and excluded lanes
  - **Styling**: Matches existing Match Controls aesthetic with simple headers and gray text values
  - **Header**: "Tournament Configuration (Change in Global Settings Page)" - clearly indicates where to make changes
  - **Implementation**:
    - JavaScript function `updateTournamentConfigDisplay()` populates values from global `config` object
    - Called automatically when Match Controls opens in setup mode
    - Minimal CSS: Single `.config-display-grid` class with 4-column layout (17% 20% 35% 23%)
  - **Impact**:
    - ✅ Quick reference to all configuration settings without navigation
    - ✅ Helps operators verify settings before generating bracket
    - ✅ Reduces need to switch between Match Controls and Global Settings pages
    - ✅ Clean, non-intrusive display that matches existing UI patterns
  - **Files modified**:
    - `tournament.html` (lines 856-898): Configuration display HTML structure
    - `css/styles.css` (lines 1513-1519): 4-column grid CSS
    - `js/bracket-rendering.js` (lines 3502, 4209-4245): Population function and call in setup mode

### Bug Fixes
- **Fixed referee conflict indicator showing on completed matches**
  - **Issue**: Completed matches were displaying "⚠️ [Name] (Referee)" when players were refereeing other matches, causing visual clutter and confusion
  - **Problem**: The referee conflict warning is only relevant for matches that can be started (pending/ready/live). For completed matches, this information is unnecessary since:
    - The match is already finished and cannot be restarted
    - Conflict detection doesn't apply to past matches
    - It creates visual confusion when combined with the actual referee assignment (e.g., "Nick (Referee)" displayed alongside "Ref: Benedict")
  - **Solution**: Modified referee conflict indicator to only display when `matchState !== 'completed'`
  - **Behavior**:
    - **Completed matches**: Display clean player names without referee conflict indicators
    - **Pending/Ready/Live matches**: Continue to show "⚠️ [Name] (Referee)" warning when player is refereeing another match
  - **Impact**:
    - ✅ Cleaner visual presentation of completed matches
    - ✅ Eliminates confusing dual-referee display ("Nick (Referee)" + "Ref: Benedict")
    - ✅ Maintains important conflict warnings for active/future matches
    - ✅ Reduces visual noise in bracket view
  - **Files modified**: `js/bracket-rendering.js` (lines 1068-1075)

---

## **v4.0.11** - UI Typography & Demo Header Spacing

### UI Improvements
- **Updated page title/logo/header font from "Droid Serif" to "Insignia Regular"**
  - **Font choice**: Insignia Regular is the font used on Unicorn darts weight certificates
  - **Rationale**: Subtle darts-themed branding reference for the tournament management software
  - **Impact**:
    - ✅ Darts-specific typography adds thematic consistency
    - ✅ Maintains professional appearance
    - ✅ Easter egg for Unicorn darts users
  - **Files modified**: CSS font-family declarations for page headers

- **Improved demo mode header spacing**
  - **Change**: Added spacing and hyphen between descriptive text and "View on GitHub" link
  - **Impact**:
    - ✅ Better visual separation between information and action link
    - ✅ Improved readability
  - **Files modified**: `tournament.html` (demo banner section)

---

# 2025-11-04

## **v4.0.10** - Unpaid Players Validation

### Enhancements
- **Added validation to prevent bracket generation when unpaid players exist**
  - **Issue**: Operators could accidentally generate brackets with unpaid players still in the tournament, leading to confusion and manual workarounds with BYE slots
  - **Solution**: Added validation check that blocks bracket generation if any players have unpaid status
  - **Validation behavior**:
    - Runs before bracket generation, after tournament existence and duplicate bracket checks
    - Checks for any players with `paid: false` status
    - If unpaid players detected: Shows alert and blocks generation
    - If all players paid: Proceeds with normal bracket generation
  - **Alert message**: "All players must be marked as paid to generate bracket. Go to Player Registration to update payment status or remove players."
  - **Operator workflow**:
    1. Attempt to generate bracket with unpaid players
    2. Receive clear alert with guidance
    3. Navigate to Player Registration page
    4. Either mark players as paid or remove them from tournament
    5. Return to Setup and generate bracket successfully
  - **Impact**:
    - ✅ Prevents operator error: Forgetting to mark players as paid before draw
    - ✅ Eliminates need for manual BYE slot workarounds
    - ✅ Clear guidance: Directs operators to exact location to fix issue
    - ✅ Maintains data integrity: Bracket only generated when all players properly registered
    - ✅ Console logging: Error logged with unpaid player count for debugging
  - **Files modified**: `js/clean-match-progression.js` (lines 884-890)

---

# 2025-11-03

## **v4.0.9** - localStorage Storage Indicator & Demo Banner Update

### Features
- **Added visible localStorage storage utilization indicator**
  - **Storage link in Recent Tournaments header**: Right-aligned "Storage: X%" link with color-coded thresholds
  - **Color coding**:
    - Green (<75%): Healthy storage usage
    - Yellow (75-90%): Running low on space
    - Amber (>90%): Almost full, action needed
  - **Interactive modal with usage details**:
    - Horizontal progress bar matching color threshold
    - Current usage (X MB of Y MB available)
    - Status message (Good/Running low/Almost full)
    - Breakdown: Tournaments, Tournament History, Settings & Players
    - Non-technical instructions for freeing space (export then delete old tournaments)
    - Optional advanced section when history exceeds 1MB (suggests Developer Console cleanup)
  - **ESC key support**: Integrates with existing modal stack system
  - **Automatic updates**: Storage indicator refreshes after tournament save/delete/import and on page load
  - **Reuses existing code**: Leverages `getLocalStorageStats()` from analytics.js and modal stack system
  - **Impact**:
    - ✅ Prevents localStorage-full situations during tournaments
    - ✅ User-friendly visibility of storage usage (no need to open Developer Console)
    - ✅ Clear, non-technical guidance for operators
    - ✅ Proactive warning system before storage becomes critical
  - **Files modified**: `tournament.html` (line 106), `css/styles.css` (lines 3071-3262), `js/tournament-management.js` (lines 329-331, 823-826, 990-993, 1463-1669), `js/main.js` (lines 189-194)

### UI Improvements
- **Updated demo-mode header banner text**
  - **Previous text**: "Demo Site. Everything you do is stored locally in your browser. Your data never leaves your device."
  - **New text**: "Darts double elimination tournament software. Free, open-source, secure, offline first, self-hostable. 📍 Demo Site: Everything you do is stored locally in your browser. Your data never leaves your device."
  - **Rationale**: Provides more context about the software itself for first-time visitors to demo site
  - **Impact**:
    - ✅ More informative for new users discovering the project
    - ✅ Highlights key features (free, open-source, secure, offline-first, self-hostable)
    - ✅ Maintains privacy transparency with location pin emoji separator
  - **Files modified**: `tournament.html` (line 37)

---

# 2025-11-01

## **v4.0.8** - Docker Documentation & Match Controls Fix

### Docker Documentation
- **Updated all Docker documentation to prioritize Docker Hub over GHCR**
  - **DOCKER-QUICKSTART.md**: Changed primary registry from GHCR to Docker Hub in all examples and documentation
  - **docker/README.md**: Reordered "Publishing to Docker Registries" section to show Docker Hub first, updated "Using Published Image" section with Docker Hub as recommended option
  - **docker/docker-compose.yml**: Changed default image from `ghcr.io/skrodahl/newton:latest` to `skrodahl/newton:latest` with GHCR as commented alternative
  - **docker/docker-compose-demo.yml**: Updated image to `skrodahl/newton:latest` (also updated version from 3.0.5-beta to latest)
  - **Rationale**: Aligns documentation with actual user behavior (90+ Docker Hub pulls vs 8 GHCR pulls), provides simpler syntax, and matches user expectations
  - **Impact**:
    - ✅ Documentation now reflects real-world usage patterns
    - ✅ Cleaner syntax for users (`skrodahl/newton` vs `ghcr.io/skrodahl/newton`)
    - ✅ GHCR still documented as alternative for GitHub-native users
    - ✅ All docker-compose files use consistent registry by default
  - **Files modified**: `DOCKER-QUICKSTART.md`, `docker/README.md`, `docker/docker-compose.yml`, `docker/docker-compose-demo.yml`

### Bug Fixes
- **Fixed Match Controls match sorting to use numerical order instead of alphabetical**
  - **Issue**: Matches sorted alphabetically (FS-1-1, FS-1-10, FS-1-11, FS-1-15, FS-1-16, FS-1-2) instead of numerically
  - **Root cause**: `localeCompare()` string sorting on match IDs treated them as text
  - **Fix**: Parse match number from ID (third segment after second hyphen) and sort numerically
  - **Applies to**:
    - Ready matches grouped by round (Frontside and Backside)
    - LIVE matches when lanes are equal or both missing (fallback sort)
  - **Impact**:
    - ✅ Match Controls now displays matches in correct numerical order: FS-1-1, FS-1-2, FS-1-10, FS-1-11, FS-1-15, FS-1-16
    - ✅ Consistent sorting for both Frontside and Backside brackets
    - ✅ Lane-based sorting for LIVE matches still prioritized, numerical sort as tiebreaker
  - **Files modified**: `js/bracket-rendering.js` (lines 2730-2762)

---

# 2025-10-31

## **v4.0.7** - Documentation & Distribution Enhancements

### Documentation
- **Security headers documentation added to Docker deployment guides**
  - **DOCKER-QUICKSTART.md**: Added comprehensive "Security Headers" section with overview of all headers included by default (X-Frame-Options, X-Content-Type-Options, Referrer-Policy, Permissions-Policy, CSP), A-grade security rating information, CSP configuration details, HSTS guidance for reverse proxies, and impact summary
  - **docker/README.md**: Added detailed "Security Headers" section with full explanation of each header, CSP rationale (why 'unsafe-inline' is required and acceptable), HSTS configuration examples for Nginx Proxy Manager and Caddy, testing instructions, and expected security rating results
  - **Docs/PRIVACY.md**: Added "Security Headers and Privacy" subsection under "Self-Hosting Considerations" explaining how security headers complement the privacy-by-architecture model, focusing on privacy-enhancing headers (Referrer-Policy, CSP, Permissions-Policy)
  - **Impact**:
    - ✅ Security features now prominently documented for self-hosters
    - ✅ Comprehensive technical explanation available for developers
    - ✅ Privacy documentation shows how headers enhance privacy guarantees
    - ✅ Clear guidance on HSTS configuration at reverse proxy level
    - ✅ Testing instructions for verifying A-grade security rating
  - **Context**: Security headers were implemented in v4.0.0 but not fully documented in Docker deployment guides
  - **Files modified**: `DOCKER-QUICKSTART.md`, `docker/README.md`, `Docs/PRIVACY.md`

### Distribution
- **Docker Hub publishing workflow added**
  - **New workflow**: `.github/workflows/docker-hub-publish.yml` - Separate GitHub Action workflow for publishing to Docker Hub
  - **Architecture**: Independent from existing GHCR workflow to avoid disrupting current publishing
  - **Features**:
    - Multi-architecture support (AMD64 + ARM64)
    - Triggered by version tags (v4.0.7, etc.) or manual dispatch
    - Uses GitHub secrets for authentication (DOCKERHUB_USERNAME, DOCKERHUB_TOKEN)
    - Automatic tagging: latest, semantic versions (major.minor.patch, major.minor, major)
    - GitHub Actions cache for faster builds
  - **Impact**:
    - ✅ Images now available on Docker Hub for better discoverability
    - ✅ No impact on existing GHCR publishing workflow
    - ✅ Both registries updated automatically on version tags
    - ✅ Self-hosters can choose preferred registry (Docker Hub or GHCR)
  - **Files added**: `.github/workflows/docker-hub-publish.yml`

---

# 2025-10-30

## **v4.0.6** - Dynamic Navigation Menu Enhancement

### Enhancements
- **Navigation menu underline now dynamically calculated**
  - **Previous implementation**: Hardcoded pixel values for menu underline position (41px, 87px, 91px, 49px) and manually calculated left positions based on cumulative widths + gaps
  - **Issue**: Fragile and required manual remeasurement whenever fonts, text, or styling changed
  - **New implementation**:
    - JavaScript automatically measures button dimensions and positions using `getBoundingClientRect()`
    - CSS custom properties (`--nav-underline-left`, `--nav-underline-width`, `--nav-underline-opacity`) control underline position
    - Updates on page load, page navigation, and window resize
  - **Impact**:
    - ✅ Maintenance-free - no more manual pixel measurements
    - ✅ Font-agnostic - adapts to any font family, size, or weight changes
    - ✅ Text-agnostic - menu items can be renamed without touching CSS
    - ✅ Layout-agnostic - adapts to gap, padding, or spacing adjustments
    - ✅ Responsive - automatically recalculates on window resize
  - **Code cleanup**: Removed 36 lines of hardcoded CSS positioning rules, replaced with 11 lines using CSS variables
  - **Files modified**: `css/styles.css`, `js/main.js`

- **Improved navigation menu clarity**
  - **Previous labels**: "Setup", "Registration", "Tournament", "Config"
  - **New labels**: "Tournament Setup", "Player Registration", "Tournament Bracket", "Global Settings"
  - **Impact**:
    - ✅ More descriptive and immediately understandable for new users
    - ✅ Reduces need for trial-and-error navigation
    - ✅ Professional and consistent naming pattern
    - ✅ Takes advantage of desktop screen space for clarity
  - **Files modified**: `tournament.html`

### Code Cleanup
- **Removed duplicate `showPage()` function**
  - **Issue**: Two identical `showPage()` function definitions existed in main.js (lines 292-307 and 391-434)
  - **Action**: Removed the simpler unused version, kept the full-featured version with help system integration, match controls, and navigation underline updates
  - **Impact**: Eliminated 15 lines of dead code
  - **Files modified**: `js/main.js`

### Documentation
- **PARKING-LOT.md now empty**
  - All known polish items and technical debt resolved
  - "Header Menu" dynamic underline rewrite completed and removed from backlog

## **v4.0.5** - UI Terminology Updates

### Enhancements
- **Renamed "Statistics" to "Leaderboard" throughout the application**
  - **Previous terminology**: Various UI elements referred to the player rankings table as "Statistics" or "Tournament Results"
  - **New terminology**: Unified naming to "Leaderboard" for clarity and consistency
  - **Changes made**:
    - Tournament page navigation button: "Statistics" → "Leaderboard"
    - Statistics modal heading: "Tournament Statistics" → "Leaderboard"
    - Registration page heading: "Tournament Results" → "Leaderboard"
    - Match Controls modal button: "Statistics" → "Leaderboard"
    - Help system updated with new terminology (2 references)
  - **Context preserved**: "Player Statistics" (individual player achievements editor) remains unchanged, as it feeds data into the Leaderboard
  - **Impact**:
    - ✅ Clearer user interface - "Leaderboard" immediately conveys competitive ranking
    - ✅ Consistent terminology across Tournament, Registration, Match Controls, and Help system
    - ✅ Distinguishes between individual player stats (achievements) and tournament rankings (leaderboard)
  - **Files modified**: `tournament.html`, `js/dynamic-help-system.js`

- **Renamed "Tournament" header to "Active Tournament"**
  - **Previous behavior**: Header showed "Tournament: My Tournament (2025-10-27)"
  - **New behavior**: Header shows "Active Tournament: My Tournament (2025-10-27)"
  - **Impact**: More descriptive label indicates the currently active/selected tournament
  - **Files modified**: `tournament.html`, `js/tournament-management.js`

- **Renamed "Match Results" to "Match History" on Setup page**
  - **Previous behavior**: Setup page showed "Match Results" heading for completed matches
  - **New behavior**: Shows "Match History: My Tournament (2025-10-27)" with dynamic tournament name
  - **Implementation**:
    - Heading now updates dynamically with active tournament name and date
    - Date portion uses normal font weight (not bold) for better visual hierarchy
    - Shows "Match History: None" when no tournament is active
  - **Impact**:
    - ✅ More descriptive label clarifies this is a historical log, not just results
    - ✅ Consistent with tournament context (shows which tournament's history)
  - **Files modified**: `tournament.html`, `js/main.js`, `js/dynamic-help-system.js`

- **Adjusted column header font size**
  - **Previous size**: 1rem
  - **New size**: 1.15rem
  - **Impact**: Improved readability and visual hierarchy for section headings
  - **Files modified**: `css/styles.css`

- **Unified "Saved Players" header structure with other column headers**
  - **Previous behavior**: "Saved Players" header used custom `.player-list-header` div with 16px font size, inconsistent with other column headers
  - **New behavior**: Uses standard `<h3>` element matching "Tournament Players", "Leaderboard", and "Match History" headers
  - **Implementation**:
    - Replaced custom `.player-list-header` div with standard `<h3>` element
    - "Saved Players" title now uses consistent 1.15rem font size
    - Right-aligned content (hint text + Import button) flows naturally using existing `justify-content: space-between` CSS
    - Button styling adjusted to maintain compact appearance (12px font, 28px height)
  - **Impact**:
    - ✅ Consistent visual hierarchy across all Registration page column headers
    - ✅ Simpler codebase - eliminates custom header structure
    - ✅ All headers now use same styling pattern
  - **Files modified**: `tournament.html`

---

## **v4.0.4** - Font System Improvements

### Enhancements
- **Unified font architecture with CSS variable control**
  - **Previous behavior**: Fonts were inconsistently applied across the application with hardcoded inline styles and varying system font fallbacks
  - **New implementation**:
    - Added `--font-body` CSS variable for centralized body text font control (currently set to Manrope)
    - Added `--font-clock` CSS variable for Match Controls clock font control (modern monospace: SF Mono/Cascadia Code)
    - Created `.match-controls-clock` CSS class to replace 150+ character inline style strings
  - **Font standardization**:
    - Bracket placement titles ("7th-8th Place", "FRONTSIDE", "BACKSIDE") → Inter font
    - Watermarks (left and center) → Inter font
    - Tournament header (bracket page title and date) → Inter font (changed from Arial in JavaScript)
    - Match Controls clock → SF Mono/Cascadia Code/Consolas (distinctive modern monospace, avoids console-style Courier New)
  - **Impact**:
    - ✅ Consistent cross-platform font rendering (Mac, Windows, Linux)
    - ✅ Single point of control: Change `--font-body` or `--font-clock` CSS variables to update fonts application-wide
    - ✅ Match Controls clock uses distinctive monospace (maintains consistent width while avoiding Courier's terminal aesthetic)
    - ✅ Clean code: CSS classes replace inline style strings in JavaScript
    - ✅ CAD watermark preserves technical monospace aesthetic (Courier/Monaco) for engineering/technical appearance
  - **Files modified**: `css/styles.css`, `js/bracket-lines.js`, `js/bracket-rendering.js`

---

## **v4.0.3** - Developer Console Enhancement

### Enhancement
- **Developer Console: Show placement ranks in "View Match Progression"**
  - **Previous behavior**: When viewing match progression in Developer Console, eliminated players showed only "→ TO: ❌" with no placement information
  - **New behavior**: Now shows placement rank alongside elimination icon (e.g., "→ TO: ❌ 3rd" for BS-FINAL loser, "→ TO: ❌ 5th-6th" for BS-2 losers)
  - **Implementation**:
    - Reuses existing `getEliminationRankForMatch()` function from `main.js` (hardcoded rank mappings for 8/16/32 player brackets)
    - Reuses existing `formatRanking()` function from `results-config.js` (formats ranks as "3rd", "5th-6th", "13th-16th", etc.)
    - Added defensive programming with function availability checks
    - Zero code duplication - leverages same rank display logic used in Winner Confirmation modal, Match Controls, and Match History
  - **Impact**:
    - ✅ Developer Console now shows consistent placement information with rest of UI
    - ✅ Makes "View Match Progression" more informative for tournament analysis
    - ✅ Displays exact elimination rank for all backside bracket matches
    - ✅ Single source of truth for all placement displays across application
  - **Files modified**: `js/analytics.js`

---

## **v4.0.2** - Referee Conflict Detection and Pre-v4.0 Import Optimization

### Bug Fixes
- **Fixed referee conflict detection bypass in Tournament Bracket**
  - **Previous behavior**: Match Controls prevented starting matches when players were refereeing other matches, showing "⚠️ [Name] (Referee)" warnings and disabling Start buttons
  - **Issue discovered**: Tournament Bracket view had no referee conflict validation - matches could be started directly from bracket, bypassing the conflict check
  - **Root cause**: Match Controls had its own duplicate conflict detection logic, while bracket rendering had none
  - **Solution implemented**:
    - Created shared `checkRefereeConflict()` utility function in `bracket-rendering.js`
    - Created `toggleActiveWithValidation()` wrapper in `clean-match-progression.js` that validates before starting matches
    - Updated bracket rendering to show visual warnings ("⚠️ [Name] (Referee)") and disable Start buttons when conflicts exist
    - Replaced duplicate conflict detection in Match Controls with shared utility function
    - Updated match state notification box to show "Blocked: [Name] refereeing" instead of "Ready to Start"
  - **Impact**:
    - ✅ Both Tournament Bracket and Match Controls now use identical referee conflict validation
    - ✅ Eliminates code duplication and maintains single source of truth
    - ✅ Prevents tournament state corruption from simultaneous player participation and refereeing
    - ✅ Consistent user experience across all views
  - **Implementation details**:
    - Base `toggleActive()` function preserved for backward compatibility (Developer Console, programmatic operations)
    - Follows existing pattern: base function + validation wrapper (similar to `updateMatchLane` / `updateMatchLaneWithValidation`)
    - Visual conflict indicators update on bracket re-render
  - **Files modified**: `js/bracket-rendering.js`, `js/clean-match-progression.js`

### Performance Improvements
- **Optimized pre-v4.0 tournament import to prevent localStorage bloat**
  - **Issue discovered**: Pre-v4.0 exports contain snapshot-based transaction history where each transaction includes a full copy of the entire tournament state in `beforeState`. A typical 32-player tournament had 178 transactions totaling 8.56 MB of redundant data.
  - **Root cause**: Pre-v4.0 used snapshot-based undo system (save full state before each action). v4.0 switched to replay-based undo (save only changes, reconstruct state by replaying). The formats are incompatible - v4.0 cannot use pre-v4.0 snapshots for undo operations.
  - **Problem**: Importing pre-v4.0 history consumed massive localStorage space (8+ MB per tournament) and provided no functionality since v4.0 undo system cannot use the snapshots.
  - **Solution implemented**:
    - Modified import logic to detect old format exports
    - Skip importing transaction history for pre-v4.0 formats
    - Continue importing all tournament data (players, matches, bracket, placements, results)
    - Log clear message: "⚠ Skipped importing X pre-v4.0 history entries (incompatible snapshot format, ~Y MB)"
  - **Impact**:
    - ✅ Prevents localStorage bloat (saves 8-10 MB per pre-v4.0 tournament import)
    - ✅ Eliminates risk of hitting browser localStorage quota limits
    - ✅ Tournament data (players, matches, results, placements) still imports correctly
    - ✅ Faster imports (no need to parse/store massive history)
    - ✅ Existing "Pre-v4.0 format: Undo not available" warning remains accurate
    - ✅ v4.0+ tournament imports continue to work normally with full undo functionality
  - **Technical details**:
    - Pre-v4.0 snapshot format: Each transaction stored entire tournament state (~50 KB each)
    - v4.0 replay format: Each transaction stores only changes (~200 bytes each)
    - Size reduction: 98.8% less localStorage usage for imported pre-v4.0 tournaments
    - The incompatible snapshot data was being imported but never used by v4.0 undo system
  - **Files modified**: `js/tournament-management.js`
  - **Related**: Resolved PARKING-LOT item "Check if pre-v4.0 transaction log can be imported" - determined that pre-v4.0 history exists but is incompatible with v4.0 undo system and should be skipped

# 2025-10-27

## **v4.0.1** - Code Cleanup and Documentation Updates

### Code Cleanup
- **Removed unused history-management.js**
  - **Previous state**: Legacy snapshot-based undo system file remained in codebase
  - **Issue**: File was not loaded in tournament.html and functions were never called
  - **Action taken**: Deleted from codebase
  - **Impact**:
    - ✅ Cleaner codebase with only actively used files
    - ✅ No functionality affected (file was already unused)
    - ✅ Completes migration to transaction-based history system introduced in v4.0.0
  - **Context**: v4.0.0 introduced per-tournament transaction-based history in `clean-match-progression.js`, making the old snapshot-based system in `history-management.js` obsolete
  - **Files removed**: `js/history-management.js`

### Documentation Updates
- **Overhauled IMPORT_EXPORT.md to match current reality**
  - **Export Schema Section**:
    - Fixed `shortLegs` type documentation: Changed from `number` to `array of integers`
    - Updated all example IDs and timestamps to match real export data
    - Added inline comments explaining each field type
    - Fixed `status` field to show all three states: `"setup|active|completed"`
  - **New Detailed Sections Added**:
    - `playerList` field format: Documented as simple array of strings (not player objects)
    - `placements` field format: Documented key-value structure (playerID → rank)
    - Player Object Structure: Complete schema with all fields and types
    - Match Object Structure: Added ALL missing fields (`numericId`, `positionInRound`, `autoAdvanced`, `completedAt`, `finalScore`)
    - Walkover player structure: Documented `isBye` flag and ID format
    - TBD player structure: Documented incomplete bracket placeholder format
  - **Transaction History Complete Rewrite**:
    - Replaced misleading simplified examples with actual transaction structures
    - Documented all 5 transaction types: `COMPLETE_MATCH`, `START_MATCH`, `STOP_MATCH`, `ASSIGN_LANE`, `ASSIGN_REFEREE`
    - Documented transaction ID format: `tx_{timestamp}`
    - Documented `completionType`: `MANUAL` vs `AUTO`
    - Showed that `COMPLETE_MATCH` transactions contain full player objects (not just IDs)
  - **Critical Clarification: Stats in Match Objects**:
    - **Added important note**: Stats embedded in match objects are historical snapshots only
    - **Single source of truth**: Global `players` array is ONLY source for Statistics table and points
    - **Never used for calculations**: Match/transaction stats are for audit trail and history keeping
    - **Architecture benefit**: Stat corrections immediately affect results without recalculating historical data
    - **Impact**: Prevents confusion about which stats data is authoritative
  - **Import/Export Function Updates**:
    - Updated `validateTournamentData` to match actual implementation
    - Fixed variable naming: `isPreV4` → `isOldFormat`
    - Updated `continueImportProcess` to match actual code flow
    - Updated all console output examples to match reality
  - **Overall Impact**:
    - ✅ Documentation now 100% accurate to v4.0 implementation
    - ✅ All code examples match actual codebase
    - ✅ Developers can trust documentation as authoritative reference
    - ✅ Clear explanation of stats architecture prevents data corruption

- **Updated Docker documentation with nginx logs information**
  - **DOCKER-QUICKSTART.md**:
    - Added "Nginx Logs (Optional)" subsection in Persistent Data section
    - Documented how to persist nginx access and error logs
    - Added viewing commands (`tail -f logs/access.log`)
    - Updated all docker-compose.yml examples (Reverse Proxy, Absolute Paths)
    - Explained use cases: troubleshooting, monitoring, security auditing, performance analysis
  - **docker/README.md**:
    - Added nginx logs section to Persistent Storage
    - Updated both Docker CLI examples (build and published image)
  - **docker/docker-compose.yml**:
    - Added commented-out logs volume mount for easy enablement
    - Updated both production and developer build sections
  - **Log Location**: `/var/log/nginx` inside container
  - **Log Files**: `access.log` (HTTP requests), `error.log` (nginx errors/warnings)
  - **Impact**:
    - ✅ Users can now easily persist nginx logs for troubleshooting
    - ✅ All documentation consistently shows logs volume mount
    - ✅ Simple uncomment to enable in docker-compose.yml

---

# 2025-10-23

## **v4.0.0** - Per-Tournament History Architecture

### Backwards Compatibility with Pre-v4.0 Exports

**Old tournament exports are supported with limited functionality.**

- **What works**: Pre-v4.0 tournament exports can be imported successfully
- **Import process**: Shows a warning modal explaining limitations before import
- **Full functionality**: All tournament features work normally (players, matches, bracket, placements, results)
- **Limitation**: Undo history is not available for imported old tournaments (new matches will generate history normally)
- **User experience**: Import confirmation modal clearly indicates whether full undo functionality is available
- **Going forward**: All v4.0+ exports include full undo functionality and version validation

### New: Per-Tournament History Storage
- **Implemented isolated transaction history for each tournament**
  - **Previous behavior**: Global `tournamentHistory` accumulated transactions from all tournaments, causing exports to bloat to 9.9MB with contaminated multi-tournament data
  - **New behavior**: Each tournament stores its own history in `tournament_${id}_history` localStorage key
  - **Benefits**:
    - ✅ Clean exports (~110KB vs 9.9MB for 32-player tournaments)
    - ✅ No cross-contamination between tournaments
    - ✅ History exports with tournament data
    - ✅ History deleted when tournament deleted
    - ✅ Complete data portability with undo functionality preserved
  - **Implementation**:
    - Updated `saveTransaction()`, `getTournamentHistory()`, `clearTournamentHistory()` in `clean-match-progression.js`
    - Updated undo/redo functions in `bracket-rendering.js`
    - Updated smart pruning in `analytics.js`
    - Updated reset tournament in `tournament-management.js`
  - **Files updated**:
    - `js/clean-match-progression.js` - Per-tournament history functions
    - `js/bracket-rendering.js` - Undo/redo system references
    - `js/analytics.js` - Smart pruning
    - `js/tournament-management.js` - Reset tournament, import/export

### New: Export Format v4.0
- **Versioned export format with validation**
  - **New field**: `exportVersion: "4.0"` in all exports
  - **Includes**: Per-tournament history, playerList snapshot, complete tournament data
  - **Structure**: Tournament data + isolated history + saved players
  - **File naming**: `{TournamentName}_{YYYY-MM-DD}.json`
  - **Console logging**: Shows transaction count on export
  - **Pristine history exports**: Complete, unpruned transaction history
    - **Previous behavior (pre-v4.0)**: Exports pruned redundant transactions (START_MATCH, STOP_MATCH after completion, kept only last ASSIGN_LANE/ASSIGN_REFEREE)
    - **New behavior**: All transactions preserved exactly as they occurred
    - **Why the change**: Per-tournament isolation makes history small enough (~110KB for 32-player tournament) that pruning is unnecessary
    - **Benefit**: Complete audit trail of all tournament actions, better debugging and verification
  - **Impact**:
    - ✅ Version validation on import
    - ✅ Complete tournament portability
    - ✅ History restoration works seamlessly
    - ✅ Undo functionality preserved after import
    - ✅ Full transaction audit trail without pruning

### New: Import Confirmation and Validation System
- **Import confirmation modal for all imports**
  - **Consistent UX**: Both "Shared Tournaments" and "Import Tournament" show confirmation modal before importing
  - **Version detection**: Automatically detects old format (pre-v4.0) vs new format exports
  - **Old format warning**: Yellow warning box explains undo history will not be available
  - **New format confirmation**: Green indicators show full functionality including undo history
  - **User choice**: Users can cancel or proceed with import after seeing details
  - **History restoration**: v4.0+ imports restore per-tournament history to correct key
  - **PlayerList restoration**: Imports restore saved players snapshot
  - **ID preservation**: Tournament IDs preserved on import for idempotent imports
  - **Impact**:
    - ✅ All imports show confirmation before proceeding
    - ✅ Clear warnings for old format limitations
    - ✅ Complete history restoration for v4.0+ exports
    - ✅ Backwards compatible with pre-v4.0 exports

### Enhanced: Developer Console Storage Display
- **Granular localStorage usage breakdown**
  - **Current Tournament** detailed view:
    - Tournament data breakdown: players array, matches array, bracket structure, placements, metadata (with sizes and counts)
    - Transaction history details: total count, average size, oldest/newest timestamps
    - Total size and percentage of overall storage
    - Smart pruning suggestions for optimization
  - **Other Tournaments** summary:
    - Shows tournament names (not IDs) for easy identification
    - Combined data + history size per tournament
    - Total storage for all inactive tournaments
  - **Global Storage** section:
    - Human-readable names (Tournament registry, Config, Saved Players)
    - Individual sizes for each global key
  - **Cleanup Opportunities**:
    - Detects orphaned keys (old global `tournamentHistory`)
    - Shows size and suggests safe deletion
  - **High Storage Warning**:
    - Alert when usage >= 80%
    - Suggests deleting older tournaments with export reminder
  - **Impact**:
    - ✅ Complete visibility into storage usage patterns
    - ✅ Easy identification of storage optimization opportunities
    - ✅ Tournament names instead of IDs for better UX
    - ✅ Actionable insights for storage management

### Documentation
- **New comprehensive import/export documentation**
  - Created `Docs/IMPORT_EXPORT.md` with complete specification
  - Covers export format v4.0 schema, localStorage architecture, validation, error handling
  - Includes testing procedures and troubleshooting guide
  - Documents transaction history system and undo integration

### Fixed: Font and Logo Loading Paths
- **Corrected asset paths to work in both file:// and web server contexts**
  - **Previous behavior**: Asset paths were simple relative (`url('fonts/...')`, `img.src = 'logo.png'`)
  - **Issue**:
    - CSS in `/css/styles.css` using `url('fonts/...')` looked for fonts in `/css/fonts/` instead of `/fonts/`
    - This caused fonts to fail loading on web servers (Docker, demo site)
    - Original paths worked for `file://` protocol but failed for `http://` protocol
    - **Font files in repository were HTML documents**, not actual TrueType fonts (GitHub download page HTML instead of raw files)
  - **Solution**: Use context-appropriate relative paths and replace font files
    - **CSS fonts**: Changed to `url('../fonts/...')` - goes up one directory from `/css/` to root, then into `/fonts/`
    - **JavaScript logo**: Kept simple relative path `logo.png` - resolved relative to HTML page location (works for both protocols)
    - **Font files**: Replaced HTML documents with actual DroidSerif TrueType font files
  - **Impact**:
    - ✅ Droid Serif fonts load correctly in Docker/web deployments
    - ✅ Club logo loads correctly in Docker/web deployments
    - ✅ Fonts and logo work when opening `tournament.html` directly (file:// protocol)
    - ✅ Preserves core "double-click to open" feature
    - ✅ Page load time significantly improved (no timeout delays)
    - ✅ No more "OTS parsing error" for fonts
- **Files updated**:
  - `css/styles.css` - Updated `@font-face` to use `../fonts/` relative paths
  - `js/main.js` - Logo loading uses simple relative path (context-aware)
  - `fonts/DroidSerif-Regular.ttf` - Replaced HTML file with actual TrueType font
  - `fonts/DroidSerif-Bold.ttf` - Replaced HTML file with actual TrueType font

### Fixed: Analytics Modal Crash
- **Fixed property name mismatch in referee conflict display**
  - **Issue**: `showQuickOverview()` tried to access `refereeValidation.conflicts.length`, but `validateRefereeAssignments()` returns `details` property, not `conflicts`
  - **Error**: `Cannot read properties of undefined (reading 'length')` when opening Analytics modal
  - **Fix**: Changed line 540 to use `refereeValidation.details.length` to match actual return value
  - **Impact**: Analytics modal now opens without errors and correctly displays referee conflict count
- **Files updated**:
  - `js/analytics.js` - Fixed property reference in Quick Overview section

### Fixed: Referee Conflict Detection Logic
- **Corrected referee conflict validation to only detect actual error states**
  - **Previous behavior**: Flagged players refereeing a match AND being a participant in another READY match as a tournament error state
  - **Issue**: This is not a tournament error state, causing false positives in Developer Console
  - **Actual error state**: One person assigned as referee to multiple active matches (regardless of state: PENDING, READY, or LIVE)
  - **Solution**: Changed validation to check for duplicate referee assignments across all active matches
    - Removed check for "referee is player in same match" (allowed, not an error)
    - Added check for "referee assigned to multiple active matches" (PENDING, READY, or LIVE)
    - Completed matches are excluded (referees can be assigned to new matches after completing previous ones)
  - **Impact**:
    - ✅ Developer Console "Referee conflicts" now only shows genuine errors
    - ✅ No false positives for normal tournament operations
    - ✅ Player refereeing own match no longer flagged (allowed by design)
    - ✅ Player busy refereeing while their match is READY handled as operational constraint (not error)
    - ✅ Prevents assigning same referee to multiple active matches (error state)
    - ✅ Cleaner, more accurate analytics for tournament organizers
- **Files updated**:
  - `js/analytics.js` - Updated referee conflict detection logic

### Fixed: Referee Conflict False Positives for Completed Matches
- **Fixed validation incorrectly checking completed matches for referee conflicts**
  - **Issue**: Validation was checking `match.state !== 'completed'` but matches don't have a `.state` property
  - **Root cause**: Match state is calculated dynamically by `getMatchState()` function, not stored on match object
  - **Symptom**: Completed matches with assigned referees were flagged as conflicts because `undefined !== 'completed'` evaluated to `true`
  - **Solution**: Changed validation to check `!match.completed` instead of `match.state !== 'completed'`
  - **Impact**:
    - ✅ Completed matches no longer flagged as having referee conflicts
    - ✅ Validation correctly ignores matches with `referee: null` or `referee: undefined`
    - ✅ Validation correctly ignores matches with referee set to empty string (dropdown "None" selection)
    - ✅ Only active matches (PENDING, READY, LIVE) are checked for duplicate referee assignments
    - ✅ Works correctly for both new v4.0 tournaments and imported pre-v4.0 tournaments
- **Files updated**:
  - `js/analytics.js` - Updated `validateRefereeAssignments()` function (lines 1757-1772)

### Enhanced: Match Elimination Displays Final Placement
- **Winner confirmation modal now shows eliminated player's final placement rank**
  - **Previous behavior**: Modal showed "• Player is eliminated" for all backside bracket eliminations
  - **New behavior**: Modal shows "• Player is placed 13th-16th" (or appropriate rank) when eliminated from backside bracket
  - **How it works**: Uses hardcoded elimination rank mappings based on which backside match the player loses
  - **Examples**:
    - BS-3-4 loser (32-player): "• Chris is placed 13th-16th"
    - BS-7-1 loser (32-player): "• Player is placed 4th"
    - BS-FINAL loser: "• Player is placed 3rd"
    - GRAND-FINAL loser: "• Player is placed 2nd"
  - **Dependency**: Relies on `tournament.bracketSize` being correct (set at bracket creation, persisted everywhere)
  - **Fallback**: Shows "is eliminated" if rank lookup fails for any reason
  - **Impact**:
    - ✅ Players immediately know their final placement when eliminated
    - ✅ More informative and satisfying UX
    - ✅ Uses existing hardcoded rank mappings (same as Results Table calculations)
    - ✅ Works for all bracket sizes (8, 16, 32 players)
- **Files updated**:
  - `js/clean-match-progression.js` - Updated winner confirmation progression display (lines 1509-1523)

### Enhanced: Backside Final Placement Consistency
- **BS-FINAL loser now gets 3rd place set immediately, consistent with all other backside matches**
  - **Previous behavior**: BS-FINAL loser didn't get placement set until Grand Final completed
  - **Inconsistency**: All other backside matches (BS-1-1 through BS-7-1) set placement immediately, but BS-FINAL didn't
  - **User impact**: 3rd place didn't appear in Results Table until tournament was fully complete
  - **Solution**: Added BS-FINAL completion hook to set 3rd place immediately when match completes
  - **Safety**: Placement is cleared and recalculated when Grand Final completes (atomic recalculation preserved)
  - **Undo safety**: All placements cleared and recalculated on any match undo (existing safeguard)
  - **Impact**:
    - ✅ Consistent UX across all backside bracket matches
    - ✅ 3rd place shows in Results Table immediately after BS-FINAL completes
    - ✅ Confirmation modal shows "• Player is placed 3rd" instead of "• Player is eliminated"
    - ✅ Makes placement system more predictable and understandable
    - ✅ No risk - existing Grand Final and undo operations already clear/recalculate all placements
- **Files updated**:
  - `js/clean-match-progression.js` - Added BS-FINAL completion hook (lines 332-353)
  - `js/bracket-rendering.js` - Added 3rd place restoration after undo operations (lines 2306-2314)

### Enhanced: Security Headers
- **Docker image now includes comprehensive security headers by default**
  - **Previous behavior**: No security headers configured in nginx, PHP version exposed in X-Powered-By header
  - **New behavior**: Six security headers configured for defense-in-depth protection, server version information hidden
  - **Headers included**:
    - **X-Frame-Options: SAMEORIGIN** - Prevents clickjacking attacks
    - **X-Content-Type-Options: nosniff** - Prevents MIME-type sniffing attacks
    - **Referrer-Policy: strict-origin-when-cross-origin** - Controls referrer information leakage
    - **Permissions-Policy** - Disables unused browser features (geolocation, microphone, camera, payment, USB, magnetometer, gyroscope, accelerometer)
    - **Content-Security-Policy (CSP)** - Prevents loading external scripts/styles/resources
    - **Server tokens hidden** - `server_tokens off` hides nginx version from attackers
    - **PHP version hidden** - `expose_php = Off` removes X-Powered-By header that reveals PHP version
  - **CSP 'unsafe-inline' requirement**:
    - CSP includes `'unsafe-inline'` for script-src and style-src
    - Required due to 68+ inline event handlers (`onclick`, `onchange`) and 217+ inline styles in tournament.html
    - This is an architectural requirement, not an oversight
    - CSP still prevents loading external scripts/styles/resources (primary XSS vector)
    - NewTon has no user-generated content or XSS attack vectors
    - Security rating: A grade on securityheaders.com (with informational warning about 'unsafe-inline')
  - **HSTS not included**:
    - Strict-Transport-Security should be added at reverse proxy level (user choice)
    - Allows flexibility for HTTP-only local deployments
    - Self-hosters can enable HSTS in their reverse proxy (NPM, Caddy, Traefik)
  - **Impact**:
    - ✅ Defense-in-depth security by default
    - ✅ Protects against clickjacking, MIME-sniffing, external resource loading
    - ✅ Hides nginx and PHP version information from attackers
    - ✅ A-grade security headers rating
    - ✅ No breaking changes - headers are additive only
    - ✅ Maintains compatibility with both HTTP and HTTPS deployments
- **Files updated**:
  - `docker/nginx.conf` - Added security headers configuration
  - `docker/php.ini` - Added `expose_php = Off` to hide PHP version

### Enhanced: Docker Image Mount Structure
- **Moved logo and payment images to dedicated images/ folder**
  - **Previous behavior**: Individual file mounts (`./logo.png:/var/www/html/logo.png`, `./payment.png:/var/www/html/payment.png`)
  - **Previous bug**: If files don't exist, Docker creates directories instead, causing 10-second browser hang when loading
  - **New behavior**: Single folder mount (`./images:/var/www/html/images:ro`)
  - **Benefits**:
    - ✅ No directory creation bug - missing images result in fast 404 instead of hang
    - ✅ Default images included (logo.jpg and payment.png with GitHub QR code)
    - ✅ Cleaner Docker Compose configuration (single mount instead of two)
    - ✅ Easy customization - drop files in images/ folder
    - ✅ Files go in correct location when copied
  - **Default images**:
    - `images/logo.jpg` - Default club logo
    - `images/payment.png` - GitHub project QR code
  - **Impact**:
    - ✅ Professional out-of-box experience with working defaults
    - ✅ No confusing slow loads or missing images for new users
    - ✅ Simple customization workflow
- **Files updated**:
  - `tournament.html` - Updated favicon and payment image paths to use images/ prefix
  - `js/main.js` - Updated logo loading logic to use images/ prefix
  - `docker/docker-compose.yml` - Changed from individual file mounts to folder mount
  - `docker/docker-compose-demo.yml` - Changed from individual file mounts to folder mount
  - `DOCKER-QUICKSTART.md` - Updated documentation for images/ folder structure
  - `docker/README.md` - Updated documentation and examples
  - `js/dynamic-help-system.js` - Updated help text for Config and Registration pages

### Fixed: Tournament Deletion Not Freeing Storage
- **Critical bug fix: Tournament deletion now properly removes per-tournament history**
  - **Bug**: Deleting tournaments only removed them from registry, leaving orphaned history keys in localStorage
  - **Impact**: Deleting a 32-player tournament left 4.3 MB orphaned data, defeating v4.0.0's storage isolation goals
  - **Root cause**: `confirmDeleteTournament()` didn't clean up `tournament_${id}_history` keys
  - **Fix**: Added `localStorage.removeItem(tournament_${tournamentId}_history)` to delete function
  - **Testing**: Verified with Developer Console that history keys are now properly removed
  - **Critical for v4.0.0**: Without this fix, "deletions actually delete" promise would be false
- **Files updated**:
  - `js/tournament-management.js` - Added per-tournament history cleanup to confirmDeleteTournament() (lines 812-814)

### Enhanced: Developer Console Orphaned Data Detection
- **Added detection and cleanup guidance for orphaned tournament data in localStorage**
  - **Purpose**: Identify and clean up leftover data from tournaments deleted with old buggy delete function (before above fix)
  - **What it detects**:
    - Orphaned `tournament_${id}_history` keys not in registry
    - Orphaned `tournament_${id}` keys not in registry
    - Old `tournamentHistory` key (pre-v4.0 global history)
  - **How it works**:
    - Compares all tournament-related localStorage keys against the tournament registry
    - Shows orphaned data in "⚠️ Orphaned Data (Not in Registry)" section
    - Provides exact `localStorage.removeItem()` commands for manual deletion
    - Labels each orphan type (Orphaned history, Orphaned tournament data, Old global history)
  - **Design decisions**:
    - Detection only, no delete buttons - surgical manual cleanup prevents accidental data loss
    - Shows sizes (MB/KB) to help users understand storage impact
    - Clear messaging: "To delete a tournament properly, use the Setup page"
    - Doesn't flag random localStorage keys, only tournament naming patterns
  - **User experience**:
    - F12 → Click version number → Click "localStorage Usage"
    - See orphaned data (if any) with exact removal commands
    - Copy/paste commands into console for surgical cleanup
    - Refresh view to verify deletion and see freed storage
  - **Testing**: Verified detection accuracy with orphaned history from old bug, false-positive resistance with random localStorage keys
- **Files updated**:
  - `js/analytics.js` - Added orphaned data detection logic (lines 1134-1167) and display section (lines 1339-1383)

### Enhanced: Developer Console Transaction History Display Order
- **Reversed display order to show newest transactions first**
  - **Previous behavior**: Transaction history displayed chronologically (#1 at top, newest at bottom)
  - **New behavior**: Reversed display order with newest transactions at top, oldest at bottom
  - **Transaction numbering**: Original indices preserved (#1 is still the first/oldest transaction, displayed at bottom)
  - **Rationale**: Most recent transactions are most important for diagnostics and verification
  - **Impact**: No scrolling required to see latest tournament actions, better UX for monitoring live tournaments
- **Files updated**:
  - `js/analytics.js` - Reversed display order in `showTransactionHistory()` function (lines 759-765)

### Fixed: Results Table Empty Value Display Consistency
- **Fixed inconsistent display of empty achievement values in Results table**
  - **Bug**: Short Legs column showed blank for empty arrays instead of `—` dash
  - **Previous behavior**: High Outs showed `—` for empty, Short Legs showed blank
  - **New behavior**: Both Short Legs and High Outs show `—` when empty
  - **Design rationale**:
    - Short Legs and High Outs display **actual values** (leg numbers, checkout amounts) → use `—` for empty
    - 180s, Tons, Legs Won, Legs Lost display **counts** → use `0` for empty
  - **Impact**: Consistent visual presentation, clearer distinction between "no data" and "zero count"
- **Files updated**:
  - `js/results-config.js` - Added length check for shortLegs and highOuts arrays (lines 547-548)

### Fixed: Developer Console Toggle Read-Only Not Updating Bracket Display
- **Fixed bracket display not updating when toggling read-only status**
  - **Bug**: Toggling read-only OFF on imported tournaments updated data but not visual display
  - **Previous behavior**:
    - Imported completed tournaments showed checkmarks (✓) on completed matches
    - After toggling read-only OFF, checkmarks remained - clicking did nothing
    - Required manual "Re-render Bracket" command to update icons
  - **New behavior**: Toggling read-only automatically re-renders bracket with correct icons
  - **Impact**:
    - Imported tournaments now behave identically to non-imported tournaments
    - Completed matches show undo icon (↻) immediately after toggling read-only OFF
    - Clicking matches works correctly - triggers undo confirmation dialog
    - Seamless UX for the "backdoor" feature (fixing errors in completed tournaments)
  - **Use case**: Toggle read-only is designed as a backdoor to fix errors in completed tournaments - now works as intended
- **Files updated**:
  - `js/analytics.js` - Added `renderBracket()` call to `commandToggleReadOnly()` function (lines 2569-2572)

### Fixed: Developer Console Transaction History Filter Renumbering
- **Fixed transaction numbers being renumbered when filtering history**
  - **Bug**: Filtering transaction history renumbered results instead of preserving original transaction numbers
  - **Previous behavior**:
    - Full history: #8, #7, #6, #5, #4, #3, #2, #1
    - Filter for FS-1-2 (3 results): #3, #2, #1 (renumbered based on filtered count)
  - **New behavior**: Original transaction numbers preserved when filtering
    - Full history: #8, #7, #6, #5, #4, #3, #2, #1
    - Filter for FS-1-2 (3 results): #7, #6, #5 (original numbers preserved)
  - **Impact**:
    - Transaction numbers serve as true identifiers regardless of filtering
    - Easy to cross-reference with console logs and debugging output
    - Maintains chronological context when viewing filtered results
    - Fulfills the intention of transaction log as audit trail
- **Files updated**:
  - `js/analytics.js` - Added `originalNumber` property preservation in `showTransactionHistory()` function (lines 713-718, 766-771)

---

## **v3.0.5-beta** - Independent Tournament List Controls

### Enhanced: Tournament List UX
- **Independent "Show All" toggle buttons for Shared and Local tournament sections**
  - **Previous behavior**: Single external "Show All" button controlled only local tournaments, shared tournaments showed all items (no pagination)
  - **New behavior**: Each section (Shared Tournaments and My Tournaments) has its own inline toggle button
  - **Benefits**:
    - **Consistent UX**: Both sections limited to 5 items by default with independent expansion
    - **Better scrolling**: When server has 20+ shared tournaments, users don't have to scroll excessively to reach local tournaments
    - **Visual clarity**: Toggle buttons inline with section headers make control more intuitive
    - **Always visible header**: "My Tournaments" header now always appears when local tournaments exist (previously only showed when shared tournaments were present)
  - **Implementation**:
    - Two new state variables: `showingAllSharedTournaments` and `showingAllLocalTournaments`
    - Two new toggle functions: `toggleSharedTournamentView()` and `toggleLocalTournamentView()`
    - Shared tournaments now limited to 5 by default (previously showed all)
    - Toggle buttons only appear when section has >5 items
    - Removed standalone `toggleTournamentsBtn` from tournament.html
  - **Files updated**:
    - `js/tournament-management.js` - Independent state management and toggle logic
    - `tournament.html` - Removed external toggle button (now inline with headers)
- **User impact**: Cleaner, more consistent UI that scales better with large numbers of shared tournaments

---

# 2025-10-22

## **v3.0.4** - Environment Variables & Port 2020 ("Double 20" 🎯)

### New: Environment Variable Configuration
- **Flexible Docker configuration via environment variables**
  - **`NEWTON_API_ENABLED`** (default: `true`) - Enable/disable REST API endpoints
    - Set to `false` to disable upload/download/delete endpoints (returns HTTP 403)
    - Use case: Demo sites, security-conscious deployments, read-only mode
  - **`NEWTON_DEMO_MODE`** (default: `false`) - Show demo privacy banner
    - Displays banner: "Demo Site. Everything you do is stored locally in your browser. Your data never leaves your device."
    - Use case: Public demo sites (like https://darts.skrodahl.net) that clarify privacy
  - **`NEWTON_GITHUB_URL`** (default: `https://github.com/skrodahl/NewTon`) - Customize GitHub link
    - Allows forks to link to their own repository in demo banner
  - **`NEWTON_HOST_PORT`** (default: `8080`) - Configurable host port mapping
    - Avoid port conflicts with other services on host machine
- **Implementation**:
  - `api/api-check.php` - Shared API access check (DRY approach)
  - `api/*.php` - All API endpoints include api-check.php
  - `tournament.html` - PHP config block + JavaScript demo banner injection
  - `docker-compose.yml` - Environment variable definitions with inline documentation
- **Backward compatible**: Environment variables have sensible defaults, existing deployments work unchanged

### Changed: Internal Port 2020 ("Double 20" 🎯)
- **nginx now listens on port 2020 internally** instead of port 80
  - **Thematic choice**: Port 2020 = "Double 20" (highest scoring segment in darts!)
  - **Practical benefit**: Avoids port conflicts when using reverse proxies (Nginx Proxy Manager, Caddy, Traefik)
  - **Docker networking**: When multiple containers share a network (e.g., with NPM), port 80 is commonly used by many services. Port 2020 reduces conflicts.
  - **Host port unchanged**: Default `8080:2020` mapping means users still access via `http://localhost:8080`
  - **Reverse proxy users**: Point to `newton:2020` (not `newton:80`)
- **Files updated**:
  - `docker/nginx.conf` - `listen 2020;` with "Double 20" comment
  - `docker/Dockerfile` - `EXPOSE 2020` with darts reference
  - `docker-compose.yml` - Port mapping `8080:2020` with emoji and explanation
  - `DOCKER-QUICKSTART.md` - Comprehensive updates with "Double 20" references throughout
- **User impact**:
  - **NPM/reverse proxy users**: No more port 80 conflicts in Docker networks
  - **Direct users**: No change (still access via localhost:8080)
  - **Fun detail**: Port choice has thematic significance for darts tournament software!

### Enhanced: DOCKER-QUICKSTART.md
- **New "Configuration" section** documenting all environment variables with use cases
- **Reverse Proxy Setup guide** for NPM/Caddy users (explains port 2020)
- **Demo Site Setup example** showing how to replicate darts.skrodahl.net
- **Updated Security Notice** - Added `NEWTON_API_ENABLED=false` option, removed broken Docs/SECURITY.md reference
- **All port references updated** from `:80` to `:2020` throughout
- **Multiple "Double 20" callouts** explaining the thematic port choice

### Technical Notes
- **Demo banner preserves static HTML**: PHP block only executes when served via nginx/PHP-FPM, gracefully ignored when opening tournament.html directly (file://). Core feature preserved: double-click tournament.html still works!
- **API check is DRY**: Shared `api/api-check.php` prevents code duplication across all API endpoints
- **Independent control**: Environment variables work independently (can enable demo mode with API enabled, or disable API without demo mode, etc.)

---

## **v3.0.3** - REST API Duplicate Prevention

### Enhanced: Tournament Upload Duplicate Prevention
- **Prevent silent overwrites when uploading tournaments to server**
  - **Previous behavior**: Uploading a tournament with the same filename would silently overwrite the existing file without warning
  - **New behavior**: Upload API returns 409 Conflict if file already exists, prompting user to confirm overwrite
  - **User flow**:
    1. Upload tournament that already exists → Confirmation dialog appears
    2. User confirms → Retry with `?overwrite=true` parameter
    3. User cancels → Upload aborted, existing file preserved
  - **API changes**:
    - `POST /api/upload-tournament.php` - Now checks `file_exists()` before writing
    - Query parameter `?overwrite=true` - Explicitly allows overwriting existing files
    - Response includes `overwritten: true` when file was replaced
  - **Safety improvement**: Prevents accidental data loss from uploading older tournament versions over newer ones
- **Implementation**: api/upload-tournament.php (duplicate check), tournament-management.js:195-264 (confirmation dialog and retry logic)
- **User impact**: Users are now warned before overwriting existing tournaments on the server, preventing accidental data loss while still allowing intentional updates.

---

# 2025-10-21

## **v3.0.2** - Docker Deployment, Extended Transaction History & UI Refinements

### New: Docker Deployment Support
- **Full Docker containerization for self-hosting**
  - **nginx + PHP-FPM Alpine** - Lightweight (~60MB) container with full PHP REST API support
  - **Multi-architecture builds** - Supports linux/amd64 (Intel/AMD) and linux/arm64 (Apple Silicon, Raspberry Pi)
  - **Persistent tournament storage** - Volume mount for `/tournaments` directory preserves uploaded tournament data
  - **10MB upload limit** - Supports large tournament files (nginx `client_max_body_size` and PHP `upload_max_filesize` set to 10MB)
  - **UTF-8 encoding** - Proper handling of international characters (Swedish/Norwegian å, ä, ö, etc.)
  - **GitHub Container Registry** - Automated builds on Git tags publish to `ghcr.io/skrodahl/newton`
  - **GitHub Actions workflow** - Automatic multi-arch builds and publishing on version tags
- **Docker configuration files:**
  - `docker/Dockerfile` - nginx + PHP-FPM Alpine-based image
  - `docker/docker-compose.yml` - Easy deployment with persistent storage
  - `docker/nginx.conf` - Web server configuration for static files and PHP API
  - `docker/php.ini` - PHP configuration for upload limits and UTF-8 encoding
  - `docker/README.md` - Quick start guide
  - `.dockerignore` - Excludes unnecessary files from image
  - `.github/workflows/docker-build.yml` - Automated build pipeline
- **Documentation:**
  - `DOCKER-QUICKSTART.md` - Step-by-step quick start guide (under 2 minutes)
  - `Docs/DOCKER.md` - Comprehensive Docker deployment guide (hosting options, reverse proxy setup, troubleshooting)
  - `README.md` - Added Docker deployment section with quick start
- **Implementation:** docker/Dockerfile, docker/docker-compose.yml, docker/nginx.conf, docker/php.ini, .github/workflows/docker-build.yml
- **User impact:** Self-hosters can easily deploy NewTon Tournament Manager on their own servers using Docker. Perfect for clubs wanting to host their own instance with full tournament sharing capabilities via PHP REST API. Supports large tournament files up to 10MB and properly handles international characters.

### Enhanced: Referee Conflict Detection - Self-Refereeing Support
- **Players can now referee their own matches without triggering conflict warnings**
  - **Previous behavior**: If a player was assigned as referee to their own match (e.g., "Chris vs Albin, Ref: Chris"), the conflict detection would block starting the match
  - **New behavior**: Conflict detection now excludes the current match being checked, allowing self-refereeing while still preventing double-booking
  - **Logic**: Added single-line check `if (m.id === match.id) return;` to skip the current match during referee conflict validation
  - **Use case**: Common in smaller tournaments where players referee their own matches
  - **Safety maintained**: Still prevents players from playing in one match while refereeing a different match
- **Implementation**: bracket-rendering.js:2550-2551 (skip current match in conflict detection loop)
- **User impact**: More flexible referee assignment without losing safety checks. Tournament operators can assign players as referees to their own matches, which is blocked appropriately when they're refereeing other matches.

### Enhanced: UI Spacing Consistency
- **Fixed spacing inconsistency between Setup and Registration page headers**
  - **Issue**: Setup page had tight spacing between "Tournament Setup" title and "Tournament Name" field due to negative margin
  - **Fix**: Changed `.setup-page-header .form-group` margin-top from `-6px` to `16px` to match Registration page spacing
- **Implementation**: styles.css:2228
- **User impact**: Consistent visual rhythm across all page headers

### Enhanced: Payment QR Code Size Adjustment
- **Reduced payment.png display height for better visual balance**
  - **Previous height**: 200px
  - **New height**: 175px
  - **Location**: Registration page header, right column
- **Implementation**: styles.css:2567
- **User impact**: More balanced layout on Registration page, particularly on lower resolution displays

### Enhanced: Transaction History Limit
- **Increased MAX_HISTORY_ENTRIES from 500 to 1000**
  - **Purpose**: Provide even more headroom for extensive 32-player tournaments with heavy operational activity
  - **Previous limit**: 500 transactions
  - **New limit**: 1000 transactions
  - **Impact**: Doubles the transaction history capacity, allowing for extremely complex tournaments with extensive lane/referee reassignments and match operations
  - **Storage impact**: Minimal - with optimized transaction storage (v3.0.1), even 1000 transactions remain well within localStorage limits
  - **Use case**: Supports tournaments with 100+ completed matches plus full operational transaction history
- **Implementation**: clean-match-progression.js:1804 (MAX_HISTORY_ENTRIES constant)
- **User impact**: Tournament operators can run even the most complex tournaments without any concern about hitting transaction limits. The combination of optimized storage (v3.0.1) and doubled capacity (v3.0.2) provides exceptional operational headroom.

### Fixed: Developer Console Transaction Display
- **Updated all hardcoded 500 transaction references to 1000 in analytics.js**
  - **Issue**: Developer Console displayed incorrect transaction percentages and capacity (showed /500 instead of /1000)
  - **Fix**: Updated 11 locations in analytics.js where transaction capacity was hardcoded to 500
  - **Affected displays**: Quick Overview, Transaction Breakdown, Transaction Log Management, validation thresholds
  - **Validation thresholds updated**: Healthy (<500), Moderate (500-799), High (800+) to maintain 50%/80% warning levels
- **Implementation**: analytics.js:216, 218, 501, 528, 570, 571, 601, 1817, 1819-1820, 2348, 2362
- **User impact**: Developer Console now correctly shows transaction capacity as X/1000 with accurate percentages. Status indicators (✅⚠️🔴) trigger at correct thresholds relative to 1000-transaction limit.

---

## **v3.0.1** - Critical Storage Optimization & UI Enhancements

### Enhanced: Match Controls - Referee Conflict Prevention
- **Visual warnings prevent starting matches when players are already refereeing**
  - **Problem**: Tournament operators could accidentally start a READY match where one player is currently assigned as referee to another match, creating scheduling conflicts at the venue
  - **Visual indicators**:
    - Player name shows warning: "⚠️ Bob (Referee)" in player vs player display
    - Match card background changes to signal that the match can't be started
    - Start Match button becomes disabled (grayed out, not clickable)
  - **Scope**: Player counts as "refereeing" if assigned as referee to ANY match with status READY or LIVE
  - **Dynamic updates**: Warning appears immediately when referee assigned, disappears when unassigned
  - **Prevents venue conflicts**: Impossible to start match where player is simultaneously playing and refereeing
- **Implementation**: bracket-rendering.js:2544-2578 (conflict detection in createMatchCard), styles.css:1442-1461 (warning colors and disabled button styling)
- **User impact**: Critical safety feature prevents double-booking players as both participants and referees. Tournament operators see clear visual warnings before attempting to start conflicting matches.

### Enhanced: Developer Console - Toggle Read-Only Command
- **New "Toggle Read-Only" command in Developer Console**
  - **Purpose**: Provides escape hatch to convert completed (read-only) tournaments back to read-write mode for editing
  - **Location**: Added to COMMANDS section in Developer Console sidebar
  - **Functionality**: Toggles `tournament.readOnly` flag and saves tournament
  - **Visual feedback**: Shows 🔒 (read-only) or 🔓 (read-write) icon with status details
  - **Status information**: Lists what's enabled/disabled in each mode:
    - Read-only: Undo disabled, match modifications disabled, data protected
    - Read-write: Undo enabled, match modifications enabled, fully editable
- **Implementation**: analytics.js:2294-2326 (commandToggleReadOnly function), tournament.html:677-679 (command link)
- **User impact**: Tournament organizers can modify completed tournaments without resetting them entirely. Useful for post-tournament corrections or adjustments.

### Fixed: Transaction Storage Optimization (Critical)
- **Resolved localStorage overflow issue in large tournaments**
  - **Problem**: 32-player tournaments with ~19 players hit 10 MB localStorage limit by BS-R6 (~35 matches), forcing manual transaction deletion to complete tournament
  - **Root cause**: `COMPLETE_MATCH` transactions stored entire tournament state (~50-100 KB each) in `beforeState` object that was never used by undo system
  - **Solution**: Removed unused `beforeState` data from all transaction types
- **Storage reduction achieved:**
  - **COMPLETE_MATCH transactions**: Removed `beforeState.matches` (entire matches array) and `beforeState.tournament` (entire tournament object) - **~98% reduction** (~50 KB → ~0.6 KB per transaction)
  - **ASSIGN_LANE transactions**: Removed `beforeState.lane`, kept `afterState.lane` for future analytics - **~50% reduction**
  - **ASSIGN_REFEREE transactions**: Removed `beforeState.referee`, kept `afterState.referee` (required for referee suggestions feature) - **~50% reduction**
- **Impact on typical 32-player tournament:**
  - Before: ~35 completed matches × 50 KB = **~1.75 MB** (just COMPLETE_MATCH transactions)
  - After: ~35 completed matches × 0.6 KB = **~21 KB** (just COMPLETE_MATCH transactions)
  - **Total reduction**: ~8-10 MB → ~300-500 KB (97% smaller)
  - **Result**: Can safely complete 100+ matches without hitting localStorage limits
- **Backward compatibility**: Existing tournaments with old transaction format continue to work (extra data simply ignored)
- **Undo system unchanged**: Still uses hardcoded `MATCH_PROGRESSION` lookup tables and manual state resetting (never used `beforeState` data)
- **Referee suggestions unchanged**: Still uses `afterState.referee` from transaction history to build timeline
- **Implementation**: clean-match-progression.js:287-300,1380-1388, bracket-rendering.js:1543-1551,1608-1616
- **User impact**: Tournament operators can complete full 32-player tournaments without localStorage errors or manual workarounds. Critical fix for tournament night reliability.

## **v3.0.1-beta** - Help System & Payment Information UI Enhancements

### Enhanced: Help System with Info Icons
- **Replaced floating help button with context-aware info icons**
  - **Info icons (ℹ️)**: Added next to page headers on Setup, Registration, and Config pages
  - **Direct click access**: Click icon to open contextual help modal for current page
  - **Clean design**: Removes positioning conflicts from floating help button
  - **Hover effect**: Icons scale and change color on hover for clear interactivity
  - **Orange accent color**: Icons use `#ff6b35` to match application theme
  - **F1 shortcut**: Keyboard shortcut remains available for all pages
  - **Tournament page unchanged**: Watermark "Press F1 for help" remains on bracket page
- **Implementation**: tournament.html:50,110,273 (info icons), css/styles.css:2997-3013 (icon styles), js/dynamic-help-system.js:437-450 (click handlers)
- **User impact**: Cleaner, more intuitive help access without UI clutter. Users can immediately identify where to get help for each page.

### Enhanced: Registration Page with Payment Information Display
- **New payment QR code display in registration header**
  - **Two-column grid layout**: Registration header now uses CSS Grid with left (forms) and right (payment info) columns
  - **QR code placement**: Displays `payment.png` in right column at 200px height with border and shadow
  - **Graceful fallback**: Image hidden automatically if `payment.png` file doesn't exist (no broken image icon)
  - **Player count repositioned**: Moved from below buttons to bottom-right of header area
  - **Dynamic bottom alignment**: Player count uses `margin-top: auto` to stay at bottom regardless of image presence
  - **Responsive layout**: Grid with `1fr auto` columns adapts to content size
- **Visual improvements**
  - **Structured form layout**: Registration controls organized in left column with consistent spacing
  - **Professional appearance**: QR code styled with subtle border and shadow matching application design
  - **Maintained functionality**: All existing registration features work identically
- **Implementation**: tournament.html:108-132 (restructured header), css/styles.css:2473-2564 (grid layout and column styles)
- **User impact**: Tournament organizers can display payment information directly on registration page. Players see payment QR code immediately when registering. Clean integration without disrupting existing workflow.

# 2025-10-16

## **v3.0.0** - Match Controls Real-Time Updates, Referee Suggestions & Developer Console Enhancements

### Enhanced: Developer Console - Lane Usage Details & Preventive Conflict Detection
- **Complete Lane Usage detail view implementation with real-time monitoring and preventive warnings**
  - **Lane Usage detail view**: Clicking "Lane Usage" statistic now shows comprehensive lane breakdown
    - Color-coded status box: Green (no conflicts), Yellow (READY conflicts), Red (LIVE conflicts)
    - Available lanes list (non-excluded lanes with total count)
    - Excluded lanes list (or "None")
    - Active lanes list (unique lanes currently in use with accurate count)
    - Live matches section: Shows lane number, match ID, and player names for each live match
    - Ready matches section: Shows pre-assigned lanes for upcoming matches
    - Auto-refresh every 2 seconds for real-time lane monitoring during tournament
    - "Back to Overview" navigation link
  - **Enhanced lane conflict detection**: `validateLaneAssignments()` now detects both LIVE and READY match conflicts
    - **LIVE conflicts (critical)**: Multiple live matches assigned to same lane - immediate issue requiring action
    - **READY conflicts (warning)**: Multiple ready matches pre-assigned to same lane - future issue, preventive warning
    - Returns separate conflict arrays (`conflicts` and `readyConflicts`) for each type
    - Properly handles 3+ matches on same lane (not just pairs)
    - Catches extreme corner case: duplicate lane assignments from undoing matches
  - **Conflict warning displays**:
    - LIVE conflicts shown in red warning box with critical alert and "both LIVE" notation
    - READY conflicts shown in yellow warning box with preventive message
    - Helpful guidance: "These matches will conflict when started. Reassign lanes before starting matches."
    - Both conflict types displayed in Lane Usage detail view with clear visual separation
  - **Updated Quick Overview**:
    - Separate display lines for "Lane conflicts (LIVE)" and "Lane conflicts (READY)"
    - Three-level color coding: Green (healthy, no issues), Yellow (READY warnings), Red (LIVE critical)
    - Overall status box reflects most severe issue detected
  - **Left pane statistics updates**:
    - Lane Usage indicator shows 🔴 for LIVE conflicts, ⚠️ for READY conflicts, ✅ for all clear
    - Accurate in-use count based on unique active lanes (fixed counting bug)
  - **Implementation**: lane-management.js:81-133 (enhanced validation), analytics.js:807-981 (detail view), analytics.js:233-240 (statistics), analytics.js:397-434 (quick overview), tournament.html:610 (click handler)
  - **User impact**: Tournament organizers can now catch duplicate lane assignments BEFORE matches start, preventing scheduling conflicts and improving tournament flow. Real-time monitoring shows exactly which lanes are free and which matches are using them.

### Enhanced: Developer Console - Quick Overview Menu Link & Tournament Timing Statistics
- **New "Quick Overview" menu link added to Statistics section for easy navigation**
  - **Direct navigation**: "Quick Overview" now appears as first item in Statistics section of left pane
  - **Always visible**: Provides permanent way to return to overview from any detailed view
  - **Real-time tournament duration**: Shows "Duration: HH:MM:SS" (e.g., "Duration: 43:26")
  - **Dynamic updates**: Duration refreshes every 2 seconds during active tournaments
  - **Format variations**: "Duration: Not started" (setup), "Duration: 43:26" (active), "Duration: 3:45:12" (completed)
  - **Complements existing navigation**: Works alongside "← Back to Overview" links in detail views
- **New tournament timing statistics added to Quick Overview**
  - **Tournament duration**: Total elapsed time from first match start
    - **Dynamic during active tournament**: Updates every 2 seconds, calculated from first START_MATCH to current time (e.g., "43:26")
    - **Static after completion**: Fixed historical value from first START_MATCH to last COMPLETE_MATCH (e.g., "3:45:12")
    - **Setup state**: Shows "Not started" when no matches have begun
    - **Undo-aware**: Clock resumes if Grand Final is undone, reverting tournament from completed to active state
  - **Average match time**: Mean duration of all completed matches (e.g., "14:23")
  - **Shortest match**: Fastest completed match with match ID (e.g., "8:15 (FS-1-2)")
  - **Longest match**: Slowest completed match with match ID (e.g., "32:45 (BS-FINAL)")
  - **Time format**: HH:MM:SS with hours omitted when zero (e.g., "14:23" instead of "0:14:23")
  - **Seconds precision**: Shows exact match durations for accurate tournament pacing analysis
  - **Separator line**: Timing statistics appear below health checks with visual separator for clear section distinction
  - **Edge case handling**: Shows "N/A" when no completed matches exist, "0:XX" for test matches under 1 minute
  - **Read-only tournament handling**: Timing statistics section hidden for read-only tournaments (completed tournaments loaded from Recent Tournaments)
    - **Rationale**: Read-only tournaments are historical imports where timing data cannot be trusted or verified
    - **Active completed tournaments**: Timing stats remain visible for tournaments completed during current session
    - **Clean presentation**: Entire timing section (including separator) omitted for read-only imports
- **Implementation**: tournament.html:598-602 (menu link), analytics.js:251-257 (duration subtitle), analytics.js:404-497 (timing calculations), analytics.js:542-555 (conditional timing display), Docs/ANALYTICS.md:80-94 (documentation)
- **User impact**: Tournament duration visible at a glance in left menu, updating in real-time. Easy one-click access to Quick Overview from any view. Tournament organizers can now monitor tournament duration continuously, track match pacing, and identify fastest/slowest matches for scheduling insights. Read-only tournaments keep Quick Overview focused on relevant validation data.

### Enhanced: Developer Console - Match Progression View Redesign
- **Complete Match Progression view redesign with side-by-side layout and improved readability**
  - **Two-column side-by-side layout**: Frontside and Backside brackets displayed in equal-width columns for maximum overview capability
    - CSS Grid layout: `repeat(2, minmax(0, 1fr))` ensures perfectly balanced columns
    - Columns maintain position even when one side has no matches (stays in lane)
    - Grand Final displayed below in special green-highlighted section
    - Single-column mode when filtering by specific side
  - **Improved match card layout**: Two-line design for optimal readability
    - **Line 1**: Status (left-aligned, 80px width) and Match ID (center-aligned, 18px font)
    - **Line 2**: `FROM: sources → TO: destinations` (center-aligned with labeled sections)
    - Clear "FROM:" and "TO:" labels eliminate ambiguity in progression flow
    - Bold arrow separator (→) between sections
  - **Enhanced state visualization**: Each match reference includes state icon
    - Example: "FROM: FS-1-3 ✅, FS-1-4 ✅" shows source match states at a glance
    - Example: "TO: ⏸️ FS-3-1, ⏸️ BS-2-6" shows destination match states
    - Round 1 matches: "FROM: R1" (italicized, gray)
    - Champion: "TO: 🏆", Eliminated: "TO: ❌"
  - **Progression Code view**: New debugging view showing raw MATCH_PROGRESSION lookup table
    - Access via "Progression Code" button in filter bar
    - Monospace text display of hardcoded progression rules
    - Traditional format: "Winner → FS-2-1 (player1)" for verifying bracket logic
    - "← Back to Match Progression" button at top for quick return to rich view
  - **Collapsible Console Output**: Console footer now collapsible and hidden by default
    - Click "Console Output" header to toggle visibility (▶ collapsed, ▼ expanded)
    - Main content area expands to fill available space when console collapsed
    - Console limited to 400px max-height when expanded
    - Flexible layout automatically adjusts content area size
  - **Implementation**: analytics.js:1067-1453 (progression views), analytics.js:2559-2575 (toggle function), tournament.html:675-700 (flexible layout)
  - **User impact**: Tournament operators get complete bracket overview at a glance with clear progression flow. Developers can verify hardcoded logic with Progression Code view. More screen space available with collapsible console.

### Enhanced: Developer Console - Reset All Config Command
- **New "Reset All Config" developer command for recovering from config corruption**
  - **Command location**: Developer Console Commands section (bottom of list, red text for visual distinction)
  - **Typed confirmation required**: Must type "RESET" in confirmation box to proceed
  - **Before/after comparison**: Shows detailed comparison for all config sections before reset
    - Point values (all 11 point types)
    - Match configuration (5 round types)
    - UI settings (4 settings)
    - Branding (club name)
    - Lane configuration (max lanes, excluded lanes)
    - Server settings
  - **Tournament data preserved**: Only resets config, never touches tournament data (matches, players, brackets, history)
  - **Auto-refresh**: Page reloads after 2 seconds to apply changes
  - **Visual warnings**: Red warning box with "⚠️ Warning: Destructive Action" alert
  - **Success feedback**: Summary of changes with automatic page refresh countdown
  - **Hidden from casual users**: Only available in Developer Console (not on Config page) to prevent accidental use
  - **Use cases**: Config corruption recovery, misconfiguration fixes, fresh start scenarios
  - **Implementation**: analytics.js:1656-1822 (command functions), tournament.html:645-647 (UI integration), Docs/ANALYTICS.md:248-285 (documentation)
  - **User impact**: Tournament operators can recover from config corruption or misconfiguration without losing tournament data. Provides safe recovery tool for extreme situations.

### Enhanced: Config Page - Help System Documentation Update
- **Developer Console comprehensive documentation added to Config page dynamic help**
  - **Updated help for "Enable Developer Analytics" setting**: Now includes detailed feature list
  - **Real-time statistics**: Lists all 5 statistics tracked (Transaction Health, Match States, Player Counts, Lane Usage, localStorage Usage)
  - **Lane Usage monitoring**: Specific mention of LIVE/READY conflict detection capabilities
  - **Validation checks**: Lists all 6 validation checks (lane conflicts, referee conflicts, match state integrity, transaction limits, player IDs, progression integrity)
  - **Developer commands**: Lists all commands (Re-render Bracket, Recalculate Rankings, Refresh Dropdowns, Validate Everything, Manage Transaction Log, Reset All Config)
  - **Transaction management**: Notes Smart Pruning capability for storage optimization
  - **Auto-refresh behavior**: Mentions 2-second auto-refresh for real-time monitoring
  - **Implementation**: dynamic-help-system.js:321-335 (help content update)
  - **User impact**: Users can discover Developer Console features and capabilities directly from Config page help, improving discoverability

### Enhanced: Match Controls - In-Modal Auto-Open Setting Toggle
- **"Automatically open Match Controls" checkbox added to Match Controls modal for convenient access**
  - **Location**: Bottom-right corner of Match Controls modal, aligned with Statistics/Close buttons
  - **Styling**: Matches button font (14px, font-weight 500) for visual consistency
  - **Bidirectional sync**: Changes sync in real-time between Match Controls modal and Config page
    - Toggle in Match Controls → Config page checkbox updates immediately
    - Toggle in Config page → Match Controls checkbox updates immediately
    - No page refresh required for sync
  - **Persistent storage**: Both checkboxes read/write from same `config.ui.autoOpenMatchControls` setting
  - **Auto-save**: Calls `saveGlobalConfig()` immediately on toggle
  - **Layout**: Buttons centered, checkbox positioned absolutely on right side
  - **Implementation**: tournament.html:907-918 (UI), bracket-rendering.js:3422-3446 (Match Controls sync), results-config.js:304-308 (Config page sync)
  - **User impact**: Users can toggle auto-open behavior directly from Match Controls without navigating to Config page. Setting is immediately available and stays in sync across both locations.

### Enhanced: Tournament Page - Navigation Buttons for Quick Page Access
- **Five navigation buttons added to Tournament page for easy access to other pages**
  - **Button layout**: Positioned in top-left corner, stacked vertically
    - **Top row**: Statistics, Match Controls (green)
    - **Middle row**: Setup, Registration, Config (stacked vertically below)
  - **Button styling**: 150px width, consistent dark background with white text
    - Left-aligned icons (≡, ➹, ⬅) with 20px fixed width
    - Centered button text with balanced padding (32px left, 12px right)
    - Statistics button opens Statistics modal
    - Match Controls button opens Match Controls modal (green highlight)
    - Setup/Registration/Config buttons navigate to respective pages using `showPage()`
  - **Visual consistency**: All buttons use `.nav-btn` class with unified icon/text layout
    - Icons positioned absolutely at left: 12px
    - Text centered in remaining button space
  - **Rationale**: Direct navigation from Tournament page improves workflow - operators can quickly access Setup, Registration, Config, or view Statistics without returning to main navigation
  - **Implementation**: tournament.html:203-222 (button structure), css/styles.css:504-525 (navigation button styling), dynamic-help-system.js:174-177 (help text updates)
  - **User impact**: Tournament operators can navigate between all major pages directly from the bracket view, reducing clicks and improving tournament management efficiency.

### Enhanced: Navigation Menu - Sliding Underline Indicator
- **Animated sliding underline added to main navigation menu for polished visual feedback**
  - **Sliding underline animation**: 1px black line smoothly transitions between active menu items
    - 0.3s CSS transition with easing for responsive, elegant movement
    - Pixel-perfect alignment under each menu item (Setup, Registration, Tournament, Config)
    - Uses CSS `:has()` selector for pure CSS implementation (no JavaScript required)
  - **Consistent menu styling**: Removed color and font-weight changes from active menu items
    - All menu items stay same color (`#444444` default, `#222222` on hover)
    - All menu items maintain `font-weight: 400` (no bold text causing layout shift)
    - Active state indicated solely by animated underline
  - **Removed button focus outlines**: Eliminated blue focus outline from all button types
    - Removed outline from `.btn`, `.zoom-btn`, and `.nav-btn` buttons
    - Cleaner interface without persistent blue glow after clicking
    - Buttons return to neutral state immediately after interaction
  - **Rationale**: Sliding underline provides modern, sophisticated navigation feedback without causing layout shifts or visual noise. Removing focus outlines eliminates visual artifacts while maintaining clean, professional appearance.
  - **Implementation**: css/styles.css:108-147 (sliding underline), css/styles.css:164-167 (active state), css/styles.css:271-276 (focus outline removal)
  - **User impact**: Navigation feels more polished and modern with smooth animated feedback. Menu bar no longer shifts position when changing pages. Buttons throughout the application have cleaner, more professional appearance without blue focus artifacts.

### Enhanced: Real-Time Clocks for Fullscreen Tournament Operation
- **Two clocks added for tournament operators running in fullscreen mode**
  - **Match Controls clock**: Displayed in top-right corner of Match Controls modal title bar
    - Format: 24-hour HH:MM (e.g., "23:05")
    - Updates every 10 seconds automatically
    - Visual styling: 1px gray border (#ccc), 8px vertical padding, 16px horizontal padding, 6px border radius
    - Monospace font (SF Mono, Consolas, Monaco, Menlo) for stable width
    - Normal font weight to distinguish from bold title text
    - Right-aligned using flexbox layout
  - **Status Panel clock**: Displayed in tournament watermark header (bottom-right box)
    - Format: 24-hour HH:MM
    - Updates every 10 seconds automatically
    - Right-aligned in Status Panel header next to tournament name
  - **Rationale**: When running tournaments in Chrome fullscreen, OS clock is hidden and operators frequently ask for time
  - **Update mechanism**: `setInterval()` functions ensure clocks stay current without manual refresh
  - **Implementation**: bracket-rendering.js:3059-3079 (Match Controls clock display), bracket-rendering.js:4064-4075 (Match Controls update function), tournament-management.js:1202-1225 (Status Panel clock), tournament-management.js:1269-1281 (Status Panel update function)
  - **User impact**: Tournament operators can see current time at a glance without exiting fullscreen mode. Match Controls clock is most prominent since operators spend majority of time in that modal.

### Fixed: Config Page - Removed Auto-Save for Point Values and Match Configuration
- **Point System and Match Configuration now require explicit Save button click**
  - **Removed auto-save behavior**: Deleted `setupConfigAutoSave()` function and all event listeners
  - **Consistent save workflow**: All config sections now require deliberate Save button click
  - **Added "Save Point Values" button**: Green primary button in Point Values section
  - **Added "Save Match Configuration" button**: Green primary button in Match Configuration section
  - **Removed "(autosave)" labels**: Cleaned up section headers for clarity
  - **Success alerts**: Both save functions show "✓ saved successfully!" confirmation alerts
  - **Rationale**: Auto-save was too aggressive for deliberate configuration changes - users expect explicit save control
  - **Implementation**: main.js:274-353 (removed auto-save function), results-config.js:351-392 (new save functions), tournament.html:452-508 (UI updates)
  - **User impact**: Configuration changes now require explicit user action before being persisted. More predictable behavior - users have control over when changes are saved, preventing accidental configuration modifications.

### Fixed: Setup Page - Scrolling in Recent Tournaments and Match Results
- **Scrollable areas now work properly with overflow-y: auto**
  - **Root cause**: `.scrollable-column-content` was missing `overflow-y: auto` CSS property
  - **Fixed sections**: Both "Recent Tournaments" and "Match Results" boxes now scroll when content exceeds height
  - **Implementation**: css/styles.css:2242 (added overflow-y property)
  - **User impact**: Long tournament lists and match results are now accessible through scrolling instead of being cut off

### Enhanced: Developer Console - Transaction Log Management & Storage Monitoring
- **Complete transaction pruning system with smart algorithm and localStorage monitoring**
  - **"Manage Transaction Log" command**: Opens dedicated management view showing current status, storage usage, and pruning options
  - **Smart Pruning algorithm**: Removes redundant transactions for completed matches only
    - Removes old ASSIGN_LANE transactions (keeps final assignment)
    - Removes old ASSIGN_REFEREE transactions (keeps final assignment)
    - Removes ALL START_MATCH and STOP_MATCH transactions (redundant after completion)
    - Preserves ALL COMPLETE_MATCH transactions (never pruned)
    - Preserves ALL transactions for active/pending matches
  - **Preview mode**: Shows detailed analysis before execution (what will be removed/kept, storage impact)
  - **Post-execution feedback**: Comprehensive statistics on transactions removed, storage freed
  - **Safety**: Undo system unaffected (uses separate state snapshots, not transaction history)
  - **Performance**: Typically removes 40-60% of transactions in active tournaments
  - **localStorage Usage statistic**: New fifth statistic in Developer Console
    - Shows total usage vs 10 MB browser limit
    - Color-coded indicators (green < 50%, amber 50-80%, red > 80%)
    - Detail view with breakdown by localStorage key (sorted by size)
    - Helps identify when transaction pruning is needed
  - **Transaction History improvements**: Reverse chronological sorting (#1 = latest transaction)
  - **Transaction History filtering system**: Comprehensive search and filter capabilities
    - **Layout optimization**: Developer Console left pane reduced from 30% to fixed 240px width for better space utilization
    - **Vertical sidebar layout**: Filter panel positioned as right sidebar next to transaction list
    - **Three-filter system** with AND logic:
      - Transaction Type dropdown (All Types, COMPLETE_MATCH, ASSIGN_REFEREE, ASSIGN_LANE, START_MATCH, STOP_MATCH)
      - Match ID text input (searches matchId field and description)
      - Search String text input (searches player names and any text in description)
    - **Enhanced transaction descriptions**: All transactions now include both player names and IDs for better debugging
      - COMPLETE_MATCH: "FS-1-3: Liam (ID: 123) defeats Peter (ID: 456)"
      - ASSIGN_REFEREE: "FS-1-1: Referee assigned to Chris (ID: 1760441429772)"
    - **Filter state preservation**: Selected filters maintained in UI when applied
    - **Results counter**: Shows "X of Y total" when filtered, "Y total" when unfiltered
    - **Clean UI**: Professional layout with proper spacing and visual hierarchy
  - **Storage calculation fixes**:
    - Updated browser limit from 5 MB to 10 MB (modern browsers: Chrome 114+, Firefox, Safari, Edge)
    - Fixed UTF-16 encoding calculation (2 bytes/char instead of 8 bytes/char)
    - Accurate storage estimates across all views
  - **Developer Console UI unification**: Consistent professional styling across all views
    - **Unified command feedback**: All commands (Re-render Bracket, Recalculate Rankings, Refresh All Dropdowns, Validate Everything) use consistent styled feedback boxes
    - **Status-based color coding**: Green for success/healthy, yellow for moderate/warnings, red for errors/critical
    - **Flat design system**: All views use border-radius: 0 for sharp corners matching application design
    - **Statistic detail views**: Quick Overview, Transaction Breakdown, Match State, Player Details, and localStorage Usage all use consistent status boxes
    - **Back to Overview navigation**: All detail views include "← Back to Overview" link for easy navigation
    - **Multi-column player list**: Player Details view uses CSS Grid (4+ columns) to efficiently display player names and IDs
    - **Visual hierarchy**: Clear status headings (16px, bold, colored) with proper spacing and typography throughout
  - **Modal width optimization**: Reduced from 90% to 75% screen width for more comfortable viewing on larger displays
  - **Implementation**: analytics.js (Transaction Log Management, localStorage Usage view, Transaction History filtering, UI styling updates), tournament.html (layout optimization, modal width), bracket-rendering.js (ASSIGN_REFEREE descriptions), clean-match-progression.js (COMPLETE_MATCH descriptions)
  - **User impact**: Operators can monitor and manage storage usage, prevent hitting browser limits, maintain tournament performance, and quickly debug tournament issues with powerful filtering capabilities. The unified UI provides a professional, consistent experience across all Developer Console views.

### Fixed: Match Controls Auto-Refresh on Lane Changes
- **Match Controls now updates immediately when lane assignments change on LIVE matches**
  - Previously, changing a lane on a LIVE match required closing and reopening Match Controls to see the updated sort order
  - LIVE matches now automatically re-sort by lane number when lanes are changed
  - **Root cause**: Modal refresh check was looking for `display === 'flex'` but Match Controls uses `display: 'block'`
  - **Solution**: Updated display check to accept both 'flex' and 'block' in `updateMatchLane()` function
  - **Side benefit**: Also fixed lane/referee resources not being immediately "released" when stopping LIVE matches
  - **Implementation**: Modified modal display check in clean-match-progression.js:1412-1414
  - **User impact**: Real-time sorting and resource availability updates during tournament operations

### Enhanced: Match Controls - Two-Column Layout & Modal Optimization
- **Complete redesign with Frontside/Backside visual separation for better tournament flow visibility**
  - **Two-column layout**: Match cards split into Frontside (left) and Backside (right) columns for both LIVE and Ready to Start sections
  - **Visual separation**: 2px vertical separator line between columns for clear bracket side distinction
  - **Modal sizing**: Maximized vertical space with 98vh max-height and 1% top margin for optimal screen utilization on all display sizes
    - **Height optimization**: Changed from 80vh to 98vh max-height, gaining ~18% more vertical space for match display
    - **Positioning**: Reduced top margin from 5% to 1%, allowing modal to sit higher and extend nearly full viewport height
    - **Lower resolution support**: Critical improvement for laptops and smaller monitors (1366x768, 1280x720) where vertical space is premium
    - **Active tournament benefit**: Can display more LIVE and READY matches simultaneously without scrolling during busy tournament periods
  - **Referee sidebar optimization**: Fixed 350px width (user-adjustable via CSS) instead of flex-based, providing more space for match cards
  - **Tournament completion centering**: Celebration card constrained to 800px max-width and horizontally centered
  - **Setup mode input**: "Add Player" field constrained to 400px max-width for better proportions
  - **Dynamic width adjustment**: Modal width intelligently adjusts based on tournament status
    - **Setup mode**: 75% width (optimized for centered player registration content)
    - **Active mode**: 90% width (maximum space for two-column Frontside/Backside match layout)
    - **Completed mode**: 75% width (optimized for centered celebration display)
  - **At-a-glance visibility**: Operators can instantly see both bracket sides simultaneously without scrolling
  - **Smart grouping**: Grand Final appears in Frontside column, BS-FINAL in Backside column
  - **Independent sorting**: Each column maintains proper round progression order (FS-R1, FS-R2... and BS-R1, BS-R2...)
  - **Implementation**: bracket-rendering.js:3150-3285 (two-column rendering logic), bracket-rendering.js:3578-3584 (celebration width), bracket-rendering.js:3082-3086 (width reset), tournament.html:774 (modal dimensions), styles.css:1816-1822 (modal height optimization), styles.css:1772 (referee sidebar width), styles.css:1391 (celebration centering)
  - **User impact**: Tournament operators gain significantly improved spatial awareness of tournament state, can manage both bracket sides efficiently, and make faster operational decisions during active tournaments. Celebration view is optimally sized for comfortable viewing.

### Fixed: Undo System - Complete Match State Restoration & Resource Clearing
- **Match undo now properly clears ALL assignments and returns match to completely clean state**
  - **Critical bug fixed**: Lane and referee assignments were persisting after undoing completed matches
  - **Root cause**: Two separate data stores (transaction history AND match objects) were not being synchronized during undo
  - **Two-part fix implemented**:
    1. **Transaction history cleanup**: Remove ALL transaction types for undone match (COMPLETE_MATCH, ASSIGN_LANE, ASSIGN_REFEREE, START_MATCH, STOP_MATCH)
    2. **Match object clearing**: Reset `match.lane = null` and `match.referee = null` during rollback
  - **Resource conflict prevention**: Without proper clearing, lanes and referees appeared "in use" but weren't shown in transaction history
  - **Clean slate principle**: Undoing a match now returns it to pristine READY state as if nothing was ever done to it
  - **Why critical**: Prevents resource conflicts, eliminates blocking of available lanes/referees, maintains data consistency between history and state
  - **Implementation**: bracket-rendering.js:2185-2194 (transaction removal), bracket-rendering.js:2273-2274 (match object clearing)
  - **Documentation**: Comprehensive update to Docs/UNDO.md explaining transaction types, data synchronization, and clean state restoration
  - **User impact**: Tournament operators can now safely undo matches without worrying about orphaned resource assignments or availability conflicts. The undo system properly releases all resources for reassignment to other matches.

### Enhanced: Player List - Payment Status Indicator & Smart Sorting
- **"In Tournament" section now shows payment status and prioritizes unpaid players**
  - **Payment status indicator**: Players who have paid entrance fee show "(Paid)" label in green (13px font, subtle styling)
  - **Smart sorting**: Unpaid players appear first, paid players at bottom (both groups alphabetically sorted)
  - **Real-time sync**: Payment status and sort order update immediately when toggled in "Tournament Players" section
  - **Visual feedback**: Quick at-a-glance confirmation of who still needs to pay
  - **Implementation**: player-management.js:95-114 (sorting logic), player-management.js:107-114 (payment indicator), player-management.js:448 (sync on toggle)
  - **User impact**: Tournament organizers can instantly see which players haven't paid during registration/check-in, reducing confusion and missed payments

### Improved: Referee Suggestions Logic
- **Complete rewrite of referee suggestions system with timeline-based event tracking**
  - **Timeline approach**: Lists show history of events, not unique players (e.g., "Jack, Ken, Bob, Ken, Nick, Ken")
  - **Recent Winners**: Last 10 match wins (up from 7, configurable 5-20 in Config page)
  - **Recent Losers**: Last 10 match losses (up from 7, configurable 5-20 in Config page)
  - **Recent Assignments**: Last 10 referee assignments (up from 7, configurable 5-20 in Config page)
  - **Players can appear multiple times**: Same player can appear multiple times in same list (timeline of their activity)
  - **Players can be in all lists**: Player can simultaneously be in Winners, Losers, AND Assignments
  - **Smart filtering**: When assigned as referee, player's OLDER match results are removed from Winners/Losers (they've done their duty)
  - **Reappearance logic**: When player completes match AFTER referee duty, they reappear in Winners/Losers
  - **Unassignment handling**: Removing referee assignment immediately returns player to Winners/Losers suggestions
  - **Replacement filtering**: Replaced referees don't appear (if Ben is replaced by Bob, only Bob shows in Recent Assignments)
  - **Per-match deduplication**: Only most recent assignment per match shows (prevents same referee appearing 3x for same match)
  - **Auto-refresh on changes**: Match Controls updates immediately when referees are assigned/changed/removed
  - **Active assignment verification**: Only currently assigned referees are filtered from suggestions (not historical assignments)
  - **Configurable limit**: Added "Number of referee suggestions to show" field in Config > User Interface (5-20, default 10)
  - **Implementation**: bracket-rendering.js:2651-2900 (getRefereeSuggestions), clean-match-progression.js:1567-1631 (updateMatchReferee auto-refresh)
  - **User impact**: Tournament operators can quickly assign referees from accurate, real-time list of eligible players - dramatically speeds up tournament management

### Maintenance: CSS Cleanup & Flat Design Unification (Complete)
- **Removed 393 lines of CSS (12% reduction) and unified all UI components to flat design button system**

  **Phase 1 - Legacy Duplicates (229 lines removed)**
  - Deleted duplicate Registration page player card styles (superseded by flat design)
  - Deleted duplicate Setup/Config page layout styles (superseded by flat design)
  - Fixed nested CSS comment syntax issue breaking Chrome's CSS parser
  - Created backup: styles.css.backup-2025-10-14

  **Phase 2 - Mobile/Responsive CSS (145 lines removed)**
  - Removed all 7 @media query blocks (1200px, 768px, 640px, 600px, 480px breakpoints)
  - Application is desktop-only, mobile support not needed
  - Removed mobile layout adjustments, podium sizing, Command Center layouts

  **Phase 3 - Unused Utilities (19 lines removed)**
  - Created CSS coverage tracker tool to analyze live runtime usage
  - Achieved 93.6% CSS coverage (233 of 249 classes actively used)
  - Removed confirmed unused utilities: `.mb-20`, `.d-flex`, `.justify-between`, `.align-center`
  - Removed disabled bracket lines feature: `.bracket-line`, `#bracketLines`
  - Removed unused button style: `.generate-bracket-btn`

  **Phase 4 - Export Modal Button Conversion (HTML inline styles removed)**
  - Converted Export Confirmation Modal buttons to flat design classes
  - Removed inline styles from Cancel button (was `background: #6c757d`)
  - Removed inline styles from Export Results button (was `background: rgba(22, 101, 52, 0.9); color: white`)
  - Now uses standard `.btn` and `.btn-success` classes for consistency
  - **Last remaining old-style buttons eliminated** - all 13 modals now use unified flat design system

  **Final Results:**
  - **Before**: 3,278 lines | **After**: 2,885 lines | **Total Reduction**: 12%
  - All 4 pages tested and working perfectly
  - All 13 modals tested and working with consistent button styling
  - No visual changes or regressions
  - Remaining CSS is lean, functional, and 93.6% actively used
  - **All UI components now unified under flat design button system**
  - **User impact**: Cleaner, more maintainable codebase with consistent button UX across entire application

### Project Structure: Code Organization
- **Reorganized JavaScript and CSS files into dedicated folders for cleaner project structure**
  - Created `js/` folder and moved all 11 JavaScript files
  - Created `css/` folder and moved styles.css
  - Updated tournament.html with new file paths
  - Updated documentation
  - **Result**: tournament.html now clearly visible as main entry point in root folder
  - **User impact**: More intuitive project structure, easier navigation for developers and contributors

### Enhanced: Tournament Export - Automatic Transaction History Optimization
- **Completed tournament exports now automatically optimize transaction history to reduce localStorage usage on import**
  - **Smart Pruning on Export**: Uses same algorithm as Developer Console to remove redundant transactions
  - **Conditional Optimization**: Only prunes when `tournament.status === 'completed'`
  - **Mid-Tournament Exports**: Preserve complete transaction history for backup/debugging purposes
  - **Algorithm Applied**:
    - Keeps ALL COMPLETE_MATCH transactions (match results never removed)
    - Keeps only LAST ASSIGN_LANE transaction per completed match
    - Keeps only LAST ASSIGN_REFEREE transaction per completed match
    - Removes ALL START_MATCH transactions (redundant after completion)
    - Removes ALL STOP_MATCH transactions (redundant after completion)
  - **Storage Optimization**: Typically removes 40-60% of transactions in completed tournaments
  - **Primary Benefit**: When importing a completed tournament, pruned history consumes significantly less localStorage space
  - **Secondary Benefit**: Smaller JSON file size makes sharing and archiving more convenient
  - **Silent Operation**: No user notification, happens automatically during export
  - **Implementation**: tournament-management.js:100-192 (pruneTransactionHistory helper, modified exportTournament)
  - **User impact**: Importing completed tournaments uses less localStorage space (helps prevent hitting 10 MB browser limits). Mid-tournament exports retain full history for safety and debugging. No manual pruning action required.

---

## **v2.5.1** - Match Controls and UI Improvements

### Enhanced: LIVE Match Sorting
- **Lane-based sorting in Match Controls**
  - LIVE matches now sort by lane assignment (ascending) first, then by match ID
  - Matches with lanes appear before matches without lanes
  - Lane order: Lane 1, Lane 2, Lane 3... (numerical ascending)
  - Within same lane status, matches sorted alphabetically by ID
  - **Benefit**: Matches organized by physical venue layout for easier tournament management
  - **Use case**: Operators can quickly find "What's on Lane 3?" without scanning through match IDs
  - **Tournament-tested**: Real-world insight from live tournament operations

### Enhanced: Config Page Reset to Defaults
- **Reset buttons for Point Values and Match Configuration**
  - Added "Reset to Defaults" button at bottom of Point Values section
  - Added "Reset to Defaults" button at bottom of Match Configuration section
  - Both buttons follow same styling pattern as other config section buttons (Branding, Lane Management)
  - **Confirmation dialog**: Prompts user before resetting to prevent accidental changes
  - **Autosave**: Changes immediately saved to localStorage after reset
  - **Auto-update**: Results table automatically refreshes when point values are reset
  - **Default values**:
    - Point Values: Participation (5), 1st (15), 2nd (13), 3rd (10), 4th (9), 5th-6th (8), 7th-8th (7), High Out (1), Ton (0), Short Leg (1), 180 (1)
    - Match Config: Regular (Best of 3), Frontside SF (Best of 5), Backside SF (Best of 3), Backside Final (Best of 5), Grand Final (Best of 5)
  - **Implementation**: `resetPointValuesToDefaults()` and `resetMatchConfigToDefaults()` in results-config.js

### Enhanced: Subtle Shadows for Depth and Actionability
- **Added subtle depth to buttons and match cards for improved visual hierarchy**
  - **Buttons**: Default state `box-shadow: 0 1px 2px rgba(0, 0, 0, 0.08)`, hover state `box-shadow: 0 2px 3px rgba(0, 0, 0, 0.12)`
  - **Match cards**: Applied same subtle shadow `box-shadow: 0 1px 2px rgba(0, 0, 0, 0.08)` to "Ready to Start" cards in Match Controls
  - **Design philosophy**: Tiny accent that leads the eye in the right direction without overdoing it
  - **User benefit**: Interactive elements feel more tangible and "actionable" while maintaining clean, professional appearance
  - **Subconscious impact**: Users won't consciously notice the shadows, but will feel the interface is more polished and professional
  - **Implementation**:
    - Buttons: Applied to base `.btn` class in styles.css, automatically cascades to all button variants (.btn-success, .btn-danger, .btn-warning, .btn-small)
    - Match cards: Applied to `.cc-match-card` class (LIVE matches retain their distinctive orange glow)
  - **Affected elements**: All action buttons (Create Tournament, Add Player, Save, Reset, Load, Delete, etc.) and Ready to Start match cards
  - **Real-world tested**: Refinement based on live tournament operation observations over multiple weeks

### Fixed: Disabled Lane and Referee Assignment for Pending Matches
- **Prevents resource blocking by disabling lane/referee dropdowns for pending matches**
  - Lane and referee dropdowns now disabled when match state is 'pending' (both players not yet determined/TBD)
  - Visual feedback: Disabled dropdowns shown with reduced opacity (0.5) and not-allowed cursor
  - **Problem solved**: Operators were assigning lanes/referees to pending matches, blocking those resources from ready matches
  - **User benefit**: Lanes and referees only show as "assigned" when actually in use by ready or live matches
  - **Consistent pattern**: Aligns with disabled "Start Match" button behavior for pending matches
  - **Applies to**: Tournament bracket view only (Match Command Center doesn't show pending matches)
  - **Implementation**: Added `disabled` attribute and visual styling in bracket rendering (bracket-rendering.js:1075-1076, 1101-1102)
  - **Real-world tested**: Fix identified through live tournament operations where resource confusion occurred

### Enhanced: Read-Only Tournament Protection
- **Player statistics locked for loaded completed tournaments**
  - Clicking player names in Results Table, Match Controls, or Winner Confirmation dialogs does nothing when `tournament.readOnly === true`
  - Silent behavior - no alert, no modal, no feedback
  - Prevents accidental modification of historical tournament data
  - **Read-only condition**: Tournament must be both loaded from file AND completed
  - **Escape hatch**: Use "Reset Tournament" to clear read-only flag and make tournament editable
  - **Applies to**: All entry points to player statistics editing (Results Table rows, Match Controls player names, Winner Confirmation player names)
  - **Implementation**: Single check in `openStatsModal()` function (player-management.js:431-433)

### Fixed: Score Preservation and Dialog Flow in Winner Confirmation
- **Match score values now preserved when editing player statistics, with correct dialog restoration**
  - When clicking player names in Winner Confirmation dialog to edit stats, the leg scores (e.g., 3-1) are now saved and restored
  - Closing stats modal now properly returns to Winner Confirmation (not Match Controls)
  - Previously, scores would reset to default values (e.g., 2-0) when returning from stats modal
  - **Root cause**: Dialog stack restore function was re-initializing input fields; custom Escape handler conflicted with dialog stack Escape handling
  - **Solution**:
    - Changed dialog stack restore function to only show modal without reinitializing fields
    - Integrated stats modal properly with dialog stack instead of manual modal management
    - Enabled Escape key via dialog stack for winner confirmation, removed conflicting custom Escape handler
    - Save and restore input values after dialog stack restoration completes
  - **Implementation**: Enhanced `openStatsModalFromConfirmation()` and `showWinnerConfirmation()` in clean-match-progression.js:1570-1681, 2195-2229

### Enhanced: Tournament Bracket - Smooth Hover Zoom for LIVE Matches
- **LIVE matches now have smooth zoom transition on hover, matching other match states**
  - Removed pulsing animation from LIVE matches that conflicted with hover zoom
  - LIVE matches now smoothly zoom in when hovered (at zoom levels < 1.0) with consistent 0.3s transition
  - Previously, LIVE matches would "pop" to zoomed state without transition to avoid horrible pulsating zoom effect
  - **Visual distinction maintained**: LIVE matches still prominent with orange gradient background, thicker orange border (3px), and orange glow on hover
  - **Rationale**: Pulse animation was visually noisy and caused disorienting pulsating zoom when hovering over tiny match cards while zoomed out
  - **Implementation**: Removed `animation: pulse 2s infinite` from `.match-live` in css/styles.css:844
  - **User impact**: Consistent, smooth hover zoom behavior across all match states. Cleaner, more professional tournament bracket interaction.

### Enhanced: Tournament Bracket - READY Match Border Color
- **READY match border changed to yellow-gold for better visual distinction**
  - Border color changed from dark brown (`rgba(180, 83, 9, 0.9)`) to yellow-gold (`rgba(240, 196, 25, 0.9)`)
  - Yellow-gold border complements the yellow gradient interior and clearly distinguishes READY matches from LIVE matches (orange)
  - Maintains 90% opacity for subtle transparency consistent with original design
  - Hover state changes to fully opaque yellow-gold for clear interaction feedback
  - **Rationale**: With pulse animation removed from LIVE matches, the dark brown READY border was too similar to LIVE orange border, causing visual confusion
  - **Implementation**: Updated `.match-ready` border colors in css/styles.css:831-836
  - **User impact**: Clear visual hierarchy across match states - yellow for READY, orange for LIVE. More intuitive and cohesive bracket appearance.

### Enhanced: Tournament Bracket - Simplified Finals Match Styling
- **Removed all special styling for finals matches (BS-FINAL, GRAND-FINAL)**
  - Finals matches now use standard state-based styling like all other matches
  - PENDING: Gray, READY: Yellow, LIVE: Orange, COMPLETED: Green
  - No special borders, backgrounds, or visual treatments
  - **Rationale**: Physical placement in the tournament bracket is sufficient distinction. Special styling added complexity and created confusing edge cases (finals looking READY when LIVE, etc.)
  - **Previous behavior**: Finals had special cream/yellow gradients and custom borders that required `:not(.match-live)` selectors and explicit LIVE overrides to prevent visual confusion
  - **New behavior**: Completely consistent visual language across entire bracket - state colors mean the same thing everywhere
  - **Implementation**: Removed `.backside-final-match` and `.grand-final-match` styling rules from css/styles.css
  - **User impact**: Simpler, more predictable bracket appearance. Match state is immediately clear regardless of position. Finals are distinguished by their prominent position at the end of the bracket, not by visual decoration.

---

# 2025-10-12

## **v2.5.0** - Developer Console

### New Feature: Developer Console
- **Hidden developer tool for real-time tournament diagnostics**
  - **Purpose**: Monitor tournament health, run validation checks, and execute developer commands without browser console
  - **Access**: Enable in Config → User Interface → "Enable Developer Analytics", then click version number in Tournament Status Panel
  - **Design**: Large modal (90% screen) with three-pane layout:
    - Left pane (30%): Statistics and commands
    - Right pane content area (49%): Dynamic detail views
    - Right pane console footer (21%): Persistent console output (always visible)
  - **Auto-refresh**: Updates every 2 seconds (pauses while scrolling)
  - **Settings take effect immediately**: No browser refresh required when enabling/disabling Developer Analytics

#### Statistics (Real-time Monitoring)
- **Transaction Health**: Shows current usage (X/500) with health indicators (✅ <50%, ⚠️ 50-80%, 🔴 >80%)
- **Match State**: Breakdown of completed/live/ready/pending matches (click to view match IDs by state)
- **Player Count**: Paid vs unpaid players (click to view complete alphabetically sorted player list with IDs)
- **Lane Usage**: Current lane utilization with conflict detection (✅/⚠️), respects excluded lanes from Config

#### Validation Checks (6 Total)
1. **Lane Assignments**: Detects overlapping lane assignments for LIVE matches
2. **Referee Assignments**: Detects referees playing in matches they're refereeing
3. **Match State Integrity**: Verifies completed matches have winner/loser assigned
4. **Transaction Count**: Warns if approaching 500-entry limit (>80%)
5. **Player ID Integrity**: Detects orphaned player references in matches array (excludes walkover-*, bye-*, tbd-*, and placeholder IDs)
6. **Progression Integrity**: Verifies winners/losers are in correct downstream matches per MATCH_PROGRESSION rules

#### Developer Commands
- **Re-render Bracket**: Force visual refresh of bracket display (`renderBracket()`)
- **Recalculate Rankings**: Recompute all player placements (`calculateAllRankings()`)
- **Refresh All Dropdowns**: Update lane and referee dropdown options
- **Validate Everything**: Run all 6 validation checks, display results in right pane, log summary to console with pass/fail details
- **View Transaction History**: Display all transactions (latest first) with timestamp, type, and description
- **View Match Progression**: Display MATCH_PROGRESSION lookup tables for current bracket size

#### Console Output Footer (Persistent)
- **Always visible**: Console output footer shows last 50 entries at bottom 30% of right pane
- **Real-time updates**: Auto-refreshes every 2 seconds with new console.log entries
- **Auto-scroll**: Scrolls to bottom when new entries appear (pauses while user scrolling)
- **Smart capture**: Only intercepts console.log while Developer Console is open
- **Buffer**: Stores last 100 entries in memory, displays last 50 with timestamps
- **Independent scrolling**: Console footer scrolls separately from content area above
- **Benefits**: Monitor command execution in real-time without switching views or using browser developer tools

#### Technical Implementation
- **Files Added**:
  - `analytics.js` - Complete analytics system (console capture, validations, commands, UI management, persistent footer)
  - `Docs/ANALYTICS.md` - Comprehensive documentation (1000+ lines: features, use cases, troubleshooting, extension guide, future improvements)
- **Files Modified**:
  - `tournament.html` - Added analytics modal HTML (90% layout, three-pane design with persistent console footer) + script tag + developerMode checkbox in Config
  - `results-config.js` - Added `globalConfig.ui.developerMode` (default: false) with save/load persistence + watermark refresh on save for immediate effect
  - `tournament-management.js` - Made version number clickable when developerMode enabled, reads directly from localStorage to avoid script loading order issues
  - `styles.css` - Fixed pointer-events to allow version number clicks despite bracket viewport grab cursor, added analytics modal CSS overrides (90% height, 1% margin)
  - `dynamic-help-system.js` - Updated Config page help to document Developer Analytics feature
- **Global Functions**: All analytics functions accessible via window object for browser console debugging
- **Dialog Stack Integration**: Uses pushDialog/popDialog for proper z-index management and Escape key support
- **Smart Auto-refresh**: Updates left pane statistics + console footer every 2 seconds, only refreshes right pane Quick Overview (other views stay static for readability)
- **Three-pane Layout**: Left 30% (stats/commands), Right content 49% (detail views), Right footer 21% (persistent console)

#### Use Cases
- **Live monitoring**: Keep console open during tournament to watch transaction health, match state, and console activity in real-time
- **Issue diagnosis**: Run validation checks to identify lane conflicts, progression errors, or data corruption
- **Command execution**: Execute commands and monitor output in persistent console footer without switching views
- **Debug workflow**: Validation results and command execution logs appear immediately in always-visible console footer

---

# 2025-10-11

## **v2.5.0** - Undo System Fixes

### Undo System Improvements

#### Fixed History Pruning Bug (Bug B)
- **Increased MAX_HISTORY_ENTRIES from 50 to 500**
  - **The problem**: History limit of 50 caused premature pruning in 32-player tournaments
  - **Impact**: Early matches (FS-R1, FS-R2) would lose their COMPLETE_MATCH transactions after ~30-40 matches completed
  - **Result**: Matches without transactions in history appeared non-undoable, even when they should be undoable
  - **The solution**: Increased limit to 500 transactions
    - 32-player bracket generates ~169 total transactions in typical tournament (62 matches + ~107 operational changes)
    - 500 provides 196% buffer for tournaments with heavy lane/referee management
    - All matches now remain undoable throughout the entire tournament

#### Fixed Transaction Type Confusion Bug (Bug A)
- **Added transaction type filtering to downstream blocking checks**
  - **The problem**: Downstream blocking check used `history.find(t => t.matchId === targetMatchId)` which returned the newest transaction for a match, regardless of type
  - **Impact**: When completed matches had operational transactions (ASSIGN_LANE, ASSIGN_REFEREE) after COMPLETE_MATCH, the check would find the wrong transaction type
  - **Result**: Matches with completed MANUAL downstream matches incorrectly showed as undoable (observed in BS-R3 → BS-R4 scenarios)
  - **The solution**: Added `&& t.type === 'COMPLETE_MATCH'` filter to 4 locations in `isMatchUndoable()` and `getDetailedMatchState()` functions
    - Lines 1934, 1946 (isMatchUndoable winner/loser checks)
    - Lines 3695, 3707 (getDetailedMatchState winner/loser checks)
  - **Result**: Downstream blocking check now correctly finds COMPLETE_MATCH transactions only, ignoring operational transactions

### Documentation
- Updated `Docs/UNDO.md` with comprehensive undo system documentation
  - Added "Transaction History Storage and Limits" section explaining MAX_HISTORY_ENTRIES and pruning behavior
  - Added "Match Undoability Rules" section documenting complete logic for when matches can/cannot be undone
  - Expanded transaction structure to show all fields (type, description, beforeState)
  - Documented all 5 transaction types (COMPLETE_MATCH, START_MATCH, STOP_MATCH, ASSIGN_LANE, ASSIGN_REFEREE)
  - Documented Bug A (transaction type confusion) with example scenario and fix details
  - Included 4 detailed example scenarios covering common undoability cases

### Files Modified
- `clean-match-progression.js` - Increased MAX_HISTORY_ENTRIES from 50 to 500
- `bracket-rendering.js` - Added transaction type filtering to 4 locations (lines 1934, 1946, 3695, 3707)
- `Docs/UNDO.md` - Comprehensive documentation of undo system behavior and limits

# 2025-10-10

## **v2.5.0** - Distributed Seeding & Visual Consistency

### Tournament Seeding Improvements
- **Distributed BYE Placement**: Replaced sequential seeding with randomized BYE distribution
  - BYEs now randomly scattered across all FS-R1 matches instead of clustering at bottom
  - Each BYE randomly placed in either player1 or player2 slot within a match
  - **Critical fairness fix**: Old sequential system created guaranteed systematic advantage
    - **The problem**: Sequential seeding clustered BYEs at bottom of FS-R1 (matches 12-16 in 32-bracket)
    - **The chain reaction**: Bottom BYEs → bottom FS-R2 BYEs → 5 guaranteed BYE-vs-BYE matches in bottom BS-R1
    - **The unfair advantage**: Mirroring places FS-R2 top-half losers into BS-R2 bottom-half positions
    - **The collision**: FS-R2 top-half losers faced walkover-advanced opponents; bottom-half losers faced real winners
    - **Result**: Losing in top half of FS-R2 was predictably easier than losing in bottom half - every single tournament
  - **The solution**: Distributed seeding eliminates this structural bias
    - Example (22 players, 32-bracket): Old system guaranteed 5 BYE-vs-BYE matches in BS-R1
    - New distributed system typically produces 2-4 BYE-vs-BYE matches, randomly distributed
    - Walkover opponents appear unpredictably throughout BS-R2, not concentrated in specific regions
    - No correlation between FS-R2 bracket position and BS-R2 opponent difficulty
    - Fewer wasted walkover matches overall, more real competitive matches throughout tournament
  - Still guarantees no BYE-vs-BYE matches in FS-R1 (max 1 BYE per match)
  - Instant execution across all bracket sizes (8, 16, 32 players)
  - Mathematical guarantee: minimum players equals number of matches, ensuring algorithm always succeeds
  - Every bracket generation produces unique, random BYE distribution
  - Eliminates both the actual systematic advantage and the visual appearance of unfairness

### Visual Consistency
- Improved the design and colors of player cards in the Registration page
- Removed green borders from "In Tournament" cards (now use neutral gray like "Available Players")
- Removed checkmarks from Saved Players cards (section headers provide sufficient context)
- Normalized text styling across all player cards (consistent font weight and color)
- Maintained subtle visual distinction with light green background (#f0fdf4) for "In Tournament" cards
- Cleaner, more professional appearance while preserving functional separation

### Files Modified
- `clean-match-progression.js` - Replaced two-pass sequential seeding with distributed random BYE placement algorithm
- `player-management.js` - Removed checkmark rendering, updated card styling
- `styles.css` - Updated border colors and text styling for Saved Players cards
- `main.js` - Version bump to 2.5.0-beta

# 2025-10-09

## **v2.4.4** - Registration Page Workflow fixes
- The "x" for removing tournament players are now hidden for participants that have paid the entrance fee
- A confirmation/warning dialog is shown when removing paid players from the Saved Players column
- Updated the help section to reflect the Registration page redesign
- Added hints/instructions to the Registration page headers

## **v2.4.3** - Registration Page Redesign & Tournament Interface Improvements

### Registration Page Redesign
- **Context-Aware Two-Column Layout**: Eliminated confusing tab interface in favor of intelligent, state-aware display
  - Left column: Tournament Players (always visible during setup and active tournament)
  - Right column: Contextual content that adapts to tournament state
    - **Setup mode**: Displays Saved Players for quick player management
    - **Active/Completed mode**: Automatically switches to Tournament Results
  - Instant switching when bracket is generated - no manual tab navigation required
  - Cleaner, more intuitive workflow aligned with natural tournament progression
- **Saved Players Section Reorganization**: Two-section layout with clear visual hierarchy
  - **Available Players** section at top: Players not yet added to current tournament
  - **In Tournament** section below: Players already added to tournament (with checkmarks)
  - Both sections display in 4-column grid for efficient space usage
  - Players dynamically move between sections when clicked (add/remove from tournament)
  - Click available player to add → moves to "In Tournament" section
  - Click tournament player to remove → moves back to "Available Players" section
  - Clean section headers with subtle styling matching app design language
- **Improved Delete Functionality**: Context-aware deletion with clear user intent
  - Delete button (`×`) only visible for Available Players (hidden for In Tournament players)
  - Prevents accidental deletion of players currently in use
  - Hover tooltip: "Remove from saved players" clarifies permanent deletion
  - Confirmation dialog with clear messaging: "This permanently deletes them from your saved players list"
  - Immediate UI update after deletion (fixed bug in renderPlayerList callback)
- **Visual Polish**: Consistent header styling and improved alignment
  - Tournament Players and Saved Players headers match styling (60px height, #f5f5f5 background)
  - Player count removed from headers for cleaner appearance
  - "Saved Players" replaces ambiguous "Player List" naming
  - Import helper text: "Import from tournament export file" clarifies functionality
  - Delete button styled to match Tournament Players remove buttons (24×24px red outline)
- **Streamlined Player Management**: No more confusion between Tournament and Player List tabs
  - Context makes it obvious: setup shows saved players, active tournament shows results
  - Single-click add/remove between Available and In Tournament sections
  - Visual feedback with checkmarks and green backgrounds for added players
  - No confirmation dialogs for add/remove (fast workflow), confirmation only for permanent deletion
- **Intelligent State Management**: UI adapts automatically to tournament lifecycle
  - Page navigation triggers layout update to show correct content
  - Bracket generation automatically switches right column to results
  - Layout updates propagate through addPlayer, removePlayer, and tournament state changes
  - Seamless experience throughout tournament creation and execution

### Visual Enhancements
- **Match Card Score Display**: Completed matches now display final score in match header
  - Active matches show: `L: 7 | Bo3`
  - Completed matches show: `Result: 2-0`
  - Score replaces lane/Bo3 info when match is complete (contextually relevant)
  - Score numbers prominently styled: 20px, bold, green (#059669), monospace font with subtle shadow
  - "Result:" label sized at 16px for clear hierarchy
  - Match ID sized at 15px for balanced header composition
  - Score automatically reverts to lane/Bo3 display when match is undone
  - Elegant use of existing space without layout changes
- **Finals Match Round Indicators**: Simplified round indicator labels for finals matches
  - BS-FINAL and GRAND-FINAL now show "FINALS" instead of repeating match ID
  - Eliminates redundancy and frees up header space
  - Allows consistent 15px match ID sizing across all match cards including finals
- **Consistent Score Ordering**: Match scores now display in Player1 vs Player2 order across all displays
  - New `formatMatchScore()` helper function provides single source of truth for score formatting
  - Scores consistently show actual player order (e.g., if Player2 won 2-1, shows "1-2" not "2-1")
  - Applied uniformly to bracket match cards and Match Results page
  - Eliminates confusion when winner is Player2
- **Walkover Match Display**: Completed walkover matches now display "W/O" instead of lane/Bo3 info
  - Bracket match cards show "W/O" in header for auto-completed walkover matches
  - Match Results page shows "(W/O)" instead of arbitrary score numbers
  - Provides clear visual indication that match was won by walkover, not played
  - Uses same `formatMatchScore()` helper for consistent handling across all displays
- **Walkover Player Styling**: Walkover players now have consistent, context-aware styling across all match states
  - Completed matches: Walkover players display with green background matching completed match styling
  - Pending/waiting matches: Walkover players blend seamlessly with normal match card backgrounds
  - Player1 walkovers maintain pinkish background and orange left border in pending matches
  - Player2 walkovers have transparent background in pending matches
  - Eliminates visual inconsistencies where walkovers appeared in different colors across tournament bracket

### User Experience Improvements
- **Match Card Hover State Preservation**: Match cards maintain zoom state when changing lane or referee assignments
  - Removed unnecessary full bracket re-renders from lane/referee update functions
  - Only dropdown options refresh across all matches (conflict detection maintained)
  - Eliminates visual interruption and bracket blinking during dropdown changes
  - Zoom naturally ends when mouse leaves card boundaries (expected behavior)
  - Smoother, more responsive user experience when managing match details
- **Bracket Zoom Step Adjustment**: Increased zoom step from 0.015 to 0.025
  - Better balance between precision and speed for mouse wheel users
  - Still provides smooth, precise control compared to original 0.05 step
  - Maintains excellent trackpad experience while improving mouse wheel responsiveness
- **Bracket Home Button Synchronization**: Home button now resets to bracket-size-specific default views
  - 32-player brackets: Returns to optimal overview zoom (0.33) with centered positioning
  - 16-player brackets: Returns to optimized default view (0.45 zoom)
  - 8-player brackets: Returns to optimized default view (0.61 zoom)
  - Matches the initial bracket render positioning for consistent "home" behavior
  - Eliminates confusion when home button returned to different view than initial load

### Files Modified
- `tournament.html` - Removed tab structure, implemented two-column context-aware layout, removed player count from headers, added import helper text, changed container from grid to block element
- `player-management.js` - Added updateRegistrationPageLayout() for context switching, renamed renderPlayerListTab() to renderPlayerList(), separated players into availablePlayers and inTournamentPlayers arrays, conditional delete button rendering with tooltip, added confirmation dialog for deletion, fixed renderPlayerList callback bug
- `bracket-rendering.js` - Added conditional score display in match headers, removed renderBracket() calls from updateMatchReferee(), added refreshAllRefereeDropdowns() when clearing referee, updated to use formatMatchScore() helper, added walkover check to display condition, updated player class assignment to include both 'bye' and 'first-throw' for Player1 walkovers, updated resetZoom() to use bracket-size-specific default positions
- `clean-match-progression.js` - Removed renderBracket() call from updateMatchLane(), added updateRegistrationPageLayout() call after bracket generation
- `main.js` - Added formatMatchScore() helper function with walkover detection, updated Match Results to use consistent score ordering, updated showPage() to call updateRegistrationPageLayout() and renderPlayerList() for registration page, version bump to 2.4.3
- `styles.css` - Restructured .match-player.bye styling to only apply green background in completed matches, removed old tab styles, added saved-players-section and saved-players-section-header styles, updated player-list-header to match column header height (60px), simplified delete button styling

# 2025-10-05

## **v2.4.2** - Bracket Zoom & Interface Polish

### Bracket Controls
- **Improved Zoom Precision**: Reduced zoom step from 0.05 to 0.015 for smoother, more precise control
  - 70% finer zoom increments allow better positioning of large 32-player brackets
  - Smooth zoom experience in Chrome, significantly improved in Safari
  - Optimal for trackpad and mouse wheel control
- **Safari Motion Blur Fix**: Removed CSS transition causing motion blur during zoom/pan
  - Added `will-change: transform` for better performance
  - Eliminated laggy, blurred rendering during bracket navigation
- **Fixed Initial Snap**: Added `updateCanvasTransform()` call when rendering bracket
  - Eliminates jarring zoom/pan snap on first interaction
  - Bracket now displays consistently from page load
- **Smart Default Positioning**: Bracket-size-specific default zoom and pan settings
  - 32-player: zoom 0.32, centered to show full bracket overview with section titles
  - 16-player: optimized zoom and centering for medium brackets
  - 8-player: optimized zoom and centering for small brackets
  - Shows Frontside Round 1 (where action starts) prominently on initial load
- **Tournament Reset Fix**: Default zoom/pan now applies correctly when switching bracket sizes
  - Reset `initialBracketRender` flag in `confirmReset()`
  - Changing from 32→16→8 player brackets now uses correct initial view for each size

### Visual Enhancements
- **Match Card Zoom Depth Effect**: Added visual depth when hovering over match cards while zoomed out
  - Zoomed match enhanced with dramatic shadow (0 20px 60px rgba(0,0,0,0.5))
  - Other matches dimmed (opacity 0.6) and blurred (0.5px) for focus effect
  - Main labels (tournament header, FRONTSIDE, BACKSIDE, FINALS) remain sharp
  - Only activates when bracket zoom < 1.0x for better readability at reduced zoom levels
  - Creates clear visual hierarchy emphasizing the match being inspected

### Interface Improvements
- **Clearer Player List Instructions**: Better guidance when the Player List is empty
- **Fixed Configuration Page Alignment**: Config page elements now properly align with page header
  - Removed excessive padding causing misalignment with "Tournament Configuration" header
  - Consistent layout with Setup and Registration pages

### Bug Fixes
- **8-Player Bracket Line Positioning**: Fixed loser feed lines extending inside FS-R1 match cards
  - Root cause: Backside rendering function incorrectly calculating `round1X` with extra horizontal spacing
  - Lines now cleanly start from left edge of frontside matches as intended
  - Vertical line positioning adjusted to -40px for optimal visual appearance
  - Matches visual consistency of 16/32-player bracket line rendering

### Files Modified
- `bracket-rendering.js` - Zoom step reduction (0.015), removed requestAnimationFrame throttling, added updateCanvasTransform() call, bracket-size-specific default zoom/pan settings, reset flag handling, match hover depth effect, fixed 8-player round1X calculation
- `bracket-lines.js` - Updated 8-player loser feed line positioning, added label IDs for blur exclusion
- `styles.css` - Removed CSS transition from `.bracket-canvas`, added `will-change: transform`, fixed `.config-sections-container` padding
- `tournament-management.js` - Reset `initialBracketRender` flag in `confirmReset()`

# 2025-10-03

## **v2.4.1** - Visual Polish & Typography

### Visual Enhancements
- **Subtle Depth**: Added subtle box shadows (`0 4px 12px rgba(0, 0, 0, 0.06)`) to all main content boxes
  - Applied to: Setup page header and columns, Registration page header and columns, Config page header and sections
  - Purpose: Provides gentle depth perception while maintaining flat design aesthetic
  - Creates visual hierarchy: background → elevated content boxes → interactive elements

### Typography
- **Droid Serif Title Font**: Application title now uses Droid Serif for a professional, editorial feel
  - Hosted locally in `/fonts` folder for offline functionality
  - Applied only to main application header (`.header h1`)
  - Creates visual anchor while keeping interface clean and functional
  - Adds formality without disrupting the modern, workflow-focused design

### UX Improvements
- **Player List Tab Order**: Swapped tab order in Registration page for better workflow
  - "Player List" tab now appears first (left) and is selected by default
  - "Tournament" tab second (right)
  - More intentional workflow: start with registry → add players → manage tournament
- **Alphabetical Sorting**: Player List now displays in alphabetical order
  - Case-insensitive sorting using `localeCompare()` for proper language-specific ordering
  - Makes scanning long player lists much easier
  - Sorted on display only - storage order unchanged

### Branding
- **Favicon**: Added favicon support using existing logo file
  - Automatically uses `logo.jpg` from root folder
  - Appears in browser tab for easy identification
  - Updates automatically when logo file is replaced

### Files Modified
- `styles.css` - Added @font-face declarations for Droid Serif, box-shadow to `.scrollable-column`, `.setup-page-header`, `.registration-page-header`, `.config-page-header`, `.config-section`
- `tournament.html` - Removed Google Fonts links, swapped tab order, adjusted default active states, added favicon link
- `main.js` - Added Player List tab initialization when showing registration page
- `player-management.js` - Added alphabetical sorting to `renderPlayerListTab()`
- `fonts/` - Added DroidSerif-Regular.ttf and DroidSerif-Bold.ttf

## **v2.4.0** - Player List Registry & UI Polish

### 🎉 New: Player List Registry

A new Player List feature helps maintain consistency across weekly tournaments by creating a persistent registry of regular players.

#### Player List Features
- **Automatic Addition**: Players added to tournaments are automatically saved to the Player List
- **Quick Add**: Click [+ Add] to quickly add players from the list to current tournament
- **Manual Curation**: Remove players from list with [× Delete] button
- **Visual Indication**: Green checkmark and bold text show which players are in the current tournament
- **Import/Export**: Player List included in tournament JSON exports with merge/replace options on import
- **Tab Interface**: Clean tab system in Registration page separates tournament players from the registry

#### Technical Implementation
- **localStorage Persistence**: Simple array stored in `playerList` key
- **Case-Insensitive Matching**: Prevents duplicate entries with different capitalization
- **Context-Aware Buttons**: [+ Add], [- Remove], [× Delete] appear based on player state
- **Additive Workflow**: Import offers "merge" or "replace" options with clear messaging

### Server Settings
- **Shared Tournament Delete Permission**: New config setting to control delete button visibility for shared tournaments
  - **Default**: Disabled (delete buttons hidden)
  - **Purpose**: Prevents accidental deletion on hosted deployments
  - **Location**: Config page → UI Settings → Server Settings
  - **Behavior**: When disabled, only Load buttons appear for shared tournaments

### UI Improvements
- **Tournament Results Table**: Now properly hides when no paid players exist, showing clean "No players added yet" message
- **Match Results Humanization**: Setup page Match Results now shows "Grand Final" and "Backside Final" instead of technical IDs (GRAND-FINAL, BS-FINAL)
- **Context-Aware Display**: Statistics modal maintains original table-based empty state display

### Files Modified
- `main.js` - Version bump to 2.4.0, added `humanizeMatchId()` function for human-readable match progression
- `player-management.js` - Player List localStorage functions, tab switching, auto-add logic, import/export
- `tournament-management.js` - Export includes Player List, import shows merge/replace dialog, conditional delete button rendering
- `tournament.html` - Tab interface for Registration page, Player List container, empty message element for results table, server settings checkbox
- `styles.css` - Tab styling, Player List item styling with green "in tournament" state
- `results-config.js` - Context-aware empty state handling, server settings in DEFAULT_CONFIG, save/load server settings
- `dynamic-help-system.js` - Updated Registration page help with Player List documentation

---

# 2025-10-02

## **v2.3.0** - Optional Server Features (Shared Tournaments)

### 🎉 New: Server-Enhanced Tournament Sharing (Optional Feature)

When deployed to a PHP-enabled web server, the application now supports shared tournament hosting - a completely optional feature that activates automatically when server dependencies are met. Local-only usage remains fully functional with zero changes.

#### Shared Tournament Features
- **Browse Server Tournaments**: Automatically displays "Shared Tournaments" section when server API is available
- **Upload to Server**: File picker-based upload (similar to Import workflow) for sharing completed tournaments
- **Delete Server Tournaments**: Remove tournaments from server with confirmation dialog
- **Graceful Degradation**: Features appear only when server is configured; local users see no difference
- **Visual Distinction**: Shared tournaments display with light blue background, sorted by date (newest first)
- **Unicode Support**: Full support for international characters (Norwegian, Swedish, Danish, etc.) in tournament names

#### Technical Implementation
- **REST API Foundation**: Three PHP endpoints in `/api` directory
  - `GET /api/list-tournaments.php` - List available tournaments
  - `POST /api/upload-tournament.php` - Upload tournament with validation
  - `POST /api/delete-tournament.php` - Delete tournament with confirmation
- **Security**: Filename validation, directory traversal prevention, CORS headers
- **Progressive Enhancement**: Server detection on page load, conditional UI injection
- **Zero Breaking Changes**: Core offline functionality completely preserved

#### Server Requirements (Optional)
- PHP 7.0+ with FastCGI/PHP-FPM
- Write permissions to `/tournaments` directory
- Web server (nginx, Apache, etc.)
- See `/api/README.md` for setup instructions

### Files Modified
- `main.js` - Version bump to 2.3.0
- `tournament-management.js` - Shared tournament loading, file-based upload, delete functionality, debug logging
- `tournament.html` - Upload file picker, conditional upload button placement
- `bracket-lines.js` - Fixed localStorage key for club name (dartsConfig)

### Files Added
- `api/list-tournaments.php` - List tournaments endpoint
- `api/upload-tournament.php` - Upload tournament endpoint with Unicode support
- `api/delete-tournament.php` - Delete tournament endpoint
- `api/README.md` - Server setup documentation and API reference

---

## **v2.2.1** - Polish and Bug Fixes

### Visual Improvements
- **Match Progression Text Styling**: "Leads to..." text in Match Controls cards now uses normal font weight and muted gray color (#6b7280) for better visual hierarchy, distinguishing it from the bold match ID

### Bug Fixes
- **Tournament Header Branding**: Fixed custom club names not displaying in tournament bracket header
  - Root cause: Incorrect localStorage key reference (`globalConfig` vs `dartsConfig`)
  - Tournament headers now properly show configured club name in "Club Name - Tournament Name" format
  - Branding updates now trigger bracket re-render for immediate visual feedback

### Files Modified
- `main.js` - Version bump to 2.2.1, application identity encoding
- `bracket-rendering.js` - Match progression text styling, identity validation
- `bracket-lines.js` - Fixed localStorage key for club name retrieval
- `results-config.js` - Added bracket re-render on branding save, default club name fallback
- `tournament.html` - Application identity initialization
- `styles.css` - Integrity hash comment

---

# 2025-10-01

## **v2.2.0** - Minimalistic Flat 2D Design

### Visual Framework Refinements
- **Consistent Border Hierarchy**: Implemented three-tier border system throughout application
  - Main containers: Bold dark borders (`#666666`) for strong visual structure
  - Section headers: Subtle light borders (`#e8e8e8`) for gentle separation
  - Internal elements: Light borders for organization without visual clutter
- **Enhanced Border Contrast**: Added dark borders to footer and main page containers matching header styling
- **Fixed Double Border Issues**: Resolved thick border appearance on column headers caused by conflicting border styles
- **Perfect Text Alignment**: Fixed vertical centering issues in all section headers across Setup, Registration, and Config pages

### Config Page Organization
- **Logical Section Grouping**: Reorganized Config page for better workflow
  - Left Column: Logo, Branding, Lane Management, User Interface
  - Right Column: Match Configuration, Point Values
- **Improved Information Architecture**: Physical/hardware settings grouped with UI preferences, while game rules and scoring grouped together

### Registration Page Fixes
- **Table Width Resolution**: Fixed Tournament Results table not extending to full container width using hidden 10th column technique
- **Container Padding Restoration**: Restored proper 24px padding for symmetric spacing throughout Registration page

### Complete Flat Design Unification
- **Eliminated All Rounded Corners**: Removed remaining `border-radius` from all interface elements for complete geometric consistency
  - Recent Tournaments items: Removed 5px rounded corners
  - Match Results cards: Changed from 8px to 0px border-radius
  - Tournament bracket match cards: Changed from 10px to 0px border-radius
  - Tournament control buttons: Changed from 10px to 0px border-radius (Stats/Results, Match Controls, Players/Points, zoom controls)
  - Match Controls (Active): Flattened Start/Stop Match buttons, Referee Suggestion items, and match cards
  - Match Controls (Celebration): Flattened Tournament Achievements items, Export button, Tournament Highlights container and stat boxes
  - **Podium Exception**: Kept rounded corners on celebratory podium stands and player name boxes for visual appeal
- **Visual Harmony Achieved**: Every functional element uses sharp, angular geometry; decorative celebration elements retain subtle rounding

### Match Controls Enhancements
- **Match Progression Information**: Added "Leads to..." text to match card headers showing tournament progression (e.g., "BS-2-2 • Leads to BS-3-1")
- **Intelligent Display**: Progression info shows destination matches or "tournament completion" for final matches
- **Compact Integration**: Progression text appears inline with match ID in bold, maintaining clean layout

### Setup Page Polish
- **Match Results Padding**: Added 8px horizontal padding to player information lines for better text breathing room within cards
- **Match Header Corners**: Removed rounded corners from match card headers for consistency with flat design

### Celebration Mode Refinements
- **UI Cleanup**: Hidden redundant "💾 Export Data" header since Export button already displays this information
- **Consistent Flattening**: Applied flat design to all celebration UI except decorative podium elements

### Technical Improvements
- **CSS Cleanup**: Removed duplicate and conflicting border definitions that caused inconsistent styling
- **Border Optimization**: Changed column headers from full borders to bottom-only borders to prevent double-border effects
- **Padding Standardization**: Unified header padding (`0 24px` for columns, `16px 24px` for config sections) for perfect vertical centering
- **Table Structure Enhancement**: Added hidden column to fix complex table width calculation issues
- **CAD-style Info Box**: Increased size by 20%

### Files Modified
- `styles.css` - Border hierarchy, table fixes, complete border-radius elimination, match result padding
- `tournament.html` - Config page reorganization, table structure enhancement
- `tournament-management.js` - Removed inline border-radius from tournament items
- `results-config.js` - Updated table generation for proper width behavior
- `bracket-rendering.js` - Match progression display, celebration UI cleanup

This update achieves complete flat design transformation across ALL pages (Setup, Registration, Config, Tournament, Match Controls, Celebration) with unified visual language, enhanced match information display, resolved layout issues, and refined organizational structure for optimal usability.

## **v2.2.0-beta** - Professional Border System & Visual Consistency Improvements

### UI Redesign - Core Pages
- **Setup, Registration, Config Pages**: Complete redesign following new flat 2D design principles
  - Removed all rounded corners, gradients, and shadows for pure flat aesthetic
  - Implemented consistent spacing system (24px primary, 16px secondary, 8px tight)
  - Standardized element heights (44px interactive elements, 60px headers, 72px content rows)
  - Applied muted monochromatic color palette with selective green/amber/red accents
  - Fixed padding issues across pages ensuring content extends to edges properly
  - Registration page: Fixed scrolling behavior (removed fixed height constraint, entire page now scrolls naturally)

### Button System Overhaul
- **Flat Outline Buttons**: Replaced filled buttons with minimal outline style throughout application
  - Base: White background with 1px gray border
  - Hover: Subtle color-tinted backgrounds (#dcfce7 green, #fef3c7 amber, #fef2f2 red)
  - Updated all dialogs: Match Controls, Statistics, Confirm Winner, Reset Tournament, Delete Tournament, Undo Confirmation
  - Consistent styling across primary actions (green), warnings (amber), and destructive actions (red)

### Modal/Dialog Improvements
- **Comprehensive rounded corner removal** from all modal dialogs for design consistency:
  - Modal containers and all content boxes
  - Undo modal: match cards and "no matches" message box
  - Confirm Winner modal: match progression info box
  - Match Controls Setup stage: setup messages and Add Player input/button
  - All text/number/date inputs in modals (with browser-specific prefixes for maximum compatibility)
  - Import/Load Tournament modals: all info boxes and buttons
- **Enhanced button states**:
  - Edit Statistics dialog: Redesigned +/− buttons (24×24px) with red/green accents and proper hover effects
  - Reset Tournament dialog: Added visual feedback when enabled (amber background) with proper contrast
  - All Cancel buttons converted to flat outline style
- **Fixed alignment issues**: Vertically centered text labels using `transform: translateY()` approach

### Design System Documentation
- **DESIGN.md principles implemented**:
  - Minimalistic flat 2D aesthetic with no gradients or shadows
  - Muted color strategy with strategic accent usage
  - Fixed desktop-focused layouts with consistent spacing
  - Typography hierarchy with proper weight and size differentiation
  - Border-based hover feedback instead of background changes

### Technical Improvements
- **Removed duplicate CSS rules** causing override conflicts on Registration and Config pages
- **Cleaned up inline styles** in favor of reusable CSS classes
- **Consistent z-index management** for modal layering
- **JavaScript refactoring**: Removed inline background style manipulation in favor of CSS class-based styling

### Bug Fixes
- **Payment Status Protection**: Prevented paid/unpaid status changes during active or completed tournaments
  - Clicking player cards in active/completed tournaments now shows "Tournament in Progress" dialog
  - Protects tournament integrity and historical data from accidental modifications
  - Applies to both active tournaments and read-only completed tournaments

### Files Modified
- `styles.css` - Extensive redesign following flat 2D principles, comprehensive rounded corner removal
- `tournament.html` - Button updates, modal structure improvements, input field styling
- `tournament-management.js` - Reset button state management cleanup
- `player-management.js` - Added tournament status validation to togglePaid()
- `bracket-rendering.js` - Match Controls Setup stage rounded corner removal (Add Player section)
- `clean-match-progression.js` - Confirm Winner progression box styling updates
- Main pages (Setup, Registration, Config, Tournament) - Layout and spacing standardization

This release establishes a comprehensive design system foundation for the entire application, replacing the previous mixed aesthetic with a cohesive, professional flat 2D interface.

# 2025-09-29
## **v2.1.5-beta**
- Made the "Save Statistics" button in the Edit Statistics dialog respond to Enter

# 2025-09-28
## **v2.1.4** Visual Changes
- Changed "Awaiting Player" in matches with no assigned players italics and muted, to make it look less like a "real" player and improve visibility when zoomed out
- Changed the layout and font size/weight for players in the upcoming matches in Match Controls for better legibility

## **v2.1.3** Read-Only Tournament Protection & Critical Bug Fixes
- **Read-Only Tournament Protection**: Complete protection system for imported and loaded completed tournaments
  - Completed tournaments from files or localStorage automatically set to read-only
  - Comprehensive undo prevention: no undo styling, no clickable undo handlers, no undo modals
  - Clean status bar messaging: "Completed tournament: Read-only" for all match hovers
  - Early prevention: undo attempts blocked before any UI appears
  - Reset Tournament escape hatch available for modification needs
- **Persistent Read-Only State**: Read-only flag survives browser refreshes and navigation
  - Fixed critical bug where readOnly flag was lost on page reload
  - Ensured data integrity for shared tournament results
  - Maintains distinction between active tournaments (editable) and archived results (protected)

### Critical Bug Fixes
- **Fixed Tournament Loading Data Loss**: Tournaments loaded from localStorage were losing players/matches after browser refresh
  - Root cause: `continueLoadProcess()` wasn't including players/matches in tournament object structure
  - Solution: Added players/matches to tournament object and global array assignment
  - Impact: Loaded tournaments now survive page refreshes with complete data
- **Fixed Read-Only Persistence**: Read-only flag wasn't saved to localStorage, causing loss on refresh
  - Root cause: `saveTournamentOnly()` function missing readOnly field in saved object
  - Solution: Added `readOnly: tournament.readOnly` to tournament save structure
  - Impact: Read-only tournaments maintain protection across browser sessions
- **Fixed App Initialization**: Page startup wasn't preserving tournament readOnly flag or complete data
  - Root cause: `autoLoadCurrentTournament()` in main.js missing players, matches, and readOnly fields
  - Solution: Added complete tournament data structure matching import/load processes
  - Impact: All tournament data and protection state preserved on app startup
- **Fixed Status Panel Import Updates**: Status Panel wasn't updating when importing tournaments
  - Root cause: Import process missing `updateTournamentWatermark()` call
  - Solution: Added watermark update to `continueImportProcess()` display updates
  - Impact: Status Panel now updates immediately for both loading and importing operations

### Technical Implementation
- **Three-Layer Protection**: Read-only checks in `isMatchUndoable()`, `handleSurgicalUndo()`, and `getDetailedMatchState()`
- **Consistent Data Structure**: Unified tournament object structure across import, load, and initialization
- **Status Bar Integration**: Non-intrusive read-only messaging through existing status system
- **Complete Undo Prevention**: UI-level prevention (no styling) + interaction-level prevention (early blocking)

### Files Modified
- `tournament-management.js` - Read-only flags, complete data structures, Status Panel updates
- `bracket-rendering.js` - Undo prevention, status messaging, match state detection
- `main.js` - App initialization with complete tournament data preservation
- `clean-match-progression.js` - Read-only undo prevention
- `history-management.js` - Read-only undo prevention

This update ensures tournament result integrity while maintaining full functionality for active tournaments, with comprehensive bug fixes that resolve data loss and state persistence issues.

-----

# 2025-09-27

## **v2.1.2** CAD-Style Information Box Enhancements
- **Dynamic Progress Display**: Replaced static "DOUBLE ELIMINATION" text with real-time tournament progress
  - Active tournaments show "COMPLETED MATCHES: #" with live match completion count
  - Completed tournaments display winner recognition: "WINNER: WINNER NAME" in all-caps CAD style
  - Automatic state switching between progress tracking and winner display
- **Header Simplification**: Streamlined CAD header for better readability
  - Removed club name from header to focus on tournament name
  - Added automatic truncation for long tournament names (35+ characters)
  - Cleaner, more professional appearance with improved space utilization
- **Winner Name Formatting**: Enhanced winner display with proper CAD technical drawing aesthetics
  - First name + last initial format: "JOHN S." for space efficiency
  - All-caps formatting maintains consistent CAD style throughout
  - Handles edge cases like single names gracefully
- **Real-Time State Integration**: CAD box now fully integrated with tournament state system
  - Updates automatically during match completions and tournament progression
  - Responds to undo operations by reverting to appropriate display mode
  - Winner changes reflect immediately without page refresh

## **v2.1.1** Bugfixes
- CAD box was not dynamically updating
- CAD box has more transparency
- Status bar message was missing from GRAND-FINAL in 8 and 16-player brackets.

## **v2.1.0** Professional Tournament Management and CAD-Style Information Display

### Tournament Management Enhancements
- **Club Branding System**: Complete overhaul of application title configuration
  - Changed "Application Title" to "Club Name" in Config page for clearer purpose
  - Automatic title generation: "[Club Name] - Tournament Manager" format
  - Enhanced tournament bracket headers with club name integration
  - Tournament displays now show "Club Name - Tournament Name" with date
  - Legacy configuration support for seamless migration from previous versions

- **Round-Based Match Organization**: Revolutionary Command & Control Center interface
  - Match Controls dialog reorganized from bracket-side grouping to chronological rounds
  - Frontside and Backside matches unified by round progression (FS-R1, BS-R1, etc.)
  - LIVE matches remain prominent and unified at the top for immediate attention
  - Maintains all bracket context while improving operational flow
  - Reflects military Command & Control Center philosophy for tournament management

### Visual and Interface Improvements
- **CAD-Style Information Box**: Professional technical drawing aesthetic
  - Replaced simple tournament watermark with authentic CAD title block
  - Mixed-size cell structure mimicking engineering drawing standards
  - Positioned flush in bottom-right corner using viewport frame
  - Monospace typography (Courier New) for technical drawing authenticity
  - Consistent 1px line weights throughout grid structure
  - Real-time tournament data: club name, format, players, matches, date, version, status

- **Enhanced Tournament Bracket Positioning**: Improved visual hierarchy
  - Tournament title block repositioned 60px higher to eliminate overlap with bracket labels
  - Better integration of club name with tournament information
  - Maintains professional appearance while providing complete branding context

- **User Experience Refinements**: Clearer communication throughout interface
  - Replaced technical "TBD" with user-friendly "Awaiting Player" in match displays
  - Improved button color coding: Export (green), Import (orange), Reset (red) for risk indication
  - Celebration messages now count only paid players, removing "registered" terminology
  - Placement labels repositioned contextually above respective tournament rounds

### Technical Infrastructure
- **Robust Data Integration**: Enhanced tournament information accuracy
  - CAD information box reads real-time data from localStorage
  - Smart match counting excludes BYE matches, includes competitive matches only
  - Dynamic status tracking: SETUP → ACTIVE → COMPLETE based on match progression
  - Accurate player count using paid players only
  - Automatic bracket size detection and display

- **Configuration Migration**: Seamless transition from legacy settings
  - Automatic extraction of club names from old "Application Title" format
  - Fallback support ensures no data loss during configuration updates
  - Maintains backward compatibility while enabling new features

### Architectural Philosophy
This release embodies the **Command & Control Center** design philosophy:
- **Information at a glance**: CAD-style technical display provides comprehensive tournament status
- **Operational efficiency**: Round-based organization matches natural tournament flow
- **Professional appearance**: Technical drawing aesthetics convey competence and precision
- **Clear communication**: User-friendly terminology eliminates confusion
- **Brand integration**: Club identity seamlessly woven throughout tournament experience

---

# 2025-09-26

## **v2.0.3** Enhanced Bracket Interaction and User Experience

### New Interactive Features
- **Hover Zoom for Match Cards**: Revolutionary new feature for crowded bracket navigation
  - Automatically activates when bracket zoom level is less than 1.0x
  - 1-second hover delay prevents accidental triggers during navigation
  - Scales individual matches to 1.0x viewport size for perfect readability
  - Smooth CSS transitions with intelligent animation conflict resolution
  - Preserves all match interactions (winner selection, lane/referee assignment)
  - Seamless integration with existing live match pulse animations

### Enhanced Visual Elements
- **Directional Navigation Labels**: Added triangular arrows to bracket section headers
  - "FRONTSIDE ►" and "◄ BACKSIDE" for clear directional guidance
  - Professional triangular arrow symbols replacing basic text indicators
  - Maintains consistent styling with existing bracket typography

- **FINALS Label Addition**: Precisely positioned championship section identifier
  - Positioned directly above BS-FINAL match card with exact bracket rendering calculations
  - Consistent vertical alignment with FRONTSIDE/BACKSIDE labels
  - Uses same professional typography and styling standards

### User Experience Improvements
- **Intuitive Match Discovery**: Hover zoom eliminates fumbling when searching for specific matches
  - Natural user behavior (pausing cursor while looking) triggers helpful zoom
  - No learning curve - feature is discoverable through normal interaction patterns
  - Becomes integral part of tournament operator workflow after discovery

- **Comprehensive Help Documentation**: Added hover zoom feature description to dynamic help system
  - Integrated into Tournament page "Bracket Navigation" section
  - Clear explanation of activation conditions and behavior
  - Updated navigation tips to include hover functionality

### Technical Excellence
- **Animation Conflict Resolution**: Sophisticated handling of overlapping visual effects
  - `zoom-hover` CSS class disables live match pulse animation during hover
  - Proper state management with timeout cleanup on mouse leave
  - Transform origin optimization for smooth scaling behavior

- **Viewport-Relative Scaling**: Consistent zoom experience regardless of current bracket zoom level
  - Dynamic scale calculation ensures 1.0x viewport appearance
  - Mathematical precision: `targetScale / currentZoomLevel = elementScale`
  - Perfect readability at any zoom level from 0.3x to 0.99x

### Bug Fixes
- **Player Statistics Reset**: Fixed tournament reset not clearing player achievement data
  - Added proper statistics clearing in `confirmReset()` function
  - Ensures clean slate for shortLegs, highOuts, tons, and oneEighties tracking
  - Maintains data integrity across tournament lifecycle

### User Experience Impact
- **Effortless Navigation**: Hover zoom transforms crowded bracket usability
- **Professional Polish**: Directional indicators and FINALS label complete visual hierarchy
- **Reliable Data Management**: Tournament reset now properly handles all player data
- **Discoverable Excellence**: Features that users find naturally and adopt into their workflow

# 2025-09-25

## **v2.0.2** Complete Tournament Bracket Visualization System

### Major Tournament Bracket Enhancements
- **Complete Tournament Progression Lines**: Implemented comprehensive visual flow system for all bracket sizes
  - Professional L-shaped connector lines showing frontside and backside progression paths
  - Custom finals routing with complex multi-path connections to BS-FINAL and GRAND-FINAL
  - BS-FINAL text indicators with arrows for clear backside completion visualization
  - 60+ progression elements for 32-player brackets with bulletproof gap prevention
  - All bracket sizes (8, 16, 32 players) now have complete visual tournament flow

- **Backside Placement Labels**: Added placement indicators below each backside bracket round
  - 8-player: "7th-8th Place", "5th-6th Place", "4th Place" labels
  - 16-player: "13th-16th Place" down to "4th Place" labels
  - 32-player: "25th-32nd Place" down to "4th Place" labels
  - Professional 24px bold text positioned below gradient background
  - Non-intrusive design providing immediate ranking feedback

- **Dynamic Tournament Header Sizing**: Bracket-specific font scaling for optimal visual proportion
  - 8-player brackets: 54px (compact for simple brackets)
  - 16-player brackets: 64px (balanced for moderate complexity)
  - 32-player brackets: 78px (prominent for complex brackets)
  - Progressive 12px increments creating smooth visual hierarchy

### Technical Achievements
- **bracket-lines.js Architecture**: Complete separation of line rendering from match positioning
- **Bracket Isolation**: Independent line generation for each bracket size with zero cross-contamination
- **Position-Based System**: Clean separation between positioning logic and line drawing
- **Gap Prevention**: 1-pixel overlap technique eliminating visual gaps at 90-degree line bends
- **Sky High Resilience**: All improvements follow established crash-resistance principles

### Bug Fixes
- **Fixed order of Backside round 2 matches in the 8-player bracket**
- **Fixed alignment of backside match-cards for the 16-player bracket**
- **Enhanced Dialog Reliability**: Fixed Edit Statistics modal button accessibility
  - Added scrollable content area preventing button cutoff at various zoom levels
  - Cancel and Save Statistics buttons always remain visible and accessible

### User Experience Impact
- **Tournament Clarity**: Complete visual understanding of tournament progression and placement structure
- **Professional Presentation**: Comprehensive ranking information with adaptive typography
- **Enhanced Reliability**: Improved modal accessibility and bracket rendering consistency
- **Scalable Excellence**: All improvements work seamlessly across supported bracket sizes

# 2025-09-22

## **v2.0.2-beta** Reset Tournament Bug Fix, Focus on Tournament Bracket Visuals
- **Fixed Event Listener Accumulation**: Resolved bug where resetting the same tournament multiple times caused exponentially increasing browser confirmation dialogs
- **Clean Event Handling**: Tournament reset input field now properly removes old event listeners before adding new ones
- **Color Consistency**: Updated reset button enabled state to use subtle orange color matching interface palette
- **Improved Watermark Positioning**: Moved "NewTon DC Tournament Manager" text from bottom of viewport to centered below last first-round match for all bracket sizes
- **Enhanced Watermark Visibility**: Increased watermark opacity for better readability while maintaining subtle appearance
- **Rendering Error**: Fixed an error where the matches in backside rounds one and two were rendered in the wrong order.
- **New file: bracket-lines.js**: Split from `bracket-rendering.js` for easier maintenance
- **Bracket Lines Proof of Concept**: Added complete tournament flow visualization for 8-player brackets with professional L-shaped connector lines showing frontside and backside progression, and finals connections

## v2.0.1 Dialog Visual Consistency
- **Dialog Color Harmonization**: Updated all modal dialogs to use consistent subtle color palette
- **Tournament in Progress Dialog**: Changed blue "Got it" button and info box border to subtle green theme
- **Reset Tournament Dialog**: Replaced bright red/blue sections with muted orange/green styling, updated "Reset Tournament" button
- **Export Dialogs**: Converted bright blue/green sections to consistent subtle green styling, updated "Export Results" button
- **Warning Boxes**: All yellow warning sections now use subtle orange border and muted background across all dialogs
- **Professional Polish**: Eliminated visual chaos from competing bright colors, creating cohesive modal experience

## v2.0.0 Tournament Management Platform Maturity
- **Major Version Release**: Complete transformation from functional tool to professional tournament management platform
- **Core Architecture**: Hardcoded tournament logic with transaction-based history system for bulletproof reliability
- **Surgical Undo System**: Transaction-based undo enabling precise match correction without affecting independent matches
- **Match Controls Command Center**: State-driven unified interface for tournament setup, match management, and celebration
- **Referee Suggestions**: Intelligent referee assignment with conflict detection and visual organization
- **Tournament Celebration**: Olympic-style podium display with achievement tracking and integrated export
- **Unified Dialog System**: Rich modal replacements with stack-aware management and Esc key integration
- **Live Tournament Intelligence**: Real-time match history, progression status bar, and dynamic results integration
- **Cohesive Visual Design**: Muted color palette with cross-component consistency, replacing bright competing colors
- **Enhanced UX**: Dynamic help system, lane management, match validation, and comprehensive workflow improvements
- **Technical Foundation**: Zero-dependency modular architecture with efficient data persistence and browser compatibility

This release represents the culmination of incremental improvements since v1.4, establishing NewTon DC as a mature, production-ready platform for competitive darts tournaments.

## v1.6.12 Debugging of Referee Suggestions
- Referee suggestions had no debugging for verifying workflow
- The suggestions show the latest 7 losers, latest 7 winners, and latest 7 assignments
- Players are moved from Recent Losers/Winners to Recent Assignments on match start/completion to avoid suggesting same referee too often
- Visual Change: Made the rounded corners of the Backside Bracket gradient more pronounced.

## v1.6.11 Backside Bracket Visual Enhancement
- **Gradient Background**: Added subtle gradient background to backside brackets for all tournament sizes (8, 16, 32 players)
- **Visual Distinction**: Backside brackets now have a gradient from 0.06 opacity on the right fading to transparent on the left
- **Consistent Styling**: Uniform visual treatment across all bracket sizes with proper positioning and rounded corners
- **Non-Intrusive Design**: Background stays behind matches and doesn't interfere with user interactions

# 2025-09-20

## v1.6.7, 1.6.8 & 1.6.9 Tournament Visuals Bug-Fix
- Improved tournament flow for 16 and 32-player brackets

## v1.6.6 Professional Visual Bracket Positioning
- **Systematic Match Alignment**: Complete overhaul of bracket positioning for 8, 16, and 32-player tournaments
- **Visual Progression Clarity**: Matches positioned to show clear convergence patterns and tournament flow
- **8-Player Bracket Excellence**: FS-R2 centered between inputs, BS mirrored to left with proper alignment
- **16-Player Bracket Refinement**: BS-R1/BS-R2 aligned with FS-R2, BS-R3/BS-R4 aligned for classical layout
- **32-Player Bracket Mastery**: Full 7-round backside positioning with strategic vertical alignment patterns
- **Finals Prominence**: 6x spacing for all bracket sizes gives finals proper visual weight
- **Backside Final Fix**: BS-FINAL now properly turns green when completed (CSS specificity resolved)
- **Enhanced Spacing**: Improved horizontal spacing options for better visual balance
- **Reset Tournament Fix**: Results Table now properly refreshes after tournament reset

# 2025-09-19

## v1.6.5 Enhanced Two-Line Match Status Display
- **Rich Contextual Information**: Upgraded status bar to show two lines of information per match
- **Match State Integration**: First line shows match ID and current state (Pending, Ready to Start, Started, Can Undo, Cannot Undo with blocking matches)
- **Walkover Detection**: Special handling for bye/walkover matches showing "Cannot Undo, Walkover"
- **Specific Undo Blocking**: Displays exact matches preventing undo operations (e.g., "Cannot undo, blocked by FS-3-1")
- **Centered Layout**: Both status lines are center-aligned for professional appearance
- **Tournament Management Integration**: Creates seamless workflow between Tournament Bracket (information) and Match Controls (actions)
- **Eliminates Guesswork**: No more visual scanning of backside bracket to find blocking matches due to complex mirroring rules

## v1.6.4 Dynamic Match Progression Status Bar
- **Tournament Flow Visualization**: Added elegant status bar system showing match progression on Tournament page
- **Smart Hover Information**: Hover over any match card to see where players advance next (e.g., "Match FS-2-1 leads to FS-3-1 and BS-2-2")
- **Purposeful Design**: Status bar background only appears when displaying information, creating a subtle "blooming" effect
- **Optimized Timing**: 300ms hover delay prevents jumpy navigation while maintaining responsiveness
- **Universal Coverage**: Works for all match states and tournament sizes using hardcoded progression lookup tables
- **Undo Context**: Helps users understand bracket flow and identify why certain matches block undo operations
- **Tournament Page Only**: Clean implementation that doesn't affect other pages

## v1.6.3 Polish & UX Improvements
- **Matches Played**: Tournament celebration now shows "Matches played" instead of meaningless "Total matches" count (excludes walkover matches)
- **Focus Preservation**: Fixed input field losing focus when adding players from Match Controls setup interface
- **Button Layout**: Swapped Match Controls and Stats/Results button positions for better accessibility

## v1.6.2 Auto-Open & UI Polish
- **Auto-Open Match Controls**: Configurable setting to automatically open Match Controls when entering Tournament page (enabled by default)
- **UI Layout Fix**: Fixed Global Settings UI options display to show checkboxes on separate lines for better readability

## v1.6.1 Small Bug-fix
- The section "Recent Assignments", in Match Controls -> Referee Suggestions was lost. Now it's found.

## v1.6.0 Command Center Revolution

### 🎯 Match Controls Command Center
Transformed Match Controls into a true tournament management Command Center with intelligent state-driven interfaces.

**Setup State Enhancements:**
- **Tournament Branding**: Title shows "Match Controls - [Tournament Name]"
- **Enhanced Status Display**: Live player count with bracket size calculation ("8 players registered, 6 entrance fees paid (ready for 16-player bracket)")
- **Interactive Player Management**: Click player names to toggle paid/unpaid status with visual feedback (✓/☐)
- **Direct Player Addition**: Add players without leaving tournament view
- **Setup Actions Hub**: Integrated buttons for Player Registration Page, Global Settings Page, and dynamic bracket generation
- **Smart Button Text**: Generate button reflects validation states ("Generate 16-Player Bracket" vs "Generate Bracket (need 4+ players)")
- **Helpful Guidance**: Visual hints and tips for interactive elements

**Active State Improvements:**
- **Tournament Branding**: Consistent naming throughout active tournament management
- **Real-time Updates**: All match state changes immediately refresh Command Center

**Celebration State Enhancement:**
- **Tournament Branding**: "🏆 [Tournament Name] Complete! 🏆"
- **Date Context**: "[Date] • Congratulations to all [X] players!" for perfect social media sharing

### 🔄 Seamless State Transitions
- **Setup → Active**: Generate bracket automatically refreshes to show matches/referees
- **Active → Setup**: Reset tournament refreshes to show setup interface
- **All Transitions**: Maintain context and tournament branding throughout

### 🎛️ Streamlined UI Architecture
- **Removed Redundant Elements**: Eliminated top-left "Generate Bracket" button
- **Promoted Match Controls**: Moved to prime top-left position for better accessibility
- **Enhanced Tournament Workflow**: Single entry point for all tournament management phases

### 🐛 Critical Fixes
- **Match Completion Refresh**: Fixed Match Controls not updating when completing matches without confirmation dialog
- **Reset Tournament Function**: Fixed ReferenceError by correcting function name from `resetTournament()` to `showResetTournamentModal()`
- **Validation Logic**: Added proper >32 player limit with clear error messaging

### 📚 Documentation Updates
- **Dynamic Help System**: Updated Tournament page help to reflect new Match Controls workflow
- **Action Buttons**: Help system buttons now direct users to Match Controls instead of removed Generate Bracket button
- **User Messages**: Updated all references to align with new workflow

### 🎨 Visual Polish
- **Consistent Typography**: Refined section headers to proper visual hierarchy
- **Professional Terminology**: "Entrance Fee Paid/Not Paid" for better consistency
- **Intuitive Icons**: ✓ for paid, ☐ for unpaid players with clear visual distinction
- **Responsive Design**: Optimized input sizing and alignment throughout

---

## v1.5.4 State-Driven Match Controls Architecture

### 🏗️ Core Architecture: Tournament State-Driven Match Controls
Completely refactored Match Controls to use tournament status as the single source of truth for UI behavior.

**Match Controls Column (Left):**
- **'setup'**: Shows styled setup message with guidance for adding players and generating matches
- **'active'**: Shows live/ready matches organized by frontside/backside brackets
- **'completed'**: Shows celebration podium with winner rankings and tournament highlights

**Referee Suggestions Column (Right):**
- **'setup'**: Shows setup message explaining referee suggestions will appear when tournament starts
- **'active'**: Shows referee suggestions (recent losers, winners, assignments) with proper headers
- **'completed'**: Shows player achievements (most 180s, highest checkout, etc.) and tournament summary

### 🐛 Critical Data Fixes
- **Results Table Rankings**: Fixed to read from tournament object instead of stale localStorage data
- **Achievement Display**: Fixed sections not being made visible after populating with achievement data
- **Tournament Persistence**: Fixed loaded tournaments not surviving browser refreshes
- **Recent Tournaments**: Fixed new tournaments not appearing in list and active status not updating

### 🎯 UI Consistency Improvements
- **Header Reset**: Active tournaments now properly reset subsection headers from celebration state
- **State Clearing**: All celebration elements properly cleared when switching tournaments
- **Setup State**: Added proper setup messages for both columns when tournament is in initial state

### 🔧 Technical Improvements
- **Single Source of Truth**: All Match Controls logic now flows from `tournament.status`
- **Reliable State Management**: Tournament status drives all UI decisions instead of derived match state
- **Consistent Updates**: All tournament operations (create, load, delete, import) now refresh displays properly
- **Data Synchronization**: Fixed discrepancies between tournament object and localStorage persistence

This architectural overhaul transforms Match Controls from a reactive system to a predictable, state-driven interface that accurately reflects tournament lifecycle at all times.

## v1.5.3 Tournament Management Modal Suite

### ✨ New Feature: Professional Tournament Management Dialogs
- **🏆 Tournament In Progress Warning Modal**
  - Replaced browser alert with rich, informative modal explaining tournament state
  - Clear guidance on where to find "Reset Tournament" (Setup page)
  - Professional styling with color-coded information boxes and helpful instructions

- **🗑️ Delete Tournament Confirmation Modal**
  - Enhanced deletion workflow with detailed tournament information display
  - Shows tournament name, date, player count, and current status before deletion
  - Clear warning about permanent data loss with color-coded danger alerts
  - Comprehensive list of what will be removed (all data, statistics, results, configuration)

- **📂 Import Tournament Overwrite Modal**
  - Intelligent conflict resolution when importing tournaments with existing names/dates
  - Side-by-side comparison showing existing vs. imported tournament details
  - Clear explanation of consequences with helpful alternative suggestions
  - User-friendly button options: "Cancel Import" vs "Overwrite Existing"

- **🔄 Load Tournament Confirmation Modal**
  - Rich before/after comparison showing current vs. selected tournament
  - Dynamic layout that hides current tournament section when none is active
  - Prominent data safety guarantee explaining no data loss will occur
  - Detailed action plan explaining exactly what happens during the load process
  - Responsive design with scrollable content and compact spacing for better fit

- **📤 Export Confirmation Modals (JSON/CSV)**
  - Comprehensive tournament overview with status, progress, and player information
  - Format-specific export details showing filename, content type, and included data
  - Smart status detection with color-coded warnings for incomplete tournaments
  - Detailed content preview listing exactly what will be included in each export format
  - Professional styling with clear file information and download confirmation

### 🎨 Enhanced User Experience
- **Consistent Design Language**: All modals follow the same professional styling and color scheme
- **Rich Information Display**: Users see comprehensive details before making decisions
- **Color-Coded Sections**: Blue for information, red for warnings, yellow for cautions, green for success
- **Esc Key Support**: All new modals integrate with the stack-aware Esc handling system
- **Improved Readability**: Compact spacing and organized layouts for better information hierarchy

### 🔧 Technical Implementation
- **Modal Integration**: All dialogs use the unified dialog stack system with proper z-index management
- **Code Consolidation**: Refactored duplicate import/load logic into reusable functions
- **Global Function Exports**: All modal functions properly available for button click handlers
- **Error Handling**: Comprehensive error checking and user feedback throughout all workflows
- **Memory Management**: Proper cleanup and data storage for modal callback functions

### 🚀 Browser Dialog Elimination
Completely replaced generic browser dialogs (`alert`, `confirm`, `prompt`) with rich, contextual modals:
- ✅ Tournament progress warnings → Rich guidance modal
- ✅ Tournament reset confirmation → Security validation modal
- ✅ Tournament deletion → Detailed impact modal
- ✅ Import conflicts → Clear overwrite decision modal
- ✅ Tournament loading → Comprehensive before/after modal
- ✅ Export confirmations → Professional export details modal

# 2025-09-18

## v1.5.2 Stack-Integrated Esc Key Support

### ✨ New Feature: Universal Esc Key Support for Dialogs
- **🔑 Stack-Aware Esc Handling**
  - Enhanced `pushDialog()` function with optional `enableEsc` parameter for explicit control
  - Single global Esc handler that respects dialog stack settings - no conflicts with existing handlers
  - Esc support enabled for Statistics Modal, Match Command Center, and Edit Statistics Modal

- **🎯 Explicit Control Model**
  - Clear intent in code with `pushDialog(dialogId, restoreFunction, true)` syntax
  - Debuggable behavior with console logging showing which dialogs close via Esc
  - Easy to enable/disable Esc per dialog for future enhancements

- **📚 Dialog Flow Improvements**
  - **Stats/Results Flow**: Stats → Esc → Closed
  - **Match Controls Statistics Flow**: Controls → Statistics → Esc → Back to Statistics → Esc → Back to Controls → Esc → Closed
  - **Match Controls Completion Flow**: Controls → Match Completion → Edit Statistics → Esc → Back to Completion → Esc → Back to Controls → Esc → Closed

### 🏗️ Architecture Enhancement
- **Consistent Integration**: Uses existing `popDialog()` restoration logic for reliable parent dialog restoration
- **Future-Proof Design**: Foundation for easy Esc enablement in future dialogs
- **Preserved Compatibility**: Existing individual Esc handlers remain unaffected

## v1.5.1 Tournament Celebration & Command Center Enhancement

### Small bug-fix
- The undo dialog was too tall. It now adapts to the number of matches it displays

### ✨ New Feature: Tournament Completion Celebration
- **🏆 Olympic-Style Podium Display**
  - Visual podium showing 1st, 2nd, and 3rd place winners with gold, silver, bronze styling
  - Medal emojis (🥇🥈🥉) and dynamic player names on podium positions
  - Dynamic congratulations message including total player count (e.g., "Congratulations to all 8 players!")

- **🎯 Tournament Highlights Section**
  - Most 180s - Player with most maximum scores
  - Highest Checkout - Best finishing score achieved
  - Shortest Leg - Fastest leg completion (in darts)
  - Responsive 3-column grid layout for key achievements

- **🏆 Tournament Achievements Column**
  - Repurposes referee suggestions column when tournament completes
  - **Player Achievements**: Most Achievement Points, Most 180s, Highest Checkout, Shortest Leg, Most Tons
  - **Tournament Summary**: Total matches, bracket size
  - **Integrated Export**: One-click JSON export directly from celebration

### 🧮 New Scoring System: Achievement Points
- **Most Achievement Points**: Calculates skill-based points excluding placement/participation
  - Rewards pure dart performance: 180s, high outs, short legs, tons
  - Highlights skill mastery vs tournament progression
  - Can recognize players who finish lower but dominated individual achievements

### 🎛️ Match Controls: Complete Tournament Command Center
- **State-Responsive Interface**: Dynamically adapts based on tournament status
  - Active tournaments: Shows matches + referee suggestions
  - Completed tournaments: Shows celebration + achievements + export
- **No More Empty States**: Replaced sad "No matches currently active" with vibrant celebration
- **Enhanced UI Refresh**: Fixed real-time updates when starting/stopping matches in dialog

### 🏗️ Foundation-Respecting Architecture
- **Single Source of Truth**: All celebration data flows from existing tournament logic and transaction history
- **State-Driven Design**: Both match section and referee section check `tournament.status` and rebuild accordingly
- **Clean Container Management**: Follows match section pattern - clear containers first, then populate based on current state
- **No Code Duplication**: Reuses existing functions and follows established architectural patterns

### 🔧 Technical Improvements
- Added tournament status checks for UI state management
- Implemented dynamic column transformation based on tournament completion
- Enhanced dialog refresh logic for real-time state updates
- Proper cleanup and restoration when tournament status changes (e.g., undo operations)

The Match Controls have evolved from a simple match management tool into the true nerve center of the entire tournament experience, providing comprehensive celebration, statistics, and export functionality while maintaining the application's core architectural principles.

---

## v1.5.0 Unified Dialog Stack System

### Major Architecture Improvement
- **Unified Dialog Stack Manager**
  - Implemented comprehensive dialog stacking system with automatic z-index management
  - All dialogs now use consistent `pushDialog()` and `popDialog()` functions for opening and closing
  - Automatic parent dialog hiding and restoration when navigating between nested dialogs
  - Console logging for debugging dialog stack state (`📚 Dialog stack: [...]`)

### Dialog Flow Improvements
- **Statistics Dialog Chain**: Stats/Results → Statistics → Edit Statistics → proper restoration
- **Match Controls Dialog Chain**: Match Controls → Statistics → Edit Statistics → proper restoration
- **Match Completion Dialog Chain**: Match Controls → Match Completion → Edit Statistics → proper restoration
- **Edit Statistics Modal**: Added Esc key support for consistent user experience
- **Event Handler Cleanup**: Fixed duplicate event listeners that caused double-close behavior in nested dialogs

### User Interface Polish
- **Edit Statistics Modal**: Removed confusing "X" close button to encourage use of Cancel/Save buttons
- **Consistent Close Behavior**: All dialog close buttons now use unified dialog stack system
- **Z-index Management**: Proper modal layering (1001, 1002, 1003...) prevents dialogs appearing behind each other

### Technical Improvements
- **Dialog Stack State Management**: Proper cleanup and restoration of dialog states
- **Event Listener Management**: Prevention of duplicate event handlers during dialog restoration
- **Automatic Parent Detection**: Smart dialog restoration without manual parent tracking

# 2025-09-17

## v1.4.6 Tournament Navigation & Help System Improvements

### User Interface Enhancements
- **Tournament Page Navigation**
  - Added "≡ Stats/Results" button to Tournament page upper-left controls for quick access to statistics
  - Repositioned Match Controls to middle row alongside Players/Points for better accessibility
  - Added subtle color guidance: green tint for Match Controls (primary action), amber tint for Generate Bracket (important/caution)
  - Uses existing Statistics modal functionality with cleaner tournament page integration
  - Inconsistent Esc key behavior
  - The Statistics dialog did not update when editing player statistics
- **Visual Consistency Improvements**
  - Added consistent backside match styling to Match Results in Setup page
  - Backside match headers now use darker background (`#d1d5db`) matching Match Controls design
  - Maintains uniform header appearance while preserving visual distinction between frontside/backside matches

### Help System Updates
- **Registration Page Help**
  - Added documentation for Export JSON functionality (results and tournament match history)
  - Added tip about using Export JSON for automated import into external tournament statistics websites
- **Config Page Help**
  - Updated Match Format Configuration descriptions for separate Frontside/Backside Semi-Finals
  - Clarified Backside Final as "Qualifier match for Grand Final"
  - Enhanced confirmation dialog description to explain impact on match result and statistics entry
- **Tournament Page Help**
  - Updated bracket navigation section to include new Stats/Results button

### Bug Fixes
- **Modal Behavior**
  - Added Esc key support to Statistics modal for consistent modal behavior
  - Statistics modal now closes with Esc key like other modals in the application

### Technical Improvements
- **Code Documentation**
  - Streamlined README.md removing duplications and improving focus (reduced from 253 to 108 lines)

# 2025-09-16

## v1.4.5 Match Controls Dialog Behavior Fix

### Bug Fix
- **Match Controls Dialog Persistence**
  - Fixed issue where Match Controls dialog would close and not reopen when confirmation dialogs are disabled
  - Root cause: Command Center reopening logic was only present in confirmation dialog handlers
  - Added same reopening logic to the no-confirmation completion path for consistent behavior
  - Match Controls now properly reopens after match completion regardless of confirmation setting
  - Maintains 500ms delay and cleanup pattern consistent with confirmation path
  - Improves workflow efficiency when using disabled confirmation dialogs

## v1.4.4 Match Undo Ranking Fix

### Bug Fix
- **Undo System Rankings Update**
  - Fixed issue where player rankings were not properly updated after undoing matches
  - Resolved tournament placement persistence bug where stale ranking data remained in localStorage
  - Corrected operation order: now clears placements, recalculates rankings, then saves tournament state
  - Ensures Results Table displays current tournament standings immediately after match undo operations
  - Maintains data integrity between in-memory tournament state and persistent storage

## v1.4.3 System Architecture Documentation & Statistics Enhancement

### Player Statistics Enhancement
- **Dynamic Ranking System**
  - New "Statistics" button in Match Controls, providing direct access to the tournament statistics and editable user statistics without leaving the Tournament page
  - Added real-time player elimination rankings that appear immediately when players are eliminated
  - Rankings display dynamically in results table during tournament play (e.g., "7th-8th", "5th-6th")
  - Clean removal of rankings when matches are undone, maintaining accurate tournament state
  - Integration with existing hardcoded progression logic for bulletproof rank calculations
  - Enhanced user experience showing live tournament standings as play progresses

### Documentation Enhancement
- **Comprehensive Undo System Documentation**
  - Added UNDO.md with complete architectural overview of the surgical undo system
  - Documents the logic behind hardcoded match progression and transaction-based history
  - Explains the surgical vs rebuilding approach for match rollbacks
  - Covers auto-advancement chain handling and error prevention mechanisms
  - Technical reference for maintaining tournament integrity during undo operations

### Architecture Insight
- **Single Sources of Truth Approach**
  - Hardcoded Match Progression (`MATCH_PROGRESSION`) as definitive bracket logic
  - Transaction-based History as chronological state record
  - Surgical state repair vs complete bracket rebuilding
  - Bulletproof data integrity through precise dependency identification

## v1.4.1 Recent Referee Assignments & UI Refinements

### Recent Referee Assignments - Enhancement
- **Added Recent Assignments Section**
  - Third section in referee suggestions showing last 10 referee assignments from transaction history
  - Chronological order with most recent assignments first
  - Same FS/BS color coding as other suggestions (light for FS, darker for BS)
  - Shows assigned referee name with round context (e.g., "John (FS-R2)")

- **UI Refinements**
  - Configurable suggestion limits for better interface management
  - Default reduced to 7 items per section (losers/winners) for less overwhelming display
  - Consistent slice limits across all suggestion categories
  - Transaction-based data ensures reliable referee assignment history

## v1.4.0 Referee Suggestions System & Enhanced Match Controls

### Referee Suggestions System - New Feature
- **Comprehensive Referee Suggestion System**
  - Added intelligent referee suggestions to Match Controls dialog
  - Expanded dialog layout from 800px to 1100px width for two-column design
  - Right column displays up to 10 recent losers first, then up to 10 recent winners
  - Each suggestion shows player name with round context (e.g., "Player Name (FS-R2)")

- **Smart Filtering Logic**
  - Automatically excludes players already assigned as referees
  - Filters out players currently in LIVE matches
  - Removes walkover players from suggestions (not eligible referees)
  - Prevents invalid referee assignments through comprehensive validation

- **Visual Organization & Color Coding**
  - Frontside (FS) players grouped first with light backgrounds
  - Backside (BS) players grouped second with darker backgrounds matching bracket scheme
  - Consistent color coding maintains visual harmony with existing match cards
  - Hover effects provide clear interaction feedback

- **Tournament Flow Integration**
  - Prioritizes eliminated players (losers) as immediately available referees
  - Shows winners with multiple appearances for activity pattern insight
  - Chronological ordering within each group (most recent first)
  - Provides operators comprehensive context for informed referee selection

## v1.3.0 Undo System & Match Controls UX Improvements

### Undo System Enhancement - Major Fix
- **Fixed Undo System Losing Match State**
  - Resolved critical issue where undoing matches would clear LIVE status, lane assignments, and referee assignments from unrelated matches
  - Root cause: Match state changes (start/stop, lane/referee assignments) were not stored as transactions
  - All match state is now properly tracked in transaction history for complete undo safety

- **Enhanced Transaction System**
  - Added `START_MATCH` and `STOP_MATCH` transaction types for match activation/deactivation
  - Added `ASSIGN_LANE` transaction type for lane assignments and changes
  - Added `ASSIGN_REFEREE` transaction type for referee assignments and changes
  - Updated `rebuildBracketFromHistory()` to process all new transaction types
  - Maintains backwards compatibility with existing tournament data

- **Improved Undo Safety**
  - Unrelated LIVE matches now preserve their state during undo operations
  - Lane and referee assignments survive bracket rebuilds
  - Undo operations are now surgical, affecting only progression-related changes
  - Single source of truth principle now applies to ALL match state changes

## v1.2.9 Match Controls UX Improvements

### Match Controls Dialog Enhancement
- **Fixed Match Controls Dialog Refresh Issue**
  - Resolved inconsistent refresh behavior between Frontside and Backside matches
  - Fixed scroll position reset when changing lane/referee assignments
  - Dialog now maintains scroll position during updates instead of jumping to top
  - Improved user experience when managing multiple matches

- **Added Stop Match Button**
  - Added red "Stop Match" button to LIVE match cards in Match Controls dialog
  - Button appears in lower right corner for easy access
  - Allows stopping accidentally started matches without exiting dialog
  - Uses existing `toggleActive()` function to return match to ready state
  - Includes proper CSS styling with hover effects

### Match Results & Export Enhancements
- **Enhanced Match Results Display**
  - Added lane and referee information to Match Results on Setup page
  - Shows "Referee: [Name] • Lane [Number]" format for completed matches
  - Clean display with subtle styling that doesn't interfere with existing layout
  - Backwards compatible with matches that had no lane/referee assignments
  - Proper styling for both regular and walkover matches

- **Enhanced JSON Export**
  - JSON export now includes complete lane and referee data for all matches
  - Lane information exported as `lane: number` field
  - Referee information exported as comprehensive object with `id` and `name`
  - Full data traceability for tournament record keeping and analysis
  - Maintains backwards compatibility with existing export structure

### Technical Improvements
- **Performance Optimization**
  - Improved DOM update efficiency by building HTML strings before setting innerHTML
  - Eliminated redundant function calls during match updates
  - Enhanced scroll position preservation during dialog refreshes

## v1.2.8 Excluded Lanes Configuration & Match Format Update

### Lane Management Enhancement
- **Excluded Lanes Configuration**
  - Added new "Excluded Lanes" field in Config → Lane Management
  - Enter comma-separated lane numbers to exclude from assignment (e.g., "5,7")
  - Excluded lanes appear as "(excluded)" in match lane dropdowns
  - Excluded lanes are grayed out and disabled, matching the existing "(in use)" pattern
  - Input validation ensures excluded lanes don't exceed maximum lane setting
  - Backwards compatible - existing configurations work without excluded lanes
  - Perfect for venues with permanently unusable lanes or temporarily occupied dartboards

- **Enhanced Lane Usage Display**
  - Updated "Show Current Lane Usage" to display excluded lanes information
  - Shows total lanes, excluded lanes, currently in use, and available for assignment
  - Provides comprehensive overview of lane availability status

- **Configuration Management**
  - Excluded lanes saved and loaded with all other global settings
  - Invalid excluded lanes (above max lanes) filtered out with warning message
  - Real-time validation when saving lane configuration

### Match Format Configuration
- **Frontside Semifinal Default Change**
  - Changed default from Best of 5 to Best of 3 for frontside semifinals
  - Provides faster tournament progression and consistent semifinal formatting
  - Affects new tournaments - existing tournaments maintain their current settings

### Technical Implementation
- Enhanced `generateLaneOptions()` to respect excluded lanes in dropdown generation
- Updated `getAvailableLanes()` to filter out both used and excluded lanes
- Modified `saveLaneConfiguration()` in both lane-management.js and results-config.js
- Added `parseExcludedLanesString()` helper function for input validation
- Updated `DEFAULT_CONFIG` to include `excludedLanes` array
- Enhanced `applyConfigToUI()` to populate excluded lanes field from saved configuration

### User Experience Improvements
- Intuitive comma-separated input format for excluded lanes (e.g., "5,7,9")
- Helper text explains the input format clearly
- Lane dropdowns show clear visual distinction between available, in-use, and excluded lanes
- Temporary exclusions easily managed by editing the excluded lanes field
- Maintains physical lane number mapping for clear operational understanding

### Files Modified
- `lane-management.js` - Enhanced lane generation logic and exclusion handling
- `results-config.js` - Updated configuration save/load with excluded lanes support
- `tournament.html` - Added excluded lanes input field to configuration form
- `main.js` - Version bump to 1.2.8

This update enables precise lane management for venues with complex dartboard availability, providing both permanent exclusions for unusable lanes and flexible temporary exclusions for occupied boards.

## v1.2.7 UI Improvements & Match Controls Synchronization

### Dialog Transparency
- Modal dialogs (Match Controls, Statistics, etc.) now have slight transparency (90% opacity)
- Improved visual depth while maintaining readability
- Allows partial visibility of background content

### Match Controls Enhancements
- **Statistics Modal Scrolling Fix**
  - Fixed button visibility issue when adding High Outs or Short Legs while browser is zoomed
  - Statistics form content now scrolls independently while keeping buttons visible at bottom
  - Proper flexbox layout ensures Save/Cancel buttons never get cut off

- **Backside Match Consistency**
  - Backside matches maintain darker background color even when moved to LIVE section
  - Added `cc-match-card-backside` class to preserve visual distinction across all states
  - Consistent color scheme between Ready to Start and Live sections

- **Real-time Synchronization**
  - Lane and Referee changes in tournament bracket now immediately reflect in Match Controls
  - Lane and Referee changes in Match Controls now immediately reflect in tournament bracket
  - Both views stay synchronized regardless of where changes are made
  - Automatic refresh of open modals when data changes

- **Streamlined Live Match Interface**
  - Live matches now show "Player 1 Wins" / "Player 2 Wins" buttons instead of player names
  - Removed redundant separate winner buttons section for cleaner interface
  - Single-click winner selection directly from player area
  - Statistics access removed from live matches (available in Match Completion dialog)

- **Improved Control Layout**
  - Lane and Referee dropdowns now aligned to left for reduced mouse movement
  - Start Match button positioned on right side for ready matches
  - More efficient control grouping and visual hierarchy

- **Enhanced Typography**
  - Round descriptions ("Frontside Round #", "Backside Round #") now displayed in bold
  - "Best of #" format text remains normal weight for clear visual distinction

### Technical Implementation
- Enhanced `createMatchCard()` function to add backside identification classes
- Added bracket refresh logic to `updateMatchLane()` and `updateMatchReferee()` functions
- Improved CSS specificity for modal content transparency and scrolling behavior
- Cross-component state synchronization for seamless user experience

### Files Modified
- `styles.css` - Modal transparency, stats modal scrolling fixes, backside match colors
- `bracket-rendering.js` - Backside class assignment, bracket refresh on updates
- `clean-match-progression.js` - Lane update with bracket refresh
- `main.js` - Version bump to 1.2.7

# 2025-09-15

## v1.2.6 UX Improvements, Match Controls

### Match Controls, Better Separation Between Ready to Start Frontside and Backside Matches
- Backside matches now have darker cards
- This gives a clearer indication of which bracket the Ready to Start matches belong to
- The style of the frontside and backside matches are now aligned with their headline bullets

### Technical Implementation
- CSS Selectors used to give the backside matches a darker color

### Files Modified
- `styles.css` - Added the CSS rule `#backMatchesSection .cc-match-card` for a darker color
- `main.js` - Version bump to 1.2.6

# 2025-09-14

## v1.2.5 - Enhanced JSON Export with Match Results

### Export Functionality Enhancement
- **Match Results in JSON Export**
  - Registration page JSON export now includes complete match history
  - Added `matchResults` section with chronological match data
  - Each match includes player details, winner, final score, and completion timestamp
  - Walkover and auto-completion flags for comprehensive match tracking
  - Maintains existing tournament metadata and player statistics sections

### Technical Implementation
- Enhanced `generateResultsJSON()` function in `results-config.js`
- Made `isWalkoverMatch()` globally available to prevent code duplication
- Match results sorted chronologically (newest first) matching UI display
- Consistent walkover detection logic across display and export functions

### Files Modified
- `results-config.js` - Enhanced JSON generation with match results section
- `main.js` - Made `isWalkoverMatch()` globally available, version bump to 1.2.5

This update provides complete tournament data export in a single JSON file, eliminating the need for separate match results export functionality.

----

## v1.2.4 - Undo System Stability & Rapid-Click Protection

### System Stability Improvements
- **Undo Operation Debouncing**
  - Added 1.5-second debounce protection for undo operations
  - Prevents rapid clicking that could cause tournament state corruption
  - Clear console logging shows when debounce is active/cleared
  - Maintains all sophisticated undo logic while preventing edge case failures

- **Enhanced Rebuild Protection**
  - Dual flag system (`rebuildInProgress` + `autoAdvancementsDisabled`) for comprehensive transaction isolation
  - Optimized protection window from 2000ms to 500ms for better performance
  - Debug logging with stack traces for auto-advancement trigger identification
  - Multiple safety checks throughout rebuild process for bulletproof operation

### Root Cause Resolution
- **Cascading Auto-Advancement Protection**
  - Identified and resolved rapid-click induced auto-advancement cascades
  - Stack trace analysis revealed overlapping rebuild operations as corruption source
  - Defense-in-depth approach maintains system integrity under all usage patterns
  - Normal single undo operations unaffected by stability improvements

### Technical Implementation
- Enhanced `handleSurgicalUndo()` with debounce logic and clear user feedback
- Extended `processAutoAdvancements()` with comprehensive blocking mechanisms
- Optimized `rebuildBracketFromHistory()` protection window for better responsiveness
- Maintained all existing debug capabilities for future troubleshooting

### Files Modified
- `bracket-rendering.js` - Undo debouncing, optimized rebuild protection, enhanced debugging
- `clean-match-progression.js` - Auto-advancement blocking with stack trace logging
- `main.js` - Version bump to 1.2.4

This update resolves tournament state corruption under rapid undo operations while maintaining the sophisticated undo system's precision and reliability for normal tournament management.

----

## v1.2.3 - Enhanced Dialog Interfaces & Tournament Experience

### User Interface Improvements
- **Undo Dialog Round Headers**
  - Enhanced consequential match display with detailed round information
  - FS/BS matches now show "⚪ Frontside - Round 3" format with hyphens
  - Finals display clean format: "BS-FINAL", "GRAND-FINAL" without icons
  - Provides precise context for understanding undo impact

- **Match Controls Dialog Scrollability**
  - Fixed dialog overflow issues in large tournaments (32+ players)
  - Implemented same flexbox layout pattern as undo dialog
  - Fixed title "Match Controls" stays at top, scrollable content fills dialog
  - Close button positioned at bottom, always accessible
  - Consistent user experience across all modal dialogs

- **Walkover Chain Detection**
  - Enhanced consequential match detection to follow walkover progressions
  - Now shows final destination where players actually compete
  - Example: FS-2-8 undo shows "BS-3-2" instead of intermediate walkover "BS-2-4"
  - Provides accurate surgical undo precision for complex tournament scenarios

### Technical Fixes
- **Rebuild Process Optimization**
  - Eliminated duplicate `processAutoAdvancements()` calls during undo rebuild
  - Fixed "completed without winner" states in matches like FS-2-1 (TBD vs TBD)
  - Resolved transaction history corruption during undo operations
  - Maintained perfect bracket state consistency across undo/redo cycles

### Files Modified
- `bracket-rendering.js` - Enhanced undo dialog headers, walkover chain detection, rebuild optimization
- `tournament.html` - Match Controls modal structure with scrollable layout
- `styles.css` - Flexbox layout styling for Match Controls dialog
- `main.js` - Version bump to 1.2.3

This update completes the undo system refinement and provides professional-grade dialog interfaces for tournament management at any scale.

----

# 2025-09-13

## v1.2.2 - Bulletproof Transaction-Based Undo System

### Revolutionary Architectural Change
- **Complete Undo System Redesign**
  - Replaced complex beforeState restoration with clean transaction-history rebuilding
  - Implemented single-source-of-truth approach using transaction history
  - Eliminated all state conflicts and unwanted match re-completions
  - Fixed surgical undo to preserve independent matches correctly

### Core Technical Improvements
- **Transaction-Based History Rebuilding**
  - New `rebuildBracketFromHistory()` function rebuilds entire bracket from clean transaction history
  - Leverages existing hardcoded progression logic for bulletproof reliability
  - Eliminates complex state reconciliation and replay conflicts
  - Ensures bracket state always matches transaction history exactly

- **Enhanced Undoability Logic**
  - Updated `isMatchUndoable()` to use transaction.completionType instead of unreliable match flags
  - Only MANUAL transactions are undoable (prevents AUTO walkover undo attempts)
  - Blocks undo only when downstream MANUAL transactions exist (preserves safety guardrails)
  - Maintains step-by-step undo approach for tournament integrity

- **Tournament Status Management**
  - GRAND-FINAL undo now properly resets tournament status from 'completed' to 'active'
  - Clears final placements to restore live standings display
  - Automatically refreshes Results table to show current tournament progress
  - Prevents incorrect final placement points after undo operations

### User Experience Fixes
- **Surgical Undo Precision**
  - Undoing FS-2-1 no longer affects independently completed FS-2-2
  - Eliminated unwanted match re-completions during undo operations
  - Maintains proper match states after complex undo sequences
  - Preserves tournament integrity with step-by-step undo safety

- **Match State Consistency**
  - Fixed progression application for both MANUAL and AUTO transactions during rebuild
  - Eliminated "TBD vs TBD" states in downstream matches after undo
  - Proper player advancement from all transaction types
  - Consistent bracket state regardless of undo sequence complexity

### Architecture Strengths
- **Single Source of Truth**: Transaction history drives all bracket state
- **Proven Foundation**: Uses existing hardcoded MATCH_PROGRESSION logic
- **Bulletproof Consistency**: Complete rebuild eliminates edge cases
- **Future-Proof Design**: Scales to any bracket size or tournament complexity

- **Debugging and Analysis**
  - Complete audit trail of all match completions preserved
  - Clear distinction between user decisions and system responses
  - Enhanced logging for tournament analysis and troubleshooting
  - Comprehensive match state validation after rebuilds

### Technical Implementation
- Enhanced `completeMatch()` function with `completionType` parameter
- New `undoManualTransaction()` function for bulletproof undo operations
- Complete `rebuildBracketFromHistory()` system for state reconstruction
- Advanced `updateAllMatchStates()` function for proper state validation
- Comprehensive transaction replay system with chronological ordering

### Files Modified
- `clean-match-progression.js` - Added transaction type marking and bulletproof match state validation
- `bracket-rendering.js` - Complete undo system redesign with enhanced dialog interface
- `tournament.html` - Fixed undo dialog font styling and improved modal structure
- `styles.css` - Added enhanced undo dialog styling matching Match Controls interface

### Bug Fixes Resolved
- Eliminated cascade undo failures in complex walkover scenarios
- Fixed matches returning to LIVE state instead of READY after undo
- Resolved "TBD vs Real Player (READY)" impossible match states
- Fixed incomplete player clearance from auto-advanced match chains
- Eliminated dialog display issues with incorrect match identifiers

This represents a fundamental architectural improvement that transforms the undo system from a complex, failure-prone cascade tracker into a bulletproof state reconstruction engine. The system now guarantees perfect tournament consistency regardless of scenario complexity.

---

## v1.2.1 - Enhanced Match Results with Player Progression Info

### Added
- **Player Progression Information**
  - Match results now display where each player advances next or their elimination rank
  - Winners show next match destination (e.g., "FS-2-1", "BS-3-2") or "Tournament Winner!"
  - Losers show either next match they move to or elimination rank (e.g., "7th-8th", "5th-6th")
  - Real-time progression info appears immediately after match completion

- **Enhanced Match Results Layout**
  - Right-aligned match scores with improved visual separation
  - Progression info displayed in italic text within parentheses for subtle emphasis
  - Flexbox layout separates player information from match scores
  - Mobile-responsive design stacks elements vertically on small screens

- **Comprehensive Ranking System Integration**
  - Leverages existing hardcoded tournament progression logic from `MATCH_PROGRESSION`
  - Reuses existing `formatRanking()` function for consistent rank display
  - Maps elimination matches to specific ranks (BS-1-1 → 7th-8th, BS-2-1 → 5th-6th, etc.)
  - Supports all bracket sizes (8, 16, 32 players) with accurate rank assignments

- **Updated Help Documentation**
  - Added "Match Results" section to Setup page help system
  - Documents new progression info display format
  - Maintains consistency with existing help text style and tone

### Technical Implementation
- `getEliminationRankForMatch()` - Maps match IDs to elimination ranks using tournament progression rules
- `getPlayerProgressionForDisplay()` - Extracts progression logic from existing winner confirmation system
- Enhanced `updateMatchHistory()` - Integrates progression info with existing match display
- New CSS classes: `.match-result-enhanced`, `.player-info`, `.result-score`, `.progression-info`
- Zero code duplication - reuses existing `MATCH_PROGRESSION` and `formatRanking()` functions

### User Experience Improvements
- Instant visibility into tournament flow and player standings
- Clear understanding of match consequences before they happen
- Consistent information display matching Match Completion dialog and Results Table
- Improved visual hierarchy with right-aligned scores and italic progression text

### Files Modified
- `main.js` - Added helper functions and enhanced match history display with progression info
- `styles.css` - New flexbox layout with italic progression info styling and mobile responsiveness  
- `dynamic-help-system.js` - Added Match Results documentation to Setup page help

This update transforms the Match Results display into a comprehensive tournament flow indicator, showing not just what happened, but what happens next for each player.

---

# 2025-09-12

## v1.2.0 - Match History Display & Visual Winner Identification

### Added
- **Comprehensive Match History Display**
  - Complete chronological match history in Setup page "Match Results" column
  - Latest completed matches shown at top, earliest at bottom
  - Shows match ID, player names, winner, and final scores when available
  - Real-time updates when matches are completed or when navigating to Setup page
  - Automatic population on page refresh/initial load

- **Visual Winner Identification**  
  - Winner's name highlighted in green (#059669) and bold in "Player vs Player" display
  - Consistent color matching with "Winner: Player" indicator
  - Clear visual hierarchy for instant match result recognition

- **Walkover Match Differentiation**
  - Auto-completed walkover matches displayed with muted/greyed styling
  - Italic text treatment distinguishes walkovers from regular matches
  - Special handling preserves walkover status in visual presentation

- **Match Completion Timestamps**
  - Added `completedAt` timestamp to all match completions
  - Enables accurate chronological sorting of match history
  - Applies to both manual match completions and auto-advanced walkovers

### Technical Implementation
- `updateMatchHistory()` function in main.js for rendering chronological match list
- `isWalkoverMatch()` helper function for consistent walkover detection
- Completion timestamps added to `completeMatch()` in clean-match-progression.js
- CSS styling with `.match-history-item`, `.winner-name`, and walkover variants
- Auto-refresh integration with tournament save operations
- Mobile-responsive design with proper stacking and spacing

### User Experience Improvements  
- Instant visual feedback showing tournament progress and results
- Quick identification of match winners through color-coded names
- Clear distinction between regular matches and administrative walkovers
- No manual refresh needed - history updates automatically as tournament progresses

### Files Modified
- `main.js` - Added match history rendering, winner highlighting, and auto-update integration
- `clean-match-progression.js` - Added completion timestamps and history refresh calls  
- `styles.css` - Match history styling with winner name highlighting and walkover differentiation
- `tournament.html` - Utilizes existing "Match Results" column structure

This update transforms the previously empty "Match Results" column into a comprehensive, real-time tournament activity log with clear visual indicators for match outcomes.

---

## Tournament Setup UX Improvements - Duplicate Prevention & Field Management

### Added
- **Duplicate Tournament Prevention**
  - Validation prevents creating tournaments with identical name AND date combinations
  - Clear error message guides users to choose different name or date
  - Same name with different dates allowed (e.g., weekly tournaments)
  - Different names on same date allowed (multiple tournaments per day)

- **Smart Tournament Field Management**
  - Tournament name field remains empty on page load for clean tournament creation
  - Tournament date field always defaults to today's date
  - Input fields preserve user work during normal navigation between pages
  - Fields automatically clear after successful tournament creation
  - Fields automatically clear after failed creation attempts (duplicates)

- **Tournament Loading Safety**
  - Added confirmation dialog when loading existing tournaments
  - Shows detailed comparison between current and target tournament (name, date, progress, players)
  - Prominent reassurance that no data is lost when switching tournaments
  - Clear information about automatic saving and ability to reload any tournament

- **Enhanced Match Completion Dialog**
  - Shows winner advancement information (which match they progress to, e.g., FS-3-1)
  - Shows loser progression (next match or elimination status)
  - Tournament finals display "wins the tournament!" message
  - Color-coded progression info with visual styling for clarity
  - Improved dialog layout with statistics tip positioned above progression information

### Enhanced
- **Dialog System Improvements**
  - Transformed Match Details dialog from browser alert to rich modal dialog
  - Transformed Undo confirmation dialog from browser confirm to rich modal dialog
  - Both dialogs now feature consistent styling, better readability, and improved UX
  - Added proper focus management with Cancel button as default selection
  - Enhanced visual indicators (box-shadow and scale) for default button choice

- **Setup Page Layout and Navigation**
  - Split Recent Tournaments area into two-column layout with scrollable content areas
  - Left column: Recent Tournaments (maintains existing functionality)
  - Right column: Match Results (prepared for future tournament activity display)
  - Eliminated page-level scrolling - Setup page now fills full browser viewport height
  - Added responsive design: columns stack vertically on mobile devices
  - Moved "Create Tournament" button to the right of the date input field
  - Improved visual alignment and button positioning

- **Registration Page Space Utilization**
  - Implemented sticky footer layout for better vertical space usage
  - Results table now positioned at bottom of viewport when few players are registered
  - Maintains two-column layout (player cards left, results table right)
  - Automatic scrolling when content exceeds viewport height
  - Responsive mobile layout with proper stacking behavior

- **Match Controls System (formerly Match Details)**
  - Transformed simple text-based match listing into interactive Match Controls interface
  - Organized matches into clear sections: LIVE matches first, then Ready matches by bracket side (Front/Back)
  - Added direct match management: start matches, complete matches, assign lanes and referees
  - Replaced single "Complete Match" button with intuitive "[Player Name] Wins" buttons for clear winner selection
  - Auto-refresh: Match Controls updates in real-time after starting matches
  - Smart navigation: cancelling or completing matches returns user to Match Controls interface
  - Consistent functionality: uses same proven tournament logic as bracket interface
  - Updated UI terminology from "Match Details" to "Match Controls" throughout application and help system

### Fixed  
- **Destructive User Behavior Prevention**
  - Eliminated automatic population of tournament name field with active tournament data
  - Prevented accidental duplicate tournament creation due to pre-filled fields
  - Reduced operator-generated failures through better UX design

### Technical Changes
- Added `clearTournamentFields()` helper function for consistent field management
- Enhanced `createTournament()` function with duplicate detection and field clearing
- Modified `autoLoadCurrentTournament()`, `loadSpecificTournament()`, and `importTournament()` to preserve user input during navigation
- Added tournament name/date validation using localStorage `dartsTournaments` array
- Improved Setup page HTML structure with flexbox layout for button positioning

### User Experience Improvements
- Prevents confusion about tournament creation status through clear field states
- Eliminates common user error of creating multiple tournaments with same name/date
- Preserves user work when navigating between pages accidentally
- Provides immediate, clear feedback when tournament creation succeeds or fails
- Creates consistent, predictable behavior for tournament management workflow

### Files Modified
- `tournament.html` - Updated Setup page layout, button positioning, and Match Controls modal structure/titles
- `tournament-management.js` - Added duplicate validation, field clearing logic, and helper functions
- `main.js` - Modified auto-load behavior to preserve user input during navigation
- `bracket-rendering.js` - Implemented Match Controls interface, winner button logic, and auto-refresh functionality
- `clean-match-progression.js` - Enhanced winner confirmation modal with Command Center return navigation
- `styles.css` - Added Match Controls styling with winner button layout and hover effects
- `dynamic-help-system.js` - Updated help documentation for Match Controls functionality

This update significantly reduces operator-generated errors, provides a much more intuitive tournament creation experience, and transforms match management with the new interactive Match Controls system.

---
# 2025-09-11
## Advanced Undo System - Walkover Match Handling & Tournament Completion

### Fixed
- **Walkover Match Undo Corruption** 
  - Resolved critical issue where undoing matches with walkover opponents left players in invalid states
  - Fixed "Walkover vs Real Player (READY)" states that violated tournament integrity
  - Players are now properly removed from auto-advanced walkover match chains during undo operations
  - Walkover matches remain as "Walkover vs TBD" after upstream match undos, preventing illegal game states

- **GRAND-FINAL Undo Tournament Completion**
  - Fixed issue where undoing GRAND-FINAL left tournament in completed state with stale rankings
  - Tournament placements and status now properly reset when GRAND-FINAL is undone
  - Results table correctly clears placement points and rankings after GRAND-FINAL undo
  - Player placement properties are reset to maintain data consistency

### Enhanced
- **Player Matching Logic**
  - Enhanced undo system to match players by name instead of ID during cleanup operations
  - Resolves issues caused by auto-advancement creating new player objects with different IDs
  - Ensures reliable player removal from walkover matches during transaction rollback

- **Tournament State Management**
  - Added `clearTournamentCompletionState()` function for proper tournament state reset
  - Tournament status transitions from "completed" back to "active" when appropriate
  - Comprehensive clearing of placement data across all tournament and player objects

### Technical Changes
- Enhanced `clearPlayerFromDownstream()` to handle walkover matches correctly
- Added name-based player matching in undo operations to handle ID changes from auto-advancement
- Implemented tournament completion state detection and clearing in `undoTransactions()`
- Added `clearedMatches` tracking to prevent restoration of cleared walkover matches
- Enhanced debugging output for walkover match state transitions and tournament completion changes

### User Experience Improvements
- Eliminates invalid tournament states that could confuse organizers and participants
- Provides reliable undo functionality even in complex scenarios with walkover progressions
- Maintains accurate results table that reflects actual tournament state
- Tournament organizers can confidently undo GRAND-FINAL without manually clearing results

### Files Modified
- `clean-match-progression.js` - Enhanced walkover handling, tournament completion state management
- `bracket-rendering.js` - Improved undo validation for auto-advanced matches

This update resolves the final critical issues in the surgical undo system, ensuring robust tournament management regardless of walkover match complexity or tournament completion state.

---
# 2025-09-10

## Enhanced Undo System - Surgical Match Correction

### Added
- **Transactional History System**
  - Replaced snapshot-based undo with transaction-based history tracking
  - Each match completion creates a discrete transaction record
  - Enables targeted undo operations without affecting unrelated matches

- **Surgical Undo Functionality**
  - Undo any completed match that has no downstream dependencies
  - Visual indicators: Winner checkmarks become undo icons (↺) on hover for undoable matches
  - Intelligent validation prevents undos that would break tournament integrity
  - Preserves original bracket assignments while clearing only affected downstream placements

### Enhanced
- **Match State Management**
  - Improved validation to prevent invalid match states (e.g., LIVE matches with TBD players)
  - Better handling of cross-bracket dependencies between frontside and backside
  - Cleaner restoration of match states during undo operations

### Technical Changes
- Implemented `saveTransaction()` for discrete match completion tracking
- Added `undoTransactions()` with recursive downstream clearing
- Enhanced `isMatchUndoable()` validation using progression rule lookups
- Added `clearPlayerFromDownstream()` for precise player removal from affected matches

### User Experience Improvements
- Tournament organizers can now correct errors discovered well after they occurred
- Particularly valuable for 32-player tournaments where mistakes might be found late in the process
- Maintains tournament integrity by preventing undos that would create invalid bracket states
- One-step-at-a-time undo approach provides predictable and safe error correction

### Files Modified
- `clean-match-progression.js` - Core transaction and undo logic implementation
- `bracket-rendering.js` - Enhanced undo validation and visual indicators
- Match progression now uses hardcoded lookup tables for precise state management

This enhancement transforms error correction from a linear "last-match-only" limitation to a flexible system that allows surgical precision in fixing tournament mistakes while maintaining bracket validity.

# 2025-09-09
## Improved Export of Results & Split Semifinal Configuration

### Added
- **Results Exported as JSON**
  - Better for importing into other systems
  - Current CSV is handled poorly in Excel

- **Split Semifinal Configuration**
  - Separate match length settings for frontside and backside semifinals
  - **Frontside Semifinal**: Best of 5 (default) - applies to FS-3-1 (8p), FS-4-1 (16p), FS-5-1 (32p)
  - **Backside Semifinal**: Best of 3 (default) - applies to BS-3-1 (8p), BS-5-1 (16p), BS-7-1 (32p)
  - Auto-save functionality for both new settings
  - Migration support for tournaments with old single "semifinal" setting
 
### Fixed
- **Tournament Import**
  - Bracket rendering failed when importing and loading tournaments
  - Bracket size is now calculated from the tournament JSON file
  
- **Match Generation Error**
  - Fixed "Assignment to constant variable" error in bracket generation
  - Corrected variable naming conflict between string IDs and numeric counters
 
### Technical Changes
- Added two new functions:
  - `exportResultsJSON()`
  - `generateResultsJSON()`
- Added semifinal detection functions:
  - `isFrontsideSemifinal(matchId, bracketSize)`
  - `isBacksideSemifinal(matchId, bracketSize)`

### Files Modified
- `tournament-management.js` - Fixed bracket loading for older tournaments
  - Added `bracketSize` calculation fallback in `loadSpecificTournament()` when property is missing
  - Added `bracketSize` calculation fallback in `processImportedTournament()` for imported tournaments
  - Ensures tournaments without stored `bracketSize` can render complete brackets by calculating from bracket array length

- `results-config.js` - Added JSON export functionality and split semifinal config
  - Added `exportResultsJSON()` function for structured data export
  - Added `generateResultsJSON()` function creating tournament metadata and player results
  - Enhanced export UI with separate JSON and CSV options for different use cases
  - Updated `DEFAULT_CONFIG` to include `frontsideSemifinal` and `backsideSemifinal` settings
  - Added migration logic for old `semifinal` config in `mergeWithDefaults()`
  - Updated config save/load functions to handle split semifinals

- `tournament.html` - Updated export interface and match configuration
  - Modified Registration page to include both "Export JSON" and "Export CSV" buttons
  - Provides users choice between structured data (JSON) for system integration and spreadsheet format (CSV) for Excel analysis
  - Replaced single "Semi-Finals" dropdown with separate "Frontside Semifinal" and "Backside Semifinal" dropdowns in Config page

- `main.js` - Enhanced auto-save functionality
  - Updated `setupConfigAutoSave()` to handle new split semifinal fields
  - Added auto-save listeners for `frontsideSemifinalLegs` and `backsideSemifinalLegs`

- `clean-match-progression.js` - Split semifinal logic and bug fixes
  - Updated `generateFrontsideMatches()` to use `config.legs.frontsideSemifinal` for semifinal matches
  - Updated `generateBacksideMatches()` to use `config.legs.backsideSemifinal` for semifinal matches
  - Added helper functions to detect frontside and backside semifinal matches
  - Fixed variable naming conflict causing "Assignment to constant variable" error
  - Separated string match IDs from numeric counters in match generation

### User Experience Improvements
- Tournament organizers can now set different match lengths for frontside vs backside semifinals
- More granular control over tournament pacing and format
- Backward compatibility maintained - existing tournaments load normally with migrated settings
- JSON export provides better data structure for external analysis tools

### Bug Fixes
- Resolved bracket generation crash when creating tournaments with split semifinal configuration
- Fixed tournament import/loading issues for tournaments missing bracketSize property
- Improved error handling in match generation process

These changes provide enhanced tournament configuration flexibility while maintaining system stability and backward compatibility.

# 2025-09-07
## Enhanced Referee Assignment System & UI Improvements

### Added
- **Intelligent Referee Assignment System**
  - Alphabetical sorting of all paid players in referee dropdowns
  - Conflict detection preventing double-assignment of referees
  - Visual indicators for unavailable referees:
    - "(assigned)" for referees already assigned to other matches
    - "(playing)" for players currently in live matches
  - Real-time dropdown updates when match states change
  - Integration with existing lane management conflict detection system

### Changed
- **Enhanced Dropdown Usability**
  - Increased referee dropdown font size for better readability
  - Expanded referee dropdown width to accommodate longer names
  - Increased lane dropdown font size for consistency
  - Expanded lane dropdown width for "(in use)" labels
  
- **Improved Match Card Layout**
  - Expanded match card dimensions
  - Increased player name font size for better visibility
  - Expanded player name max-width to utilize available space
  - Better accommodation for winner checkmarks and longer player names

- **Referee System Integration**
  - Modified `toggleActiveWithLaneValidation()` to refresh both lane and referee dropdowns
  - Enhanced `updateMatchReferee()` with conflict validation and error handling
  - Automatic dropdown refresh when referee assignments change

### Technical Changes
- Added referee conflict detection functions to `lane-management.js`:
  - `getAssignedReferees(excludeMatchId)` - tracks current referee assignments
  - `getPlayersInLiveMatches(excludeMatchId)` - identifies players in active matches
  - `isPlayerAvailableAsReferee(playerId, excludeMatchId)` - availability validation
  - `refreshAllRefereeDropdowns()` - updates all referee dropdowns system-wide
  - `generateRefereeOptionsWithConflicts()` - creates conflict-aware dropdown options
- Enhanced `updateMatchReferee()` in `bracket-rendering.js` with validation and error handling
- Updated `renderMatch()` to use new referee dropdown generation with conflict detection
- Modified CSS `.player-name-short` and `.bracket-match` classes for improved readability

### Files Modified
- `lane-management.js` - Added complete referee conflict detection system
- `bracket-rendering.js` - Enhanced referee dropdown integration and validation
- `styles.css` - Updated match card dimensions and player name styling

### User Experience Improvements
- Referees can no longer be double-assigned across matches
- Clear visual feedback when referee assignments conflict
- Much improved readability of match card text and dropdowns
- Consistent styling between lane and referee assignment systems
- Automatic prevention of assigning players who are currently playing as referees

### Bug Fixes
- Resolved referee dropdown function loading order issues
- Fixed missing function exports causing console errors
- Ensured proper integration between lane and referee management systems
- Problems with loading number of lanes from config

# 2025-09-06
## Enhanced Match Validation & Dynamic Help System

### Added
- **Enhanced Match Result Validation**
  - Real-time validation for leg scores in winner confirmation dialog
  - Core requirement: Winner must have more legs than loser
  - Smart validation against match format (Bo3/5/7) with flexibility
  - Visual feedback with red validation messages
  - Disabled confirm button for invalid inputs
  - Pre-filled winner legs based on match format, loser defaults to 0
  - Input sanitization preventing negative numbers

- **Dynamic Help System**
  - Context-aware help for all pages (Setup, Registration, Tournament, Config)
  - Floating, draggable help modal that doesn't interfere with workflow
  - Progressive disclosure with expandable help sections
  - Smart suggestions based on current tournament state
  - Keyboard shortcuts: F1 (toggle help), ESC (close), Ctrl+H (toggle)
  - Auto-detection of first-time users with welcome help
  - Contextual hints appearing based on user actions:
    - "Need more paid players" when < 4 players
    - "Ready to generate bracket" when enough players added
    - "Matches ready to start" when bracket is generated
    - "Tournament completed" celebration when Grand Final ends
  - Quick action buttons in help panel relevant to current context
  - Comprehensive help content covering all application features
  - Troubleshooting section for common issues

### Changed
- **Enhanced Winner Confirmation Dialog**
  - Added leg score input fields with validation
  - Improved visual layout with better user guidance
  - Enhanced error handling and user feedback

- **Tournament Management Functions**
  - `createTournament()` now triggers help hints for new users
  - `generateCleanBracket()` provides contextual guidance
  - `addPlayer()` and `togglePaid()` show progress hints toward minimum player count
  - `completeMatch()` celebrates first match completion
  - All winner selection functions now use enhanced validation

- **User Interface**
  - Help buttons (?) added to all page headers
  - Improved modal styling and accessibility
  - Better visual feedback for form validation states

### Technical Changes
- Added `validateLegScores()` function with comprehensive validation rules
- Added `updateValidationDisplay()` for real-time feedback
- Added `showValidationError()` for fallback error handling
- Added `dynamic-help-system.js` with complete help infrastructure
- Enhanced global function exports for help system integration
- Added contextual help detection and suggestion system
- Integrated help hooks throughout existing tournament management functions

### Files Modified
- `clean-match-progression.js` - Enhanced winner confirmation with validation
- `tournament-management.js` - Added help integration hooks
- `player-management.js` - Added help hints for player management
- `main.js` - Enhanced page navigation with help integration
- `tournament.html` - Updated winner confirmation modal, added help system scripts
- `styles.css` - Added help system and validation styling

### Files Added
- `dynamic-help-system.js` - Complete dynamic help system implementation

### Bug Fixes
- Fixed help button positioning on Registration and Config pages
- Improved modal z-index handling for better UX
- Enhanced input validation preventing invalid match results

# 2025-09-05

## Leg Tracking System Implementation
### Core Features Added:

- Added leg score inputs to winner confirmation dialog (tournament.html)
- Implemented leg score storage on match objects (`match.finalScore`)
- Added leg calculation function to sum scores from completed matches
- Updated results table to display Legs Won/Legs Lost columns
- Included leg data in CSV export functionality

### Undo System Enhancement:

- Modified undo system to preserve all player statistics during match rollbacks
 - Match-related data (progression, leg scores) gets undone with match results
- Performance statistics (tons, 180s, short legs, high outs) persist through undo operations
- Fixed player data restoration to only restore tournament and match state

### UI Improvements:

- Enhanced winner confirmation dialog with optional leg score entry
- Pre-fills winner's minimum legs based on match format (Bo3=2, Bo5=3, Bo7=4)
- Real-time results table updates after each match completion
- Added legs won/lost columns to both display table and CSV export

### Technical Implementation:

- Leg scores stored as `{winnerLegs, loserLegs, winnerId, loserId}` on match object
- Calculation function iterates through completed matches to sum player leg totals
- Undo system preserves player stats while reverting match progression
- Auto-refresh of results table after match completion

### Data Architecture:

- Match-level storage for legs (tied to match lifecycle)
- Player-level storage for performance stats (persistent across undo operations)
- Clean separation between match results and player achievements

# What happened before this?

- Everything else, essentially...
- In essence, all that needed to be done for the entire app framework. Just that it wasn't particularly useful or polished, nor was it especially stable (which is the main selling-point of the whole thing)