feat(rebuild): shard the weekly rebuild and make each shard resumable (#163)

## Problem

`weekly-rebuild-missing` runs one job per `<os>-<arch>` and walks that slot's list serially in a single `R -q -e` argument.
That was cheap while every source fallback was skipped as "already built".
Since bincraft #105/#106/#107 and #159 the gate works, and the lists are large: 8 917 source-served records on `amd64/alpine324`, 15 023 on `amd64/resolute`.

Pipeline 10910 (`weekly_rebuild_missing:alpine-324-amd64`) ran for two days, reached `[8692/23885] cholera`, and was killed there.

Two failures follow from that shape:

- **No parallelism.** The work is embarrassingly parallel across packages; one job does all of it.
- **No resumability and no clean stopping point.** The loop ends only by exhausting the list, so the only way to stop it is a kill. A restart re-walks from the first entry, paying a CRAN version resolution and an S3 `HEAD` per package before reaching new work. And a kill matches neither `success` nor `failure`, so the `Purge CDN cache` step never ran: the ~4 600 binaries 10910 did publish stayed hidden behind stale edge copies.

## What this changes

**Three shards per slot.** Each of the 18 `OS`/`ARCH` rows gains `SPLIT_INTO`/`SPLIT_INDEX`, mirroring `build-all-versions.yaml`. Cron and manual routing are unchanged: both filters already match on `${OS}-${ARCH}`, so they now match all three shards of a slot.

**`local/rebuild-missing.R`** replaces the ~1 500-character inline one-liner. The slice is interleaved rather than contiguous, because the list is alphabetical and cost clusters by name (`Rcpp*`, `Bioc*`, `rstan*`).

**Resume by re-deriving state from the bucket.** One `s3_dir_info()` listing gives ETags for the slot; a package is outstanding iff its object's ETag equals CRAN's published `MD5sum`, i.e. it is still byte-identical to CRAN's source. That is `check_s3_root_package()` evaluated in bulk. No progress file, no volume, no DB cursor, and correct when a sibling shard or a `process-updates` run completes something concurrently.

It reads ETags rather than the index's `Built` field the way `packages-to-build.R` does, because the index is no longer rewritten until the dependent pipeline runs and so cannot reflect the current run's progress.

Unknown always means "already a binary", never "rebuild it": a multipart ETag, an unreadable CRAN index or an empty listing can never mass-schedule work.

**A 20 h wall-clock budget** per shard. It exits 0, so the re-index and purge always fire and the remainder is picked up next run with no bookkeeping.

**`.crow/weekly-rebuild-reindex.yaml`** takes over re-indexing and the purge, with `depends_on: [weekly-rebuild-missing]` and `runs_on: [success, failure]`. Three shards writing one slot's `PACKAGES` concurrently would race: `update_PACKAGES()` lists the live bucket, so an early lister that uploads last publishes an index missing its siblings' work.

## Verification

`crow lint .crow/` passes on all 11 pipelines. `prek run` passes.

19 assertions in `local/tests/test-rebuild-missing.R`, 0 failures, covering the partition (disjoint, covering, deterministic, short lists, out-of-range index) and the outstanding filter (source ETag kept, binary ETag dropped, absent object kept, multipart and missing-from-CRAN treated as built).

One of those tests caught a real bug before it shipped: an empty ETag table indexed to zero length rather than to `NA`, which recycled the result away and reported "nothing to build" — the dangerous direction. Fixed with an explicit `lookup()`.

The filter run against the live `amd64/alpine324` index, using its `MD5sum` column as the ETag (established to match the objects):

```
index packages:               24343
outstanding (filter):          8950
no Built stamp:                8917
filter vs no-Built agreement:  8917 of 8917
outstanding but stamped Built:   33 (version drift vs CRAN)
shard sizes: 2984/2983/2983 (sum 8950, unique 8950)
```

It reproduces the source-served set exactly. The extra 33 are packages whose slot version differs from CRAN's current one, so no object exists at the CRAN version key: correctly outstanding.

## Notes for review

- The 20 h budget is a chosen default, exposed as `REBUILD_BUDGET_HOURS` in the pipeline.
- `depends_on` is file-level, not row-level, so on a full cron run no slot is re-indexed until the slowest of all 54 jobs finishes. The budget bounds that at roughly a day.
- An explicit cancel still skips the re-index. Recovery is to trigger `weekly-rebuild-reindex` on its own.
- The purge runs on every re-index row rather than one designated slot: a cron fires only its own slot's row, so gating on a named slot would leave every other slot unpurged.
- Out of scope: `build-all-versions` still cannot rebuild source fallbacks, because `local/build-all.R:113-122` drops every version with any `single_builds` row, which is precisely the source-fallback set.

Design: `specs/2026-08-12-shard-weekly-rebuild-design.md`
Reviewed-on: #163

local/tests/test-rebuild-missing.R

@@ -0,0 +1,94 @@
+source(file.path("..", "rebuild-missing-helpers.R"))
+
+test_that("shard_slice partitions the list without gaps or overlap", {
+  pkgs <- letters[1:10]
+  parts <- lapply(1:3, function(i) shard_slice(pkgs, 3, i))
+
+  expect_identical(parts[[1]], c("a", "d", "g", "j"))
+  expect_identical(parts[[2]], c("b", "e", "h"))
+  expect_identical(parts[[3]], c("c", "f", "i"))
+
+  expect_identical(sort(unlist(parts)), sort(pkgs))
+  expect_identical(anyDuplicated(unlist(parts)), 0L)
+})
+
+test_that("shard_slice is deterministic and survives short lists", {
+  expect_identical(
+    shard_slice(letters[1:10], 3, 2),
+    shard_slice(letters[1:10], 3, 2)
+  )
+  expect_identical(shard_slice(character(0), 3, 1), character(0))
+  # more shards than packages: the tail shards get nothing rather than erroring
+  expect_identical(shard_slice(c("a"), 3, 1), "a")
+  expect_identical(shard_slice(c("a"), 3, 2), character(0))
+})
+
+test_that("shard_slice rejects an out-of-range index", {
+  expect_error(shard_slice(letters, 3, 4), "split_index")
+  expect_error(shard_slice(letters, 3, 0), "split_index")
+})
+
+test_that("outstanding_packages keeps source fallbacks and drops real binaries", {
+  cran_version <- c(httr = "1.4.8", R6 = "2.6.1", curl = "7.1.0")
+  cran_md5 <- c(
+    httr_1.4.8 = "8756015b94a9cff6f410ca4de8557f12",
+    R6_2.6.1 = "f01b1787f12797c29194d63c9afd5d70",
+    curl_7.1.0 = "8af2ccbf5d85dc18866f45f1f26f348d"
+  )
+  etag <- c(
+    # byte-identical to CRAN: the build never happened
+    "httr_1.4.8.tar.gz" = "8756015b94a9cff6f410ca4de8557f12",
+    # a real binary was published
+    "R6_2.6.1.tar.gz" = "9d6087ee9adda3f0a3b8067cfc652c05"
+    # curl has no object at all
+  )
+
+  out <- outstanding_packages(
+    c("httr", "R6", "curl"),
+    etag,
+    cran_version,
+    cran_md5
+  )
+  expect_identical(out, c("httr", "curl"))
+})
+
+test_that("outstanding_packages treats unknowns as already built", {
+  cran_version <- c(a = "1.0", b = "1.0")
+  cran_md5 <- c(a_1.0 = "aaaa")
+
+  # a multipart ETag carries no MD5, and `b` is missing from CRAN's index:
+  # neither may schedule a rebuild
+  etag <- c("a_1.0.tar.gz" = "abc-3", "b_1.0.tar.gz" = "bbbb")
+
+  expect_identical(
+    outstanding_packages(c("a", "b"), etag, cran_version, cran_md5),
+    character(0)
+  )
+})
+
+test_that("outstanding_packages keeps a package CRAN has no version for", {
+  out <- outstanding_packages(
+    "ghost",
+    c(),
+    c(other = "1.0"),
+    c(other_1.0 = "aaaa")
+  )
+  expect_identical(out, "ghost")
+})
+
+test_that("outstanding_packages handles an empty list", {
+  expect_identical(
+    outstanding_packages(character(0), c(), c(), c()),
+    character(0)
+  )
+})
+
+test_that("parse_rebuild_args defaults the budget", {
+  a <- parse_rebuild_args(c("3", "2"))
+  expect_identical(a$split_into, 3L)
+  expect_identical(a$split_index, 2L)
+  expect_identical(a$budget_hours, 20)
+
+  b <- parse_rebuild_args(c("3", "2", "1.5"))
+  expect_identical(b$budget_hours, 1.5)
+})