feat(core): catalog plugin resource events - #1191
Merged
Merged
Conversation
Plugins can now declare structured resource types with supported and suggested events. Core derives each plugin's namespace, validates published and selected events against the active runtime catalog, and exposes `searchResourceEventTypes` so the agent can discover the event capabilities that are actually enabled. Temporary resource watches now use the same `namespace + resource type + identifier + event type` contract. `watchResourceEvents` validates selections against the catalog, reports its expiry, and supports exact cancellation by watch ID. GitHub and Vercel publishers are migrated to the contract; GitHub additionally publishes exact-issue and repository-wide issue events. This is a hard cutover from `provider` / `resourceRef`. Existing short-lived Redis watch records remain under the old prefix and expire naturally rather than being migrated. This PR does not add durable event-task persistence or execution; that work will build on this catalog in a separate PR. Refs #1174
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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.
This is the exact catalog patch reviewed in #1184, replayed directly onto main because #1184 was accidentally merged into a feature branch.
Plugins can now declare structured resource types with supported and suggested events. Core derives each plugin's namespace, validates published and selected events against the active runtime catalog, and exposes searchResourceEventTypes so the agent can discover the event capabilities that are actually enabled.
Temporary resource watches now use the same namespace + resource type + identifier + event type contract. watchResourceEvents validates selections against the catalog, reports its expiry, and supports exact cancellation by watch ID. GitHub and Vercel publishers are migrated to the contract; GitHub additionally publishes exact-issue and repository-wide issue events.
This is a hard cutover from provider / resourceRef. Existing short-lived Redis watch records remain under the old prefix and expire naturally rather than being migrated. This PR does not add durable event-task persistence or execution; that work is in #1176.
Refs #1174