feat: route SMS to primary agents - #31
Merged
Merged
Conversation
Image CI passedPre-commit validation passed. View the workflow run. |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
Routes the signed Twilio SMS/MMS bridge to the existing primary OpenCode agents (
lawnmowerman,grillmaster,homesteader, andhomerepair) rather than the isolated*-smsprofiles. The routing parser still accepts exactly four fixed destination mappings and now rejects the legacy aliases. The approved-source, signed-webhook, account, destination, media, session, and caller-controlled-routing boundaries are unchanged.Fixes: None — implements the owner-approved full-capability primary-agent SMS design.
Type of change
Validation
Impact and rollout
imagesis the producer. On an explicitly approved merge,mainpublishesghcr.io/makeitworkcloud/opencode-sms-bridgetagged with the immutable merge SHA. The separately authored charts PR #77 documents compatible chart0.1.1and has passing checks.Neither artifact is selected by GitOps today. A later focused
kustomize-clusterPR must select the exact published image SHA and chart revision together, configure only the approved source number(s) in the encrypted routing Secret, then separately verify reconciliation, health, and representative messaging. This PR does not configure Twilio, deploy, or alter the running OpenCode service.Rollback is a future GitOps selection of a compatible prior immutable image and routing configuration; no live change occurs from this PR.
Safety and secrets
AI agent materially produced this change; review the intentional expansion to existing primary-agent permissions and MCP availability carefully.