Design and implement web-based daemon console

[wauputr4]

Goal

Add a lightweight web console for inspecting the local daemon.

Scope

• Inspect customers, tickets, messages, agent runs, memory files, and owner summaries.
• Add basic operational controls such as pause profile, retry run, and gateway health.
• Keep design focused on operations, not a marketing site.

Acceptance Criteria

• Operator can monitor Wasila without reading SQLite manually.
• Console does not expose secrets.
• Access control plan is documented before production use.

[wauputr4]

Post-v0.1 UI scope, ponytail version: don't build a full console yet. Build the smallest read-only human monitor first.

Minimal pages:

1. Dashboard: daemon health, active profile, gateway types, recent errors, counts today.
2. Conversations: customer list + latest message + status/risk; click into one thread.
3. Conversation detail: chronological chat, customer response, owner/private-assistant notes, ticket links.
4. Customers: customer profile/memory summary, gateway identifiers, recent tickets/messages.
5. Tickets: open/closed list, priority, latest update, owner escalation flag.
6. Agent runs / traces: workflow run, CrewAI/private assistant result, skill executions, failures.
7. Settings read-only: provider, customer gateway, owner gateway, data paths; redact secrets.

Skip for first UI: write actions, auth system, analytics charts, live websockets. Add those only after read-only monitoring proves useful.