Enable duo_agent_readiness_settings by default

Mike Wronskirequested to merge
607567-default-enable-duo-agent-readiness-settings into master

What does this MR do and why?

The duo_agent_readiness_settings flag gates a card in Project Settings > General > GitLab Duo. The card shows which steps still stand between a maintainer and running agents and flows in one project.

The flag moved to beta on 2026-09-22. GitLab team members used the card from 2026-09-23 to 2026-10-06. They gave one feedback item: the agent configuration file should not count as required. The fix is approved and merging. We received no bug reports. GitLab.com has the flag on for everyone since 2026-10-06. Product and UI strings have sign-off.

The flag is now on by default in ee/config/feature_flags/beta/duo_agent_readiness_settings.yml. It also changes the two docs history entries in doc/user/duo_agent_platform/flows/execution/_index.md to "Enabled by default.", because the flag was introduced and enabled in the same release. There is no code change. GitLab.com does not change, and self-managed and Dedicated instances get the card in 19.5.

GitLab.com can roll back with a ChatOps command that sets the flag to false. The card only moves existing project settings, so the previous page returns at once. We plan to remove the flag in 19.6.

References

Screenshots or screen recordings

No visual change. The merge request at !259925 (merged) shows the card before and after the latest copy change.

How to set up and validate locally

  1. In the Rails console, remove any local override so the default applies: Feature.remove(:duo_agent_readiness_settings).
  2. Open a project where you are a Maintainer. Go to Settings > General > GitLab Duo and expand the section. The readiness card shows at the top.
  3. Run Feature.disable(:duo_agent_readiness_settings) and reload. The section shows the previous flat list of Duo settings.

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