chore(release): 0.2.0

[ThomasK33]

Summary

First stable release of agent-tty. Bumps package.json from 0.1.1-beta.4 to 0.2.0 and finalizes the Unreleased changelog block as [v0.2.0] - 2026-05-13.

This is Step 3 of the v0.2.0 release sequence:

• ✅ docs: prepare 0.2.0 release narrative #99 — docs: prepare 0.2.0 release narrative
• ✅ fix(release): support aube-only checkouts without package-lock.json #101 — fix(release): support aube-only checkouts without package-lock.json
• ⬅️ this PR — chore(release): 0.2.0
• Step 4 — release:finalize will push the v0.2.0 tag after merge

Why 0.2.0 (and not 0.1.0)?

No v0.1.0 tag, GitHub release, or npm version ever existed. The package shipped 0.1.1-beta.0–0.1.1-beta.4 directly. Cutting 0.2.0 as the first stable sidesteps the "did 0.1.0 ever exist?" mismatch and avoids version-going-backwards optics. Narrative: "0.1.x was the beta line; 0.2.0 is the first stable." Documented in #99.

Diff

Exactly two lines change in this commit:

• package.json — "version": "0.1.1-beta.4" → "version": "0.2.0"
• CHANGELOG.md — ## [Unreleased] → ## [v0.2.0] - 2026-05-13

Generated locally with:

npm run release:prep -- --version 0.2.0 --changelog ci
# (amend) rename [Unreleased] -> [v0.2.0] - 2026-05-13
git commit --amend --no-edit

The [Unreleased] header rename is included in the prep commit so the Release Changelog workflow's existing-version check (release-changelog.yml:97) detects ## [v0.2.0] and skips its Communique pass entirely — preserving the curated content already in the Unreleased block.

Why not package-lock.json too?

Post-#91 the repo uses aube-lock.yaml; package-lock.json no longer exists. #101 updated the release tooling to handle this case, so release:prep correctly stages only package.json.

After merge

npm run release:finalize from clean, synced main will create the annotated v0.2.0 tag and push it. The tag-triggered Release workflow then:

1. Validates v0.2.0 == package.json.version.
2. Runs mise run ci.
3. Packs the tarball + sha256 + metadata.
4. Generates Communique release notes for v0.2.0.
5. Creates the GitHub Release with assets attached.
6. Publishes to npm. Because 0.2.0 has no prerelease suffix, the workflow's dist-tag derivation publishes to latest, replacing the stale latest: 0.1.1-beta.2 mapping.

Test plan

• npm run format:check clean
• npm run lint 0 warnings / 0 errors (shows agent-tty@0.2.0 — version bump real)
• CI on this PR
• Confirm Release Changelog workflow detects existing [v0.2.0] header and skips (i.e. no bot commit appears on this branch)
• Post-merge: release:finalize succeeds and Release workflow publishes
• Post-publish verification per docs/RELEASE-PROCESS.md:
  • npm view agent-tty dist-tags → latest: 0.2.0
  • Global install: agent-tty version --json → cliVersion: 0.2.0, protocolVersion: 0.1.0
  • agent-tty --home <tmp> doctor --json → .result.ok: true

🤖 Generated with Claude Code