Releasing v1

The package is versioned 1.0.0-rc.1 and named three-voxel-reflections (unscoped). The current native run covers Apple M4 / Chrome 152. A stable release still requires the additional hardware and performance gates below.

1. Install the exact development dependencies with npm ci using the committed lockfile.
2. Run npm run check. Build-only isolated declarations are not a replacement for semantic checking against the installed Three.js type package.
3. Run npm run test:browser on native WebGPU with no fallback, and repeat on a second GPU/browser implementation. Inspect generated captures as well as numeric metrics. Preserve device/browser details and WebGPU validation messages.
4. Run npm run validate: this includes native VXGI, source textures, lighting motion, receiver normals, empty/rebuilt resources, ownership and explicit device destruction/recreation. Also test unexpected device loss in the consuming application. The pinned npm r186 distribution contains the upstream add-on; the consumer test type-checks its adapter contract.
5. Measure resolution, reflective pixel coverage, step count, memory and update costs on target hardware. Software-renderer wall times are not GPU performance claims.
6. Run npm run test:package and npm run build:site && npm run test:site. The package test packs the library, installs it in an isolated consumer, and checks all public exports with strict TypeScript and Node. Inspect the tarball inventory and notices. It must not contain node_modules or unrelated test-runtime snapshots.
7. Once stable gates pass, change the version to 1.0.0 and update the support matrix. For an RC publication use npm publish --tag next --access public; for stable use npm publish --access public, from an account permitted to publish the unscoped name. Verify registry name availability immediately before publishing. GitHub pushes and Pages deployment do not publish to npm.

The prepack hook runs the semantic/unit checks. The native browser gate is intentionally explicit rather than silently skipped on CPU-only CI.

GitHub Pages

The checks workflow builds the static documentation and asset-free lab, validates links/layouts, and deploys _site on successful main pushes. Repository Settings → Pages must use GitHub Actions. The expected site is https://hoodgail.github.io/three-voxel-reflections/; examples live at examples/. Three.js is vendored from the exact lockfile during the site build. No CDN or npm publication is required to use the lab.