refactor(daemon): drop the numeric-token heuristic instead of wrapping it

The previous commit replaced `formatGestureNoEffectWarning`'s
"drop numeric-looking positionals" regex with a per-action builder table —
but kept the regex as the table's fallback. That is two mechanisms where
there was one, and the heuristic this finding exists to remove is still
in the file.

Only `scroll`, `swipe` and `gesture <subtype> …` reach the warning by
default (`isPostGestureStabilizingAction`), and across all three exactly
one positional is not part of the gesture's identity: `scroll`'s optional
trailing amount. Echoing everything else verbatim is simpler than either
version and strictly more truthful than the original, which ate all four
coordinates of `swipe <x1> <y1> <x2> <y2>` and reported a contentless
bare "swipe".

  scroll down 0.6      -> "scroll down"
  scroll up            -> "scroll up"
  swipe 10 20 30 40    -> "swipe 10 20 30 40"   (was: "swipe")
  swipe                -> "swipe"
  gesture swipe left   -> "gesture swipe left"
  gesture fling down 100 200 -> "gesture fling down 100 200"

35 lines of table, dispatch and regex become 4 lines with one named
exception. `--postGestureStabilization` can still force an arbitrary
action through; echoing its positionals is the honest answer for one
warning string, and reconstructing each gesture subtype's layout would
fork a grammar that lives in GestureSemanticInput, downstream of the raw
positionals this function receives.

Author: thymikee

src/daemon/post-gesture-stabilization.ts

@@ -242,40 +242,26 @@ export async function capturePostGestureStabilizedResult<T>(params: {
 }
 
 /**
- * Which positionals actually name the gesture, keyed by the two actions that
- * reach this loop by default (`isPostGestureStabilizingAction`) and have a
- * single, fixed positional grammar declared elsewhere:
- *  - `scroll <direction> [amount]` — `src/commands/interaction/interactions.ts`'s
- *    `scroll` CLI reader (`readScrollDirection`/`optionalCliNumber`). Only the
- *    direction names the gesture; the amount is a magnitude, not identity.
- *  - `swipe <x1> <y1> <x2> <y2>` — `swipePayloadFromPositionals`
- *    (`@agent-device/contracts/interaction`). Swipe carries no semantic label
- *    at all: every positional IS the gesture, so dropping "numeric-looking"
- *    ones here previously produced a bare, contentless "swipe".
+ * Which positionals name the gesture in the warning. Echo them all, with one
+ * exception: `scroll <direction> [amount]` carries a trailing magnitude that
+ * is not part of the gesture's identity, so `scroll down 0.6` reads back as
+ * "scroll down".
  *
- * `gesture <pan|fling|swipe|pinch|rotate|transform> ...`
- * (`src/commands/interaction/index.ts`'s usage grammar) has no single shape —
- * each subtype's positional layout differs (e.g. `fling <direction> <x> <y>
- * [distance]` vs `pinch <scale> [x] [y]`), and the discriminator lives in
- * `GestureSemanticInput`, built downstream of the raw positionals this
- * function receives. Duplicating all five shapes here would fork that
- * grammar rather than read it, so `gesture` (and any action forced through
- * `--postGestureStabilization`) keeps the narrower "drop numeric tokens"
- * fallback below.
+ * Everything else echoes verbatim, which is both simpler and more truthful
+ * than the "drop numeric-looking tokens" heuristic this replaces. That rule
+ * ate every positional of `swipe <x1> <y1> <x2> <y2>` — the one action whose
+ * coordinates ARE its identity — and reported a contentless bare "swipe".
+ *
+ * Only `scroll`, `swipe` and `gesture <subtype> …` reach here by default
+ * (`isPostGestureStabilizingAction`); `--postGestureStabilization` can force
+ * an arbitrary action through, and echoing its positionals is the honest
+ * answer for one warning string. Reconstructing each `gesture` subtype's
+ * layout would fork a grammar that lives in `GestureSemanticInput`, built
+ * downstream of the raw positionals this function receives.
  */
-const GESTURE_DESCRIPTION_BUILDERS: Record<string, (positionals: string[]) => string[]> = {
-  scroll: (positionals) => (positionals[0] !== undefined ? [positionals[0]] : []),
-  swipe: (positionals) => positionals,
-};
-
 function describeGesturePositionals(action: string, positionals: string[]): string[] {
-  const builder = GESTURE_DESCRIPTION_BUILDERS[action];
-  if (builder) return builder(positionals);
-  return positionals.filter((value) => !isNumericPositional(value));
-}
-
-function isNumericPositional(value: string): boolean {
-  return /^[\d.-]+$/.test(value);
+  if (action !== 'scroll') return positionals;
+  return positionals.slice(0, 1);
 }
 
 /**