Rename .cofferdam to .mochi
3 changed files+5−5
.cofferdam/workflows/deploy.yml →.mochi/workflows/deploy.ymlrenamed+1−1View file
@@ -1,7 +1,7 @@
11 # Build the page and publish it as this repository's site, on every push to
22 # main. The site lands at /tutorials/laplace-dirichlet/site/.
33 #
4-# Two cofferdam-specific points. `actions/cache` is not implemented, so
4+# Two mochi-specific points. `actions/cache` is not implemented, so
55 # `setup-node` must not be given `cache: npm`; the install is done cold every
66 # run. And the site is served from a sub-path rather than a domain root, which
77 # is why vite.config.ts sets `base: './'` — the build emits relative URLs and
CLAUDE.mdmodified+3−3View file
@@ -202,7 +202,7 @@ coarser but needs no extra script.
202202
203203 ## Deployment
204204
205-`.cofferdam/workflows/deploy.yml` runs on every push to `main`: `npm ci`,
205+`.mochi/workflows/deploy.yml` runs on every push to `main`: `npm ci`,
206206 `npm run build`, then `upload-pages-artifact` and `deploy-pages`, which the
207207 vault substitutes with its own implementations to publish the repository's
208208 site. Two constraints shape it. `actions/cache` is not implemented in the
@@ -211,8 +211,8 @@ served sandboxed, in an opaque origin, so `localStorage` and friends *throw*;
211211 the app uses none, and adding one would break the deployed page while working
212212 perfectly in `npm run dev`.
213213
214-Watch a deploy with `cofferdam run list --limit 3 --json` and
215-`cofferdam run view <n> --log`.
214+Watch a deploy with `mochi run list --limit 3 --json` and
215+`mochi run view <n> --log`.
216216
217217 ## Plotting
218218
README.mdmodified+1−1View file
@@ -124,7 +124,7 @@ numbl performance rules that the drivers are written around.
124124
125125 ## Deployment
126126
127-`.cofferdam/workflows/deploy.yml` builds the page on every push to `main` and
127+`.mochi/workflows/deploy.yml` builds the page on every push to `main` and
128128 publishes it as the repository's site on the vault, at
129129 `/tutorials/laplace-dirichlet/site/`. The build is a plain `npm ci && npm run
130130 build`; `vite.config.ts` uses a relative `base`, so the sub-path needs no