v0.1.2 — packaging metadata and manifest validation
Packaging metadata and manifest validation. No skill, theme, or token-contract changes — the install identifier is unchanged.
/plugin marketplace add Avinava/document-design-system
/plugin install document-design-system@document-design-system
Fixed
- The marketplace entry declared no
license,repository, ortags. A marketplace browser reads the entry, notplugin.json, so an MIT-licensed plugin appeared unlicensed. All three are now declared and checked againstplugin.jsonso they cannot drift.
Added
validate_repository.pynow validates both manifests, which previously only CI did. It enforces the two invariants the JSON schema cannot express: the marketplace must be named for the repository, and duplicated fields must agree. A reintroduced"skills"key is rejected.- Seven tests asserting the new checks actually reject. Suite: 28 → 35.
Note
displayName was deliberately not added. It is in neither the marketplace nor the plugin-manifest schema, and the CLI ignores it — a field that looks load-bearing but does nothing.
Full detail in CHANGELOG.md.