@vfarcic/dot-ai 0.140.0 → 0.143.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@vfarcic/dot-ai",
-  "version": "0.140.0",
+  "version": "0.143.0",
   "description": "AI-powered development productivity platform that enhances software development workflows through intelligent automation and AI-driven assistance",
   "mcpName": "io.github.vfarcic/dot-ai",
   "main": "dist/index.js",
@@ -19,15 +19,13 @@
     "test:integration": "./tests/integration/infrastructure/run-integration-tests.sh",
     "test:integration:watch": "vitest --config=vitest.integration.config.ts --test-timeout=1200000",
     "test:integration:sonnet": "AI_PROVIDER=anthropic AI_PROVIDER_SDK=vercel DEBUG_DOT_AI=true ./tests/integration/infrastructure/run-integration-tests.sh",
+    "test:integration:opus": "AI_PROVIDER=anthropic_opus AI_PROVIDER_SDK=vercel DEBUG_DOT_AI=true ./tests/integration/infrastructure/run-integration-tests.sh",
     "test:integration:haiku": "AI_PROVIDER=anthropic_haiku AI_PROVIDER_SDK=vercel DEBUG_DOT_AI=true ./tests/integration/infrastructure/run-integration-tests.sh",
     "test:integration:gpt": "AI_PROVIDER=openai AI_PROVIDER_SDK=vercel DEBUG_DOT_AI=true ./tests/integration/infrastructure/run-integration-tests.sh",
-    "test:integration:gpt-pro": "AI_PROVIDER=openai_pro AI_PROVIDER_SDK=vercel DEBUG_DOT_AI=true ./tests/integration/infrastructure/run-integration-tests.sh",
     "test:integration:gemini": "AI_PROVIDER=google AI_PROVIDER_SDK=vercel DEBUG_DOT_AI=true ./tests/integration/infrastructure/run-integration-tests.sh",
-    "test:integration:gemini-flash": "AI_PROVIDER=google_fast AI_PROVIDER_SDK=vercel DEBUG_DOT_AI=true ./tests/integration/infrastructure/run-integration-tests.sh",
     "test:integration:grok": "AI_PROVIDER=xai AI_PROVIDER_SDK=vercel DEBUG_DOT_AI=true ./tests/integration/infrastructure/run-integration-tests.sh",
-    "test:integration:grok-fast": "AI_PROVIDER=xai_fast AI_PROVIDER_SDK=vercel DEBUG_DOT_AI=true ./tests/integration/infrastructure/run-integration-tests.sh",
-    "test:integration:mistral": "AI_PROVIDER=mistral AI_PROVIDER_SDK=vercel DEBUG_DOT_AI=true ./tests/integration/infrastructure/run-integration-tests.sh",
-    "test:integration:deepseek": "AI_PROVIDER=deepseek AI_PROVIDER_SDK=vercel DEBUG_DOT_AI=true ./tests/integration/infrastructure/run-integration-tests.sh",
+    "test:integration:kimi": "AI_PROVIDER=kimi AI_PROVIDER_SDK=vercel DEBUG_DOT_AI=true ./tests/integration/infrastructure/run-integration-tests.sh",
+    "test:integration:kimi-thinking": "AI_PROVIDER=kimi_thinking AI_PROVIDER_SDK=vercel DEBUG_DOT_AI=true ./tests/integration/infrastructure/run-integration-tests.sh",
     "test:integration:bedrock": "AI_PROVIDER=amazon_bedrock AI_MODEL=global.anthropic.claude-sonnet-4-20250514-v1:0 AI_PROVIDER_SDK=vercel DEBUG_DOT_AI=true ./tests/integration/infrastructure/run-integration-tests.sh",
     "test:integration:custom-endpoint": "AI_PROVIDER=openai AI_PROVIDER_SDK=vercel DEBUG_DOT_AI=true ./tests/integration/infrastructure/run-integration-tests.sh",
     "eval:comparative": "DEBUG_DOT_AI=true npx tsx src/evaluation/eval-runner.ts",
