Changelog

Licences replace the browser-confirm onboarding. A machine now joins the studio by claiming a licence, and the licence's type decides who owns the machine.

Added

• Licences — one-shot tickets that authorise exactly one agent registration. Each licence carries a type (personal or lab), a status (pending, consumed, revoked or expired), an optional label and location, and an optional expiry date.
• Personal licences — every signed-in person issues their own from the Personal Center. The code is shown once, at issue.
• Lab licences — administrators issue them from Admin → Licences for the shared benches.
• The Personal Center — the licences you issued and the machines they registered, in one place.
• Ownership by licence type — a machine registered with a personal licence belongs to that person and appears under My Computer; a machine registered with a lab licence belongs to the lab. Where the machine physically sits makes no difference.
• Licence preview — the agent's own page asks the studio what kind of licence a code is before anything is registered, so the operator sees the outcome first.
• In-place re-registration — an agent that comes back with its own agentId and agentSecret is updated rather than duplicated, keeping its identity and its place in the pool.
• Licence endpoints — GET /api/licenses, POST /api/licenses, POST /api/licenses/{id}/revoke and DELETE /api/licenses/{id}.

Changed

• Registration — POST /api/agent/register now takes a code and answers with licenseType, scope and ownerUserId. Presenting a code that was already spent is refused with used.
• The agent's own page — the registration form asks for the studio URL, the agent name and the licence code, with a Check licence action that previews the outcome.

The first release of DK Studio. It is deliberately narrow: everything listed here works end to end, and nothing else is claimed.

Added

• First-run setup wizard — licence key, database driver (SQLite, PostgreSQL or MySQL), schema initialisation and the first admin account.
• Agent licensing — issue a licence from the admin screen, watch agents claim them, revoke them when a machine is retired.
• Agent registration — the one-time handshake that gives an agent its id, API key and secret, with in-place re-registration.
• Live presence — which agents are connected, derived from the socket rather than a stored flag.
• Remote commands — shell, get_system_info, get_serial_ports, open_serial, close_serial and serial_write, delivered over the socket with an HTTP polling fallback.
• Agent console — a serial console on the agent's own page, streaming the port over server-sent events.
• Users and roles — admin, engineer and viewer, a session cookie and an admin screen for creating users.
• REST API — the same operations, scriptable, plus the agent-facing registration, auth, heartbeat, command and result endpoints.
• Documentation site — this site: sixteen pages across Introduction, Getting Started, Guides and Reference, in fifteen languages.