@devrouter/cli 0.0.56 → 0.0.58

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@devrouter/cli",
3
- "version": "0.0.56",
3
+ "version": "0.0.58",
4
4
  "description": "Local dev routing CLI with shared Traefik reverse proxy",
5
5
  "author": "Roland Schlaefli",
6
6
  "homepage": "https://github.com/rschlaefli/devrouter#readme",
@@ -0,0 +1,33 @@
1
+ # Upgrade to devrouter 0.0.57
2
+
3
+ This patch restores managed ensure with comma-separated profiles. Lifecycle events,
4
+ current state and retained request history accept profile selections separately
5
+ from workspace and operation identifiers. Repository resolution still validates
6
+ configured profiles and combines their selected resources.
7
+
8
+ ## Task
9
+
10
+ Install the published 0.0.57 patch and update `.devrouter.yml` devrouter.version to
11
+ 0.0.57 through the consumer repository workflow. No schema or database migration
12
+ is required. Keep the intended profile selection; do not substitute full or delete
13
+ runtime state to avoid the earlier validator failure.
14
+
15
+ ## Validation
16
+
17
+ Use repository profile resolution to check the intended combined selection. Run
18
+ managed ensure only on an authorized exact checkout, retaining its data and
19
+ bindings. Report the resulting application and runtime outcomes separately from
20
+ successful selection validation. Stop only runtimes owned by the validation task,
21
+ then verify their provider status and zero exact routes.
22
+
23
+ ## Limits
24
+
25
+ This patch fixes pre-dispatch profile validation. It does not introduce a host-side
26
+ preparation hook, warm Compose drift reconciliation, capacity admission, a
27
+ controller, autonomous agent recovery or complete OOM protection.
28
+
29
+ ## Report
30
+
31
+ Report installed/configured versions, exact profile selection, validation result
32
+ and any separately authorized runtime evidence. Identify retained runtime leases
33
+ without ending another task's runtime.
@@ -0,0 +1,41 @@
1
+ # Upgrade to devrouter 0.0.58
2
+
3
+ This patch permits recovery directly into a different requested profile after
4
+ retained ownership proof. Failed processes excluded by that profile no longer
5
+ have to start first. Failed transitions preserve degraded evidence and data.
6
+
7
+ ## Task
8
+
9
+ Install the published patch and update `.devrouter.yml` devrouter.version to
10
+ 0.0.58 through the consumer repository workflow. No database migration is needed.
11
+ Refresh generated agent guidance when the repository distributes it.
12
+
13
+ Repositories that generate Compose inputs before inspection may configure
14
+ `managedRuntime.devcontainer.prepareCommand` as a literal argv array. The command
15
+ runs on the host in the checkout root, once per ensure, with a sixty-second bound.
16
+ Keep it in the foreground, preserve `.devrouter.yml`, and leave diagnostics
17
+ read-only. Output is suppressed; report failures through the command exit status.
18
+
19
+ ## Validation
20
+
21
+ Resolve the intended profile and ensure only an authorized exact checkout. For
22
+ degraded recovery, verify the requested resources start without replaying excluded
23
+ processes. Verify host preparation before Compose inspection using a repository
24
+ generator whose output can be checked without exposing values. Separate successful
25
+ generation from applying changed mounts to an existing container.
26
+
27
+ Check application readiness and tooling separately. Retain data and stop only
28
+ task-owned runtimes, then verify stopped provider status and zero exact routes.
29
+
30
+ ## Limits
31
+
32
+ This release does not implement warm mount reconciliation, capacity admission,
33
+ controller observation, autonomous agent recovery or complete OOM protection.
34
+ Ownership conflicts remain actionable errors; they never authorize destructive
35
+ repair or changing another task's runtime.
36
+
37
+ ## Report
38
+
39
+ Report installed/configured versions, exact checkout and profile, preparation
40
+ result, requested-profile recovery evidence, application/tooling outcomes and
41
+ final runtime status. Identify any remaining unverified consumer behavior.