ScreenTinker fbec5767c1 ci: run the node:sqlite job against the full tree, not a pruned one ... The job as first written installed with --omit=optional, reasoning that a player has no native module. It failed immediately with sixty "Cannot find module 'better-sqlite3'" errors — because the TESTS require it directly, as a harness to inspect the database they are making assertions about. Pruning it tested nothing but the test files. Installing everything and forcing ST_SQLITE_DRIVER=node is also the stronger check: the server under test runs on node:sqlite while the harness reads the same database files with the native driver, so a divergence between the two surfaces as a failing assertion rather than as one driver agreeing with itself. This is the configuration that was actually verified locally — 1762 pass / 0 fail on both drivers. The pruned variant was written afterwards and never run before pushing. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_014kfhrUPit5MCqxeTQyqr56		2026-08-18 21:07:38 -05:00
..
workflows	ci: run the node:sqlite job against the full tree, not a pruned one	2026-08-18 21:07:38 -05:00