v0.13.1

fix: spread the schema default so checkJs accepts the frozen constant

tsc --noEmit (the CI gate) rejects the frozen readonly array in
.default(PROTECTED_TOOLS) — schemastery's array default wants a mutable
string[]. Spread into a fresh mutable copy at the schema boundary; the
frozen constant itself stays authoritative for the resolver (and its
identity test).

v0.13.0

chore: raise dsh host floor to 0.2.0-rc.2

devDeps exact pins, overrides and pnpm.overrides blocks moved
0.1.7-rc.1 -> 0.2.0-rc.2; peer floors >=0.2.0-rc.2; README
requirement lines follow. No code changes: BasicCompactionEngine /
isCompactCheckpointSource / recover() unchanged in 0.2.0.
Regression: 109/109 tests + tsc --noEmit green against the
0.2.0-rc.2 closure.

v0.12.0

fix: devDeps cordis 抬 4.0.4——release.yml 的 npm install 严格 peer 检查下，devCordis 4.0.2 与 dsh-agent 0.1.7-rc.1 的 peer ~4.0.4 冲突 ERESOLVE（CI 用 pnpm 宽松故未暴露，v0.12.0 首跑翻红根因）；lock 同步重解

v0.11.0

docs: cut 0.11.0 — bare /dcp compacts; README/SKILL upgrade notes

v0.10.0

chore(release): 0.10.0

v0.9.1

feat(skill): rename the bundled skill to dsh-dcp-config (ecosystem -config convention)

Config/usage-guide skills now uniformly end with -config. Bundled
skills register in-process with zero on-disk footprint, so the rename
migrates itself on upgrade: update the package, restart dsh, and the
new name is live — nothing to clean up by hand. README skill paths and
the anti-drift test assertions move with it; plugin ids, settings
namespaces, and other constants sharing the old spelling are
deliberately untouched.

v0.9.0

feat(skill): bundle a dsh-dcp usage/config skill (ask_user_question tuning wizard)

Ship skills/dsh-dcp/SKILL.md through ctx.skills.registerProvider (same
mechanism as dsh-llm-proxy/dsh-vault), soft-guarded in the engine
constructor and declared via static inject 'skills' — verified live
against the real dsh 0.1.2-rc.1 host (a probe plugin observed the
bundled skill through ctx.skills.list()/get() in a booted profile).
The guide documents the two config paths (/dcp set vs the
cordis.patch.yml mount config: section managed by dsh-dcp-setup), the
full key table, an ask_user_question tuning wizard that maps user
expectations to keys, the four trigger kinds, and per-session subagent
counting; the anti-drift test asserts the hardcoded routing
description verbatim against the packaged frontmatter.

README (zh/en) gains a bundled-skill section; CHANGELOG adds 0.9.0.

v0.8.0

feat(setup): --remove reverse op + guarded disable row + lifecycle smoke + uninstall docs

v0.7.0

chore(deps): ride the dsh rc/stable line — 0.1.2-rc.1 closure, retire alpha

• CI installs the dsh CLI from the newest of latest/next (never alpha,
  never hand-pinned); job renamed to "dsh rc/stable closure"
• peer floors >=0.1.2-alpha.4 -> >=0.1.2-rc.1; dev pins and overrides
  -> 0.1.2-rc.1 (release 0.7.0 will be stamped from the tag)
• READMEs announce rc/stable-only support

v0.6.0

test(ci): real-host boot smoke + CI on the rolling dsh alpha line

• scripts/smoke-boot.mjs (adapted from dsh-cron): npm pack → scratch
  profile with the tarball as a file: dep → pnpm install → dump-config
  mount proof → timed real boot. Unlike cron's bundle-patch mount this
  exercises the cordis.patch.yml layer users get from scripts/setup.mjs:
  compaction-basic disabled, dsh-dcp inserted by absolute entry path.
  DSH_BIN overrides the CLI so a scratch closure can be smoked without
  installing it globally.
• CI: the test job installs @deepseek-ai/dsh@alpha (rolling tag, never
  hand-pinned), links the closure, then runs pnpm check + pnpm test on
  node 22/24 with a frozen pnpm lock; a separate smoke job boots the
  packed plugin under the real alpha host.