@devrouter/cli 0.0.78 → 0.0.79
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 +978 -169
- package/dist/devrouter.js +3280 -998
- package/package.json +1 -1
- package/upgrade-prompts/0.0.79.md +46 -0
package/package.json
CHANGED
|
@@ -0,0 +1,46 @@
|
|
|
1
|
+
# Upgrade to devrouter 0.0.79
|
|
2
|
+
|
|
3
|
+
This release hardens the managed lifecycle. An environment whose containers were
|
|
4
|
+
removed outside Devrouter can now settle its stop, corrective actions are bounded
|
|
5
|
+
by the declared policy, and a host Devsy CLI newer than the verified pin no longer
|
|
6
|
+
blocks a managed start. `devrouter status` explains the durable intent of a
|
|
7
|
+
managed checkout, and `ensure`/`stop` report bounded stage progress on stderr.
|
|
8
|
+
Defaults stay protected: capacity admission, parking consent and automatic
|
|
9
|
+
recovery remain inert unless an operator enables them.
|
|
10
|
+
|
|
11
|
+
## Task
|
|
12
|
+
|
|
13
|
+
Use the published 0.0.79 CLI. Update the repository `devrouter.version` metadata
|
|
14
|
+
only when consumer source changes are authorized, and refresh generated agent
|
|
15
|
+
guidance only with its owner's authority. No schema, command, flag, environment
|
|
16
|
+
or journal migration is needed, and the upgrade rewrites no runtime state.
|
|
17
|
+
|
|
18
|
+
Two operating changes matter for scripts and agents:
|
|
19
|
+
|
|
20
|
+
- `ensure` and `stop` now write bounded progress lines to stderr. Parse JSON from
|
|
21
|
+
stdout only; do not merge the streams before parsing.
|
|
22
|
+
- A controller that has written a version-2 consumer snapshot or a human
|
|
23
|
+
protection pin refuses older CLIs. Keep 0.0.79 or newer for that journal; do
|
|
24
|
+
not delete snapshots or pins to downgrade.
|
|
25
|
+
|
|
26
|
+
When the host Devsy CLI is newer than the verified pin, Devrouter injects no
|
|
27
|
+
agent and the host CLI governs its own. An older or unparseable CLI stays
|
|
28
|
+
unsupported, and an explicit `DEVSY_AGENT_BINARY` keeps its exact validation.
|
|
29
|
+
|
|
30
|
+
## Validation
|
|
31
|
+
|
|
32
|
+
Verify the resolved executable and installed version. Run `devrouter doctor` and
|
|
33
|
+
confirm `global.devsy-agent` reports `ready` (a non-blocking drift warning is
|
|
34
|
+
expected when the host CLI is newer) and that `repo.cli-outdated` shows the
|
|
35
|
+
installed version and repository pin separately. Run `devrouter status` for an
|
|
36
|
+
authorized managed checkout and confirm the reported intent, phase and attention
|
|
37
|
+
reason agree with the runtime you observe. Require each lifecycle operation's own
|
|
38
|
+
terminal evidence; a status block or progress line is not stop or ensure success.
|
|
39
|
+
|
|
40
|
+
## Report
|
|
41
|
+
|
|
42
|
+
Report release revision, executable, installed version, the Devsy agent and
|
|
43
|
+
CLI/repo version diagnostics, the status block for any affected checkout, and the
|
|
44
|
+
terminal result of any authorized lifecycle operation. Keep source and package
|
|
45
|
+
validation separate from consumer readiness or recovery, and record unknown
|
|
46
|
+
ownership or surviving resources as unresolved rather than as recovered.
|