ScreenTinker 29ae184b14 Add an opt-in browser smoke test ... A whole class of defect found today was invisible to the unit suite, to a syntax check and to review, and appeared only in front of a browser: a context menu whose only item read "schedule.ctx_new", pointer handlers stacking on every calendar render so one drop fired five PUTs, and a week grid that scrolled sideways on a phone. Nothing in the repo could have caught any of them. This keeps the checks that earned their place and throws away the scratch scripts around them. It boots a server, drives every view, and asserts each view renders, none raises an uncaught error, no untranslated key reaches the screen, the calendar binds its handlers once however many times it re-renders, and nothing overflows horizontally at phone width. Deliberately NOT part of `npm test`. It needs a real browser, which CI does not have, so it is `npm run smoke` and exits 0 with an explanation when puppeteer or Chrome is missing — a test that fails for want of tooling teaches people to ignore failures. puppeteer-core rather than puppeteer, so installing it does not pull down a private copy of Chrome; it drives whichever one is already there. Verified both ways: 32/32 against current main, and it fails on the listener stacking when that fix is reverted. The missing-key case is covered by the unit guard instead, since a context menu only exists once it has been opened. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Uaeo9MvzKoyXuN6ZsbhtkL		2026-07-28 20:17:59 -05:00
..
ui-smoke.js	Add an opt-in browser smoke test	2026-07-28 20:17:59 -05:00