@volter/world 3.0.144 → 3.0.145

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.
Files changed (15) hide show
  1. package/dist/examples/customer-onboarding/README.md +1 -1
  2. package/dist/examples/customer-onboarding/package.json +4 -4
  3. package/dist/examples/integration-branches/README.md +4 -4
  4. package/dist/examples/integration-branches/package.json +4 -4
  5. package/dist/examples/workplace-agent/README.md +1 -1
  6. package/dist/examples/workplace-agent/package.json +4 -4
  7. package/dist/skills/volter-world/AGENTS.md +4 -0
  8. package/examples/customer-onboarding/README.md +1 -1
  9. package/examples/customer-onboarding/package.json +4 -4
  10. package/examples/integration-branches/README.md +4 -4
  11. package/examples/integration-branches/package.json +4 -4
  12. package/examples/workplace-agent/README.md +1 -1
  13. package/examples/workplace-agent/package.json +4 -4
  14. package/package.json +5 -5
  15. package/skills/volter-world/AGENTS.md +4 -0
package/dist/examples/customer-onboarding/README.md CHANGED
@@ -13,7 +13,7 @@ You need Node 22.6+, npm and registry access during installation. The browser pa
13
13
  Copy this starter into a new folder:
14
14
 
15
15
  ```console
16
- $ npx @volter/world@3.0.144 example customer-onboarding --dir onboarding
16
+ $ npx @volter/world@3.0.145 example customer-onboarding --dir onboarding
17
17
  $ cd onboarding
18
18
  $ npm install
19
19
  ```
package/dist/examples/customer-onboarding/package.json CHANGED
@@ -11,10 +11,10 @@
11
11
  "pg": "8.16.3"
12
12
  },
13
13
  "devDependencies": {
14
- "@volter/world": "3.0.144",
15
- "@volter/world-core": "3.0.144",
16
- "@volter/world-runtime": "3.0.144",
17
- "@volter/world-console": "3.0.139",
14
+ "@volter/world": "3.0.145",
15
+ "@volter/world-core": "3.0.145",
16
+ "@volter/world-runtime": "3.0.145",
17
+ "@volter/world-console": "3.0.140",
18
18
  "@volter/twin-stripe": "3.0.2",
19
19
  "@volter/twin-resend": "1.0.1"
20
20
  }
package/dist/examples/integration-branches/README.md CHANGED
@@ -13,7 +13,7 @@ Give two workers the same Stripe baseline, let them change different existing cu
13
13
  Use an empty parent folder. Create the baseline starter there:
14
14
 
15
15
  ```console
16
- $ npx @volter/world@3.0.144 example integration-branches --dir baseline
16
+ $ npx @volter/world@3.0.145 example integration-branches --dir baseline
17
17
  $ cd baseline
18
18
  $ npm install
19
19
  $ npx volter world init --name baseline --twins stripe
@@ -38,9 +38,9 @@ The stopped baseline retains its history and can supply local path remotes. Defa
38
38
  Create three more copies in the same parent folder:
39
39
 
40
40
  ```console
41
- $ npx @volter/world@3.0.144 example integration-branches --dir integration
42
- $ npx @volter/world@3.0.144 example integration-branches --dir worker-a
43
- $ npx @volter/world@3.0.144 example integration-branches --dir worker-b
41
+ $ npx @volter/world@3.0.145 example integration-branches --dir integration
42
+ $ npx @volter/world@3.0.145 example integration-branches --dir worker-a
43
+ $ npx @volter/world@3.0.145 example integration-branches --dir worker-b
44
44
  ```
45
45
 
46
46
  In `integration`, then `worker-a`, then `worker-b`, install dependencies and initialize with the folder's name. Before a first boot or app write, link and pull the baseline:
package/dist/examples/integration-branches/package.json CHANGED
@@ -9,10 +9,10 @@
9
9
  "stripe": "17.7.0"
10
10
  },
11
11
  "devDependencies": {
12
- "@volter/world": "3.0.144",
13
- "@volter/world-core": "3.0.144",
14
- "@volter/world-runtime": "3.0.144",
15
- "@volter/world-console": "3.0.139",
12
+ "@volter/world": "3.0.145",
13
+ "@volter/world-core": "3.0.145",
14
+ "@volter/world-runtime": "3.0.145",
15
+ "@volter/world-console": "3.0.140",
16
16
  "@volter/twin-stripe": "3.0.2"
17
17
  }
18
18
  }
package/dist/examples/workplace-agent/README.md CHANGED
@@ -13,7 +13,7 @@ You need Node 22.6+, npm and registry access during installation. No platform ac
13
13
  ## Prepare an ordinary workplace
14
14
 
15
15
  ```console
