rootfs 29.8.0-2

A revision bump with no engine change: containerd (2.1.4), runc (1.3.0), BuildKit (0.27.0), Alpine (3.24.1) and nvidia-cdi-hook (1.20.0) are identical to 29.8.0-1, and the engine is still moby docker-v29.8.0 pinned to commit 3ce5872b7950c63ba2ffbc5123101019ff3e6682.

What changed is inside the tarball: the in-distro agent is skrog-agent, not hawser-agent. Renaming the project renamed the binary the rootfs build produces, but every rootfs published before this one still carries the old name — a name crossing a boundary that cannot be renamed with it. Skrog looks for either, so nothing broke; this release is what lets that compatibility lookup go away.

The asset names change with it, for the same reason: this is the first rootfs published as skrog-rootfs-*. Earlier releases keep the hawser-rootfs-* names they were published under, and internal/release/manifest.json records them that way (#232) — a published asset's filename is a fact, not text to be renamed.

Verify before use:

# the checksum the manifest pins
sha256sum -c skrog-rootfs-29.8.0-2.tar.gz.sha256

# and that GitHub Actions signed that checksum list
cosign verify-blob --bundle skrog-rootfs-29.8.0-2.tar.gz.sha256.cosign.bundle `
  --certificate-identity-regexp '^https://github.com/wslkit/skrog/' `
  --certificate-oidc-issuer https://token.actions.githubusercontent.com `
  skrog-rootfs-29.8.0-2.tar.gz.sha256