Blue 0.1.0-rc.5

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.

Known issues

• 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.

Install

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.

Blue 0.1.0-rc.4

Blue 0.1.0-rc.4

A fast follow on rc.3: the update path itself got a fix from the
real-machine matrix.

Fixes

• Update target-exists false block — the update preflight could refuse a
  perfectly valid target release (a bare-key lookup misread the registry's
  dist-tag shape); the check now reads the real shape, verified across the
  real-machine matrix (installed rc.2 → rc.4 upgrades, downgrade rollback,
  and interrupted-update recovery).

Known issues

• Preview semantics as before: rc dist-tag, pinned harness line —
  see docs/blue-roadmap.md
  for the parked list, and the FAQ for
  the pnpm minimumReleaseAge note.

Blue 0.1.0-rc.3

Blue 0.1.0-rc.3

The third preview: @dsh-blue/blue-api first publish — the public-contract
package joins the set, making this the first six-package lockstep release.

Highlights

• In-app safe update (S38, D52) — a boot-time update check plus the
  /update command: Blue verifies the target release exists as a complete
  set before switching, swaps the profile's plugin install, and keeps the
  previous version until the new one boots — verdicts render in-panel, and a
  failed update leaves the running install untouched.
• @dsh-blue/blue-api — the renderer-independent public contracts
  (view/lifecycle/result shapes and manifest validation) published for
  downstream plugin authors.

Fixes

• Dogfood findings from the update run: panel-rendered verdicts, the
  release set derived rather than hardcoded, and a hardened npm view
  shape check.

Known issues

• Preview semantics as before: rc dist-tag, pinned harness line —
  see docs/blue-roadmap.md
  for the parked list, and the FAQ for
  the pnpm minimumReleaseAge note.

Blue 0.1.0-rc.2

Blue 0.1.0-rc.2

The first public preview release on npm: the complete Blue TUI — streaming
transcript, the editor with fuzzy slash commands, overlays and dock panes,
theming, and the model/provider/status command family — published as five
lockstep packages under the @dsh-blue scope, built against the
0.1.1-rc.2 harness line.

Highlights

• Streaming transcript — markdown rendered while it streams; tool calls
  as cards with dedicated read/diff/terminal views; 30-step fold retention.
• Editor — rounded-box input with fuzzy slash-command autocomplete and
  argument ghost hints, ! bash mode, @ file completion, # skill
  completion, Ctrl-V clipboard image paste, and large-paste folding.
• Commands — /model /effort /provider /permission /status
/context /version /theme /export /copy /btw /sessions
  and friends; a subagent-group dock pane; session-level approval choices.
• Theming — /theme hot-switching across dark / light / auto
  (OSC 11 background detection) / custom (JSON palette).
• Extensible by construction — every render component, interaction
  provider, command, and status entry is a Cordis plugin; registries drive
  the completion menu and /help.

Fixes

• rc.1 tarballs self-destructed on install (hash chunks outside exports,
  incomplete files manifests); rc.2 ships complete files=["lib/**/*"]
  manifests, a check:lib export guard, and a local pack-install precheck
  in the release pipeline (D51).

Known issues

• Preview semantics: packages carry the rc dist-tag (latest stays
  reserved for the stable line), and the harness line is pinned —
  breaking upgrades are possible between previews.
• Tool output is not streamed (presented when the tool completes); the
  approval panel has no inline diff preview yet; no desktop notifications.
  The full parked list lives in
  docs/blue-roadmap.md.
• pnpm 11 users: minimumReleaseAge (default 24h) can silently resolve the
  @rc dist-tag to the previous version during the first day after a
  publish — see the FAQ workaround.