feat(claude): emit manifest metadata fields and pin component path rules (#187) - #293
Merged
Merged
Conversation
🦋 Changeset detectedLatest commit: 3396bfa The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
ScriptedAlchemy
force-pushed
the
feat/187-s2-manifest-metadata
branch
from
September 2, 2026 06:41
ec8ab03 to
3396bfa
Compare
commit: |
This was referenced Sep 2, 2026
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
ClaudeHostConfiggainsdisplayName,metadata(free-form object), anddefaultEnabled; they emit into.claude-plugin/plugin.jsonwith plan-time validation (claude.manifest.displayName.invalid,claude.manifest.metadata.invalid,claude.manifest.defaultEnabled.invalid).metadata, but the compiler rejects it.commands/agents/workflows/outputStyles/experimental.*replace,skillsadds,./prefix,.skills exception since 2.1.221, ignored-default-folder warning) pinned as aplugin.pathscapability block with dated doc citations; the generator deliberately keeps emitting the canonical default layout only.commands/checklist item: flat.mdemission already landed; custom-path discovery is documented host behavior with a native positive probe.manifestMetadataandmanifestPaths; unified plugin adapter rows unavailable per the lsp precedent. Claude adapter 1.9.0 → 1.10.0, plugin adapter 1.8.0 → 1.9.0."commands": "./custom/deploy.md"manifest with no defaultcommands/.Test plan
pnpm typecheckpnpm lintPart of #187 (slice 2).