Core release checklist

The canonical release verification path is in VALIDATION.md.

Run before any release:

go run ./cmd/foundry validate runtime
go run ./cmd/foundry validate motion
go run ./cmd/foundry validate quality
go run ./cmd/foundry validate scaffolds
go run ./cmd/foundry doctor --json
node scripts/foundry-doctor.js

For browser parity:

node scripts/foundry-doctor.js --browser-smoke --require-browser

For downstream consumer validation:

node scripts/foundry-doctor.js --site /absolute/path/to/site

See VALIDATION.md for the full regression review checklist and CI safety bar.

Current checkpoint readiness

The 2026-06-01 Foundry productization checkpoint is ready to check in when the commands above pass. This checkpoint includes Go CLI validation/scaffolding parity, Creative route-floor/productization work, Motion Kit hardening, quality gates, compatibility fixtures, and docs/status alignment.

The following are future milestones, not blockers for this checkpoint:

• foundry upgrade
• remaining Tier 2 block variant expansion
• extension and capability-pack contracts
• shared content-model manifest extraction, unless another lane needs the same shape before release
• subjective Lighthouse/content-quality gates beyond the current objective quality checks

Administrative release steps

1. Confirm the Go validators, Go doctor, and node scripts/foundry-doctor.js pass clean.
2. Confirm the changed block, shell, flow, or SEO docs still match the current contract.
3. If new blocks were added, confirm the block registry and block-family-manifest are updated.
4. Tag the release (e.g., v0.1.20).
5. Update pins in downstream sites only when approved through the bundle process.