@devrouter/cli 0.0.45 → 0.0.48

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@devrouter/cli",
-  "version": "0.0.45",
+  "version": "0.0.48",
   "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.46.md

@@ -0,0 +1,41 @@
+# Upgrade to devrouter 0.0.46
+
+Provider mutations under parallel agent load are now observable and drain a
+realistic queue of cold starts instead of failing after a silent minute.
+
+1. Install `@devrouter/cli@0.0.46` on the host and bump `.devrouter.yml` to
+   `devrouter.version: 0.0.46`.
+2. No schema or command changes. Keep using `devrouter ensure <checkout>` and
+   `devrouter workspace up <branch>`.
+3. When several parallel `ensure` runs contend for the machine-global
+   Devsy/DevPod mutation lock, contenders now wait up to thirty minutes in
+   fair arrival order and print one throttled stderr line every ten seconds.
+   Do not treat those lines as failures; a timeout names the queue position or
+   holder PID plus true durations and usually means the holder process died
+   mid-start or a direct provider command bypassed devrouter.
+4. If a Devsy start fails with the agent-binary acquisition remediation,
+   allow Devsy to download its agent binary or export `DEVSY_AGENT_BINARY`
+   pointing at a verified official Devsy agent binary matching this platform
+   and Devsy version. Do not point it at an arbitrary binary.
+5. A checkout whose persisted managed state names a Compose project that no
+   longer has any exact containers can now rebaseline on its currently
+   observed exact workspace. If prior-project containers still exist, repair
+   that drift explicitly; Devrouter continues to fail closed.
+
+Verification:
+
+- Run `devrouter -V --repo <checkout>` and confirm the installed CLI and
+  local repository report `0.0.46`.
+- Start two linked checkouts concurrently with `devrouter ensure` and require
+  both to succeed with visible wait progress on the second, or a timeout
+  error that names the holder PID and durations.
+- When changing a checkout's workspace runtime, run one capability-only and
+  one routed profile and inspect `managedRuntime.drift`; require an empty list.
+
+Report template:
+
+- CLI/config version: `0.0.46`
+- Parallel ensure contention: `<passed or details>`
+- Wait progress output: `<observed or details>`
+- Managed-state rebaseline/profile transition: `<passed or details>`
+- Remaining blockers: `<none or details>`

package/upgrade-prompts/0.0.48.md

@@ -0,0 +1,44 @@
+# Upgrade to devrouter 0.0.48
+
+Devrouter now owns deterministic Devsy agent readiness, exposes profile
+resolution to automation, and proves that Traefik loaded managed routes before
+declaring a runtime ready.
+
+1. Install `@devrouter/cli@0.0.48` on the host and bump `.devrouter.yml` to
+   `devrouter.version: 0.0.48`.
+2. When Devsy is selected, run
+   `devrouter setup --yes --workspace-runtime devsy` once. This acquires and
+   verifies the pinned official agent. An explicit `DEVSY_AGENT_BINARY` remains
+   authoritative and must match a pinned asset.
+3. Run `devrouter doctor --repo <checkout> --json` and require
+   `global.devsy-agent` to report `ready` before starting a Devsy workspace.
+   Doctor remains network-free and does not expose the agent path.
+4. Use `devrouter profile resolve --repo <checkout> --profile <selection> --json`
+   when CI or another tool needs exact apps, dependencies, readiness targets,
+   managed services, and process markers without runtime side effects. Reject
+   invalid selections and unknown report schemas instead of widening the
+   requested profile.
+5. Keep using `devrouter ensure <checkout>`. Managed startup now proves exact
+   HTTP and TCP file-provider routers through Traefik's API. A missed hot reload
+   triggers one serialized Traefik-only restart; persistent absence fails closed
+   with the missing router names.
+
+Verification:
+
+- Run `devrouter -V --repo <checkout>` and confirm the installed CLI and local
+  repository report `0.0.48`.
+- Run `devrouter doctor --repo <checkout> --json` and require zero errors plus
+  `global.devsy-agent: ready` when Devsy is selected.
+- Run `devrouter profile resolve --repo <checkout> --profile <selection> --json`
+  with no workspace running and verify the schema-versioned exact resource set.
+- Start one safe representative profile with `devrouter ensure`, verify its
+  expected routes and zero profile drift, then stop that exact checkout and
+  require zero remaining routes.
+
+Report template:
+
+- CLI/config version: `0.0.48`
+- Devsy agent readiness: `<ready, not selected, or details>`
+- Profile resolution: `<passed or details>`
+- Representative route proof and stop: `<passed, deferred, or details>`
+- Remaining blockers: `<none or details>`