@volter/world 3.0.154 → 3.0.156

package/dist/examples/customer-onboarding/README.md

@@ -13,7 +13,7 @@ You need Node 22.6+, npm and registry access during installation. The browser pa
 Copy this starter into a new folder:
 
 ```console
-$ npx @volter/world@3.0.154 example customer-onboarding --dir onboarding
+$ npx @volter/world@3.0.156 example customer-onboarding --dir onboarding
 $ cd onboarding
 $ npm install
 ```

package/dist/examples/customer-onboarding/package.json

@@ -11,10 +11,10 @@
     "pg": "8.16.3"
   },
   "devDependencies": {
-    "@volter/world": "3.0.154",
+    "@volter/world": "3.0.156",
     "@volter/world-core": "3.0.147",
-    "@volter/world-runtime": "3.0.153",
-    "@volter/world-console": "3.0.147",
+    "@volter/world-runtime": "3.0.154",
+    "@volter/world-console": "3.0.148",
     "@volter/twin-stripe": "3.0.2",
     "@volter/twin-resend": "1.0.1"
   }

package/dist/examples/index.json

@@ -30,6 +30,7 @@
       "operate.mjs",
       "package.json",
       "public-files.json",
+      "read-slack-mail.mjs",
       "reset-receipts.mjs",
       "seed.mjs",
       "LICENSE"

package/dist/examples/integration-branches/README.md

@@ -13,7 +13,7 @@ Give two workers the same Stripe baseline, let them change different existing cu
 Use an empty parent folder. Create the baseline starter there:
 
 ```console
-$ npx @volter/world@3.0.154 example integration-branches --dir baseline
+$ npx @volter/world@3.0.156 example integration-branches --dir baseline
 $ cd baseline
 $ npm install
 $ ./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
 Create three more copies in the same parent folder:
 
 ```console
-$ npx @volter/world@3.0.154 example integration-branches --dir integration
-$ npx @volter/world@3.0.154 example integration-branches --dir worker-a
-$ npx @volter/world@3.0.154 example integration-branches --dir worker-b
+$ npx @volter/world@3.0.156 example integration-branches --dir integration
+$ npx @volter/world@3.0.156 example integration-branches --dir worker-a
+$ npx @volter/world@3.0.156 example integration-branches --dir worker-b
 ```
 
 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

@@ -9,10 +9,10 @@
     "stripe": "17.7.0"
   },
   "devDependencies": {
-    "@volter/world": "3.0.154",
+    "@volter/world": "3.0.156",
     "@volter/world-core": "3.0.147",
-    "@volter/world-runtime": "3.0.153",
-    "@volter/world-console": "3.0.147",
+    "@volter/world-runtime": "3.0.154",
+    "@volter/world-console": "3.0.148",
     "@volter/twin-stripe": "3.0.2"
   }
 }

package/dist/examples/workplace-agent/README.md

@@ -12,8 +12,14 @@ You need Node 22.6+, npm and registry access during installation. No platform ac
 
 ## Prepare an ordinary workplace
 
+This starter pins [GitHub 3.0.9](https://world.volter.ai/twins/github/~40volter~2Ftwin-github/3~2E0~2E9),
+[Linear 3.0.5](https://world.volter.ai/twins/linear/~40volter~2Ftwin-linear/3~2E0~2E5)
+and [Slack 3.0.8](https://world.volter.ai/twins/slack/~40volter~2Ftwin-slack/3~2E0~2E8).
+A catalog page may select a newer default. Keep this example's manifest and installation lock
+together; its recorded workflow does not establish behavior for a different release.
+
 ```console
-$ npx @volter/world@3.0.154 example workplace-agent --dir workplace
+$ npx @volter/world@3.0.156 example workplace-agent --dir workplace
 $ cd workplace
 $ npm install
 $ ./node_modules/.bin/volter world init --name workplace --twins github,linear,slack
