Release AI Catalog sub-agent references as a beta

What does this MR do and why?

Releases AI Catalog sub-agent references (include in a custom flow) as a beta.

  • The ai_catalog_flow_agent_references flag moves from wip to beta. The flag stays off by default, and the rollout on GitLab.com uses chatops.
  • The security review in #632224 must be complete before the flag is on by default.
  • ai_catalog_flow_agent_references is in Gitlab::Llm::Utils::AiFeaturesCatalogue with maturity: :beta, and Gitlab::Llm::StageCheck maps it to the ai_catalog license.
  • A flow with include saves only when StageCheck.available? is true for the project. For a beta feature, that needs the instance setting for experiment and beta features and, on GitLab.com, the same setting on the top-level group.
  • The catalog_items endpoint uses the same check before it resolves sub-agents.
  • Flows without include do not change.
  • The docs mark include as a beta with a flag that is disabled by default.

Merge order

Blocked by !259499 (merged), because the docs change here edits the include section that !259499 (merged) adds. This MR targets the !259499 (merged) branch. When !259499 (merged) merges, GitLab changes the target to master.

References

Screenshots or screen recordings

Not applicable. Backend only.

How to set up and validate locally

  1. Turn the flag on: Feature.enable(:ai_catalog_flow_agent_references)

  2. Create an agent in the AI Catalog, release version 1.0.0, and note its item ID.

  3. Turn the setting off: ApplicationSetting.current.update!(instance_level_ai_beta_features_enabled: false)

  4. Create a custom flow in the same project and add this to the definition:

    include:
      - source: ai-catalog
        item_type: agent
        item_id: "<id>"
        version: "1.0.0"
  5. The save fails with "Referencing AI Catalog items with include needs experiment and beta features turned on".

  6. Turn the setting on (true in step 3) and save again. The save succeeds.

  7. With the setting off, save a flow without include. The save succeeds.

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.

Edited by Angus Ryer

Merge request reports

Loading
Loading