@exodus/xqa 1.12.0 → 1.13.0

package/dist/xqa.cjs

@@ -62958,6 +62958,7 @@ var STUCK_LOOP_RULE = `Stuck loop: emit a \`stuck-loop\` finding when any of the
 var LOADING_STATE_RULE = `Transient loading state: when the screen shows spinners, skeleton screens, progress bars, "Loading..." text, or placeholder content NOT described in spec or app context \u2014 use \`screenshot\` to poll for resolution (up to 3 retries); switch to \`view_ui\` only on the final check or when you need element data to act \u2014 if loading persists after 3 retries, proceed with what is visible; if spec or app context explicitly describes a loading screen as a step, do not retry \u2014 call \`view_ui\` and assert normally`;
 var EXPECTED_CONTENT_MISSING_RULE = `Expected content missing: when \`view_ui\` shows no loading indicator yet omits an element named or strongly implied by spec or app context \u2014 and its absence is not semantically consistent with the current screen \u2014 call \`wait_seconds\` with 2\u20135 seconds and retry \`view_ui\` up to 2 times; if element remains absent, emit a \`missing-content\` finding stating what was expected and what was observed`;
 var CLIPPED_ELEMENT_RULE = `Never tap an element tagged \`[clipped-top]\`, \`[clipped-bottom]\`, \`[clipped-left]\`, or \`[clipped-right]\` \u2014 scroll to fully reveal it first, then re-call \`view_ui\` before tapping`;
+var A11Y_FALLBACK_RULE = `Missing a11y element: if you intend to tap or interact with a UI element and that element is absent from the most recent \`view_ui\` a11y tree \u2014 do NOT estimate its coordinates from the screenshot or attempt any pixel-based tap \u2014 instead, emit a \`missing-a11y-element\` finding that states: (1) your intent (what you were trying to do), (2) the approximate visual region where the element appeared (coords/size from the screenshot), (3) nearby labeled elements from the a11y tree that serve as landmarks \u2014 then continue: in freestyle mode keep exploring other reachable screens; in spec mode advance to the next step`;
 var WHAT_TO_TEST_SECTION = `## What to Test
 
 Test navigation elements first, interactions second.
@@ -62977,6 +62978,15 @@ Test navigation elements first, interactions second.
 - Static labels, decorative images, dividers
 
 If an interaction produces no observable change, retry once before flagging.`;
+var DESTRUCTIVE_ACTIONS_SECTION = `## Destructive Actions
+
+Never confirm actions that have permanent, irreversible, or externally observable consequences. Examples: sending or signing transactions, transferring funds, broadcasting messages, deleting accounts or wallets, wiping data, resetting the app, revoking sessions, logging out, uninstall prompts, in-app purchases, granting permissions to third parties, or any dialog whose primary button is labeled \`Send\`, \`Confirm\`, \`Sign\`, \`Pay\`, \`Delete\`, \`Remove\`, \`Reset\`, \`Erase\`, \`Log out\`, \`Sign out\`, \`Approve\`, or equivalent.
+
+Rules:
+- Navigate up to the confirmation step to verify the flow is reachable and the dialog renders correctly, then back out via cancel, close, or back \u2014 do not tap the destructive confirm.
+- If the only exit from a screen is the destructive confirm, emit a \`destructive-only-exit\` finding and halt that branch \u2014 do not proceed.
+- Treat irreversible in-app state changes (e.g. marking an item as consumed, claiming a one-time reward, rotating a seed) the same as destructive actions unless app context explicitly authorizes them.
+- When in doubt about reversibility, treat the action as destructive and back out.`;
 var DEAD_END_SECTION = `## Dead End and Modal Detection
 
 **Dead end** \u2014 when \`view_ui\` shows no interactive exit affordance, first consult App Knowledge for gesture-based navigation on this screen, then attempt ALL of before emitting a finding: (1) any visible back/close button, (2) swipe from the left edge (back gesture), (3) swipe down (dismiss gesture). If all fail, emit a \`dead-end\` finding describing what was visible and what was attempted.
@@ -63039,6 +63049,7 @@ var SPEC_RULES_SECTION = `## Rules
 - ${LOADING_STATE_RULE}
 - ${EXPECTED_CONTENT_MISSING_RULE}
 - ${CLIPPED_ELEMENT_RULE}
