@stolyarovmn/dsh-ui-registry-aggregator 0.5.3

@stolyarovmn/dsh-ui-registry-aggregator 0.5.3

Stable promotion of 0.5.3-rc.1 for the current DeepSeek Harness 0.2.1-rc.4 target. Runtime code is unchanged from the validated RC.

Included

• Sources, Browse, and Updates integrate through the official DSH 0.2.1 plugins.tab root slot;
• the old DOM polling bridge remains only as a compatibility fallback for 0.2.0-rc.2;
• Browse artwork resolution supports the current DSH display resource contract exports["./icon"];
• transient npm/unpkg/GitHub artwork failures are not cached as confirmed icon absence;
• package exports "./icon": "./icon.svg" and keeps icon.svg in the published files.

Compatibility

• Declares @deepseek-ai/dsh >=0.2.0-rc.2 <0.3.0.
• Isolated install + Web boot smoke passes on DSH 0.2.0-rc.2, 0.2.1-rc.2, 0.2.1-rc.3, and 0.2.1-rc.4.
• Real DSH 0.2.1-rc.4 Chromium validation passed before promotion.

Validation

• repository tests and JavaScript syntax checks pass;
• npm pack --dry-run passes;
• real RC4 browser smoke verified native Registry tabs, Browse results, SVG artwork for both plugins, the native Automation Tasks manager, and no plugin/runtime crash.

This version is the stable npm release and is intended to be published under dist-tag latest.

@stolyarovmn/dsh-ui-registry-aggregator 0.5.3-rc.1

@stolyarovmn/dsh-ui-registry-aggregator 0.5.3-rc.1

Release candidate focused on DeepSeek Harness 0.2.1-rc.4 compatibility, native Plugin Manager integration, and reliable plugin artwork.

Fixed

• A transient npm/unpkg/GitHub failure while resolving artwork no longer gets cached as a confirmed "no icon" result. The next refresh can retry immediately instead of preserving a generic icon for the negative-cache TTL.
• Browse artwork resolution now recognizes the current DSH display-resource contract exports["./icon"] in addition to the legacy top-level icon field.
• DSH 0.2.1 no longer relies on the old 0.2.0-rc.2 DOM polling workaround to expose Registry navigation.

Native DSH 0.2.1 integration

• Sources, Browse, and Updates register through the official plugins.tab root slot exposed by the DSH 0.2.1 Plugin Manager.
• The old DOM bridge remains only as a compatibility fallback for 0.2.0-rc.2, where the root tab slot was not available.
• The existing plugins.bundle.config detail-page surface remains available as a fallback/detail UI.

Packaging

• Exports "./icon": "./icon.svg" and keeps icon.svg in the published files.
• Keeps the compatibility range @deepseek-ai/dsh >=0.2.0-rc.2 <0.3.0; isolated install/boot smoke covers the currently tested 0.2.x candidates.
• Prerelease publication uses npm dist-tag next; stable releases keep the default npm tag.
• Re-running the release workflow for an already-published version does not republish it.

Validation

• Repository tests and JavaScript syntax checks pass.
• npm pack --dry-run passes.
• Published-artwork probes successfully resolve the existing Registry Aggregator 0.5.2 and Schedule Tab 0.8.0 SVGs from npm/unpkg.
• Isolated install + Web boot smoke passes on DSH 0.2.0-rc.2, 0.2.1-rc.2, 0.2.1-rc.3, and 0.2.1-rc.4.
• Real DSH 0.2.1-rc.4 Chromium validation passed end-to-end: both RC packages load into the native Plugin Manager, Sources / Browse / Updates render through plugins.tab, both Browse cards resolve SVG data URLs, the native Automation Tasks manager opens, and no plugin/runtime crash is reported.

This is intentionally published as an RC under npm dist-tag next; it is not promoted to the stable npm tag.

v0.5.2

Registry Aggregator v0.5.2

0.5.2 promotes the manually verified 0.5.2-rc.6 line for DeepSeek Harness 0.2.x. This release moves Registry Aggregator's discovery and update workflow onto the main Plugins page while keeping package lifecycle in the native DSH Plugin Manager.

Highlights

