F-036 (P8) — `.slnx`/CI drift after Azure→GitHub Actions migration

[LarsLaskowski]

Severity: 🟡 · Criterion: K12 / Build-CI · Phase: P8 · Status (review): 🆕

File(s): DockerUpdateGuard.slnx:6; .github/workflows/ci.yml, .github/workflows/release.yml (not in .slnx); deleted: azure-pipelines.yml (commit fc81f4f)

Finding

The CI/CD migration (fc81f4f) removed azure-pipelines.yml and replaced it with GitHub Actions workflows, but did not update the solution: DockerUpdateGuard.slnx:6 still references <File Path="azure-pipelines.yml" /> (a missing entry in Visual Studio/dotnet sln). The new workflows ci.yml/release.yml are not listed in the .slnx (the "Copilot" folder lists only the two instruction files). Additionally, the review matrix listed the deleted azure-pipelines.yml and omitted the workflows (see the matrix note above).

Impact

Dangling reference in the solution; the actually effective pipeline is not part of the solution view. Purely structural, no runtime error.

Recommendation

In .slnx, remove the azure-pipelines.yml entry and add .github/workflows/ci.yml + release.yml (e.g. under "Solution items").

---

_{Auto-generated from the repository code review. Source of truth: docs/review/findings.md → F-036 (P8), branch review/review-analysis-plan.}