@@ -82,6 +88,42 @@ The retry uses the recorded ticket and attempts only the notification. An uncert
 
 `company.json` and `outcomes/` are application files outside declared World services. They are not branched or reset with vendor history. After explicitly resetting this disposable World, clear only this example's receipts with `node reset-receipts.mjs`, restore the frozen clock, then seed again. Do not reuse receipts from one World with another.
 
+## Inspect Slack's local member screen
+
+The Slack twin provides workspace administration screens. They are separate from Slack's chat UI;
+read the handoff's ticket and channel messages with `operate.mjs read` as shown above.
+
+Stop the running World before starting its viewer. The viewer resumes the retained records and
+keeps running in the background:
+
+```console
+$ ./node_modules/.bin/volter world down
+$ ./node_modules/.bin/volter world view --no-open &
+$ workplace_view_pid=$!
+```
+
+Open the printed console link. Select **Slack** under **Records**, then **Its screens**.
+Choose **Sign in to Slack** and enter the synthetic default owner's address, `owner@world.test`.
+The screen asks for a confirmation code. Read the twin's captured mail in another terminal,
+from this app folder:
+
+```console
+$ ./node_modules/.bin/volter world run -- node read-slack-mail.mjs owner@world.test
+```
+
+[read-slack-mail.mjs](./read-slack-mail.mjs) reads Slack's declared local `/_twin/mail` endpoint.
+Enter the code from the latest message and continue to **Manage members**, where **World Owner**
+appears as the active primary owner. This uses synthetic local identity; no real Slack account or
+email delivery is involved. This walkthrough covers sign-in and the member list, not invitations
+or other administration actions.
+
+When finished, stop the viewer you started and retain the workplace:
+
+```console
+$ kill -INT "$workplace_view_pid"
+$ ./node_modules/.bin/volter world down
+```
+
 ## Create a synthetic GitHub organization
 
 Personal repositories use GitHub's ordinary create-repository API. Organization creation is a settings-page operation; this twin provides the declared `POST /_twin/orgs` endpoint for synthetic setup. [create-organization.mjs](./create-organization.mjs) discovers the authenticated account and sends:

package/dist/examples/workplace-agent/package.json

@@ -11,12 +11,12 @@
     "@slack/web-api": "7.19.0"
   },
   "devDependencies": {
-    "@volter/world": "3.0.154",
+    "@volter/world": "3.0.156",
     "@volter/world-core": "3.0.147",
-    "@volter/world-runtime": "3.0.153",
-    "@volter/world-console": "3.0.147",
-    "@volter/twin-github": "3.0.6",
-    "@volter/twin-linear": "3.0.4",
-    "@volter/twin-slack": "3.0.5"
+    "@volter/world-runtime": "3.0.154",
+    "@volter/world-console": "3.0.148",
+    "@volter/twin-github": "3.0.9",
+    "@volter/twin-linear": "3.0.5",
+    "@volter/twin-slack": "3.0.8"
   }
 }

package/dist/examples/workplace-agent/public-files.json

@@ -9,6 +9,7 @@
   "package-lock.json",
   "package.json",
   "public-files.json",
+  "read-slack-mail.mjs",
   "reset-receipts.mjs",
   "seed.mjs"
 ]

package/dist/examples/workplace-agent/read-slack-mail.mjs

@@ -0,0 +1,8 @@
+const base = process.env.SLACK_TWIN_URL;
+if (!base) throw new Error('Run this reader inside the workplace World.');
+const address = process.argv[2] ?? 'owner@world.test';
+const url = new URL('/_twin/mail', base);
+url.searchParams.set('to', address);
+const response = await fetch(url, { signal: AbortSignal.timeout(2000) });
+if (!response.ok) throw new Error(`Captured Slack mail: HTTP ${response.status}`);
+console.log(JSON.stringify(await response.json(), null, 2));

package/examples/customer-onboarding/README.md

@@ -13,7 +13,7 @@ You need Node 22.6+, npm and registry access during installation. The browser pa
 Copy this starter into a new folder:
 
 ```console
-$ npx @volter/world@3.0.154 example customer-onboarding --dir onboarding
+$ npx @volter/world@3.0.156 example customer-onboarding --dir onboarding
 $ cd onboarding
 $ npm install
 ```

