Blue 0.1.0-rc.5

The blue shell arrives: installing Blue is now one command.

Highlights

New package @dsh-blue/blue-cli (S37) — the blue launcher. npm i -g @dsh-blue/blue-cli@rc
ships the dsh host pinned to the tested harness line, installs Blue into its
blue profile on first run, and boots it; the direct path
(dsh plugin --profile blue add @dsh-blue/blue@rc) remains fully supported.
Upgrading = reinstalling the shell; /update keeps serving direct-install
users, and a profile that /update advanced past the shell is never
downgraded (direction guard).
Launcher hardening: a pnpm-less first run now fails with the exact install
suggestion (npm i -g pnpm, or corepack enable pnpm), and a workspace-root
install refusal (ERR_PNPM_ADDING_TO_ROOT) retries once with -w.
Docs catch-up (R6a): the website reference pages are current again —
/mcp and /permission documented (with the input-layer interception
distinction), Ctrl-G external editor and Alt+M model cycling in the key
reference, the editor page covers # skills, large-paste folding and the
external editor, the approval page covers the plan-review and permission
panels, and a "parked commands" section makes the deferral rulings public.
Records: D53 settles the follow-up cadence (upstream releases never force a
Blue release — pinned installs are immune by construction) and the lockstep
retirement conditions for the stable era; D37 gains the tools.restrict()
review addendum.

Release-day cooldown: pnpm 11's default minimumReleaseAge (24h) can
refuse the first-run calibration's exact-version install on the day of
publishing — one line of error, retry after the window or pin
minimumReleaseAge: 0. Self-corrects within 24h of this release.
latest dist-tags on npm may lag this release until re-pointed; install
specs carry @rc and are unaffected.

npm i -g @dsh-blue/blue-cli@rc
blue

Requires Node ^22.19 || >=24 and pnpm 11 (both install paths). Direct-dsh
users: dsh plugin --profile blue add @dsh-blue/blue@rc as before.