@devrouter/cli 0.0.22 → 0.0.23

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@devrouter/cli",
-  "version": "0.0.22",
+  "version": "0.0.23",
   "description": "Local dev routing CLI with shared Traefik on macOS",
   "license": "MIT",
   "repository": {
@@ -41,7 +41,8 @@
     "test": "vitest run",
     "check:docs-policy": "./scripts/check-docs-policy.sh",
     "test:watch": "vitest",
-    "demo:smoke": "./scripts/smoke-demo.sh",
+    "routing:smoke": "./scripts/smoke-routing.sh",
+    "devcontainer:smoke": "./scripts/smoke-devcontainer.sh",
     "bench:startup": "zsh -lc 'set -euo pipefail; echo \"=== dev --help (x5) ===\"; for i in {1..5}; do /usr/bin/time -p node dist/dev.js --help >/dev/null; done; echo \"=== dev app add --help (x5) ===\"; for i in {1..5}; do /usr/bin/time -p node dist/dev.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/dev.js status --json >/dev/null || true; done'",
     "typecheck": "tsc --noEmit",
     "bootstrap": "pnpm install && pnpm install:local",

package/upgrade-prompts/0.0.23.md

@@ -0,0 +1,44 @@
+You are upgrading a repository that uses devrouter to version 0.0.23.
+
+Changes in this release:
+- `dev setup --yes --json` is the first-run machine setup command for agents. It prepares devrouter-owned state such as router files, the shared `devnet` network, Traefik, and TLS certificates when mkcert is available. Without `--yes`, it reports the plan and diagnostics without mutating state.
+- `dev doctor` remains the diagnostic command. It now reports stale host routes and orphaned workspace proxy routes without changing route files, and exits non-zero when any diagnostic is an error.
+- `dev repo inspect --json` gathers repository facts for onboarding: package manager, scripts, likely ports, compose services, env variable names with values redacted, devcontainer presence, devrouter config, and agent guidance files.
+- `dev repo devcontainer write --dry-run --json` and `dev repo devcontainer write --yes` provide a conservative Node/pnpm/Postgres devcontainer scaffold. The writer only handles the supported shape and refuses custom-file conflicts instead of overwriting them.
+- `dev repo devcontainer verify --json` emits static onboarding evidence for PRs. `dev repo devcontainer verify --live --yes --json` registers proxy routes and probes HTTP routes after the devcontainer is running.
+- The runnable examples now live under `examples/`: `examples/routing/` for no-devcontainer routing with `pnpm routing:smoke`, and `examples/devcontainer/` for a live DevPod/devcontainer app plus Postgres showcase with `pnpm devcontainer:smoke`.
+- `dev doctor` includes more machine and devcontainer diagnostics for Docker Compose v2, mkcert, DevPod, Node/pnpm, devnet aliases, published devcontainer ports, and proxy upstream alias matches.
+
+Task:
+1) Bump `.devrouter.yml` `devrouter.version` to `0.0.23`.
+2) Refresh discoverability artifacts with `dev repo agents --repo <repo>` if the repo commits devrouter-managed AGENTS.md sections or bundled skills.
+3) For agent-native onboarding of a Node/pnpm/Postgres repo, start with:
+   ```sh
+   dev setup --repo <repo> --yes --json
+   dev doctor --repo <repo> --json
+   dev repo inspect --repo <repo> --json
+   dev repo devcontainer write --repo <repo> --dry-run --json
+   dev repo devcontainer write --repo <repo> --yes
+   dev repo devcontainer verify --repo <repo> --json
+   ```
+4) After the devcontainer is running, register and probe routes with:
+   ```sh
+   dev repo devcontainer verify --repo <repo> --live --yes --json
+   ```
+5) If the repo previously referenced the root `demo/` fixture in local docs, scripts, or checks, update those references to `examples/routing/` and use `pnpm routing:smoke`.
+
+Validation:
+- `dev -V --repo <repo>` shows `0.0.23` as the local repo version.
+- `dev setup --repo <repo> --yes --json` completes or reports actionable diagnostics.
+- `dev doctor --repo <repo> --json` reports no errors after required prerequisites are installed.
+- `dev repo inspect --repo <repo> --json` reports the expected package manager, likely app scripts, compose services, devcontainer state, and devrouter config.
+- If using the managed devcontainer scaffold, `dev repo devcontainer verify --repo <repo> --json` reports the expected static evidence.
+- After the devcontainer starts, `dev repo devcontainer verify --repo <repo> --live --yes --json` registers routes and probes HTTP routes successfully.
+- For devrouter itself, run `pnpm check:docs-policy`, `pnpm test`, `pnpm typecheck`, `pnpm build`, `dev setup --repo ./examples/routing --yes --json`, `dev doctor --repo ./examples/routing`, `dev repo inspect --repo ./examples/routing --json`, `pnpm routing:smoke`, and `pnpm devcontainer:smoke`.
+
+Report:
+- `.devrouter.yml` `devrouter.version` before and after
+- setup, doctor, inspect, and devcontainer verification results
+- whether the managed scaffold was written or a custom setup was left untouched
+- route URLs and TCP connection hints checked
+- unresolved risks or manual follow-ups