Remove the standalone DAP onboarding page

Mike Wronskirequested to merge
607425-remove-the-standalone-dap-onboarding-page into master

What does this MR do and why?

This MR removes the standalone Automate > Onboarding page for the Duo Agent Platform (DAP).

The onboarding steps now show as a card in Settings > General > GitLab Duo. The card sits behind the duo_agent_readiness_settings feature flag. This flag stays off. This MR does not change it.

This MR:

  • Deletes the onboarding Vue page and its Jest specs.
  • Removes the automate_onboarding and automate_onboarding_setup routes, the setup_onboarding controller action, and the onboarding helpers.
  • Removes the Onboarding item from the AI sidebar menu and the /onboarding route from the Vue router.
  • Removes the duo_agent_onboarding feature flag and all checks of it. The flag was never enabled in any environment.
  • Adds an accessible name to the readiness card progress bar. The name reads "Agent setup progress: N of 5 steps complete". A maintainer asked for this during review of merge request !252535 (merged).
  • Regenerates locale/gitlab.pot, ee/app/assets/javascripts/lib/utils/path_helpers/project.js, and config/routing/gitlab_routes.json.

The shared backend code under Ai::Catalog::Onboarding stays in place. The only change is the removed flag check in RunService#initializers_enabled?. A follow-up MR collapses this backend into one service.

After this MR merges, close the rollout issue at #596695. Then run:

/chatops run feature delete duo_agent_onboarding --dev --pre --staging --staging-ref --production

User docs for the onboarding page were already removed in merge request !249697 (merged).

References

Screenshots or screen recordings

Not applicable. The removed page sat behind a disabled feature flag, so users saw no change. The new aria-label is not visible on screen.

How to set up and validate locally

  1. Enable the feature flag in a Rails console: 
    Feature.enable(:duo_agent_readiness_settings)
  2. Open a project. Go to Settings > General. Expand GitLab Duo.
  3. Inspect the progress bar element. Check for role="progressbar" and aria-label="Agent setup progress: N of 5 steps complete".
  4. Open the project's Automate section. Check the AI sidebar. It shows Agents, Flows, Triggers, and Sessions, and does not show Onboarding.
  5. Send POST /<project>/-/automate/onboarding/setup. Check that the response returns 404.

Note: GET /<project>/-/automate/onboarding still returns 200. The Automate single-page app catches every unknown sub-path and redirects to Sessions. This is existing behavior, not a new issue.

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.

This MR carries Changelog: other.

Merge request reports