Stop counting the agent configuration file as required

What does this MR do and why?

The Duo readiness card in project settings counted the agent configuration file (.gitlab/duo/agent-config.yml) as a required step. A project without the file showed "1 step left" and a state line that said flows were not set up. But flows run without the file. They fall back to a generic image that may lack the project toolchain.

The card now counts four required steps: Agent Platform, GitLab Duo, flow execution, and a CI/CD runner. A project without the file now reads "All steps complete" when those four are in place. The agent configuration file row moves into the second group, as its first row. That group is now called "Recommended" and shows whenever the Agent Platform is on. The row stays a to-do while flow execution is off, and the Generate button stays hidden. The absent-state copy is now one sentence: "Add a config file so flows run with this project's toolchain."

The heading, subtitle and row copy are proposals. UX confirms them on this MR. The group card is not touched. No new flag is involved. The card is behind duo_agent_readiness_settings, which is on for everyone, so the change reaches every project on GitLab.com on merge.

References

Screenshots or screen recordings

Before After
632277-card-before 632277-card-generate
Flow execution off
632277-recommended-flows-off

How to set up and validate locally

  1. Turn on the duo_agent_readiness_settings flag for your user. In the Rails console, run Feature.enable(:duo_agent_readiness_settings).
  2. Open a project without .gitlab/duo/agent-config.yml and without an open merge request that adds it. Go to Settings > General > GitLab Duo and expand the card.
  3. Set up the Agent Platform, GitLab Duo, flow execution and a runner. The header reads "All steps complete" and "Ready. Flows can run in this project." The Recommended group lists the agent configuration file first, with Generate.
  4. Turn Flow execution off. You do not need to save. The header reads "1 step left". The row keeps its to-do icon and copy. Generate is hidden.

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