#877 Fixed distributed queries and status led Pull request opened by javuto Summary Fix distributed query targeting and align node activity status across the UI with the backend’s inactivity threshold. What changed • Fixed empty distributed-query targeting so “no target selected” includes all nodes in the environment • Fixed platform targeting for the

all

platform bucket • Added backend regression tests around query target selection and pending node-query creation • Added shared frontend node-status logic based on the configured inactivity window • Updated node detail, nodes table, and dashboard views to use consistent active/inactive status rules • Added

inactive_hours

to

/api/v1/stats

so the dashboard uses the exact backend threshold for: • the

Inactive ≥ Nh

KPI label • recent enrollment active/inactive badges • Added frontend regression tests for node status rendering and stats typing Why There were two related issues: • distributed queries could miss intended nodes because default/“all” targeting paths were too narrow • the frontend could label nodes as inactive even when the backend still considered them active This change makes query fanout and UI activity status consistent with backend behavior. jmpsec/osctrl