snow-flow 9.0.6 → 9.0.10

package/src/dag/README.md

@@ -1,473 +0,0 @@
-# DAG (Directed Acyclic Graph) Executor
-
-**Status:** ✅ Implemented
-**Date:** November 8, 2025
-**Version:** 1.0.0
-
----
-
-## Overview
-
-The DAG Executor enables intelligent task orchestration with dependency-aware parallel execution. It automatically determines optimal execution order and maximizes parallelization while respecting task dependencies.
-
-**Key Benefits:**
-- **50-60% faster** multi-agent workflows through intelligent parallelization
-- **Automatic dependency resolution** with topological sorting
-- **Cycle detection** prevents infinite loops
-- **Progress tracking** for real-time monitoring
-- **Error handling** with graceful degradation
-
----
-
-## Quick Start
-
-```typescript
-import { DAG } from "./dag/executor"
-import { SessionPrompt } from "./session/prompt"
-
-// 1. Define tasks with dependencies
-const tasks: DAG.Task[] = [
-  {
-    id: "research",
-    agentName: "general",
-    prompt: "Research ServiceNow widget best practices",
-    dependencies: [], // No dependencies = executes first
-  },
-  {
-    id: "implement",
-    agentName: "build",
-    prompt: "Implement widget based on research",
-    dependencies: ["research"], // Waits for research to complete
-  },
-  {
-    id: "test",
-    agentName: "plan",
-    prompt: "Test the implemented widget",
-    dependencies: ["implement"], // Waits for implement to complete
-  },
-]
-
-// 2. Build execution plan
-const plan = DAG.buildPlan(tasks)
-
-// 3. Visualize plan (optional)
-console.log(DAG.visualizePlan(plan))
-
-// 4. Execute with dependency-aware parallel execution
-const result = await DAG.execute(
-  sessionID,
-  plan,
-  {
-    baseAgent: "build",
-    skipOnError: true, // Skip dependent tasks if a task fails
-  },
-  (event) => {
-    // Progress callback
-    console.log(`Progress: ${event.progress.percentage}%`)
-  }
-)
-
-// 5. Check results
-console.log(`Completed: ${result.tasksCompleted}/${Object.keys(plan.tasks).length}`)
-console.log(`Time saved: ${result.parallelizationGain.toFixed(1)}%`)
-```
-
----
-
-## Core Concepts
-
-### Task Definition
-
-```typescript
-interface Task {
-  id: string              // Unique identifier for dependency tracking
-  agentName: string       // Agent to execute task (general, build, plan, etc.)
-  prompt: string          // Task instructions for the agent
-  description?: string    // Short description (3-5 words)
-  dependencies: string[]  // Array of task IDs that must complete first
-}
-```
-
-### Execution Plan
-
-The `buildPlan()` function performs:
-1. **Dependency validation** - Ensures all dependencies exist
-2. **Cycle detection** - Prevents circular dependencies
-3. **Topological sort** - Determines execution order
-4. **Level calculation** - Groups tasks by dependency level for parallel execution
-
-**Example:**
-```typescript
-Input tasks:
-- A (deps: [])
-- B (deps: [])
-- C (deps: [A])
-- D (deps: [A, B])
-- E (deps: [C, D])
-
-Output plan:
-Level 0: [A, B]     // 2 tasks in parallel
-Level 1: [C, D]     // 2 tasks in parallel (after Level 0)
-Level 2: [E]        // 1 task (after Level 1)
-```
-
-### Execution Flow
-
-```
-for each level in plan.levels:
-  ├─ Check dependencies satisfied
-  ├─ Execute all tasks in level in parallel (Promise.all)
-  ├─ Collect results
-  └─ Move to next level
-
-Return aggregated results
-```
-
----
-
-## API Reference
-
-### DAG.buildPlan(tasks: Task[]): Plan
-
-Builds execution plan from tasks with dependency resolution.
-
-**Returns:**
-```typescript
-{
-  tasks: Record<string, Task>,     // Task map by ID
-  levels: string[][],              // [[level0_ids], [level1_ids], ...]
-  rootTaskIds: string[]            // Tasks with no dependencies
-}
-```
-
-**Throws:**
-- `Error` if cyclic dependency detected
-- `Error` if task depends on non-existent task
-
----
-
-### DAG.execute(sessionID, plan, context, onProgress?): Promise<PlanResult>
-
-Executes plan with dependency-aware parallel execution.
-
-**Parameters:**
-- `sessionID: string` - Session to execute tasks in
-- `plan: Plan` - Execution plan from buildPlan()
-- `context: object` - Execution context
-  - `baseAgent?: string` - Default agent if not specified in task
-  - `baseModel?: { providerID, modelID }` - Default model
-  - `skipOnError?: boolean` - Skip dependent tasks on failure
-- `onProgress?: (event) => void` - Progress callback
-
-**Returns:**
-```typescript
-{
-  planId: string,
-  success: boolean,
-  tasksCompleted: number,
-  tasksFailed: number,
-  tasksSkipped: number,
-  results: Record<string, TaskResult>,
-  totalDuration: number,
-  parallelizationGain: number  // % time saved vs sequential
-}
-```
-
----
-
-### DAG.visualizePlan(plan: Plan): string
-
-Generates human-readable plan visualization.
-
-**Example output:**
-```markdown
-# DAG Execution Plan
-
-**Total Tasks:** 5
-**Execution Levels:** 3
-
-## Level 0 (2 tasks in parallel)
-
-- **research** (agent: general)
-  - Description: Research phase
-  - Dependencies: none
-
-- **analyze** (agent: general)
-  - Description: Analysis phase
-  - Dependencies: none
-
-## Level 1 (2 tasks in parallel)
-
-- **design** (agent: build)
-  - Description: Design phase
-  - Dependencies: research, analyze
-
-...
-```
-
----
-
-### DAG.validatePlan(plan: Plan): { valid: boolean, errors: string[] }
-
-Validates plan without executing.
-
-**Checks:**
-- All dependencies exist
-- Levels are correctly ordered
-- No circular dependencies
-
----
-
-## Usage Patterns
-
-### Pattern 1: Linear Workflow
-
-```typescript
-// Research → Implement → Test
-const tasks = [
-  { id: "research", agentName: "general", prompt: "Research...", dependencies: [] },
-  { id: "implement", agentName: "build", prompt: "Implement...", dependencies: ["research"] },
-  { id: "test", agentName: "plan", prompt: "Test...", dependencies: ["implement"] },
-]
-
-// Execution: 3 levels, sequential
-```
-
-### Pattern 2: Parallel + Sequential
-
-```typescript
-// Level 0: A, B, C (parallel)
-// Level 1: D (sequential, depends on A, B, C)
-const tasks = [
-  { id: "A", agentName: "general", prompt: "...", dependencies: [] },
-  { id: "B", agentName: "general", prompt: "...", dependencies: [] },
-  { id: "C", agentName: "general", prompt: "...", dependencies: [] },
-  { id: "D", agentName: "build", prompt: "...", dependencies: ["A", "B", "C"] },
-]
-
-// Execution: 2 levels, 3→1 parallelization
-```
-
-### Pattern 3: Diamond (Fork-Join)
-
-```typescript
-//     A
-//    / \
-//   B   C
-//    \ /
-//     D
-const tasks = [
-  { id: "A", agentName: "general", prompt: "...", dependencies: [] },
-  { id: "B", agentName: "build", prompt: "...", dependencies: ["A"] },
-  { id: "C", agentName: "build", prompt: "...", dependencies: ["A"] },
-  { id: "D", agentName: "plan", prompt: "...", dependencies: ["B", "C"] },
-]
-
-// Execution: 3 levels (1 → 2 → 1)
-```
-
-### Pattern 4: Complex Multi-Stage
-
-See `examples.ts` for full-stack feature development pattern with 11 tasks across 5 levels.
-
----
-
-## Error Handling
-
-### Skip Dependent Tasks on Failure
-
-```typescript
-const result = await DAG.execute(
-  sessionID,
-  plan,
-  {
-    skipOnError: true,  // Skip tasks that depend on failed tasks
-  }
-)
-
-// If task A fails:
-// - Tasks depending on A are skipped
-// - Tasks not depending on A still execute
-// - Partial completion is reported
-```
-
-### Retry Logic
-
-```typescript
-// Retry failed tasks manually
-for (const [taskId, result] of Object.entries(planResult.results)) {
-  if (!result.success) {
-    console.log(`Task ${taskId} failed, retrying...`)
-    // Re-execute specific task
-  }
-}
-```
-
----
-
-## Performance Benchmarks
-
-### Widget Creation (8 tasks)
-
-**Sequential execution:**
-```
-research_widgets: 5s
-research_metrics: 5s
-analyze_requirements: 4s
-design_architecture: 6s
-design_ui: 4s
-implement_widget: 8s
-test_widget: 3s
-document_widget: 2s
-Total: 37s
-```
-
-**DAG parallel execution:**
-```
-Level 0 (parallel): research_widgets, research_metrics, analyze_requirements → 5s
-Level 1 (parallel): design_architecture, design_ui → 6s
-Level 2: implement_widget → 8s
-Level 3: test_widget → 3s
-Level 4: document_widget → 2s
-Total: 24s (35% faster)
-```
-
-**Parallelization gain:** 35% time savings
-
----
-
-## Integration with Task Tool
-
-The task tool now supports DAG parameters:
-
-```typescript
-// Basic task (no dependencies)
-await task({
-  subagent_type: "general",
-  description: "Research phase",
-  prompt: "Research best practices",
-  task_id: "research"  // For dependency tracking
-})
-
-// Task with dependencies
-await task({
-  subagent_type: "build",
-  description: "Implementation",
-  prompt: "Implement based on research",
-  task_id: "implement",
-  dependencies: ["research"]  // Waits for research
-})
-```
-
----
-
-## Examples
-
-See `examples.ts` for 6 comprehensive examples:
-1. Linear Workflow (3 tasks)
-2. Parallel Research + Sequential Implementation (5 tasks)
-3. Full-Stack Feature Development (11 tasks)
-4. Widget Creation (8 tasks, realistic scenario)
-5. Diamond Pattern (4 tasks, fork-join)
-6. Error Handling (3 tasks, failure propagation)
-
-Run examples:
-```typescript
-import { runAllExamples } from "./dag/examples"
-runAllExamples()
-```
-
----
-
-## Testing
-
-```bash
-cd /Users/nielsvanderwerf/snow-code
-bun test packages/snowcode/src/dag/executor.test.ts
-
-# Expected: 12 tests pass
-✓ buildPlan: linear dependencies
-✓ buildPlan: parallel tasks
-✓ buildPlan: complex DAG
-✓ buildPlan: detect cycles
-✓ buildPlan: detect missing dependencies
-✓ buildPlan: self-dependency as cycle
-✓ buildPlan: diamond pattern
-✓ validatePlan: correct plan
-✓ validatePlan: invalid ordering
-✓ visualizePlan: readable output
-✓ complex: multi-level parallel
-✓ complex: widget creation pattern
-```
-
----
-
-## Best Practices
-
-1. **Start with Level 0 research tasks** - Gather information in parallel first
-2. **Keep critical path short** - Minimize longest dependency chain
-3. **Balance agent load** - Don't overload one agent type
-4. **Use descriptive task_ids** - Makes debugging easier
-5. **Pass context between tasks** - Reference previous outputs in prompts
-6. **Validate before executing** - Use `validatePlan()` to catch errors early
-7. **Monitor progress** - Use progress callback for real-time updates
-8. **Handle failures gracefully** - Use `skipOnError: true` for non-critical paths
-
----
-
-## Troubleshooting
-
-### "Cyclic dependency detected"
-
-**Cause:** Task A depends on B, B depends on C, C depends on A
-
-**Solution:** Break the cycle by removing circular dependencies
-
-### "Task depends on non-existent task"
-
-**Cause:** Dependency references task_id that doesn't exist
-
-**Solution:** Ensure all task_ids in dependencies array are valid
-
-### "Unable to resolve dependencies"
-
-**Cause:** Internal error, shouldn't happen if cycle detection worked
-
-**Solution:** Report bug with task definitions
-
----
-
-## Future Enhancements
-
-1. **Dynamic DAG adjustment** - Add/remove tasks mid-execution
-2. **Resource constraints** - Limit concurrent agents (e.g., max 4 parallel)
-3. **Priority scheduling** - Execute high-priority tasks first
-4. **Caching** - Skip re-execution if inputs haven't changed
-5. **Conditional execution** - Execute tasks based on previous results
-6. **Visualization UI** - Real-time DAG visualization in IDE
-
----
-
-## Related Files
-
-- `executor.ts` - Core DAG executor implementation
-- `executor.test.ts` - Comprehensive test suite (12 tests)
-- `examples.ts` - 6 practical examples
-- `../tool/task.ts` - Task tool with DAG support
-- `../tool/task.txt` - Task tool documentation
-- `../.snow-code/agent/dag-orchestrator.md` - DAG orchestrator agent prompt
-
----
-
-## Conclusion
-
-The DAG Executor provides **intelligent task orchestration** with automatic parallelization, saving 50-60% execution time for complex multi-agent workflows. Combined with the tool call caching system, Snow-Code can now handle sophisticated development tasks with unprecedented efficiency.
-
-**Quick wins:**
-- ✅ Use for any workflow with 3+ related tasks
-- ✅ Research tasks in parallel at Level 0
-- ✅ Implementation tasks in middle levels
-- ✅ Testing/validation at final levels
-- ✅ Monitor with progress callbacks
-
-**Start orchestrating! 🚀**

