[Tool] CI Report email subject and run page lack a link back to the parent CI PIPELINE run

[eshishki]

Context

The CI Report workflow runs on: workflow_run after CI PIPELINE finishes. When CI PIPELINE has failing tests, CI Report's own report jobs (FE-REPORT, BE-REPORT, SQL-Tester-REPORT) surface those failures via fail_on_failure: true and the workflow ends in failure. GitHub then sends a "Some jobs were not successful" email with subject:

CI Report(#25918743758): Some jobs were not successful

Two problems make this awkward to act on:

1. The email subject is uninformative

The current run-name:

run-name: CI Report(#${{ github.event.workflow_run.id }})

contains only the parent run id. No PR number, no branch. The receiver cannot tell which PR is failing without opening the link.

2. The "View workflow run" button lands in the wrong run

The id in parens (25918743758) is the parent CI PIPELINE run. The email itself is sent by the CI Report run, which has a different id (e.g. 25921958765). GitHub's "View workflow run" button — which is part of the email template and cannot be customized — always links to the run that emitted the email, i.e. the CI Report run.

So clicking the email button takes the user to the CI Report run page, not to the parent run mentioned in the subject. From there, the parent run id is shown as plain text in the page title and there is no clickable way back to the parent — the user has to manually edit the URL.

Repro

1. Open a PR that triggers CI PIPELINE.
2. Let it finish with at least one failed test.
3. Receive an email titled CI Report(#<parent_id>): Some jobs were not successful.
4. Click "View workflow run" — lands in CI Report run, with no PR/branch context and no clickable path back to the parent.

Proposal

Two minimal changes in .github/workflows/ci-report.yml:

1. Update run-name so the email subject includes the PR number when available (same-repo PRs populate workflow_run.pull_requests[0]), falling back to the head branch for cross-fork PRs. Keep the parent run id in parens for reference.

2. From the INFO job, write a markdown link to $GITHUB_STEP_SUMMARY so the Summary tab of every CI Report run shows the parent run id, branch and HEAD SHA as a one-click link.

Together these mean:

• The email subject identifies the PR / branch directly.
• After clicking "View workflow run", the receiver sees a clickable link to the parent CI PIPELINE on the run's Summary tab without editing the URL.