4 Commits

Author	SHA1	Message	Date
yiekheng	3e2bc8c7ee	docs: web app design (Telegram-free pivot, plan 3 spec) ... After live-testing the Telegram bot we hit limits that don't go away with more menu polish (Markdown fragility, callback_data limits, no native date pickers, awkward media UX). Pivot to a Next.js PWA installable on the operator's phone; remove Telegram entirely. Spec covers: service topology with bot codebase shrunk, no-auth access stance with rate limiting + reverse-proxy gating, Server Actions replacing public REST mutation endpoints, SSE for live updates, the new web-side pair flow with live QR display, multi-step reminder wizard backed by URL state, mobile-first shadcn/ui visual layer, PWA service worker via @serwist/next, and a step-by-step plan to delete the existing Telegram code first. Inherits all confirmed values from the 2026-05-03 master spec.	2026-05-09 22:15:51 +08:00
yiekheng	33e1fcd2c4	docs: add manual end-to-end pairing test runbook	2026-05-09 16:24:18 +08:00
yiekheng	0f949284b1	docs: lock in subdomain, timezone, retention defaults ... Replace open-questions section with confirmed values from brainstorming review: wabot.04080616.xyz subdomain, Asia/Kuala_Lumpur default timezone, 90-day media retention, 5-minute minimum recurrence interval. Postgres pg_hba check kept as a pre-deploy verification step. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-05-09 14:40:37 +08:00
yiekheng	42caa0d37a	docs: initial design spec for WhatsApp reminder bot ... Captures the validated design from the brainstorming session: two-service topology (Next.js web + Node bot) communicating via Postgres LISTEN/NOTIFY, Baileys for WhatsApp, grammy for Telegram, pg-boss for scheduling, Drizzle for the data model, and Docker/Gitea-registry deploy flow. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-05-03 14:36:39 +08:00