3 Commits

Include renames

Author	SHA1	Message	Date
clawbot	430ea0166e	docs: rewrite docs/RELEASE.md sentence by sentence against the prose rules ... Rewrite docs/RELEASE.md from scratch for #672: a terms list, what is needed, and six numbered steps, each with its check. Every statement is checked against the Makefile, script/, build.js, the two workflows and the tests. The step that described distribution routes not built is cut. The reproducibility claim names the build date that build.js compiles in, so it holds only within one UTC day. The commit carries the findings of the three reviews, the last two in the third review's wording: the self-contained check is described with the browser's directory as its subject, and Node and yarn must be on the PATH, because script/bootstrap leaves an nvm install off it. Model: fable-5-1	2026-11-03 03:40:28 +01:00
clawbot	0206b2f77e	chore: re-vendor canonical files from prompts at dd4027b (closes #472) ... Copies .dockerignore, .gitignore, .prettierignore, check.yml and REPO_POLICIES.md from sneak/prompts at dd4027b, keeping the repo's own entries (dist/, release/, yarn files) after the canonical content. The Dockerfile gets separate lint and test phases; its last stage depends on both, checks the git describe version and runs make build. script/lint, test, check, cibuild and docker are the canonical models. check-censored moves into the lint phase and test-verify-build into the test phase. fmt and fmt-check fall back to the nvm-installed node. The e2e image builds are uncached. Comments citing the old test caps or what runs a script are updated. Model: opus-5-5	2026-10-06 15:59:21 +02:00
clawbot	a1f082d686	docs: a release procedure from a green main to tagged, packaged artifacts (closes #387) ... Add docs/RELEASE.md, linked from README.md's Release Artifacts section, giving the release procedure as a numbered list: confirm main is green in CI, confirm the one version in package.json and the two manifests matches the intended tag, make package from a clean checkout, verify SHA256SUMS, create the annotated tag vX.Y.Z, then distribute per browser. Each step names who performs it, marks the owner-only ones, and states the check that it worked. Every repo command cited (make setup, make check, make package) exists on next; tagging and verification use standard git and coreutils, and the CRX pack line is README's own. The per-browser distribution step is written as pending the owner's choice on issue 386, with the Firefox and Chrome options named but none presented as settled. Docs only: no code or test changes. Model: opus-4-8	2026-09-21 22:00:18 +02:00