ts-quality v0.2.1 — compact doctor diagnostics and public CLI contract hardening

This release is prepared through the repo's GitHub Release authority path. Publishing the GitHub Release for tag v0.2.1 triggers .github/workflows/publish.yml in the npm-publish environment, which validates the tag/version contract, re-runs deterministic package proof, publishes the staged package to npm through Trusted Publishing/OIDC, verifies public installability, and attaches the proven tarball to the GitHub Release.

Breaking Changes

• None.

Added

• Added ts-quality doctor --machine as a compact line protocol for harnessed LLMs and agents, keeping first-contact adoption diagnostics token-light while preserving existing --json surfaces for CI-style JSON projections.

Changed

• None.

Fixed

• Fixed the public 0.2.0 drift where docs and main described doctor --machine before the published npm tarball exposed it; 0.2.1 ships the compact doctor protocol publicly.
• Fixed release verification so future public package checks require exact top-level help, doctor --help exposure of --machine, and the compact doctor --machine protocol through one shared public CLI contract verifier, preventing docs or adoption plans from claiming a CLI path that the published tarball does not expose.
• Fixed doctor --machine recommendation lines to include repeated compact command_arg= fields when the diagnostic model has a command, reducing fragile prose parsing and comma-splitting ambiguity for harnessed agents.
• Fixed doctor script ranking so scripts named for tests or coverage outrank unrelated scripts whose command bodies merely mention test files, and generic Node test scripts no longer receive a Jest-specific --runInBand suffix.

Agent migration notes

• No breaking-change migration is required for agents beyond ordinary release-note review.

Verification before release

npm run verify --silent
RELEASE_TAG=v0.2.1 GITHUB_REF_TYPE=tag npm run release:intent:check --silent

Install

npx -p ts-quality@0.2.1 ts-quality --help