As a Rovo administrator,
I want to have better governance and management of Rovo agents,
So that agents are used correctly and consistently across the organisation, and users can easily find and use the right agent for their needs.

Acceptance Criteria:

• The system allows agents to be designated as either organisation-approved or personal.

• Personal agents are only visible to the user who created them.

• Organisation-approved agents are accessible to all relevant users.

• Agent usage statistics are available, showing who is using each agent and how often.

• Agents must have unique names to avoid confusion (e.g., no duplicate "Priority Assessor" agents).

• There is a clear process for managing the agent lifecycle, including criteria for when agents should be cleaned up, based on analytics.

• Admins can delete or modify agents created by other users, especially if an agent is inappropriate.

Rationale:
Currently, anyone can create Rovo agents, which has led to a proliferation of agents with similar names and unclear purposes. This causes confusion and inconsistent results, as some agents appear to be organisation-approved but are actually personal. These enhancements will improve agent governance, making it easier for users to find the right agent and for admins to manage the agent ecosystem effectively.