Public Site Release Checklist

Use this checklist for documentation, website, registry, and migration-site

releases.

Release-Blocking Local Gates

These gates are safe for normal documentation sessions:

make public-docs-milestone-9-check
make public-docs-milestone-10-check
make static-site-release-bundle-check

The release is blocked when any of those gates fails.

Required Update Checks

When public behavior changes, update the relevant docs before release:

• language or syntax behavior: update docs/language.html, docs/syntax.html, and

docs/grammar.ebnf;

• package behavior: update docs/package-system.html, docs/packages.html, and

package examples;

• runtime behavior: update runtime boundary docs and capability docs;
• public library changes: run make libs-registry-generate and update registry

evidence;

• migration behavior: update migration, obsolescence, command-map, and feature

matrix docs;

• site route changes: run make public-ux-generate and update

site/metadata.tsv, sitemaps, and search index.

If public behavior changed but docs did not, record the reason in the release

notes before publishing.

Manual Remote Publish Steps

Remote publication is manual because it touches live domains:

1. Run make static-site-release-bundle-check.

2. Dry-run copy the bundle to the remote static roots.

3. Create a remote rollback backup before copying.

4. Publish build/static-sites/0x0/ to /var/www/sites/0x0/.

5. Publish build/static-sites/libs/ to /var/www/sites/libs/.

6. Publish build/static-sites/lang-archive/ to /var/www/sites/lang/.

7. Publish build/static-sites/jmp0x1b/ to /var/www/sites/jmp0x1b/.

8. Fetch public smoke markers from all affected domains.

9. Record the backup path, smoke results, and rollback plan in

deploy/static-sites/.

Rollback Expectations

Every site release must have a rollback source before copying files. Rollback

means restoring the previous static root and nginx config when applicable, then

running nginx -t and reloading nginx.

The public docs release hash is the SHA-256 of

build/static-sites/SHA256SUMS. Record it in

docs/public-docs-website-completion-evidence.html and

deploy/static-sites/completion-report.html after the final bundle is built.