Add interactive project upgrade wizard

[Soner (shyim)]

Summary

Implements an interactive upgrade wizard for Shopware projects that guides users through the upgrade process with a TUI interface. This mirrors the behavior of the shopware/web-installer but runs from the command line.

Key Changes

New Packages

• internal/projectupgrade/ - Core upgrade logic package containing:

  • wizard.go - Interactive TUI-based upgrade wizard using Bubble Tea
  • composer.go - Composer.json rewriting for target versions
  • plugins.go - Plugin compatibility resolution and constraint bumping
  • registry.go - Package registry abstraction for version lookups
  • releases.go - Version filtering and selection logic
  • Comprehensive test coverage for all modules

• cmd/project/project_upgrade.go - New project upgrade command with:

  • Interactive wizard mode (default when TTY available)
  • Headless mode for CI/CD pipelines
  • Git working tree validation
  • Composer-managed plugin verification

Upgrade Workflow

The wizard guides users through:

1. Welcome screen - Confirm upgrade intent
2. Version selection - Choose target Shopware version
3. Compatibility check - Query Shopware Account API for extension compatibility
4. Review - Confirm selected version and changes
5. Execution - Run upgrade tasks with live progress:
   • Back up composer.json
   • Clean up stale recipe files
   • Resolve incompatible custom plugins
   • Rewrite composer.json
   • Run composer update --with-all-dependencies
   • Execute bin/console system:update:prepare
   • Execute bin/console system:update:finish

Plugin Resolution

• Detects incompatible custom plugins by checking Shopware package constraints
• Attempts to find compatible versions via registry (Packagist or Shopware Store)
• Bumps constraints to compatible versions when available
• Removes plugins with no compatible release
• Restores composer.json on failure

Registry System

• CombinedRegistry routes lookups to appropriate backend (Store vs Packagist)
• PackagistRegistry queries repo.packagist.org with minified format support
• Extensible interface for custom registry implementations

Supporting Changes

• Enhanced internal/git/ with IsRepository() and WorkingTreeStatus() functions
• Extended internal/flexmigrator/ with CleanupByHash() for recipe file cleanup
• Version filtering logic matching web-installer behavior

Implementation Details

• Uses Bubble Tea for interactive TUI with spinner animations
• Streams subprocess output (composer, console commands) to live log view
• Graceful error handling with composer.json restoration on failure
• Context-based cancellation support for long-running operations
• Comprehensive test coverage including wizard state machine and plugin resolution

https://claude.ai/code/session_01F4pXpGEuJGsxpfTudpnoLo

[somethings (lasomethingsomething)]

Next step: prep this for team demo

[Dennis Mader (Weltraumakustik)]

Arnold Stoba (@arnoldstoba) would you please do a quick review from UX Engineering perspective on this? Maybe there's additional ideas or optimizations

[Arnold Stoba (arnoldstoba)]

General

• There is a general height problem in this wizard that imo we have to address. Maybe we can work on a smaller version of the elephant header part, just display it on the first step or just remove it completely for these kind of larger wizard/config steps, but parts of the TUI are cut off even on a 1920x1080 size terminal, would be even worse on a smaller laptop screen.
• This height problem is also especially visible in the last step, the actual upgrade. Due to the nature of the TUI the logs are cut off / pushing up the height of the TUI content. This leads to not being able to read some of the logs at all. Idk what exactly is possible here but potentially we could display them in some sort of scroll container? I'm not sure what the best option would be here, @shopware/product-dx.

Visuals

• The horizontal dividers could all be full width for consistency, this seems cleaner to me but it's an optional visual-only change.
• We could also improve the general width of the container in order to avoid all of these content wrapping issues. Might lessen the readability slightly and could clash with reusable components used in other parts of the CLI.
• The terminal bullet points are always wrapping onto the beginning of the next line whenever the content is too long. I think this should be pretty easily solvable and would improve readability and visual cleanliness. Basic example of how this could be abstracted into a go bullet.go TUI component which then could be reused everywhere (same could be done for the key-value pair UI e.g. "Version: 6.5.0.0" etc.):

package tui

import "charm.land/lipgloss/v2"

// bulletMarker is the standard bullet prefix: 2 spaces + bullet + space = 4
// display columns. The leading spaces live inside the marker so the hanging
// indent column is derived directly from the marker width.
const bulletMarker = "  • "

// HangingIndent renders body to the right of marker so that when body wraps to
// the given total width, continuation lines align under the body text instead
// of the marker. marker appears as-is on the first line; continuation lines are
// indented by marker's display width. body may carry its own ANSI styling and
// explicit newlines — only its Width is set, so the styling is preserved.
func HangingIndent(marker, body string, width int) string {
	markerW := lipgloss.Width(marker)
	bodyW := width - markerW
	if bodyW < 1 {
		// No room to wrap; join unwrapped rather than pass a negative Width.
		return lipgloss.JoinHorizontal(lipgloss.Top, marker, body)
	}
	wrapped := lipgloss.NewStyle().Width(bodyW).Render(body)
	return lipgloss.JoinHorizontal(lipgloss.Top, marker, wrapped)
}

// Bullet renders "  • text" (dim marker, LabelStyle text) with a hanging indent
// so wrapped text aligns under the first line instead of the bullet.
func Bullet(text string, width int) string {
	return HangingIndent(DimStyle.Render(bulletMarker), LabelStyle.Render(text), width)
}

// BulletRaw is like Bullet but leaves text unstyled, so callers can pass an
// already-styled or mixed-style body (e.g. a label followed by a dim detail).
func BulletRaw(text string, width int) string {
	return HangingIndent(DimStyle.Render(bulletMarker), text, width)
}

• For better separation we could also display the keyboard shortcuts below the "card". This would make it a bit more visually clear what the most important actions of the current step are, since then they would be the last element placed at the bottom of the card.

• In general the steps/flow make sense to me and are clear to understand. It's easy to select all the options and all necessary information is provided. Good work @shopware/product-dx.

I'm happy to help out with details or additional feedback, just let me know 👍🏻