package/examples/customer-onboarding/package.json

@@ -11,10 +11,10 @@
     "pg": "8.16.3"
   },
   "devDependencies": {
-    "@volter/world": "3.0.154",
+    "@volter/world": "3.0.156",
     "@volter/world-core": "3.0.147",
-    "@volter/world-runtime": "3.0.153",
-    "@volter/world-console": "3.0.147",
+    "@volter/world-runtime": "3.0.154",
+    "@volter/world-console": "3.0.148",
     "@volter/twin-stripe": "3.0.2",
     "@volter/twin-resend": "1.0.1"
   }

package/examples/index.json

@@ -30,6 +30,7 @@
       "operate.mjs",
       "package.json",
       "public-files.json",
+      "read-slack-mail.mjs",
       "reset-receipts.mjs",
       "seed.mjs",
       "LICENSE"

package/examples/integration-branches/README.md

@@ -13,7 +13,7 @@ Give two workers the same Stripe baseline, let them change different existing cu
 Use an empty parent folder. Create the baseline starter there:
 
 ```console
-$ npx @volter/world@3.0.154 example integration-branches --dir baseline
+$ npx @volter/world@3.0.156 example integration-branches --dir baseline
 $ cd baseline
 $ npm install
 $ ./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
 Create three more copies in the same parent folder:
 
 ```console
-$ npx @volter/world@3.0.154 example integration-branches --dir integration
-$ npx @volter/world@3.0.154 example integration-branches --dir worker-a
-$ npx @volter/world@3.0.154 example integration-branches --dir worker-b
+$ npx @volter/world@3.0.156 example integration-branches --dir integration
+$ npx @volter/world@3.0.156 example integration-branches --dir worker-a
+$ npx @volter/world@3.0.156 example integration-branches --dir worker-b
 ```
 
 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

@@ -9,10 +9,10 @@
     "stripe": "17.7.0"
   },
   "devDependencies": {
-    "@volter/world": "3.0.154",
+    "@volter/world": "3.0.156",
     "@volter/world-core": "3.0.147",
-    "@volter/world-runtime": "3.0.153",
-    "@volter/world-console": "3.0.147",
+    "@volter/world-runtime": "3.0.154",
+    "@volter/world-console": "3.0.148",
     "@volter/twin-stripe": "3.0.2"
   }
 }

package/examples/workplace-agent/README.md

@@ -12,8 +12,14 @@ You need Node 22.6+, npm and registry access during installation. No platform ac
 
 ## Prepare an ordinary workplace
 
+This starter pins [GitHub 3.0.9](https://world.volter.ai/twins/github/~40volter~2Ftwin-github/3~2E0~2E9),
+[Linear 3.0.5](https://world.volter.ai/twins/linear/~40volter~2Ftwin-linear/3~2E0~2E5)
+and [Slack 3.0.8](https://world.volter.ai/twins/slack/~40volter~2Ftwin-slack/3~2E0~2E8).
+A catalog page may select a newer default. Keep this example's manifest and installation lock
+together; its recorded workflow does not establish behavior for a different release.
+
 ```console
-$ npx @volter/world@3.0.154 example workplace-agent --dir workplace
+$ npx @volter/world@3.0.156 example workplace-agent --dir workplace
 $ cd workplace
 $ npm install
 $ ./node_modules/.bin/volter world init --name workplace --twins github,linear,slack
@@ -82,6 +88,42 @@ The retry uses the recorded ticket and attempts only the notification. An uncert
 
 `company.json` and `outcomes/` are application files outside declared World services. They are not branched or reset with vendor history. After explicitly resetting this disposable World, clear only this example's receipts with `node reset-receipts.mjs`, restore the frozen clock, then seed again. Do not reuse receipts from one World with another.
 
