@devrouter/cli 0.0.64 → 0.0.66

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@devrouter/cli",
-  "version": "0.0.64",
+  "version": "0.0.66",
   "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.65.md

@@ -0,0 +1,39 @@
+# Upgrade to devrouter 0.0.65
+
+This feature release adds managed-workspace network capacity support: read-only
+capacity and retained-ownership diagnostics plus opt-in daemon-bound subnet
+allocation for new managed linked-workspace Compose networks.
+
+## Task
+
+Install the published release and update `.devrouter.yml` devrouter.version to
+0.0.65. No schema migration is required. Opting a repository in needs two
+operator steps: install `~/.config/devrouter/network-policy.json` naming
+private pools, exclusions and permitted prefixes for the exact Docker daemon,
+then add `managedRuntime.network` to the repository configuration. Repository
+configuration cannot select address ranges. Adding a policy changes nothing for
+existing workspaces, networks or provider registrations.
+
+## Validation
+
+Run `devrouter doctor --repo <checkout> --json` and confirm the read-only
+network capacity report. On an authorized runtime with a valid policy, start a
+new managed linked workspace and verify the ignored generated Compose overlay,
+the persisted subnet claim, exact provider destination reuse, and subnet
+retention across stop and resume. Verify failure paths retain claims and never
+delete networks, containers or workspaces. Stop the exact runtime afterwards
+and confirm zero routes with retained data.
+
+## Limits
+
+Allocation requires complete route and daemon evidence; virtualized contexts
+such as OrbStack stay diagnostics-only until guest routes are qualified.
+Existing `/24` networks are never subdivided or migrated. Stopping a workspace
+or removing its worktree does not release a subnet, and cleanup remains
+report-only. Without a policy, allocation behavior is unchanged.
+
+## Report
+
+Report installed version, policy presence without its contents, diagnostic
+output, allocation outcomes with synthetic receipts, and any retained claims or
+resources. Separate published source, synthetic checks and live runtime proof.

package/upgrade-prompts/0.0.66.md

@@ -0,0 +1,31 @@
+# Upgrade to devrouter 0.0.66
+
+This patch release completes managed stop when Devsy replaces a workspace
+registration UID after the workload is positively absent, releasing lifecycle
+journals stuck in `stopping` so a later `ensure` is admitted again.
+
+## Task
+
+Install the published release and update `.devrouter.yml` devrouter.version to
+0.0.66. No schema migration or configuration change is required. Do not change
+the committed configuration, delete registrations, containers, or source files,
+and do not reset lifecycle state manually: the recovery runs inside the existing
+canonical stop command under its normal locks and proofs.
+
+## Validation
+
+On a workspace whose stop was previously rejected with a retained provider
+identity error after a registration replacement, run the canonical
+`devrouter stop <path>` and confirm it reports the workspace stopped with the
+absence proof, then run `devrouter ensure <path>` and confirm admission
+succeeds. Confirm `devrouter status --json` shows the expected ready state and
+that no containers, volumes, or source files were removed beyond the normal
+stop contract. For workspaces that never hit the replacement case, confirm
+existing stop, ensure, and `devrouter doctor` behavior is unchanged.
+
+## Report
+
+Report the tested CLI version, the exact workspace path or synthetic fixture,
+the stop command result, the ensure result, route state after the run, and any
+diagnostic failure output verbatim. State explicitly whether the replacement
+case was exercised or only the unchanged retained path.