One extension smoke task per covered distro family: enough of the extension e2e corpus to prove load, signature verification, and a $search/$vectorSearch round-trip to a live mongot on that platform, cron cadence rather than per-commit, on at least one arch per family (both arches where the family releases both and capacity allows - the floor artifact is per-arch, so arch is the dimension the glibc-floor spike can miss).

The wiring cost: dedicated variants per platform passing the signature-verification-secure compile flag with their own compile task group, plus build-mongot for the mongot binary, per the Scope/TD's smoke plan (SERVER-133863). The existing release variants cannot host these tasks: they forbid experimental-tagged tasks and their secure compile flag drops in patch builds. That per-platform CI cost is the reason for one smoke variant per family rather than matrix parity.

Acceptance: for each family with a validated artifact, a scheduled task exists that fails if the extension does not load, verify, and serve a query on that platform.

Part of CLOUDP-437684. Depends on SERVER-133865 (artifacts threaded into dist-test) and SERVER-133863 (smoke plan).