v1.0.1

Fix the declared peer range.

>=0.1.7-rc.2 matched 0.1.7-rc.2 but not 0.2.0-rc.2: node-semver only lets a prerelease version satisfy a range when some comparator shares its exact major.minor.patch tuple and itself carries a prerelease tag. Installing against a current harness therefore raised ERESOLVE. The range now carries an explicit prerelease branch per tuple.

@deepseek-ai/schemastery is declared as a peer as well, since the plugin imports it.

v1.0.0

First release.

Makes agent preset changes take effect on running sessions without restarting dsh:

• disable -> enable the target preset row, the only Loader path guaranteed to rerun Service.init and therefore register() again;
• recompose every live Agent onto the resulting revision, preserving sessionId and context.

Why force is required

A config-only change does not re-register the preset, so no new revision appears and sessions get stuck on the old one. docs/why-force.md records the mechanism with source references and measured evidence.

Safety

A broken definition is caught into record.broken; recompose refuses it and the old revision survives while live sessions hold it. A bad edit cannot reach a running session, and rollback is free.

Verified on

DSH 0.2.0-rc.2, with the agent-preset-registry test harness and against a live dsh web.