chore(release): cut v0.2.0

[Pher217]

Goal

Cut the v0.2.0 release — the rename release. CHANGELOG.md [Unreleased] was already written after #126; this promotes it, puts the three published components back on one version line, and closes out six rename leftovers the #126 sweep missed.

Follow-up §4 of the session note (02 Projects/OpenRemote-Control/03 Sessions/notes/2026-08-03T2300-openremote-control-librecontrol-rename.md).

Changes

Release

• CHANGELOG.md — [Unreleased] → [0.2.0] - 2026-08-03, with a summary paragraph flagging the breaking change for enrolled hosts. [Unreleased] is kept as an empty heading for the next cycle.

Versions — 0.1.0 → 0.2.0 across the three components that shared a version line at 0.1.0:

• backend/pyproject.toml (+ the matching root entry in backend/uv.lock)
• connectors/librecontrol-mcp/pyproject.toml
• connectors/messaging-gateway/package.json (+ package-lock.json)

Rename leftovers — the Node sidecar was still named orc-messaging-gateway:

• connectors/messaging-gateway/package.json, package-lock.json — package name
• connectors/messaging-gateway/README.md, deploy/README.md — prose references
• deploy/app/docker-compose.yml — the image: tag

Approach

Versions bumped only for the three components that were already in sync at 0.1.0, matching the precedent set by the v0.1.0 release commit (fe59d67), which bumped the backend specifically "to match orc-mcp and messaging-gateway".

host-agent/pyproject.toml is deliberately not touched — it sits at 0.0.1 and was already off the shared line before this release. Syncing it is a real decision (it implies the CLI is versioned with the server), not release mechanics, so it is left for a separate call.

The gateway image is built by compose itself (build: context is present, not pulled from a registry), so retagging it is self-contained — docker compose build produces the new tag and both READMEs now match it.

Test Summary

Suite	Result
messaging-gateway (npm test)	44/44 passed — 4 files, 1.11s
npm ci	clean install — confirms package.json ↔ package-lock.json agree after the name and version change
uv lock --check (backend)	exit 0 — lock consistent with the bumped pyproject.toml, 88 packages resolved

Backend, host-agent, and librecontrol-mcp changes are single version strings with no code paths touched; CI covers all four suites on this PR.

Files Changed

File	Change
CHANGELOG.md	promote [Unreleased] → [0.2.0], add release summary + sidecar-rename entry
backend/pyproject.toml	version 0.1.0 → 0.2.0
backend/uv.lock	root librecontrol-backend entry → 0.2.0
connectors/librecontrol-mcp/pyproject.toml	version 0.1.0 → 0.2.0
connectors/messaging-gateway/package.json	name → librecontrol-messaging-gateway, version → 0.2.0
connectors/messaging-gateway/package-lock.json	same, both root and packages[""] entries
connectors/messaging-gateway/README.md	heading renamed
deploy/README.md	build-step prose renamed
deploy/app/docker-compose.yml	image: librecontrol-messaging-gateway:latest

Screenshots

n/a — no UI surface changed.

After merge

Tag and publish:

git checkout main && git pull origin main
git tag -a v0.2.0 -m "v0.2.0 — the rename release"
git push origin v0.2.0
gh release create v0.2.0 --title "v0.2.0 — LibreControl" --notes-from-tag