v0.11.0 — Release notes

Agent-ready: MCP 2026-07-28, rebuilt webhooks, sequential release

Everything an operator or planner can do in the app can now be done by an AI agent or an ERP through the same rules: an MCP server on the 2026-07-28 specification with 113 tools, webhooks rebuilt for production, a sequential-release setting, a buffer that follows the routing, and the MQTT publisher removed.

Added

MCP server on the 2026-07-28 specification

Stateless Streamable HTTP or stdio, 113 tools with annotations and output schemas, and a test that proves every REST endpoint and database action has a tool. Starting, pausing and completing go through the same database function the terminal uses, so timers, job state and sequential release apply to agents too. Generate the server configuration from the new MCP page in the admin.

Added

Webhooks rebuilt

One database trigger emits 36 events with a versioned payload and a timestamped HMAC signature. Deliveries are retried five times, logged with status and latency, and can be re-sent or tested from the admin page. Endpoints that keep failing switch themselves off.

Added

Sequential release setting

Turn it on under Organization settings and an operation can only start once every earlier operation on the same part is completed. The database enforces it for the terminal, the API and agents alike. Off by default.

Added

Drop-off locations in the demo

The onboarding wizard asks whether you use drop-off slots and seeds them per cell. The work queue shows where a part is, and the Location tab shows free slots at the next cell.

Changed

In Buffer means the part is ready

In Buffer lists operations whose earlier steps are completed. Expected lists the ones still waiting upstream. Starting work while clocked on another operation switches instead of failing, and rule violations are shown in your language.

Changed

Faster admin, tighter database

Half the JavaScript on first load, on-demand language catalogs, fewer round trips on the dashboard and assignments, twenty new indexes and rewritten row-level security policies. Anonymous clients can call eight pre-login functions and nothing else.

Removed

MQTT publisher

It never opened an MQTT connection and was never tested. Use webhooks and bridge to a broker outside the app. The in-app Swagger page went too; the REST reference lives here.

A tester asked whether the operation sequence is a real dependency or just information. It was information, and the terminal’s buffer did not even look at it. That question turned into the release: the buffer follows the routing, one switch enforces the sequence, and every rule now lives in the database where the terminal, the REST API, webhooks and the MCP server all go through it.

There is no compatibility layer. Webhook consumers move to the new payload and signature, MCP clients speak protocol 2026-07-28, API clients handle 409 for rule violations. The changelog lists the migrations to apply in order.