@sellable/install 0.1.331 → 0.1.332-hermes031.202607110338

package/HERMES-SLACK-PROFILE-SCOPING.md

@@ -15,9 +15,6 @@ customer's profile-local Sellable MCP config. Customer profiles must not store
 or read Sellable Admin MCP credentials, admin Slack app tokens, or sibling
 profile config.
 
-The shared dispatcher remains a fallback/research path only. Use it only when
-Sellable Admin explicitly owns one shared listener and route registry.
-
 The 2026-07-06 Hostinger POC proved the native Hermes listener for the
 `sellable-admin` profile with the existing `Sellable Reply Bot` app in
 `#team-chat`: a human mention produced a new Hermes session and a threaded bot
@@ -34,8 +31,7 @@ hermes --profile acme send --to slack:C0BFERDV3N0 --subject '[Hermes acme smoke]
 
 That succeeded and is useful as an internal smoke test. It does not change the
 inbound listener rule: each active customer profile needs its own native Slack
-app token pair unless Sellable Admin deliberately chooses the dispatcher
-fallback.
+app token pair.
 
 ## Which Slack Values Are Enough
 
@@ -128,27 +124,14 @@ closed before making Sellable API calls instead of falling back to shared or
 admin config state. Only the `sellable-admin` profile should provision,
 inspect, or repair other profiles.
 
-For the shared dispatcher model, do not copy the shared `SLACK_BOT_TOKEN` or
-`SLACK_APP_TOKEN` into customer profile `.env` files. The dispatcher owns those
-tokens and route metadata decides the customer profile.
-
-## Shared Dispatcher Ownership
-
-The shared Slack dispatcher and its route registry are fallback Sellable Admin
-surfaces. This customer-facing installer must not create shared route bundles or
-write shared listener tokens. Sellable Admin owns Slack app creation and profile
-provisioning, then calls this installer for profile-local Sellable runtime
-bootstrap inside the already-provisioned Hermes profile.
-
 ## Verification
 
-Run the installer and dispatcher UAT before publishing installer changes:
+Run the installer and native profile UAT before publishing installer changes:
 
 ```bash
 npm run test:unit -- tests/install-package/agent-preferences.test.ts
 scripts/run-phase92-hermes-profile-bootstrap-uat.sh --mode local-temp
 scripts/run-phase92-hermes-profile-bootstrap-uat.sh --mode linux-shaped
-scripts/run-phase031-hermes-slack-dispatcher-uat.sh --mode local-fixture
 ```
 
 Expected proof:

package/bin/sellable-install.mjs

@@ -48,7 +48,7 @@ function getInstallVersion() {
   }
 }
 
-const CODEX_PLUGIN_VERSION = "0.1.61";
+const CODEX_PLUGIN_VERSION = "0.1.62-hermes031.202607110338";
 const CODEX_PLUGIN_COMPAT_VERSIONS = [
   "0.1.8",
   "0.1.9",
@@ -240,11 +240,9 @@ Hermes profile bootstrap:
   workspace id is supplied, so a customer profile fails closed if the workspace
   lock is later removed or not yet provisioned.
 
-Hermes shared Slack dispatcher:
-  Shared listener setup and route-registry validation are internal Sellable
-  Admin responsibilities. This customer-facing installer only bootstraps a
-  profile-local Sellable runtime after Sellable Admin provisions the profile
-  and dispatcher route.
+Hermes customer Slack runtime:
+  Each customer profile uses its own dedicated native Slack app and gateway.
+  Sellable Admin owns the single resumable customer bootstrap interface.
 `;
 }
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@sellable/install",
-  "version": "0.1.331",
+  "version": "0.1.332-hermes031.202607110338",
   "type": "module",
   "description": "One-command installer for Sellable MCP in Claude Code, Codex, and Hermes",
   "bin": {