Count developer/v1 sessions in the DAP Impact Developer panels

What does this MR do and why?

The Work tab of the DAP Impact dashboard undercounts Developer sessions. This MR fixes the filter and the status tiles in ee/lib/gitlab/analytics/dashboards/system/dap_impact.yaml.

Six Developer panels in "Capability outcomes" filtered flowType = "software_development". That is the legacy built-in IDE flow type. The Developer flow is developer/v1. On production for gitlab-org over the last 30 days, developer/v1 has 97,277 sessions and software_development has 408.

The status tiles also showed only finished, paused, stopped and failed. 42,920 of the developer/v1 sessions are input_required, so most sessions were invisible.

Changes:

• All eight Developer panels, the six existing ones and the two new tiles, filter developer/v1.
• The "Agentic Developer sessions" tile counts every status.
• New "Awaiting input" tile covers input_required, plan_approval_required and tool_call_approval_required.
• New "In progress" tile covers created and running.
• The tile row is now six tiles of width 2.
• The over-time line chart gains matching "Awaiting input" and "In progress" series via totalCount(status=[...]).
• Failed tooltip now says it includes stuck-session timeouts and infrastructure failures.
• The over-time tooltip lists all six series.
• "Reviews published" and "With comments" tooltips say the count includes retried and failed publish attempts.

Only developer/v1 counts as Developer. Over the last 90 days on gitlab-org the other spellings are negligible: software_development 1,022 sessions, software_development/v1 54, developer/v2-local 56, and no sessions stored under the display name Developer. The legacy IDE flow stays out; if product wants it counted the filter becomes flowType in ("developer/v1", "software_development").

References

• Resolves https://gitlab.com/gitlab-org/gitlab/-/work_items/631556
• UAT epic https://gitlab.com/groups/gitlab-org/-/work_items/23429
• Related https://gitlab.com/gitlab-org/gitlab/-/work_items/631549
• Related https://gitlab.com/gitlab-org/gitlab/-/work_items/631550

Screenshots or screen recordings

GDK on master rendering live production responses for gitlab-org, last 30 days. The six status tiles add up to the sessions total: 3,096 + 0 + 43,832 + 155 + 1,405 + 50,338 = 98,826.

How to set up and validate locally

1. Check that the YAML loads through the Analytics::CustomDashboards::SystemDashboardsLoader schema validation.
2. Run bundle exec rspec ee/spec/features/explore/system_dashboards_spec.rb -e "Work tab is selected".
3. Run bundle exec rspec ee/spec/lib/gitlab/analytics/dashboards/system/dap_impact_spec.rb. It pins the developer/v1 filter and checks that the status tiles partition every workflow status, so a new status breaks the build instead of the sum.
4. Open the DAP Impact dashboard and go to the Work tab.
5. Check that the six status tiles sum to the "Agentic Developer sessions" total.

MR acceptance checklist

Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.