[njoubert-cleverage]

Description

Fixes #372.

• A task code referenced by the outputs / error_outputs of a task or by the entry_point / end_point of a process, and that is not a task of the process, now throws an InvalidProcessConfigurationException naming the process, the task and the key holding the reference (e.g. Unknown task 'missing' in the 'outputs' of the task 'read' (from process: app.import)), instead of a MissingTaskConfigurationException (No task configuration with code : missing).
• ProcessConfigurationRegistry::getProcessConfigurations() leaves out a process whose configuration is not valid, with an error log on the cleverage_process channel (new optional logger argument), instead of making every listing fail (cleverage:process:list, lists of the UI). Getting or executing this process by its code still throws.

Rejecting such configurations when the container is compiled is left to a separate ticket (deprecation in 5.x, error in v6). cleverage:ui-process:purge-logs can still fail on an invalid process that has executions recorded: ui-process-bundle ticket to follow.

Requirements

• Documentation updates
  • Reference
  • Cookbooks
  • Changelog
• Unit tests

Breaking changes

None: the invalid processes already failed when executed, they no longer make the listings fail. The exception thrown for an unknown task reference is now an InvalidProcessConfigurationException instead of a MissingTaskConfigurationException (both extend \UnexpectedValueException and implement ProcessExceptionInterface).

🤖 Generated with Claude Code