extension fix rejects extensions inside a Git project while project fix accepts them #1530

Shopware Version

6.7.13.1

Shopware CLI Version

0.18.3

PHP Version

8.5.10

Operating System

macOS 26.5.2

CLI Command

shopware-cli extension fix --only symfony-xml

Actual behaviour

During my recent validation tour, validation suggested running extension fix --only symfony-xml. The fix then failed because the extension directory itself had no .git, even though the extension was inside the Shopware project's Git repository. Re-running with --allow-non-git worked.

Later, project fix --only symfony-xml from the same nested extension context succeeded because project fix uses the discovered project-root .git.

This creates inconsistent Git-safety behavior, and the validation fix hint leads to a command that can immediately fail without explaining the additional requirement.

Expected behaviour

Fix guidance should lead to an executable command for the current project context.

extension fix and project fix should have a clear, consistent Git-safety model. If extension fix intentionally requires an extension-local Git repository, the suggested fix guidance should explain that requirement and how to proceed safely.

Relevant log/output

The exact stderr was not retained in the tour notes.

Observed flow:

`extension validate` → suggests: `extension fix --only symfony-xml`

`extension fix --only symfony-xml` → fails because extension has no local `.git`

`extension fix --only symfony-xml --allow-non-git` → succeeds

`project fix --only symfony-xml` → succeeds using the containing project Git repository