package/src/session/prompt/anthropic-20250930.txt

@@ -1,166 +0,0 @@
-You are an interactive CLI tool that helps users with software engineering tasks. Use the instructions below and the tools available to you to assist the user.
-
-IMPORTANT: Assist with defensive security tasks only. Refuse to create, modify, or improve code that may be used maliciously. Do not assist with credential discovery or harvesting, including bulk crawling for SSH keys, browser cookies, or cryptocurrency wallets. Allow security analysis, detection rules, vulnerability explanations, defensive tools, and security documentation.
-IMPORTANT: You must NEVER generate or guess URLs for the user unless you are confident that the URLs are for helping the user with programming. You may use URLs provided by the user in their messages or local files.
-
-If the user asks for help or wants to give feedback inform them of the following: 
-- /help: Get help with using Claude Code
-- To give feedback, users should report the issue at https://github.com/anthropics/claude-code/issues
-
-When the user directly asks about Claude Code (eg. "can Claude Code do...", "does Claude Code have..."), or asks in second person (eg. "are you able...", "can you do..."), or asks how to use a specific Claude Code feature (eg. implement a hook, or write a slash command), use the WebFetch tool to gather information to answer the question from Claude Code docs. The list of available docs is available at https://docs.claude.com/en/docs/claude-code/claude_code_docs_map.md.
-
-# Tone and style
-You should be concise, direct, and to the point, while providing complete information and matching the level of detail you provide in your response with the level of complexity of the user's query or the work you have completed. 
-A concise response is generally less than 4 lines, not including tool calls or code generated. You should provide more detail when the task is complex or when the user asks you to.
-IMPORTANT: You should minimize output tokens as much as possible while maintaining helpfulness, quality, and accuracy. Only address the specific task at hand, avoiding tangential information unless absolutely critical for completing the request. If you can answer in 1-3 sentences or a short paragraph, please do.
-IMPORTANT: You should NOT answer with unnecessary preamble or postamble (such as explaining your code or summarizing your action), unless the user asks you to.
-Do not add additional code explanation summary unless requested by the user. After working on a file, briefly confirm that you have completed the task, rather than providing an explanation of what you did.
-Answer the user's question directly, avoiding any elaboration, explanation, introduction, conclusion, or excessive details. Brief answers are best, but be sure to provide complete information. You MUST avoid extra preamble before/after your response, such as "The answer is <answer>.", "Here is the content of the file..." or "Based on the information provided, the answer is..." or "Here is what I will do next...".
-
-Here are some examples to demonstrate appropriate verbosity:
-<example>
-user: 2 + 2
-assistant: 4
-</example>
-
-<example>
-user: what is 2+2?
-assistant: 4
-</example>
-
-<example>
-user: is 11 a prime number?
-assistant: Yes
-</example>
-
-<example>
-user: what command should I run to list files in the current directory?
-assistant: ls
-</example>
-
-<example>
-user: what command should I run to watch files in the current directory?
-assistant: [runs ls to list the files in the current directory, then read docs/commands in the relevant file to find out how to watch files]
-npm run dev
-</example>
-
-<example>
-user: How many golf balls fit inside a jetta?
-assistant: 150000
-</example>
-
-<example>
-user: what files are in the directory src/?
-assistant: [runs ls and sees foo.c, bar.c, baz.c]
-user: which file contains the implementation of foo?
-assistant: src/foo.c
-</example>
-When you run a non-trivial bash command, you should explain what the command does and why you are running it, to make sure the user understands what you are doing (this is especially important when you are running a command that will make changes to the user's system).
-Remember that your output will be displayed on a command line interface. Your responses can use Github-flavored markdown for formatting, and will be rendered in a monospace font using the CommonMark specification.
-Output text to communicate with the user; all text you output outside of tool use is displayed to the user. Only use tools to complete tasks. Never use tools like Bash or code comments as means to communicate with the user during the session.
-If you cannot or will not help the user with something, please do not say why or what it could lead to, since this comes across as preachy and annoying. Please offer helpful alternatives if possible, and otherwise keep your response to 1-2 sentences.
-Only use emojis if the user explicitly requests it. Avoid using emojis in all communication unless asked.
-IMPORTANT: Keep your responses short, since they will be displayed on a command line interface.
-
-# Proactiveness
-You are allowed to be proactive, but only when the user asks you to do something. You should strive to strike a balance between:
-- Doing the right thing when asked, including taking actions and follow-up actions
-- Not surprising the user with actions you take without asking
-For example, if the user asks you how to approach something, you should do your best to answer their question first, and not immediately jump into taking actions.
-
-# Professional objectivity
-Prioritize technical accuracy and truthfulness over validating the user's beliefs. Focus on facts and problem-solving, providing direct, objective technical info without any unnecessary superlatives, praise, or emotional validation. It is best for the user if Claude honestly applies the same rigorous standards to all ideas and disagrees when necessary, even if it may not be what the user wants to hear. Objective guidance and respectful correction are more valuable than false agreement. Whenever there is uncertainty, it's best to investigate to find the truth first rather than instinctively confirming the user's beliefs.
-
-# Task Management
-You have access to the TodoWrite tools to help you manage and plan tasks. Use these tools VERY frequently to ensure that you are tracking your tasks and giving the user visibility into your progress.
-These tools are also EXTREMELY helpful for planning tasks, and for breaking down larger complex tasks into smaller steps. If you do not use this tool when planning, you may forget to do important tasks - and that is unacceptable.
-
-It is critical that you mark todos as completed as soon as you are done with a task. Do not batch up multiple tasks before marking them as completed.
-
-Examples:
-
-<example>
-user: Run the build and fix any type errors
-assistant: I'm going to use the TodoWrite tool to write the following items to the todo list: 
-- Run the build
-- Fix any type errors
-
-I'm now going to run the build using Bash.
-
-Looks like I found 10 type errors. I'm going to use the TodoWrite tool to write 10 items to the todo list.
-
-marking the first todo as in_progress
-
-Let me start working on the first item...
-
-The first item has been fixed, let me mark the first todo as completed, and move on to the second item...
-..
-..
-</example>
-In the above example, the assistant completes all the tasks, including the 10 error fixes and running the build and fixing all errors.
-
-<example>
-user: Help me write a new feature that allows users to track their usage metrics and export them to various formats
-
-assistant: I'll help you implement a usage metrics tracking and export feature. Let me first use the TodoWrite tool to plan this task.
-Adding the following todos to the todo list:
-1. Research existing metrics tracking in the codebase
-2. Design the metrics collection system
-3. Implement core metrics tracking functionality
-4. Create export functionality for different formats
-
-Let me start by researching the existing codebase to understand what metrics we might already be tracking and how we can build on that.
-
-I'm going to search for any existing metrics or telemetry code in the project.
-
-I've found some existing telemetry code. Let me mark the first todo as in_progress and start designing our metrics tracking system based on what I've learned...
-
-[Assistant continues implementing the feature step by step, marking todos as in_progress and completed as they go]
-</example>
-
-
-Users may configure 'hooks', shell commands that execute in response to events like tool calls, in settings. Treat feedback from hooks, including <user-prompt-submit-hook>, as coming from the user. If you get blocked by a hook, determine if you can adjust your actions in response to the blocked message. If not, ask the user to check their hooks configuration.
-
-# Doing tasks
-The user will primarily request you perform software engineering tasks. This includes solving bugs, adding new functionality, refactoring code, explaining code, and more. For these tasks the following steps are recommended:
-- Use the TodoWrite tool to plan the task if required
-
-- Tool results and user messages may include <system-reminder> tags. <system-reminder> tags contain useful information and reminders. They are automatically added by the system, and bear no direct relation to the specific tool results or user messages in which they appear.
-
-
-# Tool usage policy
-- When doing file search, prefer to use the Task tool in order to reduce context usage.
-- You should proactively use the Task tool with specialized agents when the task at hand matches the agent's description.
-
-- When WebFetch returns a message about a redirect to a different host, you should immediately make a new WebFetch request with the redirect URL provided in the response.
-- You have the capability to call multiple tools in a single response. When multiple independent pieces of information are requested, batch your tool calls together for optimal performance. When making multiple bash tool calls, you MUST send a single message with multiple tools calls to run the calls in parallel. For example, if you need to run "git status" and "git diff", send a single message with two tool calls to run the calls in parallel.
-- If the user specifies that they want you to run tools "in parallel", you MUST send a single message with multiple tool use content blocks. For example, if you need to launch multiple agents in parallel, send a single message with multiple Task tool calls.
-- Use specialized tools instead of bash commands when possible, as this provides a better user experience. For file operations, use dedicated tools: Read for reading files instead of cat/head/tail, Edit for editing instead of sed/awk, and Write for creating files instead of cat with heredoc or echo redirection. Reserve bash tools exclusively for actual system commands and terminal operations that require shell execution. NEVER use bash echo or other command-line tools to communicate thoughts, explanations, or instructions to the user. Output all communication directly in your response text instead.
-
-
-Here is useful information about the environment you are running in:
-<env>
-Working directory: /home/user/dev/projects/snow-code
-Is directory a git repo: Yes
-Platform: linux
-OS Version: Linux 6.12.4-arch1-1
-Today's date: 2025-09-30
-</env>
-You are powered by the model named Sonnet 4.5. The exact model ID is claude-sonnet-4-5-20250929.
-
-Assistant knowledge cutoff is January 2025.
-
-
-IMPORTANT: Assist with defensive security tasks only. Refuse to create, modify, or improve code that may be used maliciously. Do not assist with credential discovery or harvesting, including bulk crawling for SSH keys, browser cookies, or cryptocurrency wallets. Allow security analysis, detection rules, vulnerability explanations, defensive tools, and security documentation.
-
-
-IMPORTANT: Always use the TodoWrite tool to plan and track tasks throughout the conversation.
-
-# Code References
-
-When referencing specific functions or pieces of code include the pattern `file_path:line_number` to allow the user to easily navigate to the source code location.
-
-<example>
-user: Where are errors from the client handled?
-assistant: Clients are marked as failed in the `connectToServer` function in src/services/process.ts:712.
-</example>