happier-release-validation

# Happier Release Validation This is the repository-owned entrypoint for the public release contract's manual-only `deep` profile. It does not publish, promote, deploy, submit stores, or create a release operation. ## Start from the target contract From the explicit candidate checkout, inspect the target-owned profile and its executable suite inventory: ```bash node scripts/pipeline/run.mjs release-contract node scripts/pipeline/run.mjs release-validate --profile deep --dry-run ``` `deep` is not part of normal release dispatch. This skill is its manual entrypoint; the registry does not pretend that semantic compatibility or human QA can be decided by a script. For general release preparation or approval, first use the installed private maintainer authority: ```bash hmaint release bootstrap --repo <absolute checkout> --json ``` Read and follow the returned private skill for general release preparation or approval. This repository skill remains the target-owned deep-certification entrypoint only. If `hmaint` is unavailable, stop and obtain the approved maintainer-tool installation; do not substitute a copied release workflow or arbitrary shell commands. ## Manual certification 1. Record the exact candidate source SHA and every independently versioned component that the candidate changes. Resolve supported stable/preview baselines to immutable tags/artifacts; a rolling tag is discovery only. 2. Read `docs/compatibility.md`, map only reachable old/new directions,...