ci: CI-unit-tests-asan-coverage creates a completion-only check-run (0 steps, instant duration)

[renecannao]

.github/workflows/CI-unit-tests-asan-coverage.yml calls LouisBrunner/checks-action only at the end, with no matching leading "create in_progress check-run" step and no check_id — unlike its correct sibling CI-unit-tests-tsan.yml. Every resulting check-run is stamped started_at == completed_at with zero steps, on success as well as failure.

Why it matters: on 2026-08-11/12 this shape caused a real, deterministic unit-test regression to be misdiagnosed twice as an infrastructure phantom. The actual job had full 40-minute logs; the check-run showed nothing. Anyone triaging from the checks UI is being actively misled.

Suggested fix: add the leading in_progress check-run step and pass check_id to the final call, mirroring CI-unit-tests-tsan.yml.

[coderabbitai]

🔗 Related PRs

#5726 - ci(asan-coverage): containerise unit-tests workflow + extract runner script [merged]
#5803 - fix(ci): prevent zombie IN_PROGRESS checks in CI-unit-tests-asan-coverage [merged]
#5891 - ci: harden TAP coverage uploads [merged]
#6003 - ci: stop hashFiles() from failing jobs whose tests passed [merged]
#6060 - ci: fetch LFS objects in sanitizer workflows [merged]

---

📝 Issue Planner

_{Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.}

• Create Plan

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!