Epic: Agent Lifecycle Governance

Overview

Comprehensive overhaul of agent creation, lifecycle management, and registry in the augment plugin. Ensures all agents follow a governed lifecycle pipeline (draft → review → staging → production → retired) regardless of creation method.

Research Findings

See agent-lifecycle-research.md for full details including:

• Complete Kagenti API surface map (35+ endpoints)
• Live cluster exploration results
• As-is vs to-be user journey maps
• 7 identified bugs with priority rankings

PRs

P0 (Critical)

• PR #3205 - Add DELETE route + UI button for draft agents
• PR #3206 - Auto-create chatAgents entry on Kagenti agent deploy
• PR 3 - Fix non-clickable agents in registry (deprioritized, partially addressed by PR #3206)

P1 (Important)

• PR #3207 - Enforce lifecycle validation on publish/unpublish routes
• PR 5 - Add createdBy field and scope My Agents tab to current user
• PR 7 - Wire syncWorkflowToChatAgents on workflow publish

P2 (Nice-to-have)

• PR 8 - Update docsContent.ts from 3-stage to 5-stage lifecycle model
• PR 9 - Research RHDH orchestrator workflows for approval automation
• PR 10 - Remove or wire orphan AgentCreationWizard component

Key Findings from Cluster Exploration

1. Kagenti API has DELETE endpoint (DELETE /api/v1/agents/{ns}/{name}) - was not wired to chatAgents cleanup
2. Two types of agents: API-managed (via backend) and K8s-native (via Helm/kubectl) - only API-managed show in backend list
3. Auth: Keycloak OIDC with 60s token TTL, both public and confidential clients
4. RHDH Orchestrator (SonataFlow) is deployed on cluster - potential for approval workflow automation

Read workspaces/augment/docs/agent-lifecycle-research.md first, then review the checked and unchecked PR items in this epic and the augment plugin's agent registry and lifecycle routes. Done means the selected lifecycle gaps are addressed across the listed creation methods, registry behavior, validation, synchronization, and documentation, with the relevant checks passing.