Audit Log For Admin-UI Actions

MCPX now keeps an append-only audit log of important Admin-UI actions, so administrators have a reliable record of who did what, when, and from where - supporting accountability and compliance reviews.

What gets recorded

Each audited action captures:

• Actor - the acting user (id, external id, email, and role).
• Action & resource - what was done and which resource it affected.
• Context - IP address and user agent of the request.
• Time & status - when it happened and, for fallible actions, whether it succeeded.

Records are stored reliably in Postgres and can be retrieved newest-first and filtered via an admin-gated API.

Data-protection rule

The audit log stores references, never sensitive values - it records the identity of a resource that changed, not the secret or configuration content itself. Audit writes are best-effort and fire-and-forget, so a transient logging failure never blocks or breaks the underlying admin action.

This release ships the backend and API. The Admin dashboard view that surfaces the audit trail follows in an upcoming release.