v0.3.0

Kiro joins the agent CLI lineup, the composer offers reply suggestions, and the fleet operator can answer questions and review plans on your behalf.

Kiro CLI support brings the lineup to seven — both execution methods, on-demand install against a pinned version, and live context and credit usage in the mirror.
Reply suggestions. The composer offers tappable reply chips, in the session mirror and in assistant chat: learned quick replies re-ranked against the latest message, plus an ✨ button that generates context-aware candidates. Fully keyboard-driven.
The fleet operator can answer a session’s question and approve or reject a plan. A new autopilot mode drives a session through the plan-review loop unattended, with a configurable cap on automatic replies (default 10, max 50).
Schedules can fire into an operator conversation instead of a session, user turns carry a badge that marks a scheduled run, and delivery is confirmed against evidence that a turn actually started.
Memos group under collapsible categories.
Host update prompt (native) — a staged build is surfaced in the top bar instead of being left to be discovered in settings.

Agent CLI self-update now actually advances. Every tool moved to one shadow model: the baked pin stays immutable, and turning self-update off reverts to it immediately.
Opus 5 and Sonnet 5 are recognised as 1M-context models in the usage estimate.
Mobile: agent selection is a horizontal swipe, and the send-key preference is honoured inside modals.

Completion reports could be lost when a background subagent was still running and the session stopped early; the report is now held and delivered afterwards.
An entire user turn could disappear from the mirror when a skill emitted its command tags in reverse order.
Deleting a worktree or session that an active schedule still references is refused instead of silently breaking the schedule.

Licensing and attribution are now stated where you receive the software. The distribution repo carries LICENSE and NOTICE, and the READMEs state that Agent Fleet is Apache-2.0.
Releases have real release notes from now on, including for every earlier version — indexed in the distribution repo’s CHANGELOG.md.

Nothing to do. The bundled agent CLI pins moved forward; AF_VERSION and the self-update opt-out behave as before.