plugin-fleet-sweep
/plugin-fleet-sweep
Use when the DSH host itself has been upgraded (or is about to be) and the whole installed fleet of Web/client plugins must be checked against the new host - one or more surfaces broke, vanished, or need their compatibility re-verified and re-released. Also use after a host upgrade to sweep for silent breaks before the user reports them, and to run the per-plugin fix/release loop (branch, bump, changelog, tag, mirrors).
- Author
- oh-my-dsh ↗
- Repository
- dsh-plugin-upgrade-skill ↗
- Licence
- MIT
- Last repository change
- 18.10.2026
Assessment and security
- Files in this package
- 3
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 18.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Use when the DSH host itself has been upgraded (or is about to be) and the whole installed fleet of Web/client plugins must be checked against the new host - one or more surfaces broke, vanished, or need their compatibility re-verified and re-released. Also use after a host upgrade to sweep for silent breaks before the user reports them, and to run the per-plugin fix/release loop (branch, bump, changelog, tag, mirrors).
Original author description
Use when the DSH host itself has been upgraded (or is about to be) and the whole installed fleet of Web/client plugins must be checked against the new host - one or more surfaces broke, vanished, or need their compatibility re-verified and re-released. Also use after a host upgrade to sweep for silent breaks before the user reports them, and to run the per-plugin fix/release loop (branch, bump, changelog, tag, mirrors).
How it works
- Standing rules
- Workflow
- Report
SKILL.md preview
--- name: plugin-fleet-sweep description: Use when the DSH host itself has been upgraded (or is about to be) and the whole installed fleet of Web/client plugins must be checked against the new host - one or more surfaces broke, vanished, or need their compatibility re-verified and re-released. Also use after a host upgrade to sweep for silent breaks before the user reports them, and to run the per-plugin fix/release loop (branch, bump, changelog, tag, mirrors). --- # Sweep a Plugin Fleet Across a DSH Host Upgrade A host upgrade changes the contracts every plugin rides on at once. The unit of work is not one plugin: it is the fleet, swept in a fixed order, with one verdict per plugin and one release loop per broken plugin. The sweep runs against the REAL upgraded host - sources and Node-based tests passing prove nothing about browser-engine and runtime-surface changes. ## Standing rules 1. **Verify on the target host, not in sources.** A plugin "loads" when its client bundle is served, its CSS `style[data-plugin]` tag exists, and zero `slot entry crashed` / activation-failure records appear. A plugin "works" only when its surface marker is in the DOM and its expected requests fire. Record which of the two you have proven. 2. **One static sweep first, cheaply.** Grep every plugin source for the APIs the new host renamed or removed (from the target version's corridor cards in `plugin-upgrade/references/`) before touching a browser. Static hits are already verdicts: broken-until-fixed. 3. **Absence of errors is weak evidence.** A surface whose UI is interaction-gated (appears only after a paste, a file operation, a focus event) shows nothing in a idle sweep. For each plugin, know its trigger and either simulate it or mark the verdict "loaded, interaction path not exercised" instead of claiming success. 4. **Fix and release per plugin, never as a fleet commit.** Each broken plugin gets its own branch-or-main commit, version bump, changelog row, tag, and mirror push (the repositories' own mirror flow; `sync-mirrors.mjs` is specific to the author's plugin repositories - use whatever the target repository documents, or skip mirrors if it has none). Mixed fleet commits make per-plugin rollbacks impossible. 5. **Compatibility builds over host-locked builds** when the plugin must span host generations: resolve renamed host exports at runtime through a fallback chain (old name → new variants) instead of static named imports, and extend unit-test module mocks with every fallback name (strict mocks throw on undefined-export access and mask the real failure). ## Workflow 1. Read the target host version's corridor cards (`plugin-upgrade/references/v<target>.md`) and derive the static sweep patterns from them - the cards name the renamed/removed surfaces. 2. Static sweep: grep every fleet repository for those patterns; record hits as broken-until-fixed with file:line. 3. Live sweep: load the real GUI in a driven headless browser against the upgraded host and per plugin assert (a) the client CSS/style tag present, (b) zero `slot entry crashed` console records, (c) the surface's DOM marker present, (d) the expected requests fired. Method: [references/fleet-sweep-checklist.md](references/fleet-sweep-checklist.md) (includes the authenticated-GUI access and instrumentation discipline from `plugin-runtime-debug/references/browser-forensics.md`). 4. Re-verify interaction-gated surfaces with their trigger simulated (paste, file write, keyboard chord) or downgrade the verdict explicitly. 5. For each broken plugin: diagnose against the host source (`plugin-runtime-debug` standing rule), fix with a host-generation-compatible approach when the fleet spans host versions, run the plugin's typecheck/tests/build, then release: version bump, changelog/compatibility-table row naming the host version range, commit, tag, mirrors. 6. Re-run the live sweep after releases and record the final per-plugin verdict table (plugin, host versions supported, evidence). ## Report End with a per-plugin table: verdict (working / fixed+released / interaction-path-unexercised / broken), the host versions covered, and the evidence (which assertion passed where). Note any host bug found (report upstream with the minimal repro) and any hot-fix living in the install tree that the next host upgrade will overwrite - list the reapplication material.
Files in this package (3)
- README.md 1 KB
- SKILL.md 4 KB
- references/fleet-sweep-checklist.md 3 KB
Versions
The database has no other skills named plugin-fleet-sweep.
Database snapshot: 13.11.2026 · package version c33c7dc43895 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 98dsh-release
DSH 插件(@dely0/dsh-personal-workbench / dsh-team-memory / dsh-skill-hub 等)**公开发布**的硬门禁与命令序列:发布前置(用户实测确认)、范围表、改版本号、同步 README 版本历史与致谢、写 Release Notes、发版前检查(PII 两面 + 变异探针)、打 tag、pnpm publish 到 npm、用 REST 建 **GitHub Release**、发布后复核(**tarball 与 shasum 对账**)。当你要「发版 / 发布 / 打 tag / 发 npm… - 95dsh-upgrade
安全升级 DeepSeek Harness (dsh):预检、切换、验证、回滚。Use when upgrading or migrating dsh to a new version, when dsh fails to start after an upgrade (duplicate loader entry id, cannot get property without inject, notarget, UNKNOWN_MODEL), when plugins break after a dsh bump, or when you need… - 100release-this
Orchestrates the full powerball-harness plugin release with build, validation, version bump, CHANGELOG, tag, and GitHub Release. Use when releasing this plugin. - 100release
CONTRIBUTOR TOOL - Cut a plugin release: bump plugin.json version, finalize CHANGELOG, update README if needed, gate on make ci, commit, tag vX.Y.Z, and create the GitHub release. Use when shipping a new plugin version. NOT distributed. - 90dsh-upgrade-pitfalls
Use when upgrading the DSH desktop app or the global dsh CLI, when a plugin stops working after an upgrade, or when a request fails with 401/431 before any model call is made — version lockstep, plugin compatibility budget, header-size limits, post-upgrade smoke checklist. DSH… - 100release
Publish a new version of the account-rotator plugin - pick the version, write its CHANGELOG entry, bump plugin.json, push, tag it with `claude plugin tag`, create the GitHub release, and check that an older install updates to it. Use when asked to release, publish, ship or cut a version.