feat: add CLI commands for account management and email fetching

.cursor/rules/010-overview.mdc

@@ -0,0 +1,37 @@
+---
+description:
+globs:
+alwaysApply: true
+---
+
+# Project overview
+This project's goal is to enable builders to create email-based apps
+
+## Success metrics
+- Reduction in time-to-zero-inbox for daily emails
+- Number of active users of email apps
+
+## Functional requirements
+### General
+- Stay lean, keep a minimal set of well-picked dependencies. The leanest codebase can lead to the greatest achievements
+- Keep the codebase modular
+- Respect Don't Repeat Yourself (DRY) rules
+
+### Relay library
+- Handle email account management (IMAP, Gmail, Outlook)
+- Implements all common email operations that you can experience with email clients
+- Credentials are stored locally
+- The implementation should be optimized for speed and concept persistence
+
+### Relay CLI
+- Wrap the library in a CLI interface
+- The UI should be designed so that it becomes easy for developers to manage their emails using their terminal
+
+### Documentation
+- Fast track the installation, usage and contribution of users
+
+### Backend API
+- Allow users to host online a REST API to develop email-based services
+- Handle user authentication (OAuth 2 using JWT as bearer tokens)
+- Handle OAuth connections (Google account)
+- Enable the fetching and labeling of emails (metadata in relational database + image/video in storage)

.cursor/rules/011-user-journeys.mdc

@@ -0,0 +1,19 @@
+---
+description:
+globs:
+alwaysApply: true
+---
+
+# User journeys
+
+## User description
+The users of this project are:
+- professional developers experiencing vendor-locking with email solutions
+- hobbyist and builders focused on prototyping multiple ideas quickly
+
+
+## Journey description
+- The user installs the CLI
+- They connect their main email account, entering their credentials
+- They fetch their first email
+- They give the CLI documentation to their coding LLM to perform tasks on it

.cursor/rules/012-key-concepts.mdc

@@ -0,0 +1,22 @@
+---
+description:
+globs:
+alwaysApply: true
+---
+
+# Key concepts
+
+We need to keep the number of user-facing concepts to a minimum. Those concepts need to be persistent and in service of the product. Their core functions are:
+- authentication and account management
+- core email interactions
+- make it easy & appealing for developers to build apps
+
+Here are our main concepts:
+- email server: a VM that can run email interactions through a specific set of possible protocols
+- email provider: organization hosting email servers
+- email account: a domain-bound address to send and receive emails
+- email protocols: convention for interactions with an email account
+- email client: a GUI for interactions with email accounts
+- credentials: user-defined secrets that enable a connection to an email account
+- message: a single e-mail (body + headers), defined by its Message-ID or IMAP UID.
+- thread: all messages sharing References/In-Reply-To headers

.cursor/rules/020-structure.mdc

@@ -0,0 +1,30 @@
+---
+description:
+globs:
+alwaysApply: true
+---
+
+# Codebase structure
+
+The codebase includes several applications with separate tech stacks and folders: core library, and CLI.
+
+- `.github/`: GitHub CI configuration
+- `.cursor/rules`: rules for coding assistants
+- `./relay`: core library for email management
+- `./cli`: CLI for email management
+- [Makefile](mdc:Makefile) high-level project commands
+- [.pre-commit-config.yaml](mdc:.pre-commit-config.yaml): pre-commit configuration file
+- [pyproject.toml](mdc:pyproject.toml): project configuration file
+
+## Core library
+The core library is a Python library + CLI for sync and async email operations, organized as follows:
+- [client.py](mdc:relay/client.py): main entry point
+- [config.py](mdc:relay/config.py): configuration management
+- [exceptions.py](mdc:relay/exceptions.py): SDK-specific exceptions
+- `models/`: data models (translatable to other languages)
+- `providers/`: email provider implementations
+    - `gmail/`: Gmail connection
+    - `outlook/`: Outlook connection
+    - `imap/`: IMAP connection
+    - `smtp/`: SMTP connection
+- `auth/`: authentication system (creds, oauth flow, secure storage)

.cursor/rules/030-tech-stack.mdc

@@ -0,0 +1,27 @@
+---
+description:
+globs:
+alwaysApply: true
+---
+
+# Tech stack
+
+This is a thorough description of technology choices for the project. We want to stay lean and avoid making project maintenance too complicated.
+
+## General
+- Makefile
+
+## Backend API
+- Python 3.11+
+- Pydantic for model validation
+- uv for dependency management
+- ty for type checking
+- ruff for code styling & format
+- pytest as testing framework
+
+
+## CLI
+- Typer
+
+## Documentation
+- Mintlify