# Task List — Livewire Real-Time Restaurant Panel

Simple checklist. Each task links to the doc with the relevant facts — read that before starting,
but how you build it is up to you.

## 1. Get real-time actually working

- [ ] Fix the broadcasting-auth endpoint mismatch so a private channel can be subscribed to from a
      Livewire page at all. ([01](01-realtime-setup.md))
- [ ] Confirm it: subscribe to any private channel and check the auth request succeeds.
- [ ] Decide whether staff accounts should be able to log into the Livewire panel — right now they
      can't. ([06](06-tenancy-permissions-policies.md))

## 2. Live order queue

- [ ] A page listing a restaurant's orders, filterable by status.
- [ ] Accept / decline actions on a pending order.
- [ ] The list updates itself when an order's status changes elsewhere (mobile), instead of
      needing a manual refresh.
- [ ] ([03](03-services-orders-and-dispatch.md), [05](05-order-status-and-dispatch-flow.md))

## 3. Dispatch board

- [ ] Show what's happening as an order gets offered to drivers, claimed, or times out.
- [ ] A way to see which drivers are currently eligible for an order and manually offer it to one.
- [ ] Surface orders that failed automatic dispatch and need manual attention.
- [ ] ([03](03-services-orders-and-dispatch.md), [05](05-order-status-and-dispatch-flow.md)) — this
      one has no mobile screen to mirror, it's new

## 4. Live delivery tracking

- [ ] A map/view showing the assigned driver's position updating live for an order that's on its
      way.
- [ ] ([02](02-broadcast-reference.md))

## 5. Chat

- [ ] View an order's conversation thread(s) and send/receive messages live.
- [ ] Handle photo/voice-note attachments.
- [ ] Unread indicators, per participant (remember: several staff can share one thread).
- [ ] ([04](04-services-other.md), [08](08-mobile-endpoint-map.md))

## 6. Access control pass

- [ ] Make sure owners and staff only ever land on their own restaurant's pages, not an open
      restaurant-by-id route like the admin panel uses.
- [ ] Gate every new page/action with the right restaurant/staff permission — not the admin-only
      permission names the existing back-office pages use.
- [ ] ([06](06-tenancy-permissions-policies.md), [07](07-existing-admin-panel.md))

## Suggested order

1 → 2 → 6 (do access control alongside the order queue, don't bolt it on after) → 3 → 4 → 5.
Chat is self-contained and can happen in parallel with 3/4 if there's more than one person on this.