ops-nuke-cicd

# NUKE CI/CD ## Quick Reference - Start from existing `nuke/Build.cs` targets and preserve output contracts before refactoring. - Keep target graph intent explicit: use `DependsOn` for hard prerequisites, `After` for ordering, `Triggers` for composed flows, and `OnlyWhenDynamic` for runtime gates. - Use this skill for pipeline orchestration and build contracts, not for application-service refactors or NUnit fixture internals. - Separate fast local feedback (`build + filtered tests`) from full CI validation (`unit + api + db + merged coverage`). - Use the iterative loop `code -> build -> run tests -> fix -> repeat` for both feature work and test hardening. - Run preflight checks before expensive targets: SDK version, Docker availability (when required), and expected file paths. - Use wrapper commands (when available): `./build.sh BuildAll`, `./build.sh LocalUnitTest`, `./build.sh ApiTest`, `./build.sh TestAll`. - Use category filters intentionally, including exclusion filter patterns such as `TestCategory!=ComponentTests&TestCategory!=DbTests&TestCategory!=ApiTest`. - Keep `UnitTest` scoped to non-API categories and create a dedicated `ApiTest` target for `TestCategory=ApiTest`. - Keep `TestAll` composed from `UnitTest + ApiTest (+ DbTest)` and coverage merge. - When migrating from legacy docker-compose/SpecFlow orchestration, decommission compose-first test flow and keep pipeline focused on NUnit API categories. - Avoid running parallel `dotnet test` invocations against the ...