@stackbone/cli 0.5.3 → 0.6.0

package/migrations/0089_eval_run_status_reason.sql

@@ -0,0 +1,25 @@
+-- 0089_eval_run_status_reason.sql — a settled eval run says WHY it settled
+-- (PLA-1879).
+--
+-- `stackbone eval` reported a run as `failed`, and the row then read `cancelled`
+-- with no `eval_run.cancel` in the audit log and nothing in the box's output.
+-- Nobody could tell which path had closed it, because the row only ever kept the
+-- status: the route's cancel, the engine's brake between cases, a plan that came
+-- apart and a target the box could not ask all wrote the same bare word.
+--
+-- One nullable column, written by whoever settles the row and never overwritten
+-- once set: the first reason is the one that explains the status, and a later
+-- seal that only fills in the totals must not replace it.
+--
+-- NULLABLE with no default and no CHECK. A run that finished normally has no
+-- reason to give, and a run sealed before this column existed has no honest one
+-- to invent; both read NULL. The text is a diagnostic for whoever opens the row,
+-- not a value anything branches on, so a CHECK would only be a second list of
+-- sentences to keep in step with the engine.
+--
+-- A separate file rather than an edit to 0038: the migrator hashes each body and
+-- verifies it on every boot, so rewriting a landed migration bricks a box that
+-- already ran it. Comments count towards that hash too.
+
+ALTER TABLE stackbone_platform.eval_runs
+    ADD COLUMN IF NOT EXISTS status_reason text;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@stackbone/cli",
-  "version": "0.5.3",
+  "version": "0.6.0",
   "license": "UNLICENSED",
   "type": "module",
   "bin": {