release

# Release ## Overview Cut a release end to end: validate the version, live-smoke-test every provider at HEAD, push the tag, wait for the Release workflow (goreleaser publishes the GitHub release with a raw commit-list body), then rewrite the notes in the house style and report back. ## Input Exactly one version matching `^v\d+\.\d+\.\d+$` (all numeric, e.g. `v0.8.0`). Reject anything else — `0.8.0`, `v0.8`, `v0.8.0-rc1` — and ask for a corrected version instead of guessing. It must not already exist and must sort above the latest tag (`git tag --sort=-v:refname | head -1` — that latest tag is also the "previous version" used in steps 2, 4, and 5). Require a clean tree on main, in sync with origin/main. ## 1. Smoke-test every provider (before tagging) Test HEAD through the real MCP path, never an installed binary or the session's connected openings-mcp server — those run the previous release. Build once (`go build -o <scratchpad>/openings-mcp ./cmd/openings-mcp`) and drive it over stdio; the request script is in the integrate-new-provider skill's MCP-surface step. - **ATS adapters** (the unified-search set: `providerOrder` in `cmd/verify-companies/main.go`): per provider, sample 3–5 companies from `internal/provider/<name>/companies.yaml`; `search_jobs_by_company` must return live listings for each, and `get_job_detail_by_company` must succeed on at least one returned job_id. - **Dedicated-tool providers** (job boards and careers sites: the `Register*` calls...