Release W&B MCP Server

Follow the controller

1. Read RELEASING.md and the target note under docs/releases/ completely.
2. Record exact source and tree SHAs. Treat moving branches and mutable tags as navigation only, never evidence.

3. Run the candidate gate:

   uv run --no-sync python scripts/public_release.py \
     preflight --version "$VERSION" --gate candidate

   Verify generated configuration/profile documentation with python scripts/public_release.py docs --check.

4. Verify the packaged src/wandb_mcp_server/runtime-contract.json hash, then inspect the exact profile/access-mode pairs generated by python scripts/public_release.py profiles --all. Do not substitute counts, subsets, or copied tool lists.
5. Run the locked/latest SDK, Python, security, isolated-wheel, and installed MCP protocol gates specified by RELEASING.md.
6. Stop at a draft candidate unless the user explicitly authorizes the next action and repository protection allows it.

Fail closed

Do not continue when the controller reports a dirty tree, inconsistent version, stale SHA, unsigned or misplaced tag, missing release note, incomplete exact profile evidence, mutable artifact, missing scan/SBOM, or mismatched digest. Record a skipped or unavailable check as a blocker, never a pass.

After the approved release PR merges, source-gate must bind the merge SHA to the reviewed head tree, required current-head checks, approval, and resolved conversations before anyone creates the signed tag.

If that post-merge gate or a final security check finds a source defect, stop before tagging or deployment. Fix it in a new reviewed PR, treat all earlier candidate evidence as stale, and stage the repaired tree again. Never amend the already-reviewed history or reuse evidence from the superseded tree.

Build only through scripts/public_release.py build into a new directory outside the checkout. Never reuse dist/. The attest command produces a deterministic predicate for the protected signer; it is not signed evidence by itself.

Keep public release documentation factual

Track public source, W&B-hosted images, customer images, and installation qualification independently. State a channel as available only when its version note contains verified immutable evidence for that channel. Otherwise use Pending or Not recorded; never carry a digest, scan result, date, chart, or rollout claim forward from another version.

Keep release notes useful to installers and contributors. Exclude private workflow links, infrastructure identifiers, approval procedures, credentials, customer identifiers, and raw responses. After any runtime-contract or source change, regenerate the generated documentation and invalidate downstream profile or artifact evidence from the previous tree.

Preserve authorization boundaries

This skill does not authorize merging, tag creation, publication, deployment, production traffic, customer rollout, or branch-protection bypasses. Public source must merge and receive a verified signed tag before production traffic can move. Managed promotion and customer publication remain separate protected approvals.

Never place credentials in arguments or evidence. Live credentials must come from a protected process environment, and release artifacts must exclude prompts, filters, customer identifiers, raw responses, private routes, and secret names.

Hand off exact evidence

Provide the protected release controller with:

• Version, signed tag, source SHA, and source tree SHA.
• Packaged runtime-contract digest and exact profile/access-mode evidence digest.
• Wheel, source distribution, checksum, SBOM, vulnerability report, signature, and provenance digests.
• Per-channel state from the release note.
• The previous immutable artifact and tested rollback boundary.

Follow the canonical release state machine. Any source or tree change invalidates downstream evidence and restarts qualification.