@@ -99,9 +97,7 @@
   "dependencies": {
     "@ai-sdk/amazon-bedrock": "^3.0.50",
     "@ai-sdk/anthropic": "^2.0.23",
-    "@ai-sdk/deepseek": "^1.0.23",
     "@ai-sdk/google": "^2.0.17",
-    "@ai-sdk/mistral": "^2.0.19",
     "@ai-sdk/openai": "^2.0.42",
     "@ai-sdk/xai": "^2.0.26",
     "@anthropic-ai/sdk": "^0.65.0",

package/prompts/operate-system.md

@@ -117,7 +117,7 @@ Once analysis is complete, respond with ONLY this JSON format:
   },
   "commands": [
     "kubectl set image deployment/my-api my-api=my-api:v2.0 -n default",
-    "kubectl apply -f /tmp/hpa.yaml"
+    "kubectl apply -f - <<EOF\napiVersion: autoscaling/v2\nkind: HorizontalPodAutoscaler\nmetadata:\n  name: my-api-hpa\n  namespace: default\nspec:\n  scaleTargetRef:\n    apiVersion: apps/v1\n    kind: Deployment\n    name: my-api\n  minReplicas: 2\n  maxReplicas: 10\nEOF"
   ],
   "dryRunValidation": {
     "status": "success",
@@ -173,7 +173,8 @@ Once analysis is complete, respond with ONLY this JSON format:
 - **Use specific resources**: `deployment/my-api` not `deployments my-api`
 - **Include namespace**: Always specify `-n namespace` for clarity
 - **Imperative when possible**: Use `kubectl set image`, `kubectl scale` for simple updates
-- **Declarative for complex**: Use `kubectl apply` for multi-field updates or new resources
+- **Declarative for complex**: Use `kubectl apply -f -` with inline heredoc YAML for new resources
+- **Never reference files**: Don't use `kubectl apply -f /path/file.yaml` - files don't exist. Always use inline YAML with heredoc: `kubectl apply -f - <<EOF\n...\nEOF`
 - **No shell operators**: Don't chain commands with `&&` or `;` - return array of individual commands
 
 **Command ordering**:
@@ -289,7 +290,7 @@ Once analysis is complete, respond with ONLY this JSON format:
   },
   "commands": [
     "kubectl patch deployment/my-api -n default --type=json -p='[{\"op\": \"add\", \"path\": \"/spec/template/spec/containers/0/resources\", \"value\": {\"requests\": {\"cpu\": \"100m\", \"memory\": \"128Mi\"}}}]'",
-    "kubectl apply -f /tmp/scaled-object.yaml"
+    "kubectl apply -f - <<EOF\napiVersion: keda.sh/v1alpha1\nkind: ScaledObject\nmetadata:\n  name: my-api-scaler\n  namespace: default\nspec:\n  scaleTargetRef:\n    name: my-api\n  minReplicaCount: 2\n  maxReplicaCount: 10\n  triggers:\n  - type: cpu\n    metricType: Utilization\n    metadata:\n      value: '70'\nEOF"
   ],
   "dryRunValidation": {
     "status": "success",

package/prompts/question-generation.md

@@ -164,10 +164,17 @@ Return your response as JSON in this exact format:
   "open": {
     "question": "Is there anything else about your requirements or constraints that would help us provide better recommendations?",
     "placeholder": "e.g., specific security requirements, performance needs, existing infrastructure constraints..."
-  }
+  },
+  "relevantPolicies": ["Minimum 3 replicas for production deployments", "Resource limits required for all containers"]
 }
 ```
 
+**CRITICAL - Relevant Policies Field:**
+- Include `relevantPolicies` array with the **descriptions** of organizational policies that influenced your question generation
+- Use the policy `description` field from the Organizational Policies section provided above
+- Only include policies that were actually applied (e.g., policies that resulted in questions being added or made required)
+- Use empty array `[]` if no organizational policies influenced the questions
+
 ## Important Notes
 
 - **CRITICAL VALIDATION REQUIREMENT**: The REQUIRED section MUST contain a question with `"id": "name"` - responses without this will be rejected

package/prompts/remediate-system.md

@@ -95,6 +95,15 @@ Once investigation is complete, respond with ONLY this JSON format:
 - **Focus on fixes**: Include only actions that change system state to resolve issue
 - **No validation actions**: Describe validation needs in `validationIntent`, not as separate actions
 
+**Kubectl Patch Strategy Selection**:
+- **Use `--type=json` for array updates** (containers, volumes, env vars):
+  - JSON Patch allows precise array element targeting by index
+  - Example: `kubectl patch deployment app -n ns --type=json -p='[{"op":"replace","path":"/spec/template/spec/containers/0/resources/limits/memory","value":"256Mi"}]'`
+- **Use `--type=merge` for simple field updates**:
+  - Simpler syntax for non-array fields
+  - Example: `kubectl patch deployment app -n ns --type=merge -p='{"spec":{"replicas":3}}'`
+- **Avoid `--type=strategic`**: Can cause "invalid character" errors with partial array specifications, especially for containers
+
 **Risk Assessment**:
 - **Low risk**: Restart pods, scale replicas, update labels, increase resource requests
 - **Medium risk**: Change environment variables, update resource limits, modify ConfigMaps/Secrets, patch deployments
@@ -125,7 +134,7 @@ Once investigation is complete, respond with ONLY this JSON format:
     "actions": [
       {
         "description": "Remove bootstrap.recovery configuration to allow fresh cluster initialization",
-        "command": "kubectl patch cluster postgres-db -n test-ns --type=json -p='[{\"op\": \"remove\", \"path\": \"/spec/bootstrap/recovery\"}]'",
+        "command": "kubectl patch cluster postgres-db -n test-ns --type=json -p='[{\"op\":\"remove\",\"path\":\"/spec/bootstrap/recovery\"}]'",
         "risk": "medium",
         "rationale": "Removing invalid backup reference allows operator to create cluster with fresh initialization instead of waiting for non-existent backup"
       }

package/prompts/resource-selection.md

@@ -82,20 +82,18 @@ Respond with ONLY a JSON object containing an array of complete solutions. Each
       "score": 95,
       "description": "Complete web application deployment with networking",
       "reasons": ["High capability match for web applications", "Includes essential networking"],
-      "patternInfluences": [
-        {
-          "patternId": "web-app-pattern-123",
-          "description": "Web application deployment pattern",
-          "influence": "high",
-          "matchedTriggers": ["web application", "frontend"]
-        }
-      ],
-      "usedPatterns": true
+      "appliedPatterns": ["High availability web application pattern", "Ingress with TLS termination"]
     }
   ]
 }
 ```
 