16
- $ npx @volter/world@3.0.144 example workplace-agent --dir workplace
16
+ $ npx @volter/world@3.0.145 example workplace-agent --dir workplace
17
17
  $ cd workplace
18
18
  $ npm install
19
19
  $ npx volter world init --name workplace --twins github,linear,slack
package/dist/examples/workplace-agent/package.json CHANGED
@@ -11,10 +11,10 @@
11
11
  "@slack/web-api": "7.19.0"
12
12
  },
13
13
  "devDependencies": {
14
- "@volter/world": "3.0.144",
15
- "@volter/world-core": "3.0.144",
16
- "@volter/world-runtime": "3.0.144",
17
- "@volter/world-console": "3.0.139",
14
+ "@volter/world": "3.0.145",
15
+ "@volter/world-core": "3.0.145",
16
+ "@volter/world-runtime": "3.0.145",
17
+ "@volter/world-console": "3.0.140",
18
18
  "@volter/twin-github": "3.0.6",
19
19
  "@volter/twin-linear": "3.0.4",
20
20
  "@volter/twin-slack": "3.0.5"
package/dist/skills/volter-world/AGENTS.md CHANGED
@@ -146,6 +146,10 @@ An app that answers as its own production hostnames (`app.example.com`) records
146
146
  2. Run `doctor`, then `tail --no-follow`, and inspect the twin's `GET /twin` manifest.
147
147
  3. Run `covers <world> --repo <app>` for missing vendor coverage.
148
148
  4. Determine whether the failure belongs to the app, twin fidelity, scenario, routing or runtime.
149
+ 5. A database preparation that fails at image build is fixed in that preparation (`runtime.database.prepare`
150
+ and what it runs against). `runtime.development.migrateDatabaseAtRuntime` is the app developer's setting for a
151
+ schema they are changing right now; it is never an operator's route past a failed preparation, and a World
152
+ that sets it is a development World whose image is not prepared.
149
153
 
150
154
  Sandbox mode refuses untwinned destinations in cooperating clients, including Node sockets a
151
155
  client opens around the injector. It does not constrain binaries or non-Node processes that
package/examples/customer-onboarding/README.md CHANGED
@@ -13,7 +13,7 @@ You need Node 22.6+, npm and registry access during installation. The browser pa
13
13
  Copy this starter into a new folder:
14
14
 
15
15
  ```console
16
- $ npx @volter/world@3.0.144 example customer-onboarding --dir onboarding
16
+ $ npx @volter/world@3.0.145 example customer-onboarding --dir onboarding
17
17
  $ cd onboarding
18
18
  $ npm install
19
19
  ```
package/examples/customer-onboarding/package.json CHANGED
@@ -11,10 +11,10 @@
11
11
  "pg": "8.16.3"
12
12
  },
13
13
  "devDependencies": {
14
- "@volter/world": "3.0.144",
15
- "@volter/world-core": "3.0.144",
16
- "@volter/world-runtime": "3.0.144",
17
- "@volter/world-console": "3.0.139",
14
+ "@volter/world": "3.0.145",
15
+ "@volter/world-core": "3.0.145",
16
+ "@volter/world-runtime": "3.0.145",
17
+ "@volter/world-console": "3.0.140",
18
18
  "@volter/twin-stripe": "3.0.2",
19
19
  "@volter/twin-resend": "1.0.1"
20
20
  }
package/examples/integration-branches/README.md CHANGED
@@ -13,7 +13,7 @@ Give two workers the same Stripe baseline, let them change different existing cu
13
13
  Use an empty parent folder. Create the baseline starter there:
14
14
 
15
15
  ```console
16
- $ npx @volter/world@3.0.144 example integration-branches --dir baseline
16
+ $ npx @volter/world@3.0.145 example integration-branches --dir baseline
17
17
  $ cd baseline
18
18
  $ npm install
19
19
  $ npx volter world init --name baseline --twins stripe
@@ -38,9 +38,9 @@ The stopped baseline retains its history and can supply local path remotes. Defa
38
38
  Create three more copies in the same parent folder:
39
39
 
40
40
  ```console
