countme: bluefin-lts testing reports to /metalink with a baked tag and is never published #1280

Scope

projectbluefin/bluefin-lts testing ships a first-party countme client (bluefin-lts#604, merged 2026-09-14): /usr/libexec/bluefin-lts-countme → GET countme.projectbluefin.io/metalink?repo=bluefin-lts&tag=…. main does not carry it (its bluefin-lts-countme.service is still ExecStart=/usr/bin/dnf makecache).

Observed in D1 projectbluefin-countme.telemetry_events (read-only query, 2026-09-27):

• ~27 repo=bluefin-lts rows 2026-09-16 → 2026-09-26, ~3/day, tag=stable/testing.
• 6 rows 2026-09-12 → 09-14 with literal tag=${IMAGE_TAG}, flavor=${IMAGE_FLAVOR}, arch=${ARCH}.

Impact

1. Wrong stream. The helper reads image-info.json image-tag, which build_scripts/90-image-info.sh:8 bakes as IMAGE_TAG="stable/testing". The factory contract (documentation docs/skills/cloudflare-workers.md, common#1205) says the stream is the booted ref's tag from bootc status, never the baked image-tag.
2. Collected, never published. documentation scripts/lib/countme-sources.mjs PROJECTBLUEFIN_REPOS = ["dakota"] drops these rows from /counts.json, and common#1205 states "Bluefin Classic and LTS never report". LTS systems are sending data no surface uses.
3. Two clients, two contracts. LTS uses weekly /metalink; common#1205 moves Dakota/Utah to daily PUT /v1/ping, whose allowlist (PING_IMAGE_FAMILIES = ["dakota","utah"]) rejects LTS.

Fixed looks like

A maintainer decision, then one of:

• LTS is counted: LTS consumes common's projectbluefin-countme (after feat(countme): replace bluefin-countme with a daily projectbluefin-countme ping #1205), bluefin-lts is added to PING_IMAGE_FAMILIES and the /analytics families, and the stream comes from bootc status; or
• LTS is not counted: remove bluefin-lts-countme helper from bluefin-lts testing before it promotes to main, and purge the stray repo=bluefin-lts / ${IMAGE_TAG} rows.