feat: Batch operations + System status endpoints

[santoshkumarradha]

Summary

Agents making multiple API calls waste time on network roundtrips. Batch operations let them do up to 20 calls in a single request. System status gives a quick health overview.

Solution

Batch Operations

POST /api/v1/agentic/batch — Execute multiple API operations concurrently.

{
    "operations": [
        {"id": "op1", "method": "GET", "path": "/api/v1/nodes"},
        {"id": "op2", "method": "GET", "path": "/api/v1/executions/exec_123"}
    ]
}

Each operation runs as a sub-request against the router. Max 20 operations per batch. Results returned with per-operation status codes.

System Status

GET /api/v1/agentic/status — Quick system health overview:

• Storage health
• Agent counts (total, active)
• Execution stats (last 24h by status)
• Server info (uptime, Go version, goroutine count)

Depends On

• # (for error helpers)

Files

• New: internal/handlers/agentic/batch.go
• New: internal/handlers/agentic/status.go
• Modify: internal/server/server.go — Register routes

Acceptance Criteria

• Batch executes up to 20 operations concurrently
• Batch returns per-operation status codes
• Batch rejects > 20 operations
• Status returns agent counts and execution stats
• Both require API key authentication

[santoshkumarradha]

Implemented in feat/agentic-api branch (commit 80e7920). PR #283.

Files: internal/handlers/agentic/batch.go, status.go