KomarDB
live

Go Beyond Connect

GB Connect

scores

progress33%
priorityhigh
complexity5/10
readiness8/10
excitement9/10
hours invested8h
last12 days ago

claude · 1 hour ago

Live TypeScript app with active pushes but progress stuck at 33% and checkpoint 15 ticked zero items in a 5.93h session — execution tracking is drifting from reality. The flurry of duplicate github_sync events also suggests a webhook/integration bug.

  • Reconcile progress % against shipped scope post go-live
  • Audit checkpoint 15 — why zero ticks after 5.93h
  • Deduplicate github_sync webhook firing 15x per push
  • Define one concrete post-launch user metric to track
  • Resolve dev↔live stage flip-flop with a release gate

notes

Go Beyond project

Plan from /cl

  1. LiveKit Cloud cutover live in production
    Production frontend bundle baked with NEXT_PUBLIC_AUDIO_BACKEND=livekit; /livekit-token mints JWTs; LiveKit dashboard shows live sessions during a real call · done 17 days ago
  2. Render + Vercel fully decommissioned
    Zero projects/services in either account; live traffic confirmed served by komarlab via Cloudflare tunnel (no x-vercel-* headers) · done 17 days ago
  3. Operational docs rewritten (komarlab + LiveKit)
    DEPLOYMENT/README/RUNBOOK/ARCHITECTURE/env.examples all reflect komarlab Docker + LiveKit Cloud as production; no stale Render/Vercel walkthroughs · done 17 days ago
  4. Delete dormant mesh fallback (useWebRTC, /ice-servers, CF_TURN_*)
    frontend/hooks/useWebRTC.ts deleted, page.tsx is single-hook (no webRTCRef indirection), server has no /ice-servers route or CF_TURN_* env reads
  5. Wire LiveKit ConnectionQualityChanged to audio pill
    Poor LiveKit connection quality surfaces as yellow/red audio pill in room header within 5s of degradation
  6. Wire LiveKit Disconnected to issue audio state
    Permanent LiveKit disconnect shows red 'Audio Warning' instead of stale 'idle'
  7. Rate limiting + room-code verify on /livekit-token
    Endpoint enforces per-IP rate limit and rejects unknown room codes before minting; pino logs new livekit.token.rejected event
  8. Move guide password gate server-side (env var)
    Password lives in server env, validated server-side with per-IP rate limit; not visible in frontend bundle
  9. 1-week LiveKit soak with no audio incidents
    7 days post-cutover (from 2026-05-24) with no reported audio failures across at least 3 tours; incident log clean

Recent checkpoints

  • 13 days ago5.9hTopdeck white-label of Connect went live in production at topdeck.gobeyondconnect.com (commit f651b6a) with today's UI polish — group photo bg, larger wordmark, dark-glass buttons, brand-aware favicons. Cloudflare Tunnel layout cleaned up: every gobeyond app moved into the renamed komar-gobeyond tunnel, every komarlab app into komar-komarlab; srtscrape migrated from .gobeyondconnect.com to .gobeyond-app.com for domain hygiene. Supports active Topdeck Thailand+Vietnam tender due ~2026-06-11; backend brand-aware room code prefix and Topdeck OG image still pending.
  • 17 days ago1.9hCut LiveKit audio backend live in production (NEXT_PUBLIC_AUDIO_BACKEND=livekit baked into the komarlab gbc-frontend bundle, /livekit-token endpoint minting JWTs). Decommissioned external infra: Vercel project + domain attachment deleted via CLI, Render service deleted via REST API, both accounts now empty. Operational docs (DEPLOYMENT, README, RUNBOOK, ARCHITECTURE, env examples) rewritten to drop Render/Vercel walkthroughs.