beetroot-ci.yml binder:host modprobe lane swallows a missing linux-modules-extra with no ::warning:: breadcrumb

Found during the codebase compatibility/CI sweep.

At .github/workflows/beetroot-ci.yml:191-192 the binder: host lane runs:

sudo apt-get update || true
sudo apt-get install -y "linux-modules-extra-$(uname -r)" || true
sudo modprobe binder_linux ... || true

The || true on every step means a genuinely missing linux-modules-extra-$(uname -r) package — which happens on hosted runners after a kernel-image refresh (the same staleness class as #211) — is silently swallowed, and the subsequent binder boot fails later with a less obvious error.

This tolerant pattern is intentionally consistent with the provide-binder composite action, but unlike #211's lanes there is no ::warning:: breadcrumb when the module can't be loaded, making a binder: host CI failure hard to attribute.

Low severity / observability nit: emit a ::warning:: (or ::notice::) when the install/modprobe step fails-soft, so a later binder boot failure is traceable to a missing module rather than looking like a redroid bug.

Verifiable at .github/workflows/beetroot-ci.yml:191-192.

Labels: ci

Start at .github/workflows/beetroot-ci.yml:191-192 and compare the binder: host lane with the provide-binder composite action and the warning behavior described in #211. Verify that a failed linux-modules-extra install or modprobe emits a :⚠️: or ::notice:: breadcrumb while the lane remains fail-soft, and confirm the workflow YAML is valid.