hatch3r-enhancability-verify

# Enhancability Verification Gate ## Quick Start This skill defines what "done" means for any feature shipping user-visible behavior, public API changes, config schema changes, or extension-point interfaces. Run before declaring a feature complete. The 8 gates below mix automated checks (machine-checkable on every PR) with one release-cadence gate (semver bump + deprecation headers at release-cut). Skipping any gate = the feature is not done. Reviewer approval and passing tests alone do not satisfy this bar — a behavior change shipped without a flag commits the whole user base to the new path; a breaking change without a major bump breaks consumers silently. Inputs the skill expects: - A repository with `src/` source modules + a feature-flag client wired (OpenFeature, LaunchDarkly, Unleash, Flagsmith, Split, flagd). - A config schema file (Zod under `src/config/`, Joi, Pydantic `BaseSettings`, envalid). - Per-environment config files (`.env.development`, `.env.staging`, `.env.production`). - API spec files (`openapi.yaml`, `openapi.json`, `asyncapi.yaml`, GraphQL SDL) with `info.version` declared. - A flag-key inventory file (`flags.yaml` or registry-of-record). Outputs the skill produces: an 8-line verdict block written to the PR conversation, plus a JSON artifact at `.audit-workspace/enhancability-verify-<sha>.json` for downstream consumption by `hatch3r-release`. ## Step 0 — Detect Ambiguity (P8 B1) Before any work, scan the invocation for unresolved questions in sc...