Sprint 10.8 — Prepare v0.1.0 release candidate

[maruson08]

Problem / motivation

The complete release path needs one repeatable clean-state dry run before any tag, GitHub Release, or npm publication.

Scope

• target version 0.1.0 once, intentionally
• automate/check clean checkout, npm ci, validation, properties, fuzz smoke, builds, browser smoke, package/license audits, reproducibility, hashes, documentation, version, and source traceability
• provide a concise release checklist and RC result

Non-goals

• npm publish
• v0.1.0 Git tag or GitHub Release
• Secure Tools integration

Acceptance criteria

• full RC dry run passes from clean source
• artifacts and hashes identify version and source commit
• remaining external release steps are concrete and documented