An apply leaves a container a maintenance window holds still (hq issue 224)

A while-stopped step stops its module's containers, and an apply arriving
mid-window read the stopped server as broken and recreated it running under
the step - for the store's collector, a registry taking an upload the sweep
then deletes. The scheduler now records each window under the node's state
directory before its first stop and erases it after its last start, so every
apply on the machine (daemon, reconcile by hand, installer) reports a held
container held-still and leaves it for the first apply after the window.
A window whose host died, or past six hours, holds nothing; the report says
which windows are open.

internal/bootstrap/apply.go

@@ -66,9 +66,12 @@ func ApplyBundle(ctx context.Context, o Options, sys system.System, d *declarati
 	// distribution's own /etc/nftables.conf among them — so it keeps the original of each file it
 	// has no record of, beside the node's state, exactly as a declaration from the mesh does
 	// (novox/hq ADR 0100).
-	report, updated, applyErr := apply.ApplyKeeping(ctx, sys, d, known, store.OriginCarried, run,
+	// Minding the maintenance windows a running host has open: the carried bundle is where the
+	// store's registry comes from, and an installer re-run at 03:31 must not restart it under its
+	// collector (novox/hq issue 224).
+	report, updated, applyErr := apply.ApplyMindingWindows(ctx, sys, d, known, store.OriginCarried, run,
 		func(line string) { say("  " + strings.TrimPrefix(line, "  ")) }, refuseSealed,
-		apply.KeepIn(filepath.Dir(o.State)))
+		apply.KeepIn(filepath.Dir(o.State)), apply.WindowsIn(filepath.Dir(o.State)))
 
 	// The bundle is consumed, whichever way the apply went: what is on the machine came from these
 	// bytes, and the carried ones must not be applied over it. The mode is the operator's word at