@womp/spark-agent 5.12.0 → 6.0.0

package/README.md

@@ -88,6 +88,8 @@ judges the reconstruction sufficient; insufficient credits or a blocker stop it.
 Reaching the cap completes the pass without a run error. Keep refining
 asks for a new pass budget, then continues in the same conversation with the
 same reference and detail level. The budget travels as structured goal data.
+`wompifyPrompt` writes the reference name prefix into the request message, which is
+also the goal objective, so every pass names the same reference.
 
 Ordinary goals support `{ action: "update_budget", goalId, creditBudget }` on
 the goal endpoint. This edits the total credit cap without resetting usage,
@@ -95,6 +97,14 @@ restarting the run, or adding a model message. Crow reads the current cap before
 worker and evaluator calls; an in-flight call may finish. Raising an exhausted
 cap leaves the goal paused until Resume. Wompify's tier caps cannot be edited.
 
+## System prompt and editor selection
+
+Every host sends `sparkSystemPrompt(skills)`: the shared agent prompt and the skills
+directory, with nothing host-specific, so it stays identical across a conversation.
+Hosts attach the editor selection to the user message it was sent with as a
+`data-selection` part (`{ nodeIds }`). It is not rendered as chat text; the model reads
+it as a short note on that message.
+
 ## Package entry points
 
 - `@womp/spark-agent` — browser-safe model loop, two tools, persistence hooks, and shared contracts
@@ -348,7 +358,8 @@ Prompt caching is enabled for every listed model: Claude Opus 5 and Fable 5 use
 automatic 5-minute caching, and GPT-6 Astra uses implicit caching with a 30-minute TTL.
 The providers manage the cache as message history grows across tool steps; no local
 response cache is used. Cache hits require matching prefixes, sufficient prompt length,
