@superblocksteam/vite-plugin-file-sync 2.0.37-next.3 → 2.0.37-next.31

package/dist/ai-service/state-machine/handlers/simple-prompt-builder.js

@@ -11,10 +11,7 @@ For complex multi-step tasks, use the build_manageChecklist tool to:
 
 Start complex tasks by creating an initial checklist, then update it throughout your work.
 
-Before you start building applications, you must first understand user's intent, goals, and the context of the application. Use tools like:
-- build_listAvailableComponents
-- study_currentAppState
-to start.
+Before you start building applications, you must first understand user's intent, goals, and the current context of the application.
 
 Do not be overly verbose, explain just enough to get your points across to the user.
 
@@ -65,10 +62,16 @@ This creates a clear boundary:
 ## App.tsx Layout Structure
 
 **For Application-Wide Layout Components:**
-Place navigation, sidebars, headers, footers, and other persistent layout components in \`App.tsx\`, not in individual pages.
+For single-page applications: 
+- Put all content in Page1/index.tsx
+- Keep App.tsx minimal with just <Outlet />.
+
+For multi-page applications: 
+- Put shared navigation/layout in App.tsx, including navigation, sidebars, headers, footers, etc. Always include the Outlet component.
+- Put page-specific content in respective page files.
 
 \`\`\`tsx
-// ✅ CORRECT - Layout components in App.tsx
+// ✅ CORRECT - Layout components in App.tsx for a multi-page application
 <BaseApp>
   <Stack direction="horizontal" height={Dim.fill()}>
     {/* Sidebar - persistent across all pages */}
@@ -93,7 +96,7 @@ Place navigation, sidebars, headers, footers, and other persistent layout compon
 </BaseApp>
 \`\`\`
 
-**Individual pages should focus on content, not layout structure:**
+**Individual pages in multi-page applications should focus on content, not layout structure:**
 \`\`\`tsx
 // ✅ CORRECT - Page focuses on content only
 <Page name="Dashboard" height={Dim.fill()} width={Dim.fill()}>
@@ -848,6 +851,109 @@ To have the API run when the page loads, use the onLoad property on Page.
 \`\`\`
 
 </using_apis>
+
+<api_state_updates>
+## 🚨 CRITICAL: Frontend/Backend Separation for State Updates
+
+**APIs are backend workflows that can only READ state. State mutations MUST happen on the frontend through EventFlow.**
+
+### The Rule:
+- **Backend (API files)**: Read state, process data, return results
+- **Frontend (scope.ts/pages)**: Update state based on API results using onSuccess/onError handlers
+- **Other frontend state updates**: Can happen anywhere via EventFlow (button clicks, input changes, etc.)
+
+### ❌ WRONG: APIs CANNOT set state variables
+APIs cannot modify StateVars or component properties. They only return data.
+
+### ✅ CORRECT: For API-triggered state updates, use onSuccess/onError handlers in scope
+When registering APIs in the scope file, use onSuccess/onError to handle state updates based on API results:
+
+\`\`\`tsx
+// In scope.ts - registering the API with state update handlers
+export const Page1Scope = registerScope("Page1", {
+  // ... other entities ...
+
+  createUserApi: {
+    onSuccess: EventFlow.runJS(({ createUserApi }) => {
+      // Update state based on API response
+      userNameVar.value = createUserApi.response.name;
+      userListVar.value = [...userListVar.value, createUserApi.response];
+      isLoadingVar.value = false;
+      CreateUserDialog.isOpen = false;
+
+      toast.success("User created successfully!");
+    }),
+    onError: EventFlow.runJS(() => {
+      isLoadingVar.value = false;
+      toast.error("Failed to create user");
+    })
+  },
+
+  fetchDataApi: {
+    onSuccess: EventFlow.setStateVar(dataVar, {
+      value: computed(() => fetchDataApi.response)
+    })
+  }
+});
+\`\`\`
+
+### Common Patterns:
+
+**Loading states:**
+\`\`\`tsx
+// In scope.ts
+searchApi: {
+  onSuccess: EventFlow.runJS(({ searchApi }) => {
+    searchResultsVar.value = searchApi.response;
+    isSearchingVar.value = false;
+  }),
+  onError: EventFlow.runJS(() => {
+    isSearchingVar.value = false;
+    searchResultsVar.value = [];
+  })
+}
+
+// In page - set loading state before API call
+<Button onClick={EventFlow
+  .setStateVar(isSearchingVar, { value: true })
+  .runApis([searchApi])
+} />
+\`\`\`
+
+**Form submissions:**
+\`\`\`tsx
+// In scope.ts
+submitFormApi: {
+  onSuccess: EventFlow
+    .runJS(({ submitFormApi }) => {
+      submittedDataVar.value = submitFormApi.response;
+      toast.success("Form submitted!");
+    })
+    .resetComponent(FormInput1)
+    .resetComponent(FormInput2)
+    .setComponentProperty(FormDialog, { property: "isOpen", value: false })
+}
+\`\`\`
+
+**Data refresh after mutation:**
+\`\`\`tsx
+// In scope.ts
+deleteItemApi: {
+  onSuccess: EventFlow
+    .runJS(() => {
+      toast.success("Item deleted");
+    })
+    .runApis([fetchItemsApi])  // Refresh the list
+}
+\`\`\`
+
+### Why this separation matters for APIs:
+- Keeps data flow unidirectional and predictable
+- APIs remain pure data processors
+- API-triggered state updates are centralized in onSuccess/onError handlers
+- Makes debugging and testing easier
+- Aligns with the Superblocks visual editor model
+</api_state_updates>
 </apis>
 
 <superblocks_state>
@@ -940,25 +1046,25 @@ Bindings give you named references to component instances so you can **read** (a
 <writing_to_component_properties>
 ## Writing to Component Properties — Policy
 
-Decide with this test: **“Can the end-user directly modify this value directly during the app lifecycle?”**  
+Decide with this test: **“Can the end-user directly modify this value directly during the app lifecycle?”**
 We distinguish **Input-like**, **Data/derived**, and **Control** props.
 
-- **INPUT-LIKE** (user-edited values)  
-  Examples: \`Input.value\`, \`Select.selected\`, \`Switch.checked\`, \`DatePicker.value\`  
-  - Marked **\`readAndWrite\`** in the component definition.  
-  - JSX provides the **default** (often via a \`default*\` prop that seeds the live \`value\`).  
-  - **Live source of truth** is the user's edits.  
+- **INPUT-LIKE** (user-edited values)
+  Examples: \`Input.value\`, \`Select.selected\`, \`Switch.checked\`, \`DatePicker.value\`
+  - Marked **\`readAndWrite\`** in the component definition.
+  - JSX provides the **default** (often via a \`default*\` prop that seeds the live \`value\`).
+  - **Live source of truth** is the user's edits.
   - **Imperative writes are rare & intentional** (reset/clear, apply suggestion). Prefer declarative props otherwise.
 
-- **DATA / DERIVED / DISPLAY** (driven by app data, APIs, or other props)  
-  Examples: \`Typography.value\`, \`Table.rows\`, \`Chart.series\`, \`Avatar.src\`  
-  - Treat as **declarative** and **reactive** only.  
+- **DATA / DERIVED / DISPLAY** (driven by app data, APIs, or other props)
+  Examples: \`Typography.value\`, \`Table.rows\`, \`Chart.series\`, \`Avatar.src\`
+  - Treat as **declarative** and **reactive** only.
   - **Never** set imperatively; pass via JSX with \`computed(...)\` so updates flow automatically.
 
-- **CONTROL** (visibility/toggle state for dialogs, sheets, modals, drawers, etc.)  
-  Examples: \`Dialog1.isOpen\`, \`Sheet1.isOpen\`  
-  - Not user-typed and not derived data; callers **control** them.  
-  - **Imperative writes are the standard pattern** for opening/closing:  
+- **CONTROL** (visibility/toggle state for dialogs, sheets, modals, drawers, etc.)
+  Examples: \`Dialog1.isOpen\`, \`Sheet1.isOpen\`
+  - Not user-typed and not derived data; callers **control** them.
+  - **Imperative writes are the standard pattern** for opening/closing:
     \`\`\`tsx
     <Button
       onClick={EventFlow.setComponentProperty(Dialog1, {
@@ -978,9 +1084,9 @@ We distinguish **Input-like**, **Data/derived**, and **Control** props.
 <setting_component_properties>
 ## Setting Component Properties
 
-**Preferred:** Pass dynamic values in JSX with \`computed(...)\`.  
-**Exceptions:**  
-- Imperative writes for **input-like** props when overwriting user input is explicitly desired.  
+**Preferred:** Pass dynamic values in JSX with \`computed(...)\`.
+**Exceptions:**
+- Imperative writes for **input-like** props when overwriting user input is explicitly desired.
 - Imperative writes for **control** props (open/close) to drive UI affordances.
 
 ### ✅ Declarative data passed as props in JSX (preferred)
@@ -1534,8 +1640,8 @@ EventFlow.runJS(() => {
 - Always supply children to components as JSX elements, not by attempting to set a children property.
 - Use layout and alignment related props on Stacks/Cards to position children. Make a visually pleasing layout using tailwind classes.
 - Use icon names from the Lucide React library.
-- Use custom components to create UI elements not provided by Superblocks
 - Use custom components to encapsulate common UI patterns like lists, menus, etc.
+- Prefer using existing components in the application, as the @superblocksteam/library package does not contain components outside of \`App\` and \`Page\`
 </component_usage_guidance>
 
 <application_file_structure>
@@ -2029,18 +2135,18 @@ export default registerComponent("UserList", propertiesDefinition, (props) => {
 
 <design_system_guidance>
 
-- This project uses **Tailwind CSS v4**  
-- All design tokens and configuration are defined directly in \`index.css\`  
-- Every app comes out of the box with a professional, subtle black-and-white theme  
-- All colors must be specified in **OKLCH** format  
+- This project uses **Tailwind CSS v4**
+- All design tokens and configuration are defined directly in \`index.css\`
+- Every app comes out of the box with a professional, subtle black-and-white theme
+- All colors must be specified in **OKLCH** format
 
 <branding_decision_gate>
-Before writing any code, determine whether the user request requires a branding/theme change 
+Before writing any code, determine whether the user request requires a branding/theme change
 
 <brand_change_definition>
 A request requires branding/theme changes only if it explicitly asks to change visual identity
 
-Examples: 
+Examples:
 - Change primary/secondary/neutral colors
 - Switch fonts or type scale
 - Adjust radii or shadows for a brand look
@@ -2054,16 +2160,16 @@ Feature requests like lists, filters, pagination, CRUD, sheets do not require br
 </branding_decision_gate>
 
 <semantic_tokens_rule>
-**USE SEMANTIC TOKENS FOR ALL STYLING** — colors, gradients, fonts, shadows, spacing, etc.  DO NOT use direct values or raw Tailwind utilities like \`text-white\`, \`bg-black\`, \`shadow-lg\`, etc. Everything must be themed via the design system tokens defined in \`index.css\`  
+**USE SEMANTIC TOKENS FOR ALL STYLING** — colors, gradients, fonts, shadows, spacing, etc.  DO NOT use direct values or raw Tailwind utilities like \`text-white\`, \`bg-black\`, \`shadow-lg\`, etc. Everything must be themed via the design system tokens defined in \`index.css\`
 </semantic_tokens_rule>
 
 <design_system_usage>
-When building components or pages:  
-- Always style with semantic tokens (e.g. \`bg-background\`, \`text-foreground\`, \`border-border\`)  
-- Never use Tailwind's default color or shadow utilities directly  
-- Typography must use semantic tokens for font family and sizes  
-- Gradients, spacing, and effects should also come from tokens or utilities built on tokens  
-- All components should be responsive by default  
+When building components or pages:
+- Always style with semantic tokens (e.g. \`bg-background\`, \`text-foreground\`, \`border-border\`)
+- Never use Tailwind's default color or shadow utilities directly
+- Typography must use semantic tokens for font family and sizes
+- Gradients, spacing, and effects should also come from tokens or utilities built on tokens
+- All components should be responsive by default
 
 ✅ Example (correct):
 \`\`\`tsx
@@ -2077,49 +2183,49 @@ When building components or pages:
 </design_system_usage>
 
 <design_token_modification>
-Modify the design system only when extending functionality All modifications must happen in \`index.css\`  
-- Add new tokens with **semantic names** (\`--color-warning\`, \`--shadow-elevated\`)  
-- Add reusable utilities with \`@utility\`  
-- Create **variants** for Shadcn components instead of writing one-off styles  
+Modify the design system only when extending functionality All modifications must happen in \`index.css\`
+- Add new tokens with **semantic names** (\`--color-warning\`, \`--shadow-elevated\`)
+- Add reusable utilities with \`@utility\`
+- Create **variants** for Shadcn components instead of writing one-off styles
 
-Do NOT remove or rename existing tokens — edit values or add new ones as needed  
+Do NOT remove or rename existing tokens — edit values or add new ones as needed
 
 <color_palette_modification>
-Only modify the color palette if explicitly requested or when replicating the look and feel of an existing brand or product (e.g. Yelp, Instacart)  
-- Choose one **primary brand color**  
-- Choose 2-3 neutrals (white, gray, black variants) and 1-2 accents  
-- Consider both dark and light modes  
-- Never exceed 5 colors without explicit approval  
+Only modify the color palette if explicitly requested or when replicating the look and feel of an existing brand or product (e.g. Yelp, Instacart)
+- Choose one **primary brand color**
+- Choose 2-3 neutrals (white, gray, black variants) and 1-2 accents
+- Consider both dark and light modes
+- Never exceed 5 colors without explicit approval
 </color_palette_modification>
 
 <gradients>
-- Avoid gradients unless explicitly requested  
-- If gradients are necessary:  
-  - Use them only as subtle accents, never for primary fills  
-  - Use analogous hues (blue→teal, purple→pink, orange→red)  
-  - Never use clashing opposites (red→cyan, orange→blue)  
-  - Limit to 2-3 color stops  
+- Avoid gradients unless explicitly requested
+- If gradients are necessary:
+  - Use them only as subtle accents, never for primary fills
+  - Use analogous hues (blue→teal, purple→pink, orange→red)
+  - Never use clashing opposites (red→cyan, orange→blue)
+  - Limit to 2-3 color stops
 </gradients>
 
 </design_token_modification>
 
 <typography_guidance>
-**Font Families**  
-- Prefer a single font family for both headings and body  
-- At most 2 families total (one heading, one body)  
-- Never use decorative fonts for body text  
-- Do not use fonts smaller than 14px  
-
-**Font Sizes & Hierarchy**  
-- Use as few font sizes as necessary to express hierarchy  
-- Default: one size for body, one for section headings, one for main heading  
-- Add more levels only when the information hierarchy demands it  
-- Avoid bloated scales (h1-h6 + multiple body variants) unless cloning a full design system  
-- Use weight, spacing, and color with size to establish hierarchy  
+**Font Families**
+- Prefer a single font family for both headings and body
+- At most 2 families total (one heading, one body)
+- Never use decorative fonts for body text
+- Do not use fonts smaller than 14px
+
+**Font Sizes & Hierarchy**
+- Use as few font sizes as necessary to express hierarchy
+- Default: one size for body, one for section headings, one for main heading
+- Add more levels only when the information hierarchy demands it
+- Avoid bloated scales (h1-h6 + multiple body variants) unless cloning a full design system
+- Use weight, spacing, and color with size to establish hierarchy
 </typography_guidance>
 
 <index_css_guidance>
-All design tokens are defined in \`index.css\` using CSS custom properties  
+All design tokens are defined in \`index.css\` using CSS custom properties
 
 Example:
 
@@ -2157,12 +2263,12 @@ Example:
 <component_implementation_guidance>
 When working with Shadcn components:
 
-1. Start with the base component in \`components/ui/\`  
-2. Add reusable styles as **variants** in the component file  
-3. Use \`cn()\` for conditional classes  
-4. Integrate with Superblocks via \`index.tsx\`  
-5. Define props in \`props.ts\`  
-6. Configure editor behavior in \`editor.ts\`  
+1. Start with the base component in \`components/ui/\`
+2. Add reusable styles as **variants** in the component file
+3. Use \`cn()\` for conditional classes
+4. Integrate with Superblocks via \`index.tsx\`
+5. Define props in \`props.ts\`
+6. Configure editor behavior in \`editor.ts\`
 
 **Always use design tokens:**
 
@@ -2200,9 +2306,9 @@ const buttonVariants = cva("...", {
 </component_variants>
 
 <outline_caveat>
-Shadcn outline variants are not transparent by default  
-If you pair an outline button with light text, it may disappear in certain themes  
-Always define outline button variants using semantic tokens for background and foreground so they remain legible in both light and dark modes  
+Shadcn outline variants are not transparent by default
+If you pair an outline button with light text, it may disappear in certain themes
+Always define outline button variants using semantic tokens for background and foreground so they remain legible in both light and dark modes
 </outline_caveat>
 
 <avoiding_errors>
@@ -2227,14 +2333,14 @@ created with \`@utility\` in \`index.css\`
 </avoiding_errors>
 
 <expected_outcomes>
-Expected outcomes when following this guidance:  
-- All components use semantic tokens, never Tailwind's built-in color or shadow utilities  
-- The entire theme is controlled centrally in \`index.css\`  
-- All colors are defined in OKLCH format  
-- Components are responsive and customizable via variants  
-- Typography is minimal, purposeful, and consistent  
-- Adding or changing tokens happens only in \`index.css\`  
-- Result: consistent, themeable, professional apps that can be branded easily  
+Expected outcomes when following this guidance:
+- All components use semantic tokens, never Tailwind's built-in color or shadow utilities
+- The entire theme is controlled centrally in \`index.css\`
+- All colors are defined in OKLCH format
+- Components are responsive and customizable via variants
+- Typography is minimal, purposeful, and consistent
+- Adding or changing tokens happens only in \`index.css\`
+- Result: consistent, themeable, professional apps that can be branded easily
 </expected_outcomes>
 
 </design_system_guidance>

package/dist/ai-service/state-machine/handlers/simple-prompt-builder.js.map

@@ -1 +1 @@
-{"version":3,"file":"simple-prompt-builder.js","sourceRoot":"","sources":["../../../../src/ai-service/state-machine/handlers/simple-prompt-builder.ts"],"names":[],"mappings":"AAAA,MAAM,CAAC,MAAM,iBAAiB,GAC5B,GAAG,EAAE,CAAC,MAAM,CAAC;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CA2tEd,CAAC"}
+{"version":3,"file":"simple-prompt-builder.js","sourceRoot":"","sources":["../../../../src/ai-service/state-machine/handlers/simple-prompt-builder.ts"],"names":[],"mappings":"AAAA,MAAM,CAAC,MAAM,iBAAiB,GAC5B,GAAG,EAAE,CAAC,MAAM,CAAC;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAq0Ed,CAAC"}

package/dist/ai-service/state-machine/helpers/cache-breakpoint.d.ts

@@ -0,0 +1,29 @@
+import type { Clark } from "../clark-fsm.js";
+import type { PrepareStepFunction } from "ai";
+export declare const cacheBreakpointHelper: (clark: Clark, { agentName, threshold, }: {
+    agentName: string;
+    threshold?: number;
+}) => {
+    nextCacheBreakpoint: () => {
+        readonly bedrock: {
+            readonly cachePoint: {
+                readonly type: "default";
+            };
+        };
+        readonly anthropic: {
+            readonly cacheControl: {
+                readonly type: "ephemeral";
+            };
+        };
+    } | undefined;
+    breakpointAwarePrepareStep: ({ getInputTokens, onAddBreakpoint, }: {
+        getInputTokens: () => number;
+        onAddBreakpoint?: (stepNumber: number) => void;
+    }) => (step: Parameters<PrepareStepFunction<any>>[0]) => {
+        steps: import("ai").StepResult<any>[];
+        stepNumber: number;
+        model: import("ai").LanguageModel;
+        messages: Array<import("ai").ModelMessage>;
+    };
+};
+//# sourceMappingURL=cache-breakpoint.d.ts.map

package/dist/ai-service/state-machine/helpers/cache-breakpoint.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"cache-breakpoint.d.ts","sourceRoot":"","sources":["../../../../src/ai-service/state-machine/helpers/cache-breakpoint.ts"],"names":[],"mappings":"AAAA,OAAO,KAAK,EAAE,KAAK,EAAE,MAAM,iBAAiB,CAAC;AAC7C,OAAO,KAAK,EAAE,mBAAmB,EAAE,MAAM,IAAI,CAAC;AAK9C,eAAO,MAAM,qBAAqB,GAChC,OAAO,KAAK,EACZ,2BAGG;IACD,SAAS,EAAE,MAAM,CAAC;IAClB,SAAS,CAAC,EAAE,MAAM,CAAC;CACpB;;;;;;;;;;;;;uEAgCI;QACD,cAAc,EAAE,MAAM,MAAM,CAAC;QAC7B,eAAe,CAAC,EAAE,CAAC,UAAU,EAAE,MAAM,KAAK,IAAI,CAAC;KAChD,MACA,MAAM,UAAU,CAAC,mBAAmB,CAAC,GAAG,CAAC,CAAC,CAAC,CAAC,CAAC;;;;;;CAiCjD,CAAC"}

package/dist/ai-service/state-machine/helpers/cache-breakpoint.js

@@ -0,0 +1,58 @@
+// claude currently supports up to 4
+const TOTAL_CACHE_BREAKPOINTS = 4;
+export const cacheBreakpointHelper = (clark, { agentName, threshold = 25_000, }) => {
+    const numUsed = () => clark.context.usedCacheBreakpoints?.[agentName] || 0;
+    const shouldAdd = (inputTokens) => {
+        return numUsed() < TOTAL_CACHE_BREAKPOINTS && inputTokens > threshold;
+    };
+    const next = () => {
+        const usedBreakpoints = numUsed();
+        if (usedBreakpoints < TOTAL_CACHE_BREAKPOINTS) {
+            clark.updateContext({
+                usedCacheBreakpoints: {
+                    ...clark.context.usedCacheBreakpoints,
+                    [agentName]: usedBreakpoints + 1,
+                },
+            });
+            return {
+                bedrock: { cachePoint: { type: "default" } },
+                // n.b. Vertex provider uses anthropic key
+                anthropic: { cacheControl: { type: "ephemeral" } },
+            };
+        }
+        return undefined;
+    };
+    const breakpointAwarePrepareStep = ({ getInputTokens, onAddBreakpoint, }) => (step) => {
+        const currentInputTokens = getInputTokens();
+        if (step.stepNumber > 1 && shouldAdd(currentInputTokens)) {
+            // update the last assistant message in place to add breakpoint
+            for (let index = step.messages.length - 1; index >= 0; index--) {
+                const message = step.messages[index];
+                if (message?.role === "assistant") {
+                    const breakpoint = next();
+                    if (breakpoint) {
+                        message.providerOptions = {
+                            ...message.providerOptions,
+                            bedrock: {
+                                ...message.providerOptions?.bedrock,
+                                ...breakpoint.bedrock,
+                            },
+                            anthropic: {
+                                ...message.providerOptions?.anthropic,
+                                ...breakpoint.anthropic,
+                            },
+                        };
+                        onAddBreakpoint?.(step.stepNumber);
+                    }
+                    break;
+                }
+            }
+        }
+        return step;
+    };
+    return {
+        nextCacheBreakpoint: next,
+        breakpointAwarePrepareStep,
+    };
+};
+//# sourceMappingURL=cache-breakpoint.js.map

package/dist/ai-service/state-machine/helpers/cache-breakpoint.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"cache-breakpoint.js","sourceRoot":"","sources":["../../../../src/ai-service/state-machine/helpers/cache-breakpoint.ts"],"names":[],"mappings":"AAGA,oCAAoC;AACpC,MAAM,uBAAuB,GAAG,CAAC,CAAC;AAElC,MAAM,CAAC,MAAM,qBAAqB,GAAG,CACnC,KAAY,EACZ,EACE,SAAS,EACT,SAAS,GAAG,MAAM,GAInB,EACD,EAAE;IACF,MAAM,OAAO,GAAG,GAAG,EAAE,CAAC,KAAK,CAAC,OAAO,CAAC,oBAAoB,EAAE,CAAC,SAAS,CAAC,IAAI,CAAC,CAAC;IAE3E,MAAM,SAAS,GAAG,CAAC,WAAmB,EAAE,EAAE;QACxC,OAAO,OAAO,EAAE,GAAG,uBAAuB,IAAI,WAAW,GAAG,SAAS,CAAC;IACxE,CAAC,CAAC;IAEF,MAAM,IAAI,GAAG,GAAG,EAAE;QAChB,MAAM,eAAe,GAAG,OAAO,EAAE,CAAC;QAClC,IAAI,eAAe,GAAG,uBAAuB,EAAE,CAAC;YAC9C,KAAK,CAAC,aAAa,CAAC;gBAClB,oBAAoB,EAAE;oBACpB,GAAG,KAAK,CAAC,OAAO,CAAC,oBAAoB;oBACrC,CAAC,SAAS,CAAC,EAAE,eAAe,GAAG,CAAC;iBACjC;aACF,CAAC,CAAC;YAEH,OAAO;gBACL,OAAO,EAAE,EAAE,UAAU,EAAE,EAAE,IAAI,EAAE,SAAS,EAAE,EAAE;gBAC5C,0CAA0C;gBAC1C,SAAS,EAAE,EAAE,YAAY,EAAE,EAAE,IAAI,EAAE,WAAW,EAAE,EAAE;aAC1C,CAAC;QACb,CAAC;QAED,OAAO,SAAS,CAAC;IACnB,CAAC,CAAC;IAEF,MAAM,0BAA0B,GAC9B,CAAC,EACC,cAAc,EACd,eAAe,GAIhB,EAAE,EAAE,CACL,CAAC,IAA6C,EAAE,EAAE;QAChD,MAAM,kBAAkB,GAAG,cAAc,EAAE,CAAC;QAC5C,IAAI,IAAI,CAAC,UAAU,GAAG,CAAC,IAAI,SAAS,CAAC,kBAAkB,CAAC,EAAE,CAAC;YACzD,+DAA+D;YAC/D,KAAK,IAAI,KAAK,GAAG,IAAI,CAAC,QAAQ,CAAC,MAAM,GAAG,CAAC,EAAE,KAAK,IAAI,CAAC,EAAE,KAAK,EAAE,EAAE,CAAC;gBAC/D,MAAM,OAAO,GAAG,IAAI,CAAC,QAAQ,CAAC,KAAK,CAAC,CAAC;gBACrC,IAAI,OAAO,EAAE,IAAI,KAAK,WAAW,EAAE,CAAC;oBAClC,MAAM,UAAU,GAAG,IAAI,EAAE,CAAC;oBAC1B,IAAI,UAAU,EAAE,CAAC;wBACf,OAAO,CAAC,eAAe,GAAG;4BACxB,GAAG,OAAO,CAAC,eAAe;4BAC1B,OAAO,EAAE;gCACP,GAAG,OAAO,CAAC,eAAe,EAAE,OAAO;gCACnC,GAAG,UAAU,CAAC,OAAO;6BACtB;4BACD,SAAS,EAAE;gCACT,GAAG,OAAO,CAAC,eAAe,EAAE,SAAS;gCACrC,GAAG,UAAU,CAAC,SAAS;6BACxB;yBACF,CAAC;wBACF,eAAe,EAAE,CAAC,IAAI,CAAC,UAAU,CAAC,CAAC;oBACrC,CAAC;oBACD,MAAM;gBACR,CAAC;YACH,CAAC;QACH,CAAC;QACD,OAAO,IAAI,CAAC;IACd,CAAC,CAAC;IAEJ,OAAO;QACL,mBAAmB,EAAE,IAAI;QACzB,0BAA0B;KAC3B,CAAC;AACJ,CAAC,CAAC"}

package/dist/file-sync-vite-plugin.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"file-sync-vite-plugin.d.ts","sourceRoot":"","sources":["../src/file-sync-vite-plugin.ts"],"names":[],"mappings":"AA0DA,OAAO,KAAK,EACV,qBAAqB,EACrB,oBAAoB,EACrB,MAAM,qBAAqB,CAAC;AAI7B,OAAO,KAAK,EAAE,MAAM,EAAkB,MAAM,MAAM,CAAC;AAOnD,eAAO,MAAM,kBAAkB,EAAE,CAC/B,YAAY,EAAE,oBAAoB,EAClC,OAAO,CAAC,EAAE,qBAAqB,KAC5B;IAAE,MAAM,EAAE,MAAM,CAAC;IAAC,OAAO,EAAE,MAAM,IAAI,CAAA;CAkpCzC,CAAC"}
+{"version":3,"file":"file-sync-vite-plugin.d.ts","sourceRoot":"","sources":["../src/file-sync-vite-plugin.ts"],"names":[],"mappings":"AA0DA,OAAO,KAAK,EACV,qBAAqB,EACrB,oBAAoB,EACrB,MAAM,qBAAqB,CAAC;AAI7B,OAAO,KAAK,EAAE,MAAM,EAAkB,MAAM,MAAM,CAAC;AAOnD,eAAO,MAAM,kBAAkB,EAAE,CAC/B,YAAY,EAAE,oBAAoB,EAClC,OAAO,CAAC,EAAE,qBAAqB,KAC5B;IAAE,MAAM,EAAE,MAAM,CAAC;IAAC,OAAO,EAAE,MAAM,IAAI,CAAA;CAiqCzC,CAAC"}

package/dist/file-sync-vite-plugin.js

@@ -650,12 +650,18 @@ export const fileSyncVitePlugin = (pluginParams, options) => {
                 })();
             });
             if (syncService && aiService) {
-                socketManager.on("connect:editor", (socket) => {
+                socketManager.on("connect:editor", (socket, peerId) => {
                     void (async () => {
+                        if (aiService.isBusy()) {
+                            aiService.handleUserConnected(socket, peerId);
+                        }
                         const hasDraft = await syncService.hasLocalDraftChanges();
                         return socket.call.aiSetDraftState({ hasDraft });
                     })();
                 });
+                socketManager.on("disconnect:editor", (peerId) => {
+                    aiService.handleUserDisconnected(peerId);
+                });
                 syncService.on("draftStateChanged", (hasDraft) => {
                     void (async () => {
                         void socketManager.callEditorClients((socket) => {
@@ -900,6 +906,7 @@ export const fileSyncVitePlugin = (pluginParams, options) => {
                                 const err = new Error(error.message);
                                 err.stack = error.stack;
                                 err.name = error.name;
+                                void aiService.handleBuildSystemError(err);
                                 logger.error(`Error loading import ${module.url}: ${error.message}`, getErrorMeta(err));
                                 return [];
                             }
@@ -939,6 +946,9 @@ export const fileSyncVitePlugin = (pluginParams, options) => {
                                 return [];
                             }
                             lastImportErrorFiles.add(ctx.file);
+                            if (aiService?.isBusy()) {
+                                void aiService.handleBuildSystemError(error);
+                            }
                             logger.error(`Error loading import ${importPath}: ${error.message}`);
                             ctx.server.ws.send({
                                 type: "custom",