Forge 1.0.0 release evidence

• Release gate: #42
• Verification date: 2026-09-03
• Stable content-model source: a8f0e86e9d82e28c5016e63a68d80282abae2bdc
• Stable create-forge source: f36722738b680f7aee547d9184fd7be37a258164

Published packages

The protected content-model publication run verified the registry artifact and triggered the tested template synchronization merged in #146. The create-forge publication run published successfully, then encountered a transient registry-metadata mismatch during its first verification window. Attempt 2 detected the identical immutable package, skipped republication, verified its integrity, created the stable GitHub release, and uploaded the publication result.

Clean-room Quick Start

The public, unversioned Quick Start was run outside the Forge checkout using Node.js 26.6.0 and npm 11.18.0:

npm create @rm-industries/forge -- stable-site --yes
cd stable-site
npm run quality

npm resolved @rm-industries/create-forge@1.0.0 from latest. The generated project installed @rm-industries/content-model@1.0.0 and initialized a clean main-branch Git repository. A local verification snapshot was committed after generation with SHA b35853f3c61165d6b6c2a3995614bde3f5216afc; this commit is evidence only and was not pushed.

The complete generated-project quality gate passed:

• formatting, code, CSS, Markdown, and spelling checks;
• unused-code, type, Astro, and policy-aware dependency checks;
• 38 unit assertions with 100% statement, branch, function, and line coverage;
• production build and 12 required-output validations;
• 93 browser and accessibility checks across Chromium, Firefox, and WebKit; and
• nine Lighthouse runs across the home, article index, and article detail pages.

Release scope and support

The stable release provides the reviewed generator, default Astro template, shared content model, Astro and Sveltia adapters, documentation, and protected release automation described in the package changelogs. No CLI or content-model migration is required from the final release candidates.

Known v1 limitations remain explicit: generated projects are owned source and do not receive automatic template migrations; npm is the supported package manager; Windows and WSL are best effort; and Sveltia compatibility remains bounded to the tested pre-1.0 minor range. The generated audit reports the time-bounded Lighthouse development-tool advisories already assessed in the security review; the policy-aware audit passes.

Use GitHub Issues for reproducible defects and feature proposals, and follow the security policy for private vulnerability reports.

Gate conclusion

• Scope, quality, security, documentation, compatibility, and API-freeze gates pass.
• Both packages are published from reviewed immutable tags with verified integrity and provenance.
• Stable public documentation uses npm’s latest resolution.
• The registry-backed Quick Start and generated-project quality gate pass in an isolated environment.
• Release features, requirements, limitations, migration impact, and support channels are documented.

The repository v1.0.0 checkpoint tag and GitHub release may be created from the reviewed merge commit that adds this evidence.