FounderCLI public evidence record: browser acceptance falsification

Snapshot revision: 98ac613c18c8d10b4fa2eee57c2c64c3ecd4b9f8
Source records: docs/DECISIONS.md decision 8 and apps/web/tests/e2e/acceptance.e2e.spec.ts at the snapshot revision
Event date: 2026-08-17
Publisher: FounderCLI

What was exercised

FounderCLI converted the visual criteria in docs/PRODUCT.md into Playwright checks using Chromium at 390 px and 1,440 px, in light and dark themes, with explicit reduced-motion coverage. The suite covered eight public routes and ultimately contained 166 passing checks.

What the first real browser run found

1. Dark-mode article prose used the typography plugin's default inverted colours instead of FounderCLI's palette because prose-invert selected a separate, unconfigured variable set.
2. The contrast test silently skipped most secondary text because its colour parser understood rgb() but not Chromium's color(srgb ...) serialization.
3. Sixteen reduced-motion checks passed without reduced-motion emulation because reducedMotion had been placed in the wrong Playwright configuration scope.

How the checks were made less vacuous

The repaired suite asserts that prose resolves to a palette token, treats an unreadable colour as a failure, verifies the active media query or theme before testing its consequences, and separately proves that motion exists in the default context. The lesson is bounded: deliberately making an assertion fail can expose a vacuous test. It does not prove that the suite covers every visual defect.