happier-release

# Happier Release Keep release policy simple: test source once, admit the operation cheaply, build each immutable candidate once, verify once per trust boundary, promote independent products in parallel where the workflow permits, and recover without rebuilding valid work. When the same approved `dev` source must ship to both public channels, select the conductor's `preview-and-production` target. It reuses one exact-SHA CI and approval packet, and it executes the union of source-only MySQL, platform, and trust-root checks once before the canonical channel workflow runs preview and production concurrently. Each channel still performs its own admission against that shared exact-source evidence. Do not try to reuse preview artifact bytes for production: channel-specific binaries embed different feature-policy environments. The fast path removes duplicate orchestration and operator wait, not required channel-specific builds or artifact verification. Channel combination does not combine product targets. `website` and `docs` are independent entries in the target-owned release target set: either may be selected without the other, and each retains its own plan, job, status surface, and recovery evidence in both single-channel and combined operations. ## Resolve authority first Inspect the public machine-readable contract with: ```bash node scripts/pipeline/run.mjs release-contract ``` Then resolve the private release authority for the absolute checkout: ```bash hmaint releas...