v0.10.0 — Release notes

A shared responsive interface and a stronger maintenance baseline

Community now uses one responsive operator interface. This release fixes tenant boundaries, PIN sessions, production transactions, and the release workflow. PWA installation is optional.

Changed

One interface across devices

Phones, tablets, and desktops use the same operator queue and details. Existing mobile bookmarks redirect to the shared routes. The standard web app works without PWA installation.

Fixed

Reliable production changes

Operation, batch, and time-tracking changes run in database transactions. Concurrent requests cannot partially start a batch or create duplicate active timers.

Fixed

Tenant and terminal boundaries

Tenant permissions, storage access, invitations, and API writes enforce ownership. PIN verification binds an employee to the current terminal session and preserves that identity in time reports.

Fixed

Self-hosted backends outside supabase.co

A container pointed at your own Supabase host, a LAN address or a custom domain now adds that origin to the Content Security Policy when it starts. Runtime settings are written as plain data, and an invalid backend URL stops the container instead of serving a page that cannot connect.

Fixed

No production actions without a verified PIN

A shared terminal signed in with an operator account must verify an employee PIN before starting, pausing or completing work. Old /m links and the operator routes send an unverified terminal to the PIN screen, and the database refuses lifecycle writes without a verified employee session.

Fixed

One start event per operation

Stopping and restarting a timer on an operation that is already in progress no longer sends a second operation.started webhook or MQTT event.

Fixed

Batch images before the batch exists

Nesting and layout images chosen while creating a batch upload to a tenant-scoped staging location, so the upload succeeds before the batch is saved.

Changed

Reviewed releases

Release checks cover the app, documentation, API helpers, MCP server, and a clean local database. Releases record their exact source commit and image digest. Production rollout remains an explicit action.

This release concentrates on reliability and maintenance. Duplicate mobile pages, unused widgets, and divergent database types have been removed. The application uses the same responsive interface across device sizes; PWA installation is an optional build setting.

Self-hosters must apply the included database migrations before deploying the matching frontend and Edge Functions. Back up the target and check existing tenant references first. Terminal users must verify their PIN again after upgrading.

Community retains its existing Business Source License 1.1. See the repository changelog and release runbook for detailed validation and deployment requirements.