The ViewModel said seven and the window drew one

[dmitrat]

Finding 20 — the last item of the fix plan. Studio 1014 green, 1007 before.

A parse error was marked with a squiggle one character wide, under the first letter of the token,
while a missing table is underlined across its whole name. That is why the screenshot pass reported
that a parse error is not marked at all: beside ten letters, one reads as nothing. The mechanism
was never broken; the length was.

The token comes out of the message — every shape this parser produces names it in single quotes
(mismatched input 'Country', extraneous input 'x', no viable alternative at input 'xy',
missing ';' at 'SELECT'). Reading it from there keeps an engine package out of a question about
drawing; the alternative was a new field on the parser's own error type. A message with no quoted
token keeps the single character it always had — the control asserts that.

The screen taught the second half

With the executed path fixed, driving Studio showed the mark still one letter wide. Whenever the
text does not parse, the live syntax check has an answer and UpdateUnderline prefers it — and
that branch hard-coded a length of one. The first test passed because nothing had run the live check.

Both branches read the token now, and Country is underlined across the word on screen.

🤖 Generated with Claude Code