@volter/supercode-orchestrator 0.4.144 → 0.4.145

package/README.md

@@ -299,25 +299,13 @@ platforms:
       host: 127.0.0.1
       port: 8090
       key: ${API_SERVER_KEY}
-  rh2:                        # -> adapters/rh2.mjs: Runhuman Room conversations as a channel
-    enabled: true
-    token: ${RH2_SESSION_TOKEN}                 # the bot principal's automation session; a reference loads as a
-                                                # credential only at the block's top level or under extra:
-    extra:
-      api_url: https://pilot.runhuman.com
-      organization: peakhealth
-      principal_id: prn_…                       # the bot's own principal (is_me, mentions)
 ```
 
-**The RH2 adapter** (`adapters/rh2.mjs`) holds an RH2 session, follows every active Room the bot is
-a member of (or `extra.rooms`), polls each conversation it may read (`GET …/messages?after=`), turns
-a person's line (`kind: human`, or a trigger's `automation`) into an `inbound` on the key
-`{platform: rh2, kind: channel, chat_id: <roomId>/<conversationId>}`, and posts the reply as an
-`agent`-kind message authored as the bot. Typing is RH2 conversation presence, tried once and
-forgotten if the deployment has no door for it.
-
-Both blocks show up in `supercode channels list --harness orchestrator` through the reader that was
-already there — `configured` by key *presence*, never by reading a value.
+RH2 integration attaches through an admin-consented app installation. A hand-written
+`platforms: rh2` block grants no integration authority and the runtime reports it as
+unsupported. The reusable RH2 transport remains in `adapters/rh2.mjs`; the Room-chat
+module supplies its app-owned settings and credentials when that module is installed.
+Native Hermes channel configuration remains the worker's configuration.
 
 **The Chat SDK sidecar** mounts `chat@4.39.0` (npm package `chat`, repo `vercel/chat`; a
 devDependency of this package, installed alongside `@chat-adapter/state-memory@4.39.0`). The

package/adapters/rh2.mjs

@@ -16,19 +16,9 @@
 //   PATCH /rooms/:room/conversations/:c/messages/:id        {body} — a streamed reply grows, a progress line updates, by edit
 //   POST /rooms/:room/conversations/:c/presence            {state: "typing"} — best effort, forgotten on 404
 //
-// The block:
-//   platforms:
-//     rh2:
-//       enabled: true
-//       token: ${RH2_SESSION_TOKEN}                      # the bot principal's session (loads as credentials.token;
-//                                                        # a nested `credentials:` block is not read as one)
-//       extra:
-//         api_url: https://pilot.runhuman.com            # or the boundary's RH2 route
-//         organization: peakhealth
-//         headers: '{"x-twins-key":"…"}'                 # optional extra request headers (JSON)
-//         rooms: room_a,room_b                           # optional; default every active Room the bot is in
-//         principal_id: prn_…                            # the bot's own principal (is_me / mentions)
-//         poll_seconds: 2
+// This is reusable transport code. The daemon does not attach it from a
+// platforms block; an installed integration module owns its settings and token.
+// See docs/adr/0006-teams-installable-apps.md (C1) and the Room-chat module (M4).
 //
 // The surface key is `{platform: 'rh2', kind: 'channel', chat_id: '<roomId>'}`: a Room is one surface, so the agent it
 // seats is one session however many of the Room's conversations it takes part in. A line wakes it where RH2 says the bot

package/bin/runtime.mjs

@@ -65,7 +65,7 @@ import { hermesAccess } from '../hermes-cli.mjs';
 
 import {
   load, save, refreshVault, step, importFrom, exportTo, closeWorld, Orchestrator, LoopbackAdapter,
-  ChatSdkAdapter, ApiServerAdapter, Rh2Adapter,
+  ChatSdkAdapter, ApiServerAdapter,
   TICK_MS, accessPolicy, applyOperator, performRemoveProfileDir, OPERATOR_OPS,
 } from '../index.mjs';
 import * as events from '../events.mjs';
@@ -86,7 +86,6 @@ const ADAPTERS = {
   loopback: (platform, profile) => new LoopbackAdapter({ platform, profile }),
   'chat-sdk': (platform, profile, ctx) => new ChatSdkAdapter({ platform, profile, profileDir: ctx.state.profiles[profile]?.dir ?? null, channel: ctx.channel, vault: ctx.vault, log: ctx.log }),
   api_server: (platform, profile, ctx) => new ApiServerAdapter({ platform, profile, channel: ctx.channel, vault: ctx.vault, state: ctx.state, log: ctx.log }),
-  rh2: (platform, profile, ctx) => new Rh2Adapter({ platform, profile, channel: ctx.channel, vault: ctx.vault, refreshVault: () => refreshVault(ctx.state, ctx.vault), log: ctx.log }),
 };
 
 /// The selector a `platforms:` block resolves through: its `extra.adapter`
@@ -341,6 +340,7 @@ function buildAdapters(state, vault = new Map(), log = () => {}) {
         continue;
       }
       const selector = adapterSelector(platform, channel);
+      if(selector==='rh2'){report.push({platform,profile:profileName,state:'unsupported (RH2 integration requires an installed app; a platforms block grants no integration authority)'});continue;}
       const make = ADAPTERS[selector];
       if (!make) {
         report.push({ platform, profile: profileName, state: `unsupported (no adapter \`${selector}\` for this platform yet)` });

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@volter/supercode-orchestrator",
-  "version": "0.4.144",
+  "version": "0.4.145",
   "type": "module",
   "description": "The orchestrator runtime over the Volter Harness ontology: one typed operational model whose folder is its serialization, read and written through the harness orchestration doors (docs/ORCHESTRATOR-IR.md)",
   "exports": {