[AAASM-3511] 🔧 (ci): Run SonarCloud analysis on dashboard PRs

[Chisanan232]

Description

The sonar job ("SonarCloud analysis") in .github/workflows/ci.yml was gated
to run only on push events or PRs carrying the manual run-coverage label.
As a result, dashboard-only PRs received no SonarCloud report — the dashboard
JS changes were never analyzed unless someone remembered to apply the label.

This PR adds needs.changes.outputs.dashboard == 'true' to the job's if:
condition so dashboard PRs are analyzed automatically:

-    if: ${{ !cancelled() && needs.changes.result == 'success' && github.actor != 'dependabot[bot]' && (github.event_name == 'push' || contains(github.event.pull_request.labels.*.name, 'run-coverage')) }}
+    if: ${{ !cancelled() && needs.changes.result == 'success' && github.actor != 'dependabot[bot]' && (github.event_name == 'push' || contains(github.event.pull_request.labels.*.name, 'run-coverage') || needs.changes.outputs.dashboard == 'true') }}

dashboard is a real output of the changes job (the dorny/paths-filter
dashboard filter). The sonar job already declares needs: [changes, coverage, dashboard-test] and backfills the last successful master Rust LCOV when the
coverage producer is skipped, so on a dashboard PR (coverage skipped,
dashboard-test runs) it scans with just the dashboard JS LCOV — no extra test
runs required.

Type of Change

• 🔧 Configuration / CI change

Breaking Changes

• No

Related Issues

• Related Jira ticket: AAASM-3511

Testing

• No tests required (explain why)

CI-config-only change to a single job-level if: gate. Validated locally with
actionlint .github/workflows/ci.yml (clean, no findings) and a yaml.safe_load
parse check. The fix takes effect on the next dashboard PR's CI run.

Checklist

• Code follows project style guidelines (cargo fmt, cargo clippy)
• Self-review of the diff completed
• Documentation updated if behaviour changed
• All CI checks passing
• Commits are small and follow the Gitmoji convention

🤖 Generated with Claude Code

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

[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

[Chisanan232]

🔎 Review (Claude Code) — ready for approval

CI: ✅ All green — 37 checks pass, 0 failures.

Scope vs AAASM-3511: ✅ Exactly addresses the root cause. The sonar job ("SonarCloud analysis") was gated github.event_name == 'push' || contains(labels, 'run-coverage'), so dashboard PRs got no SonarCloud report. The one-line change adds || needs.changes.outputs.dashboard == 'true' so dashboard PRs are analyzed automatically — and needs.changes.outputs.dashboard is a real output of the changes job (dorny/paths-filter). The job already backfills the Rust LCOV when coverage is skipped, so a dashboard PR scans cleanly with just the dashboard JS coverage; non-dashboard, non-labelled PRs are unaffected (no extra CI cost). actionlint clean, YAML valid, +1/-1.

Verdict: Minimal, correct, green. Ready to approve & merge. Once merged, subsequent dashboard PRs (incl. #1186/#1187/#1188) will get a SonarCloud check on re-run.