feat(schema): add optional status enum to registry-schema#53
Merged
Conversation
Adds an optional `status` property (verified|experimental|deprecated) to the per-plugin manifest schema. The field is not required so all existing 59 manifests continue to validate; manifest population follows in PR-R2 (workflow Go struct side) and plugin README sweeps. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
There was a problem hiding this comment.
Pull request overview
This PR extends the plugin manifest JSON Schema (schema/registry-schema.json) to support an optional status field, enabling registry entries to express verification maturity (verified, experimental, deprecated) while keeping all existing manifests valid.
Changes:
- Added optional
statusproperty to the manifest schema. - Constrained
statusto an explicit enum:verified | experimental | deprecated.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Updates the Schema section description to include `status` in the list of enum fields defined by the schema. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
- Adds one-paragraph description of the optional `status` enum (verified/experimental/deprecated) under the Schema overview - Lists `status` as optional in the Manifest Requirements section Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
intel352
added a commit
that referenced
this pull request
May 19, 2026
Preceding commit body listed `agent` in the verified set, but plugins/agent/manifest.json has type=builtin — the population script correctly skipped it per the `type != "external"` guard. The 6-count was always correct; only the parenthetical name list was wrong. Correct verified set (6): audit-chain, digitalocean, eventbus, payments, twilio, workflow-plugin-auth. No manifest files changed; schema validation still passes. Part of 2026-05-19 OSS-readiness QoL sweep. See: GoCodeAlone/workflow#714 See: #53 See: GoCodeAlone/workflow#715 Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
intel352
added a commit
that referenced
this pull request
May 19, 2026
#54) * feat(registry): populate status field across external plugin manifests Sets status=verified on 6 established plugins (agent, audit-chain, digitalocean, eventbus, payments, twilio, workflow-plugin-auth) and status=experimental on 33 remaining external plugins. Private plugins (waf, security, sandbox, supply-chain, data-protection, authz-ui, cloud-ui, workflow-plugin-supply-chain) left unchanged. Built-in plugin manifests (type != "external") unchanged. Validated against schema/registry-schema.json (draft2020) — all 59 manifests pass. Negative assertion confirms no private-plugin manifests touched. Part of 2026-05-19 OSS-readiness QoL sweep. See: GoCodeAlone/workflow#714 See: #53 See: GoCodeAlone/workflow#715 Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * docs(registry): correct verified plugin list in preceding commit body Preceding commit body listed `agent` in the verified set, but plugins/agent/manifest.json has type=builtin — the population script correctly skipped it per the `type != "external"` guard. The 6-count was always correct; only the parenthetical name list was wrong. Correct verified set (6): audit-chain, digitalocean, eventbus, payments, twilio, workflow-plugin-auth. No manifest files changed; schema validation still passes. Part of 2026-05-19 OSS-readiness QoL sweep. See: GoCodeAlone/workflow#714 See: #53 See: GoCodeAlone/workflow#715 Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
statusproperty toschema/registry-schema.jsonwith enum valuesverified | experimental | deprecatedrequiredarray — all 59 existing manifests continue to passajv validate --spec=draft2020status: "bogus") correctly fail the enum checkstatusalongsidetypeandtierenumsStatus enum semantics
verifiedwfctl.yamlof an active GoCodeAlone projectexperimentaldeprecatedRelated
statusvalues on plugin entries) follows in PR-R2 once this PR + the workflow RegistryManifest struct PR both mergeStatusfield toPluginSummary(Task 1)Test plan
ajv validate --spec=draft2020 -s schema/registry-schema.json -d plugins/*/manifest.json→ all 59 passstatus: "experimental"→ validstatus: "bogus"→ fails enum checkRollback
Revert this PR. Existing manifests are unaffected —
statuswas never required, so manifests without the field continue to validate against the original schema. If Task 16 (manifest population CI) has already merged when a rollback is needed, revert Task 16 first to keep registry CI green, then revert this PR.🤖 Generated with Claude Code