@devrouter/cli 0.0.55 → 0.0.57

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@devrouter/cli",
-  "version": "0.0.55",
+  "version": "0.0.57",
   "description": "Local dev routing CLI with shared Traefik reverse proxy",
   "author": "Roland Schlaefli",
   "homepage": "https://github.com/rschlaefli/devrouter#readme",
@@ -47,6 +47,7 @@
     "dev": "tsx src/cli.ts",
     "test": "vitest run && pnpm test:process",
     "test:package": "./scripts/package-smoke.sh",
+    "qualify:lifecycle": "node --import tsx scripts/qualify-lifecycle.ts",
     "test:process": "bash scripts/test-devrouter-process.sh",
     "check": "biome check .",
     "check:fix": "biome check --write .",

package/upgrade-prompts/0.0.56.md

@@ -0,0 +1,52 @@
+# Upgrade to devrouter 0.0.56
+
+Ordinary managed ensure automatically recovers eligible retained degraded runtimes.
+Durable lifecycle workers preserve stop precedence and proven command outcomes;
+uncertain arbitrary commands are never silently replayed. Current stopped state
+is reported separately from historical transition failures.
+
+HTTP proxy apps may declare a readiness path, accepted statuses and content type.
+A failed application check reports application-error and exits nonzero while
+retaining tools and routes for application repair. Unapplied Compose service edits
+no longer prevent exact retained Devsy stop; startup configuration checks remain.
+
+## Task
+
+Install the published patch and update `.devrouter.yml` devrouter.version to
+0.0.56. Refresh bundled agent guidance through the existing repository workflow.
+No dependency or database migration is required. Adopt application readiness only
+for a bounded read-only endpoint that represents the desired application contract:
+
+```yaml
+readiness:
+  path: /api/health
+  statuses: [200]
+  contentType: application/json
+```
+
+This field applies to HTTP proxy apps. Existing route-only apps keep their prior
+behavior. Do not treat route reachability as authenticated journey evidence.
+
+## Validation
+
+On an authorized exact checkout, verify warm ensure, declared application health,
+tooling availability after application failure, and non-destructive stop/resume.
+Confirm retained synthetic records and generated preparation state where relevant.
+After checks, stop the exact runtime and independently verify provider Stopped and
+zero exact routes. Preserve data, caches and other environments.
+
+Do not replay unknown commands, remove ownership records, bypass stop fences or
+reset data to force readiness. Ordinary ensure owns supported retained recovery;
+an agent should not need an explicit repair for eligible degraded state.
+
+## Limits
+
+This release does not activate a machine controller, global capacity admission,
+continuous autonomous recovery or coding-harness enrollment. It does not claim
+complete OOM protection. Unknown ownership and uncertain execution remain explicit.
+
+## Report
+
+Report installed and configured versions, exact checkout/profile, automatic actions,
+application and tooling proof, warm reuse, retained records, final provider/route
+state and any unsupported cases. Distinguish synthetic tests from live proof.

package/upgrade-prompts/0.0.57.md

@@ -0,0 +1,33 @@
+# Upgrade to devrouter 0.0.57
+
+This patch restores managed ensure with comma-separated profiles. Lifecycle events,
+current state and retained request history accept profile selections separately
+from workspace and operation identifiers. Repository resolution still validates
+configured profiles and combines their selected resources.
+
+## Task
+
+Install the published 0.0.57 patch and update `.devrouter.yml` devrouter.version to
+0.0.57 through the consumer repository workflow. No schema or database migration
+is required. Keep the intended profile selection; do not substitute full or delete
+runtime state to avoid the earlier validator failure.
+
+## Validation
+
+Use repository profile resolution to check the intended combined selection. Run
+managed ensure only on an authorized exact checkout, retaining its data and
+bindings. Report the resulting application and runtime outcomes separately from
+successful selection validation. Stop only runtimes owned by the validation task,
+then verify their provider status and zero exact routes.
+
+## Limits
+
+This patch fixes pre-dispatch profile validation. It does not introduce a host-side
+preparation hook, warm Compose drift reconciliation, capacity admission, a
+controller, autonomous agent recovery or complete OOM protection.
+
+## Report
+
+Report installed/configured versions, exact profile selection, validation result
+and any separately authorized runtime evidence. Identify retained runtime leases
+without ending another task's runtime.