+**CRITICAL - Applied Patterns Field:**
+- Include `appliedPatterns` array with the **descriptions** of organizational patterns you applied to this solution
+- Use the pattern `description` field from the Organizational Patterns section provided above
+- Only include patterns that directly influenced this solution's resource selection or configuration
+- Use empty array `[]` if no organizational patterns were applied
+
 IMPORTANT: Your response must be ONLY the JSON object, nothing else.
 
 ## Selection Philosophy

package/scripts/crossplane.nu

@@ -27,7 +27,7 @@ def --env "main apply crossplane" [
     (
         helm upgrade --install crossplane "crossplane/crossplane"
             --namespace crossplane-system --create-namespace
-            --set provider.defaultActivations={"*.m.upbound.io", "*.m.crossplane.io"}
+            --set provider.defaultActivations={"*.m.upbound.io","*.m.crossplane.io"}
             --wait
     )
 

package/scripts/dot-ai.nu

@@ -1,6 +1,6 @@
 #!/usr/bin/env nu
 
-# Installs DevOps AI Toolkit with MCP server support
+# Installs DevOps AI Toolkit with MCP server support and controller
 #
 # Examples:
 # > main apply dot-ai --host dot-ai.127.0.0.1.nip.io
@@ -12,8 +12,10 @@ def "main apply dot-ai" [
     --provider = "anthropic",
     --model = "claude-haiku-4-5-20251001",
     --ingress-enabled = true,
+    --ingress-class = "nginx",
     --host = "dot-ai.127.0.0.1.nip.io",
-    --version = "0.128.0",
+    --version = "0.140.0",
+    --controller-version = "0.16.0",
     --enable-tracing = false
 ] {
 
@@ -42,6 +44,13 @@ def "main apply dot-ai" [
         []
     }
 
+    (
+        helm upgrade --install dot-ai-controller
+            $"oci://ghcr.io/vfarcic/dot-ai-controller/charts/dot-ai-controller:($controller_version)"
+            --namespace dot-ai --create-namespace
+            --wait
+    )
+
     (
         helm upgrade --install dot-ai-mcp
             $"oci://ghcr.io/vfarcic/dot-ai/charts/dot-ai:($version)"
@@ -50,12 +59,15 @@ def "main apply dot-ai" [
             --set $"ai.provider=($provider)"
             --set $"ai.model=($model)"
             --set $"ingress.enabled=($ingress_enabled)"
+            --set $"ingress.className=($ingress_class)"
             --set $"ingress.host=($host)"
+            --set "controller.enabled=true"
             ...$tracing_flags
             --namespace dot-ai --create-namespace
             --wait
     )
 
+    print $"DevOps AI Controller (ansi yellow_bold)($controller_version)(ansi reset) installed in (ansi yellow_bold)dot-ai(ansi reset) namespace"
     print $"DevOps AI Toolkit is available at (ansi yellow_bold)http://($host)(ansi reset)"
 
     if $enable_tracing {

package/shared-prompts/prd-close.md

@@ -119,7 +119,7 @@ Update the PRD metadata and add completion work log:
 
 ### Step 4: Move PRD to Archive
 
-Move the PRD file to the done directory:
+Move the PRD file to the done directory and update roadmap:
 
 ```bash
 # Create done directory if it doesn't exist
@@ -129,6 +129,12 @@ mkdir -p prds/done
 git mv prds/[number]-[name].md prds/done/
 ```
 
+**Update ROADMAP.md (if it exists):**
+- [ ] Check if `docs/ROADMAP.md` exists
+- [ ] Remove the closed PRD from the roadmap (search for "PRD #[number]")
+- [ ] Remove the entire line that references this PRD
+- [ ] Closed PRDs should not appear in future roadmap as they're no longer being worked on
+
 ### Step 5: Update GitHub Issue
 
 **Reopen issue temporarily to update:**

package/shared-prompts/deploy.md

@@ -1,23 +0,0 @@
----
-name: deploy
-description: Deploy applications, infrastructure, and services to Kubernetes
-category: deployment
----
-
-# Deploy to Kubernetes
-
-What do you want to deploy?
-
-**Examples:**
-- "Deploy a Node.js web application with PostgreSQL database"
-- "Deploy Prometheus monitoring with Grafana dashboards"
-- "Deploy WordPress with MySQL and persistent storage"
-- "Deploy ArgoCD for GitOps workflows"
-- "Deploy Redis cluster for caching"
-- "Deploy ingress controller with SSL certificates"
-
-**Your deployment intent**: [Please describe what you want to deploy]
-
----
-
-Once you provide your intent, I'll call the `recommend` tool to generate deployment recommendations for your Kubernetes cluster.

package/shared-prompts/manage-org-data.md

@@ -1,42 +0,0 @@
----
-name: manage-org-data
-description: Manage organizational patterns, policy intents, and cluster resource capabilities
-category: administration
----
-
-# Manage Organizational Data
-
-## Choose what you want to manage:
-
-### Organizational Patterns:
-1. Create a new organizational pattern
-2. List existing patterns
-3. Get pattern details
-4. Search patterns
-5. Delete a specific pattern
-6. Delete all patterns
-
-### Policy Intents:
-7. Create a new policy intent
-8. List existing policy intents
-9. Get policy intent details
-10. Search policy intents
-11. Delete a specific policy intent
-12. Delete all policy intents
-
-### Resource Capabilities:
-13. Scan cluster for resource capabilities
-14. List discovered capabilities
-15. Get capability details
-16. Delete specific capability data
-17. Delete all capabilities
-18. Check scan progress
-19. Analyze capabilities
-
-**Your choice**: [Type the number (1-19) or describe what you want to do]
-
----
-
-Examples: Type "1" or "Create a new organizational pattern" or "7" or "Create a new policy intent" or "13" or "Scan cluster"
-
-Once you make your choice, I'll call the `manageOrgData` tool with the appropriate parameters.

package/shared-prompts/remediate.md

@@ -1,44 +0,0 @@
----
-name: remediate
-description: AI-powered Kubernetes issue analysis and remediation
-category: troubleshooting
----
-
-# Kubernetes Issue Remediation
-
-## What's going wrong with your Kubernetes cluster?
-
-Describe the issue you're experiencing and I'll use AI-powered investigation to identify the root cause and provide executable remediation steps.
-
-**Examples:**
-- "Pod stuck in Pending state"
-- "Database connection failing in production namespace"
-- "Application deployment not working"
-- "Something is wrong with my ingress"
-- "Memory issues in my pods"
-- "Storage problems in namespace xyz"
-- "Network connectivity issues"
-- "Service discovery not working"
-
-**Your issue description**: [Describe what's going wrong]
-
----
-
-## Execution Modes:
-
-**Manual Mode** (default): You review and approve each remediation step
-**Automatic Mode**: AI executes low-risk fixes automatically based on confidence thresholds
-
-To use automatic mode, add phrases like:
-- "fix this automatically"
-- "remediate automatically with high confidence"
-- "auto-fix if safe"
-
----
-
-Once you describe your issue, I'll call the `remediate` tool to:
-1. **Investigate** - Multi-step analysis to identify root cause
-2. **Analyze** - Provide detailed explanation with confidence level  
-3. **Remediate** - Generate specific kubectl commands with risk assessment
-4. **Execute** - Run fixes via MCP or guide you through manual execution
-5. **Validate** - Confirm the issue is resolved

package/shared-prompts/status.md

@@ -1,19 +0,0 @@
----
-name: status
-description: Check system status and health
-category: administration
----
-
-# System Status Check
-
-I'll check the comprehensive system status including:
-
-✅ **Version information**
-✅ **Vector DB connection status** 
-✅ **Embedding service capabilities**
-✅ **Anthropic API connectivity**
-✅ **Pattern management health**
-
----
-
-Calling the `version` tool to get current system status...