# ─────────────────────────────────────────────────────────────────────────
# WHAT BELONGS IN THIS FILE — and what does NOT
#
# This file is for the DEPLOYMENT'S OWN identity and its model keys. That is
# all. Provider credentials do NOT live here.
#
#   HERE, in .env
#     LEAFMESH_LICENSE_KEY, LEAFMESH_ENV_TOKEN
#     the ports, REDIS_* / Postgres  (the store the vault itself lives in)
#     your model provider key(s): OPENAI_API_KEY / ANTHROPIC_API_KEY /
#       GOOGLE_API_KEY …  (these are read from the environment as the mesh
#       starts, so they must be here — the vault is read too late for them)
#
#   NOT HERE — in the VAULT, added on Studio's Infrastructure page
#     every channel credential  (Slack bot_token / signing_secret / app_token,
#       Teams, Discord, Cliq, WhatsApp, Email)
#     every connector credential (MCP, Zapier, Composio, n8n, custom)
#     Config then names it:  connection: "slack-workspace"
#
# Why it matters: since 2.4.180 the mesh REFUSES TO BOOT if it finds a
# provider credential written into config — and `${ENV_VAR}` does not help,
# because substitution happens before the check runs, so the check sees the
# token itself. `connection:` is the only path that works.
#
# Note: a value is EMPTY here, never a comment. `KEY=   # explanation` is read
# by python-dotenv as the COMMENT being the value.
# ─────────────────────────────────────────────────────────────────────────

# {{project_name}} — environment
LEAFMESH_LICENSE_KEY=
OPENAI_API_KEY=
ANTHROPIC_API_KEY=
REDIS_HOST=localhost
REDIS_PORT=6379
REDIS_PASSWORD=
PAGER_WEBHOOK=
# Slack escalation channel (manager.escalation → provider: slack). The
# escalation target only uses SLACK_RECRUITING_CHANNEL (its channel_id).
# SLACK_BOT_TOKEN / SLACK_SIGNING_SECRET are NOT read by the escalation
# target — they belong to a `channels: {slack: {...}}` block (ChannelConfig).
# Add that channels block to actually post to Slack; until then the bot
# token + signing secret are not auto-consumed.
SLACK_BOT_TOKEN=
SLACK_SIGNING_SECRET=
SLACK_RECRUITING_CHANNEL=
LEAFMESH_ENV_TOKEN=development
# ── ATS / calendar connectors (YAML-first agents) ──
# n8n workflow URLs against YOUR systems:
#   sourcing_agent        → ATS candidate search / LinkedIn Recruiter
#   recruiting_ops_agent  → ATS funnel / stage / time-to-hire ledger
#   panel_booker_agent    → calendar (Google/Outlook) or ATS scheduling
N8N_SOURCING_WEBHOOK_URL=
N8N_ATS_FUNNEL_WEBHOOK_URL=
N8N_PANEL_BOOKING_WEBHOOK_URL=
N8N_AUTH_TOKEN=
