docs: align target access and release deployment guidance - #17
Conversation
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 2980103d2d
ℹ️ 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".
| "/api/v1/workspaces/{workspaceId}/agents/{agentId}/mcp/servers/{serverId}/target-access": { | ||
| "get": { |
There was a problem hiding this comment.
Add the target-access operations to API navigation
The API reference uses an explicit endpoint list in docs.json, but the Agent capabilities and target tools group omits both the new GET and PUT operations for this path. Consequently, users cannot discover these target-access APIs through the published reference navigation; add both operation references alongside the existing Agent MCP server endpoints.
AGENTS.md reference: AGENTS.md:L5-L7
Useful? React with 👍 / 👎.
Documents agent target access settings and brings Kubernetes, VM, configuration, operations, and production-readiness guidance in line with the supported release matrix and current Helm values.\n\nValidation:\n- npm run check\n- npm run validate\n- npm run links\n\nPart of the coordinated release-readiness update.