spike(content-node): what Kubo cannot do, and whether a custom Boxo service is justified #71

Summary

Decide which gaps, if any, need custom Go code built on Boxo rather than configuration of Kubo.

Estimated size: S

Proposal

• Check, against the Kubo release we pin, whether it can: serve a Pinning Service API (as a server), restrict its gateway to an allowlist of CIDs, and apply a takedown denylist.
• For each gap, recommend: configuration, reverse-proxy rule, existing tool, or custom Boxo service, with the cost of owning Go code in this repo.

Acceptance criteria

• A written yes or no per gap with a link to the docs checked.
• Follow-up issues opened only for the gaps that need code.

Dependencies

• feat(infra): run Kubo in docker-compose (server profile, pinned version) #59

Part of #43. Ground rules for the content layer: no secrets in the repo, content-layer failures must never block or discard quantum execution, and tests and docs ship with every PR.