You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Compact generated catalogs and dynamically split oversized Community catalogs into balanced alphabetical ranges below the firmware-safe byte limit.
Publish a dynamic catalog-list index so native Plugin Hub can follow Community catalog splits without requiring a plugin update.
Add blacklist.json; repositories listed there are omitted from every generated catalog before whitelist or curated-source ingestion is applied.
Add optional curated DETAILS.md payload content, convert its safe Markdown subset to versioned semantic HTML during catalog generation, and publish rich-details metadata for the current CrossPoint plugin contract.
Keep catalog.json as the union catalog feed while browse.lists_url drives the current dynamic Community catalog navigation.
Propagate optional plugin compatibility metadata through release discovery, curated catalogs, and release-asset imports, normalize it for native firmware filtering, and map the compatibility fields in device.json.
Align the browser WebUI with firmware plugin discovery across /.crosspoint/plugins, /plugins, and /.plugins, preserving an existing plugin's root for update, reinstall, and removal.
Let the browser WebUI fall back to the built-in Community catalog URL when the dynamic catalog-list index is temporarily unavailable.
Publish all currently discovered plugins through the single user-facing Community Plugins catalog and remove the dormant Official catalog/policy path.
Show Plugin Hub v0.1.6 in the installed Plugins picker.
Keep Plugin Hub itself discoverable in Community Plugins so installed copies can be updated through the normal catalog bundle update path.
Reset automatic discovery to the folder-first repository standard: one plugin repository with exactly one direct child <plugin-id>.crosspoint-plugin/ installable payload directory.
Keep Plugin Hub itself as the intentional root-layout exception so its firmware bootstrap, root catalogs, and production stable branch remain unchanged.
Add PLUGIN_HUB_AGENT_GUIDE.md so developers can hand the publishing workflow directly to an AI coding agent.
Consolidate the authoritative publishing, catalog, manifest, capability, and maintainer rules into PLUGIN_HUB_CONTRACT.md; keep the README as a project overview instead of a duplicate specification.
Move Plugin Hub's canonical repository identity, runtime/catalog URLs, bootstrap source, generated mirrors/details, and self-update endpoint to crosspoint-reader/crosspoint-plugin-hub after the repository transfer, with no pre-release old-repository compatibility layer.