• Main Plugins workflow — Installed | Sources | Browse | Updates now lives directly on the main Plugins page and follows the native Installed heading/count visual language.
• Native Installed stays native — the original DSH Installed package cards remain the Installed view rather than being replaced by a duplicate list.
• Update from Installed — installed packages with a newer eligible version get an Update → vX.Y.Z action directly beside the native package controls.
• Update all — eligible installed updates can be processed sequentially from the main Plugins page; Registry Aggregator updates itself last.
• Live update count — the main Updates entry shows how many updates are currently available.
• Browse without opening the plugin — Sources, Browse, and Updates can be used directly from the Plugins page; plugins.bundle.config remains available inside Registry Aggregator as the supported fallback/detail view.

Stability fixes

• The DSH 0.2.0-rc.2 compatibility bridge now waits until the native Plugin Manager inventory has finished loading before mounting, avoiding the observed pluginManager/listBundles skeleton hang.
• The previous MutationObserver-based approach is gone; the bridge reconciles slowly after native inventory is ready.
• Opening a plugin detail page tears down the main-page surface, fixing the duplicate Registry Aggregator UI that previously remained above the detail page.
• Native Installed DOM visibility is restored when the bridge is disposed.

DSH 0.2.0-rc.2 integration note

Stock DSH 0.2.0-rc.2 does not expose a supported list-level Plugin Manager slot. The main Plugins-page integration is therefore an explicit, version-pinned rc.2 compatibility bridge. It is intentionally isolated from the old DSH 0.1.x compatibility line and should be replaced by a native slot when DSH exposes one.

The normal detail-page integration continues to use the supported plugins.bundle.config slot.

Compatibility

• DSH peer range: >=0.2.0-rc.2 <0.3.0
• Validation baseline: DSH 0.2.0-rc.2
• Compatibility evidence is evaluated against the actually running DSH version.
• DSH 0.1.x users should remain on the historical v0.4.17 / dsh-0.1.7 line.

Validation

• JavaScript syntax checks
• repository unit/client contract tests
• npm package dry-run validation
• isolated DSH 0.2.0-rc.2 install smoke test
• manual verification in the real Harness UI of the main Plugins-page Installed | Sources | Browse | Updates navigation and Browse results

The verified UI screenshot is included in the README.

Known limitations

• build-script approval remains in the native Add plugin dialog;
• Update all cancellation is not implemented yet;
• automatic update discovery does not yet cover GitHub-only installed dependencies without npm package identity;
• the main Plugins-list surface is a DSH 0.2.0-rc.2 compatibility bridge until a supported list-level Plugin Manager slot exists.

Install

$DSH_VERSION = "0.2.0-rc.2"
$PROFILE = "dsh-020-test"
$env:DSH_HOME = "$env:USERPROFILE\.dsh-020-test"

pnpm dlx "@deepseek-ai/dsh@$DSH_VERSION" plugin --profile $PROFILE add "@stolyarovmn/dsh-ui-registry-aggregator@0.5.2"
pnpm dlx "@deepseek-ai/dsh@$DSH_VERSION" --profile $PROFILE

v0.5.1

Registry Aggregator v0.5.1

0.5.1 promotes the manually verified 0.5.1-rc.1 line for DSH 0.2.x. This patch release focuses on plugin artwork coverage and clearer action semantics in the Updates view.

Highlights

• Broader package artwork recovery — the official DSH top-level manifest icon remains the first choice. When it is absent, npm-discovered packages can now recover their GitHub repository from npm manifest metadata and use a safe repository-local README logo/icon as a fallback.
• Safer GitHub fallback — a missing or unreadable repository package.json no longer prevents README artwork discovery.
• Native installed artwork in Updates — installed update rows reuse the native Plugin Manager BundleInfo.meta.icon when available instead of showing a generic plugin glyph.
• Clear Refresh vs Update semantics — content/list refresh keeps the single-arrow Refresh glyph, while package update actions use a distinct local two-arrow Update glyph consistent with the DSH visual language.
• Artwork safety remains bounded — fetched fallback artwork is restricted to repository-local SVG/PNG/JPEG/WebP files and the existing 256 KiB limit.

Compatibility

• DSH peer range: >=0.2.0-rc.2 <0.3.0
• Validation baseline: DSH 0.2.0-rc.2
• DSH 0.1.x users should stay on the historical v0.4.17 / dsh-0.1.7 line.

Validation

• Repository unit/client contract tests
• JavaScript syntax checks
• npm package dry-run validation
• isolated DSH 0.2.0-rc.2 install smoke test
• manual verification in the real Harness UI of Browse artwork recovery and the visual distinction between Refresh and package Update actions

Install

$DSH_VERSION = "0.2.0-rc.2"
$PROFILE = "dsh-020-test"
$env:DSH_HOME = "$env:USERPROFILE\.dsh-020-test"

