Skip to content

fix: use verified staging Control API endpoint in Control Center - #52

Merged
zskbot merged 9 commits into
mainfrom
fix/control-center-use-verified-staging-api
Nov 16, 2026
Merged

zskbot merged 9 commits into
mainfrom
fix/control-center-use-verified-staging-api

Conversation

@zskbot

@zskbot zskbot commented Nov 16, 2026 •

Copy link
Copy Markdown
Member

Summary

  • Update the Control Center API base URL to the staging Worker hostname in the Cloudflare account that owns the active staging deployment and custom domain.
  • The previous ocodejs-df1.workers.dev hostname returned DNS ENOTFOUND from GitHub-hosted runners.
  • The replacement huynhthuongg2505-f9b.workers.dev hostname now passes DNS, health/live, health/ready, service registry, and https://ocodejs.co CORS checks after syncing the CI-tested Worker source to staging.

Safety

  • This changes one frontend API URL only.
  • No DNS, Access/WAF, secrets, or Production Worker settings changed.
  • Keep this PR unmerged until Preview/Pages and browser checks are reviewed.

Summary by Sourcery

Use the verified staging Control API endpoint and expand CI smoke checks across public ecosystem sites.

Bug Fixes:

  • Point the Control Center and staging smoke tests at the verified staging Control API hostname to restore reliable connectivity from hosted environments.

Enhancements:

  • Add diagnostic HTTP smoke coverage for OCodeJS ecosystem and Pages endpoints, including status, redirects, content metadata, and page titles.

CI:

  • Run the ecosystem HTTP smoke test as part of the Control API workflow and trigger the workflow when its script changes.

@vercel

vercel Bot commented Nov 16, 2026 •

Copy link
Copy Markdown
Contributor

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
ocodejs-profile Error Error Nov 16, 2026 9:42pm UTC
ocodejs.github.io Ready Ready Preview Nov 16, 2026 9:42pm UTC
pages.ocodejs.theme Ready Ready Preview Nov 16, 2026 9:42pm UTC

Request Review

@sourcery-ai

sourcery-ai Bot commented Nov 16, 2026 •

Copy link
Copy Markdown

Reviewer's Guide

Uses of the API

Point the Control Center at the verified staging Control API Worker so its API requests reach the active deployment.

  • index.html L58

Tests

Update the staging smoke check’s default API base URL to match the verified Worker endpoint used by the Control Center.

  • scripts/check-control-api-staging.mjs L1

Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it. You can also reply to a
    review comment with @sourcery-ai issue to create an issue from it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time. You can also comment
    @sourcery-ai title on the pull request to (re-)generate the title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time exactly where you
    want it. You can also comment @sourcery-ai summary on the pull request to
    (re-)generate the summary at any time.
  • Generate reviewer's guide: Comment @sourcery-ai guide on the pull
    request to (re-)generate the reviewer's guide at any time.
  • Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
    pull request to resolve all Sourcery comments. Useful if you've already
    addressed all the comments and don't want to see them anymore.
  • Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
    request to dismiss all existing Sourcery reviews. Especially useful if you
    want to start fresh with a new review - don't forget to comment
    @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

@qodo-code-review

Copy link
Copy Markdown

ⓘ Qodo reviews are paused because your trial has ended. Ask your workspace admin to add credits to resume reviews. Manage billing

@chatgpt-codex-connector

Copy link
Copy Markdown
Codex Review Summary: ❌ Failed

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ❌ Failed 2026-11-16T21:39:21.429943Z
We couldn’t complete this review. Comment @codex review to try again.
1fbc353 PR opened
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@chatgpt-codex-connector

Copy link
Copy Markdown

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.

sourcery-ai[bot]
sourcery-ai Bot previously approved these changes Nov 16, 2026

@sourcery-ai sourcery-ai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sourcery assessment

Approved.

@sourcery-ai sourcery-ai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey - I've found 2 issues

Prompt for AI Agents
Please address the comments from this code review:

## Individual Comments

### Comment 1
<location path="index.html" line_range="58" />
<code_context>
 let dashboardRequestSequence=0;
 let dashboardAbortController=null;
