@slatesvideo/shared 0.7.0 → 0.7.2

package/dist/operations/surface.d.ts

@@ -61,7 +61,8 @@ export declare function toolDefinition(op: SurfaceOp): ToolDefinition;
  * Render a tool surface.
  *
  * `desktop` sends `core` plus whatever groups have been loaded this run; `mcp`
- * renders all definitions; the MCP server filters its connection listing from that set.
+ * renders all definitions, and the MCP server lists all of them unless started with
+ * `--tools=compact`.
  */
 export declare function toolDefinitions(ops: readonly SurfaceOp[], opts: {
     surface: 'desktop' | 'mcp';

package/dist/operations/surface.js

@@ -11,9 +11,12 @@
 //
 //   2. TIERS. 90 ops is 112 KB of descriptions and JSON schemas on EVERY
 //      desktop Studio Agent turn. `core` is what a session needs to work;
-//      `extended` is selected through `slates_load_tools`. Both surfaces replace
-//      the optional selection on a named/group load. MCP keeps every direct
-//      operation callable for compatibility and notifies when its listing changes.
+//      `extended` is selected through `slates_load_tools`. Tiers are a DESKTOP
+//      mechanism: we build every turn there, so a load reaches the model. The
+//      MCP server lists every op and leaves hiding definitions to the host
+//      (tiering there left Claude and Codex users unable to generate in 0.6.0;
+//      see the TOOLS comment in packages/mcp/src/server.ts). `--tools=compact`
+//      is the opt-in exception.
 //
 //   3. ONE SCHEMA RENDERER. The desktop rendered `$refStrategy: 'none'` and
 //      the MCP server rendered `target: 'openApi3'`, so "the two surfaces
@@ -142,6 +145,9 @@ export const OPERATION_GROUPS = {
         'slates_relocate_project',
         'slates_undo_relocate_project',
         'slates_reveal_file',
+        'slates_reorder_folders',
+        'slates_reorder_pins',
+        'slates_link_asset_source',
     ],
     // The cut and the export. A generation session never touches these.
     script: ['slates_get_script_document', 'slates_update_script_document', 'slates_get_script_sections', 'slates_update_script_section', 'slates_get_script_suggestions', 'slates_update_script_suggestions', 'slates_get_script_uses', 'slates_preview_script_variation', 'slates_create_script_variation', 'slates_get_shot_inputs', 'slates_reuse_shot_take'],
@@ -179,6 +185,9 @@ export const OPERATION_GROUPS = {
         'slates_duplicate_shot',
         'slates_split_shot',
         'slates_merge_shots',
+        'slates_get_usage',
+        'slates_get_app_settings',
+        'slates_set_app_settings',
     ],
     // A third transport nobody without Blender installed can reach.
     blender: [
@@ -238,7 +247,8 @@ export function toolDefinition(op) {
  * Render a tool surface.
  *
  * `desktop` sends `core` plus whatever groups have been loaded this run; `mcp`
- * renders all definitions; the MCP server filters its connection listing from that set.
+ * renders all definitions, and the MCP server lists all of them unless started with
+ * `--tools=compact`.
  */
 export function toolDefinitions(ops, opts) {
     const loaded = new Set(opts.groups ?? []);

package/dist/prompts/agent-doctrine.js

@@ -76,13 +76,34 @@ export function buildSkillIndex() {
     return entries;
 }
 // ── Preamble ───────────────────────────────────────────────────────
-const PREAMBLE = fork(`You are the Slates Studio Agent — a production assistant living inside Slates, the AI video creation studio. You plan and execute video/image production runs by chaining the Slates tools: script → characters → images → videos → quality-check → regenerate, ending with assets in the user's project (and on the timeline when asked).`, `You are connected to Slates, the AI video creation studio, through its MCP tool surface. These tools plan and execute real video/image production runs that spend the user's Slates credits: script → characters → images → videos → quality-check → regenerate, ending with assets in the user's project. Follow the working method and hard rules below on every Slates task — this is the same doctrine the in-app Studio Agent runs on.`);
+// FORKED, and the MCP side is a SUMMARY THAT MUST FIT IN THE CUT. Claude Code
+// keeps only the first 2,048 characters of a server's instructions (docs,
+// 2026-09-30), and 0.6.0's cut fell mid-sentence in step 4, so every hard rule
+// after it never reached the model. What an agent needs to act safely — how to
+// find a tool when the host shows names only, the spend gate, real numbers, the
+// current project — sits here; the sections below expand it for clients that
+// read everything. mcp-instructions-smoke asserts these lines land inside the
+// cut with the UPDATE AVAILABLE notice in front of them.
+const PREAMBLE = fork(`You are the Slates Studio Agent — a production assistant living inside Slates, the AI video creation studio. You plan and execute video/image production runs by chaining the Slates tools: script → characters → images → videos → quality-check → regenerate, ending with assets in the user's project (and on the timeline when asked).`, `You are connected to Slates, the AI video creation studio. These tools run real image, video and audio generations that spend the user's Slates credits, ending with assets in the user's project.
+
+## Essentials (the sections below expand on these)
+
+- FINDING TOOLS: every Slates capability is its own slates_* tool. If your client shows tool names only, search your tools for the task (for example "slates generate video") and load that tool before calling it. If a tool is missing from your list entirely, slates_load_tools finds and loads it.
+- SPENDING: before ANY generation, price every step with slates_estimate_generation_cost, show the user the itemized total in ONE message, and wait for their OK. Pass confirm: true only to relay an explicit user OK for that exact spend.
+- REAL NUMBERS ONLY: every cost, balance or count you state is copied from a tool result in this session. Never describe how a generation looks unless you fetched it this session.
+- PROJECT: call slates_get_workspace_state once, work in the user's current project, and never create a project unless asked.
+- CRAFT: before prompting a model, read its guide with slates_get_prompting_guide (pass the model id). For how or where in the app, use topic "app-manual".
+- Speak in the app's words and name assets by code and label (IMG-A12), never by tool name or UUID.`);
 // ── The working method ─────────────────────────────────────────────
 export const WORKING_METHOD = [
-    both(`For HOW/WHERE questions, load slates_get_prompting_guide with topic "app-manual" and relevant query keywords. Teach the documented buttons and tabs, preserving model-specific conditions; do not invent UI paths or mutate the project when the user only asks for instructions. Slates is a sandbox of optional tools, not a required pipeline.`),
+    both(`For HOW/WHERE questions, load slates_get_prompting_guide with topic "app-manual" and relevant query keywords. Teach the documented buttons and tabs, preserving model-specific conditions; do not invent UI paths or mutate the project when the user only asks for instructions. When the control is on screen, offer to point at it (slates_highlight_control); show a picture of a screen (slates_get_manual_picture) only when the user cannot find something or asks what it looks like. Slates is a sandbox of optional tools, not a required pipeline.`),
     both(`1. UNDERSTAND the outcome the user wants. If intent is clear, act with sane defaults — don't interrogate. If genuinely ambiguous, batch every question into ONE message.`),
     both(`2. ORIENT: call slates_get_workspace_state once at the start of a workflow. Work in the user's CURRENT project — this chat lives inside it. NEVER create a new project unless explicitly asked; if there's no current project, ask which to use.`),
-    both(`3. LOAD KNOWLEDGE ON DEMAND: slates_get_prompting_guide returns a short card by default; query a section or technique when needed. Use slates_load_tools with query to find a capability, then names to load its exact schema. A load replaces the previous optional selection. Before quoting a model, load its tool schema or routing guide. Use workspace generationDefaults when the user has no preference. Read the model card delivered by the estimate; fetch a section or full guide for an unfamiliar mode or missing detail. Reuse guidance already in context; retrieve it again when omitted or stale.`),
+    // FORKED: the desktop sends core tools plus what `slates_load_tools` loaded,
+    // so its agent must load before calling. The MCP server lists every tool and
+    // the host decides what to show (Essentials, FINDING TOOLS), so telling an MCP
+    // client to load first costs it a turn for a tool it already has.
+    fork(`3. LOAD KNOWLEDGE ON DEMAND: slates_get_prompting_guide returns a short card by default; query a section or technique when needed. Use slates_load_tools with query to find a capability, then names to load its exact schema. A load replaces the previous optional selection. Before quoting a model, load its tool schema or routing guide. Use workspace generationDefaults when the user has no preference. Read the model card delivered by the estimate; fetch a section or full guide for an unfamiliar mode or missing detail. Reuse guidance already in context; retrieve it again when omitted or stale.`, `3. LOAD KNOWLEDGE ON DEMAND: slates_get_prompting_guide returns a short card by default; query a section or technique when needed. Before quoting a model, read its tool schema or routing guide. Use workspace generationDefaults when the user has no preference. Read the model card delivered by the estimate; fetch a section or full guide for an unfamiliar mode or missing detail. Reuse guidance already in context; retrieve it again when omitted or stale.`),
     // FORKED: `present_plan` is a loop-level DESKTOP tool, deliberately not in
     // ALL_OPERATIONS, so MCP never sees it and has no plan gate at all. Its
     // substitute is the per-op `requires_confirm` threshold plus the host

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@slatesvideo/shared",
-  "version": "0.7.0",
+  "version": "0.7.2",
   "description": "Shared operations layer for the Slates MCP server and CLI: auth, cloud/desktop clients, and the single tool surface both consume. Most users want @slatesvideo/mcp-server or @slatesvideo/cli instead.",
   "license": "MIT",
   "type": "module",
@@ -40,7 +40,7 @@
     "dist",
     "!dist/**/*.map",
     "skills",
-    "exports/slates-prompt-builder/generated",
+    "exports/slates-prompt-builder/generated",
     "exports/slates-chatgpt-images/generated",
     "README.md"
   ],
@@ -48,7 +48,7 @@
     "sync-partials": "node scripts/sync-partials.mjs",
     "build-prompt-builder": "node scripts/build-prompt-builder.mjs",
     "check-prompt-builder": "node scripts/build-prompt-builder.mjs --check",
-    "build-chatgpt-skill": "node scripts/build-chatgpt-skill.mjs",
+    "build-chatgpt-skill": "node scripts/build-chatgpt-skill.mjs",
     "build": "node scripts/build-chatgpt-skill.mjs --check && node scripts/sync-partials.mjs --check && node scripts/build-prompt-builder.mjs --check && node scripts/embed-skills.mjs && tsc && node scripts/render-capability-partials.mjs --check && node scripts/update-check-check.mjs",
     "typecheck": "node scripts/sync-partials.mjs --check && node scripts/build-prompt-builder.mjs --check && node scripts/embed-skills.mjs && tsc --noEmit",
     "prepublishOnly": "npm run build && node ../../scripts/cinematic-catalogue-check.mjs && node ../../scripts/prompt-control-check.mjs",