feat(dashboard)!: add dedicated System plugin pages - #1058
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
dcramer
changed the title
dcramer
marked this pull request as ready for review
July 26, 2026 22:00
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit f8efa53. Configure here.
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
1 participant
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.
System now gives each loaded plugin a dedicated
/system/plugins/:pluginpage, with a desktop navigation rail, a mobile view selector, manifest-backed details, capabilities and skills, and complete operational records on small screens. The overview keeps aggregate activity and plugin launch panels without inferred reporting-versus-available status counts. Plugin pages only claim that operational activity is absent after the report request succeeds with no data; loading, failure, and stale-report states remain distinct.The authenticated plugin inventory exposes only the safe manifest metadata needed by these pages. Both dashboard mounting layers now forward
/system/*, so copied links and refreshed plugin pages continue to work. The route docs and API/browser coverage follow the same contract, including a four-field mobile record and a direct deep-link reload.This is a hard naming cutover for the exported plugin inventory API:
pluginReportSchemabecomespluginSchema,pluginReportsSchemabecomespluginsSchema,PluginReportbecomesPlugin,PluginReportsbecomesPlugins, andreadPluginReportsbecomesreadPlugins. Consumers importing the old names must update them; operational report exports retain the explicitPluginOperationalReportnaming.