platform/model
Database models live here and are the source of truth for table structure. Migrations must reference these models or be kept in sync with them.
Required model groups:
- users and roles.
- game management plugins and installed plugin versions.
- server instances and config versions.
- AI providers and secret references.
- run endpoints and capabilities.
- jobs and job events.
- artifacts and chunks.
- log streams and ingestion cursors.
- audit events.
- durable alerts and their acknowledgement/resolution audit links.
- server-bound plugin lifecycle installations and linked jobs.
- reviewable AI config diffs and approval fences.
Every implemented database model must include field comments, JSON/database tags, and an explicit table name function or equivalent mapping in the chosen stack.
Durable Client Manager persistence
File and MySQL stores persist the Client Manager installation aggregate, component sessions, registration nonce fences, and lifecycle audit references. Session tokens are stored only as hashes; nonce and heartbeat sequence checks are bounded and restart-safe. Reset, ownership/endpoint reassignment, update activation, rollback, revoke, and uninstall fence or expire component sessions without deleting distribution or audit history.