Skip to content

docs(r-cran-status): verify win-builder submissions - #97

Merged
gadenbuie merged 2 commits into
mainfrom
docs/r-cran-status-win-builder
Oct 15, 2026
Merged

gadenbuie merged 2 commits into
mainfrom
docs/r-cran-status-win-builder

Conversation

@gadenbuie

Copy link
Copy Markdown
Collaborator

Summary

Adds a Win-Builder section to the r-cran-status skill so agents can answer questions like "did win-builder get my package?" or "is win-builder processing my submission?" (both added as trigger phrases to the skill description).

  • What win-builder is: runs R CMD check on Windows for packages submitted via check_win_devel() (or _release() / _oldrelease()); the tarball is uploaded by anonymous FTP to a per-flavor drop folder and results are emailed to the maintainer in DESCRIPTION within ~15–30 minutes.
  • Two-step verification: (1) the FTP drop-folder listing is the authoritative "did the upload arrive" check (with a note that server timestamps are European time); (2) the incoming_pretest/ web listing shows check progress — entry format {package}_{version}_{yyyymmdd}_{hhmmss}, with 00check.log inside each entry. Entries linger for months, so match version and date, not just the name.
  • Gotchas (aligned with official docs + R-package-devel, not folklore): a missing pretest entry ≠ failed upload — it lags behind the FTP listing and queues can jam for hours; don't advise resubmitting while the tarball is still queued (a duplicate won't speed it up); if the tarball vanished but no results email arrived, check the maintainer's spam folder and recent pretest entries, and after several hours suggest asking on R-package-devel rather than resubmitting.
  • Workflow routing rule: win-builder / check_win_devel() requests → Win-Builder section.
  • Skill version bumped 1.0 → 1.0.1.

Token budget

Lines ~Tokens Description
Before (main) 185 1,864 84
After 233 2,346 100
Δ +48 +482 +16

The description sits exactly at the 100-token limit from count-skill-tokens.py; the body remains well under the 5,000-token / 500-line limits. An initial draft of the section was compacted by ~170 tokens during review without losing any guidance.

Add a Win-Builder section that verifies whether a package submitted via
check_win_devel() actually arrived on win-builder: FTP drop folder listing
as the authoritative receipt check, the incoming_pretest/ listing for
progress, and gotchas covering queue delays and lost results emails.
Bump skill version to 1.0.1.
@gadenbuie
gadenbuie merged commit 4400f97 into main Oct 15, 2026
1 check passed
@gadenbuie
gadenbuie deleted the docs/r-cran-status-win-builder branch October 15, 2026 15:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant