v0.3.0

Changes

Features

• ci(compat): run the patrol weekly and make its reds visible (#17) @zlZayn
• chore(compat): swap the declared host line and prove what got installed (#16) @zlZayn
• chore(compat): ask npm whether the declared host range still holds (#15) @zlZayn
• feat(doctor): make an unmounted install say so (#14) @zlZayn

Bug Fixes

• fix(test): judge the promised host families from the committed manifest (#19) @zlZayn

v0.2.2

Bug Fixes

• a Chinese interface still showed the card as "DSML Rescue": the zh dictionary carried the English
  title, so the language file looked translated while only its description was. It reads DSML 续跑
  now, and en is untouched.
• the release flow's npm probe asked for dsh-plugin-sample, a leftover from the template it was
  copied from. It could never find this package, so a re-run would attempt to publish again instead
  of recognising a version that is already on npm.

Documentation

• the recordings were finally read against the documents, and two claims had no evidence at all: a
  cancelled turn that also leaked the markup, and a marker line with no closing bracket. Neither
  exists in any recording, and the evidence note now says which half of the aborted-turn rule is
  observed and which half is reasoned.
• the continuation sentence is quoted exactly once, in docs/ARCHITECTURE.md, with
  src/messages.ts named as its source; a redline test fails the build when the two disagree, so the
  quotation cannot go stale the way an unre-checked one does.
• docs/ARCHITECTURE.md states the three edges of "actionable" that the word alone invites a reader
  to get wrong, gives the tail window its number, marks the ASCII-bar and tokenizer-artifact cases as
  robustness arguments rather than observations, splits "rescue budget" from "output ceiling", and
  adds the row for a human prompt clearing the streak.
• the architecture's verification section is now a pointer: the counts it used to restate live in
  docs/VERIFICATION.md alone, which also names the case no recording can supply.
• Known traps in AGENTS.md are one line plus a link instead of a second copy of the reasoning, and
  the two READMEs are described for what they are — the user-facing summary, never the first place a
  rule is written down.
• both READMEs now say the leak and the emptiness are two halves of one criterion, so "an empty turn"
  alone does not read as something this plugin answers.

Maintenance

• the recording replay's aborted-turn assertion could not fail — the harness never offers
  turn-stopping for a turn that did not close normally, so the assertion held no matter what the
  detector did. It asserts that property now, and refuses to pass silently when the fixture holds no
  aborted turn to exclude.

v0.2.1

Changes

Features

• fix(locale): state the behaviour in the plugin card, 0.2.1 (#10) @zlZayn

v0.2.0

Bug Fixes

• a turn cut off at its output ceiling is no longer treated as a stall — the seam carries no stop
  reason, so the exclusion reads the closing message's output count against the ceiling the request
  was sent under

Features

• the first release published without a token: npm publishing now goes through OIDC (Trusted
  Publisher), so no long-lived credential exists in this repository

Documentation

• the two READMEs are rewritten for their own language rather than translated from each other, and
  show the real leaked markup so a reader recognises the failure they just hit
• the vocabulary is settled across every document: reasoning, DSML markup, turn, subagent
• docs/VERIFICATION.md states what each check establishes and what it leaves open, plus a
  repeatable end-to-end run against a local mock provider

Refactoring

• the token accounting moved into the machine state, so the truncation comparison lives in the pure
  layer the fixtures can reach