Troubleshooting and evidence

Common distinctions

Manifest is visible, content is not installed

Retrieve the complete content or every chunk, verify size and digest, then ask for installation approval. Discovery alone is not delivery.

The client shows no prompt

The host may not support elicitation. Use the published resources or fallback tool and present the choices in the host's supported interaction.

The offer appears on a new stateless connection

Without an exact release acknowledgement or client installation context, the server intentionally does not fingerprint the machine.

A chunk was returned

It is not the complete skill. Reconstruct all indexed chunks and verify the complete digest.

The skill was installed but no hook runs

Expected: hooks, schedulers and improvement runners are separate client capabilities and require their own configuration, support checks and approvals.

A write response was lost

Use the durable operation identity and reconcile the original outcome. Do not infer rollback from a timeout.

Evidence

The implementation qualification is recorded in docs/qualifications/openepm-mcp-skill-delivery-2026-11-06.json. It covers exact resource bytes, digest and chunk reconstruction, consent-state separation, connection-scoped offer behavior, authorization boundaries, Codex-free server packaging, negative native-dependency detection and the owner-laptop rollout. It does not prove that a particular client installed the skill or activated a client runtime.

See the published skill tool and resource contract for the exact retrieval interface.