chore: release v0.2.1

[github-actions]

🤖 New release

• telepath-macros: 0.2.0 -> 0.2.1
• telepath-server: 0.2.0 -> 0.2.1 (✓ API compatible changes)
• telepath-client: 0.2.0 -> 0.2.1 (✓ API compatible changes)
• host-pty-server: 0.2.0 -> 0.2.1

Changelog

telepath-macros

0.2.1 — 2026-05-30

Added

• macros,server: Emit ResponseStatus::AppError for Result<T, AppErrorPayload> returns (#193)

telepath-server

0.2.1 — 2026-05-30

Added

• macros,server: Emit ResponseStatus::AppError for Result<T, AppErrorPayload> returns (#193)

telepath-client

0.2.1 — 2026-05-30

Added

• macros,server: Emit ResponseStatus::AppError for Result<T, AppErrorPayload> returns (#193)

host-pty-server

0.2.1 — 2026-05-30

Added

• macros,server: Emit ResponseStatus::AppError for Result<T, AppErrorPayload> returns (#193)

---

This PR was generated with release-plz.

[tarotene]

Closing as stale duplicate

Why: v0.2.1 was already released by run 26686026473 (triggered by the merge of #197):

• git tag v0.2.1 + GitHub Release created ✅
• telepath-wire/macros/server/client 0.2.1 → crates.io ✅
• tools/telepath 0.2.1 → crates.io ❌ (Cargo.lock dirty — see below)

Origin of this PR: release-plz run 26686022733 (triggered by #201 merging 12 seconds before #197 merged) computed the diff against a Cargo.toml = 0.2.0 checkout that pre-dated the v0.2.1 tag, and opened this PR not knowing the release had already happened in the concurrent run.

Next steps:

• tools/telepath 0.2.1 will be backfilled to crates.io manually.
• PR fix(ci): use cargo update --precise to avoid registry dep churn in bump-excluded #204 will add workflow hardening to prevent the dirty-lock failure from recurring.