docs: plan for #307 — publish to Connect from Workbench

[posit-vip-triage]

Closes #307

This plan proposes adding cross-product scenarios that verify publishing from a Workbench session to Connect using both the terminal (rsconnect-python) and the Posit Publisher extension UI. The current VIP test suite deploys content to Connect via the Connect API, which validates Connect's publishing pipeline but skips the user-facing workflow most customers exercise during UAT.

The plan outlines:

• Two new Gherkin scenarios in src/vip_tests/workbench/test_publish_to_connect.feature
• A reusable Python Shiny test bundle under src/vip_tests/_bundles/
• Dependencies on two separate primitives (in-session command execution and IDE extension installation) tracked in other issues
• Cleanup via connect_client regardless of which deployment path was used

Merging this PR will trigger an implementation PR — comment to iterate on the plan first.

Plan

The full plan is in thoughts/shared/plans/2026-05-29-issue-307-workbench-to-connect-publishing.md.

Key points

• Architecture: New cross-product test with both @workbench and @connect markers
• Components: Feature file, step definitions, Python Shiny bundle, validation demo
• Verification: Collected via --categories workbench, runnable against live Workbench + Connect
• Dependencies: Two primitives tracked separately (in-session execution, IDE extension install)
• Out of scope: Implementing the primitives, R Shiny from Workbench, failure scenarios

Generated by Triage open issues on posit-dev/vip for issue #307 · ● 6.4M · ◷