verikun 0.15.0 → 0.16.0

package/README.md

@@ -390,15 +390,51 @@ class:Button    simplified type ("Button") or full class ("android.widget.Button
 ```
 
 Modifiers: `--contains` makes text/desc matches substring-based; `--index N`
-selects the Nth match (0-based) when a selector intentionally matches several;
-`--enabled` matches only a control that is **actionable right now** — use it for a
-Submit/Check button the app disables until a form is valid, since such a button is
-present long before it is usable and tapping presence taps a dead control (with
-auto-wait this reads as "wait until it is pressable").
+selects the Nth match (0-based) when a selector intentionally matches several.
 If a selector for an action matches more than one element and no `--index` is
 given, the command fails with exit code 2 and lists the candidates — it never
 taps a guess.
 
+### State modifiers
+
+A selector can also require an element's a11y **state**, in both polarities:
+
+| Modifier | Matches | Negative form |
+|---|---|---|
+| `--enabled` | actionable right now | `--not-enabled` |
+| `--selected` | the current option of a segmented control / tab bar / mode picker | `--not-selected` |
+| `--checked` | a ticked checkbox / switch / radio | `--not-checked` |
+| `--focused` | the element holding input focus | `--not-focused` |
+
+Unset means *don't care*; these never narrow a selector you didn't ask them to.
+
+Reach for `--enabled` on a Submit/Check button the app disables until a form is
+valid: such a button is present long before it is usable, so tapping presence taps
+a dead control (with auto-wait this reads as "wait until it is pressable").
+
+The **negative** forms are what make a toggle drivable. A segmented control whose
+options share one handler *flips* on any tap, so "tap the option I want" lands on
+the other one whenever it was already chosen — exit 0, nothing to notice, and the
+run exercises the wrong mode. Guard it instead:
+
+```sh
+vk find "@mode_video --not-selected" --no-wait && vk tap @mode_video
+```
+
+A modifier can be written as a flag **or appended to the selector string**, as
+above. The string form exists because a `vk ai` control node (`if-present`,
+`when`, `repeat`, `while-present`, `read`) holds a bare selector with nowhere to
+put a flag — and a guard is exactly where the toggle case needs one:
+
+```
+if-present "id:mode_video --not-selected" { tap id:mode_video }
+```
+
+**`--selected` and `--focused` are Android-only.** `idb` reports no such
+attribute for iOS — not merely unset, the key does not exist in its output — so
+using them with `--ios` exits **3** rather than silently matching nothing.
+`--enabled` and `--checked` work on both.
+
 ### Auto scroll-into-view
 
 An element can be in the hierarchy without being reachable at the point a tap

package/dist/agent/engine.js

@@ -4,6 +4,7 @@ exports.DEFAULT_GUARD_SETTLE_MS = exports.DEFAULT_RUN_TIMEOUT_MS = void 0;
 exports.runPlan = runPlan;
 const node_crypto_1 = require("node:crypto");
 const selector_1 = require("../ui/selector");
+const state_support_1 = require("../ui/state-support");
 const errors_1 = require("../errors");
 const ir_1 = require("./ir");
 /** An outcome is environment-flavoured if it carries an exit-3 CliError, or simply
@@ -191,6 +192,11 @@ async function runPlan(plan, deps) {
             deps.log(`[ai] guard selector '${selector}' did not parse (${e.message}) — treating as not present`);
             return false;
         }
+        // Outside the catch on purpose. A guard pinning state this platform cannot report
+        // would match nothing forever, so "not present" is a lie that silently skips the
+        // body — the plan is unrunnable HERE and must say so, not quietly do nothing.
+        if (deps.platform)
+            (0, state_support_1.assertStateSupported)(sel, deps.platform);
         const deadline = Date.now() + Math.max(0, settleMs);
         // A non-zero window must buy at least one SECOND look, independent of the clock.
         // Measured on emulator-5554: one uiautomator dump costs ~2.4s, which already exceeds
@@ -368,6 +374,8 @@ async function runPlan(plan, deps) {
         catch (e) {
             return { status: 'fail', where, reason: `read selector '${selector}' did not parse: ${e.message}` };
         }
+        if (deps.platform)
+            (0, state_support_1.assertStateSupported)(sel, deps.platform);
         // Same patience as a conditional guard: the value may not have rendered yet.
         const deadline = Date.now() + Math.max(0, guardSettleMs);
         let looks = 0;

package/dist/agent/grammar.js

@@ -112,12 +112,29 @@ SELECTORS (the engine auto-heals case/whitespace/partial, so prefer stable ident
   class:Button      type or class
   "Sign in"         bare string == text:Sign in
 
+A selector may also pin ELEMENT STATE, in both polarities:
+  --enabled  / --not-enabled     actionable right now
+  --selected / --not-selected    current option of a segmented control / tab bar / mode picker
+  --checked  / --not-checked     checkbox / switch / radio state
+  --focused  / --not-focused     holds input focus
+On a command leaf write it as a flag. On a CONTROL NODE append it to the selector string —
+that is the only place one can go, and it is what makes a state-conditional guard possible:
+  { "type":"if-present", "selector":"id:mode_video --not-selected",
+    "body":[ { "type":"command","command":"tap","positionals":["id:mode_video"],"flags":[] } ] }
+
 RULES:
 - --enabled on a tap makes it match only a control that is ACTIONABLE right now, and (with
   auto-wait) wait until it becomes so. Use it for any button that the app disables until
   something else is done — a Check/Submit/Continue that only lights up once an answer is
   selected or a form is valid. Without it the step taps a dead control, does nothing, and
   the failure surfaces later as a confusing timeout on the NEXT step.
+- A picker or toggle whose options share ONE handler FLIPS on any tap, so an unconditional
+  "tap the option you want" lands on the option you did NOT want whenever it was already
+  chosen — and its starting state is usually content-driven, so you cannot know it now.
+  Guard it: if-present "id:<option> --not-selected" { tap id:<option> }. The guard makes an
+  already-correct state a no-op instead of a flip. Unguarded, the flow completes either way
+  and the test PASSES having exercised the opposite mode — a false green, worse than a fail.
+  Same shape for a checkbox that toggles: guard with --not-checked / --checked.
 - assert is for VERIFICATION only and is terminal — never use it as a step you expect to
   fail. Put genuinely-optional UI behind if-present.
 - tap/text SCROLL THEIR TARGET INTO VIEW automatically, so "scroll down to X and tap it"

package/dist/args.js

@@ -44,6 +44,19 @@ const BOOLEAN = new Set([
     'no-restart',
     'allow-install',
     'allow-unsafe-anonymous',
+    // Selector state modifiers (STATE_ATTRS in ui/selector.ts) and their negations.
+    // `enabled` was missing here until 0.15.0, and the omission was not cosmetic: a
+    // non-BOOLEAN flag swallows the next token, so `vk tap --enabled @submit` bound
+    // the SELECTOR as the flag's value and died with "Missing selector". Only the
+    // trailing form worked. Any new modifier must be listed here.
+    'enabled',
+    'selected',
+    'checked',
+    'focused',
+    'not-enabled',
+    'not-selected',
+    'not-checked',
+    'not-focused',
 ]);
 function parseArgs(argv) {
     const positionals = [];

package/dist/cli.js

@@ -35,6 +35,7 @@ var __importStar = (this && this.__importStar) || (function () {
 Object.defineProperty(exports, "__esModule", { value: true });
 exports.platformFromFlags = platformFromFlags;
 exports.deviceFromFlags = deviceFromFlags;
+exports.stateFromFlags = stateFromFlags;
 exports.parsePoint = parsePoint;
 exports.healNote = healNote;
 exports.parseDuration = parseDuration;
@@ -58,6 +59,7 @@ const errors_1 = require("./errors");
 const exec_1 = require("./exec");
 const drivers_1 = require("./drivers");
 const selector_1 = require("./ui/selector");
+const state_support_1 = require("./ui/state-support");
 const format_1 = require("./ui/format");
 const viewport_1 = require("./ui/viewport");
 const output_1 = require("./output");
@@ -93,15 +95,42 @@ function deviceFromFlags(flags, platform) {
         (platform === 'android' ? process.env.ANDROID_SERIAL : undefined) ||
         undefined);
 }
-function buildSelector(raw, flags) {
+/**
+ * Read the `--enabled` / `--not-enabled` / `--selected` / … pairs off the flags.
+ *
+ * An ABSENT flag must stay `undefined`, never `false`: these modifiers are tri-state
+ * ("must be" / "must not be" / "don't care"), so passing `flagBool()` straight through —
+ * which is what this replaced — would quietly turn every selector on every command into
+ * "must be disabled, unselected, unchecked and unfocused".
+ */
+function stateFromFlags(flags) {
+    const state = {};
+    for (const attr of selector_1.STATE_ATTRS) {
+        const yes = (0, args_1.flagBool)(flags, attr);
+        const no = (0, args_1.flagBool)(flags, `not-${attr}`);
+        if (yes && no)
+            throw new errors_1.CliError(`Cannot combine --${attr} with --not-${attr}.`, 2);
+        if (yes)
+            state[attr] = true;
+        else if (no)
+            state[attr] = false;
+    }
+    return state;
+}
+function buildSelector(ctx, raw) {
     if (!raw) {
         throw new errors_1.CliError('Missing selector. e.g. `@login_button`, `text:Login`, `desc:Submit`.', 2);
     }
-    return (0, selector_1.parseSelector)(raw, {
-        contains: (0, args_1.flagBool)(flags, 'contains'),
-        index: (0, args_1.flagNum)(flags, 'index'),
-        enabled: (0, args_1.flagBool)(flags, 'enabled'),
+    const sel = (0, selector_1.parseSelector)(raw, {
+        contains: (0, args_1.flagBool)(ctx.flags, 'contains'),
+        index: (0, args_1.flagNum)(ctx.flags, 'index'),
+        ...stateFromFlags(ctx.flags),
     });
+    // Every command's selector — and so every `vk ai` leaf, which reaches these handlers
+    // through executeOutcome — funnels through here, which is why the platform check lives
+    // at this seam rather than in the (platform-free) selector layer.
+    (0, state_support_1.assertStateSupported)(sel, ctx.platform);
+    return sel;
 }
 function parsePoint(s) {
     const m = /^(-?\d+)\s*,\s*(-?\d+)$/.exec(s.trim());
@@ -458,7 +487,7 @@ function cmdUi(ctx) {
     return 0;
 }
 async function cmdFind(ctx) {
-    const sel = buildSelector(ctx.positionals[0], ctx.flags);
+    const sel = buildSelector(ctx, ctx.positionals[0]);
     const { matches, tier } = await matchWaiting(ctx, sel, { all: (0, args_1.flagBool)(ctx.flags, 'all') });
     if ((0, args_1.flagBool)(ctx.flags, 'json'))
         (0, output_1.json)(matches.map(format_1.toJsonShape));
@@ -511,7 +540,7 @@ async function cmdTap(ctx) {
         ctx.record?.note({ element: target, message: `tapped by index [${idx}]` });
     }
     else {
-        const sel = buildSelector(raw, ctx.flags);
+        const sel = buildSelector(ctx, raw);
         ({ element: target, tier, waitedMs, swipes, point } = await resolveTappable(ctx, sel, {
             all: (0, args_1.flagBool)(ctx.flags, 'all'),
         }));
@@ -530,7 +559,7 @@ async function cmdText(ctx) {
     if (ctx.positionals.length < 2) {
         throw new errors_1.CliError('Usage: verikun text <selector> <text...>  (use -- before text starting with "-")', 2);
     }
-    const sel = buildSelector(ctx.positionals[0], ctx.flags);
+    const sel = buildSelector(ctx, ctx.positionals[0]);
     const value = ctx.positionals.slice(1).join(' ');
     const { element: target, tier, waitedMs, swipes, point } = await resolveTappable(ctx, sel);
     ctx.record?.note({
@@ -606,7 +635,9 @@ async function cmdSwipe(ctx) {
     let waitedMs = 0;
     const on = (0, args_1.flagStr)(ctx.flags, 'on');
     if (on) {
-        const onSel = (0, selector_1.parseSelector)(on, { contains: (0, args_1.flagBool)(ctx.flags, 'contains') });
+        // Through buildSelector, not parseSelector: --on used to see only --contains, so
+        // `swipe --on X --enabled` silently ignored the modifier it was given.
+        const onSel = buildSelector(ctx, on);
         const { element, waitedMs: w } = await resolveOneWaiting(ctx, onSel);
         waitedMs = w;
         ctx.record?.note({ selector: onSel, element });
@@ -762,7 +793,7 @@ function cmdLog(ctx) {
     return 0;
 }
 async function cmdWait(ctx) {
-    const sel = buildSelector(ctx.positionals[0], ctx.flags);
+    const sel = buildSelector(ctx, ctx.positionals[0]);
     const gone = (0, args_1.flagBool)(ctx.flags, 'gone');
     const timeout = (0, args_1.flagNum)(ctx.flags, 'timeout') ?? 10000;
     const interval = (0, args_1.flagNum)(ctx.flags, 'interval') ?? 400;
@@ -822,7 +853,7 @@ function evalAssert(els, sel, flags) {
     return { pass, reason, matches };
 }
 async function cmdAssert(ctx) {
-    const sel = buildSelector(ctx.positionals[0], ctx.flags);
+    const sel = buildSelector(ctx, ctx.positionals[0]);
     // Auto-wait subsumes the common "wait then assert": poll until the assertion
     // passes or the window elapses. `--gone` therefore waits for disappearance.
     const deadline = Date.now() + waitWindowMs(ctx.flags);
@@ -1353,6 +1384,9 @@ async function runAiTest(file, opts, backend, platform, device) {
             guardSettleMs: guardSettleMs(),
             runId: started.id,
             deadline,
+            // The RESOLVED platform — for --server that is the server's, which supersedes
+            // the client's --platform (leaves are gated server-side; guards run here).
+            platform,
         });
     }
     catch (e) {
@@ -1859,6 +1893,15 @@ SELECTORS
   class:Button    type or full class name
   "Sign in"       bare string == text:"Sign in"
   Modifiers: --contains (substring), --index N (pick Nth match)
+  State:     --enabled / --selected / --checked / --focused, each with a --not-
+             form (--not-selected). Unset = don't care. Use the negative to guard
+             a toggle: tapping a picker whose options share a handler FLIPS it, so
+             an unconditional tap lands on the wrong mode and still exits 0.
+             May be written as a flag or appended to the selector string
+             ("@mode_video --not-selected") — the latter is how a \`vk ai\`
+             if-present/when/repeat guard carries one.
+             --selected and --focused are Android-only (idb reports neither);
+             on iOS they exit 3 rather than matching nothing.
 
 AUTO-WAIT (selector lookups retry until they resolve)
   Selector commands (tap, text, find, assert, swipe --on) re-poll the screen for

package/dist/ui/ios-parse.js

@@ -1,5 +1,6 @@
 "use strict";
 Object.defineProperty(exports, "__esModule", { value: true });
+exports.IOS_UNREPORTED_STATE = void 0;
 exports.isInteresting = isInteresting;
 exports.parseIosHierarchy = parseIosHierarchy;
 const viewport_1 = require("./viewport");
@@ -13,6 +14,23 @@ const TAPPABLE_TYPES = new Set([
 const SCROLLABLE_TYPES = new Set(['ScrollView', 'Table', 'TableView', 'CollectionView', 'WebView']);
 const CHECKABLE_TYPES = new Set(['Switch', 'Toggle', 'CheckBox', 'RadioButton']);
 const TEXT_INPUT_TYPES = new Set(['TextField', 'SecureTextField', 'SearchField', 'TextView']);
+/**
+ * State attributes idb does not report, so `Element` can only ever say `false`.
+ *
+ * MEASURED against the Flutter fixture's `@vk_state` screen on an iPhone 17 Pro simulator
+ * (iOS 26.5): a selected and an unselected segment came back byte-identical apart from
+ * label and frame, and a focused text field was indistinguishable from an unfocused one.
+ * The key is not merely unset — `idb ui describe-all` has no such key in its schema at all
+ * (it emits AXFrame, AXLabel, AXUniqueId, AXValue, content_required, custom_actions,
+ * enabled, frame, help, role, role_description, subrole, title, type, and nothing else),
+ * so no app can supply it and there is nothing to derive it from.
+ *
+ * Exported so `--selected` / `--focused` can be REJECTED on iOS rather than silently
+ * matching nothing — a filter that can never match is exactly the false-green failure the
+ * modifier exists to prevent. Keep this list next to the hard-coded `false`s below; if idb
+ * ever starts reporting one, delete it from here in the same change that parses it.
+ */
+exports.IOS_UNREPORTED_STATE = ['selected', 'focused'];
 function str(v) {
     return typeof v === 'string' ? v : v == null ? '' : String(v);
 }
@@ -81,6 +99,7 @@ function buildElement(raw) {
         checkable,
         checked: checkable && isTrue(raw.AXValue),
         focusable: false,
+        // `focused` and `selected` are not derivable — see IOS_UNREPORTED_STATE above.
         focused: false,
         scrollable: SCROLLABLE_TYPES.has(type),
         enabled: raw.enabled === undefined ? true : isTrue(raw.enabled),

package/dist/ui/selector.js

@@ -1,19 +1,68 @@
 "use strict";
 Object.defineProperty(exports, "__esModule", { value: true });
+exports.STATE_ATTRS = void 0;
 exports.parseSelector = parseSelector;
 exports.matchElements = matchElements;
 exports.resolveOne = resolveOne;
 const errors_1 = require("../errors");
 const format_1 = require("./format");
+/**
+ * The element state a selector can require. Each is TRI-STATE on a Selector:
+ * unset = don't care, `true` = must be, `false` = must NOT be.
+ *
+ * The negative half is not symmetry for its own sake. A segmented control whose
+ * options share one handler *flips* on any tap, so "tap it unless it is already
+ * selected" is the only safe way to land on a known option — and a plan that
+ * cannot say that taps blind, completes either way, and passes having exercised
+ * the opposite mode.
+ */
+exports.STATE_ATTRS = ['enabled', 'selected', 'checked', 'focused'];
+/** Trailing ` --selected` / ` --not-checked` / … on a selector STRING. */
+const STATE_MODIFIER = new RegExp(`\\s+--(not-)?(${exports.STATE_ATTRS.join('|')})\\s*$`, 'i');
+/**
+ * Peel state modifiers off the END of a selector string.
+ *
+ * Flags normally arrive as flags, but a control node's selector has nowhere to put
+ * one: `if-present` / `when` / `repeat` / `while-present` / `read` all hold a bare
+ * `selector: string` (and `swipe --on` is a flag value). Guards are exactly where
+ * "tap it only if it is not already selected" needs to be expressed, so the string
+ * itself carries them and every caller converges on this one parser:
+ *
+ *     if-present "id:mode_video --not-selected" { tap id:mode_video }
+ *
+ * Only these modifiers, only at the end, and only after whitespace — so `text:--selected`
+ * and `text:a --selected b` are still plain values. A `text:` value that genuinely ENDS
+ * in " --selected" would be misread; use `--contains` on a shorter substring if you ever
+ * meet one. Note the engine interpolates `{{ctx.…}}` before parsing, so a value captured
+ * by `read` could in principle end in a modifier — end-anchoring plus the required space
+ * is what keeps that from being a practical concern.
+ */
+function splitStateModifiers(raw) {
+    const state = {};
+    let rest = raw;
+    for (;;) {
+        const m = STATE_MODIFIER.exec(rest);
+        if (!m)
+            return { rest, state };
+        const attr = m[2].toLowerCase();
+        const want = !m[1];
+        if (state[attr] !== undefined && state[attr] !== want) {
+            throw new errors_1.CliError(`Selector '${raw}' asks for both --${attr} and --not-${attr}.`, 2);
+        }
+        state[attr] = want;
+        rest = rest.slice(0, m.index);
+    }
+}
 function parseSelector(raw, opts = {}) {
+    const { rest, state } = splitStateModifiers(raw);
     let kind = 'text';
-    let value = raw;
-    if (raw.startsWith('@')) {
+    let value = rest;
+    if (rest.startsWith('@')) {
         kind = 'id';
-        value = raw.slice(1);
+        value = rest.slice(1);
     }
     else {
-        const m = /^(id|text|desc|class):([\s\S]*)$/.exec(raw);
+        const m = /^(id|text|desc|class):([\s\S]*)$/.exec(rest);
         if (m) {
             kind = m[1];
             value = m[2];
@@ -21,20 +70,35 @@ function parseSelector(raw, opts = {}) {
     }
     if (!value)
         throw new errors_1.CliError(`Empty selector value in '${raw}'`, 2);
-    return { kind, value, contains: !!opts.contains, index: opts.index, enabled: opts.enabled, raw };
+    const sel = { kind, value, contains: !!opts.contains, index: opts.index, raw };
+    for (const attr of exports.STATE_ATTRS) {
+        // An explicit flag beats one embedded in the string; absent means absent, not false.
+        const want = opts[attr] !== undefined ? opts[attr] : state[attr];
+        if (want !== undefined)
+            sel[attr] = want;
+    }
+    return sel;
 }
-/** Is this element actionable right now?
+/** Keep only elements whose state matches every attribute the selector pins.
  *
- *  Just `enabled` — the a11y attribute, matching what Maestro's `enabled: true` means.
- *  An earlier version also required `clickable || longClickable`, reasoning that a
- *  disabled Button might report clickable=false. That was speculation and it was wrong in
- *  the direction that hurts: plenty of legitimate tap targets are CONTAINERS whose own
- *  clickable flag is false (the tappable child is inside), so the extra conjunct filtered
- *  out real elements and turned `--enabled` into a source of phantom "not found" misses —
- *  which then burned model repairs. Prefer under-filtering here: a tap on a present-but-
- *  odd element fails loudly, whereas a selector that silently matches nothing looks like
- *  app drift and sends the heal loop chasing it. */
-const isActionable = (e) => e.enabled;
+ *  Each predicate is exactly the one a11y attribute and nothing else — `--enabled` is
+ *  `enabled`, matching what Maestro's `enabled: true` means. An earlier version also
+ *  required `clickable || longClickable`, reasoning that a disabled Button might report
+ *  clickable=false. That was speculation and it was wrong in the direction that hurts:
+ *  plenty of legitimate tap targets are CONTAINERS whose own clickable flag is false (the
+ *  tappable child is inside), so the extra conjunct filtered out real elements and turned
+ *  `--enabled` into a source of phantom "not found" misses — which then burned model
+ *  repairs. Prefer under-filtering here: a tap on a present-but-odd element fails loudly,
+ *  whereas a selector that silently matches nothing looks like app drift and sends the
+ *  heal loop chasing it. Same rule for any attribute added to STATE_ATTRS — do not
+ *  strengthen a predicate with a conjunct the platform reports unreliably (`--not-checked`
+ *  deliberately does NOT also require `checkable`). */
+function filterByState(elements, sel) {
+    const pinned = exports.STATE_ATTRS.filter((attr) => sel[attr] !== undefined);
+    if (pinned.length === 0)
+        return elements;
+    return elements.filter((el) => pinned.every((attr) => el[attr] === sel[attr]));
+}
 const norm = (s) => s.trim().toLowerCase();
 const strip = (s) => s.toLowerCase().replace(/[^a-z0-9]+/g, '');
 /** The ordered match tiers for a selector. First tier with a hit wins. */
@@ -91,8 +155,7 @@ function tiers(sel) {
 function matchElements(elements, sel) {
     // Applied BEFORE the tier ladder, not after: filtering the candidate pool keeps a
     // disabled exact match from shadowing an enabled partial one.
-    if (sel.enabled)
-        elements = elements.filter(isActionable);
+    elements = filterByState(elements, sel);
     for (const { tier, test } of tiers(sel)) {
         const found = elements.filter(test);
         if (found.length === 0)

package/dist/ui/state-support.js

@@ -0,0 +1,41 @@
+"use strict";
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.unsupportedStateAttrs = unsupportedStateAttrs;
+exports.assertStateSupported = assertStateSupported;
+const errors_1 = require("../errors");
+const selector_1 = require("./selector");
+const ios_parse_1 = require("./ios-parse");
+// Which state attributes a platform's accessibility backend can actually answer for.
+//
+// A state modifier narrows the candidate pool, so one the platform never populates does
+// not fail — it matches NOTHING, quietly, after burning the full auto-wait window, and
+// then reports "No element matched selector", which is a claim about the screen that
+// isn't true. That is the same false-signal failure mode `--selected` was added to fix,
+// so it is refused here instead: an unsupported modifier is an environment error (exit
+// 3), the way `clearApp` and `currentApp` already refuse on iOS rather than pretending.
+//
+// This is a capability table, not device I/O — the per-platform truth lives with the
+// parser that hard-codes the value (see IOS_UNREPORTED_STATE), so the two cannot drift.
+const UNREPORTED = {
+    android: [], // uiautomator dumps all four as real node attributes
+    ios: ios_parse_1.IOS_UNREPORTED_STATE,
+};
+/** State attributes this selector pins that the platform cannot report. */
+function unsupportedStateAttrs(sel, platform) {
+    const blind = UNREPORTED[platform];
+    if (blind.length === 0)
+        return [];
+    return selector_1.STATE_ATTRS.filter((attr) => sel[attr] !== undefined && blind.includes(attr));
+}
+/** Throw unless every state modifier on `sel` means something on `platform`. */
+function assertStateSupported(sel, platform) {
+    const bad = unsupportedStateAttrs(sel, platform);
+    if (bad.length === 0)
+        return;
+    // Name both polarities: --not-selected is refused for the same reason as --selected,
+    // and echoing only the attribute reads as though the wrong flag was typed.
+    const named = bad.map((a) => `--${a}/--not-${a}`).join(' and ');
+    throw new errors_1.CliError(`${named} cannot be used on ${platform}: its accessibility backend does not report ` +
+        `${bad.join(' or ')}, so the selector could only ever match nothing. ` +
+        `Match on ${platform === 'ios' ? '@id, text or --enabled/--checked' : 'another attribute'} instead.`, 3);
+}

package/dist/version.js

@@ -3,4 +3,4 @@ Object.defineProperty(exports, "__esModule", { value: true });
 exports.VERSION = void 0;
 // GENERATED by scripts/gen-version.mjs from package.json's "version" at build time
 // (the `prebuild` script). Do NOT edit by hand; bump package.json instead.
-exports.VERSION = '0.15.0';
+exports.VERSION = '0.16.0';

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "verikun",
-  "version": "0.15.0",
+  "version": "0.16.0",
   "description": "Drive Android emulators/devices and iOS simulators for AI agents: tap, type, swipe, screenshot, and inspect the UI hierarchy by semantic identifiers — like Puppeteer for native apps.",
   "keywords": [
     "android",