@devrouter/cli 0.0.51 → 0.0.53

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@devrouter/cli",
-  "version": "0.0.51",
+  "version": "0.0.53",
   "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.52.md

@@ -0,0 +1,34 @@
+# Upgrade to devrouter 0.0.52
+
+Managed process ownership now handles large environments correctly. Explicit
+`ensure --repair` recovers a retained degraded runtime without deleting its data
+or invoking provider bootstrap. Ordinary `ensure` retains its degraded-state guard.
+
+## Task
+
+1. Install the published CLI with `npm install -g @devrouter/cli@0.0.52`.
+2. Bump `devrouter.version` in the consumer `.devrouter.yml` to `0.0.52`.
+3. For an approved exact workspace recovery, inspect status and run
+   `devrouter ensure <checkout> --repair --json`. Omit the profile to reuse the
+   recorded profile. Preserve required non-secret Compose interpolation settings.
+4. Stop at ownership or configuration drift. Repair requires retained containers;
+   it never creates missing resources or changes the recorded profile.
+
+## Validation
+
+Verify installed/configured versions with `devrouter -V --repo <checkout>`.
+Repair accepts a stopped primary only with every project container explicitly
+stopped and no checkout routes. It starts retained IDs, including their existing
+entrypoints, then replays the current repository adapter. Owned processes may
+restart when fingerprints change. Failure can leave owned resources running.
+
+Require zero command exit status, ready services/processes, exact active route
+rules and targets, and no managed drift. Check the application separately.
+No live recovery is implied by installing the CLI. No schema migration or manual
+state-file edit is required.
+
+## Report
+
+Report installed/configured versions, exact checkout/profile, repair exit status,
+managed state, application check, and remaining blockers. Distinguish source
+checks from live runtime proof. Data deletion remains a separate explicit action.

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.