[Epic]: IDE v4 polish — glitches & differences from SikuliX

[julienmerconsulting]

Summary

Following @RaiMan's ask in #375 — how to document, with minimum admin overhead, the glitches and differences vs SikuliX he encounters while using the new IDE day-to-day — this is the tracking Epic for the v4 IDE polish wave.

Each observation becomes a Bug sub-issue created directly from this Epic via the "Create sub-issue" action in the GitHub panel. The parent/child link is automatic — no manual attaching needed.

In scope

• One sub-issue per glitch / UI inconsistency / behavior difference vs SikuliX that's worth fixing.
• Sub-issues use the bug_report.yml template.
• Labels on subs: bug, ide-ui, modernization — applied at creation.
• Milestone on subs: OculiX 4.0.

Out of scope

• Modern Recorder polish — separate scope.
• API surface changes on Region / Screen / Pattern — handled separately.
• Visual Intelligence (ONNX) — different Epic.
• Reporter module.
• OCR / performance — dedicated threads ([Feature]: OCR perf — cap upscale to 0.8 on large search regions (full-screen findText ~2× faster, zero accuracy loss) #378 etc.).

Sub-issues checklist

Auto-populated by GitHub as sub-issues are created. No manual maintenance.

Target release

OculiX 4.0

Current status

Planning (rail set up, awaiting first observations).

Known risks / open questions

• Reporting cadence is voluntary — this Epic adapts to your pace.
• Some reported "glitches" may turn out to be intentional design choices in the new IDE → quick discussion per sub before "fix" vs "by design / close".
• Triage debt risk if reports land faster than they're picked up — accepted trade-off.

Success criteria

• Every observation closes with: (a) a fix PR before v4 ships, OR (b) explicit "wontfix / by design" with reasoning.
• Zero open glitch sub-issues at v4 release time.
• v4 release notes acknowledge @RaiMan's contribution to the polish wave.

---

@RaiMan — your rail is here 🦎

Following your ask in #375. Workflow, minimum overhead as you wanted:

1. When you encounter a glitch in the new IDE, scroll down on this Epic to the "Sub-issues" panel → click "Create sub-issue" → pick the Bug template.
2. Just a clear title + short description + screenshot if it's visual. GitHub auto-links to this parent, you don't have to think about it.
3. The sub appears in the panel above with its status. Zero maintenance from either side.

No ping needed — this Epic is my watch. And given your daily use of the new IDE for your own work, there should be plenty to report 😏. Don't hold back — even small "this used to feel snappier" notes count. That's exactly the point of the v4 polish wave.

Thanks in advance.