+- ${A11Y_FALLBACK_RULE}
 - Each item in \`**Assertions**\` is a mandatory pass/fail check \u2014 verify using \`view_ui\` when the assertion targets an element attribute, label, or presence in the tree; use \`screenshot\` when the assertion is purely visual; if neither can confirm, emit a \`spec-deviation\` finding based on what is observable
 - Flag crash dialogs, unexpected system errors, or navigation failures that occur as a direct result of executing a spec step; if you observe a visibly broken element in passing while navigating, note it without interacting with it`;
 function buildSpecModeBody({
@@ -63083,12 +63094,7 @@ var SPEC_MODE_TEMPLATE = (specContent, options) => {
 ${DEV_ENVIRONMENT_SECTION}` : "";
   return buildSpecModeBody({ specContent, contextBlock, environmentSection });
 };
-var FREESTYLE_TEMPLATE = (options) => {
-  const { appContext, initialState: initialState2, buildEnv } = options ?? {};
-  const contextBlock = buildContextSections(appContext, initialState2);
-  const environmentSection = buildEnv === "dev" ? `
-
-${DEV_ENVIRONMENT_SECTION}` : "";
+function buildFreestyleBody({ contextBlock, environmentSection }) {
   return `You are a navigation and interaction testing agent. Your first action MUST be a \`view_ui\` call. Your role is to find broken navigation flows and non-functional interactive elements. Do not report content bugs, copy errors, or visual style issues unless they directly prevent a navigation action from completing.
 
 ${contextBlock}
@@ -63106,6 +63112,7 @@ ${TOOL_SELECTION_SECTION}
 - ${LOADING_STATE_RULE}
 - ${EXPECTED_CONTENT_MISSING_RULE}
 - ${CLIPPED_ELEMENT_RULE}
+- ${A11Y_FALLBACK_RULE}
 
 ## Exploration Strategy
 
@@ -63113,11 +63120,21 @@ Explore breadth-first: map all screens reachable from the current screen before
 
 ${WHAT_TO_TEST_SECTION}
 
+${DESTRUCTIVE_ACTIONS_SECTION}
+
 ${DEAD_END_SECTION}${environmentSection}
 
 ## Output
 
 CRITICAL: Call \`set_output\` each time your findings change \u2014 when you discover something new, confirm a false positive, or revise a finding. Each call replaces the previous output entirely, so always pass the full current list. Do not reply in plain text.`;
+}
+var FREESTYLE_TEMPLATE = (options) => {
+  const { appContext, initialState: initialState2, buildEnv } = options ?? {};
+  const contextBlock = buildContextSections(appContext, initialState2);
+  const environmentSection = buildEnv === "dev" ? `
+
+${DEV_ENVIRONMENT_SECTION}` : "";
+  return buildFreestyleBody({ contextBlock, environmentSection });
 };
 function generateExplorerPrompt({
   mode,
@@ -76458,7 +76475,7 @@ function resolveXqaDirectory() {
   return result.value;
 }
 var program2 = new Command();
-program2.name("xqa").description("AI-powered QA agent CLI").version(`${"1.12.0"}${false ? ` (dev build +${"3c4f23d"})` : ""}`);
+program2.name("xqa").description("AI-powered QA agent CLI").version(`${"1.13.0"}${false ? ` (dev build +${"5e72ba0"})` : ""}`);
 program2.command("init").description("Initialize a new xqa project in the current directory").action(() => {
   runInitCommand();
 });

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@exodus/xqa",
-  "version": "1.12.0",
+  "version": "1.13.0",
   "type": "module",
   "engines": {
     "node": ">=22"
@@ -26,9 +26,9 @@
     "typescript": "^5.8.3",
     "vitest": "^3.2.1",
     "zod": "^3.0.0",
-    "@qa-agents/eslint-config": "0.0.0",
-    "@qa-agents/explorer": "0.0.0",
     "@qa-agents/display": "0.0.0",
+    "@qa-agents/explorer": "0.0.0",
+    "@qa-agents/eslint-config": "0.0.0",
     "@qa-agents/mobile-ios": "0.0.0",
     "@qa-agents/pipeline": "0.0.0",
     "@qa-agents/shared": "0.0.0",