Summary
Coordinate with UX to define, approve, and implement the final UI/UX for WBS Deploy Setup, based on the tool’s existing three-state workflow.

Background
Following guidance from Leif, we began moving from the previously reviewed layout (single-column setup that becomes two columns with live status) toward a tab-based interface. The proposed direction reflects the tool’s current three states: configuration, launch/progress, and completion.

This ticket is about converging on a final UX decision with design review, not locking in any one layout prematurely. We already have useful reference artifacts (last year’s reviewed draft and a current tab-based draft), but both are inputs only and fully open to direction from UX.

The tool’s current functional scope has the following capabilities, requirements, and provisions and are important considerations in whatever design we settle upon:

• Install Git, Docker, and clone the most current release of the wikibase-release-pipeline repository to the server
• Collect configuration equivalent to .env values used in manual setup (see wikibase-release-pipeline/deploy/template.env).
• Guide domain input for Wikibase and Query Service, including validation that domains resolve to the target server.
• Show live launch progress/log output after save while the services boot which can take 2-10 mins depending on the server speed.
• On completion, return service links and generated credentials/settings, and clearly communicate that this data is ephemeral and removed after the post-setup window.

Scope
Work with UX to schedule and complete review of the target interaction model for this setup flow. Review can happen using working prototypes (live and/or screenshots) from current drafts, or UX can provide an alternative target directly. After a UX direction is agreed, implement that UI in the setup tool and prepare it for review.

Acceptance Criteria / Definition of Done

1. UX review has been completed and a clear target interaction model has been agreed for the setup flow (tab-based or an approved alternative).
2. The selected design explicitly supports all current tool states and capabilities:
   • configuration input and guidance
   • domain validation feedback
   • launch/progress visibility
   • completion output with links + ephemeral credential messaging
3. Implementation of the agreed design is completed in the setup tool.
4. Updated UI is shared for review with UX/stakeholders and feedback is incorporated.
5. Working code has passed PR review and been merged.