docs(rfc): platform-mcp-as-plugin → out of Draft, plugin-only + retire platform-agent image (CTO sign-off) #3181
Reference in New Issue
Block a user
Delete Branch "docs/rfc-platform-mcp-plugin-signoff"
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?
Takes rfc-platform-mcp-as-plugin out of Draft for CTO sign-off. Decisions resolved (§6), gated rollout (§5), sign-off block (§8). Directive: retire the molecule-platform-agent image; platform agent = claude-code workspace + entitlement-gated plugin. Root structural fix for the recurring #3164 fragility. Awaiting CTO sign-off in §8.
APPROVED on
5852a212.5-axis review: this is a docs/RFC-only change moving the platform-MCP-as-plugin RFC out of draft for CTO sign-off. Correctness: the document now records concrete decisions and a gated migration sequence, including the required plugin-fetch hardening before retiring the baked platform-agent image. Robustness: rollout is staged with observability, fetch hardening, staging proof, cutover, reprovision, then retirement; the current baked image safety-net risk is explicitly called out instead of hidden. Security: org-root entitlement remains the load-bearing boundary and the diff introduces no secrets or behavior-changing code. Performance: no runtime/code impact. Readability: the resolved-decision and sign-off sections make the remaining approval surface clear.
Latest CI/all-required and related contexts are green on this head.
APPROVED on
5852a212.Gate reconciliation: the protected main branch currently requires CI / all-required, E2E API Smoke Test, Handlers Postgres Integration, Secret scan, qa-review, security-review, and reserved-path-review. All seven have success statuses on this head. The earlier red statuses I flagged are not BP-required for this docs/RFC PR: sop-checklist / all-items-acked (pull_request) is superseded by the successful pull_request_target SOP status, reserved-path-review has since posted success on the required pull_request_target context, gate-check-v3 is not in the protected required set, and the cancelled E2E Staging SaaS jobs are informational/non-required here.
5-axis review: correctness: this is a docs-only RFC signoff update and the diff consistently moves platform-MCP-as-plugin from draft to CTO signoff with concrete rollout gates and resolved decisions. Robustness: it explicitly keeps plugin-fetch hardening and staging proof ahead of image retirement, so the RFC does not paper over the current safety-net dependency. Security: org-root entitlement remains the privileged boundary; no secrets or behavior-changing code are introduced. Performance: no runtime effect. Readability: the migration sequence, decisions, and signoff request are materially clearer than the draft.