Fix key drop after code-expansion in tapKeySeq (consumeWhite context pop)

consumeWhite()'s whitespace-skipping loop evaluated `*ctx->at <= 32` before
calling isEnd(). isEnd() may pop an exhausted parser context (such as the
sub-context pushed by tapKeySeq's expandCodes for hexCodeOf/decCodeOf/
altCodeOf/uCodeOf), which moves ctx->at to the parent's next token. Because
the dereference happened first and the loop body then ran ctx->at++, the first
character of that parent token was stepped over and dropped.

Concretely, `tapKeySeq x y hexCodeOf(!) x y` typed `x y 2 1 y` — the `x`
following the expansion was lost. Reordering the condition so isEnd() (and its
context pop) runs before the dereference keeps ctx->at on the restored token.

Verified on uhk-80-right: the TapKeySeq regression test now passes and the
full on-device test suite is green (52/52).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Author: kareltucek

right/src/str_utils.c

@@ -136,11 +136,15 @@ bool IsEnd(parser_context_t* ctx) {
 static void consumeWhite(parser_context_t* ctx)
 {
     while (!isEnd(ctx)) {
-        while (*ctx->at <= 32 && !isEnd(ctx)) {
+        // isEnd() may pop an exhausted parser context (e.g. an expandCodes/
+        // template expansion), moving ctx->at to the parent's next token. It
+        // must be checked *before* dereferencing ctx->at, otherwise a ctx->at++
+        // here would step over that token's first character and drop it.
+        while (!isEnd(ctx) && *ctx->at <= 32) {
             ctx->at++;
         }
         if (ctx->at[0] == '/' && ctx->at[1] == '/' && consumeCommentsAsWhite) {
-            while (*ctx->at != '\n' && !isEnd(ctx)) {
+            while (!isEnd(ctx) && *ctx->at != '\n') {
                 ctx->at++;
             }
         }
@@ -322,7 +326,7 @@ void ConsumeAnyIdentifier(parser_context_t* ctx)
 
 void ConsumeUntilDot(parser_context_t* ctx)
 {
-    while(*ctx->at > 32 && *ctx->at != '.' && !isEnd(ctx))    {
+    while(!isEnd(ctx) && *ctx->at > 32 && *ctx->at != '.') {
         ctx->at++;
     }
     if (*ctx->at != '.') {

right/src/test_suite/tests/test_tapkeyseq.c

@@ -1,16 +1,9 @@
 #include "tests.h"
 
-// Regression test for a tapKeySeq bug: when a code-expansion command such as
-// hexCodeOf(...) sits in the middle of the sequence, the key that immediately
-// follows the expansion used to be dropped.
+// Regression test for a template expansion bug.
 //
-// `tapKeySeq x y hexCodeOf(!) x y` must type
-//     x y 2 1 x y
-// ('!' == U+0021, so hexCodeOf(!) expands to the key sequence `2 1`). The bug
-// dropped the final key of the whole sequence whenever a code-expansion command
-// preceded it, so the tail came out as `... x` instead of `... x y`. Distinct
-// keys (x/y) around the expansion make a dropped key surface as a wrong-char
-// mismatch rather than only a timeout.
+// `tapKeySeq x y hexCodeOf(!) x y` would produce "xy21y" due to wrong ConsumeWhite/isEnd expansion.
+
 static const test_action_t test_tapkeyseq_hexcode[] = {
     TEST_SET_MACRO("u",
         "tapKeySeq x y hexCodeOf(!) x y\n"