docs: route SMS bridge to primary agents - #77
Merged
Conversation
Chart CI passedRepository hygiene and Helm validation passed. View the workflow run. |
8 tasks
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
Updates the SMS bridge chart contract to route the four fixed destination numbers to the existing primary OpenCode agents:
lawnmowerman,grillmaster,homesteader, andhomerepair. This implements the owner decision that approved-source SMS sessions use the same agent configuration, permissions, MCPs, skills, and shared instructions as the normal agents. The chart does not select or deploy the bridge.Fixes: None — documents the owner-approved routing boundary.
Type of change
Validation
opencode-sms-bridge.Impact and rollout
The paired
imageschange changes the bridge's validated agent allowlist. This PR releasesopencode-sms-bridge0.1.1with matching consumer documentation only. The bridge has no current GitOps consumer selection, so merging/publishing this chart does not reconcile a workload or configure Twilio. A future focusedkustomize-clusterPR must select this chart and the paired immutable image SHA together, supply the encrypted approved-sender routing secret, and independently verify reconciliation and health.Rollback is a later consumer pin to chart
0.1.0and a compatible prior image; no live resource changes occur from this PR.Safety and secrets
AI agent materially produced this change; review the owner-only ingress and full-agent-access boundary carefully.