1.0.8

• Reuse existing Bootstrap utilities for game layout and remove redundant custom positioning styles while preserving gameplay and desktop/mobile appearance. (#36)
• Serve the existing baseball favicon as PNG with the correct MIME type and use the shared image path in production and browser-test builds. (#36)
• Clarify code comments and streamline repository guidance without changing runtime behavior. (#33, #34, #35)

Validation:

• Build and all 91 tests passed in the pinned Node 24 deployment container; Firebase was disconnected during these checks. ESLint and Prettier passed for the same source, and merged main CodeQL succeeded.
• All 11 public assets match the validated production build byte-for-byte. JavaScript/CSS cache identifiers and the PNG favicon MIME type are correct.
• Production verification covered 1440px, 390px and 320px widths, sequential guest allocation, weekly/all-time rankings, Google-authenticated gameplay, guest gameplay, batting and upward ball reflection, three-out completion, finishing without saving, retry with the same guest number and reset score/counts, and one guest score save with ranking reflection.
• No horizontal page overflow or browser console errors/warnings were observed.

Live Firestore checks were explicitly authorized and limited to one page load: three ranking-fetch batches (12 query invocations), one guest allocation transaction, and one guest score save. There was no polling or repeated page reload. These counts describe application operations; billed document reads and SDK transport requests were not instrumented.

One normal guest-play record (guest 741, 0 points) was saved for verification. Authenticated score overwrite and deletion were not exercised in production; their contracts passed Firebase-mocked tests.

Release commit: ec06963903ce1f0927db746e85faceab5d3c3307.
Deployed site: https://baseballgames.jp.net/