Add pre-action screenshot capture for action validation in debug mode

[mdshakib007]

PR Type

REFECTOR

PR Checklist

• Tests for the changes have been added / updated.
• Documentation comments have been added / updated.
• A changelog entry has been made.
• Version number has been updated.
• Required modules have been added to respective "requirements*.txt" files.
• Relevant Test Cases added to this description (below).
• (Team) Label with affected action categories and semver status.

Overview

Add pre-action screenshot capture for action validation in debug mode.
basically it will help ZAI to validate previous and next screenshot to compare when run

Test Cases

• TEST-0000

[riz-hossain]

🔎 ZeuZ PR Review

Open the full report in ZeuZ: Review findings and apply suggestions

Overview	Value
Agents	✅ 4 completed
Suggestions	💡 2

Agent breakdown

→ General Review

Status: ✅ Completed
Suggestions: 1 suggestion

The change is directionally good, but the pre-action capture is triggered too early relative to existing pre-action waits, which can make the BEFORE screenshot reflect the wrong UI state.

→ Security Review

Status: ✅ Completed
Suggestions: 0 suggestions

No security issues found in this PR diff. The change is limited to debug-mode pre-action screenshot capture and does not introduce new auth, injection, or secret-handling concerns in the reviewed code paths.

→ Performance Review

Status: ✅ Completed
Suggestions: 0 suggestions

No performance regressions stand out in this PR diff. The pre-action capture is scoped to debug mode and reuses the existing screenshot pipeline without introducing new query, cache, or unbounded-memory patterns.

→ Testing Review

Status: ✅ Completed
Suggestions: 1 suggestion

The PR adds a new pre-action screenshot path, but it isn’t covered by regression tests. I recommend adding focused unit coverage for the debug-only pre-action branch and the immediate-capture behavior.

Open ZeuZ to inspect full findings, continue an agent conversation, or apply safe patch suggestions.