opencode-thrum-pro 0.1.8 → 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.
|
|
@@ -26,18 +26,8 @@ than no dashboard.
|
|
|
26
26
|
|---|---|
|
|
27
27
|
| `dashboard.set/get/show/clear/delete` RPCs (daemon-side) | **LANDED** on trunk (merge `6c7539236f83`); usable only against daemons BUILT after that merge — verify your daemon's build before relying on the RPCs |
|
|
28
28
|
| `thrum dashboard` CLI (set/show/get/update/delete/clear/results) | **LANDED** on trunk (merge `108511a0`); usable only against a `thrum` binary BUILT after that merge — verify your CLI's build before relying on these commands |
|
|
29
|
-
| Web UI Dashboard tab (where the human SEES a board) | **
|
|
30
|
-
| Answer round-trip (user clicks → message + nudge to you) | **
|
|
31
|
-
|
|
32
|
-
**Consequence until the next deploy carries E3 and E4:** publishing a board
|
|
33
|
-
is STILL a no-op for the human on any box running a pre-E3/pre-E4 binary —
|
|
34
|
-
it renders NOWHERE there and, even where it renders, an answer cannot
|
|
35
|
-
return to you, even though the UI and answer-round-trip code now both exist
|
|
36
|
-
on trunk. Do NOT substitute a dashboard for a nudge or a direct message
|
|
37
|
-
unless you know the box you're talking to has deployed a build containing
|
|
38
|
-
BOTH E3 and E4. If the human cannot see the board or their answer cannot
|
|
39
|
-
reach you, the question DOES disappear — the exact failure the dashboard
|
|
40
|
-
exists to kill.
|
|
29
|
+
| Web UI Dashboard tab (where the human SEES a board) | **SHIPPED** in v0.11.0-rc.1 (E3, merge `49712f87`) |
|
|
30
|
+
| Answer round-trip (user clicks → message + nudge to you) | **SHIPPED** in v0.11.0-rc.1 (E4, merge `ea95318a`) |
|
|
41
31
|
|
|
42
32
|
**Consequence, now that E2 has landed:** the `thrum dashboard ...` command
|
|
43
33
|
shapes below are runnable — but, per the E2 row above, only against a CLI
|
|
@@ -89,7 +79,7 @@ cat > /tmp/board.md <<'EOF'
|
|
|
89
79
|
{"title": "My board", "widgets": [ ... ]}
|
|
90
80
|
EOF
|
|
91
81
|
thrum dashboard set --doc-file /tmp/board.md
|
|
92
|
-
thrum dashboard set
|
|
82
|
+
thrum dashboard set < /tmp/board.md # stdin is the default when --doc-file is omitted
|
|
93
83
|
|
|
94
84
|
# HTML regions come from FILES ONLY — never inline (backticks in shell strings EXECUTE)
|
|
95
85
|
thrum dashboard set --html-file /tmp/panel.html --html-id my-panel
|