Core v1.0.1 release notes

Status: approved 2026-08-25 stabilization release for the v1.0.x LTS maintenance line

Foundry Core 1.0.1 is the tooling-boundary stabilization patch for v1. The framework, migration lane, upgrade rehearsal, documentation, and release gate now use Go, Hugo, and Git only.

What changed

• Removed all executable Node maintenance, browser-audit, visual-capture, and pilot scripts from Core.
• Removed the final fixture package.json and Node setup from the dormant cross-platform workflow.
• Added foundry validate tooling, included in foundry check and foundry release-check, to reject package manifests, package-manager locks, executable Node scripts, and Node workflow commands.
• Changed Section migration render proof and upgrade rehearsal so they never bind or execute a consumer dependency tree, Tailwind CLI, or Node toolchain. Both paths now use Hugo and Go module replacements only.
• Replaced active Node commands in the documentation with the Go validation, fixture-browser, visual-example, WCAG-receipt, and release contracts.

Browser JavaScript boundary

Small assets in assets/js/ remain where a portable visitor interaction needs them. They run in the browser, ship as customer-owned source, and do not add a Node runtime, package manager, server, build, migration, or release dependency.

Compatibility and evidence

This patch does not change rendered theme, block, layout, or customer content contracts. The v1.0.0 responsive, WCAG automation, LikeStyle migration, and lab performance receipts remain the current release baseline. They still do not claim complete WCAG 2.2 conformance or field Core Web Vitals; assistive- technology, independent human, Safari, and eligible field-p75 evidence retain their explicit states.

The compatible maintenance line remains v1.0.x, with documented bug-fix support through 2027-08-25. Distribution LTS designation and consumer adoption remain separate release facts.

The exact candidate passed the full Go suite, all 25 Core release checks, and all 23 compatibility fixtures. The real LikeStyle source-directory migration produced 150 portable files (8,045,689 bytes), excluded 19 generated or tooling paths, and built directly with Hugo as 52 pages, 77 static files, and three aliases. The release process rechecks the immutable remote tag after publication; that administrative receipt cannot exist inside the tag it verifies.