All sprint evidence in one dashboard

Cashier risk actions need manager approval, audit evidence and CSV export.

OTP, WhatsApp, Telegram, email and LAN notifications start behind audited outbox contracts.

Real providers stay dry-run and env-gated until operator setup.

External messages require consent, template rules, audit and blocked secret payload fields.

Customer opt-in, opt-out and transactional messaging decisions are audited before external sends.

OTP, WhatsApp, Telegram, email and LAN in-app sends are simulated with audit evidence.

OTP, WhatsApp, Telegram, email and LAN in-app providers are mapped with health and failover rules.

Notification sends are blocked, mocked or routed to LAN fallback before real provider calls.

External notification delivery uses consent/env gates, retry backoff and dead-letter audit.

WhatsApp and Telegram inbound webhooks require secrets, replay protection and audit.

WhatsApp and Telegram inbound events write to audited outbox before order or POS workflows.

WhatsApp and Telegram commands cannot bypass POS button workflow or manager approval audit.

Owner/admin cloud auth is env-only while POS/waiter/kitchen LAN fallback remains independent.

Google Tag, Cloudflare and product metrics stay privacy-safe and dry-run.

Analytics events are gated by consent, PII, kill switch and LAN-safety rules.

Cloud backend does not take authority away from POS Local Hub.

Firebase, Cloudflare, notification and AWS env names are mapped to value-free runtime storage targets.

Cloud sync queues later without blocking LAN order, print or approval flows.

QR, website, POS and waiter orders are accepted once and routed to core destinations.

Station-scoped printer jobs are idempotent and duplicate-safe.

POS, waiter, kitchen and printer devices stay visible without internet.

Firebase, Cloudflare, Google, notification and AWS env names are scoped without values.

AWS/Nginx/Cloudflare smoke checks use value-free health JSON.

Current sprint QA markers, runbooks and safety flags are visible in one local dashboard.

Local pages and mock APIs are grouped for GitHub/AWS operator smoke checks.

Staging DNS, TLS, proxy, smoke and rollback steps stay manual and production-safe.

Subdomain, custom domain, QR and website routes resolve tenant before order ingest.

Public QR and website submits map to tenant domain routing and order ingest without payment capture in QA.

QR, website and POS menu visibility require active products, modifiers and kitchen printer routes.

QR and website totals must match order ingest before any payment capture or cloud sync.

Pay-at-counter and cash-on-delivery are mock-ready while online card stays provider-disabled.

QR and website order confirmations write audited outbox records before any provider send.

Customer-facing public order status is read-only and cannot mutate POS, kitchen or printer state.

QR and website receipts link pricing, payment, confirmation and status evidence without mutation.

Receipt delivery writes audited outbox records before WhatsApp, email or Telegram provider sends.

Public receipt/status links are masked, read-only and blocked from order, payment, receipt or provider-send mutation.

Public receipt reads are rate-limited, replay-protected, bot-guarded and audited without blocking LAN authority.

Public receipt revoke, expiry and restore-denied decisions are audited without mutating source links or LAN authority.

Public receipt payloads preserve customer totals while blocking internal ids, provider targets, audit ids and raw contact values.

The dashboard shell is grouped, denser and operator-focused without changing POS cashier behavior.

Mobile, tablet and desktop screenshots must prove no horizontal overflow before design handoff.

Manual GitHub push and AWS staging handoff paths stay explicit without performing external mutation.

Server, Nginx, env storage and route smoke checks stay staging-only and value-free.

Firebase, Cloudflare, tags, OTP, WhatsApp, Telegram and email stay dry-run and env-gated.

Provider readiness is visible without exposing env values, secrets or performing live calls.

External services can be disabled while POS, waiter, kitchen and printer LAN authority remains active.

Sprint continuity and AI CTO/Senior DevOps/Senior QA role rules are recorded as standing project policy.

MUPZAAI can guide patterns read-only without modifying it or using secrets.

Push candidates are scanned for env files, keys, service accounts and provider tokens.

Generated folders and secret-bearing files are blocked before GitHub push.

Operator receives safe manual GitHub/AWS staging steps without repo-side mutation.