chore(release): 0.5.0

[github-actions]

The next agent-tty release. Merging this PR creates the release tag and GitHub Release and starts the publish pipeline.

[0.5.0] - 2026-06-16

Added

• Default semantic operations (wait, snapshot, screen hash, batch render-wait steps, host semantic replay) to the in-process libghostty-vt renderer when the optional native package is available, falling back to ghostty-web when it is not. Visual artifacts (screenshot, record export --format webm) still default to ghostty-web. Explicit --renderer, AGENT_TTY_RENDERER, and config.json.defaultRenderer overrides are unchanged. (#157 by @ThomasK33)
• Dashboard maximized views now restore on Enter as well as Esc; footer hint updated to esc/⏎ restore. (#153 by @ThomasK33)
• Documented the stable CLI exit-code contract (0–11) in docs/USAGE.md, including batch fail-fast / --keep-going semantics and a note that a standalone wait timeout exits 0 with timedOut: true in the envelope (exit code 11 only surfaces from a timed-out wait step inside a fail-fast batch). (#150 by @ThomasK33)
• README scannability pass: anchor nav, numbered Quickstart "canonical loop", and a grouped command-surface table (lifecycle / input / observation / live view / environment). (#150 by @ThomasK33)
• New hostMain unit tests covering normalizeExitSignal, session-commandability assertions, and renderer-name resolution, plus an idle-timeout auto-exit integration test. (#158 by @ThomasK33)

Changed

• Host inspect/runtime metadata now reports the active renderer backend dynamically, and capability discovery (version --json, doctor --json) distinguishes semantic-render availability from browser-backed visual capability. Legacy render-wait modes degrade rather than disappear when only render waits lack a renderer. (#157 by @ThomasK33)
• Per-session RPC socket directory is created 0o700, the socket file 0o600, and persisted state (session manifests and the Home Registry) 0o600, independent of the caller's umask, so other local users cannot connect to a session's control socket or read its state on shared machines. (#158 by @ThomasK33)
• CI now runs aube audit --audit-level high (via a new mise run audit task wired into mise run ci and the linux-static job); the seven advisories present at audit time were cleared via package.json overrides (brace-expansion, esbuild, vite, ws). (#158 by @ThomasK33)
• README tagline now mentions agent-browser alongside Playwright. (#155 by @ThomasK33)
• RELEASE.md support contract is now version-agnostic so release-please bumps don't re-stale it. (#158 by @ThomasK33)

Fixed

• README status version is now driven by release-please's extra-files updater, so the in-README version stays in sync with package.json on every release PR. (#156 by @ThomasK33)
• Standing release PR branch is now release-please--branches--main instead of release-please--branches--main--components--agent-tty, restoring the documented round-trip and preventing release-please from silently skipping release creation on a component mismatch. (#147 by @ThomasK33)
• Internal review fixes from the renderer-default split: host renderer operations stay leased during backend use, and automatic private host renderer defaults no longer leak into spawned PTY environments. (#157 by @ThomasK33)

Release / CI

• feat: commits now bump the minor version pre-1.0 (0.4.x → 0.5.0); fix: still bumps patch, and feat!: / BREAKING CHANGE: continue to bump minor instead of jumping to 1.0.0. Reaching 1.0.0 remains an explicit Release-As: 1.0.0 decision. (#152 by @ThomasK33)
• New pr-title workflow validates PR titles against Conventional Commits using amannn/action-semantic-pull-request@v6.1.1, since the squash-merge subject becomes the commit that release-please parses. (#154 by @ThomasK33)

---

Maintained by the release-please workflow. Notes are regenerated by Communique on every push to main, so manual edits to this PR are overwritten.