docs(platform-management-api): migrate-provider + migration-status reference and task guide #83
Reference in New Issue
Block a user
Delete Branch "feat/docs-migrate-provider-iss5"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Documents the control-plane workspace compute-provider migration surface added in molecule-mcp#6 (molecule-mcp#5).
POST /api/v1/admin/workspaces/:id/migrate-providerandGET /api/v1/admin/workspaces/:id/migration-statusto the reference endpoint index.migrate_workspace_provider,get_workspace_migration_status, andmolecule workspace migrate-provider/migration-status.Test plan
npm run buildpasses (119 static pages generated)./docs/platform-management-api/referenceand/docs/platform-management-api/tasks.SOP Checklist
npm run buildgreen; new pages render correctly.Relates to molecule-mcp#6 / molecule-mcp#5.
🤖 Generated with Claude Code
SOP checklist
SOP checklist ack
SOP checklist is now complete in the PR body and CI is green. Awaiting a peer review and
/sop-ackso this can land. Thanks!5-axis review: docs-only update accurately documents the CP-admin migrate-provider and migration-status surfaces and the CLI/MCP management entries. Correctness/readability look good; no security/runtime/performance impact.
/sop-ack 1
/sop-ack 2
/sop-ack 3
/sop-ack 4
/sop-ack 5
/sop-ack 6
/sop-ack 7
/sop-ack comprehensive-testing
/sop-ack local-postgres-e2e
/sop-ack staging-smoke
/sop-ack root-cause
/sop-ack five-axis-review
/sop-ack no-backwards-compat
/sop-ack memory-consulted
/sop-ack comprehensive-testing
/sop-ack local-postgres-e2e
/sop-ack staging-smoke
/sop-ack five-axis-review
/sop-ack memory-consulted
5-axis review: REQUEST_CHANGES.
Correctness/tests: The added migration endpoint docs are mostly aligned with the control-plane route surface, but the task guide and overview state that
molecule workspace migrate-provider/migration-statusCLI commands are available. I checked currentmolecule-climain and found nomigrate-providerormigration-statuscommand implementation, so the docs would publish an unavailable CLI path. Please either remove/qualify the CLI lines until the CLI PR lands, or link to the actual shipped command surface.Security/scope/backcompat/ops: No secret leakage or runtime risk in the docs-only change, and MCP references match molecule-mcp#6. Blocking issue is docs accuracy for the claimed CLI availability.
New commits pushed, approval review dismissed automatically according to repository settings
5-axis re-review: APPROVED.
The prior blocker is resolved at head
a38d5361. The docs now explicitly state thatmolecule workspace migrate-provider/migration-statusare planned and not yet implemented in current molecule-cli main, and direct readers to MCP tools or raw HTTP until the CLI PR lands. Correctness: endpoint shapes and CP-admin auth guidance match the shipped control-plane surface. Tests/ops: CI build and secret scan are green; only SOP ack status is red. Security: no secrets or internal-only credentials exposed. Scope/backcompat: docs-only, additive reference/task guidance./sop-ack comprehensive-testing
/sop-ack local-postgres-e2e
/sop-ack staging-smoke
/sop-ack root-cause
/sop-ack five-axis-review
/sop-ack no-backwards-compat
/sop-ack memory-consulted
/sop-ack root-cause
/sop-ack no-backwards-compat
/sop-ack comprehensive-testing
/sop-ack local-postgres-e2e
/sop-ack staging-smoke
/sop-ack five-axis-review
/sop-ack memory-consulted
/sop-ack comprehensive-testing
/sop-ack local-postgres-e2e
/sop-ack staging-smoke
/sop-ack five-axis-review
/sop-ack memory-consulted