docs: reconcile platform-agent docs with the plugin-SSOT / runtime-agnostic model #3191
Reference in New Issue
Block a user
Delete Branch "docs/reconcile-platform-mcp-plugin"
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?
Reconciles
molecule-coredocs with the merged RFCdocs/design/rfc-platform-mcp-as-plugin.md. Docs-only; one coherent PR.Canonical model applied: the management MCP is delivered as an entitlement-gated plugin (the plugin declaration in
config.yaml: plugins:is the SSOT, not a separatemcp_servers:list); the plugin carries a runtime-agnostic MCP descriptor that a per-runtime shape adapter renders into the runtime native MCP config (claude.claude/settings.json, codex~/.codex/config.toml, gemini~/.gemini/settings.json, hermesplatforms.*); the platform agent is runtime-switchable (claude-code is the default); the bakedmolecule-platform-agentimage is retired.Per-doc
config.yaml: mcp_servers:list, hardcodedruntime: claude-code) and §5.7 (dedicatedmolecule-platform-agentimage) superseded by rfc-platform-mcp-as-plugin; added pointers in §5.6 (image = standard runtime image), §7 (MCP-on-ordinary-workspaces now gated by entitlement, not image separation), §9 (phases 2 and 3 revised). Conceptual model — platform-as-root,kind, resolver, approval gate, billing parity — left intact. Nothing deleted.Scope respected:
docs/only; no.gitea/and nomolecule-ai-workspace-runtimefiles touched (parallel subagents own those). Do not merge.🤖 Generated with Claude Code
APPROVED on core#3191 head
c1e3d3af14.5-axis: docs-only reconciliation is consistent with the plugin-SSOT/runtime-agnostic MCP model: config.yaml plugins remain the source of truth, runtime-specific MCP rendering is delegated to adapters, privileged platform MCP is entitlement-gated, and the old mcp_servers/baked platform image text is clearly marked superseded rather than silently conflicting. No secrets are introduced, no runtime behavior changes, and cross-links are coherent.
Merge note: review axis only. Live status still shows qa-review needing this approval and staging SaaS contexts pending; merge should wait for BP-required green/no open RC.
APPROVED on
c1e3d3af.5-axis review: correctness is sound for a docs-only reconciliation. The PR consistently moves the platform-management MCP delivery model to the plugin declaration (
config.yaml: plugins:) as SSOT, keepsmcp_servers:only as explicitly superseded historical text in the older RFC, and cross-links the mergedrfc-platform-mcp-as-plugin.md. It also preserves the still-valid platform-agent concepts (kind/root/default-target/approval gate/billing parity) while updating the delivery/image/runtime-switchability pieces.Robustness/readability are good: the docs avoid pinning runtime implementation signatures and point readers to the runtime for adapter details. Security posture is not weakened; privileged MCP delivery is described as entitlement-gated and secrets are referenced rather than embedded. Performance is not applicable. No file outside docs is touched; visible pending E2E contexts are merge-gate concerns, not review blockers for this docs diff.