@devrouter/cli 0.0.30 → 0.0.32

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@devrouter/cli",
-  "version": "0.0.30",
+  "version": "0.0.32",
   "description": "Local dev routing CLI with shared Traefik reverse proxy",
   "author": "Roland Schlaefli",
   "homepage": "https://github.com/rschlaefli/devrouter#readme",
@@ -55,6 +55,7 @@
     "test:watch": "vitest",
     "routing:smoke": "./scripts/smoke-routing.sh",
     "devcontainer:smoke": "./scripts/smoke-devcontainer.sh",
+    "workspace:lifecycle-smoke": "./scripts/smoke-workspace-lifecycle.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.31.md

@@ -0,0 +1,23 @@
+# Upgrade to devrouter 0.0.31
+
+## What changed
+
+Devrouter now persists managed-workspace ownership in the consumer repository's Git common directory. `workspace ls` classifies owners as `present`, `missing`, `locked`, or `conflict`; `workspace stop` pauses exact runtime/routes without removing the checkout; full `workspace down` fails before side effects for dirty or locked worktrees; and `workspace gc` reports cleanup candidates without mutation unless `--yes` is supplied.
+
+The ambiguous `workspace down --keep-devpod` flag was removed. Normal config, app, status, and doctor commands still work outside Git, but the `workspace` command group now requires a Git repository.
+
+## Steps
+
+1. Install `@devrouter/cli@0.0.31` on the host and bump `.devrouter.yml` to `devrouter.version: 0.0.31`.
+2. Run `devrouter repo agents --repo <repo>` to refresh the generated `AGENTS.md` section and bundled devrouter skill.
+3. In every existing managed linked worktree, run `devrouter workspace ensure .` once. This validates the exact DevPod/path and adopts it into the durable owner ledger.
+4. Replace `workspace down --keep-devpod` automation. Use `workspace stop <workspace>` to pause runtime/routes while retaining checkout and data, or `workspace down <workspace> --keep-worktree` to delete runtime/routes while retaining the checkout and owner record. There is no supported mode that removes a worktree while leaving its DevPod running.
+5. If the repository uses the managed devcontainer scaffold, run `devrouter repo devcontainer write --dry-run --json`, review the plan, then apply it with `--yes`. Custom linked-worktree overlays must pass `WORKSPACE` and `DEVROUTER_WORKSPACE` into the app and mount `DEVROUTER_GIT_COMMON_DIR` at the same absolute path.
+6. Run `devrouter workspace gc --repo <repo> --json` and review every eligible candidate in the dry-run report. Add `--yes` only when every eligible candidate is approved, because apply cleans all eligible candidates in the repository scope; legacy, locked, present, and conflicting evidence is never mutated.
+
+## Verify
+
+- `devrouter workspace ls --repo <repo> --json` shows expected owner, DevPod, route, path, and branch evidence.
+- A dirty linked worktree rejects full `workspace down` without stopping its DevPod or removing routes.
+- `devrouter doctor --repo <repo> --json` reports one `workspace.ownership-cleanup` check and an exact GC command when review is needed.
+- A non-Git folder with `.devrouter.yml` still supports `devrouter app ls`, `devrouter repo inspect`, and `devrouter doctor`; workspace commands return the clear Git-required error.

package/upgrade-prompts/0.0.32.md

@@ -0,0 +1,26 @@
+# Upgrade to devrouter 0.0.32
+
+Devrouter now owns the complete local devcontainer reconciliation path for both primary and linked checkouts. Normal startup is `devrouter ensure <checkout>`; do not branch on checkout kind or script separate router, DevPod, TLS, and live-verify steps.
+
+1. Install `@devrouter/cli@0.0.32` on the host and bump `.devrouter.yml` to `devrouter.version: 0.0.32`.
+2. Keep `devrouter setup --repo <checkout> --yes` as a one-time machine bootstrap. Replace recurring setup, `devpod up`, and `repo devcontainer verify --live --yes` wrapper steps with `devrouter ensure <checkout>`.
+3. Use `devrouter stop <checkout>` for a non-destructive pause. It stops only the exact DevPod and removes that checkout's routes.
+4. Replace manual `devpod ssh ... --command` seed, migration, and fixture invocations with `devrouter exec <checkout> -- <command...>`.
+5. Keep `workspace up <branch>` for creating linked worktrees. Existing `workspace ensure` remains compatible but should no longer be selected conditionally.
+6. Run `devrouter repo agents --repo <checkout>` to refresh generated guidance.
+
+Verification:
+
+- Run `devrouter ensure <checkout> --json` twice and confirm the same exact DevPod is reused and trusted HTTPS routes succeed.
+- Run `devrouter exec <checkout> -- node -e 'console.log(process.cwd())'` and confirm it prints the checkout's container mount.
+- Run the old live-verify command once only as a compatibility check; it should warn and succeed without insecure TLS.
+
+Report template:
+
+- CLI/config version: `0.0.32`
+- Wrapper migration: `<files changed or not applicable>`
+- Primary ensure: `<cold/warm DevPod id and trusted routes>`
+- Linked ensure: `<cold/warm workspace id and namespaced routes>`
+- Exec proof: `<command and exit status>`
+- Compatibility live verify: `<passed or skipped with reason>`
+- Remaining blockers: `<none or details>`