feat(den): replace dashboard home with telemetry usage insights MVP

[benjaminshafii]

Summary

• Replaces the Den /dashboard home screen with an org-facing telemetry usage insights view
• Adds full telemetry infrastructure: DB schema, ingest + adoption API endpoints, app-side reporter, dashboard wired to real data
• Real data: org member count, pending invites, active users (from telemetry events). Enterprise-only preview for advanced analytics (hideable)
• Preserves the "Download OpenWork" CTA

Screenshots

Dashboard with enterprise preview expanded (active users from real telemetry)

Dashboard with enterprise preview hidden (non-enterprise view)

Build verification

• pnpm --filter @openwork-ee/den-db build — passed
• pnpm --filter @openwork-ee/den-web build — passed

What was built

den-db

• telemetry_events table: id, org_id, user_id, event_type, event_timestamp, created_at
• Indexed on (org_id, event_type, event_timestamp) and (org_id, user_id)
• Added telemetryEvent type ID prefix (tev)
• Exported gte operator from drizzle barrel

den-api

• POST /v1/telemetry/ingest — batch ingest, auth-extracted identity, always returns 204
• GET /v1/telemetry/adoption — members, pending invites, active users 7d/30d, 12-week weekly trend
• Routes isolated in src/routes/telemetry/index.ts, registered in app.ts

app

• den-telemetry.ts — fire-and-forget reporter, lazy activation on Den sign-in, batched POSTs, no retries, no local storage
• trackSessionActive() wired into actions-store.ts when OpenCode creates a session

dashboard

• Calls GET /v1/telemetry/adoption, falls back to org context data if unavailable
• Live section: OpenWork users + pending invites (always visible)
• Enterprise preview: active users, trend chart, settings, plugin/skill tables (hideable)

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
openwork-app	Ready	Preview, Comment	May 6, 2026 0:08am
openwork-den	Ready	Preview, Comment	May 6, 2026 0:08am
openwork-den-worker-proxy	Ready	Preview, Comment	May 6, 2026 0:08am
openwork-landing	Ready	Preview, Comment, Open in v0	May 6, 2026 0:08am
openwork-share	Ready	Preview, Comment	May 6, 2026 0:08am

[benjaminshafii]

End-to-end telemetry verification

Tested the full telemetry pipeline locally with pnpm dev:den + pnpm dev:den:seed-demo (Acme Robotics, 17 members, 3 pending invites).

Steps

1. Pushed telemetry_event table schema via db:push
2. Signed in as alex@acme.test on http://localhost:3005
3. Called GET /api/den/v1/telemetry/adoption — returned real org data:

   {"members":17,"pendingInvites":3,"activeUsers7d":0,"activeUsers30d":0,"weeklyTrend":[0,0,0,0,0,0,0,0,0,0,0,0]}

4. Called POST /api/den/v1/telemetry/ingest with a session.active event — returned 204
5. Called GET /api/den/v1/telemetry/adoption again — active user count incremented:

   {"members":17,"pendingInvites":3,"activeUsers7d":1,"activeUsers30d":1,"weeklyTrend":[0,0,0,0,0,0,0,0,0,0,0,0]}

Result

Step	Status
Den stack boots	den-api on 8788, den-web on 3005
telemetry_event table created	db:push applied
GET /v1/telemetry/adoption before ingest	activeUsers7d: 0
POST /v1/telemetry/ingest with session.active	204
GET /v1/telemetry/adoption after ingest	activeUsers7d: 1
Dashboard shows "From telemetry" label	Real data flowing

Full pipeline working: app event → ingest endpoint → DB → adoption query → dashboard.

[benjaminshafii]

Verification (make-pr skill)

Build

• pnpm --filter @openwork-ee/den-db build — passed
• pnpm --filter @openwork-ee/den-web build — passed

UI verification (Chrome MCP)

• Signed in as alex@acme.test on http://localhost:3005
• Dashboard loads with real data: 17 OpenWork users, 3 pending invites
• Active this week: 1 with "From telemetry" label — real data from the ingested session.active event
• Enterprise preview shows/hides correctly via toggle
• Console errors: none
• Failed network requests: none
• GET /v1/telemetry/adoption returned 200

API verification

Before ingest:
{"members":17,"pendingInvites":3,"activeUsers7d":0,"activeUsers30d":0,"weeklyTrend":[0,0,0,0,0,0,0,0,0,0,0,0]}

POST /v1/telemetry/ingest → 204

After ingest:
{"members":17,"pendingInvites":3,"activeUsers7d":1,"activeUsers30d":1,"weeklyTrend":[0,0,0,0,0,0,0,0,0,0,0,0]}

Screenshots

• Dashboard with enterprise preview expanded
• Dashboard with enterprise preview hidden

Full pipeline verified: app event → POST /v1/telemetry/ingest → DB → GET /v1/telemetry/adoption → dashboard.