chore(release): prepare api-to-typemcp v0.2.2

[sjungwon03]

Summary

• preserves the divergent main release lineage with a no-fast-forward reconciliation merge
• bumps the public api-to-typemcp skill version from 0.2.1 to 0.2.2
• updates release-contract fixtures to require the matching GitHub tag and registry version

Verification

• python3 .agents/scripts/test_skill_release.py — 15 passed
• python3 -m unittest discover -s skills/api-to-typemcp/tests -p "test_*.py" -q — 140 passed
• python3 .agents/scripts/test_validate_docs.py — 8 passed
• python3 .agents/scripts/test_workspace.py — 3 passed
• python3 .agents/scripts/validate_docs.py
• python3 -m py_compile .agents/scripts/*.py skills/api-to-typemcp/scripts/*.py
• git diff --check

Closes #75

[sjungwon03-ai]

Review: chore(release): prepare api-to-typemcp v0.2.2

Verdict: APPROVE — version bump and release-gate hardening are correct and well-tested.

What changed

• skills/api-to-typemcp/SKILL.md: frontmatter version 0.2.1 → 0.2.2.
• .github/workflows/release-promotion.yml: the former dev-only guard is replaced with a two-tier gate accepting dev or a strict release/<positive-issue>-<kebab> branch, plus main/dev ancestry checks and a two-parent merge requirement for release branches. Checkout is pinned to a SHA (actions/checkout v4) with fetch-depth: 0.
• .agents/scripts/validate_release_promotion.py: rewritten to assert the new contract (branch regex, pinned checkout, ancestry, merge-parent count).
• .agents/scripts/test_skill_release.py: fixture versions updated to 0.2.2.
• Two task briefs documenting the v0.2.1 promotion and v0.2.2 release preparation.

Assessment

• Correctness: The branch regex ^release/[1-9][0-9]*-[a-z0-9]+(-[a-z0-9]+)*$ correctly rejects release/0-*, empty segments, and uppercase. Ancestry guards ensure only lineage-preserving candidates pass.
• Security: No secrets in the diff. The workflow reads github.head_ref only for the branch-name guard; no untrusted input reaches a shell expansion. Pinned checkout SHA prevents supply-chain drift.
• Tests: CI e2e, docs-and-harness, and bundled-engine all passed on the exact head SHA. release-skill correctly skipped (no tag event).
• Backward compatibility: dev promotion remains accepted; the new release/* path is strictly additive.

No blockers found.

---

Reviewed by sjungwon03-ai (automated)

[sjungwon03-ai]

Independent review — head 761184d

One blocking release-claim finding; everything else verified clean.

Blocking

• README.md:22 — install section still links releases/tag/v0.2.1. Both prior preps bumped this link inside the prep commit (e6ab414 for v0.2.0, 2274a10 for v0.2.1). Without the bump, the public README points at a stale release the moment v0.2.2 is published via the dev → main merge. One-line fix in the prep commit; note the file is outside the current diff so it must be added to this PR.

Verified

• Reconciliation 8fd9112 is a clean no-fast-forward merge with exactly two parents (dev 0d512946 + main 169bf82f); combined diff empty — no evil merge. Both main v0.2.1 lineage 169bf82f and base 0d512946 are ancestors of head; dev functionality (MCP installation feature set, 140 engine tests) fully preserved.
• Version agreement: skills/api-to-typemcp/SKILL.md:4 = 0.2.2; all 9 release-contract fixture sites in .agents/scripts/test_skill_release.py agree on 0.2.2.
• release-promotion.yml guard and validate_release_promotion.py assertions match; actions pinned to full SHAs; release-skill job fires only on push to main (skip on this PR is correct).
• Secrets scan, conflict-marker scan, and git diff --check all clean; no build artifacts or node_modules in tree.
• CI run 30419789455 at exact head 761184dc: docs-and-harness pass, bundled-engine pass, e2e pass, release-skill skipped (expected).
• Local on fresh clone at detached head: test_skill_release.py 15/15 OK, test_validate_docs.py 8/8 OK, test_workspace.py 3/3 OK, validate_release_promotion.py + validate_docs.py pass, py_compile clean.

[sjungwon03]

Resolved the release-claim finding in the new HEAD 611dcca064bd4b7049a805250b2d9e9b1f01af71:

• README now links to GitHub Release v0.2.2.
• Added a release-contract regression test that derives the expected README release tag from SKILL.md; it failed against the prior v0.2.1 link and now passes.

Fresh verification: release contract 16 passed; engine 140 passed; docs 8 passed; workspace 3 passed; docs/release-promotion validation, Python compile, and git diff --check passed.

[sjungwon03-ai]

Superseding review — head 611dcca064bd4b7049a805250b2d9e9b1f01af71

The single blocking finding from the prior CHANGES_REQUESTED on 761184dc is resolved in the new commit 611dcca ("fix(release): align README link with v0.2.2"). No new blockers introduced.

Resolved findings

• Prior blocker: README.md:22 install section still linked releases/tag/v0.2.1, so the public README would point at a stale release the moment v0.2.2 was published.
  • Resolution evidence: README.md line 22 now reads - [GitHub Release v0.2.2](https://github.com/Theorvane/type-mcp-api-agent-skill/releases/tag/v0.2.2), matching skills/api-to-typemcp/SKILL.md version: 0.2.2.
  • Regression guard: new test test_readme_release_link_matches_the_skill_version in .agents/scripts/test_skill_release.py derives the expected tag from SKILL.md and asserts the README contains it, so future prep commits cannot silently drift again.
  • Docs sync: .agents/task-briefs/75-release-api-to-typemcp-v0-2-2.md verification table updated to the new 16-test count.

Verified on the new head

• Delta 761184dc...611dcca is exactly one commit touching three files: the README link fix, the new release-contract test, and the task-brief count update. No unrelated changes, no artifacts, no secrets or conflict markers.
• New test correctly parses version: from SKILL.md frontmatter and checks the README for releases/tag/v{version} — logic is sound and fails closed on mismatch.
• CI run 30420600831 at exact head 611dcca: docs-and-harness success, bundled-engine success, e2e success, release-skill skipped (expected — fires only on push to main).
• Version agreement holds across SKILL.md (0.2.2), README release link (v0.2.2), and the release-contract fixtures validated by the harness.
• PR remains mergeable; mergeable_state: blocked reflects the required-review gate, not a conflict — informational only, not a code-quality blocker.

Release prep is now self-consistent and guarded by a regression test. Approving.