The connector sent title and body as one sendMessage, so any notification
over Telegram's 4096 UTF-16 unit limit was refused with 'message is too
long' and, because a delivery is retried until the channel confirms it,
retried every ten minutes for ever without ever arriving. The chat channel
had its own splitter; both now share one in sdk/telegramtext, which counts
UTF-16 units rather than runes so an emoji-heavy body isn't over the limit
either.
The manifest now carries an authority block naming the api credential
service, so the marketplace view shows the slot instead of relying on
the description text. The client takes the full Authorization header:
the api slot accepts a basic username/password or a bearer token,
setting both is an error. Egress stays operator-supplied at accept time
because the instance host comes from the instance_url setting, which a
static egressHosts list cannot express.
Live testing against dev483891 surfaced four gaps the fake hid: write
responses wrap the row in result, reference fields come back as
display_value objects without display_value=true, the blackout table is
cmn_schedule_span (spans of schedule.type=blackout), not cmn_blackout,
and an approval updates sys_updated_on without moving sys_id, so the
poll cursor is now sys_updated_on|sys_id bounded above by the current
time. Approval values are compared case-insensitively. Adds a regression
test for the in-place approval. All lookups, deliveries and the
approved/rejected event path verified live; test rows cleaned up.
client.go holds the Table API client (instance URL setting, basic
credential in the api slot). incident.go delivers create/update with a
note and polls incident.updated. change.go raises and withdraws change
requests idempotently on correlation_id and turns approvals into
change.approved and change.rejected events. cmdb.go resolves owner,
delegate, support group, environment and data class through
cmdb_ci_server, cmdb_ci_appl then cmdb_ci. calendar.go answers active
blackouts for the Timing guard. listen.go polls both tables with a
chg/inc cursor. Built against a developer instance; tests fake the
Table API.
Each template the operator declares becomes an action with the effect declared
for it, so judgement decides on the declaration. A launch carries Archie's
idempotency key in the task message; invoking again finds that task instead of
launching another, so a resumed run never launches twice. A task that ends in
error is a known failure; one still running at the deadline is unknown.
Lookups run no guards and the helpers read as root, so an instruction injected
into an event could steer the agent into listing anywhere on the host. Each
host now names the roots its lookups may look under, and any other path is
refused before a command is built.
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.
Mirrors archie-core's proto/forge/v1 change: the SDK Forge interface and
server dispatch gain CreateIssue; gitea resolves label names to IDs
(creating missing labels) and github passes label names through.
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.
AcceptInvitations accepted every pending repository invitation, so any
GitHub user could add the forge's account to a repository by sending an
invitation. The host now passes the connection's configured repositories
in AcceptInvitationsRequest and the extension leaves an invitation to
anything else pending. The Gitea forge is unchanged: it has no
invitations to accept.