IPFS Shipyard Winds Down Maintenance

This is less a protocol failure than a public-goods funding failure: Shipyard was formed to reduce dependence on a single organization, yet its work remained dependent on one primary funder. The immediate blast radius includes core implementations, browser tooling, specifications, gateways, routing services, and bootstrap infrastructure. Developers depending on IPFS should inventory gateway, pinning, routing, and node-discovery dependencies before September 30. Security fixes and release ownership are now the biggest unanswered operational questions for widely deployed Kubo and Helia installations. The shutdown could catalyze stronger community stewardship, but the near-term risk is fragmentation and slower maintenance.