@devrouter/cli 0.0.61 → 0.0.63

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@devrouter/cli",
-  "version": "0.0.61",
+  "version": "0.0.63",
   "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.62.md

@@ -0,0 +1,35 @@
+# Upgrade to devrouter 0.0.62
+
+This patch restores manual tooling access after interrupted preparation has drained,
+when the exact retained Devsy runtime can be proven. Each subsequent command keeps
+requiring fresh identity proof until a later ensure replaces the interrupted result.
+History rollover preserves the latest preparation result.
+
+## Task
+
+Install the published patch through the established workflow and update
+`.devrouter.yml` devrouter.version to 0.0.62. No schema migration is required.
+Refresh distributed agent guidance through the existing repository workflow.
+Do not restart or recreate a retained runtime to test tooling access.
+
+## Validation
+
+Confirm the installed version and exact checkout/provider identity. Run canonical
+`devrouter exec <checkout> -- node --version` once on an already-running runtime.
+Verify a known completion and unchanged configuration, managed state, routes,
+container identity and retained data. Preserve the interrupted ensure result.
+Never replay an uncertain command. Continue only already-authorized validation.
+
+## Limits
+
+Recovery requires Devsy with the plain local Docker command and exact ownership
+proof. It does not repair missing stop baselines, change provider configuration,
+resolve repository bootstrap errors, provide complete OOM protection, enable
+capacity admission, or establish autonomous agent recovery. Synthetic qualification
+is not live consumer acceptance. Installation alone does not change runtime state.
+
+## Report
+
+Report installed version, exact checkout/provider, command outcome, preservation
+checks, remaining limitations and final runtime/route state or existing retention
+lease. Distinguish released source from consumer acceptance.

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.