## Goal Beta scope per [`@phikai`](https://gitlab.com/groups/gitlab-org/-/work_items/22675#note_3562765776): *"Remove the current settings for setting this up and switch to flow"*. DAP reviewer assignment currently has two config surfaces. Remove the project setting so the only setup path is the standard one: enable the **Recommend Reviewers** flow, then create a trigger in **Automate > Triggers** on **Merge request > Marked ready**. The `merge_request_ready` event and its worker (`Ai::Catalog::Flows::ExecuteMergeRequestReadyWorkflowTriggersWorker`) already exist, and the trigger UI already offers it as the **Marked ready** action of the consolidated **Merge request** event. But the trigger path does not yet carry everything the flow needs, so the gaps below must close **before** the setting is removed. Note that the trigger path is **already user-reachable today**: neither the trigger worker nor the Recommend Reviewers catalog item is gated by `dap_powered_recommend_reviewers`, so any group with beta flows enabled can create the trigger now and get runs with no `reviewer_data` ([#607673](https://gitlab.com/gitlab-org/gitlab/-/work_items/607673)). Phase A is therefore fixing a live defect, not just reaching parity. ## Phases | Phase | Scope | Risk | |---|---|---| | **A** | Close the trigger-path gaps. No new user-visible surface. | Revertible by MR revert; bespoke path untouched | | **B** | Remove the `dap_powered` setting from UI and API. Update docs. | Revertible by MR revert; existing `dap_powered` rows keep working either way | | **C** | Reset existing `reviewer_assignment_strategy = dap_powered` rows. | Rollback is a data restore | | **D** | Delete the bespoke code path. | Low | Phase C is gated on Phase A being verified end to end, because that is the point rollback stops being a simple code revert. ## Known Beta limitation `MergeRequests::ReadyEvent` is only published on a draft > ready transition. The bespoke path also fires for merge requests opened non-draft, once diffs land. Migrating loses that coverage until the `merge_request_created` trigger exists, which `@phikai` scoped to GA. This must be stated in the docs rather than discovered by users. ## Out of scope - `merge_request_created` trigger, a GA requirement: [#592452](https://gitlab.com/gitlab-org/gitlab/-/work_items/592452), [!242698](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/242698) - Suggest vs. assign: [#605889](https://gitlab.com/gitlab-org/gitlab/-/work_items/605889) - Billing for trigger-driven runs — a GA requirement per the same [`@phikai` note](https://gitlab.com/groups/gitlab-org/-/work_items/22675#note_3562765776) ## Acceptance criteria Carried over from [#603494](https://gitlab.com/gitlab-org/gitlab/-/work_items/603494). - [ ] DAP Reviewer Assignment is configured and executed via the DAP Trigger platform, with no bespoke trigger infrastructure remaining - [ ] Users can configure the flow through **Automate > Triggers** using a standard event type - [ ] The configuration experience is consistent with how other DAP flows are configured - [ ] The bespoke trigger code introduced in [&20711](https://gitlab.com/groups/gitlab-org/-/work_items/20711) is removed