@devrouter/cli 0.0.57 → 0.0.59

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@devrouter/cli",
-  "version": "0.0.57",
+  "version": "0.0.59",
   "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.58.md

@@ -0,0 +1,41 @@
+# Upgrade to devrouter 0.0.58
+
+This patch permits recovery directly into a different requested profile after
+retained ownership proof. Failed processes excluded by that profile no longer
+have to start first. Failed transitions preserve degraded evidence and data.
+
+## Task
+
+Install the published patch and update `.devrouter.yml` devrouter.version to
+0.0.58 through the consumer repository workflow. No database migration is needed.
+Refresh generated agent guidance when the repository distributes it.
+
+Repositories that generate Compose inputs before inspection may configure
+`managedRuntime.devcontainer.prepareCommand` as a literal argv array. The command
+runs on the host in the checkout root, once per ensure, with a sixty-second bound.
+Keep it in the foreground, preserve `.devrouter.yml`, and leave diagnostics
+read-only. Output is suppressed; report failures through the command exit status.
+
+## Validation
+
+Resolve the intended profile and ensure only an authorized exact checkout. For
+degraded recovery, verify the requested resources start without replaying excluded
+processes. Verify host preparation before Compose inspection using a repository
+generator whose output can be checked without exposing values. Separate successful
+generation from applying changed mounts to an existing container.
+
+Check application readiness and tooling separately. Retain data and stop only
+task-owned runtimes, then verify stopped provider status and zero exact routes.
+
+## Limits
+
+This release does not implement warm mount reconciliation, capacity admission,
+controller observation, autonomous agent recovery or complete OOM protection.
+Ownership conflicts remain actionable errors; they never authorize destructive
+repair or changing another task's runtime.
+
+## Report
+
+Report installed/configured versions, exact checkout and profile, preparation
+result, requested-profile recovery evidence, application/tooling outcomes and
+final runtime status. Identify any remaining unverified consumer behavior.

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.