chore: Update to ADL CLI v0.26.0 and dependency versions

.flox/env/manifest.toml

@@ -5,24 +5,24 @@ go.pkg-path = "go"
 go.version = "1.25"
 
 golangci-lint.pkg-path = "golangci-lint"
-golangci-lint.version = "2.5.0"
+golangci-lint.version = "^2.6.0"
 golangci-lint.pkg-group = "common"
 
 go-task.pkg-path = "go-task"
-go-task.version = "3.45.4"
+go-task.version = "^3.45.4"
 go-task.pkg-group = "common"
 
 git.pkg-path = "git"
-git.version = "2.51.0"
+git.version = "^2.51.0"
 git.pkg-group = "common"
 
 docker.pkg-path = "docker"
-docker.version = "28.4.0"
+docker.version = "^28.5.1"
 docker.pkg-group = "common"
 
 claude-code.pkg-path = "claude-code"
+claude-code.version = "^2.0.37"
 claude-code.pkg-group = "common"
-claude-code.version = "2.0.15"
 
 [hook]
 on-activate = '''

.infer/config.yaml

@@ -0,0 +1,327 @@
+gateway:
+  url: http://localhost:8080
+  api_key: ""
+  timeout: 200
+  oci: ghcr.io/inference-gateway/inference-gateway:latest
+  run: true
+  docker: true
+  exclude_models:
+    - ollama_cloud/cogito-2.1:671b
+    - ollama_cloud/kimi-k2:1t
+    - ollama_cloud/kimi-k2-thinking
+    - ollama_cloud/deepseek-v3.1:671b
+client:
+  timeout: 200
+  retry:
+    enabled: true
+    max_attempts: 3
+    initial_backoff_sec: 5
+    max_backoff_sec: 60
+    backoff_multiplier: 2
+    retryable_status_codes:
+      - 400
+      - 408
+      - 429
+      - 500
+      - 502
+      - 503
+      - 504
+logging:
+  debug: false
+  dir: ""
+tools:
+  enabled: true
+  sandbox:
+    directories:
+      - .
+      - /tmp
+    protected_paths:
+      - .infer/
+      - .git/
+      - '*.env'
+  bash:
+    enabled: true
+    whitelist:
+      commands:
+        - ls
+        - pwd
+        - tree
+        - wc
+        - sort
+        - uniq
+        - head
+        - tail
+        - task
+        - make
+        - find
+      patterns:
+        - ^git status$
+        - ^git branch( --show-current)?( -[alrvd])?$
+        - ^git log
+        - ^git diff
+        - ^git remote( -v)?$
+        - ^git show
+  read:
+    enabled: true
+    require_approval: false
+  write:
+    enabled: true
+    require_approval: true
+  edit:
+    enabled: true
+    require_approval: true
+  delete:
+    enabled: true
+    require_approval: true
+  grep:
+    enabled: true
+    backend: auto
+    require_approval: false
+  tree:
+    enabled: true
+    require_approval: false
+  web_fetch:
+    enabled: true
+    whitelisted_domains:
+      - golang.org
+    safety:
+      max_size: 8192
+      timeout: 30
+      allow_redirect: true
+    cache:
+      enabled: true
+      ttl: 3600
+      max_size: 52428800
+  web_search:
+    enabled: true
+    default_engine: duckduckgo
+    max_results: 10
+    engines:
+      - duckduckgo
+      - google
+    timeout: 10
+  github:
+    enabled: true
+    token: '%GITHUB_TOKEN%'
+    base_url: https://api.github.com
+    owner: inference-gateway
+    safety:
+      max_size: 1048576
+      timeout: 30
+  todo_write:
+    enabled: true
+    require_approval: false
+  safety:
+    require_approval: true
+export:
+  output_dir: .infer
+  summary_model: ""
+agent:
+  model: ""
+  system_prompt: |
+    Autonomous software engineering agent. Execute tasks iteratively until completion.
+
+    IMPORTANT: You NEVER push to main or master or to the current branch - instead you create a branch and push to a branch.
+    IMPORTANT: You ALWAYS prefer to search for specific matches in a file rather than reading it all - prefer to use Grep tool over Read tool for efficiency.
+    IMPORTANT: You ALWAYS prefer to see AGENTS.md before README.md files.
+    IMPORTANT: When reading project documentation, prefer AGENTS.md if available, otherwise fallback to README.md - start by Using Grep tool and read all the headings followed by '^##' - found the section you were looking for? great - use Read tool. You didn't find anything? continue to see '^###'
+
+    RULES:
+    - Security: Defensive only (analysis, detection, docs)
+    - Style: no emojis/comments unless asked, use conventional commits
+    - Code: Follow existing patterns, check deps, no secrets
+    - Tasks: Use TodoWrite, mark progress immediately
+    - Chat exports: Read only "## Summary" to "---" section
+    - Tools: ALWAYS use parallel execution when possible - batch multiple tool calls in a single response to improve efficiency
+    - Tools: Prefer Grep for search, Read for specific files
+
+    PARALLEL TOOL EXECUTION:
+    - When you need to perform multiple operations, make ALL tool calls in a single response
+    - Examples: Read multiple files, search multiple patterns, execute multiple commands
+    - The system supports up to 5 concurrent tool executions by default
+    - This reduces back-and-forth communication and significantly improves performance
+
+    WORKFLOW:
+    When asked to implement features or fix issues:
+    1. Plan with TodoWrite
+    2. Search codebase to understand context
+    3. Implement solution
+    4. Run tests with: task test
+    5. Run lint/format with: task fmt and task lint
+    6. Commit changes (only if explicitly asked)
+    7. Create a pull request (only if explicitly asked)
+
+    EXAMPLE:
+    <user>Can you create a pull request with the changes?</user>
+    <assistant>I will checkout to a new branch</assistant>
+    <tool>Bash(git checkout -b feat/my-new-feature)</tool>
+    <assistant>Now I will modify the files</assistant>
+    <tool>Read|Edit|Grep etc</tool>
+    <tool>Bash(git add <files>)</tool>
+    <tool>Bash(git commit -m <message>)</tool>
+    <assistant>Now I will push the changes</assistant>
+    <tool>Bash(git push origin <branch>)</tool>
+    <assistant>Now I'll create a pull request</assistant>
+    <tool>Github(...)</tool>
+  system_prompt_plan: |-
+    You are an AI planning assistant in PLAN MODE. Your role is to analyze user requests and create detailed, actionable plans WITHOUT executing them.
+
+    CAPABILITIES IN PLAN MODE:
+    - Read, Grep, and Tree tools ONLY for gathering information
+    - Analyze code structure and dependencies
+    - Break down complex tasks into clear steps
+    - Explain reasoning and approaches
+    - Identify potential challenges and solutions
+
+    RESTRICTIONS IN PLAN MODE:
+    - DO NOT execute Write, Edit, Delete, Bash, or modification tools
+    - DO NOT make any changes to files or system
+    - DO NOT attempt to implement the plan
+    - Focus solely on planning and explanation
+
+    PLANNING WORKFLOW:
+    1. Use Read/Grep/Tree to understand the codebase
+    2. Analyze the user's request thoroughly
+    3. Break down into logical, sequential steps
+    4. Explain your reasoning for each step
+    5. Identify files/components that need changes
+    6. Suggest testing and validation approaches
+    7. Present the complete plan to the user
+
+    OUTPUT FORMAT:
+    Structure your plan clearly with:
+    - Overview: What needs to be done and why
+    - Steps: Numbered, actionable steps with explanations
+    - Files: List of files that would be modified
+    - Testing: How to verify the changes
+    - Considerations: Potential issues or alternatives
+  system_reminders:
+    enabled: true
+    interval: 4
+    reminder_text: |-
+      <system-reminder>
+      This is a reminder that your todo list is currently empty. DO NOT mention this to the user explicitly because they are already aware. If you are working on tasks that would benefit from a todo list please use the TodoWrite tool to create one. If not, please feel free to ignore. Again do not mention this message to the user.
+      </system-reminder>
+  verbose_tools: false
+  max_turns: 50
+  max_tokens: 8192
+  max_concurrent_tools: 5
+  optimization:
+    enabled: true
+    model: ""
+    min_messages: 50
+    buffer_size: 2
+git:
+  commit_message:
+    model: ""
+    system_prompt: |-
+      Generate a concise git commit message following conventional commit format.
+
+      REQUIREMENTS:
+      - MUST use format: "type: Brief description"
+      - MUST be under 50 characters total
+      - MUST use imperative mood (e.g., "Add", "Fix", "Update")
+      - Types: feat, fix, docs, style, refactor, test, chore
+
+      EXAMPLES:
+      - "feat: Add git shortcut with AI commits"
+      - "fix: Resolve build error in container"
+      - "docs: Update README installation guide"
+      - "refactor: Simplify error handling"
+
+      Respond with ONLY the commit message, no quotes or explanation.
+scm:
+  pr_create:
+    prompt: ""
+    base_branch: main
+    branch_prefix: ""
+    model: ""
+  cleanup:
+    return_to_base: true
+    delete_local_branch: false
+storage:
+  enabled: true
+  type: sqlite
+  sqlite:
+    path: .infer/conversations.db
+  postgres:
+    host: localhost
+    port: 5432
+    database: infer_conversations
+    username: ""
+    password: ""
+    ssl_mode: prefer
+  redis:
+    host: localhost
+    port: 6379
+    password: ""
+    db: 0
+conversation:
+  title_generation:
+    enabled: true
+    model: ""
+    system_prompt: |-
+      Generate a concise conversation title based on the messages provided.
+
+      REQUIREMENTS:
+      - MUST be under 50 characters total
+      - MUST be descriptive and capture the main topic
+      - MUST use title case
+      - NO quotes, colons, or special characters
+      - Focus on the primary subject or task discussed
+
+      EXAMPLES:
+      - "React Component Testing"
+      - "Database Migration Setup"
+      - "API Error Handling"
+      - "Docker Configuration"
+
+      Respond with ONLY the title, no quotes or explanation.
+    batch_size: 10
+    interval: 0
+chat:
+  theme: tokyo-night
+a2a:
+  enabled: true
+  cache:
+    enabled: true
+    ttl: 300
+  task:
+    status_poll_seconds: 5
+    polling_strategy: exponential
+    initial_poll_interval_sec: 2
+    max_poll_interval_sec: 60
+    backoff_multiplier: 2
+    background_monitoring: true
+    completed_task_retention: 5
+  tools:
+    query_agent:
+      enabled: true
+      require_approval: false
+    query_task:
+      enabled: true
+      require_approval: false
+    submit_task:
+      enabled: true
+      require_approval: false
+    download_artifacts:
+      enabled: true
+      download_dir: /tmp/downloads
+      timeout_seconds: 30
+      require_approval: false
+init:
+  prompt: |-
+    Please analyze this project and generate a comprehensive AGENTS.md file. Start by using the Tree tool to understand the project structure.
+    Use your available tools to examine configuration files, documentation, build systems, and development workflow.
+    Focus on creating actionable documentation that will help other AI agents understand how to work effectively with this project.
+
+    The AGENTS.md file should include:
+    - Project overview and main technologies
+    - Architecture and structure
+    - Development environment setup
+    - Key commands (build, test, lint, run)
+    - Testing instructions
+    - Project conventions and coding standards
+    - Important files and configurations
+
+    Write the AGENTS.md file to the project root when you have gathered enough information.