Vorno 0.18.1
Published task definitions become board cards
August 27, 2026
Features
- None. This is a targeted fix release.
Improvements
- None.
Bug Fixes
A published task definition now appears on the board — A board card is an orchestrator session;
tasks/<slug>/task.yamlis only a definition. Publishing wrote the yaml but never minted the orchestrator, so a definition written by any producer outside the app — a script, a sync, an external tool — existed on disk and rendered nowhere. Workspace load now reconciles the tasks directory and adopts any published-but-unbound definition through the same path a fresh create uses, so the card carries its task slug, the reserved Task label, and the spec's sources, project, and working directory. Reconciliation is idempotent, so a slug that already has a card is left alone across restarts. (aeb62ff8,50e7f52c)One malformed definition can no longer block workspace load — Reconciliation is fail-soft: an unparseable or invalid
task.yamlis skipped with a logged warning while its valid siblings still adopt and the workspace finishes loading. A definition whose id does not match its own directory is refused the same way, rather than minting a fresh duplicate card on every restart. (50e7f52c)Task cards no longer collide across workspaces — A task slug is only unique within one workspace, so reconciliation now scopes its bound-slug check to the workspace being loaded. Previously a card in one workspace could suppress a same-named task in another indefinitely. (
50e7f52c)
Breaking Changes
- None. All changes are backward-compatible.