- README documents install-from-disk and what actually works today
- jaitest prints the recovery steps when a poisoned build cache makes
:test report NO-SOURCE, and AGENTS.md records the failure mode
- JaiSyntaxHighlighter maps every one of the lexer's token types; asserted over
the whole corpus (105 distinct token types seen, all mapped)
- JaiHighlightingLexer refines IDENT into built-in types and loop variables for
colouring only, so the parser never sees them as reserved
- colour settings page with a demo file that is itself asserted to lex cleanly
Lexes all 714 .jai files (17.1M chars, 3.0M tokens) and asserts round-trip
tiling, strict offset progress, and zero BAD_CHARACTER. Green on first run.
jaitest: use cleanTest and retry once when a concurrent Gradle run clobbers
build/test-results (java.io.EOFException with no XML).
JaiLexer mirrors compose_new_token in the compiler's own lexer. Nested block
comments and here-strings are each consumed inside a single token, so the lexer
state is always 0 and it can restart at any token boundary.
13 plain-JUnit tests, one per gotcha in the language reference §14.
