@devrouter/cli 0.0.61 → 0.0.62
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 +326 -191
- package/dist/devrouter.js +275 -111
- package/package.json +1 -1
- package/upgrade-prompts/0.0.62.md +35 -0
package/package.json
CHANGED
|
@@ -0,0 +1,35 @@
|
|
|
1
|
+
# Upgrade to devrouter 0.0.62
|
|
2
|
+
|
|
3
|
+
This patch restores manual tooling access after interrupted preparation has drained,
|
|
4
|
+
when the exact retained Devsy runtime can be proven. Each subsequent command keeps
|
|
5
|
+
requiring fresh identity proof until a later ensure replaces the interrupted result.
|
|
6
|
+
History rollover preserves the latest preparation result.
|
|
7
|
+
|
|
8
|
+
## Task
|
|
9
|
+
|
|
10
|
+
Install the published patch through the established workflow and update
|
|
11
|
+
`.devrouter.yml` devrouter.version to 0.0.62. No schema migration is required.
|
|
12
|
+
Refresh distributed agent guidance through the existing repository workflow.
|
|
13
|
+
Do not restart or recreate a retained runtime to test tooling access.
|
|
14
|
+
|
|
15
|
+
## Validation
|
|
16
|
+
|
|
17
|
+
Confirm the installed version and exact checkout/provider identity. Run canonical
|
|
18
|
+
`devrouter exec <checkout> -- node --version` once on an already-running runtime.
|
|
19
|
+
Verify a known completion and unchanged configuration, managed state, routes,
|
|
20
|
+
container identity and retained data. Preserve the interrupted ensure result.
|
|
21
|
+
Never replay an uncertain command. Continue only already-authorized validation.
|
|
22
|
+
|
|
23
|
+
## Limits
|
|
24
|
+
|
|
25
|
+
Recovery requires Devsy with the plain local Docker command and exact ownership
|
|
26
|
+
proof. It does not repair missing stop baselines, change provider configuration,
|
|
27
|
+
resolve repository bootstrap errors, provide complete OOM protection, enable
|
|
28
|
+
capacity admission, or establish autonomous agent recovery. Synthetic qualification
|
|
29
|
+
is not live consumer acceptance. Installation alone does not change runtime state.
|
|
30
|
+
|
|
31
|
+
## Report
|
|
32
|
+
|
|
33
|
+
Report installed version, exact checkout/provider, command outcome, preservation
|
|
34
|
+
checks, remaining limitations and final runtime/route state or existing retention
|
|
35
|
+
lease. Distinguish released source from consumer acceptance.
|