@devrouter/cli 0.1.1 → 0.1.3

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@devrouter/cli",
-  "version": "0.1.1",
+  "version": "0.1.3",
   "description": "Local dev routing CLI with shared Traefik reverse proxy",
   "author": "Roland Schlaefli",
   "homepage": "https://github.com/rschlaefli/devrouter#readme",
@@ -55,6 +55,11 @@
     "qualify:codex-journey": "DR_JOURNEY_HARNESS=codex ./scripts/qualify-harness-journey.sh",
     "qualify:non-node": "./scripts/qualify-non-node-consumer.sh",
     "qualify:slow-dependency": "./scripts/qualify-slow-dependency-recovery.sh",
+    "qualify:killed-runtime": "./scripts/qualify-killed-runtime-recovery.sh",
+    "qualify:cohorts": "node --import tsx scripts/qualify-lifecycle-cohorts.ts",
+    "qualify:preparation": "node --import tsx scripts/qualify-process-preparation.ts",
+    "qualify:profiles": "node --import tsx scripts/qualify-profile-alternation.ts",
+    "qualify:host-suspend": "node --import tsx scripts/qualify-host-suspend.ts",
     "test:process": "bash scripts/test-devrouter-process.sh",
     "check": "biome check .",
     "check:fix": "biome check --write .",

package/upgrade-prompts/0.1.2.md

@@ -0,0 +1,57 @@
+# Upgrade to devrouter 0.1.2
+
+This is a patch release on top of 0.1.1. It carries the post-release reliability
+review corrections: truthful recovery guidance, a harness gate that honors its
+full wait budget and recognizes its own lifecycle commands in every supported
+invocation form, evidence-accurate hook wording, bounded cause-and-location
+diagnostics for unprovable capacity history, and a content-digest fence on
+capacity snapshot replacement.
+
+## What changed for a consumer
+
+- The recovery line a refused managed start prints now reads `devrouter doctor
+  --repo <checkout>` (single-quoted when the path needs it) instead of a
+  positional path that `doctor` never accepted. Stored guidance that quotes the
+  old form should be refreshed.
+- The harness gate (`devrouter harness gate`, wired as a PreToolUse hook) now
+  recognizes `devrouter` lifecycle commands as direct executables and through
+  the `npx`, `pnpm exec`, `npm exec` and `yarn` launchers, including
+  `env` and assignment prefixes. During a transition, `devrouter status`,
+  `stop` and `ensure` reach their own bounded checks instead of being deferred
+  or refused as unrelated calls. Unrelated calls still defer or refuse as
+  before.
+- A gated call under a budget now waits the whole budget: the gate observes once
+  more at the deadline instead of refusing early when the next poll interval
+  would overrun it.
+- Hook output no longer reports "environment settled" for passthrough,
+  unmanaged, invalid-payload or unavailable evidence; each decision says what it
+  actually observed.
+- `devrouter doctor` names the bounded cause and the exact journal entry when
+  capacity history is unprovable, and the network-capacity check names the
+  missing evidence inputs, so the operator can act without guessing.
+
+## Task
+
+Use the published 0.1.2 CLI. Refresh consumer-side guidance that quotes the old
+positional recovery command, and update the repository `devrouter.version`
+metadata only when consumer source changes are authorized. No schema, command,
+flag, environment or journal migration is needed, and the upgrade rewrites no
+runtime state.
+
+## Validation
+
+Verify the resolved executable and installed version with `devrouter -V`, then
+run `devrouter doctor --repo <checkout>` and confirm `global.cli-path`
+reports one authoritative install. For an environment whose harness hook uses
+`devrouter harness gate`, run one gated lifecycle command during a transition
+and confirm it reaches its own check. When `doctor` reports unprovable capacity
+history, follow the named cause-keyed recovery instead of deleting journal
+state.
+
+## Report
+
+Report the release revision, the executable and installed version, the doctor
+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.

package/upgrade-prompts/0.1.3.md

@@ -0,0 +1,55 @@
+# Upgrade to devrouter 0.1.3
+
+This is a patch release on top of 0.1.2. It carries the managed-stop and
+managed-profile corrections found while qualifying the reliability roadmap, a
+repaired Docker network inventory template, and one measured efficiency change
+that removes a redundant provider startup per registry read. No schema, CLI
+flag, environment variable or journal migration changes.
+
+## What changed for a consumer
+
+- `stop --delete` settles three shapes that a 0.1.2 install could leave stuck in
+  `stopping`, where `workspace journal settle` reported already-settled and every
+  later `ensure` was refused: a primary checkout whose Devsy registration was
+  already gone, a managed environment whose ignored generated profile had been
+  removed, and a stop that refused after the managed population changed outside
+  devrouter. Each correction keeps the fail-closed refusal whenever ownership,
+  identity or surviving resources are unproven.
+- A checkout held up by one of those shapes recovers with the supported flow once
+  this CLI is installed: run `devrouter stop <checkout> --delete`, or
+  `devrouter workspace journal settle <checkout>` when no lifecycle worker can be
+  running. Do not delete provider registrations or edit journal files by hand.
+- The Docker network inventory template is one complete JSON object per network
+  again, so the capacity check reads the daemon's networks instead of reporting
+  unknown inventory and refusing managed allocation.
+- Lifecycle actions start the provider CLI fewer times: on the retained
+  qualification fixture a cold or retained `ensure` fell from 26 to 18 provider
+  invocations and `stop --delete` from 22 to 16, with the same ownership proofs
+  and Docker work.
+- `status` and `doctor` report an unwound nested mount as a bounded non-blocking
+  observation, and read a container's mount table only when a configured mount
+  nests.
+
+## Task
+
+Use the published 0.1.3 CLI. Update the repository `devrouter.version` metadata
+only when consumer source changes are authorized. No schema, command, flag,
+environment or journal migration is needed, and the upgrade rewrites no runtime
+state; a checkout already stuck in `stopping` is released by running the
+supported stop or settlement command.
+
+## Validation
+
+Verify the resolved executable and installed version with `devrouter -V`, then
+run `devrouter doctor --repo <checkout>` and confirm `global.cli-path` reports
+one authoritative install. For a checkout that an earlier version left in
+`stopping`, run the supported stop or settlement flow and confirm the terminal
+provider and route state. Record unknown ownership or surviving resources as
+unresolved rather than as recovered.
+
+## Report
+
+Report the release revision, the executable and installed version, the doctor
+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.