A check that could only ever answer for itself
Build Phase 5 validated a manifest's dependencies by looking for a sibling manifest file in this repo. A dependency is, by definition, another plugin, so the check could only ever confirm things this repo builds. CC now owns the field: it is passed through to plugin.json, CC installs dependencies transitively at enable time, and refuses to enable or disable a plugin whose dependencies are unsatisfied.
1. Try a manifest value
| build passthrough | |
|---|---|
tests/schemas/test-plugin-schema.sh | |
claude plugin validate (measured on 2.1.251) |
Measured: the array form passes validate; a string in its place fails it ("Validation failed"). The Agent Plugins root manifest keeps its allowlist and does not carry the field; the Cursor manifest drops it.
2. Before and after
| before | after | |
|---|---|---|
| who checks a dependency exists | Phase 5, by sibling manifest file in manifests/ | CC, against the marketplace, at install and enable time |
| what a user sees when it is missing | nothing (the plugin installed anyway) | plugin enable fails naming the missing dependency |
| version constraints | not expressible | { "name", "version": "~2.1.0" } |
| ork's own dependencies | none | none (the field is pass-through; hq-ext declares its dependency on ork in its own repo) |