accelerate: put the offending value back in the out-of-range warning

Copilot review, #3580. env_int64_min's warning named the constraint but not
the value that broke it, which is the one thing you need to fix a typo'd knob.

This was a regression from this PR. The original printed the raw string:

  dasLLAMA: {name} `{raw}` is not an integer >= {min_v} — keeping {def_v}

Delegating the parse to env_int64 dropped `{raw}` — and quietly dropped a
second case with it: env_int64 falls back on unparseable input, so a typo'd
DASLLAMA_ACCEL_MIN_NTOK stopped warning at all and silently did nothing. That
is the exact failure mode this registry exists to prevent.

Both restored with one branch: read the raw value first, then parse with a
sentinel default one below the floor, so unparseable and out-of-range fall
into the same check. An unset knob still returns the default in silence, which
is the registry's documented contract.

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

Author: borisbat

modules/dasLLAMA/dasllama/dasllama_math_accelerate.das

@@ -223,11 +223,14 @@ def dasllama_accelerate_disable() {
     clear_float_batch_override()
 }
 
-// env_int64 with a floor: out-of-range is worth a word, unlike a plain unset knob
+// env_int64 with a floor. A SET but bad value is worth a word either way — unparseable and
+// out-of-range both land below the floor via the sentinel default, so one branch covers both.
 def private env_int64_min(name : string; def_v : int64; min_v : int64) : int64 {
-    let v = env_int64(name, def_v)
+    let raw = env_str(name, "")
+    return def_v if (empty(raw))
+    let v = env_int64(name, min_v - 1l)
     if (v < min_v) {
-        to_log(LOG_WARNING, "dasLLAMA: {name} must be an integer >= {min_v} — keeping {def_v}\n")
+        to_log(LOG_WARNING, "dasLLAMA: {name} `{raw}` is not an integer >= {min_v} — keeping {def_v}\n")
         return def_v
     }
     return v