Skip to content

todo.md

Latest commit

 

History

History
35 lines (34 loc) · 3.59 KB

todo.md

File metadata and controls

35 lines (34 loc) · 3.59 KB
Raw

Project TODO

  • Define MailDM domain models, security boundaries, provider contracts, and retention rules.
  • Create a secure database schema and migration for Discord identities, Gmail connections, encrypted credentials, schedules, jobs, delivery history, and audit-safe events.
  • Build a polished MailDM landing page, live status view, and public OAuth success/error pages.
  • Implement Discord HTTP Interaction signature verification, slash-command routing, and Discord REST API DM delivery.
  • Implement multi-user, multi-Gmail-account configuration with labels, account attribution, disconnect, and reauthorization flows.
  • Implement Google OAuth authorization-code linking with one-time state validation and encrypted refresh-token persistence.
  • Implement strictly read-only Gmail unread-message retrieval, in-memory sanitization, bounded normalization, filtering, and deduplication.
  • Implement DM-only AI provider credential setup, fixed recommended model lists, validation, encryption, and safe credential handling.
  • Implement structured summary generation through extensible AI provider adapters and retain only safe summary metadata/history.
  • Implement per-user timezone scheduling through managed scheduled HTTP callbacks with transactional claims, idempotent delivery, retry-safe behavior, and the exact no-mail message.
  • Implement Gmail reauthorization prompts and retry-safe callback rearming for transient digest failures.
  • Define extensible source and delivery interfaces for later Outlook, Slack, and read-only GitHub notification integrations.
  • Add unit tests, integration-focused tests, project documentation, and secure deployment configuration guidance.
  • Perform type checks, run tests, and verify the rendered experience at desktop and mobile sizes.
  • Save the initial Manus implementation checkpoint.
  • Deliver the secure end-to-end setup and test instructions.
  • Restrict the user-facing MVP scope and documentation to Gmail-only, with Outlook, Slack, and GitHub deferred.
  • Add a /sample command that delivers a clear illustrative brief before OAuth or AI-key setup.
  • Add first-class /settings and /summary-now commands using real configuration and data.
  • Add feedback storage and verified thumbs-up/down interactions for delivered briefs.
  • Replace soft account disconnection with disconnect-and-purge deletion of Gmail tokens and associated account data.
  • Add user data-deletion handling and public privacy/Google OAuth verification preparation pages.
  • Add adversarial prompt-injection, Gmail normalization, and AI-key validation success/failure tests.
  • Re-run verification, save the Gmail-only MVP checkpoint, and deliver the updated setup/test guide.
  • Recover the stopped development server and verify preview responsiveness.
  • Investigate and mitigate the repeated development-server stop caused by external Discord command-registration requests.
  • Verify MailDM environment-variable presence without exposing secret values.
  • Inspect crash logs and identify why the development server stopped responding.
  • Restart the development server and verify the public preview port is exposed.
  • Save a checkpoint containing the startup-resilience fix.
  • Push the completed MailDM code to the GitHub repository on a review branch and verify the remote diff.
  • Reconcile the local MailDM history with GitHub main so the review branch has a common ancestor.
  • Verify the pushed review branch contents with a successful GitHub comparison or pull-request URL and record the branch and commit for review.