@devrouter/cli 0.6.1 → 0.6.3

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@devrouter/cli",
-  "version": "0.6.1",
+  "version": "0.6.3",
   "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.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.

package/upgrade-prompts/0.6.3.md

@@ -0,0 +1,51 @@
+# Upgrade to devrouter 0.6.3
+
+This patch qualifies explicit fresh managed initialization on Devsy 1.24.0 in
+addition to 1.19.0. The operation and its data, context and ownership guarantees
+are unchanged. Early ineligible repair now refuses before repository preparation
+and records a known failure; cancellation and uncertain completion stay distinct.
+Use ordinary ensure for startup and inspect exact-checkout diagnostics when an
+explicit recorded-profile repair is ineligible. Qualify preserving source hooks
+before starting a retained environment. Ordinary startup retains its existing provider support.
+
+## Task
+
+Within an authorized consumer adaptation, install the published CLI, verify its
+executable/version, bump `devrouter.version` in `.devrouter.yml`, and refresh
+existing guidance with `devrouter repo agents`. Explicitly managed controllers
+must use the matching initialization protocol. No configuration migration is
+required for ordinary startup.
+
+Before adopting a changed Devsy release, follow the explicit agent preparation
+in `docs/GETTING_STARTED.md`: `devrouter setup --yes --workspace-runtime devsy`.
+That machine setup needs its own authority. A host-governed readiness result
+without a verified matching agent does not prove replacement can acquire one.
+The 1.24.0 replacement qualification uses the matching verified Linux agent;
+ordinary lifecycle calls never substitute an unverified inherited binary.
+
+For a new disposable checkout, follow the current `docs/DEVCONTAINER.md`
+`freshBootstrap` contract and request `ensure <path> --initialize-new` only
+within existing consumer authority. Qualify the complete selected composition,
+new local data volumes, explicit shared caches and repository-owned database
+identity/emptiness checks. Unqualified provider versions and contexts refuse.
+
+The durable attempt is consumed before provider creation. Failure, cancellation,
+unknown completion, stop, replacement, registration loss and settlement never
+rearm it. Preserve partial data and use supported preserving recovery. Never
+clear the attempt or treat this operation as an existing-environment reset.
+
+## Validation
+
+1. Run the consumer's static configuration and bootstrap checks for actual edits.
+2. With runtime authority, initialize a new disposable fixture on the exact
+   qualified provider version; verify actual work, retained synthetic data
+   through preserving stop/resume, and refusal of a repeated initialization.
+3. Check failure/cancellation retention and replay refusal. End with canonical
+   `devrouter stop <path>` and verify stopped provider state and zero exact routes
+   unless the user explicitly retains the environment.
+
+## Report
+
+Report exact source/package/executable and provider identities, actual checks,
+retained-data evidence, remaining consumer prerequisites and final runtime state.
+A compatible release or installation alone does not prove consumer recovery.