qol-tray-dev-recompilelisted

# qol-tray dev recompile Use the host's canonical dev recompile action for an ordered host restart. Do not manually kill supervised plugin processes unless source inspection proves the host restart path cannot perform the required cleanup. ## Source ownership - Find the frontend trigger and endpoint by searching for `recompile-self`; UI placement and labels are not stable documentation. - Trace the endpoint through the recompile service, restart scheduler, plugin-manager shutdown, daemon tracker, and process replacement code. - Read dev-link/build-state code to determine whether plugin binaries are rebuilt or merely restarted. - Read the running build's response/logs to confirm which path actually executed. Never rely on a copied function sequence or version label from this skill. The checked-out call graph and runtime trace own the behavior. ## Restart contract A full host recompile is trustworthy only when the live path: 1. Produces or selects the intended host binary. 2. Stops short-lived plugin invocations and resident daemons through the supervisor. 3. Clears process-tracking state without deleting user configuration. 4. Replaces or restarts the host with the selected binary. 5. Lets the new host rediscover and supervise plugins from declared provenance. If any step is absent or failed in runtime evidence, report that boundary rather than claiming a fresh slate. ## Plugin provenance matters Restarting a daemon does not prove its executable was rebuilt. Before d