opencode-thrum-pro 0.1.9 → 0.1.10
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
|
@@ -61,6 +61,10 @@ Build once per artifact on its `artifact.build_host` via `artifact.build_command
|
|
|
61
61
|
|
|
62
62
|
## 5. The staged order — canary, waves, prepare-and-hold, promotion gate
|
|
63
63
|
|
|
64
|
+
> 🔴 **If any node fails during the rollout — canary or any wave — STOP THE ROLLOUT.** Do not roll, restart, or recommend
|
|
65
|
+
> restarting any further node (including the build host / primary) until the failure is root-caused and fixed or the
|
|
66
|
+
> owner explicitly decides to continue. A node that went down and was recovered by hand is a FAILURE, not a green.
|
|
67
|
+
|
|
64
68
|
- **Canary first, alone.** One node (adapter `topology.canary`) rolls first. Its health must be observed green before any wave proceeds.
|
|
65
69
|
- **Waves with coordinated dependency/order/rollback.** Subsequent waves follow `topology.waves`. When related daemons share ordering (e.g., connected-repo daemons that must restart together), respect the adapter-defined dependency and restart order; a failure in one dependent daemon triggers coordinated rollback per adapter `rollback` / `backup.restore_command`.
|
|
66
70
|
- **Prepare-and-hold + release BY NAME.** If the mechanism supports it, prepare all nodes in a wave (acquire + verify artifact, take BEFORE snapshot, but do not restart) then release by explicit node name, not by broadcast.
|