@sellable/install 0.1.325 → 0.1.327

package/README.md

@@ -122,17 +122,6 @@ It creates:
 /srv/hermes/profiles/acme/.env        # only when Slack token inputs are supplied
 ```
 
-Bootstrap also writes `SELLABLE_LOCK_WORKSPACE_ID=<workspace-id>` and
-`SELLABLE_REQUIRE_WORKSPACE_LOCK=1` into the profile's Hermes MCP env.
-Customer profiles are therefore locked to their own Sellable workspace:
-Sellable MCP requests are forced to that workspace, workspace switching/creation
-is blocked, workspace listings are filtered, and a missing lock fails closed
-instead of falling back to shared/admin config. Use the `sellable-admin` profile
-for provisioning or cross-profile inspection.
-
-See [`HERMES-SLACK-PROFILE-SCOPING.md`](./HERMES-SLACK-PROFILE-SCOPING.md) for
-the customer Slack isolation contract and Socket Mode token requirements.
-
 If no token is supplied, bootstrap still creates a pending
 `sellable/config.json` so the profile path is concrete from the first MCP
 launch. Finish auth with:
@@ -153,36 +142,6 @@ sellable hermes profile bootstrap \
   --slack-app-token "$SLACK_APP_TOKEN"
 ```
 
-The Slack app must also be configured for inbound Socket Mode delivery. Outbound
-Slack Web API sends can work before this is complete, but Hermes will not hear
-mentions until the app has Socket Mode enabled, an app-level token with
-`connections:write`, bot scopes/events for `app_mention` plus channel/group/IM
-message events, and a fresh workspace reinstall after scope or event changes.
-
-Scope the profile to its customer channel at install time:
-
-```bash
-sellable hermes profile bootstrap \
-  --profile acme \
-  --profiles-root /srv/hermes/profiles \
-  --workspace-id ws_acme \
-  --slack-bot-token "$SLACK_BOT_TOKEN" \
-  --slack-app-token "$SLACK_APP_TOKEN" \
-  --slack-home-channel C0ACME12345 \
-  --slack-home-channel-name sellable-acme \
-  --slack-allowed-users U0OPERATOR1 \
-  --slack-require-mention true
-```
-
-When `--slack-home-channel` is supplied without
-`--slack-allowed-channels`, bootstrap writes
-`SLACK_ALLOWED_CHANNELS=<home-channel-id>` too. That fail-closes a customer
-profile to the intended channel by default. Use
-`--slack-allowed-channels C...,G...` only when a profile is deliberately allowed
-to listen in multiple channels. Pass channel IDs, not `#channel-name`, and use
-separate Slack bot/app tokens per customer profile when you need hard isolation
-between concurrently listening Hermes profiles.
-
 Customer profiles should use customer-scoped Sellable credentials. A shared
 Sellable admin token can work for internal admin automation, but it is weaker
 isolation and should not be the default for customer profiles. After changing
@@ -212,6 +171,7 @@ source-scout agents.
 Use the same public entrypoints across supported hosts:
 
 - Claude Code: `/sellable:create-campaign`
+- Claude Code: `/sellable:find-leads`
 - Claude Code: `/sellable:create-ab-test`
 - Claude Code: `/sellable:create-evergreen-campaigns`
 - Claude Code: `/sellable:foundation`
@@ -220,6 +180,7 @@ Use the same public entrypoints across supported hosts:
 - Claude Code: `/sellable:refresh-sender-engagement`
 - Claude Code: `/sellable:refill-sends`
 - Codex: `$sellable:create-campaign`
+- Codex: `$sellable:find-leads`
 - Codex: `$sellable:create-ab-test`
 - Codex: `$sellable:create-evergreen-campaigns`
 - Codex: `$sellable:foundation`
@@ -228,6 +189,7 @@ Use the same public entrypoints across supported hosts:
 - Codex: `$sellable:refresh-sender-engagement`
 - Codex: `$sellable:refill-sends`
 - Hermes: `/sellable-create-campaign`
+- Hermes: `/sellable-find-leads`
 - Hermes: `/sellable-create-ab-test`
 - Hermes: `/sellable-create-evergreen-campaigns`
 - Hermes: `/sellable-foundation`
@@ -237,6 +199,7 @@ Use the same public entrypoints across supported hosts:
 - Hermes: `/sellable-refill-sends`
 - Codex Desktop plugin: `sellable@sellable`
 - Codex visible skill: `Sellable Create Campaign`
+- Codex visible skill: `Sellable Find Leads`
 - Codex visible skill: `Sellable Create A/B Test`
 - Codex visible skill: `Sellable Create Evergreen Campaigns`
 - Codex visible skill: `Sellable Foundation`
@@ -245,6 +208,7 @@ Use the same public entrypoints across supported hosts:
 - Codex visible skill: `Sellable Refresh Sender Engagement`
 - Codex visible skill: `Sellable Refill Sends`
 - Internal MCP workflow prompt: `create-campaign-v2`
+- Internal MCP workflow prompt: `find-leads-v2`
 - Internal MCP workflow prompt: `refill-sends-workflow`
 - Internal/backward-compatible memory prompt: `interview`
 

package/agents/registry.json

@@ -26,8 +26,8 @@
       "ownership": "message strategy, proof inventory, token rules, skeptical-prospect review, and selected winner only",
       "codex": {
         "description": "Message Drafting worker for campaign-backed template proposals after confirm_lead_list imports a non-empty bounded review batch.",
-        "model": "gpt-5.6-sol",
-        "modelReasoningEffort": "high",
+        "model": "gpt-5.5",
+        "modelReasoningEffort": "xhigh",
         "sandboxMode": "read-only",
         "nicknameCandidates": [
           "Message Drafting",