fix(manifest): point root plugin.json at Agent Plugins v1.0.0 - #1345
fix(manifest): point root plugin.json at Agent Plugins v1.0.0#1345tmchow wants to merge 1 commit into
Conversation
Swap the Antigravity $schema for the canonical Agent Plugins identifier, mirror public metadata, guard authoring rules in CI, and document posture (including skills-ref vs runtime nuance for Claude frontmatter).
Shakeyswings
left a comment
There was a problem hiding this comment.
LGTM — Approve.
This PR updates the root plugin.json to point at the Agent Plugins v1.0.0 schema, mirrors public metadata, adds CI authoring assertions, and records posture docs. Changes are limited to metadata, tests, and docs (no runtime/permission changes). I reviewed the diffs and the new guard tests; they address the conformance gap described in the PR.
Please convert this draft to a ready PR and wait for CI to finish; otherwise, this is approved and can be merged once CI is green.
Shakeyswings
left a comment
There was a problem hiding this comment.
LGTM — Approve.
This PR updates the root plugin.json to point at the Agent Plugins v1.0.0 schema, mirrors public metadata, adds CI authoring assertions, and records posture docs. Changes are limited to metadata, tests, and docs (no runtime/permission changes). I reviewed the diffs and the new guard tests; they address the conformance gap described in the PR.
Please convert this draft to a ready PR and wait for CI to finish; otherwise, this is approved and can be merged once CI is green.
Thanks for reviewing it. Just fyi you don't need to spend your tokens on automated reviews, we've got it covered :) Also can you ensure your bot isn't double posting comments? Thanks! |
Summary
Root
plugin.jsonused Antigravity’s$schemaURL, so a conformant Agent Plugins client must reject the whole package at the door. This PR points that manifest at the Agent Plugins v1.0.0 schema, mirrors public metadata, locks the authoring rules in CI, and records internal posture docs.Beyond the original plan-only branch, this includes the implementation of U1–U3 (manifest + guard + specs), not just the plan document.
What changed
plugin.json:$schema→https://agent-plugins.org/schemas/1.0.0/plugin.schema.json; author/homepage/repository/license/keywords mirrored from.claude-plugin/plugin.json;versionleft for release-please.tests/release-metadata.test.ts(schema const, name pattern, closed field set, author/value/extensionsshapes + negative fixtures).docs/specs/agent-plugins.md(posture +skills-refvs runtime nuance for Claude frontmatter); smalldocs/specs/antigravity.mdnote; plan underdocs/plans/.No skill frontmatter edits. No README marketing note. No converter target in this PR.
Skills frontmatter (explicit non-blocker)
Claude-only top-level keys (
argument-hint,disable-model-invocation) fail the referenceskills-refvalidator. That does not prove shipping Agent Plugins clients skip those skills—many clients ignore unknown fields. Runtime impact is unverified; optional converter remains follow-up only if a client requires reference-clean emission.Validation
bun test tests/release-metadata.test.ts(includes new guard suite)bun run release:validateagy plugin validate .andagy plugin validate ./.agy(v1.0.10)grok plugin validate .Related
cursor/agent-plugins-conformance-plan-c1d8)Security Disclosure
No security-relevant changes. Manifest metadata and test-only assertions only; no shell/exec, secrets, or permission surface changes.
Agent Disclosure