dsh-plugin-clarify v0.2.1

Changes

• Reorders model-visible Clarify DATA so stable Session context and history precede turn-varying decisions, drafts, feedback, and repair data.
• Preserves the public six-method Remote API, clarify.wire/1 data model, prompt token budget, history trimming, and repair behavior.
• Keeps the tested compatibility boundary at official @deepseek-ai/dsh@0.1.0-rc.8 with dsh-plugin-auxiliary-runtime@0.1.0 and SeekTTY 1.2.0.

Verification

• 217 tests passed
• build passed
• pack-check passed with 38 package entries
• T3 passed with 9 checks
• PR verify and contract-matrix CI passed

This release establishes a longer identical request prefix eligible for Provider prefix caching. No real-Provider A/B was performed, so it does not claim a measured cache-hit, latency, or cost improvement.

Assets

• dsh-plugin-clarify-0.2.1.tgz
• SHA256SUMS

Verify with: shasum -a 256 -c SHA256SUMS

Rollback: reinstall the v0.2.0 release tgz; Auxiliary 0.1.0 and SeekTTY 1.2.0 do not need to change.

Post-release validation

• Re-downloaded Clarify 0.2.1, Auxiliary Runtime 0.1.0, and SeekTTY 1.2.0 from their GitHub Releases and verified every SHA256SUMS file.
• Installed official stock @deepseek-ai/dsh@0.1.0-rc.8 in a new tool environment.
• Passed the SeekTTY packed stock add, boot, remove, and re-add contract.
• Passed the unchanged SeekTTY Clarify doctor acceptance with the downloaded Clarify tgz.
• Installed all three downloaded assets in a newly initialized stock tui Profile; dump-config exposed auxiliary-runtime, clarify, and seektty/tui-runner.
• Real PTY /doctor reported 0 errors, 0 warnings, and 99 plugins running both before and after removing and reinstalling Clarify 0.2.1.
• Real PTY /clarify reached running and routed through Auxiliary, then returned the expected MISSING_CREDENTIAL configuration failure because the isolated environment intentionally contained no API key.

No paid Provider call or cache/cost A/B was performed during post-release validation.