-const CONTROL_API_BASE='https://ocodejs-server-api-staging.ocodejs-df1.workers.dev/api/v1';
+const CONTROL_API_BASE='https://ocodejs-server-api-staging.huynhthuongg2505-f9b.workers.dev/api/v1';
 const MCP_ENDPOINT='https://ocodejs-mcp-staging.huynhthuongg2505-f9b.workers.dev/mcp';
 const services=[['AI Agent Runtime','Điều phối tác vụ agent','Chưa kết nối','off','—'],['API Gateway','Định tuyến API & rate limits','Chưa kết nối','off','—'],['Identity / Auth','OAuth · session · account','Chưa kết nối','off','—'],['MCP Registry','Quản lý MCP endpoints','Chưa kết nối','off','—'],['Developer Telemetry','Logs · metrics · traces','Chưa kết nối','off','—']];
</code_context>
<issue_to_address>
**CI passes for broken dashboard**

When the workers.dev endpoint used by the dashboard fails while the custom-domain endpoint remains healthy, `check-control-api-staging.mjs` uses its default `https://api-staging.ocodejs.co/api/v1` because the workflow supplies no override, so CI passes without checking the dashboard’s endpoint and users see it as UNVERIFIED.

Configure the smoke test or workflow to probe the same workers.dev endpoint that the dashboard uses.
</issue_to_address>

### Comment 2
<location path="index.html" line_range="58" />
<code_context>
 let dashboardRequestSequence=0;
 let dashboardAbortController=null;
-const CONTROL_API_BASE='https://ocodejs-server-api-staging.ocodejs-df1.workers.dev/api/v1';
+const CONTROL_API_BASE='https://ocodejs-server-api-staging.huynhthuongg2505-f9b.workers.dev/api/v1';
 const MCP_ENDPOINT='https://ocodejs-mcp-staging.huynhthuongg2505-f9b.workers.dev/mcp';
 const services=[['AI Agent Runtime','Điều phối tác vụ agent','Chưa kết nối','off','—'],['API Gateway','Định tuyến API & rate limits','Chưa kết nối','off','—'],['Identity / Auth','OAuth · session · account','Chưa kết nối','off','—'],['MCP Registry','Quản lý MCP endpoints','Chưa kết nối','off','—'],['Developer Telemetry','Logs · metrics · traces','Chưa kết nối','off','—']];
</code_context>
<issue_to_address>
**Operators verify the wrong endpoint**

When an operator follows the staging guide or Worker README to verify or troubleshoot the API, the guide and README still point to the old `ocodejs-df1.workers.dev` hostname, which returns DNS `ENOTFOUND`, so operators cannot verify the dashboard’s replacement endpoint and receive misleading diagnostics.

Update the staging guide and Worker README to direct operators to the replacement workers.dev endpoint.
</issue_to_address>

Sourcery assessment

Approval pending. 2 findings to address first.

Blocking findings: index.html:58, index.html:58


Sourcery is free for open source - if you like our reviews please consider sharing them ✨

Comment thread index.html Resolved
Comment thread index.html Resolved
@sourcery-ai
sourcery-ai Bot dismissed their stale review November 16, 2026 21:41

Sourcery withdrew this approval because the latest commits introduced blocking findings.

@vercel

vercel Bot commented Nov 16, 2026

Copy link
Copy Markdown
Contributor

Deployment failed for project pages.ocodejs.theme with the following error:

Resource is limited - try again in 24 hours (more than 100, code: "api-deployments-free-per-day").

Learn More: https://vercel.com/ocodejs-co?upgradeToPro=build-rate-limit

@vercel

vercel Bot commented Nov 16, 2026

Copy link
Copy Markdown
Contributor

Deployment failed for project ocodejs.github.io with the following error:

Resource is limited - try again in 24 hours (more than 100, code: "api-deployments-free-per-day").

Learn More: https://vercel.com/ocodejs-co?upgradeToPro=build-rate-limit

@zskbot
zskbot merged commit 4e64a66 into main Nov 16, 2026
5 of 8 checks passed

This branch had an error being deployed

1 failed deployment
Preview – ocodejs-profile — 6f3fe314 Deployed Nov 16, 2026 by vercel[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant