@devrouter/cli 0.0.59 → 0.0.61

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@devrouter/cli",
-  "version": "0.0.59",
+  "version": "0.0.61",
   "description": "Local dev routing CLI with shared Traefik reverse proxy",
   "author": "Roland Schlaefli",
   "homepage": "https://github.com/rschlaefli/devrouter#readme",
@@ -48,6 +48,8 @@
     "test": "vitest run && pnpm test:process",
     "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.60.md

@@ -0,0 +1,40 @@
+# Upgrade to devrouter 0.0.60
+
+This patch retains a coherent degraded candidate after an external reset and
+failed recreation when exact ownership, complete service population and unchanged
+configuration are proven. Existing ordinary ensure can recover that record.
+It also includes foreground controller observation of independent infrastructure
+and application readiness, with bounded subscriptions and durable session fencing.
+
+## Task
+
+Install the published patch through the existing consumer workflow and update
+`.devrouter.yml` devrouter.version to 0.0.60. No schema migration is required.
+Refresh distributed agent guidance with the repository's established workflow.
+Use ordinary ensure on the authorized exact checkout; preserve data and recorded
+ownership. Never manufacture fingerprints or adopt another checkout's containers.
+
+## Validation
+
+Verify the requested profile, exact provider/container ownership, preparation and
+application readiness separately. If recreation fails, inspect whether the exact
+candidate was proven and retained as degraded. Retry ordinary ensure through its
+supported recovery path. Incomplete proof remains an explicit diagnostic.
+
+For ongoing observation, use the documented foreground controller session flow;
+verify infrastructure readiness remains distinct from an application error.
+Stop the exact task runtime after qualification and verify stopped provider state
+and zero exact routes, retaining data.
+
+## Limits
+
+Source and installed synthetic-provider tests cover these contracts. They do not
+prove the original other-host reset incident, complete OOM protection, capacity
+admission or autonomous agent recovery. Controller observation does not repair or
+schedule workloads. Live acceptance requires the existing runtime owner's evidence.
+
+## Report
+
+Report installed version, exact checkout/profile, ownership and recovery results,
+application versus tooling readiness, retained data and final stopped/route state.
+Identify incomplete or synthetic-only evidence without expanding release claims.

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.