@volter/world 3.0.184 → 3.0.185

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 +2 -2
  3. package/dist/examples/integration-branches/README.md +4 -4
  4. package/dist/examples/integration-branches/package.json +2 -2
  5. package/dist/examples/workplace-agent/README.md +1 -1
  6. package/dist/examples/workplace-agent/package.json +2 -2
  7. package/dist/skills/volter-world/AGENTS.md +2 -2
  8. package/examples/customer-onboarding/README.md +1 -1
  9. package/examples/customer-onboarding/package.json +2 -2
  10. package/examples/integration-branches/README.md +4 -4
  11. package/examples/integration-branches/package.json +2 -2
  12. package/examples/workplace-agent/README.md +1 -1
  13. package/examples/workplace-agent/package.json +2 -2
  14. package/package.json +2 -2
  15. package/skills/volter-world/AGENTS.md +2 -2
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.184 example customer-onboarding --dir onboarding
16
+ $ npx @volter/world@3.0.185 example customer-onboarding --dir onboarding
17
17
  $ cd onboarding
18
18
  $ pnpm install
19
19
  ```
package/dist/examples/customer-onboarding/package.json CHANGED
@@ -11,9 +11,9 @@
11
11
  "pg": "8.16.3"
12
12
  },
13
13
  "devDependencies": {
14
- "@volter/world": "3.0.184",
14
+ "@volter/world": "3.0.185",
15
15
  "@volter/world-core": "3.0.161",
16
- "@volter/world-runtime": "3.0.181",
16
+ "@volter/world-runtime": "3.0.182",
17
17
  "@volter/world-console": "3.0.157",
18
18
  "@volter/twin-stripe": "3.0.2",
19
19
  "@volter/twin-resend": "1.0.1",
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.184 example integration-branches --dir baseline
16
+ $ npx @volter/world@3.0.185 example integration-branches --dir baseline
17
17
  $ cd baseline
18
18
  $ pnpm install
19
19
  $ ./node_modules/.bin/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.184 example integration-branches --dir integration
42
- $ npx @volter/world@3.0.184 example integration-branches --dir worker-a
43
- $ npx @volter/world@3.0.184 example integration-branches --dir worker-b
41
+ $ npx @volter/world@3.0.185 example integration-branches --dir integration
42
+ $ npx @volter/world@3.0.185 example integration-branches --dir worker-a
43
+ $ npx @volter/world@3.0.185 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,9 +9,9 @@
9
9
  "stripe": "17.7.0"
10
10
  },
11
11
  "devDependencies": {
12
- "@volter/world": "3.0.184",
12
+ "@volter/world": "3.0.185",
13
13
  "@volter/world-core": "3.0.161",
14
- "@volter/world-runtime": "3.0.181",
14
+ "@volter/world-runtime": "3.0.182",
15
15
  "@volter/world-console": "3.0.157",
16
16
  "@volter/twin-stripe": "3.0.2",
17
17
  "@volter/world-ui": "1.0.161"
package/dist/examples/workplace-agent/README.md CHANGED
@@ -19,7 +19,7 @@ The catalog offers current defaults. Keep this example's manifest and installati
19
19
  together; its recorded workflow does not establish behavior for a different release.
20
20
 
21
21
  ```console
22
- $ npx @volter/world@3.0.184 example workplace-agent --dir workplace
22
+ $ npx @volter/world@3.0.185 example workplace-agent --dir workplace
23
23
  $ cd workplace
24
24
  $ pnpm install
25
25
  $ ./node_modules/.bin/volter world init --name workplace --twins github,linear,slack
package/dist/examples/workplace-agent/package.json CHANGED
@@ -11,9 +11,9 @@
11
11
  "@slack/web-api": "7.19.0"
12
12
  },
