feat(plugin): publish madtea through the omp plugin marketplace channel #560

Open
opened 2026-09-21 20:46:43 +00:00 by hexajon · 0 comments
Owner

Phase 2 of ADR 0039 (docs/decisions/0039-pi-first-class-harness.md). Refs #546.

ADR 0039 chose MCP wiring alone and deferred the omp-native plugin package. The channel is documented and scriptable: a .omp-plugin/marketplace.json manifest plus omp plugin install.

One trap the record names: a manifest mcpServers declaration replaces rather than merges a plugin's default .mcp.json. The packaging must not clobber a user's existing servers.

Acceptance criteria:

  • A marketplace manifest ships in the repo and omp plugin install works from it.
  • The manifest does not overwrite a user's existing mcpServers entries.
  • The release flow publishes the manifest with the plugin, and docs/contributing/releasing.md says how.
Phase 2 of ADR 0039 (docs/decisions/0039-pi-first-class-harness.md). Refs #546. ADR 0039 chose MCP wiring alone and deferred the omp-native plugin package. The channel is documented and scriptable: a .omp-plugin/marketplace.json manifest plus omp plugin install. One trap the record names: a manifest mcpServers declaration replaces rather than merges a plugin's default .mcp.json. The packaging must not clobber a user's existing servers. Acceptance criteria: - A marketplace manifest ships in the repo and omp plugin install works from it. - The manifest does not overwrite a user's existing mcpServers entries. - The release flow publishes the manifest with the plugin, and docs/contributing/releasing.md says how.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
sixfold-space/madtea#560
No description provided.