How should resellers scope delivery across downloads and an MCP interface?

A reseller can ask for a delivery manifest containing `release_id`, `schema_version`, `content_digest`, `licence_reference` and the supported access methods. Downloads and MCP responses should identify the same release when they expose equivalent content.

For an MCP interface, scope tools or resources that retrieve case bundles, list task definitions or return policy text. Define pagination, filtering and missing-record responses before customers build integrations. A request for a fixed release should not silently return content from a newer one.

The pilot can compare a downloaded case bundle with the same case retrieved through the interface. Check stable identifiers, field meanings and whether either channel omits attachments or context needed to answer the task. If the interface returns only excerpts, that limitation should be explicit.

Also clarify how licence information and generated-content notices remain accessible when records travel through automated systems. A notice on a download page alone may not accompany a tool response. Versioned metadata gives downstream customers a practical way to document what they used and lets the reseller investigate discrepancies without guessing which package or interface state produced them.