@devrouter/cli 0.0.35 → 0.0.37

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@devrouter/cli",
-  "version": "0.0.35",
+  "version": "0.0.37",
   "description": "Local dev routing CLI with shared Traefik reverse proxy",
   "author": "Roland Schlaefli",
   "homepage": "https://github.com/rschlaefli/devrouter#readme",
@@ -45,6 +45,7 @@
     "build": "tsup",
     "dev": "tsx src/cli.ts",
     "test": "vitest run && pnpm test:process",
+    "test:package": "./scripts/package-smoke.sh",
     "test:process": "bash scripts/test-devrouter-process.sh",
     "check": "biome check .",
     "check:fix": "biome check --write .",
@@ -57,6 +58,7 @@
     "routing:smoke": "./scripts/smoke-routing.sh",
     "devcontainer:smoke": "./scripts/smoke-devcontainer.sh",
     "workspace:lifecycle-smoke": "./scripts/smoke-workspace-lifecycle.sh",
+    "workspace:cleanup-smoke": "./scripts/smoke-workspace-cleanup-report.sh",
     "bench:startup": "zsh -lc 'set -euo pipefail; echo \"=== dev --help (x5) ===\"; for i in {1..5}; do /usr/bin/time -p node dist/devrouter.js --help >/dev/null; done; echo \"=== dev app add --help (x5) ===\"; for i in {1..5}; do /usr/bin/time -p node dist/devrouter.js app add --help >/dev/null; done; echo \"=== dev status --json (x3, best effort) ===\"; for i in {1..3}; do /usr/bin/time -p node dist/devrouter.js status --json >/dev/null || true; done'",
     "typecheck": "tsc --noEmit",
     "bootstrap": "pnpm install && pnpm install:local",

package/upgrade-prompts/0.0.36.md

@@ -0,0 +1,31 @@
+# Upgrade to devrouter 0.0.36
+
+Devrouter gains a report-only inspection path for managed linked workspaces: `devrouter workspace cleanup` joins ownership, DevPod registration and runtime, checkout, route, advisory activity, and integration evidence, and the opt-in `--measure-size` adds per-workspace storage consumption. Configuration, ownership, and route-state schemas are unchanged; only the cleanup `--json` report version moves, from `1` to `2`.
+
+1. Install `@devrouter/cli@0.0.36` on the host and bump `.devrouter.yml` to `devrouter.version: 0.0.36`.
+2. If any agent workflow parses cleanup `--json`, accept `schemaVersion: 2`. Fields are additive, but a strict equality check against `1` now fails.
+3. Use `devrouter workspace cleanup --repo <repo> --inactive-for 30d [--json]` to decide what is worth reclaiming. It has no `--yes` and no apply mode, and it never touches DevPod, routes, ownership, Git, Docker, applications, worktrees, or branches. Act only through the exact `workspace gc` or `workspace down` command a row suggests; never script raw `devpod` or `git worktree remove` calls from its output.
+4. Add `--check-merged` only when you want the read-only origin and GitHub/GitLab checks. Without it the report stays local, and integration state is reported as `not-verified` rather than guessed.
+5. Add `--measure-size` only when you need sizes. It walks each worktree and asks Docker to size the attributed container, so leave it off for routine evidence checks. Reclaimable figures are `worktree` plus `containerWritable`; `imageShared` covers layers shared with other containers, overlaps across workspaces, and must never be summed or presented as reclaimable.
+6. Treat every `unknown` figure as unknown rather than zero. A workspace with no attributed container reports a measured `0`, which is a different and trustworthy answer.
+7. Run `devrouter repo agents --repo <checkout>` to refresh generated guidance.
+
+No manual migration is required. Existing owner records, routes, and devcontainer wiring are read as-is, and a repository with no managed linked workspaces reports an empty list rather than an error.
+
+Verification:
+
+- Run `devrouter -V --repo <checkout>` and confirm both the installed CLI and the local repository report `0.0.36`.
+- Run `devrouter workspace cleanup --repo <repo> --json` and confirm `schemaVersion` is `2` and no `consumption` key is present.
+- Run the same command with `--measure-size` and confirm each workspace carries `consumption`, and that `reclaimable` equals `worktree` plus `containerWritable` wherever both are measured.
+- Run it once with Docker unavailable and confirm the container figures are `unknown` with a reason, worktree bytes stay measured, and the report is still complete.
+- Run `devrouter workspace ls --repo <repo> --json` before and after the report and confirm the output is identical; the report changes no state.
+
+Report template:
+
+- CLI/config version: `0.0.36`
+- Cleanup `--json` consumers updated for `schemaVersion` 2: `<yes or not applicable>`
+- Report-only run: `<workspace count and evidence states>`
+- Suggestions acted on, if any: `<exact command and result, or none>`
+- Sized run: `<reclaimable totals and any unknown figures with reasons>`
+- Docker-absent run: `<container fields unknown, worktree measured>`
+- Remaining blockers: `<none or details>`

package/upgrade-prompts/0.0.37.md

@@ -0,0 +1,30 @@
+# Upgrade to devrouter 0.0.37
+
+Devrouter HTTPS readiness probes now pin curl to the exact certificate served
+by the local Traefik router. This avoids a macOS SecureTransport failure while
+retaining hostname verification, SNI, and the existing route status contract.
+
+1. Install `@devrouter/cli@0.0.37` on the host and bump `.devrouter.yml` to
+   `devrouter.version: 0.0.37`.
+2. No schema or data migration is required.
+3. Re-run `devrouter doctor --repo <checkout> --json` and then use
+   `devrouter ensure <checkout> --json` for managed startup. The readiness
+   probe still requires the existing mkcert setup and does not use an
+   insecure certificate bypass.
+
+Verification:
+
+- Run `devrouter -V --repo <checkout>` and confirm both the installed CLI and
+  local repository report `0.0.37`.
+- Run `devrouter repo devcontainer verify --repo <checkout> --json` and confirm
+  the static checks pass.
+- Run `devrouter ensure <checkout> --json` and confirm the HTTPS route reaches
+  the existing status contract (`100..499` accepted, `5xx` rejected).
+
+Report template:
+
+- CLI/config version: `0.0.37`
+- mkcert setup and certificate readiness: `<passed or details>`
+- Static verification: `<passed or details>`
+- Managed HTTPS readiness: `<passed or details>`
+- Remaining blockers: `<none or details>`