| Environment | Target | Purpose | Release policy |
|---|---|---|---|
| GitHub Pages | https://ocodejs.github.io/ |
Static Control Center | Updated only after an approved merge to main and successful Pages workflow |
| Control API staging | ocodejs-server-api-staging |
Read-only service, agent and provider registries | Staging-only Worker versions; no Production routes |
| MCP staging | ocodejs-mcp-staging |
Streamable HTTP MCP endpoint | Fixed read-only tool allowlist |
| Account Auth Preview | Cloudflare Workers Preview URL protected by Access | Build and route validation | No production deploy command; dedicated Preview resources required |
- Read the current branch, PR base, current Worker version and relevant workflow status.
- Create a feature branch; do not commit directly to
main. - Add or update tests and documentation with the code change.
- Open a PR. For stacked work, record the exact base PR and merge order in the PR body.
- Wait for all relevant CI jobs to pass:
- Control API unit tests
- MCP Worker unit tests
- Control Center inline JavaScript validation
- OCode.js Pages theme validation
- Static accessibility and local Markdown link checks
- Deploy only the named staging Worker after CI passes.
- Read back the Worker version and deployment. Confirm that the intended staging version receives 100% of staging traffic.
- Record the deployment ID, version ID, CI run and remaining verification gaps in the PR.
- Do not merge PRs or deploy Production unless explicitly approved.
The current staging API routes are read-only. The runtime readiness route must report not_configured, executionEnabled: false, and runLifecycle: disabled until a provider and isolated run store are deliberately configured:
GET /api/v1/health/liveGET /api/v1/health/readyGET /api/v1/servicesGET /api/v1/agentsGET /api/v1/providersGET /api/v1/providers/{providerId}GET /api/v1/runtime/statusGET /api/v1/mcp/connections
The MCP staging endpoint is:
https://ocodejs-mcp-staging.huynhthuongg2505-f9b.workers.dev/mcp
Perform MCP checks in this order:
initializewith protocol version2025-03-26.- Send
notifications/initialized. - Call
tools/list. - Confirm the exact six-tool read-only allowlist:
get_control_api_health,list_services,list_agents,get_agent_definition,list_providers,get_provider_definition. - Do not invoke a write tool; none should be exposed.
The connected execution runner currently blocks outbound HTTP requests to Workers.dev hostnames. Therefore, a successful upload/deployment is not equivalent to a successful external HTTP smoke test. Keep that distinction in release notes.
- Confirm the Preview hostname is protected by the existing Cloudflare Access policy.
- Configure the seven Preview-only values listed in Environment Configuration.
- Attach a dedicated Preview PostgreSQL database.
- Confirm
GET /api/healthreturns200 ready. - Verify registration, invalid-password handling, GitHub OAuth, Google OAuth, session persistence, logout, and session revocation.
- Keep sign-in disabled until all checks pass.
The current Preview has built successfully but does not have the database or provider secrets. Do not report it as a working login system.
- For a staging Worker regression, identify the last known-good staging version and restore that version using the Cloudflare Worker deployment controls.
- Verify the resulting staging deployment percentage and health endpoints.
- Do not change production Worker versions, routes, DNS or secrets as part of a staging rollback.
- Record the failed version, rollback version and relevant request IDs.
Production remains disconnected. A Production release requires a separate explicit approval after:
- Authentication and authorization are verified.
- Agent provider selection, execution policy, quotas and approval gates are implemented.
- MCP write operations, if ever required, have authentication and destination validation.
- Metrics, audit storage, alerting and retention are operational.
- Security review, load tests, recovery tests and rollback drills pass.