pnpm dlx "@deepseek-ai/dsh@$DSH_VERSION" plugin --profile $PROFILE add "@stolyarovmn/dsh-ui-registry-aggregator@0.5.1"
pnpm dlx "@deepseek-ai/dsh@$DSH_VERSION" --profile $PROFILE

v0.5.0

Registry Aggregator v0.5.0

0.5.0 is the first stable Registry Aggregator release for the clean DSH 0.2.x architecture. It promotes the manually verified 0.5.0-rc.14 line and intentionally carries no DSH 0.1.x compatibility layer.

Highlights

• Native DSH 0.2 integration — Registry Aggregator lives in the native Plugin Manager detail page and keeps install/enable/disable/uninstall lifecycle ownership in DSH.
• Federated Sources — npm, GitHub, custom JSON, and corporate catalogs can be enabled, disabled, refreshed, added, removed, counted, and health-checked independently.
• Fast Browse — empty search shows popular packages; search combines enabled sources with compact source/release/freshness/tag/compatibility/page-size filters.
• Combinable sorting — relevance, stars, downloads, freshness, and name can be combined; active criteria contribute equally through percentile-normalized ranking.
• One-click install — Browse delegates package inspection and installation to the native remote.pluginManager API and tracks installed state from native bundle inventory/events.
• Compatibility evidence — package peer ranges are evaluated against the DSH version that is actually running. Cards show Compatible, Incompatible, or Not verified, and Browse can filter by compatibility.
• Package evidence — cards can show explicit package versions, GitHub stars, release/repository freshness, package artwork, npm 30-day downloads, and lazy lifetime npm download totals.
• Updates — npm-backed installed bundles are checked for newer versions and can be updated through the native Plugin Manager.
• DSH-native visual language — compact filters, switches, icon actions, hairline borders, semantic state colors, and layout behavior follow the DSH 0.2.x Plugin Manager conventions used by this release.
• Host-side hardening — network RPC uses bounded responses, timeouts, redirect validation, DNS pinning, and private-network blocking.

Compatibility

• DSH peer range: >=0.2.0-rc.2 <0.3.0
• Validation baseline: DSH 0.2.0-rc.2
• Compatibility badges use the active DSH installation version at runtime rather than a hardcoded RC value.
• DSH 0.1.x users should stay on the historical v0.4.17 / dsh-0.1.7 line.

Validation

• Repository unit/client contract tests
• JavaScript syntax checks
• npm package dry-run validation
• isolated DSH 0.2.0-rc.2 install smoke test
• manual UI verification of the promoted 0.5.0-rc.14 build in the real Harness UI, including Sources, Browse, filtering/sorting, compatibility status, package download evidence, and install controls

Known limitations

• Build-script approval remains in the native Add plugin dialog.
• Bulk Update all / cancellation is not included in this DSH 0.2.x release line yet.
• GitHub-only installed packages without npm package identity are not yet included in automatic update discovery.

Install

$DSH_VERSION = "0.2.0-rc.2"
$PROFILE = "dsh-020-test"
$env:DSH_HOME = "$env:USERPROFILE\.dsh-020-test"

pnpm dlx "@deepseek-ai/dsh@$DSH_VERSION" plugin --profile $PROFILE add "@stolyarovmn/dsh-ui-registry-aggregator@0.5.0"
pnpm dlx "@deepseek-ai/dsh@$DSH_VERSION" --profile $PROFILE

v0.4.17-rc.3

What's Changed

• docs: add DSH UI code reference by @Stolyarovmn in #44
• docs: pin UI reference to DSH 0.1.7-rc.2 by @Stolyarovmn in #45
• docs: add DSH styling rules to UI reference by @Stolyarovmn in #46
• feat: plugin updates and DSH 0.1.7-rc.2 compliant Registry UI by @Stolyarovmn in #43

Full Changelog: v0.4.16...v0.4.17-rc.3

v0.4.17

Registry Aggregator v0.4.17

0.4.17 promotes the tested 0.4.17-rc.3 build to the stable latest channel.

Highlights

• Plugin updates — installed bundles and Registry Updates cards can start updates through the DSH Plugin Manager.
• Update all — available updates run sequentially, with cancellation stopping the active operation where possible and preventing the remaining queue from starting.
• Cancellable operations — individual update actions expose progress and cancellation through Plugin Manager request ids.
• Compact Add Source — Name, Type, Catalog/API URL, Cancel, and Add fit into a much shorter desktop form.
• DSH-aligned UI — controls, borders, radii, state colors, links, and card behavior were aligned with the DSH 0.1.7-rc.2 UI conventions used by this release.
• Actionable installed Browse results — an installed plugin with a newer discovered version now exposes Update rather than a disabled install action.
• Compatibility floor — the package and CI smoke test now target DSH 0.1.7-rc.2.

