feat: add Twilio SMS bridge chart and mobile agents - #74
Merged
Conversation
Chart CI passedRepository hygiene and Helm 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
opencode-sms-bridgechart with hardened ingress/worker containers, a single-writer RWO state contract, and named Secret-reload wiring.*-smsOpenCode primary agents and bumpsopencode-serverto0.1.58for immutable configuration publication.Fixes: None (owner-approved Twilio mobile-agent implementation).
Type of change
Validation
Impact and rollout
The bridge chart requires a published immutable image SHA and a later cluster-owned PVC, Service, TunnelBinding, and SOPS Secret overlay. The
opencode-serverrelease automatically opens a separate GitOps version-pin PR after confirmed publication; that desired-state change does not deploy by itself. Do not configure Twilio webhooks until the later GitOps selection is reconciled, healthy, and explicitly approved for functional testing.Safety and secrets
AI agent materially produced this change; review mobile-agent tool denial, Reloader annotations, and chart-to-GitOps ownership boundaries carefully.