0.25.19
2026-05-29 — current release.
Highlights
Vantage cockpit: metadata-only metrics endpoint
A new read-only GET /api/v1/metrics/vantage endpoint exposes
aggregate health and counts for the Seglamater Vantage operator cockpit.
Returns version, instance hostname, database health, uptime, and total
workspace / member / channel / message counts — no message
content, no per-user data, no PII. End-to-end encryption on chat
messages is unaffected and remains intact even if a poller token is
exposed.
Access requires a new bot token scope — mint via
POST /api/admin/bots/{id}/tokens with
{"label":"vantage-reader","scope":"metrics"}. JWT (human)
sessions and standard (scope=default) bot tokens are
rejected with HTTP 403 even when the underlying account is admin.
Existing bot tokens default to scope=default and behave
exactly as before.
Admin → Bots: easier community management
The bot row's Tokens button is now labeled Manage — it always opened the full bot detail panel (tokens, communities, bio), but the old label hid the door. Each row now also shows a Communities chip: yellow “No communities” for bots that aren’t yet a member of anything (the typical state right after provisioning), neutral count for those that are. Single round-trip backend query; no N+1.
Database
Migration 063_bot_token_scope.sql adds scope TEXT NOT
NULL DEFAULT 'default' on bot_tokens with a
CHECK constraint over ('default','metrics').
Existing rows fill with 'default'; no behavior change for
tokens already in service.
Upgrade
Managed instances apply this release via the in-app Admin → Updates page (signed image + HMAC-authenticated apply). Migration runs at startup. No operator action required beyond clicking Apply.
For self-hosted installs, pull the new image and restart per the self-hosting guide.
Signing
Verify the image signature before pulling:
cosign verify \
--key https://updates.seglamater.app/.well-known/keys/chatalot.pub \
registry.seglamater.app/seglamater/chatalot:0.25.19
Tickets
- CHAT-174 — Vantage cockpit metadata-only metrics endpoint (preserve E2EE)
- CHAT-3f242d36 — Bots admin: rename Tokens → Manage, add Communities chip
- CHAT-cf361bae — Phase 2 follow-up (scoped bot tokens: catalog + middleware enforcement)
Full per-commit history is in CHANGELOG.md in the canonical repository.