Make script releases and deployments traceable #139

What

It's unclear which script version runs where, and how to move from one version to the next.

• GitHub shows no record of what is deployed to the CDN or custom domains, or when. Today latest.js, light.js and hello.js on the CDN match the 2023 v11 tag, while auto-events.js matches a 2026-08-17 build on main.
• There's no point-in-time build to download for a version.
• dist/ is committed, so branches that rebuild it conflict with each other, and agents have to restore it before each commit.
• main's dist/v11/app.js no longer matches the published, immutable sri/v11.js.

Why

Deploys change the scripts on every customer site. We need a clear path from version X to Y, a way to see what is live, and rollbacks that don't depend on someone's local checkout.

Notes

Deploys stay a manual step from the maintainer's laptop (Bunny CDN and Caddy credentials live there).