@sungen/driver-mobile 3.2.24 → 3.2.25

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@sungen/driver-mobile",
-  "version": "3.2.24",
+  "version": "3.2.25",
   "description": "Sungen mobile platform driver (Appium / WebdriverIO) — gesture vocabulary, mobile selector strategies, viewpoint gate, and the WDIO runner. Plugs into @sun-asterisk/sungen via the capability SPI.",
   "main": "src/index.ts",
   "types": "src/index.ts",
@@ -13,7 +13,7 @@
   "author": "eqe team (engineer & quality) — Sun Asterisk",
   "license": "MIT",
   "dependencies": {
-    "@sun-asterisk/sungen": "3.2.24",
+    "@sun-asterisk/sungen": "3.2.25",
     "@wdio/appium-service": "^9.0.0",
     "@wdio/cli": "^9.0.0",
     "@wdio/local-runner": "^9.0.0",

package/src/patterns/lifecycle-patterns.ts

@@ -7,7 +7,39 @@
  * Mobile-only: on a web project these hit the missing-template guard (SG-E020) and fail
  * loud, same policy as every gesture.
  */
-import { StepPattern } from '@sun-asterisk/sungen';
+import { StepPattern, ParsedStep, PatternContext, StepTemplateData } from '@sun-asterisk/sungen';
+
+/**
+ * The app-lifecycle templates all resolve the target app through `__resolveAppId()`, a helper the
+ * appium test-file template emits ONLY when the feature declares its app id:
+ *
+ *     Feature: plan-list
+ *       Path: com.example.app/.MainActivity | com.example.app
+ *
+ * Without that line the spec compiled clean, warned nothing, and then died at runtime with
+ * `ReferenceError: __resolveAppId is not defined` — taking the WHOLE spec down, not the one step,
+ * because the failure lands in a before hook. (Field case: a mobile unit scaffolded with the nav
+ * recipe in `--path` instead of `--reach`, so Path never carried an app id.)
+ *
+ * Refusing here converts that into a compile-time message naming the missing line.
+ */
+const requiresAppId = (
+  step: ParsedStep, context: PatternContext, verb: string
+): StepTemplateData | null => {
+  if (context.featurePath) return null;
+  const reason =
+    `${verb} needs the app id: the mobile lifecycle steps resolve the target app from the feature's `
+    + `Path, and this feature declares none, so the generated helper would be missing and the whole `
+    + `spec would fail at runtime. Add it under the Feature line, e.g. `
+    + `Path: com.example.app/.MainActivity | com.example.app  (for a mobile unit, --path carries the `
+    + `APP ID and --reach carries the navigation recipe).`;
+  context.diagnostics?.add('SG-E024', reason, { feature: context.featureName, step: step.text });
+  return {
+    templateName: 'lifecycle-missing-app-id',
+    data: { reason },
+    comment: `${verb} without a Path app id — see SG-E024`,
+  };
+};
 
 export const lifecyclePatterns: StepPattern[] = [
   {
@@ -15,7 +47,8 @@ export const lifecyclePatterns: StepPattern[] = [
     // present — `tap [Restart Button]` belongs to the tap pattern, not here.
     name: 'restart-app',
     matcher: (step) => /\brestart(s)?\b/i.test(step.text) && /\bapp\b/i.test(step.text) && !step.selectorRef,
-    resolver: () => ({ templateName: 'restart-app-action', data: {}, comment: 'Restart the app (kill → relaunch → settle)' }),
+    resolver: (step, context) => requiresAppId(step, context, 'restart the app')
+      ?? { templateName: 'restart-app-action', data: {}, comment: 'Restart the app (kill → relaunch → settle)' },
     priority: 16,
   },
   {
@@ -23,7 +56,8 @@ export const lifecyclePatterns: StepPattern[] = [
     // (appium:app); the template fails loud with the fix when the cap is absent.
     name: 'reinstall-app',
     matcher: (step) => /\bre-?install(s)?\b/i.test(step.text) && /\bapp\b/i.test(step.text) && !step.selectorRef,
-    resolver: () => ({ templateName: 'reinstall-app-action', data: {}, comment: 'Reinstall the app (remove → install → launch)' }),
+    resolver: (step, context) => requiresAppId(step, context, 'reinstall the app')
+      ?? { templateName: 'reinstall-app-action', data: {}, comment: 'Reinstall the app (remove → install → launch)' },
     priority: 16,
   },
   {