The host connector answers filesystem_usage, directory_sizes and old_files on
configured hosts over SSH with pinned host keys, dialling through the egress
tunnel when confined. The sops engine decrypts with the sops library instead
of the CLI, takes its file from settings and an age identity from its secrets.
The bundled internal/channels/telegram package (17 files) is deleted; the
channel now ships as archipelago/channels/telegram, launched by archiemessaging
through the existing channel-extension machinery. An existing [chat.telegram]
config enables it with the same keys: the token stays a secret reference
(token_ref) the host resolves, allowed_user_ids and show_tool_calls map onto
extension settings. Per-org bots compose the same extension per org from the
org's credential binding. Reload support is now derived from a channels.Reloader
interface instead of a *telegram.Gateway assertion. The five host-only seams
(/update, release announcements, running versions, in-place show_tool_calls,
reload) are dropped from the channel and need a contract home or deletion.
The switch to the age library read only native age keys, so an
AGE_IDENTITY holding an SSH private key or a plugin identity (a YubiKey)
stopped working. Both parse again; a plugin that asks for input fails with
a message saying so, and a passphrase-protected identity file is refused
by name.
The age, Vault and SOPS engines shelled out with stderr discarded, so a
missing key and a broken setup both surfaced as 'exit status 1' and were
reported as the engine being unavailable. age now decrypts with the age
library and Vault reads over its API (KV v1 or v2, detected as the CLI
does), so neither needs a CLI on the host. SOPS still uses the CLI, whose
library would pull in every cloud KMS SDK, but decrypts the whole file to
JSON and looks the key up itself, so the key never reaches the CLI.
Errors say what GitHub refused in its own words instead of the request URL
and an empty field list. Webhook review states arrive lower-case and were
never normalised, so a webhook-delivered change request did not read as one.
A review the token would post as REQUEST_CHANGES on its own pull request
comments instead, which GitHub accepts. Secondary rate limits wait up to two
minutes and retry.
The channel ran a hand-written SMTP listener and trusted the From address,
so anyone reaching the port could act as any user. It now uses go-imap,
go-message, go-msgauth and go-smtp; settings change accordingly.