41
- $ npx @volter/world@3.0.144 example integration-branches --dir integration
42
- $ npx @volter/world@3.0.144 example integration-branches --dir worker-a
43
- $ npx @volter/world@3.0.144 example integration-branches --dir worker-b
41
+ $ npx @volter/world@3.0.145 example integration-branches --dir integration
42
+ $ npx @volter/world@3.0.145 example integration-branches --dir worker-a
43
+ $ npx @volter/world@3.0.145 example integration-branches --dir worker-b
44
44
  ```
45
45
 
46
46
  In `integration`, then `worker-a`, then `worker-b`, install dependencies and initialize with the folder's name. Before a first boot or app write, link and pull the baseline:
package/examples/integration-branches/package.json CHANGED
@@ -9,10 +9,10 @@
9
9
  "stripe": "17.7.0"
10
10
  },
11
11
  "devDependencies": {
12
- "@volter/world": "3.0.144",
13
- "@volter/world-core": "3.0.144",
14
- "@volter/world-runtime": "3.0.144",
15
- "@volter/world-console": "3.0.139",
12
+ "@volter/world": "3.0.145",
13
+ "@volter/world-core": "3.0.145",
14
+ "@volter/world-runtime": "3.0.145",
15
+ "@volter/world-console": "3.0.140",
16
16
  "@volter/twin-stripe": "3.0.2"
17
17
  }
18
18
  }
package/examples/workplace-agent/README.md CHANGED
@@ -13,7 +13,7 @@ You need Node 22.6+, npm and registry access during installation. No platform ac
13
13
  ## Prepare an ordinary workplace
14
14
 
15
15
  ```console
16
- $ npx @volter/world@3.0.144 example workplace-agent --dir workplace
16
+ $ npx @volter/world@3.0.145 example workplace-agent --dir workplace
17
17
  $ cd workplace
18
18
  $ npm install
19
19
  $ npx volter world init --name workplace --twins github,linear,slack
package/examples/workplace-agent/package.json CHANGED
@@ -11,10 +11,10 @@
11
11
  "@slack/web-api": "7.19.0"
12
12
  },
13
13
  "devDependencies": {
14
- "@volter/world": "3.0.144",
15
- "@volter/world-core": "3.0.144",
16
- "@volter/world-runtime": "3.0.144",
17
- "@volter/world-console": "3.0.139",
14
+ "@volter/world": "3.0.145",
15
+ "@volter/world-core": "3.0.145",
16
+ "@volter/world-runtime": "3.0.145",
17
+ "@volter/world-console": "3.0.140",
18
18
  "@volter/twin-github": "3.0.6",
19
19
  "@volter/twin-linear": "3.0.4",
20
20
  "@volter/twin-slack": "3.0.5"
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@volter/world",
3
- "version": "3.0.144",
3
+ "version": "3.0.145",
4
4
  "description": "Run your app against a world of twins. `World` and `Repo` — one method per verb: init, up, run, log, diff, reset, branch, checkout, clone, fetch, changeset, push — and the `volter` command, one client of them.",
5
5
  "keywords": [
6
6
  "volter",
@@ -31,12 +31,12 @@
31
31
  ],
32
32
  "dependencies": {
33
33
  "@modelcontextprotocol/sdk": "^1.30.1",
34
- "@volter/world-core": "3.0.144",
35
- "@volter/world-runtime": "3.0.144",
34
+ "@volter/world-core": "3.0.145",
35
+ "@volter/world-runtime": "3.0.145",
36
36
  "zod": "^4.6.5"
37
37
  },
38
38
  "peerDependencies": {
39
- "@volter/world-console": "3.0.139"
39
+ "@volter/world-console": "3.0.140"
40
40
  },
41
41
  "peerDependenciesMeta": {
42
42
  "@volter/world-console": {
@@ -44,7 +44,7 @@
44
44
  }
45
45
  },
46
46
  "devDependencies": {
47
- "@volter/world-console": "3.0.139"
47
+ "@volter/world-console": "3.0.140"
48
48
  },
49
49
  "bin": {
50
50
  "volter": "dist/src/cli.js"
package/skills/volter-world/AGENTS.md CHANGED
@@ -146,6 +146,10 @@ An app that answers as its own production hostnames (`app.example.com`) records
146
146
  2. Run `doctor`, then `tail --no-follow`, and inspect the twin's `GET /twin` manifest.
147
147
  3. Run `covers <world> --repo <app>` for missing vendor coverage.
148
148
  4. Determine whether the failure belongs to the app, twin fidelity, scenario, routing or runtime.
149
+ 5. A database preparation that fails at image build is fixed in that preparation (`runtime.database.prepare`
150
+ and what it runs against). `runtime.development.migrateDatabaseAtRuntime` is the app developer's setting for a
151
+ schema they are changing right now; it is never an operator's route past a failed preparation, and a World
152
+ that sets it is a development World whose image is not prepared.
149
153
 
150
154
  Sandbox mode refuses untwinned destinations in cooperating clients, including Node sockets a
151
155
  client opens around the injector. It does not constrain binaries or non-Node processes that