Disable inherited GrumPHP autoload validation for fixture extensions

[Copilot]

The php: 8.2 TYPO3: 13 Actions job was failing in GrumPHP’s composer_validate_autoload task. The failure came from functional test fixture classes under Tests/Functional/Fixtures/Extensions/blog_example, which are intentionally not part of this extension’s PSR-4 autoload mapping.

• Root cause

  • grumphp.yml imports pluswerk/grumphp-config, which enables composer_validate_autoload by default.
  • That task validates the repository against the extension’s Composer autoload rules and flags the fixture extension classes as violations.

• Change

  • Add a local override in grumphp.yml to disable only the inherited composer_validate_autoload task.
  • Keep the rest of the shared GrumPHP configuration unchanged.

• Why this scope

  • The failing classes live in functional test fixtures, not in the extension’s production autoload tree.
  • This avoids changing fixture namespaces or broader lint behavior for unrelated tasks.

grumphp:
  tasks:
    composer_validate_autoload:
      metadata:
        enabled: false