@devrouter/cli 0.0.50 → 0.0.52

package/package.json

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

@@ -0,0 +1,40 @@
+# Upgrade to devrouter 0.0.51
+
+Devrouter can now turn an exact profile selection into repository-owned literal
+bindings for CI or other automation without touching a runtime.
+
+1. Install `@devrouter/cli@0.0.51` on the host and bump `.devrouter.yml` to
+   `devrouter.version: 0.0.51`.
+2. Keep using `devrouter profile resolve` when automation only needs exact
+   selected resources. No consumer change is required for that command.
+3. When automation needs build arguments, readiness URLs, or other literals,
+   add a separate version-1 contract inside the repository and invoke
+   `devrouter profile plan --contract <repo-relative-yaml>`. Map every selectable
+   app, constrain dependency and service registries, and set the exact managed
+   process list for that workload.
+4. Treat bindings as data. Validate the keys expected by the consumer and pass
+   each value as a literal argument or input. Do not evaluate the values through
+   a shell or template engine.
+5. Refresh generated guidance with `devrouter repo agents` when the repository
+   stores Devrouter's generated `AGENTS.md` section or bundled skill.
+
+Verification:
+
+- Run `devrouter -V --repo <checkout>` and confirm the installed CLI and local
+  repository report `0.0.51`.
+- With no workspace running, run `devrouter profile plan --repo <checkout>
+  --profile <selection> --contract <repo-relative-yaml> --output <plan.json>
+  --json` and require exit status zero.
+- Require stdout and `<plan.json>` to contain the same schema-version-1 profile,
+  repository-relative `contractPath`, and expected literal `bindings`. Require
+  the file mode to be `0600`.
+- Reject unknown schema versions, missing mappings, unexpected binding keys, and
+  any resource selection outside the contract instead of widening the profile.
+
+Report template:
+
+- CLI/config version: `0.0.51`
+- Profile and contract: `<selection and repository-relative path>`
+- Literal binding plan: `<passed, not used, or details>`
+- Runtime side effects: `none`
+- Remaining blockers: `<none or details>`

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.