@axiom-lattice/core 2.1.82 → 2.1.84

package/dist/index.mjs

@@ -5884,9 +5884,6 @@ var SandboxLatticeManager = class _SandboxLatticeManager extends BaseLatticeMana
     return this.keys();
   }
   resolvePolicy(config) {
-    if (config.vmIsolation) {
-      return { vmIsolation: config.vmIsolation };
-    }
     if (config.projectId) {
       return { vmIsolation: "project" };
     }
@@ -14087,6 +14084,7 @@ function createFilesystemBackendFactory(middlewareConfigs) {
   return async (stateAndStore) => {
     const { tenantId, workspaceId, projectId, assistant_id, threadId } = stateAndStore;
     const sandboxManager = getSandBoxManager();
+    console.log(`[filesystemBackend] creating sandbox: tenantId=${tenantId} workspaceId=${workspaceId} projectId=${projectId} assistant_id=${assistant_id} threadId=${threadId} vmIsolation=${filesystemConfig.config?.vmIsolation || "(default)"}`);
     const sandbox = await sandboxManager.getSandboxFromConfig({
       assistant_id: assistant_id || "",
       thread_id: threadId || "",
@@ -20332,7 +20330,7 @@ You have nine tools for agent management:
 - **list_tools** \u2014 See all available tools that can be assigned to agents
 - **get_agent** \u2014 View the full configuration of a specific agent
 - **create_agent** \u2014 Create a REACT or DEEP_AGENT agent
-- **create_workflow** \u2014 Create a WORKFLOW agent from a concise DSL (load create-workflow skill first)
+- **create_workflow** \u2014 Create a WORKFLOW agent from a concise DSL (load create-workflow skill + task-relevant domain skills first)
 - **validate_workflow** \u2014 Validate a workflow agent's DSL
 - **update_workflow** \u2014 Update a workflow agent's DSL or config
 - **update_agent** \u2014 Modify an existing REACT or DEEP_AGENT agent's configuration
@@ -20429,14 +20427,23 @@ Use this when the process is fully known. A workflow is a deterministic LangGrap
 | needs + if model (YAML DSL) | Single orchestrator delegates linearly |
 | No LLM routing decisions | Orchestrator uses LLM to route |
 
-### Phase 0: Load the Skill
+### Phase 0: Load Skills
+
+**BEFORE designing, you MUST load relevant skills:**
 
-**BEFORE designing, you MUST load the create-workflow skill:**
+1. **Always load** the \`create-workflow\` skill \u2014 it teaches the YAML DSL syntax, step format, and design patterns:
 
 \`\`\`
 skill(skill_name: "create-workflow")
 \`\`\`
 
+2. **Determine and load task-relevant domain skills** \u2014 do NOT skip this step:
+   a) **First, scan** the \`<available_skills>\` section above. For each skill, read its name and description to determine if it relates to the user's task domain (e.g., financial analysis, sales, data processing, reporting)
+   b) **Then, load each relevant skill** by calling \`skill(skill_name: "<skill-name>")\` \u2014 call this once per relevant skill, NOT in a batch
+   c) Read the loaded skill content for domain-specific workflow patterns, reusable sub-workflows, and DSL best practices
+
+**If you skip step 2, you will miss critical domain knowledge and produce a suboptimal design.**
+
 ### Phase 1: Design
 
 1. **Analyze the process.** Map every step, branch, data dependency.
@@ -20551,7 +20558,7 @@ All fields except name, type, and prompt are optional.
 
 ### create_workflow (WORKFLOW)
 
-Creates a WORKFLOW agent from a YAML linear DSL. Before calling, load the \`create-workflow\` skill. Must pass \`skillLoaded: true\`.
+Creates a WORKFLOW agent from a YAML linear DSL. Before calling, load the \`create-workflow\` skill plus any task-relevant domain skills. Must pass \`skillLoaded: true\`.
 
 \`\`\`typescript
 {
@@ -20866,6 +20873,14 @@ var agentArchitectConfig = {
   ],
   internalSubAgents: [agentReviewerConfig],
   middleware: [
+    {
+      id: "filesystem",
+      type: "filesystem",
+      name: "Filesystem",
+      description: "Read, write, edit, list, search files",
+      enabled: true,
+      config: {}
+    },
     {
       id: "skill",
       type: "skill",
@@ -22549,6 +22564,7 @@ var MicrosandboxServiceClient = class {
     );
   }
   async volumeFsList(volumeName, path3) {
+    console.log(`[volumeFsList] volume=${volumeName} path="${path3}" url=POST /api/volumes/${encodeURIComponent(volumeName)}/fs/list`);
     const result = await this.request(
       `/api/volumes/${encodeURIComponent(volumeName)}/fs/list`,
       {
@@ -22556,6 +22572,10 @@ var MicrosandboxServiceClient = class {
         body: { path: path3 }
       }
     );
+    console.log(
+      `[volumeFsList] result: ${result.entries.length} entries:`,
+      result.entries.map((e) => `${e.path} (kind=${e.kind})`).join(", ")
+    );
     return result.entries;
   }
   async volumeFsDownload(volumeName, path3) {