woltspace 0.5.1

The woltspace wheel, 0.5.1. Published to PyPI from ae20dd1.

The tui and the wheel ship on their own now (#413)

Until 0.5.0 the wheel pinned one exact @woltspace/tui version and refused any other, for both woltspace tui and the pty bridge behind the web tui. Every tui change forced a wheel release.

Now the tui declares the minimum woltspace version it needs and checks it itself at startup. The wheel checks only that a binary on PATH really is the @woltspace/tui bin it claims to be. /health reports the lodge version so the tui can do that check. The container image installs @woltspace/tui@latest.

Tags split from here: v* for the wheel, tui-v* for the tui.

Also in this wheel

• The update skill is written for the installed package (#410): installed versus published versions, GitHub release notes, breaking-change flag, uv tool install and npm i -g on consent, migrations shipped inside the wheel. No more git pull of a checkout that does not exist natively.
• Install docs match the native-first install.sh (#409), and the stale committed copy of the update skill at the repo root is gone.

Install or upgrade

uv tool install 'woltspace[connectors]==0.5.1'
woltspace stop && woltspace start

Container users: woltspace rebuild --latest then woltspace restart. Any published tui works with this wheel; the tui tells you if the lodge is too old for it.