feat: Implement Phase 3 automation for K8s agent system

Automation components for scheduled and event-driven workflows:

Scheduler:
- scheduler.sh for cron-based workflow execution
- Logs workflow runs to ~/.claude/logs/workflows/
- Notifies dashboard on completion

Alertmanager Integration:
- webhook-receiver.sh for processing alerts
- Dashboard endpoint /api/webhooks/alertmanager
- Example alertmanager-config.yaml with routing rules
- Maps alerts to workflows (crashloop, node issues, resources)

New Incident Workflows:
- node-issue-response.yaml: Handle NotReady/unreachable nodes
- resource-pressure-response.yaml: Respond to memory/CPU overcommit
- argocd-sync-failure.yaml: Investigate and fix sync failures

Dashboard Updates:
- POST /api/webhooks/alertmanager endpoint
- POST /api/workflows/{name}/complete endpoint
- Alerts create pending actions for visibility

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

workflows/incidents/node-issue-response.yaml

@@ -0,0 +1,108 @@
+name: node-issue-response
+description: Respond to node issues (NotReady, unreachable)
+version: "1.0"
+
+trigger:
+  - alert:
+      match:
+        alertname: KubeNodeNotReady
+  - alert:
+      match:
+        alertname: KubeNodeUnreachable
+  - manual: true
+    inputs:
+      - name: node
+        description: Node name
+        required: true
+
+defaults:
+  model: sonnet
+
+steps:
+  - name: identify-node
+    agent: k8s-diagnostician
+    model: haiku
+    task: |
+      Identify the affected node:
+      - Node: {{ inputs.node | default(alert.labels.node) }}
+
+      Get node details:
+      - Current conditions
+      - Last heartbeat time
+      - Kubelet status
+      - Resource capacity vs allocatable
+    output: node_info
+
+  - name: check-workloads
+    agent: k8s-diagnostician
+    model: haiku
+    task: |
+      List workloads on the affected node:
+      - Pods running on the node
+      - Any pods in Pending state due to node issues
+      - DaemonSets that should be on this node
+
+      Node: {{ steps.identify-node.output.node_name }}
+    output: workload_status
+
+  - name: check-metrics
+    agent: prometheus-analyst
+    model: haiku
+    task: |
+      Check node metrics history:
+      - CPU/memory usage trend before issue
+      - Network connectivity metrics
+      - Disk I/O and space
+      - Any anomalies in last hour
+
+      Node: {{ steps.identify-node.output.node_name }}
+    output: metrics_analysis
+
+  - name: diagnose-and-recommend
+    agent: k8s-orchestrator
+    model: sonnet
+    task: |
+      Analyze the node issue:
+
+      Evidence:
+      - Node info: {{ steps.identify-node.output }}
+      - Workloads: {{ steps.check-workloads.output }}
+      - Metrics: {{ steps.check-metrics.output }}
+
+      Determine:
+      1. Root cause (network, resource exhaustion, kubelet crash, hardware)
+      2. Impact (number of affected pods, critical workloads)
+      3. Recovery options
+
+      For Pi cluster context:
+      - Pi 5 nodes: Can handle more recovery actions
+      - Pi 3 node: Be conservative, limited resources
+
+      Recommend actions with risk classification.
+    output: diagnosis
+
+  - name: safe-actions
+    condition: "{{ steps.diagnose-and-recommend.output.has_safe_action }}"
+    agent: k8s-diagnostician
+    model: haiku
+    task: |
+      Execute safe recovery actions:
+      - Attempt to reschedule affected pods
+      - Check if node recovers on its own
+
+      Do NOT:
+      - Drain the node (requires confirmation)
+      - Cordon the node (requires confirmation)
+    output: recovery_result
+
+outputs:
+  - diagnosis
+  - recovery_result
+
+notifications:
+  on_complete:
+    summary: |
+      Node issue response for {{ steps.identify-node.output.node_name }}:
+      - Status: {{ steps.diagnose-and-recommend.output.node_status }}
+      - Root cause: {{ steps.diagnose-and-recommend.output.root_cause }}
+      - Affected pods: {{ steps.check-workloads.output.pod_count }}