Delete records for Deprecated Gilab Planner

Background

When GitLab Duo Planner was initially introduced, it was a custom agent that required users to explicitly add it to their projects through the AI agents catalog. This process created Ai::Catalog::ItemConsumer records in the database that persist even after the custom agent is deleted.

Problem

Duo Planner has since been migrated to a foundational agent, which is automatically visible to all users without requiring explicit addition to projects. This creates a problem for users who previously added the custom Planner agent—they now see two Duo Planner agents in their interface:

• The legacy custom agent (from the old ItemConsumer record)
• The new foundational agent

This duplication causes confusion and a poor user experience.

Proposed Solution

Delete the legacy Ai::Catalog::ItemConsumer records for the deprecated custom Planner agent (ID: 348) from the database. This will:

• Remove the duplicate Planner agent from affected users' interfaces
• Preserve chat history in a read-only state (no data loss)
• Leave users with only the foundational Planner agent visible

Impact: Currently 243 records need to be deleted (as of December 3rd, 2025).

User Impact

• Positive: Users will have a cleaner interface with only one Planner agent
• Minimal disruption: Historical chat conversations remain accessible in read-only mode
• No data loss: All previous interactions are preserved