Incorrect Foundational Agents and Flows Settings values when DAP is disabled at the instance-level
## Description When DAP is disabled at the instance level, foundational agent and flow settings appear disabled in the UI but retain their backend values. This means if those settings were enabled before DAP was disabled, they remain enabled downstream. ## Steps to reproduce - On SM instance, go to Duo admin-level settings. - Ensure flow settings are enabled and then disable DAP. - Go to Duo settings for a top-level group - Observe the following: <table> <tr> <th>Expectation</th> <th>Reality</th> </tr> <tr> <td> ![Screenshot_2026-04-17_at_10.45.10_AM](/uploads/cf667d33fe9a09bdbbbeb5e37a1452b2/Screenshot_2026-04-17_at_10.45.10_AM.png){width="900" height="415"} Downstream flow settings should be disabled and locked </td> <td> ![Screenshot 2026-04-17 at 10.46.04 AM.png](/uploads/d051a93c925cf1d1be9b08e20a29a2ae/Screenshot_2026-04-17_at_10.46.04_AM.png){width="900" height="407"} Downstream flow settings (in this case top-level group) shows that flows are still enabled and unlocked. </td> </tr> </table> cc: @frwang1 @bastirehm
issue