Plan collections in the plugin: tabs, whole-collection install, abilities

[pbking]

Summary

The plugin half of the collections design agreed on 2026-09-02, as a design document: docs/collections.md. No code changes. The service side, which is the contract this builds on, is the matching PR in Twenty-Bellows/patternbuilderwp.com (docs/collections.md there, plus product, architecture and decisions D30–D36).

What the plugin plan covers:

• Proxy routes for collections (community list and detail, the account's collections CRUD, upload and update carrying a collection, /cloud/status with the new entitlements shape), and the one PHP method that installs a whole collection, shared by the REST path and the ability.
• Community tab collections-first: collection tiles, a collection view with Save collection to this site (one destination, one design-tokens step for the union, sequential progress, skip-if-installed, failure list), search in two groups, and the local pattern category footprint named for the collection.
• Uploaded tab management: the collections rail with Personal locked and metered, create, rename, describe, visibility where allowed, delete with the delete-or-move prompt, move pattern, the over-policy banner.
• Upload picker in the cloud panel when there is more than Personal.
• Seven agent abilities: list-collections, get-collection, search-cloud-patterns, install-collection, install-cloud-pattern, upload-pattern, create-collection. All through the WordPress user's own connection; none changes visibility or deletes.
• Code map, tests, order of work as commits, and acceptance criteria.

Test plan

• Documentation only; nothing to run.

🤖 Generated with Claude Code

https://claude.ai/code/session_01DWfn4hJb2BSiyeCLemmNgg

---

Generated by Claude Code