Reporting bugs

A good report has four things:

1. What you ran (the command or the file), and the Tessera version or commit.
2. What you expected.
3. What happened, with the complete error: the ERROR block with its code and position, not a paraphrase.
4. The smallest .tess file or project that shows it.

For a wrong or confusing error message, say what the message should have said. Error messages are a feature, so a message that sent you the wrong way is a bug.

For an accessibility problem, say which assistive technology and browser you used and what you heard or saw. Automated tools find only part of the problem, so a report from a person is worth more than a scan.

There is no public issue tracker yet, because there is no public hosting. Until there is, report bugs to the project's author directly.