@whybebabo/dsh-code-nav v0.1.2

@whybebabo/dsh-code-nav v0.1.2

Documentation-only release. The client bundle is byte-identical to v0.1.1
(lib/client.js sha256 F31583CA…63D0E) — the version string is not embedded in
it. Selection → add to conversation behaves exactly as in v0.1.1.

Fixed

• Install docs pointed at the wrong profile. Both READMEs and
  cordis.patch.yml said dsh plugin --profile desktop add …, which cannot
  work: the desktop profile is owned exclusively by the Electron app and the CLI
  refuses it — error: profile "desktop" is managed exclusively by the Electron application. They now document dsh plugin --profile web add …, and
  cordis.patch.yml records the desktop caveat (install from the in-app plugin
  page instead).

npm cannot amend the files of an already-published version, so this fix from
commit e04d2e9 only reaches users through a new release.

Upgrading from an earlier version

Name an exact version instead of relying only on the ^ range:

@whybebabo/dsh-code-nav@0.1.2

pnpm 11 guards against freshly published packages with
minimumReleaseAge, whose built-in default is 1440 minutes (24 hours). Because
that value is a built-in default and not an explicit setting,
minimumReleaseAgeStrict defaults to false: instead of failing, pnpm falls
back to a version old enough to pass the age gate. So while ^0.1.1 is recorded
in the profile, a reinstall resolves 0.1.1 (mature) over 0.1.2 (too new) and the
command reports success while the installed version never changes.

With an exact version there is a single candidate in range; pnpm installs it and
records it in minimumReleaseAgeExclude. Reinstalling 0.1.2 this way was
verified to land on 0.1.2 (lib/client.js sha256 F31583CA…63D0E).

(Note the contrast: setting minimumReleaseAge explicitly turns strict mode on
by default, and then an over-age request fails outright with
ERR_PNPM_NO_MATURE_MATCHING_VERSION rather than falling back.)

Alternatively, wait 24 hours after a release before upgrading with a ^ range.

Install

dsh plugin --profile web add @whybebabo/dsh-code-nav

See the README for the fork origin and the full difference table against
upstream. The upstream change is open as
AnakinCao/dsh-code-nav#1;
if it merges and upstream publishes, prefer the upstream package.