v0.23.3

---

version: 0.23.3
date: 2026-06-10
headline: "Patch — the hot-tree desync behind v0.23.2's red CI, fixed at the source; the demo-story lockstep gate holds."
themes: ["docs", "skills", "ci"]
highlights:

• "Bundled plugin skills resynced with their src/dos/skills sources"
• "The canonical-example lockstep gate is green on its own registry"
• "Carries the full v0.23.0 through v0.23.2 content to PyPI"

---

TL;DR — the fourth cut of the v0.23.x line. v0.23.2's CI went red on two hot-tree desyncs: a concurrently-edited skill source committed ahead of its regenerated plugin copy, and the new canonical-example lockstep gate catching its own registry's docstring. Both were fixed at the source; this tag re-cuts on the green tree. Everything in the v0.23.0, v0.23.1, and v0.23.2 notes ships under this version.

skills — the generated pair, resynced

• claude-plugin/skills/ regenerated in lockstep with src/dos/skills/ — the kindless-arbitrate captures refreshed to the honest verdict in both copies.
  • Why: the bundled copy is byte-pinned to its source by tests/test_plugin_manifest.py; a source edit committed between a regeneration and the release commit shipped the pair out of sync.

docs — the lockstep gate holds

• The demo-story registry's own docstring now spells the canonical ship stamp canonically (fix) — the new tests/test_canonical_example_lockstep.py gate caught its own registry on its first CI run.
• docs/293 Phase 2 placement revised after the kernel's own SELF_MODIFY refusal.

ci — three refusals, all correct

• The v0.23.x line took three publish refusals to land: a workflow parse error (v0.23.0), stale FTUE version literals (v0.23.1), and the hot-tree desync above (v0.23.2). Each was the ci-green witness gate declining an unwitnessed "ready" — the pipeline working as designed.