Sync the self-hosting stack

2026-09-08 08:01:10 +02:00
parent d53062d14e
commit 9b7a93452a
1 changed files with 26 additions and 0 deletions
@@ -9,6 +9,32 @@ one of them changed. An entry says which artefact and which version, so `web 0.1
 Every version published to a channel appears here. Nothing is written from memory afterwards: a build
 cannot be published without its entry.
 ## 2026-09-08 — Nobody running Jarvis could tell how much it was actually being used `api 0.107.0` `web 0.130.0`
 A platform administrator had no way to answer "is this instance quiet or busy, growing or stalled,
 used by three people or by thirty" — only the individual screens for organizations, conversations and
 agents, none of them a total, none of them over time.
 **A new "Statistics" page**, under Settings, visible only to a platform administrator. It shows the
 instance as a whole: how many users, organizations, assets and agents exist right now, how many
 conversations and messages have been sent, and how each breaks down — assets by type, agents by
 status, messages by who sent them.
 **Trends, not just totals.** A day-by-day chart of new users, new conversations and new messages, over
 the last week, month, quarter or year — each on its own scale, because a shared axis flattens a
 handful of new users next to a few thousand messages into a line that says nothing.
 **Who is actually using it.** A sortable, searchable table of every user, ranked by conversations
 owned and messages sent, alongside when they last did anything and when they last signed in — the list
 an administrator reaches for when a licence renewal asks whether a seat is worth keeping.
 Two new database indexes ship with this release, applied the same way every schema change here is:
 automatically, when the api starts. They only add — nothing is dropped, nothing becomes unique, so the
 schema guard has nothing to refuse.
 No new environment variable, no new permission: an existing platform administrator sees the page the
 day this lands, anyone else does not see it in the menu, and a direct API call is refused.
 ## 2026-09-04 — An approval asks for your decision once, not twice `web 0.129.0`
 **A request waiting on you carried Approve and Reject on the card itself, and pressing either one