fix(ci): do not cancel-in-progress on main pushes (#5395)

Main and schedule/dispatch runs share one concurrency group via github.ref
when there is no pull_request.number. cancel-in-progress: true then killed
prior main CI before it could fail, which is how v0.9.8 assertion
regressions shipped (#5383). Keep cancel-in-progress only for pull_request
events so superseded PR heads still cancel; apply the same fix to ohos.yml
which used the identical group pattern.

Agent-assisted change.

Co-authored-by: Cursor Agent <cursoragent@cursor.com>
Co-authored-by: Hunter Bown <Hmbown@users.noreply.github.com>

Author: Hmbown

.github/workflows/ci.yml

@@ -19,7 +19,10 @@ permissions:
 
 concurrency:
   group: ci-${{ github.event.pull_request.number || github.ref }}
-  cancel-in-progress: true
+  # PRs: cancel superseded head runs. Push/schedule/dispatch on main must not
+  # cancel each other — they share github.ref with no pull_request.number, and
+  # canceling mid-run hid assertion failures that shipped in v0.9.8 (#5383).
+  cancel-in-progress: ${{ github.event_name == 'pull_request' }}
 
 env:
   CARGO_TERM_COLOR: always

.github/workflows/ohos.yml

@@ -30,7 +30,8 @@ permissions:
 
 concurrency:
   group: ohos-${{ github.event.pull_request.number || github.ref }}
-  cancel-in-progress: true
+  # Same as ci.yml: cancel superseded PR heads only; never cancel main pushes.
+  cancel-in-progress: ${{ github.event_name == 'pull_request' }}
 
 env:
   CARGO_TERM_COLOR: always