ci: add Trunk CI workflow (Check + Merge Queue + Flaky Tests)

[IgorGanapolsky]

What

Adds .github/workflows/trunk.yml to integrate Trunk into the CI pipeline for Random-Timer.

Why

Completes Step 5 of the Trunk onboarding checklist:

• Trunk Check runs on every PR and push, posting inline annotations
• merge_group trigger enables the Trunk Merge Queue to validate batched PRs before they land on develop
• Flaky Test upload sends Android (JUnit XML) and iOS (XCTest) test results to Trunk's Flaky Test detection dashboard

Required Action Before Merging

⚠️ Add TRUNK_TOKEN as a Repository Secret before this workflow runs:

1. Get token from app.trunk.io/igor-personal → Settings → Repositories
2. Go to GitHub Secrets → New repository secret
3. Name: TRUNK_TOKEN, Value: (paste token)

Checklist

• trunk-io/trunk-action@v1 runs on pull_request + push + merge_group
• TRUNK_TOKEN secret wired in (must be added manually)
• Android JUnit XML paths configured for Gradle builds
• iOS XCTest XML paths configured
• continue-on-error: true on upload steps so test failures don't block CI
• org-slug: igor-personal matches Trunk dashboard org

[trunk-io]

Merging to develop in this repository is managed by Trunk.

• To merge this pull request, check the box to the left or comment /trunk merge below.

After your PR is submitted to the merge queue, this comment will be automatically updated with its status. If the PR fails, failure details will also be posted here

[gemini-code-assist]

Important

Installation incomplete: to start using Gemini Code Assist, please ask the organization owner(s) to visit the Gemini Code Assist Admin Console and sign the Terms of Services.

[sonarqubecloud]

Quality Gate failed

Failed conditions
3 Security Hotspots

See analysis details on SonarQube Cloud

[sentry]

Bug: The iOS test results upload step is misconfigured. It uses junit-paths to look for XML files, but the CI generates binary .xcresult bundles, causing the upload to silently fail.
_{Severity: MEDIUM}

Suggested Fix

Replace the junit-paths parameter with xcresult-path and point it to the .xcresult bundle generated by the test step. This aligns the uploader with the actual artifact being produced, allowing it to process the binary test results directly.

Prompt for AI Agent

Review the code at the location below. A potential bug has been identified by an AI
agent.
Verify if this is a real issue. If it is, propose a fix; if not, explain why it's not
valid.

Location: .github/workflows/trunk.yml#L63

Potential issue: The "Upload iOS Test Results" step in the `trunk.yml` workflow is
configured to use the `junit-paths` parameter, which expects JUnit XML files. However,
the CI process generates a binary `.xcresult` bundle. The glob pattern
`**/*.xcresult/**/*.xml` will never match any files because `.xcresult` bundles are a
binary format and do not contain XML files directly. The workflow is missing a
conversion step (e.g., using `xcpretty`) to create JUnit XML. Because
`continue-on-error: true` is enabled, this step will silently fail without uploading any
iOS test data, defeating the purpose of the flaky test detection feature for iOS.

_{Did we get this right? 👍 / 👎 to inform future reviews.}

[github-actions]

❌ CI Some checks failed

Check	Result
Android Tests	success
iOS Build & Tests	success
Python Unit Tests	success
Python Script Tests + Release Gate	failure
Playwright Local Checks	success
Security	success

View details

[IgorGanapolsky]

Closing: superseded by later work or has unresolvable merge conflicts. Reopen if still needed.