v0.1.9

The whole interface is now operable without sight or a mouse. --accessible
drops the alternate screen, the mouse capture and the colour, renders the view
as plain ASCII and keeps the recent status changes in a linear activity log,
so a screen reader has something to read that is not a repainting grid.
Ctrl+P opens a command palette over the actions the key-bars carry, so
everything reachable by a hint is also reachable by name, and shift+tab now
walks focus backwards wherever tab walks it forwards — on every screen and
every form. A terminal resized below 80x24 shows the resize message without
disturbing the selection, the focus or anything half-typed behind it.

The native host tells the extension what actually went wrong. An ensure
that could not produce a daemon carries a code to route on — aria2c-missing
when the binary is not there, daemon-failed when it is and the daemon still
did not come up — instead of arriving untagged and being filed under "check
the server in Settings", which is no remedy for a daemon that died on launch.
When it dies early there is no stderr to quote, so the failure now carries the
tail of aria2.log rather than ending in a bare "exited during startup: ".

A new diagnostics verb answers the extension's "Report a problem" with the
host's view of the install — paths, the config and its parse error, the aria2c
lookup, the daemon record and probe, the session size and the last log lines —
and never the RPC secret, because the report is pasted into a public tracker.

v0.1.8

The native host now tags a missing aria2c with a machine-readable code, so
the extension can tell it apart from a missing host instead of sending the
user to reinstall what they already have.

The TUI also shows why it is not connected: the reason was recorded on every
failed connect and rendered nowhere, leaving a machine without aria2c
looking like a silently broken app.

v0.1.7

aria2c is now found beside the aria2t binary, not only on PATH — the
Windows installer puts it there, and neither the installing shell nor the
browser that spawns the native host has re-read the user PATH yet.

v0.1.6

Aria2t is the product name in the wordmark, the quit confirm, the welcome
panel and the built-in daemon hint. The binary, the config path and the
command stay lowercase.

v0.1.5

aria2t 0.1.5

v0.1.4

aria2t 0.1.4

v0.1.3

The aria2t binary now doubles as the browser extension's native-messaging host —
Chrome launches the same binary with a chrome-extension:// argument and it
speaks the framed stdio protocol instead of starting the TUI. Verbs: hello,
status, ensure, reveal, clean-control, delete-files. install.sh <extension-id>
points a host manifest at it.

Downloads no longer leave aria2's bookkeeping behind. The daemon runs with
--force-save so completed downloads survive a restart, which also keeps the
.aria2 control file; those are now deleted when a download finishes, and the
control file plus the .torrent saved by --bt-save-metadata go with a
download that is removed. Deleting either is only safe together with dropping
the download from the saved session, so the gid is recorded and the session is
filtered before the daemon is next spawned.

Removing is remove-then-purge-until-it-lands: aria2.remove returns before aria2
has moved the group to the results list, so a single purge after it fired too
early and left the download parked as a "complete" row that had to be removed a
second time.

Also: magnet metadata is persisted so a restart resumes the transfer instead of
re-fetching metadata; seeding torrents are really deleted on remove; and the
1280x800 promo screenshot set lands in tui/docs/promo.

v0.1.2

Theme-matched README media: light demo gif and light/dark logo marks
referenced by the theme-aware README.

v0.1.1

• Windows builds (amd64, arm64) in the release matrix.

v0.1.0

• Initial public release: Bubble Tea TUI for aria2 with managed daemon,
  torrents/magnet/Metalink support, file picker, scheduler, integrity checks.