@devrouter/cli 0.0.58 → 0.0.60

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@devrouter/cli",
-  "version": "0.0.58",
+  "version": "0.0.60",
   "description": "Local dev routing CLI with shared Traefik reverse proxy",
   "author": "Roland Schlaefli",
   "homepage": "https://github.com/rschlaefli/devrouter#readme",
@@ -48,6 +48,7 @@
     "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",
     "test:process": "bash scripts/test-devrouter-process.sh",
     "check": "biome check .",
     "check:fix": "biome check --write .",

package/upgrade-prompts/0.0.59.md

@@ -0,0 +1,34 @@
+# Upgrade to devrouter 0.0.59
+
+This patch lets short-lived preparation children finish naturally after the
+foreground command exits successfully. The helper holds its lifecycle lock and
+checks cancellation during a bounded two-second drain window. Persistent children
+still prevent application startup and use existing owned-group cleanup.
+
+## Task
+
+Install the published patch and update `.devrouter.yml` devrouter.version to
+0.0.59 through the consumer workflow. No schema or dependency migration is needed.
+The next authorized ensure delivers the matching runtime helper automatically.
+Keep preparation synchronous and avoid detached sessions or process groups.
+
+## Validation
+
+On an authorized exact checkout, verify preparation finishes and the intended
+profile starts. Test application readiness independently from successful build
+output. Preserve data, stop task-owned runtimes and verify stopped provider status
+and zero exact routes. Do not start another task's runtime to repeat qualification.
+
+## Limits
+
+An isolated Linux fixture proves natural drainage of a short-lived child and
+continued rejection of persistent children. The reported Turbo descendant has
+not been identified, so this patch alone does not prove that consumer startup
+succeeds. Warm mount reconciliation, capacity admission and complete OOM protection
+remain outside this patch.
+
+## Report
+
+Report installed version, exact checkout/profile, preparation outcome, application
+readiness and final runtime state. Include remaining blockers without treating
+cached build success as successful environment startup.

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.