Entry-point system map for comedy-cellar-bot - monorepo layout, SST resource graph, data flow, load-bearing design decisions with rationale, invariants whose violation is an incident, and known weak points with file:line. Use when new to this repo, when planning any change that spans packages/ or infra/, when asking "why is it built this way", or before touching scraping, stages, the shared database, crons, or the reservation path. Also the index to the 14 sibling cellar-* skills.
Catalog of every configuration axis in comedy-cellar-bot - the five SST secrets (and the load-bearing clertPublishableKey typo), the SES Email identity resource, root .env, the Lambda env flags IS_ACTIVE/IS_CRON/STAGE, the per-stage map in infra/config.ts, the frontend VITE_ env chain and generated sst-env.d.ts files, localStorage flags, and cron schedules as config. Use when adding or rotating a secret, adding an env var or a new stage, wiring config into a Lambda or the frontend, or when a deploy crashes at infra/api.ts:23, a cron runs (or refuses to run) in the wrong stage, or import.meta.env comes back undefined.
Operations runbook for comedy-cellar-bot - what sst dev / pnpm deploy:prod actually do, the prod topology (comedycellar.mafz.al domains, crons, Supabase), the three cron jobs' real behavior, the admin-email telemetry decoder, log access, DB ops commands, and health checks. Use when running the app locally with sst dev, deploying or removing a stage, interpreting a "New Show Cron" / "Sync Show Cron" / "new reservation!" / "Show Notification Cron" email, wondering whether a cron actually ran, triggering a manual sync, or looking for logs of a deployed Lambda.
Symptom-to-triage tables, time-costing traps, and discriminating experiments for comedy-cellar-bot. Use when diagnosing a live misbehavior - empty show listings, crons that seem dead, off-by-one dates, duplicate rows from /api/shows/new, /api/shows/scan returning [], 500s from /api/settings, Clerk auth failures, frontend infinite loading, CI/build breakage, "Cannot find name 'sst'" type errors, broken mobile layout, or admin-email floods/silence.
Measure-don't-eyeball diagnostic recipes and runnable probes for comedy-cellar-bot — check-api.sh and freshness-check.sh (read-only health/scraper canary against our own API), plus recipes for token staleness, offline fixture parsing, proving a library behavior with node -e, DB spot checks, log tailing, bundle size, and config-drift greps. Use when you need a NUMBER instead of a guess — "is the scraper still landing shows", "is the API up", "how old is the anti-bot token", "does this show up in prod", "how big is the bundle", "prove this function returns [] not throws" — or before/after any change when you want evidence rather than a hunch.
Chronicle of every settled investigation, dead end, and revert in comedy-cellar-bot, each as Symptom → Root cause → Evidence (SHA/date/path) → Status. Use when a bug looks familiar, before re-attempting something that may have been tried and abandoned (Cognito, Sentry, Slack notifications, multi-day sync), when asked "why is this dead code here" (core/slack.ts, frontier.ts, commented Sentry), or when writing a post-incident entry.
Ranked open problems for comedy-cellar-bot (ship user notifications, scraper self-monitoring, backend test harness, data-quality repairs, multi-venue) each with the specific asset, first file-level steps, and a falsifiable milestone; plus the research discipline for turning a hunch into an accepted result here. Use when asked "what should we build next", "how do we make this self-running", "how do we ship notifications", when planning a new feature or experiment, or when deciding whether an idea is proven enough to promote. Not for live bugs or outages.
Decision-gated recovery runbook for a live scraper outage: show data in comedy-cellar-bot has gone stale, crons are erroring, comedycellar.com returns 403/challenge/garbage, or the site's HTML/JSON changed shape. Use when "the scraper broke", when "Sync Show Cron" failure emails arrive, when the freshness probes show no new shows landing, or when planning/executing an x-code-localize token recapture. Contains numbered phases with exact commands, expected observations, branch playbooks (token recapture, HTML drift, JSON drift, hard blocking), fenced wrong paths, and a numeric definition of "recovered".