fix(release-qa): deep-link Slack counts to bucket sections via user-content- anchors

[nollymar]

Closes #35841

Problem

Each bucket count in the release QA Slack notification links to the workflow run summary with a per-bucket fragment (e.g. #qa-missing), but clicking it lands at the top of the run page rather than the bucket section.

Example: https://github.com/dotCMS/core/actions/runs/26459945291#qa-missing

Root cause

GitHub's markdown sanitizer prefixes anchor ids in the job summary with user-content-. The summary declares <a id="qa-missing"> but the rendered element is id="user-content-qa-missing", so #qa-missing matches nothing.

Fix

Point the Slack count links at #user-content-<anchor>. The markdown anchor markers are unchanged — GitHub adds the prefix on render. One-line change in slackCounts plus the corresponding test assertions.

Notes

• Follow-up to merged PR feat(release): compact Slack QA section + @-mention flagged-PR authors #35815 (the original branch was deleted on merge, hence a new branch/PR).
• Tests: 37/37 pass.

🤖 Generated with Claude Code

[claude]

Claude finished @nollymar's task in 39s —— View job

---

Rollback safety analysis — ✅ Safe to Rollback

• Read docs/core/ROLLBACK_UNSAFE_CATEGORIES.md
• Reviewed PR diff against every unsafe category
• Applied AI: Safe To Rollback label

Scope of changes

• .github/scripts/release-qa-status/src/format.ts — prefix user-content- on Slack count anchor links
• .github/scripts/release-qa-status/src/format.test.ts — corresponding test assertions

Analysis

These changes only affect the CI-side Slack notification formatter for the release QA status job. The diff does not touch any category in the reference document:

Category	Match?
C-1 Structural data model change	No
C-2 Elasticsearch mapping change	No
C-3 contentlet_as_json model version bump	No
C-4 DROP TABLE / DROP COLUMN	No
H-1 One-way data migration	No
H-2 RENAME TABLE / COLUMN	No
H-3 PK / unique constraint restructuring	No
H-4 New ContentType field type	No
H-5 Storage provider change	No
H-6 DROP PROCEDURE / FUNCTION	No
H-7 NOT NULL column without default	No
M-1 Non-broadening column type change	No
M-2 Push publishing bundle format change	No
M-3 REST / GraphQL API contract change	No
M-4 OSGi public interface change	No

No runonce tasks, no SQL, no schema or mapping changes, no runtime Java/REST surface touched. Rolling back to N-1 has no application impact — the previous version of the script would simply emit the previous (broken) anchor links in the Slack message, which is the prior state.
· Branch fix/release-qa-anchor-deeplink