The scanner did not list await as a keyword that expects an
expression next, so it read the / in an await-prefixed regex
literal as division. A closing brace inside that regex then closed
template interpolation tracking early and hid a real vi.waitFor(
call from the guard. Add await to the keyword set and add a
regression test for this exact form.
Co-authored-by: Paperclip <noreply@paperclip.ing>
