Make Docbot state diagram compact

[DenysKuchma]

Make Docbot state diagram more compact

[github-actions]

Explorbot Self-Regression

Commit 9220007 · run

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

Attempt details

• basic (native) attempt 1 — PASS: login evidence: PASS (post-login plan=true, post-login research=true); research: PASS (files=6, 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 issue tracking feature was exercised through creation, filtering (by status and label), search, and detail viewing. Core flows work—issues can be created and all filtering/search mechanisms correctly narrow results. The standout problem is automation reliability: multiple retries were needed to complete basic UI interactions, though the product ultimately behaves correctly.

Coverage

• Pages: /issues, /issues/{id}
• Features: Create issue, filter by status, filter by label, search issues, view issue details

What works

• Issue creation — ET-1 Create new issue with title and description
• Status filtering — ET-2 Filter issues by status
• Label filtering — ET-3 Filter issues by label
• Search — ET-4 Search for specific issue
• View issue details — ET-5 View issue details

Execution Issues

• ET-1 Create new issue with title and description — required multiple click retries on dialog submit button before succeeding