Browser verification

Build and start the real server. Test at desktop width and390×844, and resize a mobile docs page to desktop.

• Home: increase/decrease/undo counter; copy install command; navigate to Framework, Documentation and Playground. No horizontal page overflow.
• Home code examples: switch app/page/services tabs using click and ArrowLeft/ArrowRight/Home/End; only the selected panel is visible and focus follows keyboard selection. Explore the architecture scrolls to the layer diagram.
• Documentation: search middleware, open a result, search a nonsense word, clear with Escape; open category and heading anchors; copy a code sample. Mobile Browse documentation opens. On widening, the complete guide navigation is visible.
• Playground: run state with and without undo; middleware { "value":4,"multiplier":3,"add":2 } produces14 and ordered trace; invalid form shows name/email errors; valid form isValid=true; DI singleton shares across requests, scoped shares only within a request, transient shares neither. Invalid JSON and scope display actionable errors. Reset restores defaults.
• Keyboard: visible focus, skip link, Enter/Space buttons, arrows/Home/End for example tabs, / focuses docs search. Mobile navigation opens and Escape closes.
• Without JavaScript: primary navigation and guides remain visible; examples show readable source, disabled controls and guidance. If the Node endpoint is absent, the DI example reports failure and recovers on the next run.
• Inspect home, features, docs and playground at both widths; check console for unexpected errors. Keep outputs unmodified; no browser-injected substitutes for real framework behavior.