style: refine the ASCII homepage and mobile layout

[LIghtJUNction]

Changes

• Keep the existing ASCII renderer and all four scenes. Replace the blue-black card with an open monochrome stage, clearer headline spacing and a single row of bilingual scene controls.
• Put copy and links before the art in reading order. Keep the art viewport stable when switching scenes. Use a quieter account row instead of the large filled account card.
• Redraw paused character art when the theme changes. Honor the hidden state when the vendor renderer sets an inline display style, so the shared SVG and canvas cannot overlap.
• Preserve public-board editing, local drafts, keyboard access, reduced-motion behavior and the no-JavaScript image fallback. No new frontend dependencies or authentication changes.

Verification

Verified the exact source against main fab1772f2c35deeba99af33c639dd8dccc730d1e in ASCII home verification:

• Baseline: 37 tests passed. The new markup regression failed on the original source, then passed with the change.
• Updated source: 129 related Python tests passed, with no failures or skips.
• Actual Chromium rendering under the page CSP: 320, 360, 390, 768 and 1440 pixels, each in light and dark mode. Checked overflow, stable scene positions, keyboard and touch selection, theme changes while still, menu/editor access, draft preservation, custom SVG, long content and guest access.
• Animation/pause and no-JavaScript fallback passed. The existing first-read browser checks also passed.
• Ruff, compilation, whitespace checks and reproducible Bun 1.4.0 asset generation passed.

The ascii-home-verification artifact contains rendered screenshots, synthetic HTML fixtures, test XML and source evidence. These are browser-emulation checks, not physical-phone acceptance.

The existing browser workflow now runs these checks on future relevant changes. The temporary source-transfer workflow and patch are not included in this PR. Not merged or deployed.

[chatgpt-codex-connector]

You have reached your Codex usage limits for security reviews. Please try again later.

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.