Remove Komodo backend in favor of native hosts

docs/native-hosts.md

@@ -1,8 +1,7 @@
 # Native host management
 
-Electric Cherry controls Docker/Plutainer through an outbound host agent. A native
-instance never uses Komodo or a filesystem mounted into the controller. The
-controller owns desired state, campaigns, collections, safety queues and history;
+Electric Cherry controls Docker/Plutainer through an outbound host agent. The controller
+does not need mounted game-server files. It owns desired state, campaigns, collections, safety queues and history;
 the agent owns local execution and its durable operation journal.
 
 Fleet health checks query RCON even when container inspection is unavailable. A
@@ -554,16 +553,12 @@ coverage is not evidence that a real T5/T6 server has been deployed here. Run:
   execution and after execution but before acknowledgement. Verify the same
   operation IDs and absence of duplicate containers/restarts.
 
-Legacy backend code remains for existing database registrations. New native
-launches do not require its configuration, API, network or mounted directories.
-
 ### Provisioning progress and diagnostics
 
 Native launches distinguish initial eligibility evaluation from an actual wait
 for startup capacity. The operation page records payload preparation, command
 submission, agent acknowledgement and execution, and separate container, game,
-map and Plutonium revision checks. Native actions use host-agent steps rather
-than legacy Komodo deployment steps. Evidence remains available after completion.
+map and Plutonium revision checks. Evidence remains available after completion.
 
 The **Host agent execution** panel reads the durable command state directly,
 including its queue time and latest report time. Agent receipts are recorded in