feat(ci): Trunk Flaky Tests upload on the fast-path vitest job (per-PR volume)

[diegosouzapw]

Follow-up to #7175: the Trunk uploads were wired only into ci.yml (heavy gate — runs on the release PR), so the Flaky Tests dashboard would never accumulate per-PR volume. This adds the same JUnit + SHA-pinned advisory upload to the quality.yml fast-path Vitest job, which runs on every PR — that's where flake detection actually feeds from.

Same guards as #7175: continue-on-error (never blocks), own-origin only (forks have no TRUNK_TOKEN).

[gemini-code-assist]

Warning

You have reached your daily quota limit. Please wait up to 24 hours and I will start processing your requests again!

[mergify]

Queued — the merge queue status continues in this comment ↓.

[diegosouzapw]

@Mergifyio queue

[mergify]

queue

⚠️ Cannot use Merge Queue batch

Details

⚠ The 'Merge Queue Batch' feature requires a higher subscription tier. Upgrade your subscription to enable it.

[diegosouzapw]

@Mergifyio queue

[mergify]

Merge Queue Status

• ✅ Entered queue — 2026-07-15 03:16 UTC · Rule: release · triggered by @diegosouzapw with the @mergifyio queue command
• ❌ Checks failed · on draft merge queue: checking release/v3.8.49 (af0c72f) and #7205 together #7224
• 🚫 Left the queue — 2026-07-15 03:59 UTC · at 90e2e6b8e10efbfc24c1313dca00f14a0a651626

This pull request spent 42 minutes 44 seconds in the queue, including 16 minutes 22 seconds running CI.

Waiting for

• #check-pending=0

All conditions

• #check-pending=0
• #check-success>=1
• check-success=Merge integrity (changelog + generated skills)
• any of:
  • #check-failure=0
  • all of:
    • #check-failure=1
    • check-failure=dast-smoke

Reason

The merge conditions cannot be satisfied due to failing checks

• 0
• 1
• dast-smoke

Hint

You may have to fix your CI before adding the pull request to the queue again.
If you update this pull request, to fix the CI, it will automatically be requeued once the queue conditions match again.
If you think this was a flaky issue instead, you can requeue the pull request, without updating it, by posting a @mergifyio queue comment.

Requeued — the merge queue status continues in this comment ↓.

[diegosouzapw]

@Mergifyio queue

[mergify]

queue

☑️ Command queue ignored because it is already running from a previous command.

[diegosouzapw]

@Mergifyio requeue

[mergify]

Merge Queue Status

• ✅ Entered queue — 2026-07-15 05:51 UTC · Rule: release · triggered by @diegosouzapw with the @mergifyio queue command
• ✅ Checks passed · on draft merge queue: checking release/v3.8.49 (abe686d) and #7205 together #7245
• ✅ Merged — 2026-07-15 05:54 UTC · at 90e2e6b8e10efbfc24c1313dca00f14a0a651626 · squash

This pull request spent 3 minutes 25 seconds in the queue, including 3 minutes 3 seconds running CI.

Required conditions to merge

• #check-pending=0
• #check-success>=1
• check-success=Merge integrity (changelog + generated skills)
• any of:
  • #check-failure=0
  • all of:
    • #check-failure=1
    • check-failure=dast-smoke