[bug] Automations (listed as Free) are unusable on Free tier — dispatch requires the paid relay #5331

Summary
The pricing page lists Automations with a checkmark under Free, but in practice automations cannot
run on the Free tier. All automation dispatch routes through the relay, and the relay is gated behind
the paid "expose host service via relay" capability. As a result, a feature advertised as Free is
unreachable without a paid plan — including automations targeting my own local device.

Environment

• Superset desktop v1.12.5, macOS (Apple Silicon, macOS 15 / Darwin 24.6)
• Free tier

What I expected
Per the pricing page (Compare Plans → Features → Automations = ✓ under Free), I expected to be able
to create and run automations against my local device on the Free plan. The only row marked paid-only
in that section is Remote workspaces (— under Free), which I'd expect to be the thing that needs an
upgrade — not Automations.

What actually happens

• Automations against my own device are marked skipped_offline / "target host offline", even though
  the host-service is running locally and the desktop app is connected to it.
• The host shows Offline in Hosts settings despite superset start reporting running.

Root cause I traced

1. The host only shows "online" while it holds an outbound relay tunnel to relay.superset.sh;
   v2Hosts.isOnline is set from that presence.
2. Automation dispatch is cloud-side only and hard-gates on it: in dispatch.ts, if (!host.isOnline) →
   { status: "skipped_offline", error: "target host offline" }, otherwise it sends via
   relayMutation(..., relayUrl). There is no local/loopback dispatch path — even "this device"
   automations go cloud → relay → host.
3. The host-service only opens the tunnel if (env.RELAY_URL && env.ORGANIZATION_ID). The desktop's
   buildEnv() (host-service-coordinator) deletes RELAY_URL from the child env unless the local setting
   expose_host_service_via_relay is true (defaults false).
4. That setting is gated in the UI behind the paid tier, so on Free the host-service never receives
   RELAY_URL, never tunnels, never goes online → every automation is skipped_offline.

Additional finding (please confirm intended behavior)
When I enabled expose_host_service_via_relay locally, the host-service still did not receive
RELAY_URL / register with the relay after respawn — suggesting entitlement is also enforced
server-side at the relay. If so, there is currently no path at all for a Free-tier user to use
Automations as advertised.

Ask
Is Automations intended to be Free? If yes, this looks like either (a) a pricing-page error
(Automations should not show ✓ under Free), or (b) a product bug (Free-tier automations targeting the
local device should not require the paid relay — they need a local dispatch path, or the relay needs
to permit local-target automations on Free). Could you clarify which, and fix accordingly?