feat: Add Ops Dashboard API endpoints

[dsactivi-2]

Summary

• Adds new /api/ops/* endpoints for the Ops Dashboard
• Provides unified event stream and task history with filtering

New Endpoints

Endpoint	Auth	Description
GET /api/ops/events	User	Unified event stream (tasks + audit)
GET /api/ops/tasks/history	User	Task history with duration & audit data
GET /api/ops/stats	Admin	Aggregated statistics

Query Parameters

Events:

• since - ISO timestamp (default: 24h ago)
• limit - max events (default: 100, max: 500)
• agentId - filter by agent
• type - filter by event type

Tasks History:

• limit - max tasks (default: 50, max: 200)
• status - filter by status
• assignee - filter by agent
• includeAudit - include audit entries

Test plan

• TypeScript compiles without errors
• Endpoints tested with curl
• Deployed to server and verified

🤖 Generated with Claude Code

[github-actions]

@sentry review

[sentry]

Bug: Filtering by agentId on the /api/ops/events endpoint is non-functional because entry.agent is always undefined, as the audit_entries table lacks an agent column.
_{Severity: HIGH | Confidence: High}

🔍 Detailed Analysis

The /api/ops/events endpoint attempts to filter audit decision events by agentId. This logic relies on the entry.agent property, which is sourced from the audit_entries database table. However, the audit_entries table schema does not include an agent column, causing entry.agent to always be undefined. As a result, the filtering condition entry.agent && entry.agent !== agentId is never met, and the feature fails silently, returning unfiltered results. Additionally, the agentId field in the response for these events is always undefined.

💡 Suggested Fix

Refactor the code to use the newer db.audit.list() function, which queries the audit_events table that correctly includes an agent_id. Alternatively, add an agent column to the audit_entries table and ensure it is populated when entries are created.

🤖 Prompt for AI Agent

Review the code at the location below. A potential bug has been identified by an AI
agent.
Verify if this is a real issue. If it is, propose a fix; if not, explain why it's not
valid.

Location: src/api/ops.ts#L149-L156

Potential issue: The `/api/ops/events` endpoint attempts to filter audit decision events
by `agentId`. This logic relies on the `entry.agent` property, which is sourced from the
`audit_entries` database table. However, the `audit_entries` table schema does not
include an `agent` column, causing `entry.agent` to always be `undefined`. As a result,
the filtering condition `entry.agent && entry.agent !== agentId` is never met, and the
feature fails silently, returning unfiltered results. Additionally, the `agentId` field
in the response for these events is always `undefined`.

_{Did we get this right? 👍 / 👎 to inform future reviews.
Reference ID: 507408}