@devrouter/cli 0.6.0 → 0.6.2

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@devrouter/cli",
-  "version": "0.6.0",
+  "version": "0.6.2",
   "description": "Local dev routing CLI with shared Traefik reverse proxy",
   "author": "Roland Schlaefli",
   "homepage": "https://github.com/rschlaefli/devrouter#readme",

package/upgrade-prompts/0.6.1.md

@@ -0,0 +1,51 @@
+# Upgrade to devrouter 0.6.1
+
+This patch repairs managed-state persistence and explicit stop recovery after
+container replacement. It also makes interrupted or stalled ensure operations
+inspectable without waiting for the lifecycle mutation lock. Repository schemas
+and existing routing configuration remain compatible.
+
+## Task
+
+Install the published 0.6.1 CLI and inspect `devrouter upgrade 0.6.1`. Within an
+authorized consumer adaptation, bump `devrouter.version` in `.devrouter.yml`
+and refresh existing generated agent guidance with `devrouter repo agents`.
+No schema migration, application restart or consumer data reset is required by
+the metadata upgrade itself.
+
+Inspect a managed operation with `devrouter status --repo <exact-checkout>
+--json`. For explicit diagnostic output, use `devrouter logs --repo
+<exact-checkout> --tail 100`. The ensure output snapshot is private and bounded
+to 32 KiB, has no follow mode, and is unavailable when its operation evidence
+cannot be validated. Stage and output freshness do not prove liveness. Worker
+handshake and cancellation limits are distinct from execution, which has no
+implicit deadline.
+
+Ordinary stop continues to refuse changed immutable ownership. For a separately
+authorized recovery of replaced containers, use `devrouter stop <exact-checkout>
+--repair --json`. This requires complete provider, daemon, source, configuration,
+mount, population and exact-ID proof, preserves volumes and cannot combine with
+`--delete`. A service network namespace is equivalent only when live inspection
+proves the exact owned target; changed or uncertain evidence still refuses.
+`ensure --repair` remains a separate recovery operation. Do not bypass a
+refusal with raw Docker or provider mutations.
+
+## Validation
+
+1. Confirm the installed CLI and executable with `devrouter -V`, and inspect
+   this adaptation prompt. Run existing static consumer checks for actual edits.
+2. When runtime verification is separately authorized, use the exact checkout
+   for ordinary ensure, actual application work and supported recovery. Check
+   data retention and neighbour isolation rather than treating readiness as
+   proof of working application behavior.
+3. After the last runtime check, stop that exact checkout and verify its provider
+   is stopped and its owned routes are absent unless explicitly kept running.
+   An unknown worker, ownership conflict or surviving resource remains a refusal.
+
+## Report
+
+Report installed version and executable, consumer metadata changes, checks and
+producing source/package identities, any explicit recovery performed, retained
+data proof, and final provider/route state. Distinguish publication, global
+installation and consumer runtime acceptance. Keep private runtime data out of
+shared source and release artifacts.

package/upgrade-prompts/0.6.2.md

@@ -0,0 +1,51 @@
+# Upgrade to devrouter 0.6.2
+
+This patch extends managed startup with explicit initialization for a new
+disposable environment. Existing configurations and ordinary preserving
+startup remain compatible. No reset, data deletion or implicit initialization
+is introduced.
+
+## Task
+
+Within an authorized consumer adaptation, install the published CLI, confirm
+its executable/version, bump `devrouter.version` in `.devrouter.yml` and refresh
+existing agent guidance with `devrouter repo agents`. Update an explicitly
+managed controller to the matching version before using the new intent there;
+an old controller refuses the new protocol field.
+
+A repository that needs first initialization may declare
+`managedRuntime.devcontainer.freshBootstrap` with literal `command` argv,
+nonempty `dataVolumes` keys and optional distinct `sharedCaches` keys. For a new
+disposable checkout only, request `devrouter ensure <path> --profile <name>
+--initialize-new --json`. The repository owns database identity, emptiness,
+schema and seed validation. Qualify its original hooks as preserving.
+
+Read `docs/DEVCONTAINER.md` for the supported context and mount requirements.
+The initial qualified provider is Devsy 1.19.0 with the default environment
+probe. Non-cache volumes must use new local storage; declared shared caches
+must be external. Unsupported contexts and unknown ownership refuse.
+
+An initialization request durably consumes one attempt before provider
+creation. Failure, cancellation and unknown completion retain partial data and
+the attempt. Stop, replacement, registration loss and journal settlement never
+rearm it. Use supported preserving recovery, or a new disposable checkout for
+a new attempt. Never hand-edit its journal, infer reset authority or bypass
+worker, ownership, endpoint or population refusals.
+
+## Validation
+
+1. Run the consumer's static configuration and bootstrap checks for actual edits.
+2. When runtime verification is authorized, initialize a new disposable fixture
+   with the explicit flag, verify actual application work and exact synthetic
+   data through stop/resume and the intended replacement path, and confirm a
+   second initialization request refuses.
+3. Verify failure/unknown completion preserves data and prevents replay. Finish
+   with canonical `devrouter stop <path>` and prove stopped provider state and
+   zero exact routes unless the user explicitly keeps it running.
+
+## Report
+
+Report exact source/package/executable identities, changed configuration,
+qualified provider/context and tests, initialization/preserving behavior,
+actual retained-data evidence, remaining consumer prerequisites and final
+provider/route state. A release or installation alone is not consumer recovery.