@devrouter/cli 0.6.1 → 0.6.2
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 +797 -221
- package/dist/devrouter.js +926 -762
- package/package.json +1 -1
- package/upgrade-prompts/0.6.2.md +51 -0
package/package.json
CHANGED
|
@@ -0,0 +1,51 @@
|
|
|
1
|
+
# Upgrade to devrouter 0.6.2
|
|
2
|
+
|
|
3
|
+
This patch extends managed startup with explicit initialization for a new
|
|
4
|
+
disposable environment. Existing configurations and ordinary preserving
|
|
5
|
+
startup remain compatible. No reset, data deletion or implicit initialization
|
|
6
|
+
is introduced.
|
|
7
|
+
|
|
8
|
+
## Task
|
|
9
|
+
|
|
10
|
+
Within an authorized consumer adaptation, install the published CLI, confirm
|
|
11
|
+
its executable/version, bump `devrouter.version` in `.devrouter.yml` and refresh
|
|
12
|
+
existing agent guidance with `devrouter repo agents`. Update an explicitly
|
|
13
|
+
managed controller to the matching version before using the new intent there;
|
|
14
|
+
an old controller refuses the new protocol field.
|
|
15
|
+
|
|
16
|
+
A repository that needs first initialization may declare
|
|
17
|
+
`managedRuntime.devcontainer.freshBootstrap` with literal `command` argv,
|
|
18
|
+
nonempty `dataVolumes` keys and optional distinct `sharedCaches` keys. For a new
|
|
19
|
+
disposable checkout only, request `devrouter ensure <path> --profile <name>
|
|
20
|
+
--initialize-new --json`. The repository owns database identity, emptiness,
|
|
21
|
+
schema and seed validation. Qualify its original hooks as preserving.
|
|
22
|
+
|
|
23
|
+
Read `docs/DEVCONTAINER.md` for the supported context and mount requirements.
|
|
24
|
+
The initial qualified provider is Devsy 1.19.0 with the default environment
|
|
25
|
+
probe. Non-cache volumes must use new local storage; declared shared caches
|
|
26
|
+
must be external. Unsupported contexts and unknown ownership refuse.
|
|
27
|
+
|
|
28
|
+
An initialization request durably consumes one attempt before provider
|
|
29
|
+
creation. Failure, cancellation and unknown completion retain partial data and
|
|
30
|
+
the attempt. Stop, replacement, registration loss and journal settlement never
|
|
31
|
+
rearm it. Use supported preserving recovery, or a new disposable checkout for
|
|
32
|
+
a new attempt. Never hand-edit its journal, infer reset authority or bypass
|
|
33
|
+
worker, ownership, endpoint or population refusals.
|
|
34
|
+
|
|
35
|
+
## Validation
|
|
36
|
+
|
|
37
|
+
1. Run the consumer's static configuration and bootstrap checks for actual edits.
|
|
38
|
+
2. When runtime verification is authorized, initialize a new disposable fixture
|
|
39
|
+
with the explicit flag, verify actual application work and exact synthetic
|
|
40
|
+
data through stop/resume and the intended replacement path, and confirm a
|
|
41
|
+
second initialization request refuses.
|
|
42
|
+
3. Verify failure/unknown completion preserves data and prevents replay. Finish
|
|
43
|
+
with canonical `devrouter stop <path>` and prove stopped provider state and
|
|
44
|
+
zero exact routes unless the user explicitly keeps it running.
|
|
45
|
+
|
|
46
|
+
## Report
|
|
47
|
+
|
|
48
|
+
Report exact source/package/executable identities, changed configuration,
|
|
49
|
+
qualified provider/context and tests, initialization/preserving behavior,
|
|
50
|
+
actual retained-data evidence, remaining consumer prerequisites and final
|
|
51
|
+
provider/route state. A release or installation alone is not consumer recovery.
|