2 Commits

Author SHA1 Message Date
root
cd1fda3e21 Fix: CORS + relative URL + Langfuse tracing wired into gateway
Three fixes:
1. CORS headers on all gateway responses (browser dashboard was
   blocked by same-origin policy)
2. Dashboard JS uses window.location.origin instead of hardcoded
   localhost:3700 (LAN browsers couldn't reach it)
3. Langfuse tracing wired into every gateway request — api() wrapper
   creates spans for each lakehouse call, logGeneration for LLM calls.
   Week simulation now produces 34 observations per run visible in
   Langfuse UI.

7 traces confirmed in Langfuse after restart. Every /sql, /search,
/vram, /simulation call is tracked with timing + inputs + outputs.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
2026-04-17 00:53:18 -05:00
root
4a2bfce6e0 Week simulation + live dashboard + self-orientation + verification
Week simulation engine: 5 business days, 4-8 contracts per day,
3 rotating staffers with handoffs between days. Runs hybrid search
per contract via the gateway. 28 contracts, 108/108 filled (100%),
5 emergencies, 4 handoffs, 3.2s total.

Dashboard at :3700/ — dark theme, shows:
  - Contract cards sorted by priority with match status
  - Day navigation across the work week
  - Week summary stats (fill rate, emergencies, handoffs)
  - Live alerts (erratic/silent workers)
  - Playbook entries
  - Real-time service health + VRAM

Self-orientation (/context) + verification (/verify) endpoints so
any agent can understand the system and fact-check claims without
human intermediary.

Accessible on LAN at http://192.168.1.177:3700

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
2026-04-17 00:45:46 -05:00