Submit imurun 0.1.0 to CRAN

[WestonVoglesonger]

Tracking issue for getting imurun onto CRAN.

Hard blocker: imuGAP must be on CRAN first

imurun Imports: imuGAP (>= 0.1.0) and currently pulls it via Remotes: ACCIDDA/imuGAP. CRAN does not accept packages that depend on non-CRAN packages, and Remotes is stripped from the submission tarball. Therefore imuGAP must be accepted on CRAN before imurun can be submitted. Once imuGAP is live, remove or adjust the Remotes entry so imuGAP resolves from CRAN.

Already in place

• R CMD check workflow regenerates roxygen documentation and runs R CMD check --as-cran.
• CRAN-shaped DESCRIPTION, license metadata, spelling check, and package metadata.
• CRAN submission workflow cran-submission.yaml (Port CRAN submission workflow (cran-submission.yaml) from imuGAP #33).
• cran-comments.md (Add cran-comments.md for the CRAN submission #34).
• NEWS.md has a # imurun 0.1.0 heading.
• No direct cmdstanr use, so no Additional_repositories entry is needed.

Remaining submission checklist

• imuGAP accepted on CRAN and imurun's Remotes adjusted.
• Run a fresh R CMD check --as-cran at error-on: warning and confirm the expected 0 errors / 0 warnings / 1 new-submission note.
• Refresh cran-comments.md with the final check environments/results if needed.
• Maintainer (cre: Carl) triggers submission and replies to the CRAN confirmation email.

[WestonVoglesonger]

Handoff: I’m leaving ACCIDDA next week. @pearsonca, please own this release tracker. After imuGAP is available on CRAN, remove/adjust Remotes, run the final CRAN checks, refresh cran-comments, submit as maintainer, and close the issue after acceptance.