fix(webapp): small things from the 4.5.1-rc1 render check (#1175) #1176

Merged
claude-bot merged 3 commits from fix/1175-render-check-findings into main 2026-10-13 18:29:35 +00:00
Collaborator

Closes #1175.

  1. The roster count is about players and says so. On the session page: "N of M players have answered"; "No players have answered yet." when the reader has answered and no player has; no count and no "nobody" line in a campaign with no players. Frontend only (pages/session/confirmed.js, AreYouIn.jsx). This week's inline count is unchanged: it counts everybody and matches its rows.
  2. Map at phone width. The map-level breadcrumb buttons and the marker panel's Close button get a 24 px minimum target (Map.css), with no change at desktop. See "Not confirmed" below.
  3. /favicon.ico serves the icon, not the app's HTML (nginx.conf, an exact-match location onto /favicon.png).
  4. The remind button's refusals say what is true. A bot that does not list the nudge feature: 409 "The bot is an older version and cannot post this yet. Ask whoever runs Quest Board to update it." A bot whose features are unknown because it is not answering: 503 "The bot is not answering. Try again in a minute." Before, both read "The bot needs updating…". With backend and bot at the same release the first cannot show (BOT_FEATURES lists rsvp_nudge).

No bot API contract change, no migration.

Verified

On docker-test: vitest for src/components/session, src/pages/session, src/pages/wiki/Map* (561 passed); test_rsvp_nudge.py and test_nginx_upload_limit.py (41); ruff; frontend lint; changelog check. A frontend-prod build served /favicon.ico as image/png, the same bytes as /favicon.png, with the CSP and the other security headers.

Not confirmed

Item 2. The a11y journey for the wiki pages, which includes the map, passed on the phone project before the fix, and there is no baseline allowance for it. The violation was seen once, in the render check, on a map whose test markers had been placed on top of one another at one corner; overlapping targets fail target-size by themselves, so it may never have been a defect in the page. The two CSS changes are the controls that measured under 24 px on reading the code, and are harmless either way. Not re-run after the fix.

This PR touches no journey, so it is also the first real run of the desktop-only path from #1174.

🤖 Generated with Claude Code

Closes #1175. 1. **The roster count is about players and says so.** On the session page: "N of M players have answered"; "No players have answered yet." when the reader has answered and no player has; no count and no "nobody" line in a campaign with no players. Frontend only (`pages/session/confirmed.js`, `AreYouIn.jsx`). This week's inline count is unchanged: it counts everybody and matches its rows. 2. **Map at phone width.** The map-level breadcrumb buttons and the marker panel's Close button get a 24 px minimum target (`Map.css`), with no change at desktop. See "Not confirmed" below. 3. **`/favicon.ico` serves the icon**, not the app's HTML (`nginx.conf`, an exact-match location onto `/favicon.png`). 4. **The remind button's refusals say what is true.** A bot that does not list the nudge feature: 409 "The bot is an older version and cannot post this yet. Ask whoever runs Quest Board to update it." A bot whose features are unknown because it is not answering: 503 "The bot is not answering. Try again in a minute." Before, both read "The bot needs updating…". With backend and bot at the same release the first cannot show (`BOT_FEATURES` lists `rsvp_nudge`). No bot API contract change, no migration. ## Verified On `docker-test`: vitest for `src/components/session`, `src/pages/session`, `src/pages/wiki/Map*` (561 passed); `test_rsvp_nudge.py` and `test_nginx_upload_limit.py` (41); ruff; frontend lint; changelog check. A `frontend-prod` build served `/favicon.ico` as `image/png`, the same bytes as `/favicon.png`, with the CSP and the other security headers. ## Not confirmed Item 2. The a11y journey for the wiki pages, which includes the map, passed on the phone project **before** the fix, and there is no baseline allowance for it. The violation was seen once, in the render check, on a map whose test markers had been placed on top of one another at one corner; overlapping targets fail `target-size` by themselves, so it may never have been a defect in the page. The two CSS changes are the controls that measured under 24 px on reading the code, and are harmless either way. Not re-run after the fix. This PR touches no journey, so it is also the first real run of the desktop-only path from #1174. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
fix(webapp): map breadcrumb and Close targets are 24px (#1175)
All checks were successful
CI / Which journeys does this change need? (pull_request) Successful in 15s
CI / Does this change touch the recording path? (pull_request) Successful in 15s
CI / Synthetic session harness (no GPU, no LLM) (pull_request) Has been skipped
CI / Bot/backend version sync (pull_request) Successful in 27s
CI / Feedback site tests (pull_request) Successful in 40s
CI / Backend lint (ruff) (pull_request) Successful in 1m1s
CI / Summarisation accuracy eval harness (stub provider) (pull_request) Successful in 1m48s
CI / Docker image build (pull_request) Successful in 2m25s
CI / Bot tests and audit (pull_request) Successful in 3m10s
CI / Frontend (shard 2/2) (pull_request) Successful in 9m57s
CI / Frontend (shard 1/2) (pull_request) Successful in 12m30s
CI / End-to-end journeys (phone) (phone) (pull_request) Successful in 11m18s
CI / End-to-end journeys (keyboard) (keyboard) (pull_request) Successful in 12m19s
CI / End-to-end journeys (desktop) (desktop) (pull_request) Successful in 12m28s
CI / Backend migration, tests, and audit (pull_request) Successful in 38m43s
077c1e74e0
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
claude-bot scheduled this pull request to auto merge when all checks succeed 2026-10-13 17:50:51 +00:00
claude-bot deleted branch fix/1175-render-check-findings 2026-10-13 18:29:35 +00:00
Sign in to join this conversation.
No description provided.