chore: release v2.2.0

[mabry1985]

v2.2.0

Minor release capturing the biome standardization work:

• feat(workspace-config): biome-linter rule (feat(workspace-config): biome-linter rule — fleet tracks one biome version #43) — FLEET_BIOME_VERSION single-source-of-truth + a workspace-config rule so the fleet tracks one biome version together (flags JS/TS repos off the pin / still on ESLint / missing biome.json; N/A for non-node repos).
• chore(lint): ESLint → biome 2.4.16 (chore(lint): migrate ESLint → biome 2.4.16 #42) — release-tools itself now lints with biome.

Squash-merging this chore: release v2.2.0 commit triggers the Release workflow → tags v2.2.0, publishes to npm (OIDC provenance), posts Discord notes.

🤖 Generated with Claude Code

[protoquinn]

👀 Quinn is reviewing — verdict (PASS / WARN / FAIL) + findings to follow.

[protoquinn]

QA Audit — PR #44 | chore: release v2.2.0

VERDICT: WARN

---

CI Status

• Lint + smoke test: queued

Diff Review
Clean version-bump PR: package.json and package-lock.json bumped 2.1.1 → 2.2.0. No functional changes — this is a pure release commit. Squashing triggers the Release workflow which handles tagging + publish + Discord notes.

Observations

• MEDIUM: CI check (Lint + smoke test) is still queued — formal PASS/FAIL withheld pending a terminal result. This review is non-blocking.
• No unresolved CodeRabbit threads.
• The diff is trivially correct and self-contained. No structural review needed for a two-line version bump.

— Quinn, QA Engineer

[protoquinn]

Submitted COMMENT review on protoLabsAI/release-tools#44. CI is still queued — I'll re-inspect check_ci once the Lint + smoke test reaches a terminal state for the formal verdict (PASS expected on this clean version bump).

[protoquinn]

CI terminal-green, no blockers on prior review — auto-approving on green (#748).