# Verification — 6 October 2026

Environment: Windows, Python 3.14.5, Node 24.16.0 (Node is used only for the JavaScript syntax check).

- `python -m unittest discover -s tests -v`: **21 tests passed**.
- Python source parsed successfully.
- `node --check static/app.js`: passed.
- Browser: admin login, explicit fictional demo initialization, Hinglish incoming order, product/date confirmation proposal, customer HAAN confirmation, scheduled order table and manual edit/save verified.
- Screenshot: `dashboard-preview.jpg`, taken from the running demo workspace.

Tests cover: missing-area/address follow-ups, no order before confirmation, duplicate provider IDs, duplicate order review, repeat draft confirmation, unknown/ambiguous products and units, media retention, AI failure/low confidence (mocked), cutoff equality, same-day cutoff, holiday/departed/disabled routes, backup consistency, transactional CSV import, number/customer isolation, source-event adapters, authentication/CSRF/static-file restrictions, signed webhook persistence/idempotency, staff/driver role boundaries, staff review booking and preserved unknown-number events.

The logged unknown-number error during the failure-retention test is expected: the test verifies the raw event remains available instead of disappearing.

Not verified: real Meta credentials/token permissions/message delivery, actual Ollama inference/model-language accuracy, printer output, multi-browser print pagination, production concurrency/load, external hosting, multi-instance behavior or disaster recovery. The running workspace contains six fictional customers and one simulated order; no live customer message was sent during verification.

## Linked-device update

28 tests passed after adding linked history import and manual keyword flows. A real QR was displayed, the user linked their phone, the saved session reconnected, and the queue drained completely. At that point 2,538 chats and 8,583 unique WhatsApp messages were committed; the customer/contact table contained 1,644 records including the existing demo entries. There were zero enabled flows and the only outbox records remained the two original simulated replies. Actual WhatsApp outbound sending was not exercised. The user's chat data and session files remain in the local data folder and are not included in the source ZIP.