Prepare readiness rows and flow picker for group settings

Mike Wronskirequested to merge
629953-readiness-row-and-picker into master

What does this MR do and why?

This MR prepares shared frontend components for a new group readiness section. It makes no visible change by itself.

Group Owners need one view of whether their group can run GitLab Duo agents and flows. A later MR will build that view from the same components as the project readiness card. This MR extends those components first, so the later MR can stay small.

Changes in this MR:

  1. duo_readiness_row.vue can render without a status icon. It can also show a disabled state, with muted text and a disabled icon, for a setting whose parent is off. Its control still uses native disabled behaviour.
  2. The row gains a note slot for a third line of text, such as "Inherited: On by default".
  3. A new duo_readiness_section.vue component wraps a heading, a subtitle, and a bordered list of rows.
  4. The foundational flow picker moves out of duo_flow_settings.vue into its own foundational_flow_picker.vue component. It keeps its Code Review consent dialog and its remount-on-cancel behaviour, so two settings pages can mount it.
  5. The foundational agents settings component gains a showDefaultToggle prop, default true, so a page can show only the per-agent availability table.
  6. The settings entry point now reads six new dataset keys, sent by a later MR:
    • the owner's Agent Platform value and settings path
    • the owner's foundational agents value
    • the inherited GitLab Duo availability value and its source
    • the root ancestor name

References

Part of epic gitlab-org#23651. Implements #629953. Stacked on !257287 (merged).

Screenshots or screen recordings

No user-facing change.

How to set up and validate locally

  1. Run the Jest specs for duo_readiness_row, duo_readiness_section, foundational_flow_picker, the foundational agents settings component, and the settings entry point.
  2. Open a project's GitLab Duo settings card. Confirm it looks the same as before this change.
  3. Open a group's GitLab Duo flow settings. Confirm the flow picker still works the same way, including the consent dialog and cancel behaviour.

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