@sungen/driver-ui 3.2.3-beta.3 → 3.2.4

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@sungen/driver-ui",
-  "version": "3.2.3-beta.3",
+  "version": "3.2.4",
   "description": "Sungen UI capability (Playwright) — step patterns, viewpoint gate, and phase hooks. 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.3-beta.3"
+    "@sun-asterisk/sungen": "3.2.4"
   },
   "peerDependencies": {
     "@playwright/test": "^1.57.0"

package/src/patterns/interaction-patterns.ts

@@ -372,8 +372,15 @@ export const interactionPatterns: StepPattern[] = [
   },
   {
     name: 'toggle-switch',
+    // Matches the unconditional-flip verb "toggle(s)" — e.g. `When User toggles [X]`. Steps that
+    // say `check`/`uncheck [X] toggle` also contain the word "toggle" (as the element-type suffix)
+    // but express a desired on/off STATE, not a blind flip — those must fall through to the
+    // idempotent check-checkbox/uncheck-checkbox patterns below instead (priority 8), so excluding
+    // the check/uncheck verbs here is what makes that routing possible.
     matcher: (step: ParsedStep) =>
-      (step.text.includes('toggles') || step.text.match(/\btoggle\b/)) && !!step.selectorRef,
+      (step.text.includes('toggles') || step.text.match(/\btoggle\b/)) &&
+      !/\b(checks?|unchecks?)\b/.test(step.text) &&
+      !!step.selectorRef,
     resolver: (step, context) => {
       const resolved = context.selectorResolver.resolveSelector(step.selectorRef!, undefined, step.elementType, step.nth);
       return {

package/src/patterns/table-patterns.ts

@@ -214,9 +214,27 @@ export const tablePatterns: StepPattern[] = [
       const elementType = elementTypeMatch ? elementTypeMatch[1].toLowerCase() : 'button';
       const elementRole = typeToRole[elementType] || elementType;
 
+      // Resolve the inner action element through selectors.yaml (honoring any
+      // AI-authored locator / testid / custom name), scoped to the matched row via
+      // parentLocator. When no YAML entry exists the resolver auto-infers role+name,
+      // and when resolution throws we rebuild the historical getByRole string — so the
+      // no-entry / unmapped cases stay byte-identical to the previous hardcoded output.
+      let actionLocator: string;
+      try {
+        const elementResolved = context.selectorResolver.resolveSelector(
+          elementName, context.featureName, elementType, step.nth
+        );
+        actionLocator = context.renderLocator({ ...elementResolved, parentLocator: 'tableRow' });
+      } catch {
+        const escapedName = String(elementName)
+          .replace(/\\/g, '\\\\').replace(/'/g, "\\'")
+          .replace(/\n/g, '\\n').replace(/\r/g, '\\r').replace(/\t/g, '\\t');
+        actionLocator = `tableRow.getByRole('${elementRole}', { name: '${escapedName}' })`;
+      }
+
       return {
         templateName: 'table-action-in-row',
-        data: { ...tableResolved, elementName, filterValue, action, elementRole },
+        data: { ...tableResolved, elementName, filterValue, action, elementRole, actionLocator },
         comment: `${action} ${elementName} in ${tableName} table row with ${step.dataRef}`,
       };
     },