-and an unexpired entry. Cache writes can cost more than uncached input, while subsequent
+and an unexpired entry. Goal state stays out of the system prompt: objectives,
+goal rules and evaluator feedback arrive in appended goal messages. Cache writes can cost more than uncached input, while subsequent
 cache reads are cheaper. The UI displays actual reported reads/writes, not assumed savings.
 See [Claude caching](https://platform.claude.com/docs/en/build-with-claude/prompt-caching)
 and [OpenAI caching](https://developers.openai.com/api/docs/guides/prompt-caching).

package/dist/agent.d.ts

@@ -22,7 +22,6 @@ export type SparkAgentOptions = {
     runId: string;
     messageId: string;
     signal?: AbortSignal;
-    context?: string;
     instructions?: string;
     maxSteps?: number;
     maxOutputTokens?: number;

package/dist/agent.js

@@ -2,7 +2,7 @@ import { sparkErrorDiagnostics } from "./error-diagnostics.js";
 import { WompifyCreditCapReachedError } from "./wompify.js";
 import { createUIMessageStream, stepCountIs, streamText, } from "ai";
 import { createSparkTools } from "./agent-tools.js";
-import { SPARK_AGENT_PROMPT } from "./prompt.js";
+import { sparkSystemPrompt } from "./prompt.js";
 import { calculateStepCost } from "./pricing.js";
 import { contextWindowFor, fitMessagesToContext } from "./context-budget.js";
 function errorMessage(error) {
@@ -124,14 +124,7 @@ export function runSparkAgent(options) {
                     controller,
                     write: (chunk) => writer.write(chunk),
                 });
-                const readSystem = () => [
-                    options.instructions ?? SPARK_AGENT_PROMPT,
-                    options.context,
-                    "Available skills (read before using their APIs):",
-                    ...options.capabilities.skills.map(({ name, version, description }) => `- ${name} (${version}): ${description}`),
-                ]
-                    .filter(Boolean)
-                    .join("\n\n");
+                const readSystem = () => sparkSystemPrompt(options.capabilities.skills, options.instructions);
                 const generation = streamText({
                     model: options.model,
                     system: readSystem(),

package/dist/index.d.ts

@@ -8,5 +8,5 @@ export { recoverSceneOperation, type SceneOperation, type SceneOperationStore }
 export type { JavaScriptExecutor, JavaScriptGlobals, JavaScriptUserWait } from "./executor.js";
 export { DEFAULT_MODEL_ID, getSparkModel, REASONING_EFFORT_LABELS, resolveReasoningEffort, SPARK_MODELS, } from "./models.js";
 export type { ModelProvider, ReasoningEffort, SparkModel } from "./models.js";
-export { SPARK_AGENT_PROMPT } from "./prompt.js";
+export { SPARK_AGENT_PROMPT, sparkSystemPrompt } from "./prompt.js";
 export type { ExecutionResult, ExecutionScreenshot, SparkRuntimeEvent, SparkRuntimeEventSink, SparkContextMessage, SparkImage, SparkRunInput, SparkRuntime, } from "./types.js";

package/dist/index.js

@@ -6,4 +6,4 @@ export * from "./capabilities.js";
 export { createSdkSceneEditor, createSdkSceneHost, } from "./sdk-scene-host.js";
 export { recoverSceneOperation } from "./scene-operations.js";
 export { DEFAULT_MODEL_ID, getSparkModel, REASONING_EFFORT_LABELS, resolveReasoningEffort, SPARK_MODELS, } from "./models.js";
-export { SPARK_AGENT_PROMPT } from "./prompt.js";
+export { SPARK_AGENT_PROMPT, sparkSystemPrompt } from "./prompt.js";

package/dist/model-history.d.ts

@@ -1,5 +1,5 @@
 import { type ModelMessage } from "ai";
 import type { createSparkTools } from "./agent-tools.js";
-import type { SparkUIMessage } from "./ui.js";
+import { type SparkUIMessage } from "./ui.js";
 /** UI artifact previews already represented by a tool result are not model output. */
 export declare function convertSparkMessages(messages: SparkUIMessage[], tools: ReturnType<typeof createSparkTools>): Promise<ModelMessage[]>;

package/dist/model-history.js

@@ -1,4 +1,5 @@
 import { convertToModelMessages } from "ai";
+import { sparkDataPartSchemas } from "./ui.js";
 function record(value) {
     return typeof value === "object" && value !== null && !Array.isArray(value)
         ? value
@@ -30,5 +31,15 @@ export function convertSparkMessages(messages, tools) {
             parts: message.parts.filter((part) => part.type !== "file" || (!previews.has(part.url) && part.providerMetadata?.spark?.inspect !== false)),
         };
     });
-    return convertToModelMessages(history, { tools });
+    return convertToModelMessages(history, {
+        tools,
+        convertDataPart: (part) => {
+            if (part.type !== "data-selection")
+                return undefined;
+            const selection = sparkDataPartSchemas.selection.safeParse(part.data);
+            return selection.success
+                ? { type: "text", text: `[Scene objects selected when this message was sent (node IDs): ${selection.data.nodeIds.join(", ")}]` }
+                : undefined;
+        },
+    });
 }

package/dist/prompt.d.ts

@@ -1 +1,8 @@
-export declare const SPARK_AGENT_PROMPT = "You are Spark, Womp's unified assistant.\nUse read_skill({names:[...]}) to load the required APIs together. Skills provide TypeScript\ndeclarations for documentation; execute_javascript runs JavaScript, with top-level await.\nOnly the listed capabilities are available. Reading a skill does not grant additional permissions.\nUse only the supplied womp APIs and output helpers to access application services and state.\nIf a capability is unavailable, explain what is missing and ask the user to enable it when applicable.\nDo not work around missing capabilities by inspecting page globals, DOM or framework internals,\nor making direct network requests. Native execution is not a security sandbox; it does not expand\nthe supported API or the user's granted capabilities.\nGive each execute_javascript call a concise present-progressive purpose, such as \"Generating a car image\", \"Inspecting the scene\", or \"Importing the model\". Write purpose before code.\nEach execution has fresh local variables. Keep stable object, job, and artifact references.\nUse print for concise, filtered observations; await emitImage or emitFile with a host-issued artifact\nreference to show actual output. emitImage inspects by default; use { inspect: false } to display without adding image bytes to model context.\nCompleted generations are shown automatically to the user; image bytes are intentionally omitted from your context. Acknowledge completion without listing, re-emitting, or inspecting outputs unless the task requires it. Use returned artifact references for follow-up work.\nDo not claim visual verification without inspecting the image. Missing artifact references must be recovered or reported; omitted image bytes alone are not a missing result.\nInspect the scene before editing and verify the committed result.\nPreserve existing content unless the user asks to replace or delete it. Use the latest target revision\nwhen a write requires one. Capabilities own transactions: an entire script is not atomic.\nIf an operation fails after earlier effects, use its receipts to inspect and retry only unresolved work.\nNever claim an uncertain commit rolled back. Never resubmit a job just because waiting timed out.\nComplete related work in this conversation without delegating to another agent. Report limits,\nunsupported actions, cancellation, and incomplete work truthfully. You cannot see what your work\ncosts: model use can be billed, not only generations. Never estimate credits used or call work free;\nreport only credit figures a host message or tool provides. Finish with a concise explanation\nof the result in the user's language; keep implementation details out of that explanation.\n\nCreation intent\n\nResolve the requested outcome from the current message and preceding dialogue, not keyword matches.\nExplicit method choices take precedence. Continue edits in the existing representation unless the user\nasks to change it. Creation defaults do not apply to help, discussion, imports, or account questions.\n\n- Build directly with editable scene shapes for ordinary 3D requests, including \"3D X\" and\n  \"make X in 3D\", and when the user wants individually editable shapes or geometry that blends\n  with existing objects. Organic appearance alone does not require Geometry Nodes.\n\n- Use OpenSCAD for parametric, measured, mechanical, printable, or real-world-fit objects,\n  except when another method is explicit (including primitives with dimensions), or when\n  parametric organic/procedural geometry, animation, or Geometry Nodes is requested:\n  use Geometry Nodes for those, not Workbench Flow. Do not claim print readiness without validation.\n\n- For mesh wompification, read mesh-wompify and scene-editing together and reconstruct only the specified reference using primitives and curves.\n\n- Use mesh generation when the user explicitly requests a mesh, asks to turn an existing or\n  attached image into 3D, or chooses a sculpted result rather than individually editable shapes.\n\n- Use image generation for pictures, logos, concept art, wallpapers, and other clearly visual output.\n\n- For an ambiguous creative request without explicit 3D or printing intent, generate one image\n  preview first. Then offer one short, outcome-based choice: refine the image, turn it into a\n  sculpted 3D piece, or build it from individually editable shapes. Offer adjustable CAD instead\n  of editable shapes when the subject is measured or must fit something real.\n\n- Also preview first when a 3D request without a named method depends on likeness or surface\n  detail that shapes cannot carry (characters, creatures, people, food, sculptures, specific\n  vehicles or branded items). Plain functional objects still build directly.\n\n- Generating a result does not authorize importing, converting, or building it in the scene.\n\n- Use Workbench Flow for image/mesh generation explicitly requested through Flow/nodes or\n  continued edits to that Flow workflow, unless the user asks for an inline result. Flow must be\n  open; explain that prerequisite if closed instead of silently generating inline. Merely opening\n  Flow does not redirect ordinary scene requests or inline generation to it.\n\n- After a preview, offer the choice above. After other completed generation, you may briefly\n  suggest a relevant next step using available capabilities. Describe its outcome, not internal tools. Suggestions are optional,\n  not a mandatory menu, and never authorize actions. Wait for a clear choice and follow existing\n  confirmations. Reuse the existing artifact/reference for the chosen follow-up, including as the\n  image-to-mesh input, instead of regenerating the source. Preserve its defining features when building it.\n\n- Choose construction methods by the user's requested workflow and the\n  available capabilities, not by assuming editable shapes require lower\n  fidelity. Outside the preview defaults above, a sculpted appearance does not by itself\n  require mesh generation.\n  Respect an explicit method choice and pursue the reference's visible shape\n  and detail with that method. Offer alternatives only for a specific\n  demonstrated limitation; ask before switching or simplifying the requested\n  result. No method guarantees exact reconstruction from a single image.\n\n- Ask at most one focused question at a time, only when a sensible default\n  would likely produce the wrong outcome. Do not repeat resolved questions.\n  Interpret replies using the preceding offer; if several options were\n  offered and \u201Cyes\u201D does not identify one, clarify briefly.\n\n- Treat a clear answer to your question as an instruction to proceed.\n  Continue from existing results rather than restarting the workflow.\n\nOffer only workflows available in this host. Follow their authorization\nand confirmation requirements before generation or scene changes. If a requested workflow is unavailable,\nexplain the limitation rather than silently substituting another.";
+import type { SparkSkill } from "./capabilities.js";
+export declare const SPARK_AGENT_PROMPT = "You are Spark, Womp's unified assistant.\nUse read_skill({names:[...]}) to load the required APIs together. Skills provide TypeScript\ndeclarations for documentation; execute_javascript runs JavaScript, with top-level await.\nOnly the listed capabilities are available. Reading a skill does not grant additional permissions.\nUse only the supplied womp APIs and output helpers to access application services and state.\nIf a capability is unavailable, explain what is missing and ask the user to enable it when applicable.\nDo not work around missing capabilities by inspecting page globals, DOM or framework internals,\nor making direct network requests. Native execution is not a security sandbox; it does not expand\nthe supported API or the user's granted capabilities.\nGive each execute_javascript call a concise present-progressive purpose, such as \"Generating a car image\", \"Inspecting the scene\", or \"Importing the model\". Write purpose before code.\nEach execution has fresh local variables. Keep stable object, job, and artifact references.\nUse print for concise, filtered observations; await emitImage or emitFile with a host-issued artifact\nreference to show actual output. emitImage inspects by default; use { inspect: false } to display without adding image bytes to model context.\nCompleted generations are shown automatically to the user; image bytes are intentionally omitted from your context. Acknowledge completion without listing, re-emitting, or inspecting outputs unless the task requires it. Use returned artifact references for follow-up work.\nDo not claim visual verification without inspecting the image. Missing artifact references must be recovered or reported; omitted image bytes alone are not a missing result.\nInspect the scene before editing and verify the committed result.\nPreserve existing content unless the user asks to replace or delete it. Use the latest target revision\nwhen a write requires one. Capabilities own transactions: an entire script is not atomic.\nRecover ordinary tool errors yourself: use confirmed receipts and fresh reads, retry only unresolved work,\npreserve successful changes, and never replay an interrupted script. Do not narrate internal failures\nunless recovery cannot continue. Never claim an uncertain commit rolled back. Never resubmit a job just because waiting timed out.\nComplete related work in this conversation without delegating to another agent. Report limits,\nunsupported actions, cancellation, and incomplete work truthfully. You cannot see what your work\ncosts: model use can be billed, not only generations. Never estimate credits used or call work free;\nreport only credit figures a host message or tool provides. Finish with a concise explanation\nof the result in the user's language; keep implementation details out of that explanation.\n\nCreation intent\n\nResolve the requested outcome from the current message and preceding dialogue, not keyword matches.\nExplicit method choices take precedence. Continue edits in the existing representation unless the user\nasks to change it. Creation defaults do not apply to help, discussion, imports, or account questions.\n\n- Build directly with editable scene shapes for ordinary 3D requests, including \"3D X\" and\n  \"make X in 3D\", and when the user wants individually editable shapes or geometry that blends\n  with existing objects. Organic appearance alone does not require Geometry Nodes.\n\n- Use OpenSCAD for parametric, measured, mechanical, printable, or real-world-fit objects,\n  except when another method is explicit (including primitives with dimensions), or when\n  parametric organic/procedural geometry, animation, or Geometry Nodes is requested:\n  use Geometry Nodes for those, not Workbench Flow. Do not claim print readiness without validation.\n\n- For mesh wompification, read mesh-wompify and scene-editing together and reconstruct only the specified reference using primitives and curves.\n\n- Use mesh generation when the user explicitly requests a mesh, asks to turn an existing or\n  attached image into 3D, or chooses a sculpted result rather than individually editable shapes.\n\n- Use image generation for pictures, logos, concept art, wallpapers, and other clearly visual output.\n\n- For an ambiguous creative request without explicit 3D or printing intent, generate one image\n  preview first. Then offer one short, outcome-based choice: refine the image, turn it into a\n  sculpted 3D piece, or build it from individually editable shapes. Offer adjustable CAD instead\n  of editable shapes when the subject is measured or must fit something real.\n\n- Also preview first when a 3D request without a named method depends on likeness or surface\n  detail that shapes cannot carry (characters, creatures, people, food, sculptures, specific\n  vehicles or branded items). Plain functional objects still build directly.\n\n- Generating a result does not authorize importing, converting, or building it in the scene.\n\n- Use Workbench Flow for image/mesh generation explicitly requested through Flow/nodes or\n  continued edits to that Flow workflow, unless the user asks for an inline result. Flow must be\n  open; explain that prerequisite if closed instead of silently generating inline. Merely opening\n  Flow does not redirect ordinary scene requests or inline generation to it.\n\n- After a preview, offer the choice above. After other completed generation, you may briefly\n  suggest a relevant next step using available capabilities. Describe its outcome, not internal tools. Suggestions are optional,\n  not a mandatory menu, and never authorize actions. Wait for a clear choice and follow existing\n  confirmations. Reuse the existing artifact/reference for the chosen follow-up, including as the\n  image-to-mesh input, instead of regenerating the source. Preserve its defining features when building it.\n\n- Choose construction methods by the user's requested workflow and the\n  available capabilities, not by assuming editable shapes require lower\n  fidelity. Outside the preview defaults above, a sculpted appearance does not by itself\n  require mesh generation.\n  Respect an explicit method choice and pursue the reference's visible shape\n  and detail with that method. Offer alternatives only for a specific\n  demonstrated limitation; ask before switching or simplifying the requested\n  result. No method guarantees exact reconstruction from a single image.\n\n- Ask at most one focused question at a time, only when a sensible default\n  would likely produce the wrong outcome. Do not repeat resolved questions.\n  Interpret replies using the preceding offer; if several options were\n  offered and \u201Cyes\u201D does not identify one, clarify briefly.\n\n- Treat a clear answer to your question as an instruction to proceed.\n  Continue from existing results rather than restarting the workflow.\n\nOffer only workflows available in this host. Follow their authorization\nand confirmation requirements before generation or scene changes. If a requested workflow is unavailable,\nexplain the limitation rather than silently substituting another.";
+/**
+ * The system prompt every host sends: the agent prompt and the skills directory.
+ * It must stay identical across the turns and steps of a conversation, or the
+ * provider's prompt cache misses; per-turn state travels in messages instead.
+ */
+export declare function sparkSystemPrompt(skills: readonly Pick<SparkSkill, "name" | "version" | "description">[], instructions?: string): string;

package/dist/prompt.js

@@ -16,8 +16,9 @@ Do not claim visual verification without inspecting the image. Missing artifact
 Inspect the scene before editing and verify the committed result.
 Preserve existing content unless the user asks to replace or delete it. Use the latest target revision
 when a write requires one. Capabilities own transactions: an entire script is not atomic.
-If an operation fails after earlier effects, use its receipts to inspect and retry only unresolved work.
-Never claim an uncertain commit rolled back. Never resubmit a job just because waiting timed out.
+Recover ordinary tool errors yourself: use confirmed receipts and fresh reads, retry only unresolved work,
+preserve successful changes, and never replay an interrupted script. Do not narrate internal failures
+unless recovery cannot continue. Never claim an uncertain commit rolled back. Never resubmit a job just because waiting timed out.
 Complete related work in this conversation without delegating to another agent. Report limits,
 unsupported actions, cancellation, and incomplete work truthfully. You cannot see what your work
 costs: model use can be billed, not only generations. Never estimate credits used or call work free;
@@ -88,3 +89,15 @@ asks to change it. Creation defaults do not apply to help, discussion, imports,
 Offer only workflows available in this host. Follow their authorization
 and confirmation requirements before generation or scene changes. If a requested workflow is unavailable,
 explain the limitation rather than silently substituting another.`;
+/**
+ * The system prompt every host sends: the agent prompt and the skills directory.
+ * It must stay identical across the turns and steps of a conversation, or the
+ * provider's prompt cache misses; per-turn state travels in messages instead.
+ */
+export function sparkSystemPrompt(skills, instructions = SPARK_AGENT_PROMPT) {
+    return [
+        instructions,
+        "Available skills (read before using their APIs):",
+        ...skills.map(({ name, version, description }) => `- ${name} (${version}): ${description}`),
+    ].join("\n\n");
+}

package/dist/server/executor.d.ts

@@ -9,7 +9,7 @@ export type ResolvedSparkModel = {
 };
 export type SparkRunExecutorOptions = {
     resolveModel(settings: SparkRunSettings): ResolvedSparkModel | Promise<ResolvedSparkModel>;
-    createHost(context: SparkRunExecutionContext): Promise<Pick<SparkAgentOptions, "capabilities" | "executor" | "artifacts" | "persistence" | "context"> & {
+    createHost(context: SparkRunExecutionContext): Promise<Pick<SparkAgentOptions, "capabilities" | "executor" | "artifacts" | "persistence"> & {
         dispose(): void;
     }>;
 };

package/dist/server/executor.js

@@ -23,7 +23,6 @@ export function createSparkRunExecutor(options) {
                 runId: context.runId,
                 messageId: context.assistantMessageId,
                 signal: context.signal,
-                context: [host.context, context.goal ? `Active goal: ${JSON.stringify(context.goal.objective)}\nKeep working toward this objective and verify it with concrete tool results before claiming completion. Do not ask whether to continue. If you need user input or access, explain exactly what is missing. Latest evaluation: ${context.goal.lastReason ?? "Not evaluated yet."}` : undefined].filter(Boolean).join("\n\n"),
             });
             return { stream: run.stream, result: run.result.finally(() => host.dispose()) };
         }

package/dist/server/service.js

@@ -57,7 +57,8 @@ function normalizeUserMessage(message) {
         throw new SparkServiceError(400, "A new chat message must have the user role.");
     }
     for (const part of message.parts) {
-        if (part.type === "text")
+        // The data schemas are checked with the rest of the message (validateUIMessages).
+        if (part.type === "text" || part.type === "data-selection")
             continue;
         if (part.type === "file" &&
             part.mediaType.startsWith("image/") &&
@@ -76,12 +77,20 @@ function normalizeUserMessage(message) {
         },
     };
 }
-/** Budget accounting stays in the host; the worker receives the task and progress. */
+const GOAL_WORK_RULES = "Keep working toward this objective and verify it with concrete tool results before claiming completion. Do not ask whether to continue. If you need user input or access, explain exactly what is missing.";
+/**
+ * Budget accounting stays in the host; the worker receives the task and progress.
+ * Goal state travels in these appended messages, not the system prompt, so each
+ * turn reuses the provider's cached prefix.
+ */
 function goalContinuationText(goal) {
-    return `Continue working toward the goal: ${goal.objective}\nProgress check: ${goal.lastReason}`
+    return `Continue working toward the goal: ${goal.objective}\n${GOAL_WORK_RULES}\nProgress check: ${goal.lastReason}`
         + (wompifyContextSchema.safeParse(goal.settings.wompify).success
             ? "\nKeep refining the existing reconstruction at the same detail level. Compare it with the reference and improve the remaining shape and color discrepancies." : "");
 }
+function goalStartText(goal, action) {
+    return `${action === "set" ? "Goal" : "Resume the goal"}: ${goal.objective}\n${GOAL_WORK_RULES}`;
+}
 export class SparkAgentService {
     store;
     executeRun;
@@ -222,7 +231,7 @@ export class SparkAgentService {
             } : { ...current, settings: runSettings, status: "active", updatedAt: now(),
                 idleTurns: 0, };
             const inputMessage = normalizeUserMessage(message ?? {
-                id: crypto.randomUUID(), role: "user", parts: [{ type: "text", text: command.action === "set" ? goal.objective : `Resume the goal: ${goal.objective}` }],
+                id: crypto.randomUUID(), role: "user", parts: [{ type: "text", text: goalStartText(goal, command.action) }],
             });
             await validateUIMessages({ messages: [inputMessage], metadataSchema: sparkMessageMetadataSchema, dataSchemas: sparkDataPartSchemas });
             await this.store.saveConversationGoal(conversationId, goal);

package/dist/ui.d.ts

@@ -89,6 +89,11 @@ export type SparkDataParts = {
         toolCallId: string;
         receipt: ExecutionReceipt;
     };
+    selection: SparkSelectionData;
+};
+/** Editor node IDs selected when a user message was sent; never rendered as chat text. */
+export type SparkSelectionData = {
+    nodeIds: string[];
 };
 export type ExecuteJavaScriptInput = {
     purpose: string;
@@ -321,6 +326,13 @@ export declare const sparkDataPartSchemas: {
         }, z.core.$strip>>;
         usage: z.ZodOptional<z.ZodUnknown>;
     }, z.core.$strip>;
+    /**
+     * The editor selection when a user message was sent. Hosts attach it to that
+     * message and do not render it; the model reads it as text (model-history.ts).
+     */
+    readonly selection: z.ZodObject<{
+        nodeIds: z.ZodArray<z.ZodString>;
+    }, z.core.$strip>;
 };
-export { parseWompifyCommand, WOMPIFY_PRESETS, wompifyPrompt, wompifyContext, wompifyContextSchema, type WompifyRequest, type WompifyContext } from "./wompify.js";
+export { parseWompifyCommand, WOMPIFY_PRESETS, wompifyPrompt, wompifyContextSchema, type WompifyRequest, type WompifyContext } from "./wompify.js";
 export { parseSparkGoalCommand, DEFAULT_GOAL_CREDITS } from "./goals.js";

package/dist/ui.js

@@ -79,6 +79,12 @@ export const sparkDataPartSchemas = {
         cost: sparkStepCostSchema.optional(),
         usage: z.unknown().optional(),
     }),
+    /**
+     * The editor selection when a user message was sent. Hosts attach it to that
+     * message and do not render it; the model reads it as text (model-history.ts).
+     */
+    // Editor ids are the engine's decimal integers; 8192 covers a select-all at the engine's budgets.
+    selection: z.object({ nodeIds: z.array(z.string().min(1).max(64)).min(1).max(8192) }),
 };
-export { parseWompifyCommand, WOMPIFY_PRESETS, wompifyPrompt, wompifyContext, wompifyContextSchema } from "./wompify.js";
+export { parseWompifyCommand, WOMPIFY_PRESETS, wompifyPrompt, wompifyContextSchema } from "./wompify.js";
 export { parseSparkGoalCommand, DEFAULT_GOAL_CREDITS } from "./goals.js";

package/dist/wompify.d.ts

@@ -29,8 +29,11 @@ export declare const wompifyContextSchema: z.ZodObject<{
     }>;
 }, z.core.$strip>;
 export type WompifyContext = z.infer<typeof wompifyContextSchema>;
-export declare function wompifyContext(context?: WompifyContext): string | undefined;
-export declare function wompifyPrompt(preset: WompifyRequest["preset"], referenceName: string, note?: string): string;
+/** The Wompify request message, which is also the goal objective every continuation repeats. */
+export declare function wompifyPrompt(request: WompifyContext & {
+    referenceName: string;
+    note?: string;
+}): string;
 export declare function parseWompifyCommand(text: string): {
     preset: WompifyRequest["preset"];
     note: string;

package/dist/wompify.js

@@ -15,13 +15,12 @@ export const wompifyContextSchema = z.object({
     referenceNamePrefix: z.string().trim().min(1).max(200),
     preset: z.enum(["simple", "high", "ultra"]),
 });
-export function wompifyContext(context) {
-    if (!context)
-        return undefined;
-    return `Use the mesh-wompify skill for reference name prefix ${JSON.stringify(context.referenceNamePrefix)} at tier ${WOMPIFY_PRESETS[context.preset].label}. Stop if that skill is unavailable.`;
-}
-export function wompifyPrompt(preset, referenceName, note = "") {
-    return `Wompify ${JSON.stringify(referenceName)} at tier ${WOMPIFY_PRESETS[preset].label}.${note.trim() ? `\n${note.trim()}` : ""}`;
+/** The Wompify request message, which is also the goal objective every continuation repeats. */
+export function wompifyPrompt(request) {
+    const note = request.note?.trim();
+    return `Wompify ${JSON.stringify(request.referenceName)} at tier ${WOMPIFY_PRESETS[request.preset].label}.`
+        + `\nUse the mesh-wompify skill for reference name prefix ${JSON.stringify(request.referenceNamePrefix)}. Stop if that skill is unavailable.`
+        + (note ? `\n${note}` : "");
 }
 export function parseWompifyCommand(text) {
     const match = /^\/wompify (simple|high|ultra)(?:\n([\s\S]*))?$/u.exec(text.trim());

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@womp/spark-agent",
-  "version": "5.12.0",
+  "version": "6.0.0",
   "description": "Portable skills-based AI agent with local and durable chat transports for Womp",
   "type": "module",
   "main": "./dist/index.js",