Wire pluto PTD probes to the fleet UA wrapper (--app pluto) — wrapper exists with zero callers, probes ship untagged

Pluto's PTD probes are plain untagged curl (e.g. curl https://evolutiva.pensanta.com/api/app-version). pluto/scripts/probe-curl.sh:20 exists and stamps -A evolutiva-internal-probe/pluto-ptd but has ZERO callers anywhere in the tree (measured 2026-07-31: 6 grep hits, all inside the wrapper's own header comments). Fleet standard is the PATH wrapper ~/.local/bin/probe-curl.sh v2.0 (--app pluto | PROBE_APP=pluto, no default, exit 2 if absent; bin-venus-cc owns, queued behind Elazar's go). SEVERITY IS LATENT, NOT ACTIVE — this corrects the dispatch premise. Pluto's untagged probes do NOT contaminate pluto usage telemetry: logRouteUsage has exactly one call site, src/app/(protected)/template.tsx:2, so /api/* never invokes it; and it returns early on a missing middleware-stamped pathname header (usage-telemetry.ts:131, comment :29-30) and needs params.userId. The UA skip at :135 is a third gate behind two structural ones. Zero historical rows affected, so the companion 'quantify/correct contamination' item was NOT filed — there is nothing to quantify (evidence: tag coder-pluto-cc-ms8fb53hbklo; audit-venus-ca accepted, tag audit-venus-ca-ms8fap775wei). Scope: adopt the fleet wrapper for pluto's PTD probe path so a probe added against a PAGE route later cannot be counted as a pageview. Prefer the PATH wrapper with --app pluto over the repo-local copy; decide whether pluto/scripts/probe-curl.sh should then be deleted (bin-venus-cc's v2.0 design intends the repo-local copies to go). Cross-check pluto-solo/scripts/probe-curl.sh (byte-identical, retired-lane tree, separate triage).