v0.1.13

Preserve existing plugin config.json settings during browser updates and reinstalls while installing defaults for new users. Protect plugin credentials against unsafe FAT filename variants, 8.3 aliases, and duplicate paths. Add automated installer regression coverage.

v0.1.12

Plugin Hub v0.1.12 adds optional capability-aware discovery of Community Plugins, Themes and Wallpaper Packs. Stock CrossPoint retains the existing plugin-only Community catalog; additional catalogs appear only when firmware advertises the required capabilities. Device and PSRAM metadata is advisory and does not block manual installation. This update also improves resolution-aware theme and wallpaper package validation and keeps the official pluginhub identity and stable bootstrap.

v0.1.11

Unify Themes and Wallpaper Packs with the Plugin Hub catalog-details contract. The catalog now validates packaged DETAILS.md and descriptions directly from release ZIPs, publishes versioned rich-details pages, and preserves the existing plugin catalog and browser-plugin behavior. Includes publishing guides and regression tests.

Plugin Hub

Plugin Hub 0.1.10 adds an optional capability-aware catalog index to the on-reader manifest, preserves the legacy plugin catalog, and documents self-contained plugin/theme/wallpaper authoring, capability compatibility, and catalog publication.

v0.1.9

Adds capability-aware Community Themes and Wallpaper Packs catalogs and an opt-in extended catalog index. Legacy plugin catalogs and installation behavior remain unchanged. Firmware installation support follows separately.

v0.1.8

Plugin Hub v0.1.8 removes the version suffix from the installed on-device plugin title, keeps the version in manifest and device metadata, updates documentation, and validates release metadata before packaging. Stable promotion and catalog refresh now synchronize the stable bootstrap branch with the newest eligible main commit while guarding against unreleased runtime changes.

Plugin Hub v0.1.7

Plugin Hub 0.1.7

Compatible with stock CrossPoint Nightly and Razor-Crest.

• Use a full-width, right-aligned action column in the browser plugin catalog, with a responsive layout on narrower screens.
• Keep Install in the default style, highlight Reinstall in yellow and Remove in red.
• Confirm removals and recursively clean plugin installation files, including nested assets, without deleting separate persistent plugin settings.
• Support Razor-Crest's selected-plugin Reinstall handoff while preserving the existing CrossPoint Nightly browser UI.

Tested on CrossPoint Nightly. Automated checks: 4 browser tests and 42 catalog tests passed.

Plugin Hub v0.1.6

Plugin Hub 0.1.6

• 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.

v0.1.5

Hotfix stable Plugin Hub to Community-only catalog

v0.1.4

Plugin Hub 0.1.4 adds forward compatibility with the newer firmware plugin-directory API while preserving support for older firmware.

• Uses api.dir when available to locate Plugin Hub's real runtime directory.
• Stores config as plugin-local config.json on newer firmware.
• Falls back to /.crosspoint/plugin-hub.json on older firmware.
• Migrates legacy config settings forward without deleting the old file, preserving downgrade compatibility.
• Reads its own manifest.json from the actual runtime directory for self-version detection.
• Adds regression coverage for both legacy and api.dir firmware behavior.