clickup-multi-env-setup

# ClickUp Multi-Environment Setup ## Overview Configure separate ClickUp workspaces and API tokens for development, staging, and production. ClickUp does not have sandbox environments, so the recommended approach is separate workspaces with separate tokens per environment. ## Environment Strategy | Environment | Workspace | Token | Rate Limit | Purpose | |-------------|-----------|-------|-----------|---------| | Development | Dev workspace | Personal token | 100 req/min | Local development, testing | | Staging | Staging workspace | Service token | 100 req/min | Integration testing, QA | | Production | Production workspace | Service token | Per plan | Live traffic | **Key point:** All ClickUp API calls go to `https://api.clickup.com/api/v2/` regardless of environment. Environment isolation comes from using different tokens that are authorized for different workspaces. ## Configuration ```typescript // src/config/clickup.ts interface ClickUpEnvConfig { token: string; teamId: string; defaultListId?: string; timeout: number; retries: number; cacheEnabled: boolean; cacheTtlMs: number; } function getClickUpConfig(): ClickUpEnvConfig { const env = process.env.NODE_ENV ?? 'development'; const base = { timeout: 30000, retries: 3, cacheEnabled: true, cacheTtlMs: 60000, }; switch (env) { case 'production': return { ...base, token: requireEnv('CLICKUP_API_TOKEN_PROD'), teamId: requireEnv('CLICKUP_TEAM_ID_P...