## Problem Projects fail to get value from the Duo Agent Platform because nothing tells a maintainer whether their repository is ready for it. Setup spans instruction files, an execution environment, flow activation, indexing, and runners, and there is no single place that shows a project's state, what matters most, or what the maintainer can act on. This is the most common adoption blocker we see in the field: DAP gets introduced before the repo and environment are ready, flows underperform or fail, and trust erodes. The existing diagnostics each cover one slice. The admin health check covers instance connectivity, license, and runners. `gitlab:duo:verify_setup` covers group, project, and flow config. The CLI `/doctor` covers the local client and auth. None of them assesses repository readiness, and none is aimed at a project maintainer. ## Outcome A persistent readiness surface under Automate that: - shows the project's current state across the configuration areas DAP depends on, - leads with the single highest-impact next step instead of a checklist, - turns each gap into a one-click fix (a draft MR or a direct link), and - is honest about what a maintainer can fix versus what needs a group owner or administrator. ## Principles 1. Diagnosis first, action second. The surface is a health check that links to fixes. It is not a wizard that runs flows. Initializers are how you close a gap, not the headline. 2. Stateful and returnable. It reflects live state on every visit, not a one-time "did you run onboarding?" flag. 3. Priority-led, not a completion score. No percentage and no "X of Y done." Items rank as start-here, recommended, or optional, weighted to the project, so things a project does not need never read as gaps. 4. Compose, do not duplicate. Surface the admin health check and `verify_setup` results through a maintainer lens instead of rebuilding them, including the cases a maintainer cannot fix. ## Scope Two things: a readiness surface under Automate that shows a project's state across the areas DAP depends on and leads with the highest-impact next step, and the one-click functionality behind it that closes each gap (instruction and config files, CI improvements, file protection, and enabling supporting capabilities). The surface composes existing diagnostics (admin health check, verify_setup) through a maintainer lens, including an honest handoff for prerequisites a maintainer cannot fix, such as a missing runner. ## Non-goals - Replacing the admin health check, `verify_setup`, or CLI `/doctor`. This composes with them. - Instance or group administration. This is a project-scoped, maintainer-facing surface that can link out to admin-owned settings. - A scored or graded repository rating. See principle 3. **Design spec:** https://pajamas-prototyping-kit-fe3fa0.gitlab.io/#/duo-onboarding-v2