13
13
  "devDependencies": {
14
- "@volter/world": "3.0.184",
14
+ "@volter/world": "3.0.185",
15
15
  "@volter/world-core": "3.0.161",
16
- "@volter/world-runtime": "3.0.181",
16
+ "@volter/world-runtime": "3.0.182",
17
17
  "@volter/world-console": "3.0.157",
18
18
  "@volter/twin-github": "3.0.9",
19
19
  "@volter/twin-linear": "3.0.5",
package/dist/skills/volter-world/AGENTS.md CHANGED
@@ -33,8 +33,8 @@ subject to sandbox and network policy. Remove that vendor's fake values and endp
33
33
  keep live credentials out of the config and generated World env. Follow
34
34
  [turn a service off](../../docs/guides/turn-a-service-off.md), including its credential-launch order.
35
35
  `volter world view --no-open` runs the World with its
36
- dashboard and prints its link for the person; it keeps running, so start it in the background,
37
- and stop a World you started with `up` first (`down` keeps its state).
36
+ dashboard and prints its link for the person; it keeps running, so start it in the background.
37
+ It reuses a World already running; closing the viewer stops only compute the viewer started.
38
38
 
39
39
  ## Share it on a platform
40
40
 
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.184 example customer-onboarding --dir onboarding
16
+ $ npx @volter/world@3.0.185 example customer-onboarding --dir onboarding
17
17
  $ cd onboarding
18
18
  $ pnpm install
19
19
  ```
package/examples/customer-onboarding/package.json CHANGED
@@ -11,9 +11,9 @@
11
11
  "pg": "8.16.3"
12
12
  },
13
13
  "devDependencies": {
14
- "@volter/world": "3.0.184",
14
+ "@volter/world": "3.0.185",
15
15
  "@volter/world-core": "3.0.161",
16
- "@volter/world-runtime": "3.0.181",
16
+ "@volter/world-runtime": "3.0.182",
17
17
  "@volter/world-console": "3.0.157",
18
18
  "@volter/twin-stripe": "3.0.2",
19
19
  "@volter/twin-resend": "1.0.1",
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.184 example integration-branches --dir baseline
16
+ $ npx @volter/world@3.0.185 example integration-branches --dir baseline
17
17
  $ cd baseline
18
18
  $ pnpm install
19
19
  $ ./node_modules/.bin/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.184 example integration-branches --dir integration
42
- $ npx @volter/world@3.0.184 example integration-branches --dir worker-a
43
- $ npx @volter/world@3.0.184 example integration-branches --dir worker-b
41
+ $ npx @volter/world@3.0.185 example integration-branches --dir integration
42
+ $ npx @volter/world@3.0.185 example integration-branches --dir worker-a
43
+ $ npx @volter/world@3.0.185 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,9 +9,9 @@
9
9
  "stripe": "17.7.0"
10
10
  },
11
11
  "devDependencies": {
12
- "@volter/world": "3.0.184",
12
+ "@volter/world": "3.0.185",
13
13
  "@volter/world-core": "3.0.161",
14
- "@volter/world-runtime": "3.0.181",
14
+ "@volter/world-runtime": "3.0.182",
15
15
  "@volter/world-console": "3.0.157",
16
16
  "@volter/twin-stripe": "3.0.2",
17
17
  "@volter/world-ui": "1.0.161"
package/examples/workplace-agent/README.md CHANGED
@@ -19,7 +19,7 @@ The catalog offers current defaults. Keep this example's manifest and installati
19
19
  together; its recorded workflow does not establish behavior for a different release.
20
20
 
21
21
  ```console
22
- $ npx @volter/world@3.0.184 example workplace-agent --dir workplace
22
+ $ npx @volter/world@3.0.185 example workplace-agent --dir workplace
23
23
  $ cd workplace
24
24
  $ pnpm install
25
25
  $ ./node_modules/.bin/volter world init --name workplace --twins github,linear,slack
package/examples/workplace-agent/package.json CHANGED
@@ -11,9 +11,9 @@
11
11
  "@slack/web-api": "7.19.0"
12
12
  },
13
13
  "devDependencies": {
14
- "@volter/world": "3.0.184",
14
+ "@volter/world": "3.0.185",
15
15
  "@volter/world-core": "3.0.161",
16
- "@volter/world-runtime": "3.0.181",
16
+ "@volter/world-runtime": "3.0.182",
17
17
  "@volter/world-console": "3.0.157",
18
18
  "@volter/twin-github": "3.0.9",
19
19
  "@volter/twin-linear": "3.0.5",
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@volter/world",
3
- "version": "3.0.184",
3
+ "version": "3.0.185",
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",
@@ -32,7 +32,7 @@
32
32
  "dependencies": {
33
33
  "@modelcontextprotocol/sdk": "^1.30.1",
34
34
  "@volter/world-core": "3.0.161",
35
- "@volter/world-runtime": "3.0.181",
35
+ "@volter/world-runtime": "3.0.182",
36
36
  "zod": "^4.6.5"
37
37
  },
38
38
  "peerDependencies": {
package/skills/volter-world/AGENTS.md CHANGED
@@ -33,8 +33,8 @@ subject to sandbox and network policy. Remove that vendor's fake values and endp
33
33
  keep live credentials out of the config and generated World env. Follow
34
34
  [turn a service off](../../docs/guides/turn-a-service-off.md), including its credential-launch order.
35
35
  `volter world view --no-open` runs the World with its
36
- dashboard and prints its link for the person; it keeps running, so start it in the background,
37
- and stop a World you started with `up` first (`down` keeps its state).
36
+ dashboard and prints its link for the person; it keeps running, so start it in the background.
37
+ It reuses a World already running; closing the viewer stops only compute the viewer started.
38
38
 
39
39
  ## Share it on a platform
40
40