Upgrade a DSH 0.1.1 plugin to 0.1.5

Help the developer diagnose and modify one plugin at a time. Treat source migration, artifact verification, runtime activation, and business behavior as separate gates.

The migration knowledge covers the DSH 0.1.1 to 0.1.5 transition, derived and verified from one exact catalog version pair (declared below). Keep the skill's product scope at the release-line level (0.1.1 to 0.1.5), while keeping the catalog target exact. First record the plugin's actual DSH ranges and requested target. When a newer patch or prerelease appears, use the catalog for known changes only, inspect the additional interval, and report that it is not catalog-confirmed until the catalog and this skill are deliberately updated — a pass for the catalog pair never proves an unlisted version combination.

Current catalog version pair

This block is the single source of truth for the exact refs. Every command below and every reference file defers to it; the references avoid repeating the literals on purpose. When the catalog advances, update this block, the migrate analyze example, and the shipped catalog together.

• source ref: dsh-v0.1.1-rc.2
• target ref: dsh-v0.1.5-rc.2

Standard commands target this pair and need no --target-version. If the developer explicitly targets a newer 0.1.5 build before the catalog is updated, inspect that additional interval first (see source-investigation.md), then pass its exact version to every migration phase as --target-version <actual-0.1.5-version>. That changes dependency pins and runtime expectations only; the catalog's API claims still end at the declared pair.

Inputs

Determine: