molecule-core/org-templates/molecule-dev/.env.example
rabbitblood 15ac834239 feat(template): expand dev team to 30+ roles with multi-repo coverage
- org.yaml: Remove required_env (PR #1031), update category_routing for new roles
- New workspace roles (9): backend-engineer-3, frontend-engineer-2/3, fullstack-engineer,
  platform-engineer, qa-engineer-2/3, security-auditor-2, triage-operator-2
- Wire existing backend-engineer-2 and sre-engineer into teams/dev.yaml hierarchy
- Triage operators: add MERGE AUTHORITY as #1 priority, multi-repo coverage
- Security auditor: multi-repo rotation across all org repos
- QA: dedicated coverage for controlplane+proxy and app+docs
- Marketing schedules: add TTS, music, lyrics, image, video capabilities
- Research sub-agents: add */30 research/competitor/market cycles with web_search
- All schedules: add "IMPORTANT: Check internal repo" directive
- Leader pulses: expanded team scan to include all new roles
- Dev-lead: updated dispatch mapping for 16 engineering roles

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
2026-04-20 00:29:56 -07:00

12 lines
452 B
Plaintext

# Place a .env file in each workspace folder to inject secrets.
# These become workspace-level secrets (encrypted, never exposed to browser).
#
# Example for Claude Code workspaces:
# CLAUDE_CODE_OAUTH_TOKEN=sk-ant-oat01-...
#
# Example for OpenAI/LangGraph workspaces:
# OPENAI_API_KEY=sk-proj-...
#
# Each workspace folder can have its own .env with different keys.
# A .env at the org root is shared across all workspaces (workspace overrides win).