Compatibility

• DSH: >=0.1.7-rc.2 <0.2.0
• Tested with DSH 0.1.7-rc.2

Validation

• Repository unit/UI scenario suite
• npm package dry-run validation
• isolated DSH 0.1.7-rc.2 install smoke test
• manual UI verification of the promoted 0.4.17-rc.3 build

This stable release intentionally promotes the known-good rc.3 implementation without the later experimental UI rewrite.

v0.4.16

Registry Aggregator v0.4.16

This release integrates Registry Aggregator directly into the native DSH Plugins page and improves Installed/Browse metadata consistency.

Highlights

• Native Plugins-page integration — Registry Aggregator self-embeds below DSH Installed on stock DSH without a manual UI patch.
• Installed card enrichment — native Installed cards get update badges and expandable registry metadata while DSH title, enable/disable, and navigation controls remain native.
• Exact Installed metadata — installed packages resolve through exact npm lookup with downloads, GitHub stars/repository freshness, bundle verification, tags, and DSH compatibility.
• Shared card presentation — Installed details reuse the Browse card presentation but suppress duplicate title, description, install controls, and command text already represented by the native card.
• Correct star sorting — missing GitHub star evidence is resolved before server-side Stars sorting and pagination.
• Consistent popularity UI — GitHub stars use the same highlighted treatment in Browse and Installed.
• Runtime compatibility — DSH compatibility is derived from the active DSH runtime and declared DSH peer dependencies.
• Persisted Browse state — query, filters, ordered sort criteria, selected tab, and page size persist across openings.
• Cache hardening — metadata/evidence caches are bounded and identical concurrent requests are coalesced.
• Resilient source behavior — exact npm package lookup is isolated from unrelated GitHub Search failures.

Compatibility

• DSH: >=0.1.7-rc.1 <0.2.0
• Tested with DSH 0.1.7-rc.2

Validation

The release is intended to be published only after the repository CI suite, package dry-run validation, and isolated DSH install smoke test pass.

v0.4.15

Registry Aggregator v0.4.15

This release focuses on reliability, source-state clarity, and tighter integration with the native DSH Plugin Manager.

Highlights

• Reliable Sources status — npm/GitHub health checks are lightweight and separate from verified bundle counting.
• Independent verified counts — npm and GitHub package/repository counts load independently and show native DSH progress while calculating.
• Resilient GitHub access — transient network/HTTP failures are retried, while GitHub health no longer consumes Search API quota.
• Installed bundle awareness — Browse reads native pluginManager.listBundles(), shows Installed <version>, and prevents duplicate installs.
• Update visibility — newer discovered versions are shown as Update available <installed> → <available> without pretending DSH has an in-place update API.
• Cancel install — active installs can be cancelled through native pluginManager.cancelInstall(requestId) while preserving the existing install progress UI.
• npm + GitHub provenance — npm-discovered plugins with a GitHub repository are enriched through exact repository lookup and can show both source badges without paging through hundreds of GitHub Search results.
• Search relevance — exact package/name matches are promoted only in the client presentation layer; existing stars, downloads, evidence, paging, and explicit sorting are unchanged.
• Sources refresh fixes — Refresh remains usable during long count calculations and immediately rechecks health/count state.

Compatibility

• DSH: >=0.1.7-rc.1 <0.2.0
• Tested with DSH 0.1.7-rc.2

Validation

The release candidate passed the repository CI suite, package dry-run validation, and isolated DSH install smoke tests before release.

v0.4.14

Registry Aggregator 0.4.14

This release publishes the package from the canonical renamed repository through npm Trusted Publishing.

Highlights

• canonical repository: Stolyarovmn/dsh-ui-registry-aggregator;
• npm package: @stolyarovmn/dsh-ui-registry-aggregator;
• Trusted Publisher uses .github/workflows/publish.yml;
• README screenshots and repository metadata point to the renamed repository;
• Browse/search behavior is unchanged from the working 0.4.13 baseline;
• GitHub stars remain hydrated asynchronously after results render.

Compatibility

• DeepSeek Harness: >=0.1.7-rc.1 <0.2.0
• tested with DSH 0.1.7-rc.1