docs: Platform Management API developer guide #57
Reference in New Issue
Block a user
Delete Branch "docs/platform-management-api"
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?
What
Adds a developer-facing Platform Management API guide under
content/docs/platform-management-api/. Today the platform has no real management API docs — the only machine-readable artifact is a/schedules-only swaggo stub. This fills that gap with prose + task guides that derive from the OpenAPI SSOT rather than re-authoring endpoint definitions.Pages shipped
index.mdxgetting-started.mdxauth-model.mdxADMIN_TOKEN) — how to obtain each + the credential → route tier matrixtasks.mdxreference.mdxPlus
content/docs/platform-management-api/meta.json(section nav) and a one-line addition to the top-levelcontent/docs/meta.json.SSOT / derivation
The reference section derives from and links to the OpenAPI management spec at
molecule-coreworkspace-server/docs/openapi/management.yaml(branchfeat/openapi-management-spec, authored in parallel). The spec is the single source of truth for endpoint shapes; this PR writes the prose/guides around it and explicitly does not duplicate endpoint definitions. When prose and spec disagree, the spec wins.Accuracy / safety
Verification (Phase 4)
next build(Fumadocs) green: 115/115 static pages, TypeScript clean. All 5 new pages compiled to HTML.Per the dev SOP, a pure-docs change may skip the code Five-Axis; the merge gate here is build-green + link/anchor integrity, both verified above.
Do not merge without review.
🤖 Generated with Claude Code
Approved per comprehensive pre-merge review at HEAD
b87fb67— Fumadocs build 115/115 green, accuracy verified vs OpenAPI SSOT + live router (billing-mode tenant route, /api/v1/* paths, auth_token field, tier split). CTO-authorized.Second approval under CTO authorization.