@devrouter/cli 0.0.77 → 0.0.79

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@devrouter/cli",
-  "version": "0.0.77",
+  "version": "0.0.79",
   "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.78.md

@@ -0,0 +1,35 @@
+# Upgrade to devrouter 0.0.78
+
+Provider queue diagnostics now distinguish the first waiter from the observed
+lock holder. They report held duration and remaining acquisition time, including
+that acquisition timeout does not stop the holder. Missing or changing evidence
+reports an unknown holder. Acquisition, ownership, cancellation and startup
+behavior remain unchanged. No schema, command, flag or environment migration is
+needed.
+
+## Task
+
+Use the published 0.0.78 CLI. Update the repository devrouter.version metadata
+only when consumer source changes are authorized. Preserve staged work and the
+existing runtime owner. Refresh generated agent guidance only with its owner's
+authority. No generated runtime configuration or journal rewrite is needed.
+
+For a queued operation, distinguish its queue leader from the observed provider
+lock holder. An acquisition timeout describes the waiting operation; it does not
+cancel the holder. Unknown holder evidence requires inspection, not lock removal.
+Historical configuration-drift repair remains subject to its existing proof gates.
+
+## Validation
+
+Verify the resolved executable and installed version. Use existing captured or
+synthetic queue evidence to check holder attribution and timeout semantics; do
+not start an unrelated workspace to exercise diagnostics. Require independent
+terminal evidence for any already-authorized lifecycle operation. Preserve
+live-worker, exact ownership, configuration and surviving-resource checks.
+
+## Report
+
+Report release revision, executable, installed version, queue versus holder
+evidence, and terminal operation result where available. Keep source and package
+validation separate from consumer readiness or recovery. Record unknowns without
+interpreting diagnostic messages as permission to cancel or remove resources.

package/upgrade-prompts/0.0.79.md

@@ -0,0 +1,46 @@
+# Upgrade to devrouter 0.0.79
+
+This release hardens the managed lifecycle. An environment whose containers were
+removed outside Devrouter can now settle its stop, corrective actions are bounded
+by the declared policy, and a host Devsy CLI newer than the verified pin no longer
+blocks a managed start. `devrouter status` explains the durable intent of a
+managed checkout, and `ensure`/`stop` report bounded stage progress on stderr.
+Defaults stay protected: capacity admission, parking consent and automatic
+recovery remain inert unless an operator enables them.
+
+## Task
+
+Use the published 0.0.79 CLI. Update the repository `devrouter.version` metadata
+only when consumer source changes are authorized, and refresh generated agent
+guidance only with its owner's authority. No schema, command, flag, environment
+or journal migration is needed, and the upgrade rewrites no runtime state.
+
+Two operating changes matter for scripts and agents:
+
+- `ensure` and `stop` now write bounded progress lines to stderr. Parse JSON from
+  stdout only; do not merge the streams before parsing.
+- A controller that has written a version-2 consumer snapshot or a human
+  protection pin refuses older CLIs. Keep 0.0.79 or newer for that journal; do
+  not delete snapshots or pins to downgrade.
+
+When the host Devsy CLI is newer than the verified pin, Devrouter injects no
+agent and the host CLI governs its own. An older or unparseable CLI stays
+unsupported, and an explicit `DEVSY_AGENT_BINARY` keeps its exact validation.
+
+## Validation
+
+Verify the resolved executable and installed version. Run `devrouter doctor` and
+confirm `global.devsy-agent` reports `ready` (a non-blocking drift warning is
+expected when the host CLI is newer) and that `repo.cli-outdated` shows the
+installed version and repository pin separately. Run `devrouter status` for an
+authorized managed checkout and confirm the reported intent, phase and attention
+reason agree with the runtime you observe. Require each lifecycle operation's own
+terminal evidence; a status block or progress line is not stop or ensure success.
+
+## Report
+
+Report release revision, executable, installed version, the Devsy agent and
+CLI/repo version diagnostics, the status block for any affected checkout, and the
+terminal result of any authorized lifecycle operation. Keep source and package
+validation separate from consumer readiness or recovery, and record unknown
+ownership or surviving resources as unresolved rather than as recovered.