Suppress maintenance watchers during provisioning

Keep maintenance observations and automatic requests clear of active lifecycle operations and retained recovery capacity while preserving owned recovery and explicit retries. Fixes #55
2026-10-01 11:54:22 -04:00
parent a3cd3ee585
commit 0cb48c435e
8 changed files with 366 additions and 18 deletions
@@ -95,6 +95,9 @@ Maintenance decides when work is needed and verifies the result. Provisioning
 executes every lifecycle operation using the shared safety checks and queues.
 Health recovery uses one restart followed by one rebuild if needed; drift repair
 requests a rebuild with a linked Campaign. **Rebuild deletes all instance files.**
+Maintenance skips observations and new automatic work on servers with active
+Provisioning operations or retained recovery capacity. Other servers continue
+normally, and existing maintenance still tracks its own operation's outcome.

 Plutonium updates are applied by Plutainer's startup updater
 (`PLUTAINER_AUTO_UPDATE` must be enabled). Check versions and choose **Update on
@@ -109,6 +112,7 @@ Optional daily restarts are independent of updates. Schedules use the saved
 timezone, follow daylight saving changes, and coalesce missed days into one run.
 Intentionally stopped servers are excluded. Existing schedules, pending jobs,
 operation IDs, and history survive the move from Settings and Watchdog.
+Servers owned by Provisioning are skipped for that scheduled occurrence.

 **Pause all maintenance** holds new and queued maintenance while checks and
 submitted recovery continue. Each capability retains its own policy. Automatic