A terminal reader, ipx; the server is ipxd (#437)

ipx-tui (crates/tui) is iPX's reader in ratatui: your feeds, a feed's
items, an item's text as plain text, read and flagged as on the page,
through the API with an API token. It installs as `ipx`, so the daemon's
binary is now `ipxd`: the Dockerfile, release script, tests and every
doc and message that names its commands follow.

Naming the binary ipxd alone renamed its crate, and with it every log
target (ipx::scan became ipxd::scan): the default filters are ipx=info,
so nearly every line would have been dropped and the dashboard's queries
on the targets gone blank. The daemon's code is now a library still
called ipx, under a five-line ipxd main.rs, and the targets are as they
were.

ratatui is taken without its default features: 32 new packages in place
of 78.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01RqkrVDqdiQEMWAkNGQ2tYA

grafana/dashboard.py

@@ -19,7 +19,7 @@ PROM = {"type": "prometheus", "uid": "${prometheus}"}
 SEL = '{container="iPX"}'
 # ipx logs one JSON object a line (IPX_LOG_FORMAT=json). Each scan and download event carries its
 # fields (ev, feed, new, bytes, msg, error.type, ...); a failed request its method, path, route,
-# status and duration_ms. Events are logged under ipx::scan, `ipx status`'s answer under ipx::io,
+# status and duration_ms. Events are logged under ipx::scan, `ipxd status`'s answer under ipx::io,
 # so the filter is on the ev field, not the target.
 EV = SEL + ' |= "\\"ev\\":\\"" | json | __error__="" | ev != ""'
 # Each request ipx answers, the event stream aside, as a histogram (#364): its line in the log is