0.5.0

Published as torta-app and torta-ai 0.5.0.

The first ticket is a conversation, not a form

The wizard’s three-field ticket page is gone. It asked for the one answer nobody has ready, in a shape that could not help you find it.

The workspace is now created with empty queues and no ticket at all. The board opens with the terminal panel already on the agent that takes requests, and that agent speaks first: it asks what you want built, interviews you for what it should do, why it matters and the one number that settles it, then authors the ticket through the same ticket.py every other ticket goes through. There is still exactly one way a ticket comes into being.

The empty board says what to do about being empty, and names the agent to go and talk to.

The house rules became linters

Every threshold lives in torta.json:

• No em dash in prose. Markdown files are read whole. Source files are tokenised, so only comments are read and a dash inside a string literal stays code.
• A comment block fits its shape. At most 4 rows and at most 80 columns. A JSDoc block is exempt from the row count.
• A commit message is type(scope): summary, between 80 and 90 columns, with - bullets and an ordered set of trailer sections, and no attribution trailer.

The linters read Python, JavaScript, JSON and shell, and an extensionless file by its shebang. The commit gate runs from a hook; the prose gate is a step in the project’s check.

See the style schema for every key.

The imperative mood is enforced

Every commit subject and body bullet must be an instruction: update the wizard, not updated the wizard or updating the wizard. Past tense, gerunds and third person are rejected by name, and an irregular verb table catches wrote, built, sent and the rest.

Every em dash is gone

One pass removed the banned character from prose, comments and generated workspace text. No behaviour changed.

The docs site, and one line for beginners

These pages went up at docs.torta.app, with the non-coder path leading the home page and a copy button on every command block.

Setting up without knowing a terminal is now one pasted line, which installs Node if it has to, installs Claude Code and asks you to sign in, works around the folder permissions that cause most install failures, and opens your browser. It says what it is doing before each step, and a second run finds everything already there. It is the source of the non-coder path.