Complete Captain service preparation, delivery status and staff controls

[sridharkalaibala]

Captain service changes need to retain each preparation independently, keep held food out of the kitchen until explicitly sent, and show what reached each kitchen destination. This adds stable order-line identity, seats/courses/allergies, idempotent hold/fire, scoped staff handover and manager approval with reasons/audit, plus per-printer delivery and renderer-confirmed kitchen display status. Quantity edits keep receipt fields consistent; missing new catalogue items refuse the complete edit instead of disappearing.

Integrated with current develop kitchen audio/board work. Both boards exclude held food and show allergy details. Spoken announcements read all items in queue order. Currency precision follows shop metadata while stored payment snapshots retain their original units. The companion Captain app enables preparation controls only when this server advertises support. POS is 1.8.4; distribute a local Windows installer, not a public POS release.

Validation: 11,427 API checks passed (11 existing skips), 3,539 desktop checks passed (5 existing skips), 15 targeted quantity/service checks and 17 metadata/approval checks passed. ESLint has zero errors; formatting, generated API documentation, attribution, frontend build and packaging dependency checks passed after the release metadata updates. Physical device/printer acceptance remains for the user.

[github-actions]

Merged to develop. Anyone can test this - you do not need write access.

Try it at https://develop.posnic.io, or run it yourself:

git fetch origin develop && git checkout develop
npm install && npm --prefix api install
npm run dev   # then http://localhost:3000

When you have tested it, say what you did and what happened, and set
QA passed or QA failed. If you cannot set labels, just comment -
a maintainer will.

Reporting that something is broken is as useful as fixing it. It is
better found here than by a shopkeeper.