Release Notes
0.1.0
The first full release: the schema, the watcher, the dispatcher, the runtime and the board.
Published as torta-app and torta-ai 0.1.0.
What shipped
The schema. Every ticket rule moved into the workflow section of
torta.json, read by the linters. The roster became presets: solo and
full-team.
The engine. One cross-platform watch over every queue, a derived
events.jsonl transcript, and a deterministic dispatcher.
The runtime. Agent sessions behind one seam, with leases so two sessions never hold one home, per-ticket budgets, approvals, and a failure taxonomy.
The board. Kanban queues per agent, the statuses tab, the access map of what each agent may touch, and the needs-you lane.
Onboarding. An interactive five-question torta init that publishes your
first thing to build as a real ticket in a real queue.
The CLI. init, sync, doctor and verify: stamp the workflow,
generate the walls, render the briefs, probe readiness.
Packaging
torta-app carries the payload, and torta-ai is the installable alias that
depends on it. The engine, templates and profiles are staged into the tarball
at pack time and removed afterwards.
The check
The check generates every valid platform combination, runs each generated workspace’s own test suite, runs the Node suite, and installs the built tarball as a smoke test.