🐛 Remove concurrency group from coverage suite

[clubanderson]

Concurrency group blocked manual triggers behind scheduled runs. 2-hour schedule with 25-min runtime won't overlap naturally.

[kubestellar-prow]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign clubanderson for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[netlify]

✅ Deploy Preview for kubestellarconsole canceled.

Name	Link
🔨 Latest commit	61ab3aa
🔍 Latest deploy log	https://app.netlify.com/projects/kubestellarconsole/deploys/69cd401bf0820e0008cab30e

[github-actions]

Thank you for your contribution! Your PR has been merged.

Check out what's new:

• KubeStellar Console — Live multi-cluster dashboard
• Marketplace — Community extensions
• Knowledge Base — Troubleshooting and how-tos

Stay connected: Slack #kubestellar-dev | Multi-Cluster Survey

[github-actions]

👋 Hey @clubanderson — thanks for opening this PR!

🤖 This project is developed exclusively using AI coding assistants.

Please do not attempt to code anything for this project manually.
All contributions should be authored using an AI coding tool such as:

• Claude Code (Opus 4.5 / 4.6) — recommended
• GitHub Copilot
• Cursor
• Other AI coding assistants

This ensures consistency in code style, architecture patterns, test coverage,
and commit quality across the entire codebase.

---

This is an automated message.

[Copilot]

Pull request overview

This PR updates the GitHub Actions coverage workflow to avoid manual workflow_dispatch runs being serialized behind scheduled runs by removing the workflow-level concurrency group.

Changes:

• Removed the concurrency group from the coverage workflow.
• Added a comment explaining why a concurrency group is no longer used.

[Copilot]

Removing the workflow-level concurrency means multiple runs (especially concurrent workflow_dispatch + schedule) can execute in parallel and race on the shared side effect of updating the same coverage badge gist. That can lead to the badge showing an older/incorrect percentage depending on which run finishes last.

Consider restoring concurrency in a way that unblocks manual runs without allowing conflicting badge updates (e.g., move concurrency to a dedicated badge-update job, or gate the gist update to scheduled runs / a single concurrency group just for the update).

Suggested change

	# No concurrency group — 2-hour schedule won't overlap with 25-min runs
	concurrency:
	group: coverage-hourly-badge
	cancel-in-progress: false

[clubanderson]

🔄 Auto-Applying Copilot Code Review

Copilot code review found 1 code suggestion(s) and 0 general comment(s).

@copilot Please apply all of the following code review suggestions:

• .github/workflows/coverage-hourly.yml (line 11): concurrency: group: coverage-hourly-badge cancel-in-progress: false

Push all fixes in a single commit. Run cd web && npm run build && npm run lint before committing.

---

Auto-generated by copilot-review-apply workflow.