v0.7.0 — Release notes

Location-aware work, issue reporting, and operator modes

Four areas tightened at once: parts that know where they are and where they go next, issue reports that carry cell context, work queues that read like real manufacturing, and an operator terminal that tells setup apart from production.

Added

Location-aware issue reporting

A quality issue now records where the part was and where it was headed next. The route stays attached to the problem, so a planner or operator can act without reconstructing it afterward.

Added

Batch production mode

A batch can run in manual or automated mode. Automated mode is reserved for laser-nesting batches, where one program drives the whole nest.

Added

Resources assigned to cells

Machines and resources can be tied to the cells they belong to, so the queue and the floor agree on what runs where.

Added

Operator terminal work modes

The terminal separates setup and prep from production. A shared terminal handles login and operator switching, so one tablet serves a real cell instead of one fixed user.

Added

Scan a CNC program from the terminal

Operators can scan the program name straight from the terminal detail panel, so the right file loads at the machine without retyping.

Fixed

Admin Users page rendered raw keys

A translation namespace clash dropped most of the Users page labels. Fixed the merge and filled the missing translations across English, Dutch, and German — no more raw keys on screen.

Fixed

API key generation on the hosted app

Generating an API key and uploading storage failed from the hosted frontend. Cross-origin handling now matches the request against an allowed list instead of a single hardcoded address.

Changed

Admin polish across Operations, Assignments, and Parts

Translated the last hardcoded English, added labels to icon-only buttons, and evened out page spacing and loading states.

v0.7 closes the gap between what happens on the floor and what the system knows about it. A part carries its current cell and its next one. An issue holds that same context, so a problem points back to where it started. The work queue reads in manufacturing terms (material, thickness, tooling, batches) instead of a flat task list. And the operator terminal knows whether work is ready for setup or ready for production, on a tablet that a whole cell can share.