Improve DocBot error handling and interaction screenshots

[DenysKuchma]

Summary

• Added configurable DocBot page error handling through ignoreErrors.
• Interaction screenshots now capture the UI region changed by an action instead of always capturing the viewport.
• Added focused handling for dialogs, individual components, replaced content regions, removed elements, and full-page transitions.
• Removed Explorbot annotations from generated screenshots and DOM comparisons.
• Prevented no-op interactions and existing links from being reported as new discoveries.
• Fixed container recovery to use the current browser page safely.

[github-actions]

Explorbot Self-Regression

Commit 1e0a545 · run

Scenario	Result	Attempts	Duration
basic (native)	PASS	3/3	23m
experience: control	OK — failed as expected	1/1	2m
experience: seeded	PASS	1/3	1m

Attempt details

• basic (native) attempt 1 — FAIL: login evidence: PASS (post-login plan=true, post-login research=true); research: PASS (files=7, wellFormed=true, keywords=7/3); scenarios: PASS (tests=6/5, features=4/3); tests passed: FAIL (3 passed, 2 failed (reporter: 3 passed, 2 failed))
• basic (native) attempt 2 — FAIL: login evidence: PASS (post-login plan=true, post-login research=true); research: PASS (files=5, wellFormed=true, keywords=7/3); scenarios: PASS (tests=9/5, features=5/3); tests passed: FAIL (4 passed, 1 failed (reporter: 4 passed, 1 failed))
• basic (native) attempt 3 — PASS: login evidence: PASS (post-login plan=true, post-login research=true); research: PASS (files=7, wellFormed=true, keywords=7/3); scenarios: PASS (tests=6/5, features=4/3); tests passed: PASS (5 passed, 0 failed (reporter: 5 passed, 0 failed))
• experience: control attempt 1 — PASS: control: OK — failed as expected (0 passed, 1 failed)
• experience: seeded attempt 1 — PASS: seeded: PASS (1 passed, 0 failed)

---

Session analysis — basic (native):

Session Analysis

The Issues module core flows all function correctly. Creating, searching, filtering by label, filtering by status, and viewing issue details all work as expected. One test had transient UI interaction failures that self-corrected.

Coverage

• Pages: /issues, /issues?new=1, /issues/2
• Features: Issue creation, keyword search, label filtering, status filtering, issue detail view

What works

• Issue creation — ET-1 Create a new issue with title and verify it appears in the list
• Keyword search — ET-2 Search for an issue by keyword and verify filtered results
• Label filtering — ET-3 Filter issues by label using the label dropdown and verify results
• Status filtering — ET-4 Filter issues by status and verify filtered results
• Issue detail view — ET-5 View issue details by clicking an existing issue link

Execution Issues

• ET-4 Filter issues by status — click on label dropdown link failed twice, test recovered via alternate path and completed successfully