Problem

There are 4 workflows that trigger on issue events, overlapping in scope and sometimes conflicting:

1. Qwen Triage (qwen-triage.yml) — issues: opened
2. Qwen Automated Issue Triage (qwen-automated-issue-triage.yml) — issues: opened/reopened
3. Qwen Scheduled Issue Triage (qwen-scheduled-issue-triage.yml) — hourly cron
4. Qwen Issue Follow-up Bot (qwen-issue-followup-bot.yml) — issues: opened + every 6h

When an issue is opened, multiple workflows fire simultaneously. They race on labels and comments, and Qwen Triage frequently gets cancelled mid-execution due to concurrency conflicts (e.g., Follow-up Bot's comment triggers a new event).

Proposed Direction

Consolidate into at most 2 non-conflicting workflows:

• Option A: One unified workflow (Qwen Triage) handles everything — classification, labeling, related issue linking, missing info requests. Retire the others.
• Option B: Split by responsibility — "classify & label" (immediate, on open) vs "community engagement" (scheduled only, no opened trigger). Avoid concurrent execution on the same issue.

Context

Discovered while fixing #4785. The immediate fix (making Qwen Triage use /triage skill invocation) is separate from this consolidation work.