Publish an automated agent compatibility matrix

[Scriptception]

Problem

Five adapters are tested against repository expectations, but users cannot see which current agent versions, scopes, file locations, and invocation paths have been verified.

User outcome

Users can choose a supported target and understand exactly what Skilldeck will install and how to invoke it.

Scope

• Define supported, tested, and experimental status per agent and scope.
• Add adapter contract fixtures derived from current official formats.
• Record the verification date and relevant tool version.
• Document deprecation and urgent format-change handling.

Non-goals

• Guaranteeing compatibility with every future agent release.
• Installing into undocumented locations.

Acceptance criteria

• All five adapters appear in a public matrix with project/global scope and invocation behavior.
• CI validates rendered frontmatter, paths, and stamps against versioned fixtures.
• Unsupported scopes fail with an actionable message.
• A format change requires a matrix and changelog update.

Validation

• Smoke-test installation and invocation on each supported agent where automation is available.
• Manually verify any target that cannot run in CI and record the evidence date.

Relationships

• Required before the first verified release is declared broadly compatible.
• Informs the skill lifecycle policy.