@sellable/mcp 0.1.557 → 0.1.559

package/dist/tools/workspaces.js

@@ -1,5 +1,5 @@
 import { getApi, resetApi } from "../api.js";
-import { getConfig, updateActiveWorkspace } from "../auth.js";
+import { getConfig, getEffectiveConfiguredWorkspaceId, getLockedWorkspaceId, resolveWorkspaceIdForRequest, updateActiveWorkspace, } from "../auth.js";
 export const workspaceToolDefinitions = [
     {
         name: "list_workspaces",
@@ -81,21 +81,53 @@ export const workspaceToolDefinitions = [
 export async function listWorkspaces() {
     const api = getApi();
     const { workspaces } = await api.get("/api/v3/workspaces");
-    return { workspaces };
+    const lockedWorkspaceId = getLockedWorkspaceId();
+    if (!lockedWorkspaceId) {
+        return { workspaces, workspaceLock: { enabled: false } };
+    }
+    return {
+        workspaces: workspaces.filter((ws) => ws.id === lockedWorkspaceId),
+        workspaceLock: {
+            enabled: true,
+            workspaceId: lockedWorkspaceId,
+            hiddenWorkspaceCount: workspaces.filter((ws) => ws.id !== lockedWorkspaceId).length,
+        },
+    };
 }
 export function getActiveWorkspace() {
     const config = getConfig();
+    const lockedWorkspaceId = getLockedWorkspaceId();
     return {
-        activeWorkspaceId: config.activeWorkspaceId || config.workspaceId || null,
+        activeWorkspaceId: getEffectiveConfiguredWorkspaceId(config),
         activeWorkspaceName: config.activeWorkspaceName || null,
+        workspaceLock: lockedWorkspaceId
+            ? { enabled: true, workspaceId: lockedWorkspaceId }
+            : { enabled: false },
     };
 }
 export async function getWorkspace(workspaceId) {
+    const allowedWorkspaceId = resolveWorkspaceIdForRequest(workspaceId, "get_workspace");
+    if (!allowedWorkspaceId) {
+        return {
+            ok: false,
+            error: "No active workspace selected.",
+        };
+    }
     const api = getApi();
-    const { workspace } = await api.get(`/api/v3/workspaces/${encodeURIComponent(workspaceId)}`);
+    const { workspace } = await api.get(`/api/v3/workspaces/${encodeURIComponent(allowedWorkspaceId)}`);
     return { workspace };
 }
 export async function setActiveWorkspace(workspaceId, userConfirmed) {
+    const lockedWorkspaceId = getLockedWorkspaceId();
+    if (lockedWorkspaceId && workspaceId !== lockedWorkspaceId) {
+        return {
+            ok: false,
+            code: "WORKSPACE_LOCKED",
+            activeWorkspaceId: lockedWorkspaceId,
+            requestedWorkspaceId: workspaceId,
+            error: "This Hermes profile is locked to its customer workspace and cannot switch workspaces.",
+        };
+    }
     const api = getApi();
     const { workspaces } = await api.get("/api/v3/workspaces");
     const match = workspaces.find((ws) => ws.id === workspaceId);
@@ -131,6 +163,15 @@ export async function setActiveWorkspace(workspaceId, userConfirmed) {
     };
 }
 export async function createWorkspace(name) {
+    const lockedWorkspaceId = getLockedWorkspaceId();
+    if (lockedWorkspaceId) {
+        return {
+            ok: false,
+            code: "WORKSPACE_LOCKED",
+            activeWorkspaceId: lockedWorkspaceId,
+            error: "This Hermes profile is locked to its customer workspace and cannot create or switch workspaces. Use the sellable-admin profile for provisioning.",
+        };
+    }
     const api = getApi();
     const { workspace } = await api.post("/api/v3/workspaces", { name });
     updateActiveWorkspace({
@@ -146,7 +187,9 @@ export async function createWorkspace(name) {
 export async function addTeammate(input) {
     const args = input || {};
     const config = getConfig();
-    const workspaceId = args.workspaceId || config.activeWorkspaceId || config.workspaceId;
+    const workspaceId = resolveWorkspaceIdForRequest(args.workspaceId ||
+        getEffectiveConfiguredWorkspaceId(config) ||
+        undefined, "add_teammate");
     if (!workspaceId) {
         return {
             ok: false,

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@sellable/mcp",
-  "version": "0.1.557",
+  "version": "0.1.559",
   "type": "module",
   "description": "Sellable MCP server for Claude Code, Codex, and Hermes campaign workflows",
   "main": "dist/index.js",

package/skills/create-campaign/SKILL.md

@@ -721,7 +721,7 @@ Treat host capabilities as concrete functions, not prose conventions:
   import and before dispatching Message Drafting only.
 - `launch_message_drafting`: Claude Code uses `Task` with `subagent_type`
   `post-find-leads-message-scout` when listed; Codex uses the returned
-  compatibility agent or a generic `gpt-5.5` / `xhigh` Message Drafting agent.
+  compatibility agent or a generic `gpt-5.6-sol` / `high` Message Drafting agent.
 
 If a required interactive question function or MCP loader is missing, stop and
 explain the Sellable install/reload problem. Source work uses product-native MCP
@@ -1082,8 +1082,8 @@ updates.
    In Codex, the filter-choice answer is the campaign-scoped go-ahead to use
    this single Message Drafting background agent in step-wise and YOLO modes.
    Do not ask a separate question to start it. If the named custom agent is not
-   available, spawn a generic background agent with `model: "gpt-5.5"` and
-   `reasoning_effort: "xhigh"` using the same lean campaign/table basis. If no
+   available, spawn a generic background agent with `model: "gpt-5.6-sol"` and
+   `reasoning_effort: "high"` using the same lean campaign/table basis. If no
    background-agent tool is callable, start the same full message branch inline
    before filter drafting or skip-filter message review and record it as
    `statusSource: "parent-thread-fallback"`.

package/skills/create-campaign-v2/SKILL.md

@@ -291,7 +291,7 @@ in the branch read means "filters still owned by parent," not `blocked`.
 
 Keep the handoff lean: `campaignId`, `workflowTableId`, concise brief/source summary, source-use rule, and 3-5 sample rows (`rowId`, name, title, company, signal). Do not paste copied row counts, hashes, full row IDs, broad row data, or local debug artifacts.
 
-Route user copy feedback before `approve-message` back to Message Drafting; parent does not rewrite. The branch loads the full `generate-messages` prompt, every required asset, then `get_subskill_prompt({ subskillName: "create-campaign-v2-validation" })`; do not render `renderedFallbackSample`, concerns, or `qaReceipt` in the happy path. Generic fallback is `gpt-5.5` / `xhigh` Message Drafting. Handoff is labeled Markdown, not raw JSON.
+Route user copy feedback before `approve-message` back to Message Drafting; parent does not rewrite. The branch loads the full `generate-messages` prompt, every required asset, then `get_subskill_prompt({ subskillName: "create-campaign-v2-validation" })`; do not render `renderedFallbackSample`, concerns, or `qaReceipt` in the happy path. Generic fallback is `gpt-5.6-sol` / `high` Message Drafting. Handoff is labeled Markdown, not raw JSON.
 
 ## Hard Gates
 

package/skills/create-evergreen-campaigns/SKILL.md

@@ -437,7 +437,7 @@ fallback only when app thread tools are unavailable; the receipt must include
 `fallbackReason`, or backend verify rejects it.
 When visible Codex app thread tools are unavailable but local Codex CLI is
 available, the accepted durable streaming-worker command shape is:
-`codex -a never -s danger-full-access -c model_reasoning_effort=xhigh exec --skip-git-repo-check -m <worker-model> -C <repo> -o <worker-final-file> -`.
+`codex -a never -s danger-full-access -c model_reasoning_effort=high exec --skip-git-repo-check -m <worker-model> -C <repo> -o <worker-final-file> -`.
 The approval, sandbox, and reasoning-effort config flags must come before the
 `exec` subcommand for Codex CLI builds that expose `-a`/`-s`/`-c` only at top
 level. `--skip-git-repo-check` belongs after `exec` because current customer and VPS Codex CLI builds expose it
@@ -447,26 +447,26 @@ forms fail on current customer CLI installs. Pipe the lane packet prompt on
 stdin, require the worker to write `workerDispatch.receiptArtifactHint`, and
 pass exactly one lane packet per worker.
 When launching durable Codex CLI workers from an automation parent, pass an
-explicit supported worker model and explicit `xhigh` reasoning effort instead
+explicit supported worker model and explicit `high` reasoning effort instead
 of relying on the Codex CLI defaults. Use the parent runtime model when known,
 for example:
-`codex -a never -s danger-full-access -c model_reasoning_effort=xhigh exec --skip-git-repo-check -m <worker-model> -C <repo> -o <worker-final-file> -`.
+`codex -a never -s danger-full-access -c model_reasoning_effort=high exec --skip-git-repo-check -m <worker-model> -C <repo> -o <worker-final-file> -`.
 In Codex CLI, the parent runtime model is visible in the run header as
 `model: <model-name>`. Copy that exact model string into child worker launches
-first. If the parent header says `model: gpt-5.5`, launch workers with
-`-m gpt-5.5` plus `-c model_reasoning_effort=xhigh`; do not invent or probe
+first. If the parent header says `model: gpt-5.6-sol`, launch workers with
+`-m gpt-5.6-sol` plus `-c model_reasoning_effort=high`; do not invent or probe
 nearby aliases such as `gpt-5.3-codex`, `gpt-5.2`, `gpt-5-codex`,
 `codex-latest`, or `codex-mini-latest` before trying the exact parent model. A
-one-line probe must include the same `-c model_reasoning_effort=xhigh` override
+one-line probe must include the same `-c model_reasoning_effort=high` override
 and count as supported only when it exits 0 and returns the requested output; a
 session header followed by a `not supported` error is rejected, not accepted.
 Do not rely on the Codex CLI default model or default reasoning effort; some
-customer and VPS installs default to unavailable model aliases or to `high`
-reasoning. `-m gpt-5.5` alone is not enough. If a child worker reports GPT 5.5
-with `high` reasoning, treat that as a launcher bug, relaunch with the explicit
-`xhigh` config before mutation, and do not ask the user to continue through the
+customer and VPS installs default to unavailable model aliases or to reasoning
+below `high`. `-m gpt-5.6-sol` alone is not enough. If a child worker reports GPT 5.6-Sol
+with reasoning below `high`, treat that as a launcher bug, relaunch with the explicit
+`high` config before mutation, and do not ask the user to continue through the
 model-quality warning. If the parent cannot identify a supported worker model
-and launch it with `xhigh` reasoning, stop with
+and launch it with `high` reasoning, stop with
 `blocked: worker_model_unavailable` before mutation.
 When wrapping multiple local Codex CLI workers in a shell launcher, run the
 wrapper with `/bin/bash -lc` or another explicitly chosen portable shell. Do not
@@ -479,7 +479,7 @@ Do not embed `<<'WORKER_PROMPT'` heredocs inside a single quoted or double
 quoted `/bin/bash -lc '...'` command string; nested quoting is brittle and can
 truncate the first worker before mutation. For multi-worker launchers, write one
 plain prompt file per lane under the current run directory, then start each
-worker with `codex -a never -s danger-full-access -c model_reasoning_effort=xhigh exec --skip-git-repo-check -m "$WORKER_MODEL" -C "$REPO" -o
+worker with `codex -a never -s danger-full-access -c model_reasoning_effort=high exec --skip-git-repo-check -m "$WORKER_MODEL" -C "$REPO" -o
 "$worker_final_file" - < "$worker_prompt_file"`. Keep launcher shell variables
 double-quoted and keep the prompt heredoc only in a standalone script/prompt-file
 write step, not inside an already quoted shell argument. If the first launcher
@@ -585,7 +585,7 @@ launchers, write the same prompt body to `<worker-prompt-file>` and launch the
 worker with stdin redirected from that file:
 
 ```
-codex -a never -s danger-full-access -c model_reasoning_effort=xhigh exec --skip-git-repo-check -m <worker-model> -C <repo> -o <worker-final-file> - <<'WORKER_PROMPT'
+codex -a never -s danger-full-access -c model_reasoning_effort=high exec --skip-git-repo-check -m <worker-model> -C <repo> -o <worker-final-file> - <<'WORKER_PROMPT'
 Use $sellable:create-campaign as the governing campaign workflow for this one lane worker.
 Use the evergreen plan/packet below only for lane scope, source metadata,
 postconditions, side-effect caps, and durable receipt proof.
@@ -632,10 +632,10 @@ Do not launch, start, schedule, send, or use paid InMail.
 For filter proof, durable receipt status must be `filterDecisionReceipt.status:"applied"` only; never `completed`, `confirmed`, `done`, or aliases.
 For generated messages, `update_cell` is allowed only for the semantic Approved checkbox. Never use `update_cell` for generated message text/body/sample copy. Bad copy requires `revise_message_template_and_rerun` or brief/template revision plus Generate Message rerun. Any generated-message cell override is `blocked: generated_message_cell_override`.
 If `bootstrap_create_campaign.modelQuality.status === "warn"` because the child
-worker reports GPT 5.5 with `high` reasoning, that is a parent launcher
+worker reports GPT 5.6-Sol with reasoning below `high`, that is a parent launcher
 configuration bug, not an operator approval path inside the worker. Stop before
 mutation, tell the parent to relaunch this lane with
-`-c model_reasoning_effort=xhigh`, and do not mark the worker goal complete.
+`-c model_reasoning_effort=high`, and do not mark the worker goal complete.
 Complete only this lane. Do not end with narration only. Before your final
 response, run a local file-existence and JSON self-check for
 <receiptArtifactPath>. If the lane succeeded, write the canonical success
@@ -656,7 +656,7 @@ receipt, or an accepted Post Engagers no-source blocked/no-op receipt.
 WORKER_PROMPT
 
 # Multi-worker launcher equivalent:
-codex -a never -s danger-full-access -c model_reasoning_effort=xhigh exec --skip-git-repo-check -m <worker-model> -C <repo> -o <worker-final-file> - < <worker-prompt-file>
+codex -a never -s danger-full-access -c model_reasoning_effort=high exec --skip-git-repo-check -m <worker-model> -C <repo> -o <worker-final-file> - < <worker-prompt-file>
 ```
 
 If any placeholder cannot be filled from the current plan, matching