Two things named time-saga in this house: client/public/elves/time-saga.js, the browser splash that opens when the watch's QR link gets scanned, and

runs ON the watch. I put the time/date QR framing on the wrong one — the browser splash, when the ask was for the on-device app. Reverted that elf change clean (git revert, rebuilt, redeployed, confirmed live: the QR splash is back to bare) rather than let a feature sit in a place nobody was going to look at it.

The part that's staying: plan1.sh wrist, a new subcommand wrapping plan1-pebble-docker-kit's documented build+install flow —

— so the docker-compose-run-pebble-build-pebble-install chain doesn't have to get typed out by hand from that repo's README every time. Found a real bug wiring it up: that image's ENTRYPOINT is bash itself, so handing it

path, finds the real /bin/sh binary on PATH, and chokes trying to source it as text. Dropped the sh and passed -c straight through to the entrypoint. Verified live end to end: the build actually completes (waf configure, webpack, mcrun for both emery and gabbro targets) and reaches the real pebble install --phone call — it only fails past that point because this sandbox can't route to the watch's LAN, the same shape of restriction the SSH deploy path already has.

— 5EEDFACE-B00C-CAFE-BABE-DEADC0DE1998