Pinning IPFS Dependencies for Policies, Tools, and others

When a policy or tool is published to the methodology library, I want to ensure that the IPFS file is pinned so that the policy will remain healthy and available even if the policy author's IPFS node goes offline

Considerations

* maintaining a dedicated pinning service or subscription for the methodology library
* providing clear guidance so authors understand how to make their policies remotely accessible with intention
* enforcing policies published to methodology library to be pinned
* IPFS at Shipyard shutting down https://ipshipyard.com/blog/2026-the-end-of-ipfs-at-shipyard/
* https://blog.ipfs.tech/2026-08-beyond-sponsored-gateways/
* Cloudflare IPFS Gateway, https://developers.cloudflare.com/web3/ipfs-gateway/

No files, tests, or entry points are identified. Start by reviewing the listed IPFS and Cloudflare references, then clarify the pinning approach and publication behavior required for policies and tools. Done is not defined beyond keeping published IPFS files available.

Written by the indexing model from the issue text.