@skyramp/mcp 0.2.5 → 0.2.6

package/build/prompts/enhance-assertions/uiAssertionsPrompt.js

@@ -186,17 +186,28 @@ await page.context().addInitScript(() => {
 });
 \`\`\`
 
-And immediately after **every** \`page.goto()\` call in the test, add:
+And immediately after **every** \`page.goto()\` call in the test, add exactly these two statements — do NOT substitute a different activation approach or a different \`waitForFunction\` body:
 
 \`\`\`typescript
+// Activate Flutter accessibility semantics by clicking the hidden placeholder
+await page.evaluate(() => { const el = document.querySelector('flt-semantics-placeholder'); if (el) el.dispatchEvent(new MouseEvent('click', { isTrusted: true, bubbles: true, cancelable: true })); });
 // Wait for Flutter semantics tree to be fully populated before interacting
 await page.waitForFunction(
     () => document.querySelector('flt-semantics-host')?.children?.length > 0,
-    { timeout: 10000 }
+    { timeout: 20000 }
 );
 \`\`\`
 
-This is required because Flutter web accessibility semantics are not activated by default in headless Chromium — synthetic click events are marked as untrusted and ignored by Flutter's gate. The \`isTrusted\` patch makes the click trusted; the \`waitForFunction\` after EVERY \`goto()\` ensures the ARIA tree is fully populated before any \`getByRole\` queries or \`click()\` calls run. Without both additions, Flutter interactions will time out in CI/Docker execution.
+The \`waitForFunction\` check MUST be \`children?.length > 0\` (tree populated), NOT \`!!document.querySelector('flt-semantics-host')\` (tree merely exists — it appears immediately but empty). If you see an existing body click or \`locator.click\` block after a goto, replace the entire block with the exact two statements above.
+
+This is required because Flutter web accessibility semantics are not activated by default in headless Chromium. The \`isTrusted\` patch makes synthetic click events trusted; the \`dispatchEvent\` call triggers Flutter to build the ARIA tree; the \`children?.length > 0\` wait ensures the tree is fully populated before any \`getByRole\` queries or \`click()\` calls run. Without all three (patch + dispatchEvent + populated wait), Flutter interactions will time out in CI/Docker execution.
+
+**Also check for brittle flt-semantic-node-* selectors:** If the test uses \`page.locator("#flt-semantic-node-N")\` for any interaction (clicks, navigations), replace it with a semantic selector (\`getByRole\`, \`getByText\`, or \`getByLabel\`) — \`flt-semantic-node-N\` IDs change between sessions and across devices, making the test brittle. Example: replace \`page.locator("#flt-semantic-node-78").click()\` with \`page.getByText("Settings").click()\` using the visible label from the same line's context.
+
+**Flutter assertion grounding rule:** For Flutter web tests, use the following priority order when adding \`expect()\` assertions:
+1. **Existing selectors in the test file** — prefer these first; they were captured from the live accessibility tree during recording.
+2. **\`browser_blueprint\` snapshot** — if a blueprint was captured, use element roles, names, and text that appear verbatim in the snapshot.
+3. **Source code / diff** — only consult source code after exhausting the above. Flutter's accessibility tree frequently omits or transforms text (e.g. CJK characters split into individual nodes, \`ExcludeSemantics\` widgets, icon-only buttons), so what appears in the Dart source may not exist in the ARIA tree at runtime. If a selector derived from source cannot be confirmed in the blueprint or recorded trace, skip the assertion rather than risk a false positive.
 
 ### Pre-Edit Assertion Analysis
 Before editing the given test file, you must output a \`<thinking>\` block. The aim of the \`<thinking>\` block is to analyze each in-scope item (action, selector, or captured network response) in the given test file and output a JSON array that ensures no assertion rule is overlooked. The JSON array should match the template below — every assertion category and every rule title under it must appear as a key, even when the value is \`[]\`.

package/node_modules/playwright/lib/mcp/skyramp/traceRecordingBackend.js

@@ -1235,6 +1235,14 @@ Cell row ${params.row}, column ${params.column} has "${actual}", expected "${par
         locator: { kind: "text", body: text, options: { exact: false } }
       };
     }
+    const colonTextMatch = refLine.match(/\[ref=\w+\](?:\s*\[[^\]]*\])*\s*:\s*(.+?)\s*$/);
+    if (colonTextMatch && colonTextMatch[1].trim()) {
+      const text = colonTextMatch[1].trim();
+      return {
+        selector: `internal:text="${text}"i`,
+        locator: { kind: "text", body: text, options: { exact: false } }
+      };
+    }
     return null;
   }
   /**
@@ -1671,8 +1679,12 @@ Cell row ${params.row}, column ${params.column} has "${actual}", expected "${par
       }
     }
     if (!isFlutter) return;
-    const placeholder = page.locator("flt-semantics-placeholder").first();
-    const clicked = await placeholder.click({ force: true }).then(() => true).catch(() => false);
+    const clicked = await page.evaluate(() => {
+      const el = document.querySelector("flt-semantics-placeholder");
+      if (!el) return false;
+      el.dispatchEvent(new MouseEvent("click", { isTrusted: true, bubbles: true, cancelable: true }));
+      return true;
+    }).catch(() => false);
     if (!clicked) {
       traceDebug("Flutter detected but placeholder click failed");
       return;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@skyramp/mcp",
-  "version": "0.2.5",
+  "version": "0.2.6",
   "main": "build/index.js",
   "exports": {
     ".": "./build/index.js",