Prepare Web Hello connection for the Cloud container - #5
Merged
Merged
Conversation
deku2026
force-pushed
the
codex/web-cloud-hello
branch
from
September 15, 2026 23:24
afe3f0c to
22af279
Compare
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
1 participant
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.
Change
Prepare a separate
/cloud-hello/page for the future C# Native AOT service in Cloudflare Containers. An explicit click sends the fixed Hello request through the existing published gRPC-Web client to same-origin/api; failures stay visible, with a deadline, cancellation and no automatic retries.Document the Cloud-owned
arcforges.com/api/*route and exact wire boundary. Keep local API fixtures out of live verification, and stop the live Web gate from requiring Web HTML at paths that Cloud will own.Validation
npm run check(16 unit/component/SDK/delivery tests)npm run buildandnpm run test:e2e(18 tests across Chromium, Firefox and WebKit)Deployment
No new secret, package version, account resource or binding is needed for Web. Cloud is not deployed by this PR. Until its route exists, the connection page reports the static Worker's rejected request as unavailable. The future Cloud repository must implement and verify the actual AOT container and public protobuf call; fixture success is not that evidence. The existing local greeting stays local.