@devrouter/cli 0.0.62 → 0.0.64

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@devrouter/cli",
-  "version": "0.0.62",
+  "version": "0.0.64",
   "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.63.md

@@ -0,0 +1,36 @@
+# Upgrade to devrouter 0.0.63
+
+This patch waits for healthy lifecycle workers before tooling execution and
+recovers stop when a saved baseline proves a linked Devsy runtime absent.
+
+## Task
+
+Install the published patch through the established workflow and update
+`.devrouter.yml` devrouter.version to 0.0.63. No schema migration is required.
+Refresh distributed agent guidance through the existing repository workflow.
+Installation does not require a runtime restart.
+
+## Validation
+
+Confirm the installed version and exact checkout/provider identity. On an
+already-running authorized runtime, run canonical `devrouter exec <checkout> --
+node --version` and verify completion without restarting services. Never replay
+an uncertain command. For an already-authorized absent-runtime recovery, use
+canonical `devrouter stop <checkout> --json`; verify stopped state, zero scoped
+routes and retained history. Run ensure only within the consumer owner's scope.
+A successful stop does not prove that subsequent startup succeeds.
+
+## Limits
+
+Absent-runtime recovery requires a valid saved baseline, exact linked-workspace
+ownership and Devsy selection. It does not override mixed-provider selection,
+repair legacy records without baselines, solve exhausted Docker network pools,
+enable capacity admission or provide complete OOM protection or autonomous agent
+recovery. Host process-inspection restrictions still require permitted host
+execution; never remove locks or weaken ownership checks to work around them.
+
+## Report
+
+Report installed version, exact checkout/provider, command outcome, preservation
+checks and final runtime/route state or explicit retention requirement. Separate
+released source, synthetic checks and live consumer acceptance.

package/upgrade-prompts/0.0.64.md

@@ -0,0 +1,34 @@
+# Upgrade to devrouter 0.0.64
+
+This patch lets canonical ensure wait for healthy lifecycle work on the same
+checkout and clarifies process-inspection permission failures.
+
+## Task
+
+Install the published patch and update `.devrouter.yml` devrouter.version to
+0.0.64. No schema migration or runtime restart is required. Refresh distributed
+agent guidance through the existing repository workflow.
+
+## Validation
+
+Confirm the installed version. On an authorized runtime, invoke ensure while a
+bounded tooling command is active. Verify waiting, preserved tooling exit status
+and successful ensure after completion when the lifecycle fence stays unchanged.
+Verify the exact runtime stops with zero routes and retained data when finished.
+A waiting exec refreshes runtime proof before admission; ensure establishes its
+runtime inside the worker. Stop or another fence change cancels the waiting
+invocation. Never replay an uncertain command.
+
+## Limits
+
+Waiting is bounded to thirty minutes, with no FIFO guarantee or persistent queue.
+Permission diagnostics direct agents to a permitted host context; they do not
+repair operating-system permissions or authorize lock removal. This patch does
+not solve network exhaustion, activate capacity admission, or claim complete OOM
+protection or autonomous agent recovery.
+
+## Report
+
+Report installed version, exact checkout/provider, command outcomes, retained
+runtime/data evidence and final runtime/route state. Separate published source,
+synthetic checks and live consumer acceptance.