v1.0.2 — fix peer range excluding harness prereleases

Fixes a peer-dependency range that silently excluded published DSH harness
prereleases, which made npm install fail with ERESOLVE for users on those
builds.

The problem

The peer range was:

>=0.2.0-rc.1 <0.3.0

node-semver only lets a prerelease version satisfy a range if some comparator
in that range sits on the version's exact major.minor.patch tuple and itself
carries a prerelease tag. This range has only >=0.2.0-rc.1, which sits on the
0.2.0 tuple. Every other prerelease was therefore silently dropped — including
two versions that are actually published today:

• 0.1.7-rc.2
• 0.2.1-alpha.1 (the current alpha dist-tag)

Those users hit ERESOLVE and had to work around it by hand.

The fix

All four @deepseek-ai/* peer entries now enumerate every published harness
build in the supported line:

0.1.5-alpha.1 || 0.1.5-alpha.2 || 0.1.5-rc.1 || 0.1.5-rc.2 || 0.1.5-rc.3 ||
0.1.6-alpha.1 || 0.1.6-alpha.2 || 0.1.7-alpha.1 || 0.1.7-alpha.2 ||
0.1.7-rc.1 || 0.1.7-rc.2 || 0.2.0-rc.1 || 0.2.0-rc.2 || 0.2.1-alpha.1

This is the same convention @panando/dsh-pua uses. A regression test asserts
the range keeps covering every published build, so this cannot silently return.

Install

dsh plugin --profile web add @panando/dsh-prompt-optimizer

See the v1.0.1 release notes for the full feature list and the v1.0.0
web-boot crash note.