R1.5 (NIX-OS-67) — POSID-NNNNN daily sequence (local)

3/3 local Gate 1 checks passed. Format helper handles padding cases (4-digit seq, 3-digit config, overflow). DAO advances correctly, resets independently per business_date (proving daily reset), and survives a 5-way parallel advance that returns exactly {1,2,3,4,5} — the atomic INSERT … ON CONFLICT DO UPDATE … RETURNING holds the row lock so no two orders can share a number. Timezone math verified: 18:00 UTC in Asia/Phnom_Penh resolves to the next day — cashiers close shift at 22:00 local, not UTC.

Gate 2 (prod) will prove the end-to-end flow. Ring a cart, check out, inspect the receipt (should show POS{N}-0001), verify cafe.pos_sequences has a row with next_seq=2, and confirm Odoo pos.order.name carries the NIX-issued number too.

00What's new

lib/db/pos_sequences.ts (new) — advanceSequence via atomic UPSERT+RETURNING, peekSequence, businessDateForTimezone, formatPosOrderNumber. Table cafe.pos_sequences already shipped in R1.2 — no new migration.
lib/tenant.ts — TenantConfig gains timezone (read from public.tenants.timezone, default Asia/Phnom_Penh).
lib/odoo/queries.ts — createPosOrder accepts optional overrideName; when provided, it rides on both pos.order.name and pos_reference so receipts and order history both show it.
/api/odoo/order — advances the per-register daily sequence before calling Odoo, formats the NIX order number, passes as overrideName. Gracefully falls back to Odoo's auto-generated name if sequencing fails (log + continue).
Register / PaymentModal — client now sends posConfigId in the order POST so the API has what it needs.

R1.5 — POSID-NNNNN daily sequence LOCAL

00What's new

01Format helper — padding rules✓ 5 assertions

02DAO — advance / peek / daily reset / 5-way concurrency✓ 9 assertions