@devrouter/cli 0.0.57 → 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/dist/devrouter-lifecycle-worker.js +229 -68
- package/dist/devrouter.js +155 -100
- package/package.json +1 -1
- package/upgrade-prompts/0.0.58.md +41 -0
package/package.json
CHANGED
|
@@ -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.
|