Feature: Shift lifecycle management, cash drawer reconciliation, & business day close

[khaira777]

Operations & Shift Management Feature Request

Extracted from fork codewithsharma/FloCafe (branch: develop):

Overview

Full shift management lifecycle, cash drawer float tracking, drawer count reconciliation with variance calculation, shift enforcement middleware, and business date day-close reporting.

Proposed Changes

1. Shift Schema & Migrations:
   • Migration 69 (shifts table, shift_id on orders and bills, indices) and Migration 70 (expected_cash_cents and variance_cents columns on shifts).
2. Shift Lifecycle & Cash Reconciliation:
   • Open shift modal (opening float input), Close shift modal (cash drawer count), Force close shift option.
   • Shift reconciliation logic comparing system-calculated expected cash vs actual cash count to determine variance.
   • Reference: main/services/shift.ts, frontend/src/components/shifts/.
3. Shift Enforcement Middleware:
   • Option to require an open shift prior to performing cash transactions.
   • Reference: main/middleware/shift-enforcement.ts.
4. Day Close & Business Date Accounting:
   • Migration 71 (day_closes table storing business date, closed user, and summary JSON).
   • Timezone-safe local day boundary calculation (localDayBoundsUtc) to avoid UTC vs local business day discrepancies.
   • Reference: main/services/day-close.ts.

[khaira777]

Verdict: VALID ENHANCEMENT — large; needs product decision before implementation

Findings:

• No shifts, day_closes, drawer-float, or enforcement logic exists on main (the only "shift" hit is a timezone comment at main/db.ts:4785). X/Z report menu items (main/index.ts:529-530) just navigate the renderer to the reports page; reports.ts has daily-stats (main/routes/reports.ts:105) but no business-day close.
• Timezone-aware local-day logic already exists for order/bill numbering (dateStampInTimezone, see feat: configure invoice numbering #297) and is reusable for localDayBoundsUtc-style day boundaries.
• Migrations 69-71 referenced are fork-only; current schema is v68.

Suggested scope (MVP first): shifts table + open/close modals with opening float and drawer count + expected-vs-actual variance; then shift enforcement middleware and day-close accounting as separate follow-ups. Overlaps: #278 (cash refunds in day-close expected cash), #287 (SHIFT_START/END audit events), #280 (inventory snapshot at close). Maintainer decision needed: is shift enforcement a desired workflow change (forces open shift before cash transactions)?