Normalize coverage artifacts and expose build outputs

[PSchmiedmayer]

♻️ Current situation & Problem

SchmiedmayerLab/NutriSight#1 exposed a layout mismatch in the reusable coverage workflow. A single artifact is extracted directly into the download destination, while multiple artifacts retain artifact-named wrapper directories. The workflow assumed only the wrapped layout, so a valid xcresult could not be found.

The reusable build workflow inferred its result bundle and artifact names correctly, but did not expose them to downstream jobs. Callers therefore had to duplicate an inferred name when invoking the coverage workflow.

⚙️ Release Notes

• Normalize single and multiple xcresult artifact layouts before conversion.
• Support both direct and wrapped lcov artifact layouts.
• Validate downloaded coverage inputs and report clear errors for invalid bundles.
• Expose resolved result_bundle and artifact_name outputs from the reusable xcodebuild workflow.

📚 Documentation

The coverage workflow now documents the single-artifact extraction behavior inline and stages downloads outside the checked-out repository. Callers can pass the build output to coverage through needs..outputs.artifact_name while existing literal names and glob patterns remain supported.

✅ Testing

• Ran actionlint across all reusable workflows.
• Ran yamllint, REUSE validation, and whitespace checks.
• Verified the single-artifact path with the NutriSight xcresult; xccov read 78.11% coverage.
• Verified that two wrapped xcresult bundles merge into a readable result.
• Verified direct and wrapped lcov path resolution.
• Passed end-to-end consumer validation in Fix CI scheme selection and stabilize hosted UI tests NutriSight#1 against commit 5251e4c, including Codecov upload: https://github.com/SchmiedmayerLab/NutriSight/actions/runs/29235977361

Code of Conduct & Contributing Guidelines

By creating and submitting this pull request, I agree to follow the Code of Conduct and Contributing Guidelines.

• I agree to follow the Code of Conduct and Contributing Guidelines.

[coderabbitai]

Warning

Review limit reached

@PSchmiedmayer, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 4 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: afc2613a-82a9-4c09-b9a2-854e9aa8f9bd

📥 Commits

Reviewing files that changed from the base of the PR and between 5484c49 and 5251e4c.

📒 Files selected for processing (2)

• .github/workflows/coverage.yml
• .github/workflows/xcodebuild.yml

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[Copilot]

Pull request overview

This PR updates the reusable coverage.yml workflow to normalize downloaded coverage artifact layouts so both single-artifact (flattened) and multi-artifact (wrapped) download layouts can be processed reliably before converting/uploading coverage.

Changes:

• Downloads coverage artifacts into ${{ runner.temp }} to avoid staging inside the checked-out repository.
• Adds validation and layout normalization for .xcresult bundles (flattened vs. wrapped extraction).
• Improves lcov path resolution to support both direct-file and wrapped-directory artifact layouts.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.