Documentation

Launch Readiness

What must be true before the open beta package is treated as public release-ready.

First public package

The planned free open beta package centers on Chat Mirror and Follow Wheel. Blur Beta is handled as a separate paid early-access beta with Windows signing as a public-release gate.

- Each real artifact needs an approved release file and delivery path.
- Each ready artifact needs exact sizeBytes and SHA-256 in the manifest.
- Windows desktop artifacts need signed executable proof before broad public access.
- The download page should keep open-beta or placeholder labels until files are real.

Creator-site handoff

The standalone product site can stay separate while a creator hub promotes it as a stream-tool project.

- Use a creator hub for discovery traffic.
- Use this standalone site for manifests, beta downloads, docs, and custom requests.
- Do not promise accounts, payments, licensing, or auto-delivery until those paths exist.

Release review

Every release pass should prove the visible site and the manifest agree.

- Run npm run check:release for a blocker summary.
- Run npm run validate:manifest, npm run test, npm run typecheck, npm run lint, and npm run build.
- Browser-check the homepage, downloads, docs, custom request, and the first tool detail pages.