+## Inspect Slack's local member screen
+
+The Slack twin provides workspace administration screens. They are separate from Slack's chat UI;
+read the handoff's ticket and channel messages with `operate.mjs read` as shown above.
+
+Stop the running World before starting its viewer. The viewer resumes the retained records and
+keeps running in the background:
+
+```console
+$ ./node_modules/.bin/volter world down
+$ ./node_modules/.bin/volter world view --no-open &
+$ workplace_view_pid=$!
+```
+
+Open the printed console link. Select **Slack** under **Records**, then **Its screens**.
+Choose **Sign in to Slack** and enter the synthetic default owner's address, `owner@world.test`.
+The screen asks for a confirmation code. Read the twin's captured mail in another terminal,
+from this app folder:
+
+```console
+$ ./node_modules/.bin/volter world run -- node read-slack-mail.mjs owner@world.test
+```
+
+[read-slack-mail.mjs](./read-slack-mail.mjs) reads Slack's declared local `/_twin/mail` endpoint.
+Enter the code from the latest message and continue to **Manage members**, where **World Owner**
+appears as the active primary owner. This uses synthetic local identity; no real Slack account or
+email delivery is involved. This walkthrough covers sign-in and the member list, not invitations
+or other administration actions.
+
+When finished, stop the viewer you started and retain the workplace:
+
+```console
+$ kill -INT "$workplace_view_pid"
+$ ./node_modules/.bin/volter world down
+```
+
 ## Create a synthetic GitHub organization
 
 Personal repositories use GitHub's ordinary create-repository API. Organization creation is a settings-page operation; this twin provides the declared `POST /_twin/orgs` endpoint for synthetic setup. [create-organization.mjs](./create-organization.mjs) discovers the authenticated account and sends:

package/examples/workplace-agent/package.json

@@ -11,12 +11,12 @@
     "@slack/web-api": "7.19.0"
   },
   "devDependencies": {
-    "@volter/world": "3.0.154",
+    "@volter/world": "3.0.156",
     "@volter/world-core": "3.0.147",
-    "@volter/world-runtime": "3.0.153",
-    "@volter/world-console": "3.0.147",
-    "@volter/twin-github": "3.0.6",
-    "@volter/twin-linear": "3.0.4",
-    "@volter/twin-slack": "3.0.5"
+    "@volter/world-runtime": "3.0.154",
+    "@volter/world-console": "3.0.148",
+    "@volter/twin-github": "3.0.9",
+    "@volter/twin-linear": "3.0.5",
+    "@volter/twin-slack": "3.0.8"
   }
 }

package/examples/workplace-agent/public-files.json

@@ -9,6 +9,7 @@
   "package-lock.json",
   "package.json",
   "public-files.json",
+  "read-slack-mail.mjs",
   "reset-receipts.mjs",
   "seed.mjs"
 ]

package/examples/workplace-agent/read-slack-mail.mjs

@@ -0,0 +1,8 @@
+const base = process.env.SLACK_TWIN_URL;
+if (!base) throw new Error('Run this reader inside the workplace World.');
+const address = process.argv[2] ?? 'owner@world.test';
+const url = new URL('/_twin/mail', base);
+url.searchParams.set('to', address);
+const response = await fetch(url, { signal: AbortSignal.timeout(2000) });
+if (!response.ok) throw new Error(`Captured Slack mail: HTTP ${response.status}`);
+console.log(JSON.stringify(await response.json(), null, 2));

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@volter/world",
-  "version": "3.0.154",
+  "version": "3.0.156",
   "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.",
   "keywords": [
     "volter",
@@ -32,11 +32,11 @@
   "dependencies": {
     "@modelcontextprotocol/sdk": "^1.30.1",
     "@volter/world-core": "3.0.147",
-    "@volter/world-runtime": "3.0.153",
+    "@volter/world-runtime": "3.0.154",
     "zod": "^4.6.5"
   },
   "peerDependencies": {
-    "@volter/world-console": "3.0.147"
+    "@volter/world-console": "3.0.148"
   },
   "peerDependenciesMeta": {
     "@volter/world-console": {
@@ -44,7 +44,7 @@
     }
   },
   "devDependencies": {
-    "@volter/world-console": "3.0.147"
+    "@volter/world-console": "3.0.148"
   },
   "bin": {
     "volter": "dist/src/cli.js"