@devrouter/cli 0.1.0 → 0.1.1

package/dist/devrouter-lifecycle-worker.js

@@ -5347,7 +5347,7 @@ function retain(session, previous) {
 
 // src/core/reliability-operation-store.ts
 function installedCliVersion() {
-  return true ? "0.1.0" : "0.0.0-dev";
+  return true ? "0.1.1" : "0.0.0-dev";
 }
 function compareCliVersions(left, right) {
   const parts = (value) => value.split(".").map((part) => Number.parseInt(part, 10) || 0);
@@ -7163,7 +7163,7 @@ function loadRepoConfig(repoPath, read2 = (file) => import_node_fs18.default.rea
   const config = parseConfig(parsed ?? {}, configPath);
   const requiredVersion = config.devrouter?.version;
   if (requiredVersion && !hasWarnedVersionMismatch) {
-    const cliVersion = true ? "0.1.0" : "0.0.0-dev";
+    const cliVersion = true ? "0.1.1" : "0.0.0-dev";
     if (cliVersion !== "0.0.0-dev" && compareSemver2(requiredVersion, cliVersion) > 0) {
       hasWarnedVersionMismatch = true;
       process.stderr.write(
@@ -11957,6 +11957,11 @@ function reliabilityRecovery(reason2, repoPath) {
     case "stop-incomplete":
     case "operation-unknown":
       return [`Run: devrouter stop ${repoPath}`, `Run: devrouter ensure ${repoPath} --repair`];
+    case "start-refused":
+      return [
+        `Run: devrouter doctor ${repoPath} to read the refused fixed host-port claim and its holder`,
+        `Stop the holding workspace or change this repository's own published binding, then run: devrouter ensure ${repoPath}`
+      ];
     case "unadmittable":
       return [
         `Run: devrouter stop ${repoPath}`,
@@ -11970,6 +11975,13 @@ function reliabilityRecovery(reason2, repoPath) {
       return [];
   }
 }
+function refusedManagedStart(result) {
+  if (result?.ok !== true) return false;
+  const value = result.value;
+  if (typeof value !== "object" || value === null) return false;
+  const conflicts = value.hostPortConflicts;
+  return Array.isArray(conflicts) && conflicts.length > 0;
+}
 function readReliabilityStatus(options) {
   let provider;
   try {
@@ -11989,7 +12001,7 @@ function readReliabilityStatus(options) {
     return void 0;
   }
   if (!record5) return void 0;
-  const reason2 = reliabilityAttention(record5.state);
+  const reason2 = reliabilityAttention(record5.state) ?? (record5.state.desired === "running" && refusedManagedStart(record5.result) ? "start-refused" : void 0);
   return {
     desired: record5.state.desired,
     phase: record5.state.phase,

package/dist/devrouter.js

@@ -4275,7 +4275,7 @@ function loadRepoConfig(repoPath, read2 = (file) => import_node_fs7.default.read
   const config = parseConfig(parsed ?? {}, configPath);
   const requiredVersion = config.devrouter?.version;
   if (requiredVersion && !hasWarnedVersionMismatch) {
-    const cliVersion = true ? "0.1.0" : "0.0.0-dev";
+    const cliVersion = true ? "0.1.1" : "0.0.0-dev";
     if (cliVersion !== "0.0.0-dev" && compareSemver(requiredVersion, cliVersion) > 0) {
       hasWarnedVersionMismatch = true;
       process.stderr.write(
@@ -6259,7 +6259,7 @@ var init_reliability_contract = __esm({
 
 // src/core/reliability-operation-store.ts
 function installedCliVersion() {
-  return true ? "0.1.0" : "0.0.0-dev";
+  return true ? "0.1.1" : "0.0.0-dev";
 }
 function compareCliVersions(left, right) {
   const parts = (value) => value.split(".").map((part) => Number.parseInt(part, 10) || 0);
@@ -15902,6 +15902,11 @@ function reliabilityRecovery(reason, repoPath) {
     case "stop-incomplete":
     case "operation-unknown":
       return [`Run: devrouter stop ${repoPath}`, `Run: devrouter ensure ${repoPath} --repair`];
+    case "start-refused":
+      return [
+        `Run: devrouter doctor ${repoPath} to read the refused fixed host-port claim and its holder`,
+        `Stop the holding workspace or change this repository's own published binding, then run: devrouter ensure ${repoPath}`
+      ];
     case "unadmittable":
       return [
         `Run: devrouter stop ${repoPath}`,
@@ -15915,6 +15920,13 @@ function reliabilityRecovery(reason, repoPath) {
       return [];
   }
 }
+function refusedManagedStart(result) {
+  if (result?.ok !== true) return false;
+  const value = result.value;
+  if (typeof value !== "object" || value === null) return false;
+  const conflicts = value.hostPortConflicts;
+  return Array.isArray(conflicts) && conflicts.length > 0;
+}
 function readReliabilityStatus(options) {
   let provider;
   try {
@@ -15934,7 +15946,7 @@ function readReliabilityStatus(options) {
     return void 0;
   }
   if (!record5) return void 0;
-  const reason = reliabilityAttention(record5.state);
+  const reason = reliabilityAttention(record5.state) ?? (record5.state.desired === "running" && refusedManagedStart(record5.result) ? "start-refused" : void 0);
   return {
     desired: record5.state.desired,
     phase: record5.state.phase,
@@ -21024,7 +21036,7 @@ Run several worktrees of one repo in parallel without host/route collisions. A *
 - **TLS**: namespaced hosts (\`web.<ws>.localhost\`) are not covered by the \`*.localhost\` wildcard; devrouter auto-extends the mkcert cert SANs for active hosts when TLS is enabled.
 - **devcontainer integration**: managed scaffolds list the base compose file, then \`\${localEnv:DEVCONTAINER_COMPOSE_OVERLAY:docker-compose.default.yml}\`; custom repositories may keep another default overlay. Selecting \`.devcontainer/docker-compose.devrouter.yml\` for linked worktrees must pass \`WORKSPACE\` and \`DEVROUTER_WORKSPACE\` across the combined base/overlay config and bind-mount \`\${DEVROUTER_GIT_COMMON_DIR}\` to the same absolute app-container path. The app exposes \`\${WORKSPACE}-app\`; the proxy uses \`upstream: \${WORKSPACE}-app:<port>\`.
 - **Lifecycle**: after one-time \`setup\`, use \`ensure .\` for both primary and linked checkouts; never branch manually on checkout kind or use live verify as startup. \`stop .\` is non-destructive; \`stop . --delete\` is explicit exact-owner cleanup without worktree removal; and \`exec . -- <command...>\` runs one-shot commands only in the exact running workspace runtime (DevPod or Devsy). Never substitute raw \`devpod up\`, \`stop\`, \`delete\`, or the Devsy equivalents: they bypass devrouter's machine-global ownership lock, which serializes provider mutations in a fair arrival-order queue and lets contenders wait up to thirty minutes with throttled stderr progress before failing with the queue position or holder PID and true durations. Runtime selection is path-aware: \`DEVROUTER_WORKSPACE_RUNTIME=devpod|devsy\` forces one runtime, an exact-path registry owner wins next, then the machine preference from \`devrouter setup --workspace-runtime\`, then installed-CLI auto-detection. \`workspace up\` creates linked worktrees; destructive worktree removal and GC remain ledger-scoped. Dirty or locked full down fails before side effects. For Devsy, run \`devrouter setup --yes --workspace-runtime devsy\` once per installed Devsy release, rerunning it after a Devsy update, so Devrouter acquires and verifies the official Linux agent in its own machine cache. Devrouter supports Devsy releases in the range >=1.16.2 <2.0.0 and refuses a release whose published asset has no SHA-256 digest. \`doctor\` reports \`ready\`, \`missing\`, \`stale\`, or \`invalid\` without network access, and \`ensure\` fails before the provider queue when readiness is not \`ready\`. An explicit \`DEVSY_AGENT_BINARY\` remains authoritative and must match the official asset for the installed release.
-- **Interrupted lifecycle**: ensure reconciles an interrupted or never-dispatched ensure after positive worker drainage and automatically repairs retained degraded runtimes. Unknown arbitrary exec is never replayed; explicit stop reconciles that uncertainty. Preserve journals and retained configuration when evidence is unavailable. This does not provide OOM prevention or capacity-managed automatic recovery.
+- **Interrupted lifecycle**: ensure reconciles an interrupted or never-dispatched ensure after positive worker drainage and automatically repairs retained degraded runtimes. Unknown arbitrary exec is never replayed; explicit stop reconciles that uncertainty. A start refused before any provider mutation \u2014 a fixed published host port already held by a running container \u2014 stays visible in \`status\` as a \`start-refused\` attention reason naming the read-only \`doctor\` check and the consumer-side fix; an explicit \`stop\` releases the intent and the reason, and a later admitted ensure clears it. Preserve journals and retained configuration when evidence is unavailable. This does not provide OOM prevention or capacity-managed automatic recovery.
 - **Managed process identity**: \`ensure\` executes an exact captured adapter snapshot. Default reuse includes command argv, workspace, and adapter SHA-256. Set \`DEVROUTER_PROCESS_FINGERPRINT_ENV\` only to comma-separated non-secret environment names whose values affect runtime identity; secret-like names are rejected and raw values are never persisted.
 - **Route state**: the versioned Traefik dynamic file is authoritative for both metadata and rendering. JSON is a compatibility mirror; valid headerless generations migrate automatically, while corrupt canonical metadata fails closed.
 - **Cleanup**: \`workspace cleanup --repo . --inactive-for 30d --json\` is a report-only, no-\`--yes\` report for managed linked workspaces. It joins ownership (\`present|missing|locked|conflict\`), workspace runtime registration, runtime state (\`running|stopped|busy|not-found|absent|unknown\`), checkout, route, advisory activity, and integration evidence without mutating the workspace runtime, routes, ownership, Git, Docker, applications, worktrees, or branches. Local DevPod/Devsy list/status checks always run; \`--check-merged\` alone enables read-only origin and matching GitHub/GitLab checks. Treat \`not-found\` as stale runtime after Docker pruning; busy, unavailable, or conflicting evidence suppresses destructive suggestions. Explicit \`gc\`/\`down\` can remove exact stale registration only after expected-ID \`NotFound\` proof and ownership revalidation. GC never removes Git worktrees, branches, or prune state. Git has no worktree-removal hook.
@@ -21299,7 +21311,7 @@ function buildOnboardingPrompt(options = {}) {
     "- if kind=app and runtime=proxy:",
     "  - HTTP-only optional readiness: { path: /api/health, statuses: [200], contentType: application/json }; statuses default to [200], explicit lists allow unique 2xx/4xx codes, never redirects. Paths stay on the configured host with no query, fragment, percent escapes, backslash or dot segments. Media types match their case-insensitive base type.",
     "  - Declared application readiness failures return applicationReadiness.status=application-error and a nonzero ensure exit, while retaining tooling and routes for application fixes; do not reset caches or recreate the provider. Absent readiness means legacy route liveness, not full application readiness.",
-    "  - A configured FIXED published host binding already held by a running container refuses managed ensure before any provider start (hostPortConflicts in --json, nonzero exit) naming the port, holder container, compose project, and owning workspace when attributable. Ephemeral host::container bindings are exempt. Never rewrite consumer ports to resolve a conflict: stop the holding workspace or use the consumer's own override, then ensure again. Unverifiable evidence also refuses.",
+    "  - A configured FIXED published host binding already held by a running container refuses managed ensure before any provider start (hostPortConflicts in --json, nonzero exit) naming the port, holder container, compose project, and owning workspace when attributable. Ephemeral host::container bindings are exempt. Never rewrite consumer ports to resolve a conflict: stop the holding workspace or use the consumer's own override, then ensure again. The refused start stays visible in `devrouter status` as a `start-refused` attention reason that names the read-only `doctor` check and the consumer-side fix; an explicit `stop` releases the intent and the reason, and a later admitted ensure clears it. Unverifiable evidence also refuses.",
     '  - upstream: "host:port" (an already-running port, e.g. a devcontainer published on 127.0.0.1:3000, or a container reachable by name on a shared Docker network such as `derivatives-db:5432`)',
     `  - upstream may use the \`${WORKSPACE_PLACEHOLDER}\` placeholder (e.g. \`${WORKSPACE_PLACEHOLDER}-app:3000\`) to target a per-workspace devcontainer alias; it is substituted with the resolved workspace token at runtime and re-validated. Do NOT put \`${WORKSPACE_PLACEHOLDER}\` in \`host\` (rejected) \u2014 the host is auto-namespaced.`,
     "  - managed `devrouter ensure` requires every HTTP/TCP proxy upstream to begin with the exact resolved workspace/project alias prefix before it mutates DevPod or routes",
@@ -23193,7 +23205,7 @@ function probeInstalledCliVersion(executable) {
 }
 function buildCliPathCheck(options = {}) {
   const id5 = "global.cli-path";
-  const runningVersion = options.runningVersion ?? (true ? "0.1.0" : "0.0.0-dev");
+  const runningVersion = options.runningVersion ?? (true ? "0.1.1" : "0.0.0-dev");
   if (runningVersion === "0.0.0-dev") {
     return {
       id: id5,
@@ -24041,7 +24053,7 @@ async function buildDoctorReport(options = {}) {
           suggestion: `Remedy ${expansionNotice.remedy.code}: set a named default profile other than '${expansionNotice.profile}'${remedyCandidates}.`
         });
       }
-      const cliVersion = true ? "0.1.0" : "0.0.0-dev";
+      const cliVersion = true ? "0.1.1" : "0.0.0-dev";
       const configVersion = config.devrouter?.version;
       const installedKnown = cliVersion !== "0.0.0-dev";
       const versionComparison = installedKnown && configVersion ? compareSemver(configVersion, cliVersion) : void 0;
@@ -30021,7 +30033,7 @@ var init_version = __esm({
 
 // src/cli.ts
 var import_commander = require("commander");
-var CLI_VERSION = true ? "0.1.0" : "0.0.0-dev";
+var CLI_VERSION = true ? "0.1.1" : "0.0.0-dev";
 var VERSION_FLAGS = /* @__PURE__ */ new Set(["-V", "--version"]);
 function withErrorHandling(action2) {
   return async (...args) => {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@devrouter/cli",
-  "version": "0.1.0",
+  "version": "0.1.1",
   "description": "Local dev routing CLI with shared Traefik reverse proxy",
   "author": "Roland Schlaefli",
   "homepage": "https://github.com/rschlaefli/devrouter#readme",
@@ -54,6 +54,7 @@
     "qualify:harness-journey": "./scripts/qualify-harness-journey.sh",
     "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",
     "test:process": "bash scripts/test-devrouter-process.sh",
     "check": "biome check .",
     "check:fix": "biome check --write .",

package/upgrade-prompts/0.1.1.md

@@ -0,0 +1,48 @@
+# Upgrade to devrouter 0.1.1
+
+This is a patch release on top of 0.1.0. It closes one way a managed environment
+could sit blocked without saying so: a start that admission refused on a fixed
+published host-port claim left the journal recording the intent as `running`
+while no runtime existed, so `devrouter status` reported a stable, drifting-free
+environment that could not progress.
+
+## What changed for a consumer
+
+- A managed `ensure` refused because a running container already holds a fixed
+  published host port now stays visible after the command exits. `devrouter
+  status` reports a `start-refused` attention reason with two recovery
+  commands: the read-only `devrouter doctor <repo>` check that names the
+  conflicting consumer binding and its holder, and the consumer-side fix
+  followed by `devrouter ensure <repo>`.
+- An explicit `devrouter stop <repo>` releases that intent and the reason, and a
+  later admitted ensure clears it. Nothing else about the refusal changed: the
+  start is still refused before any provider mutation, and live-worker,
+  unknown-ownership and surviving-resource checks still refuse fail-closed.
+- The release also carries `pnpm qualify:slow-dependency`, the developer
+  qualifier behind the Q06 dependency-recovery evidence. It is a repository
+  script and has no consumer-facing effect.
+
+## Task
+
+Use the published 0.1.1 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.
+
+## Validation
+
+Verify the resolved executable and installed version, then run `devrouter
+doctor` for the checkout and confirm `global.cli-path` reports one
+authoritative install. Run `devrouter status` and confirm the reported intent,
+phase and attention reason agree with the runtime you observe. When the reported
+reason is `start-refused`, resolve the named binding as the owner of that
+port — the shared router is never the side to stop — and keep each lifecycle
+operation's own terminal evidence separate from a status block or progress line.
+
+## Report
+
+Report the release revision, the executable and installed version, 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.