pr-agent: a bot comment no longer cancels a review

[bong-water-water-bong]

On #62, the Docs7 bot's comment started an issue_comment run. Its job was skipped, but the workflow-level concurrency group still cancelled the running review (run 36114466708).

Concurrency now sits on the job, so only runs that actually execute take the group.

🤖 Generated with Claude Code

[github-actions]

PR Reviewer Guide 🔍

Here are some key observations to aid the review process:

🎫 Ticket compliance analysis 🔶 62 - Partially compliant Compliant requirements: Fix for NPU lane idle timeout issue implemented Hardware context now created per generate() call Context dropped at end of generate() and on exception paths Performance measurements and verification provided Documentation update noted in ticket description Non-compliant requirements: The follow-up items about npu-draft bench and 35B path not addressed in this PR Requires further human verification: Verification of performance claims on actual hardware Confirmation that xrt-smi shows no hardware contexts after fix

⏱️ Estimated effort to review: 2 🔵🔵⚪⚪⚪

🧪 No relevant tests

🔒 No security concerns identified

⚡ Recommended focus areas for review Concurrency Configuration Change The concurrency configuration has been moved from the workflow level to the job level in the GitHub Actions workflow. This change ensures that only jobs that actually execute will cancel other in-progress runs in the same concurrency group, rather than comments that skip jobs (like bot comments) cancelling the entire review run. This is a good change for workflow reliability. # on the job, not the workflow: a comment that skips the job (a bot's, say) must not cancel a review concurrency: group: pr-agent-${{ github.event.pull_request.number || github.event.issue.number }} cancel-in-progress: true