Draft: Fix AI Catalog private-item alert copy to remove top-level group mention

Jannik Lehmannrequested to merge
duo/fix/598099-ai-catalog-private-item-alert-copy into master

What does this MR do and why?

Fixes the info alert shown in the AI Catalog consumer modal for private items. The previous copy incorrectly stated that private items could be enabled in the item's top-level group. Groups do not expose an Enable action for AI Catalog items, making this copy misleading and causing users to hunt for a UI that doesn't exist.

Before:

This %{itemType} is private and can only be enabled in the project it was created in or its top-level group. Duplicate the agent to use the same configuration in other projects.

After:

This %{itemType} is private and can only be enabled in its managing project: %{projectName}. Duplicate the %{itemType} to use the same configuration in other projects.

Changes:

  • Removes the incorrect "top-level group" enablement path
  • Adds the managing project name (%{projectName}) so users know exactly which project they need access to
  • Uses consistent %{itemType} interpolation in the duplicate nudge (instead of hardcoded "agent")
  • Updates locale/gitlab.pot with the new msgid
  • Removes the old orphaned msgid from all translated .po files
  • Adds a spec assertion to verify the managing project name is rendered in the alert

References

Screenshots or screen recordings

Before After
Alert mentions "top-level group" (non-existent UI path) Alert shows managing project name

How to set up and validate locally

  1. Navigate to the AI Catalog (Explore or group page)
  2. Find a private AI Catalog item
  3. Click Enable — the modal should show the updated alert text with the managing project name

MR acceptance checklist

Evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.

Merge request reports