You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Follows #4. Records the registered service id, corrects the two log lines the bridge actually prints, and updates the layout docs so channels/http reads as the brain and channels/discord as one way in.
Verified against the live host: the service connects, loads its secrets, and reports 4014 (disallowed intent(s)) with the fix, backing off 300s rather than hot-looping — deployed and waiting on the Message Content toggle.
This pull request updates documentation to reflect the deployment of the data-discord service and clarify the relationship between data-http and data-discord as two surfaces sharing a single brain. It also updates the service ID for data-discord and refines the environment variable documentation.
File
Change
Summary
AGENTS.md
modified
Clarifies the roles of channels/http and channels/discord.
README.md
modified
Updates descriptions for channels/http and channels/discord and introduces the "Two surfaces, one brain" concept.
services/discord.md
modified
Updates the service ID and environment variable documentation, and adds a verification note about deployment.
Reviewers should start by examining the changes in AGENTS.md and README.md to understand the updated architectural description.
This pull request updates documentation to reflect the deployment of the data-discord service and clarify the relationship between data-http and data-discord as two surfaces sharing a single brain. It also updates the service ID for data-discord and refines the environment variable documentation.
File
Change
Summary
AGENTS.md
modified
Clarifies the roles of channels/http and channels/discord.
README.md
modified
Updates descriptions for channels/http and channels/discord and introduces the "Two surfaces, one brain" concept.
services/discord.md
modified
Updates the service ID and environment variable documentation, and adds a verification note about deployment.
Reviewers should start by examining the changes in AGENTS.md and README.md to understand the updated architectural description.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Follows #4. Records the registered service id, corrects the two log lines the bridge actually prints, and updates the layout docs so
channels/httpreads as the brain andchannels/discordas one way in.Verified against the live host: the service connects, loads its secrets, and reports
4014 (disallowed intent(s))with the fix, backing off 300s rather than hot-looping — deployed and waiting on the Message Content toggle.