README: where the lab is deployed and how CI publishes it
1 changed file+4−0
README.mdmodified+4−0View file
@@ -73,6 +73,10 @@ Two exports, both written by the browser itself with no server and no bundled en
7373
7474 The recording is real time, which is what using nothing but the platform costs: a three-second movie takes three seconds to write, the tab has to stay in front, and a machine that cannot keep up drops frames rather than slowing down (the lab says how many of the run's frames it drew). Below real time the picture and the sound are slowed together, so the sound drops in pitch as a tape would. A run whose frames would need more than about sixty a second cannot have all of them drawn at real time, and the lab says so and offers the slower speeds.
7575
76+## The live app
77+
78+The lab is deployed at <https://plate-dynamics-lab.vault1-sites.magland.org/>. `.mochi/workflows/deploy.yml` typechecks, runs the tests and builds `apps/lab` on every push to `main`, then publishes it; a regression in the tests stops the deployment. The site sits at the root of an origin of its own, which the repository's site label gives it, so the build's base path comes from `configure-pages` rather than being written into the Vite config. Having its own origin also lets the page use `localStorage`, which is where the lab keeps your settings and your source edits: a site served under the forge's own host is sandboxed, and reading storage there throws.
79+
7680 ## Running
7781
7882 ```bash