internal/

Package admin is the operator's panel: sign in, sign out, a layout, and one page that says what this server is and how it is doing.

Package api is version 1 of the sim telemetry API: the contract a telemetry client talks to, exactly as docs/API-V1.md defines it.

Package app is the server's runtime: it decides which mode to start in, builds the listeners for that mode, and switches between them without the operator having to restart anything.

Package auth holds the server's credentials: how a password is hashed, how a random token is minted, and how any of it is compared.

Package buildinfo reports which build of the server is running.

Package clientbuild turns one prebuilt Windows client into a client that knows this team's address.

Package config is the server's configuration: the small file beside the binary, the environment variables that override it, and the organisation settings that live in the database.

Package db is the only package that speaks PostgreSQL.

Package driverauth holds a driver's session.

Package httpx is the server's HTTP plumbing: the hardened http.Server, the middleware every route wears, and the decoders that read a request body.

Package logging builds the server's one logger: slog, JSON, to stdout, with a redaction layer wrapped around it.

Package metrics is the private port: Prometheus counters and pprof, bound to loopback and nothing else.

Package packaging describes what a release package contains.

Package plugins runs the server's plugins.

Package pluginweb mounts every plugin that asked for a route.

Package setup is the first-run wizard: the only thing this server serves until an operator has told it what it is.

Package web holds what the server-rendered pages share: the one stylesheet, and the template helpers that format a number for an operator.