Skip to content

feat: add Discord community runtime and gateway transport#275

Open
lev-goryachev wants to merge 9 commits intomainfrom
discovery
Open

feat: add Discord community runtime and gateway transport#275
lev-goryachev wants to merge 9 commits intomainfrom
discovery

Conversation

@lev-goryachev
Copy link
Copy Markdown
Contributor

Summary

  • add the Discord community bot runtime foundation, including connector abstractions, automation engine/executor modules, CRM/message ingestion helpers, and guild mapping cache support
  • introduce the first Redis-backed Discord gateway transport for hosted onboarding, plus gateway proxy connectors and shared action handlers
  • update Discord onboarding to run on the hosted gateway path and surface channel permission diagnostics instead of silent failures

Test plan

  • static Python compile checks on touched client-kit files
  • local gateway service startup and Redis command-path smoke checks
  • local end-to-end onboarding smoke test through the hosted gateway path
  • reviewer pass on connector contract stability for future non-Discord adapters
  • reviewer pass on rollout plan for remaining Discord-only hooks (reaction roles, checklist, announce)

@lev-goryachev lev-goryachev force-pushed the discovery branch 3 times, most recently from 03bac12 to 84f21ec Compare April 9, 2026 09:35
@lev-goryachev lev-goryachev marked this pull request as ready for review April 9, 2026 17:38
@lev-goryachev lev-goryachev force-pushed the discovery branch 3 times, most recently from c8ae061 to a5a1dde Compare April 10, 2026 14:52
Collapse the current discovery branch into one commit on top of origin/main so the remaining PR diff reflects only the final client-kit state we actually want to review.
Revert files that leaked into the squashed discovery diff so the PR stays focused on the Discord and automation work reviewers actually need to read.
Read disabled rule ids from the backend runtime endpoint and shorten the poll interval so rule toggles apply without a manual bot restart.
Load the automation schema eagerly and drop the disabled-rule cache plumbing in favor of published enabled rules. Route hosted Discord actions through trusted backend gateway APIs while consuming inbound events through the existing external-message path.
Ignore local .cursor files so workspace-specific agent state does not keep polluting the discovery branch.
Drop legacy Discord transport and CRM member-state paths so bots use the trusted gateway flow end to end and keep the Discord integration reviewable.
Remove the unused pin_checklist setup flag and the redundant gateway allowlist re-application so the Discord bot keeps less stale legacy surface.
Capture the current gateway-only cleanup before the next simplification pass so we can refactor the Discord stack with an easy rollback point.
Move the gateway-only bot onto shared lightweight Discord helpers so it stops importing the full integration module for snowflake parsing, setup flags, auth token lookup, and contextual logging. Reuse the same helper definitions in fi_discord2 to reduce duplication without changing gateway behavior.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant