Concierge declares but never installs the management-MCP plugin — molecule-platform-agent image lacks plugin boot-install (no create_workspace) [RFC#3045 remaining half] #3063

Open
opened 2026-06-19 04:53:23 +00:00 by molecule-code-reviewer · 0 comments
Member

Gap: concierge DECLARES the management-MCP plugin but never INSTALLS it (no create_workspace)

#3049 made the org concierge correctly declare its management MCP as a pinned gitea:// plugin — verified live on a fresh staging concierge:

workspace_declared_plugins: molecule-ai-plugin-molecule-platform-mcp | gitea://molecule-ai/molecule-ai-plugin-molecule-platform-mcp#main

But the plugin is never installed on the box, so create_workspace is still not exposed.

Root cause (SSM, fresh staging concierge box, 2026-06-19)

The concierge runs the special molecule-platform-agent image (153263036946/.../molecule-platform-agent@sha256:1c3c...). On that box, after 11+ min online:

  • /configs/plugins is empty.
  • docker logs molecule-workspace has ~zero plugin/gitea/declared/boot-install lines.
  • grep -rilE 'workspace_declared_plugins|boot-install|skip.unsupported.source' /appno matches — the image does not contain the declared-plugin boot-install that standard runtime images (claude-code, seo-agent) have.
  • MOLECULE_TEMPLATE_REPO_TOKEN is present on the box (so a boot-install, if present, could fetch).

Standard runtimes install declared gitea:// plugins (seo-agent installs seo-all — template-delivery-e2e passes). The concierge can't, because its image lacks the pipeline.

Fix (RFC #3045 — the incomplete half)

RFC #3045 (CTO-approved) was: deliver the management MCP as a plugin via MCPServerAdaptor and retire the special molecule-platform-agent image, running the concierge on a standard plugin-capable runtime. #3049 delivered only the declaration. The remaining keystone:

  • Run the concierge on a standard runtime image (claude-code) that performs the declared-plugin boot-install + MCPServerAdaptor, OR
  • Add the plugin boot-install entrypoint to the molecule-platform-agent image.
    Either way the declared molecule-ai-plugin-molecule-platform-mcp#main then installs → /configs/.claude/settings.json gains mcpServers.molecule-platformcreate_workspace exposed.

Status of related work (all merged this session)

  • #3055 SaaS restart re-stub fix · #3049 gitea:// declaration · #3058 provision-request contract producer-pin (+ controlplane #871 consumer test). The declaration + restart layers are done + verified; THIS image/runtime gap is what still blocks create_workspace.

Refs: RFC #3045, #3049, project_saas_restart_re_stub_config. Task #52 (verify concierge create_workspace) is NOT satisfiable until this lands.

## Gap: concierge DECLARES the management-MCP plugin but never INSTALLS it (no create_workspace) #3049 made the org concierge correctly declare its management MCP as a pinned gitea:// plugin — **verified live** on a fresh staging concierge: ``` workspace_declared_plugins: molecule-ai-plugin-molecule-platform-mcp | gitea://molecule-ai/molecule-ai-plugin-molecule-platform-mcp#main ``` But the plugin is **never installed on the box**, so `create_workspace` is still not exposed. ## Root cause (SSM, fresh staging concierge box, 2026-06-19) The concierge runs the **special `molecule-platform-agent` image** (`153263036946/.../molecule-platform-agent@sha256:1c3c...`). On that box, after 11+ min online: - `/configs/plugins` is **empty**. - `docker logs molecule-workspace` has **~zero** plugin/gitea/declared/boot-install lines. - `grep -rilE 'workspace_declared_plugins|boot-install|skip.unsupported.source' /app` → **no matches** — the image **does not contain the declared-plugin boot-install** that standard runtime images (claude-code, seo-agent) have. - `MOLECULE_TEMPLATE_REPO_TOKEN` **is** present on the box (so a boot-install, if present, could fetch). Standard runtimes install declared gitea:// plugins (seo-agent installs `seo-all` — template-delivery-e2e passes). The concierge can't, because its image lacks the pipeline. ## Fix (RFC #3045 — the incomplete half) RFC #3045 (CTO-approved) was: deliver the management MCP as a plugin via `MCPServerAdaptor` **and retire the special `molecule-platform-agent` image**, running the concierge on a standard plugin-capable runtime. #3049 delivered only the *declaration*. The remaining keystone: - Run the concierge on a standard runtime image (claude-code) that performs the declared-plugin boot-install + `MCPServerAdaptor`, OR - Add the plugin boot-install entrypoint to the `molecule-platform-agent` image. Either way the declared `molecule-ai-plugin-molecule-platform-mcp#main` then installs → `/configs/.claude/settings.json` gains `mcpServers.molecule-platform` → `create_workspace` exposed. ## Status of related work (all merged this session) - #3055 SaaS restart re-stub fix · #3049 gitea:// declaration · #3058 provision-request contract producer-pin (+ controlplane #871 consumer test). The declaration + restart layers are done + verified; THIS image/runtime gap is what still blocks `create_workspace`. Refs: RFC #3045, #3049, project_saas_restart_re_stub_config. Task #52 (verify concierge create_workspace) is NOT satisfiable until this lands.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: molecule-ai/molecule-core#3063