@devrouter/cli 0.0.60 → 0.0.62

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@devrouter/cli",
-  "version": "0.0.60",
+  "version": "0.0.62",
   "description": "Local dev routing CLI with shared Traefik reverse proxy",
   "author": "Roland Schlaefli",
   "homepage": "https://github.com/rschlaefli/devrouter#readme",
@@ -49,6 +49,7 @@
     "test:package": "./scripts/package-smoke.sh",
     "qualify:lifecycle": "node --import tsx scripts/qualify-lifecycle.ts",
     "qualify:controller": "node --import tsx scripts/qualify-controller.ts",
+    "qualify:stop-drift": "node --import tsx scripts/qualify-config-drift-stop.ts",
     "test:process": "bash scripts/test-devrouter-process.sh",
     "check": "biome check .",
     "check:fix": "biome check --write .",

package/upgrade-prompts/0.0.61.md

@@ -0,0 +1,40 @@
+# Upgrade to devrouter 0.0.61
+
+This patch keeps manual ensure and exec usable after settled operation history
+reaches its bound. Managed Devsy startup records exact stop ownership before
+application readiness on supported local Unix Docker endpoints. With that recorded
+baseline, ordinary stop tolerates changed or missing repository configuration
+without deleting containers or volumes.
+
+## Task
+
+Install the published patch through the established consumer workflow and update
+`.devrouter.yml` devrouter.version to 0.0.61. No repository schema migration is
+required. Refresh distributed agent guidance through the established workflow.
+
+Use canonical ensure, exec and stop for the authorized exact checkout. Stop
+baselines are captured by a qualifying startup; installation alone does not create
+them for older runtimes. Do not fabricate ownership records or replay a failing
+post-create hook to obtain a baseline.
+
+## Validation
+
+Verify installed version, exact checkout/profile and provider identity. For a
+baseline-backed runtime, verify stop after configuration drift, retained-data
+resume, and final stopped provider state with zero exact routes. Keep existing
+passing evidence only where source, toolchain and relevant environment agree.
+
+## Limits
+
+Legacy records without a baseline retain the existing configuration-dependent
+stop path. Other recognized Docker transports retain legacy behavior with a
+notice. Invalid or mismatched ownership does not fall back to weaker proof.
+This patch does not repair repository bootstrap/database errors, establish data
+preservation after a destructive hook, prevent every provider replacement, enable
+capacity admission, or provide complete OOM protection or autonomous recovery.
+
+## Report
+
+Report installed version, exact checkout/profile, whether a stop baseline existed,
+checks performed, retained-data evidence, final provider and route state, and any
+remaining recovery limitation. Distinguish fixture proof from consumer acceptance.

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.