Source conflicts

Contradictions and open questions

Public sources can disagree because they describe different roles, revisions, package formats, or products. The catalog keeps each conflict visible until a source or schema change resolves it.

open

Agent Plugins support in ChatGPT and Codex

S-050The Agent Plugins compatible-client list names ChatGPT and Codex for the open package format.

S-090OpenAI first-party documentation describes a vendor package centered on .codex-plugin/plugin.json.

HandlingKeep open-standard and vendor-native package assertions separate; do not infer package-level conformance from either statement alone.
resolved-by-model

MCP support as a single claim

S-019MCP defines independent client and server primitives, transports, and utilities.

S-136Zed documents implemented MCP primitives and missing coverage separately.

HandlingDecompose MCP into atomic features and never publish one brand-level boolean.
open

Hosted product versioning

methodBrowser compatibility normally targets enumerable product releases.

S-088Hosted agent surfaces can change without a stable public build identifier.

HandlingUse dated hosted observations and evidence timestamps; never fabricate releases.
resolved-by-model

Plugin hooks portability

S-113VS Code supports host-specific plugin namespaces and compatible hook shapes.

S-053Agent Plugins 1.0 does not define hooks as a portable core component.

HandlingRepresent hooks as host extensions instead of portable Agent Plugins core support.
open

Gemini ACP naming and version

S-132Gemini CLI exposes an ACP mode in its configuration surface.

S-065ACP evolves independently and remote transport work remains in progress.

HandlingRequire protocol revision, transport, and role instead of treating a flag as full conformance.

Needs a decision

Open questions

These questions do not block publication. They do prevent a general "verified" claim.