@devrouter/cli 0.0.52 → 0.0.54

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@devrouter/cli",
-  "version": "0.0.52",
+  "version": "0.0.54",
   "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.53.md

@@ -0,0 +1,42 @@
+# Upgrade to devrouter 0.0.53
+
+Managed process adapters can prepare dependencies synchronously before launching
+the background application. Exact managed Devsy stop can finish retained service
+shutdown after the primary has stopped.
+
+## Task
+
+1. Install the published CLI with `npm install -g @devrouter/cli@0.0.53` and
+   verify `devrouter-process --help` advertises `--prepare-command`.
+2. Bump `devrouter.version` in the consumer `.devrouter.yml` to `0.0.53` when
+   updating that repository's release pin. No schema migration is required.
+3. If dependency preparation currently consumes application readiness time,
+   adapt the repository-owned managed adapter to call
+   `devrouter-process ensure --prepare-command <command>` before its application
+   command. Keep preparation in the foreground; do not daemonize or detach.
+   Unchanged owned processes skip preparation. Explicit fingerprints remain
+   caller-owned and must encode any required preparation identity.
+4. For an approved retained-runtime recovery, preserve required Compose
+   interpolation settings and use `devrouter stop <checkout>`. A stopped primary
+   is not sufficient shutdown evidence: require every project container stopped
+   and zero checkout routes before guarded `ensure --repair`.
+
+## Validation
+
+Verify installed/configured versions with `devrouter -V --repo <checkout>`.
+Check preparation failure/cancellation, warm reuse, application readiness and
+exact shutdown for the affected consumer. Preparation must finish before its
+readiness deadline begins.
+
+Stop validates ownership, configuration and complete container membership on
+every mutation boundary. Changed, missing or unreadable evidence blocks cleanup.
+An original provider failure is still reported after successful residual service
+cleanup; inspect fresh state before choosing another operation. No containers,
+volumes or runtime data are deleted. Repair retains its unchanged-configuration
+guard and never creates missing resources or invokes provider bootstrap.
+
+## Report
+
+Report installed/configured versions, exact checkout and retained profile,
+preparation and readiness outcomes, all-container shutdown proof, route count,
+and remaining blockers. Installing the package alone is not live recovery proof.

package/upgrade-prompts/0.0.54.md

@@ -0,0 +1,26 @@
+# Upgrade to devrouter 0.0.54
+
+Retained configuration verification now resolves service `env_file` values before
+computing Compose hashes. This corrects false drift with affected Compose
+versions without relaxing ownership, file membership or container checks.
+
+## Task
+
+Install the published `@devrouter/cli@0.0.54` package and update the consumer's
+`devrouter.version` pin when adopting this release. No schema migration or
+generated configuration rewrite is required.
+
+## Validation
+
+For an approved exact runtime recovery, preserve the original Compose
+interpolation settings and use canonical stop and guarded repair. Real
+configuration changes and missing retained resources still block recovery.
+Never persist or print a resolved Compose model: it may contain credentials.
+Require complete retained-container shutdown, zero exact routes and separate
+application readiness proof. Adapter side effects retain their own approval
+boundaries; this release does not authorize cache deletion or data changes.
+
+## Report
+
+Report installed/configured versions, exact checkout/profile, command outcome,
+container and route state, application proof and remaining blockers.