fix(workbench): test_launch_positron skips (.positron-console not found) though Positron is installed

[samcofer]

VIP version

0.54

Affected area

Workbench tests

What happened?

test_ide_launch.py::test_launch_positron[chromium] skipped with:

Positron console element not found within timeout — selector may have changed or Positron may not be fully available (Locator.wait_for: Timeout 30000ms exceeded.
Call log:
  - waiting for locator(".positron-console") to be visible
)

Positron is installed and reachable on this deployment — test_ide_extensions.py::test_positron_extensions[chromium] PASSED in the same run — so the launch gate is producing a false negative rather than a genuine "not installed" result.

What did you expect to happen?

test_launch_positron should detect the launched Positron session and run (or fail with an accurate reason), not skip claiming Positron may not be available.

Steps to reproduce

vip verify --workbench-url https://pwb.demo.soleng.posit.it --interactive-auth

Notes

Likely the same .positron-console-visibility launch gate flagged in #390 — the console element is hidden when the Terminal tab is active even though Positron loaded successfully. A more resilient gate (e.g. the Console tab a.action-label[aria-label="Console"]) would avoid the spurious skip. Ref #390.

[ian-flores]

Cross-linking during triage: this is the Positron launch-gate false negative already scoped in the Launch gate section of #390 (.positron-console is hidden when the Terminal tab is active → spurious skip). #390 notes the Console-tab gate (a.action-label[aria-label="Console"]) must be reintroduced together with the git-ops readback fix, since the gate alone turns a graceful skip into a readback failure. Sibling: #478 (JupyterLab analog). Deliberately not filed under the #480 org epic — this is a correctness bug.

[ian-flores]

Investigated live on dev.current.posit.team (Positron-enabled). The fix is blocked on the deployment, not the test code:

1. The Positron console selectors have drifted on the current build — PositronSession.CONSOLE_TAB (a.action-label[aria-label="Console"]) and CONSOLE_PANEL (.positron-console) both match 0 elements; the bottom panel shows the Terminal and the Console view isn't open.
2. The only Console control is a button labelled "Start New Console Session". Clicking it opens the interpreter quickpick — which is empty (quickpick_options: []): dev.current's Positron has no R/Python interpreters available, so no console session can start and no console DOM ever renders ([class*=console] → 0 elements).

So test_launch_positron can't be validated on dev.current — Positron is installed but has no interpreters. To fix + validate this we need a Positron deployment with interpreters configured. Note the same drifted selectors also affect exec.py's Positron readback (positron_eval_r / git-ops), so this is really 'modernize Positron console selectors + open the console view' once a suitable deployment is available.

(Companion #478 JupyterLab launch-gate fix shipped in #494.)