@devrouter/cli 0.0.73 → 0.0.75

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@devrouter/cli",
-  "version": "0.0.73",
+  "version": "0.0.75",
   "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.74.md

@@ -0,0 +1,35 @@
+# Upgrade to devrouter 0.0.74
+
+This patch fixes canonical stop after managed Devsy startup fails before
+registration, including Devsy-only installations without the legacy DevPod CLI.
+It preserves completed startup outcomes and refuses unknown ownership, live
+workers, surviving containers (including stopped containers), and routes.
+No configuration schema, command, or flag migration is required. Successful
+absence proof is reported as `runtimeAbsent: true` in stop JSON.
+
+## Task
+
+Use the published 0.0.74 CLI. Update `.devrouter.yml` devrouter.version to 0.0.74
+when consumer source changes are authorized; preserve another task's staged
+work. No DevPod installation or runtime-selection change is needed. Refresh
+generated agent guidance only when that repository's owner authorizes it.
+
+For an affected exact linked checkout, use canonical `devrouter stop <path>
+--json`. A completed journal alone is not evidence that resources are absent;
+do not edit lifecycle state or delete provider data to bypass a refusal. This
+fix does not recover retained-container identity drift or replace surviving
+resources.
+
+## Validation
+
+Verify the CLI version and exact checkout ownership. Run the supported stop
+under the checkout owner's recovery authority. Require successful absence proof
+and settled lifecycle state before retrying ensure. Revalidate the original port
+conflict before that retry, then require provider, application and route proof.
+Do not infer consumer recovery from package or regression tests.
+
+## Report
+
+Report the installed CLI version and release revision, exact checkout, stop
+result, lifecycle state, subsequent ensure and route/application evidence, or
+the precise fail-closed blocker. Confirm source/index and runtime data retention.

package/upgrade-prompts/0.0.75.md

@@ -0,0 +1,35 @@
+# Upgrade to devrouter 0.0.75
+
+This patch fixes canonical stop after initial managed Devsy startup is cancelled
+before managed runtime state is saved. Stop uses the exact drained ensure's
+recorded profile and validates complete live ownership and Compose configuration
+hashes. No configuration schema, command, flag or runtime-provider migration is
+required.
+
+## Task
+
+Use the published 0.0.75 CLI. Update `.devrouter.yml` devrouter.version to 0.0.75
+only when consumer source changes are authorized. Preserve staged work owned by
+another task. Refresh generated agent guidance only with the repository owner's
+authority. No DevPod installation is needed.
+
+For an affected exact checkout, use `devrouter stop <path> --json` with the same
+non-secret Compose inputs used at startup. Existing interrupted workspaces can
+recover when the exact operation history and all live configuration and ownership
+proofs remain available. Missing, unreadable, conflicting or changed evidence
+remains a refusal; never fabricate journal state or replace the selected profile
+with the default to bypass it. Stop is non-destructive and retains volumes.
+
+## Validation
+
+Verify the released CLI revision and exact checkout ownership. Let the checkout's
+runtime owner perform the canonical stop, require provider cessation and route
+removal proof, then verify stopped lifecycle state. Revalidate port conflicts
+before a new ensure and require its own provider, application and route proof.
+A successful stop or source test does not prove successful application startup.
+
+## Report
+
+Report release version/revision, exact checkout, producing stop result and
+lifecycle state, subsequent ensure evidence or precise refusal, and source/index
+preservation. Separate released source from live consumer acceptance.