Release versioning + managed updates

The problem

Main moves fast — merging features continuously means users on main get changes immediately, including potentially breaking ones. No way to pin to a known-good state or roll back cleanly.

What we want

Tagged releases — semantic versioning (or simple date-based tags) so users can pin to a stable version.

woltspace update CLI command — checks for new releases, shows changelog, pulls the update.

Dog-assisted updates — ask dog "any updates?" → dog checks tags → if new version available, spawns a beaver to walk the user through it (warns about breaking changes, runs migrations if needed).

Rough shape

1. Tagging: after merging a batch of PRs, tag a release (v0.1.0, v0.2.0, etc.). Users clone at latest tag by default.
2. woltspace update: pulls latest tag (not main), shows diff summary. woltspace update --edge for main.
3. Dog tool: check_updates tool — compares current tag vs latest. Reports what changed.
4. Beaver migration sessions: for breaking changes, spawn a beaver that reads the changelog and applies necessary migrations (config changes, new env vars, etc.).

Not right now

This is a roadmap item. Current priority: ship wolf scheduler, test it live. Versioning comes after the pace of breaking changes justifies it.

🤖 Generated with Claude Code

The issue names no files or tests and explicitly marks this as a roadmap item. Start by reviewing the existing CLI entry point and the proposed woltspace update command, then define the release and update scope; done would require agreed behavior for tagged releases, stable updates, --edge, check_updates, and migration sessions.