A team runs three agent validation jobs in parallel: one for API changes, one for UI changes, and one for workflow changes. Each job must run in its own matrix copy, upload separate evidence, and avoid cancelling the other agent validations when one scope fails. Which option completes the workflow?

The correct option ensures each validation job runs independently and uploads distinct evidence. Setting fail-fast: false for the strategy is crucial because it prevents GitHub Actions from canceling all in-progress jobs if one matrix job fails. This directly addresses the requirement to "avoid cancelling the other agent validations when one scope fails." The uses: actions/upload-artifact@v4 line correctly specifies the action for uploading artifacts. Finally, path: reports/${{ matrix.agentscope }}/ correctly defines the local directory from which artifacts will be uploaded, ensuring separate evidence for each agentscope. Incorrect options: max-parallel is not a valid strategy key for controlling failure behavior. run is for executing commands, not specifying actions. artifact is not a valid parameter for actions/upload-artifact@v4. concurrency manages job concurrency, not failure behavior. upload-path is not a valid parameter for actions/upload-artifact@v4. cancel-in-progress is a concurrency setting, not a strategy setting for individual job failure. with is used to pass inputs to an action, not to specify the action itself. name is for the artifact's name, not the source path.