Enable ai_governance_mcp_server_activity by default for 19.4

Dheeraj Joshirequested to merge
djadmin/aigov-mcp-card-ff-beta into master

What and why

Turns the MCP servers card on for the 19.4 limited beta, as requested on #627998.

The card itself is already merged and has been dark behind a wip flag, so this is a flag flip plus its documentation, not new development.

Changes

  • Moves ai_governance_mcp_server_activity.yml from wip/ to beta/, sets type: beta and default_enabled: true, and adds rollout_issue_url.
  • Updates push_frontend_feature_flag(:ai_governance_mcp_server_activity, ...) in both governance controllers from type: :wip to type: :beta. Feature::Definition#valid_usage! raises when the in-code type disagrees with the YAML, so these have to move together with the file.
  • Documents the card in doc/user/ai-governance/governance-dashboard.md, which previously covered four data cards and did not mention MCP servers.

Scope note

The card lists registered MCP servers and their status. It does not show per-server usage counts; that is tracked separately in #627996. The documentation says so explicitly rather than implying the card reports activity.

The agent tool calls card is unaffected and stays behind ai_governance_tool_calls, which is not yet on master.

Screenshots

Pending.

How to set up and validate locally

Feature.enable(:gitlab_duo_governance_settings)
Feature.enable(:ai_governance_dashboard)

Do not enable ai_governance_mcp_server_activity manually. With this branch checked out it is on by default.

  1. Open the group's GitLab Duo governance settings page on the dashboard tab.
  2. Confirm the MCP servers card renders below the other data cards.
  3. Hover or tab to a truncated server description and confirm the popover shows the full text.
  4. Run Feature.disable(:ai_governance_mcp_server_activity), reload, and confirm the card disappears.

References

MR acceptance checklist

Evaluate this MR against the MR acceptance checklist.

Edited by Dheeraj Joshi

Merge request reports