Say a module assigned and left out of its machine's composition as a condition (issue 380)

A push leaves out a module whose settings do not compose and sends the rest,
which is right, but only plan said so: nfs-server ran nowhere for days while
the operator believed it ran. The self-check now raises needs-operator for a
setting nobody gave, naming the setting and the command, and left-out for any
other cause; both warnings, cleared once the module composes or is unassigned.
status and node show list the same modules as assigned, not applied.

cmd/mesh-controller/doctor.go

@@ -136,6 +136,11 @@ var probeRegistry = []probe{
 	{ID: "D-root", Asserts: "no agent can become root without a person on a machine where the router or a channel " +
 		"proving its sender runs: not by its own account, and not through a tool that runs its command as an account " +
 		"that can", From: "ADR 0259 §8", Kind: kindRootNotFree, Phase: 2, run: probeAgentRoot},
+	// A module assigned and left out of its machine's composition (novox/hq issue 380): said on that machine, the
+	// operator's, never urgent; cleared once it composes again or is unassigned.
+	{ID: probeLeftOutID, Asserts: "no module assigned to a machine is left out of its composition unsaid: each " +
+		"raises needs-operator for a setting nobody gave, left-out for any other cause", From: "issue 380",
+		Kind: kindLeftOut, Raises: []string{kindNeedsOperator}, Phase: 1, run: probeLeftOut},
 	{ID: "DW", Asserts: "the watchdogs of the signals table ran within three of their intervals",
 		From: "ADR 0227 rule 6: the watchers are watched", Kind: "watchdogs-silent", Phase: 1, run: probeWatchdogs},
 	// The core's health definitions (novox/hq to-be 45 §8, ADR 0236): what a core component's new build is