@devrouter/cli 0.0.62 → 0.0.63
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 +1391 -1268
- package/dist/devrouter.js +355 -96
- package/package.json +1 -1
- package/upgrade-prompts/0.0.63.md +36 -0
package/package.json
CHANGED
|
@@ -0,0 +1,36 @@
|
|
|
1
|
+
# Upgrade to devrouter 0.0.63
|
|
2
|
+
|
|
3
|
+
This patch waits for healthy lifecycle workers before tooling execution and
|
|
4
|
+
recovers stop when a saved baseline proves a linked Devsy runtime absent.
|
|
5
|
+
|
|
6
|
+
## Task
|
|
7
|
+
|
|
8
|
+
Install the published patch through the established workflow and update
|
|
9
|
+
`.devrouter.yml` devrouter.version to 0.0.63. No schema migration is required.
|
|
10
|
+
Refresh distributed agent guidance through the existing repository workflow.
|
|
11
|
+
Installation does not require a runtime restart.
|
|
12
|
+
|
|
13
|
+
## Validation
|
|
14
|
+
|
|
15
|
+
Confirm the installed version and exact checkout/provider identity. On an
|
|
16
|
+
already-running authorized runtime, run canonical `devrouter exec <checkout> --
|
|
17
|
+
node --version` and verify completion without restarting services. Never replay
|
|
18
|
+
an uncertain command. For an already-authorized absent-runtime recovery, use
|
|
19
|
+
canonical `devrouter stop <checkout> --json`; verify stopped state, zero scoped
|
|
20
|
+
routes and retained history. Run ensure only within the consumer owner's scope.
|
|
21
|
+
A successful stop does not prove that subsequent startup succeeds.
|
|
22
|
+
|
|
23
|
+
## Limits
|
|
24
|
+
|
|
25
|
+
Absent-runtime recovery requires a valid saved baseline, exact linked-workspace
|
|
26
|
+
ownership and Devsy selection. It does not override mixed-provider selection,
|
|
27
|
+
repair legacy records without baselines, solve exhausted Docker network pools,
|
|
28
|
+
enable capacity admission or provide complete OOM protection or autonomous agent
|
|
29
|
+
recovery. Host process-inspection restrictions still require permitted host
|
|
30
|
+
execution; never remove locks or weaken ownership checks to work around them.
|
|
31
|
+
|
|
32
|
+
## Report
|
|
33
|
+
|
|
34
|
+
Report installed version, exact checkout/provider, command outcome, preservation
|
|
35
|
+
checks and final runtime/route state or explicit retention requirement. Separate
|
|
36
|
+
released source, synthetic checks and live consumer acceptance.
|