v0.23.2

---

version: 0.23.2
date: 2026-06-10
headline: "Patch — fix the stale FTUE version literals so CI can green and the v0.23.x content can finally publish."
themes: ["docs", "arbiter", "ci"]
highlights:

• "README front-door badge and verify-action pin examples now track the released version"
• "arbitrate honors a kindless --lane naming a known free cluster lane"
• "Carries the full v0.23.0 + v0.23.1 content to PyPI"

---

TL;DR — the third cut of the v0.23.x line, and the one that publishes. v0.23.0 was refused by the publish pipeline's ci-green witness gate (a workflow parse error), v0.23.1 fixed the parse but was refused again on stale doc version literals the drift guard caught. Both refusals were the gate working. Everything in the v0.23.0 and v0.23.1 notes ships under this version.

docs — the drift the guard was built for

• Three stale 0.22.0 literals fixed — the README front-door badge line and the verify-action README's pin examples (dos-version and the pre-commit rev:).
  • Why: the bump sweep is keyed old→new, so a literal added after a release (naming the then-current version) is invisible to every later sweep; tests/test_docs_version_drift.py caught all three — the verify-action leg on its first-ever CI run.
• Historical version references in FTUE prose drop the v prefix so the drift guard (anchored on v + dotted triple) pins live banners without flagging an anecdote that names an old release on purpose.

arbiter — kindless lane requests

• arbitrate honors a kindless --lane naming a known free cluster lane instead of refusing it (fix).
  • How: src/dos/arbiter.py.

ci / readme — riding along

• Release tooling tolerant-decodes gate subprocess output (fix).
• The README audience gradient closes — hand-off lines and the router back-link (docs/292 P4), plus issue #1's witnessed closure as a second self-demo anecdote.
• docs/293 planned — the design-doc plan dialect, dogfooding dos.plan_sources.