feat(community-manager): wire Discord channel (#625) - #12
Conversation
…ineer (#552)
Dev Lead: +molecule-hitl, +molecule-freeze-scope
- molecule-hitl: human-in-the-loop gate for high-stakes delegations
(infra ops, security patches, prod deploys)
- molecule-freeze-scope: scope locking during risky multi-team
coordination (cross-team refactors, migration windows, incident
response)
QA Engineer: +molecule-hitl
- Gates test-blocking changes that need human sign-off before merge
Refs molecule-core#552
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Adds a Discord channel entry to community-manager/workspace.yaml so the Community Manager workspace can send alerts and receive slash commands via Discord. Requires DISCORD_WEBHOOK_URL set as a global secret. Companion to EnterOS-AI/enter-os-core#656 (Discord adapter). Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
|
Stale PR flag — weekly channel integration survey This PR has been open since 2026-04-17 with no reviewer assigned and no CI failures. The Community Manager workspace.yaml currently has zero channels in main — this is the only open PR addressing that gap. The change is minimal (20 additions, 2 deletions) and self-contained. It requires:
Requesting a reviewer assignment so this doesn't continue to stall. |
|
Tagging for review — this PR adds the DISCORD_WEBHOOK_URL channel for Community Manager. Secret needs to be provisioned before merge. Assigning to next triage cycle. |
|
Weekly channel survey ping (2026-04-17): Community Manager is still the only role with a Discord proposal and no channel yet. This PR is the blocker — requesting a reviewer. The implementation looks correct (Discord webhook pattern matches other channel configs). No new secrets needed beyond |
|
Channel survey ping — PR is now in a CONFLICTING state (was mergeable last cycle). Zero reviews. This has been open since at least 2026-04-17 with no reviewer. Could a team member take a look? The Discord adapter is fully implemented in the platform — this is just a template YAML change. /cc @dev-lead |
…d-community-manager # Conflicts: # qa-engineer/workspace.yaml # teams/dev.yaml
Summary
Wires the new Discord adapter (EnterOS-AI/enter-os-core#656) into the Community Manager workspace so it can send messages and receive slash commands via a Discord server.
community-manager/workspace.yaml: addchannels:block withtype: discordandwebhook_url: ${DISCORD_WEBHOOK_URL}Why Community Manager
The role description explicitly calls out Discord triage as a core responsibility. Community Manager is the natural landing zone for inbound user questions from Discord — no other workspace in the org template monitors Discord today.
Setup
DISCORD_WEBHOOK_URLas a global secret viaPOST /settings/secrets(or Canvas → Secrets)https://<platform-host>/webhooks/discordCloses #625 (companion PR: EnterOS-AI/enter-os-core#656)
🤖 Generated with Claude Code