[WRONG BRANCH] fix(issue-quality): include duplicate translated sections in area heuristics

[luvs01]

Motivation

• The area-label heuristics ignored appended English translations when the original issue body already contained the same template headings, because section extraction returned only the first matching heading section.

Description

• Add extractSections(body, heading) to return every matching markdown section for a heading and keep extractSection(body, heading) as a compatibility wrapper that returns the first match, preserving existing callers.
• Update bodyForAreaHeuristics to collect and join every semantic section returned by extractSections so appended translation text is considered alongside the source-language sections when running heuristics.
• Strengthen the regression test in .github/scripts/issue-quality.test.cjs to simulate the real workflow construction (source body plus appended translation) and assert that translation-derived heuristics (for example refresh token -> account-pool) are detected.
• Changes are limited to the issue-quality scripts and do not alter workflow permissions, triggers, or GitHub mutation boundaries. Files changed: .github/scripts/issue-quality.cjs, .github/scripts/issue-quality.test.cjs.

Testing

• Ran node --test .github/scripts/issue-quality.test.cjs and all tests passed (112 tests, 0 failures).
• Ran bun run typecheck which completed successfully.
• Ran git diff --check which reported no problems.
• Attempted bun run test; the full repository suite did not complete within the environment timeout so it was not finished, and bun run prepush was therefore not reached.

---

Codex Task

[coderabbitai]

Warning

Review limit reached

@luvs01, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 39 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: ef71975b-7cd3-419a-bc3d-dc51a8be129d

📥 Commits

Reviewing files that changed from the base of the PR and between 121f1ad and 3dadea4.

📒 Files selected for processing (2)

• .github/scripts/issue-quality.cjs
• .github/scripts/issue-quality.test.cjs

---

_{Comment @coderabbitai help to get the list of available commands.}

[github-actions]

✅ Deterministic PR hygiene checks passed.

[github-actions]

⏳ DRAFT

• wrong target branch (main); retarget to dev.

What to do

• Retarget this PR to dev — all contributions go to dev.

Its title has been prefixed with [WRONG BRANCH].
This pull request was already a draft. Its draft status will be preserved after every issue above is resolved.