AMYboard release tags

[bwhitman]

We want to eventually ship multiple firmwares for AMYboard, a dev version for recent development that may have more bugs, and a release version that has had more testing. That's not too hard on its own - we could have ./release.sh take a release_tag parameter and make sure the firmware updaters know which one to use. But the webapp and the firmware are linked in code, a dev firmware may require a dev webapp as well. We could have a separate dev website like amyboard.com/editor-dev , or we could also have the webapp detect the tag of the current firmware on first "pull" (syncing) and set the parameter and code path there. A nice upside of detecting on sync is that we could also alert the user if their firmware is out of date (no matter what tag they were on)

[bwhitman]

Implemented: dev / release channels via a separate dev site

Went with the "separate dev website" option, implemented as its own Vercel project on a subdomain (rather than a amyboard.com/editor-dev path):

• release → https://amyboard.com — flashes the real GitHub release (releases/latest)
• dev → https://amyboard-dev.vercel.app — flashes a rolling GitHub prerelease tagged dev

The flasher picks its channel from the hostname of the site it's served on, so the dev site only ever flashes dev firmware and amyboard.com only ever flashes the release. The same web artifact is deployed to both; only the hostname differs.

Already live

• amyboard-dev.vercel.app is up and serving the channel-aware flasher.
• The dev prerelease exists with amyboard-firmware/full/sys-AMYBOARD.bin. It's flagged prerelease, so it does not become releases/latest — the release channel (currently v-may-2026) is unaffected. Verified: dev .bin fetches through the dev site's proxy with a 200.

For collaborators

Publish a dev build — from tulip/, with the ESP-IDF env active (see CLAUDE.md):

./dev.sh            # firmware + web
./dev.sh firmware   # only build + upload the dev .bin
./dev.sh web        # only build + deploy the dev site

• firmware → builds AMYboard and uploads the three bins to the dev prerelease (created on first run, --clobbered after).
• web → builds amyboardweb/stage/ (python3 dev.py --build-only) and deploys to the amyboard-dev Vercel project (--prod).

Channel resolution (tulip/amyboardweb/static/esptool/js/script.js):

• amyboard.com → release
• any host containing amyboard-dev → dev
• localhost → dev
• anything else → release (safe default)
• ?channel=dev|release overrides for testing (honored on the flasher page or the parent editor page)

Download bases:

• release: https://github.com/shorepine/tulipcc/releases/latest/download/…
• dev: https://github.com/shorepine/tulipcc/releases/download/dev/…

Promote dev → release (unchanged from today):

./release.sh v-XXX-2026 upload     # firmware → becomes releases/latest
cd amyboardweb && ./deploy.sh      # web → amyboard.com

Files

• tulip/dev.sh (new)
• tulip/amyboardweb/static/esptool/js/script.js — channel resolver + per-channel URLs + dev badge
• tulip/amyboardweb/static/esptool/index.html — data-url → data-bin, badge element
• tulip/amyboardweb/static/esptool/css/style.css — .channel-badge
• tulip/amyboardweb/dev.py — --build-only flag
• AGENTS.md / CLAUDE.md — new "AMYboard Dev Channel" section

Not done / open

• Sync-time tag detection (the third option in the description) is not implemented. The channel is decided by the site, not by the connected board's firmware tag — so there's no "your firmware is out of date" alert yet, and syncing doesn't auto-select a channel. That's the natural follow-up if we want the out-of-date nudge regardless of which tag the user is on.
• Vercel auto-URL caveat: the per-deploy hash URL came out as amyboard-<hash> (Vercel dropped the -dev), so only the stable amyboard-dev.vercel.app alias resolves to dev; raw per-deployment hash URLs fall back to release. If we want it bulletproof regardless of URL, we'd switch from hostname-detection to a build-time channel stamp written only by dev.sh.

Status

The live endpoints above are already up, but the source changes are still pending merge to main (currently on a local working tree). Once merged, ./dev.sh and the channel-aware flasher source will be available to everyone.