v0.4.1 — Batch Lifecycle Fix + Docs Cleanup

Fixes the batch/nesting lifecycle and cleans up documentation.

Batch Lifecycle Fixed

The CAD/CAM nesting workflow now works end-to-end:

• Batch create with operations and nesting metadata (sheet size, utilization, CAM program)
• Machine-reported start — operator_id is now optional, supporting CAD/CAM integrations where the machine reports batch start directly
• Machine-reported stop — works without time entries, marks all operations as completed
• Time distribution — when an operator is involved, time is distributed across operations weighted by estimated hours

Root cause was RLS policies on batch_operations and operation_batches that blocked Edge Function access. Fixed with migration.

CSV Import Fixed

api-parts/bulk-sync and api-operations/bulk-sync were missing enableSync — CSV import for parts and operations silently failed. Now works. E2E test passes 15/15 against production.

Documentation

• Removed 25+ hallucinated features from docs (drag-and-drop assignment, quality dashboards, wrong API endpoints, fake MCP tools)
• New feature pages: QRM & Flow Control, Operator Terminal, Batch & Nesting
• Rewrote Operator Manual and Admin Manual as proper guides
• CSV import page with download links to Dutch job shop templates
• Fixed tool counts (55→50), webhook schema (event_type→events array), removed ALPHA banner
• Sidebar restructured: core features first, API section trimmed

Templates

CSV import templates included at templates/csv/ with realistic Dutch manufacturing data.

---

Full Changelog: v0.4.0...v0.4.1

v0.4.0 — QRM Terminal & POLCA Capacity Signals

Job shops run on flow. When work piles up at the press brake because laser kept feeding it, you get bottlenecks and missed due dates. This release brings QRM principles into the operator terminal — capacity problems visible before they happen.

POLCA Cell Signals

Cell column shows where a job is and where it goes next, with a live GO/PAUSE signal. If the downstream cell is near capacity, operators see a pause icon. Core POLCA: don't release work unless the next cell can absorb it.

Operator Status Bar

Diagonal stripe patterns signal operator state at a glance: green (active), yellow stripes (idle — not clocked on), red-to-green (rush order), amber (stuck >2h). Shows operator name, current operation, live timer.

Rush & Hold

Two toggles in every operation detail panel. Rush sorts jobs first everywhere and changes the status bar. Hold pauses operations with visibility in queue headers. Foremen set these from any device.

Backlog Status & Section Totals

Terminal shows "Te laat" / "Vandaag" / "Binnenkort" per row. Section headers and kanban columns show total hours, pieces, rush count, hold count.

Batch API

New endpoints for nesting/batching: api-batches (CRUD) and api-batch-lifecycle (start/stop/add operations). Ready for nesting software integration.

Work Queue Kanban

One column per manufacturing cell with totals. Operation detail modal now includes full routing visualization.

Architecture & Stability

Decomposed 6 oversized modules into 30+ focused ones. 98 new tests (617 total). 25 API bugs fixed. Flow column rebuilt from scratch.

---

Full Changelog: v0.3.3...v0.4.0

v0.3.3

Eryxon Flow 0.3.3

Patch release finalizing the integrated work from PRs #434 through #438.

Included

• merged security hardening, route refactor, API docs, E2E tooling, and 3D viewer measurement work from the parallel PR stack
• aligned release packaging, documentation, and repository structure
• refreshed non-breaking app and docs dependencies
• consolidated all maintained docs into the website/ documentation tree
• updated architecture docs for security boundaries, API authentication, and the current 3D viewer runtime model

Validation

• npm run lint
• npx tsc --noEmit
• npm run test:run (442 tests passed)
• npm run build
• cd website && npm run build

Upgrade Notes

• version: 0.3.3
• primary migration: supabase/migrations/20260202200000_fix_signup_notification_trigger.sql
• configure the notify-new-signup Supabase Database Webhook explicitly in each environment

Follow-up

• one moderate transitive swagger-ui-react / dompurify advisory remains and requires a forced dependency change; it should be handled in a separate maintenance PR