@exodus/xqa 1.7.0 → 1.9.0

package/dist/xqa.cjs

@@ -52765,7 +52765,6 @@ var findingSchema = external_exports.object({
     "motion-regression",
     "interaction-regression",
     "continuity-regression",
-    "hint-drift",
     "step-skipped"
   ]),
   flow: external_exports.string(),
@@ -62952,9 +62951,7 @@ Each step has this shape:
 - If an outcome state is present, it is your verification target. After acting, call \`view_ui\` and confirm the outcome is met before marking the step complete. If no outcome is given, proceed when the action succeeds.
 - A hint is advisory only. Prefer an element matching the hint, but if no literal match exists, use intent and visual context to select the best candidate. Never fail a step solely because a hint label is absent.
 - Infer element role (primary action, secondary action, dismissal) from visual hierarchy, position, and hint text. Authors do not specify role.
-- If you act without a hint match, emit a \`hint-drift\` finding with the expected hint text and the actual label you acted on. This is non-blocking. Continue execution.
-- If no element satisfies the intent after exhausting visible UI, emit a \`spec-deviation\` finding and halt that step.
-- If \`hint-drift\` is emitted AND the outcome state fails to verify on the same step, escalate to \`spec-deviation\`. Drift plus outcome failure means a structural change, not cosmetic drift.`;
+- If no element satisfies the intent after exhausting visible UI, emit a \`spec-deviation\` finding and halt that step.`;
 var SPEC_OPTIONAL_STEPS_SECTION = `## Optional Steps
 
 Before executing a step, call \`view_ui\` to observe current screen state.
@@ -62963,8 +62960,6 @@ A step MAY be skipped if and only if:
 - The action's direct target (element, modal, screen) is not present, AND
 - The current screen state already satisfies the expected postcondition of this step (i.e. the step's effect has already occurred or was never needed).
 
-When skipping, emit a \`step-skipped\` finding with a one-sentence reason explaining what was absent and what already-satisfied condition justified the skip.
-
 Do NOT skip if:
 - The target is absent but the screen is in an unexpected or intermediate state.
 - You are uncertain whether the postcondition is satisfied.
@@ -75776,7 +75771,7 @@ function resolveXqaDirectory() {
   return result.value;
 }
 var program2 = new Command();
-program2.name("xqa").description("AI-powered QA agent CLI").version(`${"1.7.0"}${false ? ` (dev build +${"a108066"})` : ""}`);
+program2.name("xqa").description("AI-powered QA agent CLI").version(`${"1.9.0"}${false ? ` (dev build +${"0938687"})` : ""}`);
 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.7.0",
+  "version": "1.9.0",
   "type": "module",
   "engines": {
     "node": ">=22"