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

What does this MR do and why?

Fix the info alert shown in the AI Catalog consumer modal for private items. The previous copy incorrectly stated that a private item could be enabled in its "top-level group", but group-level Enable does not exist. This was misleading and could cause users to hunt for a UI that isn't there.

Old copy:

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.

New copy:

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" mention
  • Names the managing project explicitly using %{projectName} interpolation (already available via item.project.nameWithNamespace)
  • Uses consistent %{itemType} interpolation in the duplicate nudge (instead of hardcoded "agent")
  • Updates locale/gitlab.pot and all 26 translated .po files (old translations cleared; translators will pick up the new string in the next cycle)
  • Adds a spec assertion verifying the managing project name is rendered in the alert

References

Screenshots or screen recordings

Before After
"...can only be enabled in the project it was created in or its top-level group. Duplicate the agent..." "...can only be enabled in its managing project: Group-1 / Project 1. Duplicate the flow..."

How to set up and validate locally

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

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

Loading
Loading