Report each command a batch ran, with its status

[DavertMik]

The bug

form() sends many commands and gets back one pass/fail. A command that errors erases the evidence that everything before it worked.

Session OtherYappiestIndigo973 (trace 33fe2b45ba23ed568a2dcc0769deacb3):

I.amOnPage('/projects/.../suite/28989496')                  // ran, navigated
I.waitForElement('Description Persistence Suite Other…')    // a title, not a locator — 30s timeout

The tool reported only Form execution FAILED!. Pilot concluded the reload never happened, rejected finish() three times, and failed a scenario whose own verifications had passed.

The fix

attachStepLogger already listened to both step.passed and step.failed, so it always saw which commands ran and which one broke — the list was just discarded on the error path.

The executors own the information; the tools only read it:

• Action.executedSteps — {command, success, error?}, the shape click() already returns.
• Navigator.executedSteps — accumulated across the attempts it drives, alongside the existing lastFailureReason.
• form() / interact() — read those and report, in the message (the channel that reaches the tester conversation and Pilot's session log) and as structured attempts, which pilot's formatActions already reads.

Form execution FAILED! element (…) still not present on page after 30 sec
  OK I.amOnPage('/projects/.../suite/28989496')
  FAILED I.waitForElement('Description Persistence Suite Other…')

No prompt changes: with the commands enumerated, neither the Tester nor Pilot has to infer what ran.

ActionResult was considered as the carrier and rejected — it is a page-state snapshot, persisted and rebuilt via fromState(WebPageState), and on the failure path executeOnce throws before captureOnce() runs, so the only ActionResult available is the previous state object StateManager owns and reuses.

Verification

• tests/unit/executed-steps.test.ts — the failing command is recorded with success:false, nothing after it appears, and the report lists OK/FAILED plus how many never ran.
• bun test tests/unit/ tests/integration/ — 1193 pass, 1 skip. The one failure (remote > announces the run…) reproduces on clean main under the full suite and passes standalone: pre-existing ordering issue, unrelated.

🤖 Generated with Claude Code