mobile-automator 0.31.0 → 0.31.2

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "mobile-automator",
-  "version": "0.31.0",
+  "version": "0.31.2",
   "description": "Host-agnostic mauto CLI for AI-driven mobile QA automation — analyzes a mobile project and drives devices through mobile-mcp.",
   "homepage": "https://github.com/sh3lan93/mobile-automator#readme",
   "repository": {

package/src/assertion/evaluator.js

@@ -282,4 +282,8 @@ function evaluate(assertion = {}, ctx = {}) {
   return result(type, true, pass, message);
 }
 
-module.exports = { MECHANICAL_TYPES, evaluate };
+// `matches`/`findFirst` are exported for the real-device E2E harness
+// (sample-app/scripts/lib/resolve.js), which resolves tap targets with THIS
+// matcher so the harness and `mauto assert` can never disagree about what a
+// target string means (#94).
+module.exports = { MECHANICAL_TYPES, evaluate, matches, findFirst };

package/src/config/schema.js

@@ -12,14 +12,14 @@
 
 const fs = require('fs');
 const path = require('path');
-const Ajv = require('ajv');
 
 const { formatError } = require('../schemas/format-error');
+const { createCliAjv } = require('../schemas/cli-ajv');
 
 const CONFIG_SCHEMA_PATH = path.resolve(__dirname, '../schemas/config_schema.json');
 
 const schema = JSON.parse(fs.readFileSync(CONFIG_SCHEMA_PATH, 'utf8'));
-const ajv = new Ajv({ allErrors: true, strict: false });
+const ajv = createCliAjv();
 
 // Resolve a local `$ref` ("#/definitions/stringList") to a fixpoint: a
 // resolved node may itself be another `$ref` (e.g. a `$ref` to a `$ref`), so

package/src/scenario/validator.js

@@ -2,9 +2,9 @@
 
 const fs = require('fs');
 const path = require('path');
-const Ajv = require('ajv');
 
 const { formatError } = require('../schemas/format-error');
+const { createCliAjv } = require('../schemas/cli-ajv');
 
 // Path to the canonical scenario schema, bundled inside the package.
 // src/scenario/validator.js -> ../schemas/scenario_schema.json
@@ -13,7 +13,7 @@ const DEFAULT_SCHEMA_PATH = path.resolve(__dirname, '../schemas/scenario_schema.
 class ScenarioValidator {
   constructor({ schemaPath = DEFAULT_SCHEMA_PATH } = {}) {
     const schema = JSON.parse(fs.readFileSync(schemaPath, 'utf8'));
-    const ajv = new Ajv({ allErrors: true, strict: false });
+    const ajv = createCliAjv();
     this._validateFn = ajv.compile(schema);
   }
 

package/src/schemas/cli-ajv.js

@@ -0,0 +1,32 @@
+'use strict';
+
+// The only place the CLI's Ajv instance is constructed (#191).
+//
+// There used to be two hand-copied `new Ajv({ allErrors: true, strict: false })`
+// literals — one in src/config/schema.js, one in src/scenario/validator.js —
+// plus a third mirror in the schema lint guard tied to them by nothing but a
+// comment. Three copies of "the CLI's own options" that nothing kept true:
+// change the options in src and the guard would keep vouching for the old
+// ones. A guard that hand-maintains a copy of the thing it guards is itself a
+// drift surface — the same lesson that produced docs-corpus.js.
+//
+// Everything that needs the CLI's Ajv — both call sites above, the unit tests
+// that validate envelopes against the shipped schemas, and
+// tests/lint/schemas-valid.test.js, which compiles every schema with the real
+// instance — now consumes this factory. That guard also fails on any other
+// construction site in src/ or bin/, so the options cannot quietly return as
+// literals.
+
+const Ajv = require('ajv');
+
+// allErrors: true — `mauto validate` and config validation report every
+// problem in one pass, not just the first one they hit.
+// strict: false — result_schema.json declares `format: "date-time"` and no
+// instance here registers formats, so strict mode would turn Ajv's warning
+// into an error. The CLI tolerates the warning rather than claim format
+// checking it does not actually do.
+function createCliAjv() {
+  return new Ajv({ allErrors: true, strict: false });
+}
+
+module.exports = { createCliAjv };