@devrouter/cli 0.6.0 → 0.6.1
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 +310 -75
- package/dist/devrouter.js +1995 -726
- package/package.json +1 -1
- package/upgrade-prompts/0.6.1.md +51 -0
package/package.json
CHANGED
|
@@ -0,0 +1,51 @@
|
|
|
1
|
+
# Upgrade to devrouter 0.6.1
|
|
2
|
+
|
|
3
|
+
This patch repairs managed-state persistence and explicit stop recovery after
|
|
4
|
+
container replacement. It also makes interrupted or stalled ensure operations
|
|
5
|
+
inspectable without waiting for the lifecycle mutation lock. Repository schemas
|
|
6
|
+
and existing routing configuration remain compatible.
|
|
7
|
+
|
|
8
|
+
## Task
|
|
9
|
+
|
|
10
|
+
Install the published 0.6.1 CLI and inspect `devrouter upgrade 0.6.1`. Within an
|
|
11
|
+
authorized consumer adaptation, bump `devrouter.version` in `.devrouter.yml`
|
|
12
|
+
and refresh existing generated agent guidance with `devrouter repo agents`.
|
|
13
|
+
No schema migration, application restart or consumer data reset is required by
|
|
14
|
+
the metadata upgrade itself.
|
|
15
|
+
|
|
16
|
+
Inspect a managed operation with `devrouter status --repo <exact-checkout>
|
|
17
|
+
--json`. For explicit diagnostic output, use `devrouter logs --repo
|
|
18
|
+
<exact-checkout> --tail 100`. The ensure output snapshot is private and bounded
|
|
19
|
+
to 32 KiB, has no follow mode, and is unavailable when its operation evidence
|
|
20
|
+
cannot be validated. Stage and output freshness do not prove liveness. Worker
|
|
21
|
+
handshake and cancellation limits are distinct from execution, which has no
|
|
22
|
+
implicit deadline.
|
|
23
|
+
|
|
24
|
+
Ordinary stop continues to refuse changed immutable ownership. For a separately
|
|
25
|
+
authorized recovery of replaced containers, use `devrouter stop <exact-checkout>
|
|
26
|
+
--repair --json`. This requires complete provider, daemon, source, configuration,
|
|
27
|
+
mount, population and exact-ID proof, preserves volumes and cannot combine with
|
|
28
|
+
`--delete`. A service network namespace is equivalent only when live inspection
|
|
29
|
+
proves the exact owned target; changed or uncertain evidence still refuses.
|
|
30
|
+
`ensure --repair` remains a separate recovery operation. Do not bypass a
|
|
31
|
+
refusal with raw Docker or provider mutations.
|
|
32
|
+
|
|
33
|
+
## Validation
|
|
34
|
+
|
|
35
|
+
1. Confirm the installed CLI and executable with `devrouter -V`, and inspect
|
|
36
|
+
this adaptation prompt. Run existing static consumer checks for actual edits.
|
|
37
|
+
2. When runtime verification is separately authorized, use the exact checkout
|
|
38
|
+
for ordinary ensure, actual application work and supported recovery. Check
|
|
39
|
+
data retention and neighbour isolation rather than treating readiness as
|
|
40
|
+
proof of working application behavior.
|
|
41
|
+
3. After the last runtime check, stop that exact checkout and verify its provider
|
|
42
|
+
is stopped and its owned routes are absent unless explicitly kept running.
|
|
43
|
+
An unknown worker, ownership conflict or surviving resource remains a refusal.
|
|
44
|
+
|
|
45
|
+
## Report
|
|
46
|
+
|
|
47
|
+
Report installed version and executable, consumer metadata changes, checks and
|
|
48
|
+
producing source/package identities, any explicit recovery performed, retained
|
|
49
|
+
data proof, and final provider/route state. Distinguish publication, global
|
|
50
|
+
installation and consumer runtime acceptance. Keep private runtime data out of
|
|
51
|
+
shared source and release artifacts.
|