@devrouter/cli 0.0.65 → 0.0.67

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@devrouter/cli",
-  "version": "0.0.65",
+  "version": "0.0.67",
   "description": "Local dev routing CLI with shared Traefik reverse proxy",
   "author": "Roland Schlaefli",
   "homepage": "https://github.com/rschlaefli/devrouter#readme",

package/upgrade-prompts/0.0.66.md

@@ -0,0 +1,31 @@
+# Upgrade to devrouter 0.0.66
+
+This patch release completes managed stop when Devsy replaces a workspace
+registration UID after the workload is positively absent, releasing lifecycle
+journals stuck in `stopping` so a later `ensure` is admitted again.
+
+## Task
+
+Install the published release and update `.devrouter.yml` devrouter.version to
+0.0.66. No schema migration or configuration change is required. Do not change
+the committed configuration, delete registrations, containers, or source files,
+and do not reset lifecycle state manually: the recovery runs inside the existing
+canonical stop command under its normal locks and proofs.
+
+## Validation
+
+On a workspace whose stop was previously rejected with a retained provider
+identity error after a registration replacement, run the canonical
+`devrouter stop <path>` and confirm it reports the workspace stopped with the
+absence proof, then run `devrouter ensure <path>` and confirm admission
+succeeds. Confirm `devrouter status --json` shows the expected ready state and
+that no containers, volumes, or source files were removed beyond the normal
+stop contract. For workspaces that never hit the replacement case, confirm
+existing stop, ensure, and `devrouter doctor` behavior is unchanged.
+
+## Report
+
+Report the tested CLI version, the exact workspace path or synthetic fixture,
+the stop command result, the ensure result, route state after the run, and any
+diagnostic failure output verbatim. State explicitly whether the replacement
+case was exercised or only the unchanged retained path.

package/upgrade-prompts/0.0.67.md

@@ -0,0 +1,41 @@
+# Upgrade to devrouter 0.0.67
+
+This patch release makes the reliability journal incapable of deadlocking
+lifecycle commands and completes managed stop when a registration was deleted
+rather than replaced. It restores workspaces that every canonical command
+previously refused with "Lifecycle admission is blocked." after a saturated
+journal held a drained `INTERRUPTED` ensure.
+
+## Task
+
+Install the published release and update `.devrouter.yml` devrouter.version to
+0.0.67. No schema migration or configuration change is required. Do not change
+the committed configuration, delete registrations, containers, or source files,
+and do not reset lifecycle state manually. Recovery runs inside the existing
+canonical commands under their normal locks, ownership proofs, and journal
+accounting. If a command reports a live worker, wait for it or re-run later;
+`workspace journal settle` refuses while a worker outcome is still observable.
+
+## Validation
+
+On a workspace whose commands were refused with "Lifecycle admission is
+blocked." (saturated journal with a drained interrupted ensure), run
+`devrouter stop <path>` and confirm it completes — including the case where the
+Devsy registration was already deleted and every workload is positively absent
+— then run `devrouter ensure <path> --json` and confirm admission succeeds with
+routes published. On a record whose worker is provably gone and that still
+refuses progress, run `devrouter workspace journal settle <path> --json` and
+confirm it reports the settled operation, then retry `ensure`. Confirm refusal
+messages now name the blocking field and remediation. For workspaces that never
+hit the deadlock, confirm existing stop, ensure, exec, and `devrouter doctor`
+behavior is unchanged, and confirm a downgrade attempt (record written by a
+newer CLI than the installed one) fails with an explicit upgrade instruction
+instead of a mid-flight refusal.
+
+## Report
+
+Report the tested CLI version, the exact workspace path or synthetic fixture,
+each command result (stop, ensure, settle if used) with route state after the
+run, any diagnostic failure output verbatim, and whether the
+deleted-registration case, the saturated-journal case, or only the unchanged
+retained path was exercised.