Unreleased

On main above the 0.4.1 tag, not yet on npm.

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 non-coder guide

A setup path for somebody who has never opened a terminal: install Node, paste two lines, then work in the browser. It is the source of the non-coder path.