@devrouter/cli 0.0.37 → 0.0.39

package/package.json

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

package/upgrade-prompts/0.0.38.md

@@ -0,0 +1,45 @@
+# Upgrade to devrouter 0.0.38
+
+Devrouter now supports profile-scoped environments: a `profiles` map in
+`.devrouter.yml` plus `devrouter ensure --profile <name>` starts, routes, and
+readiness-probes only the apps a task needs. Comma-separated selections
+(`--profile manage,pwa`) merge profiles with deduplication, and managed
+adapters receive `DEVROUTER_PROFILE` so they can scope their dev process tree
+to the same selection.
+
+1. Install `@devrouter/cli@0.0.38` on the host and bump `.devrouter.yml` to
+   `devrouter.version: 0.0.38`.
+2. No schema or data migration is required. Repositories without a `profiles`
+   key keep the implicit full behavior; adding `profiles` is optional.
+   Validation is strict: unknown keys, references to apps that are not routed
+   (`kind=app`), references to apps that are not `kind=dependency` in
+   `dependencies`, `readiness` entries outside the profile's apps, and more
+   than one `default: true` are rejected at config-load time.
+3. Optional: declare profiles and select one per task, e.g.
+   `devrouter ensure <checkout> --profile <name>` or
+   `devrouter ensure <checkout> --profile <name-a>,<name-b>`. The merged name
+   is canonicalized (sorted unique), so order does not affect identity.
+   Repository post-start adapters can read `DEVROUTER_PROFILE` and must treat
+   an empty/unset value as the default profile.
+4. Consumers that parse `ensure --json` output must accept the new `profile`
+   field in the result object.
+
+Verification:
+
+- Run `devrouter -V --repo <checkout>` and confirm both the installed CLI and
+  the local repository report `0.0.38`.
+- Run `devrouter doctor --repo <checkout> --json` and confirm the config still
+  validates.
+- With profiles declared, run `devrouter ensure <checkout> --profile <name>
+  --json` and confirm the result reports `"profile": "<name>"` and that only
+  the profile's routes are published (`devrouter ls`).
+- Re-run `devrouter ensure <checkout> --json` without `--profile` and confirm
+  the default/full route set is restored.
+
+Report template:
+
+- CLI/config version: `0.0.38`
+- Config validation: `<passed or details>`
+- Profile-scoped ensure: `<passed or details>`
+- Default (full) ensure after profile use: `<passed or details>`
+- Remaining blockers: `<none or details>`

package/upgrade-prompts/0.0.39.md

@@ -0,0 +1,48 @@
+# Upgrade to devrouter 0.0.39
+
+Devrouter now lets managed devcontainers select independent runtime dimensions.
+The optional `managedRuntime` registry names base Compose services, optional
+Compose capabilities, and repository-owned process markers. Profiles may select
+routed apps, optional services, and processes independently, including
+route-free capability profiles such as an AI gateway or MCP server.
+
+1. Install `@devrouter/cli@0.0.39` on the host and bump `.devrouter.yml` to
+   `devrouter.version: 0.0.39`.
+2. Repositories without `managedRuntime` keep their existing app-only profile
+   behavior. No database or data migration is required.
+3. For a managed devcontainer, register every base service, optional Compose
+   service, and managed process marker. Keep the source `devcontainer.json`
+   as the full native configuration; `devrouter ensure` owns its ignored
+   generated sibling for selective startup.
+4. Add profiles for the real dependency graph. For example, an `ai` profile
+   can select the application, `litellm`, and its process, while an `mcp`
+   profile can select only the MCP service and process. Omitted optional
+   dimensions stay stopped; use `*` or a `full` profile for the complete set.
+5. Refresh generated discoverability artifacts with `devrouter repo agents`.
+   Do not commit `.devcontainer/devcontainer.devrouter.json` or place secrets
+   in the registry or managed runtime state.
+
+Verification:
+
+- Run `devrouter -V --repo <checkout>` and confirm both the installed CLI and
+  local repository report `0.0.39`.
+- Run `devrouter doctor --repo <checkout> --json` and confirm the configuration
+  and managed registry validate.
+- Run a managed app profile and a capability-only profile with
+  `devrouter ensure <checkout> --profile <name> --json`; confirm desired and
+  active services/processes match and that a capability-only profile has no
+  application routes.
+- Switch profiles in the same workspace and confirm the DevPod and volumes are
+  retained, post-create does not rerun, and dropped resources stop only after
+  exact ownership proof.
+- Run `devrouter status --repo <checkout> --json` and inspect any reported drift
+  before continuing development.
+
+Report template:
+
+- CLI/config version: `0.0.39`
+- Registry and profile validation: `<passed or details>`
+- Managed app profile: `<passed or details>`
+- Capability-only profile: `<passed or details>`
+- Warm transition and exact stop: `<passed or details>`
+- Remaining blockers: `<none or details>`