[P2] Fix demo correctness and add lazy, visual, and accessibility regression checks

[Banegasn]

Objective

Turn the Angular site into a lightweight, trustworthy consumer integration test and component showcase.

Evidence

• app.routes.ts declares progress twice; the first entry has the wrong Divider title/description.
• All page components are eagerly imported, contributing to a 731.17 kB initial bundle against a 500 kB budget (46% over).
• Four component stylesheets exceed configured budgets, including home by 3.39 kB.
• Screenshot automation scrapes README HTML from the live CDN, suppresses page errors, and reaches into tooltip private state, so it can report success without testing the current workspace artifact.
• The demo build emits repeated SSR/localStorage warnings.

Scope

• Remove route/metadata duplication and add route metadata tests.
• Lazy-load component pages and analyze shared dependencies/bundle budgets.
• Make demo examples derive from or validate against package docs/APIs.
• Replace private-state/CDN screenshot hacks with workspace-built public-API fixtures.
• Add deterministic Playwright visual snapshots and axe scans for light/dark/reduced-motion/responsive modes.
• Fail on page errors and broken custom-element registration.

Acceptance criteria

• Every route is unique and has correct title/description metadata.
• Initial bundle is within an intentional documented budget.
• Demo screenshots use local packed/built packages and public APIs only.
• Console/page errors fail the regression suite.
• Representative pages pass visual and automated accessibility checks across themes/viewports.
• SSR/prerender warnings are removed or explicitly justified.

Dependencies

Blocked by the toolchain/CI foundation. Visual baselines should be captured after token/motion defaults stabilize.

Autonomous execution contract

Keep the demo a consumer of package public APIs; never import package internals to make tests pass.