[thomasluizon]

Closes thomasluizon/orbit-tickets#1492

Pull requests now split domain mutation testing into domain-habit-freeze and domain-user-invariants, using the same file patterns and available-core concurrency as nightly runs. This keeps each domain shard within the existing mutation scope while retaining --since:origin/main on the PR path.

The change is confined to .github/workflows/mutation.yml. A shared YAML matrix replaces the event-specific JSON matrix so PR, scheduled, and manual runs use the same four jobs. The PR step reuses the nightly argument construction to pass each shard's quoted --mutate patterns and --concurrency from nproc. Application and infrastructure retain their job names and configured mutation scope. The 45-minute timeout and mutation thresholds stay unchanged.

External interface evidence

Restored the manifest's Stryker.NET 4.16.0 with dotnet tool restore and read its installed NuGet package metadata, which identifies source commit f9109e24c615a7030a3b33e5532c665c974e4ec5. Read the source at that exact commit before changing the workflow:

• ConfigBuilder loads file configuration before CLI options. CommandLineConfigReader replaces the mutate input with repeated CLI values, parses --since:origin/main, and accepts integer concurrency.
• MutantFilterFactory enables both file-pattern and since filters. BroadcastMutantFilter passes only remaining mutants to each subsequent filter, enforcing shard boundaries alongside diff selection. SinceMutantFilter retains Stryker's existing changed-source and changed-test behavior within that scope.

Test evidence

• dotnet build Orbit.slnx: exit 0, zero errors; existing package and obsolete-API warnings.
• dotnet test: exit 0; 7,150 passed, zero failed or skipped across analyzer, domain, application, and infrastructure suites.
• actionlint .github/workflows/mutation.yml: exit 0 before and after the change. The unchanged lint check does not detect missing PR shards; no existing workflow behavior test covers that defect.
• The matrix regression probe below exits 1 against the parent workflow with PR matrix is not shared with nightly, then exits 0 against the fixed workflow:

check='job = YAML.load(STDIN.read).fetch("jobs").fetch("mutation"); matrix = job.fetch("strategy").fetch("matrix").fetch("include"); abort "PR matrix is not shared with nightly" unless matrix.is_a?(Array); abort "Unexpected mutation jobs" unless matrix.map { |entry| entry["shard"] || entry["project"] } == %w[domain-habit-freeze domain-user-invariants application infrastructure]'
git show HEAD^:.github/workflows/mutation.yml | ruby -ryaml -e "$check"
ruby -ryaml -e "$check" < .github/workflows/mutation.yml

A temporary Ruby/Bash probe also parsed the workflow and executed its actual Stryker step bodies with argument capture for all four jobs under pull_request, schedule, and workflow_dispatch. All 12 checks passed, including literal shard glob arguments, PR-only since selection, explicit concurrency, empty application/infrastructure overrides, stable naming, and the 45-minute timeout. No permanent test file was added for this workflow-only change.

Mutation CI completion, the post-merge run for orbit-api#723, and propagation through #746 remain for the orchestrator to verify. No CI waiting or merge was performed by this worker.

Assumptions

• Use the existing nightly shard names on PRs instead of retaining a separate Mutation (domain) job; this preserves the naming convention and the application/infrastructure names while exposing both required domain shards.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[pullfrog]

✅ No new issues found.

Reviewed changes in .github/workflows/mutation.yml, including shard coverage, CLI argument construction, and event-specific execution.

• Shared matrix: Pull requests now use the same two domain shards as scheduled and manual runs, with application and infrastructure entries preserved.
• Scoped PR execution: Repeated, quoted --mutate arguments and explicit concurrency retain --since:origin/main; the domain patterns exactly partition the existing configured scope.
• Verification: All 12 event/job shell argument probes passed. Checked the cited Stryker source to confirm CLI override behavior and cumulative shard/since filtering. Full mutation runtime was not reproduced locally.

  ^{｜ View workflow run ｜ Using gpt-6.1-sol ｜ 𝕏}