VPN controls for stable: agent, web and Slack settings - #103
Open
makeitfutureDev wants to merge 2 commits into
Open
makeitfutureDev wants to merge 2 commits into
makeitfutureDev wants to merge 2 commits into
Conversation
Signed-off-by: Tiberiu Socaci <tsocaci@makeitfuture.com>
Signed-off-by: Tiberiu Socaci <tsocaci@makeitfuture.com>
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
2 participants
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.
Prepared channel VPN services can now be controlled by asking the agent, using the web channel VPN switch beside Network, or opening Slack Settings → Network. Channel managers/admins can start and stop; admitted members can read status. All surfaces share a fixed channel-bound helper and fresh authorization, with safe diagnostics and no credential/profile disclosure.
Connected requires fresh readiness; starting is explicit. OFF disables automatic startup and cleans up supervised or manually started owned containers. Provisioning remains operator-only.
Validation: complete coverage suite 2,559 passed, 0 failed, 13 conditional skips; static/security-coverage/secret/DCO checks passed; production audit has no high/critical findings (one existing moderate). Five web tests passed including real Chromium. Real Claude 2.1.265 and Codex 0.153.4 invoked status/enable/status/disable against isolated actual MCP handlers/controller and rejected a subsequent enable after manager revocation. The fixture uses an injected service, not a provider connection.
Provider connection remains blocked by the server certificate's missing Key Usage extension; verification is preserved and no SQL has run. Private Airtable cases are prepared but writes await requester selection of a personal connection. Actual Slack clicks and provider-backed success remain open acceptance gates in TEST-PLAN.md.
Stable candidate:
8f76b18f8c75dc4f8267e42d1d83317360849704(use the branch full SHA for approval). The only extra stable commit updates a test parser to recognize inline MCP registrations; runtime source is identical to the backport verified by both live engines and Chromium. This PR excludes unrelated beta changes. After promotion, refresh installed VPN supervisor bundles withinstall-unit; provider certificate repair remains external.Final checks: candidate
8f76b18f8c75dc4f8267e42d1d83317360849704has passing GitHub CI on Node 22.13 and 24, hygiene and DCO. Full stable coverage: 2,559 passed / 0 failed / 13 conditional skips; static, security-coverage, secret scan, DCO and production high-severity audit passed. Real browser acceptance: all five tests passed. Actual Claude/Codex isolated MCP acceptance passed against the unchanged production sources; the last commit changes only the registration-parser test.Beta is merged in PR #102 and running on Xavier at
1d6c284de13ebc7e4d259379a7262c5ac681a302; post-restart health and both engine smoke probes passed. Stable promotion awaits explicit candidate confirmation required by the repository policy. Atlas read-only status confirms configured service, no missing credential names, disabled startup and no running pair; provider-backed successful connection remains blocked.