Use canonical Public Apps control-plane hostnames - #5
Merged
nathan-thillairajah merged 2 commits intoSep 24, 2026
Merged
Conversation
nathan-thillairajah
changed the title
jsibbison-square
approved these changes
Sep 24, 2026
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.
The Apps control-plane allowlist has an outdated Public production hostname and no Public staging entry. Use the agreed Public control-plane URLs:
https://compose-ctrl.apps.builderlab.xyzhttps://compose-ctrl.apps.builderlabstaging.xyzReplace the old singular-
appproduction entry and add staging. Extend the exact-host tests to reject the obsolete spelling, UI hosts, HTTP, lookalike suffixes, alternate ports, and userinfo. The existing Block staging entry is unchanged.Validation: all six control-plane tests, workspace tests, clippy, and formatting passed. The rebuilt local CLI successfully fetched the authenticated Public staging contract after browser login. Production hostname acceptance is covered by unit tests; no production request was made. Hosted tool calls and app capabilities remain disabled in the staging contract, so deployment and consent testing are still blocked by platform configuration.