docs: add separate OpenAI, Anyway, and Traceloop guides

[chilu18]

Summary

• add standalone OpenAI implementation guide
• add standalone Anyway implementation guide
• add standalone Traceloop implementation guide
• update docs/opencto README index with direct links

Validation

• npx markdownlint-cli2 docs/opencto/OPENAI_IMPLEMENTATION_GUIDE.md docs/opencto/ANYWAY_IMPLEMENTATION_GUIDE.md docs/opencto/TRACELOOP_IMPLEMENTATION_GUIDE.md docs/opencto/README.md

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: c044298fdf

ℹ️ 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".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Add required date params to OpenAI usage runbook step

The runbook currently says to call /api/v1/cto/openai/usage without query parameters, but the API worker forwards start and end directly to OpenAI as start_time/end_time (see proxyOpenAI call path in opencto/opencto-api-worker/src/index.ts), and the dashboard tool contract requires both dates (get_openai_usage in opencto/opencto-dashboard/src/lib/realtime/shared.ts). Following this step as written sends empty values and can return upstream errors instead of validating the ops path.

Useful? React with 👍 / 👎.