release: @focus-mcp/cli v2.2.1 — sync develop → main

[samuelds]

Sync develop → main for cli 2.2.1 release. Includes: dist-tag fix in stable-publish.yml + version bump 2.2.0 → 2.2.1.

[Copilot]

Pull request overview

Syncs develop into main for the @focus-mcp/cli v2.2.1 release, including a workflow tweak intended to ensure the npm @latest dist-tag is correct after publishing.

Changes:

• Bump @focus-mcp/cli version from 2.2.0 to 2.2.1.
• Add a post-publish step to re-assert the npm latest dist-tag.
• Update CHANGELOG.md for 2.2.1 and remove several (previous) changeset files.

Reviewed changes

Copilot reviewed 8 out of 8 changed files in this pull request and generated 2 comments.

File	Description
package.json	Version bump to 2.2.1.
CHANGELOG.md	Add 2.2.1 release notes entry.
.github/workflows/stable-publish.yml	Add an “Ensure @latest dist-tag” step after publishing.
.changeset/*.md	Remove several changeset markdown files.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

The new dist-tag step only runs when steps.publish.outputs.published == 'true', but the publish step sets published=false for "already/previously published" output. If a run is re-triggered to fix a bad dist-tag for an already-published version, this step will be skipped and the tag won’t be corrected. Consider setting a separate output (e.g. should_tag_latest=true for both successful publish and already-published cases) or relaxing the if: so the dist-tag update can run when publish was skipped due to an existing version.

[Copilot]

npm dist-tag add ... || echo "→ dist-tag update skipped" will make the workflow succeed even if the dist-tag update fails due to auth/registry issues. Since this workflow is intended to enforce the latest tag, it’s safer to only ignore known-benign errors (e.g. tag already set) and otherwise fail the job so releases don’t silently ship with an incorrect tag.

Suggested change

	npm dist-tag add "${NAME}@${VERSION}" latest || echo " → dist-tag update skipped"
	set +e
	DIST_TAG_OUTPUT=$(npm dist-tag add "${NAME}@${VERSION}" latest 2>&1)
	DIST_TAG_STATUS=$?
	set -e
	echo "$DIST_TAG_OUTPUT"
	if [ "$DIST_TAG_STATUS" -eq 0 ]; then
	exit 0
	fi
	if echo "$DIST_TAG_OUTPUT" | grep -Eiq "already set|already has .*latest|cannot modify existing version"; then
	echo " → latest dist-tag already set; continuing."
	exit 0
	fi
	echo " → failed to update latest dist-tag" >&2
	exit "$DIST_TAG_STATUS"