Plan a reverse action from a state it can move from

CHANGELOG.md

@@ -25,6 +25,11 @@
   instead of just the path, so the mismatch is visible in the log.
 - Network calls and API requests recorded during a run are matched against the site the same way, so calls made
   from a redirected host are captured instead of silently dropped.
+- [Pilot] A test that checks a reverse action — going back a page, undoing, closing, collapsing, clearing a
+  filter — is now planned from a starting point where that action has somewhere to go. Pilot used to plan the
+  click from wherever the page happened to be, so a test of the previous-page control that started on page 1
+  clicked an inert arrow and reported a failure the app had not caused. It now plans the steps that reach the
+  state the action leads back from before the step being measured.
 
 ## 2026-09-17
 

src/ai/pilot.ts

@@ -475,6 +475,10 @@ export class Pilot implements Agent {
         the elements needed for the scenario. The page summary does not list every element.
         Prefer interacting with the current page over navigating away.
 
+        A scenario that verifies a reverse or returning action can only be measured from the state that
+        action leads back from. When the page is not in that state, plan the steps that reach it first —
+        exercising the control from the wrong end proves nothing and is not a defect.
+
         Tester never sees <experience> — a recorded recipe reaches it only when you open one.
         The entries listed are what was recorded on the page you are on now; recipes for the
         pages this test moves to are listed when it gets there. Open the ones whose titles fit a