The route is gone. Clear the 404 wall or return home.
Move the paddle, launch the ball, and clear all 30 bricks.
LEFTAMOVERIGHTDMOVESPACELAUNCHPPAUSEBrick Breaker is ready to start.
The component does not set an HTTP status on an ordinary route. Next.js supplies
the 404 response when it is used from app/not-found.tsx.
Keyboard handling is scoped to the focused playfield. Pointer capture and
touch-action are limited to the playfield rather than the whole page.
The 30 bricks form a pixel 404. Each brick scores 10 points and clearing the
wall adds a 104-point route bonus, so a successful run ends at exactly 404.
The canvas is supplementary. The 404 heading, score, lives, phase, instructions, buttons, announcements, and permanent Home link remain ordinary DOM content. The game starts only after an explicit action, pauses when the page becomes hidden, and removes decorative effects when reduced motion is requested.
