As a platform user I want to onboard and manage Certifai targets from a Next.js app inside breakpilot-platform so that onboarding lives in the
platform instead of the standalone Dioxus dashboard.
Part of #186. This is a full onboarding-design revisit, not a port — rethink
the wizard and flows.
Acceptance criteria
Next.js app in breakpilot-platform driving the agent API
(targets / artifacts / scans / applicable-scans).
Feature parity with the current wizard (multi-artifact, PLC formats, opt-in
scans, live-URL schemes) on top of a redesigned UX.
A defined path to retire the Dioxus compliance-dashboard onboarding.
**As a** platform user **I want** to onboard and manage Certifai targets from a
**Next.js** app inside breakpilot-platform **so that** onboarding lives in the
platform instead of the standalone Dioxus dashboard.
Part of #186. This is a full **onboarding-design revisit, not a port** — rethink
the wizard and flows.
## Acceptance criteria
- [ ] Next.js app in breakpilot-platform driving the agent API
(targets / artifacts / scans / applicable-scans).
- [ ] Feature parity with the current wizard (multi-artifact, PLC formats, opt-in
scans, live-URL schemes) on top of a redesigned UX.
- [ ] A defined path to retire the Dioxus compliance-dashboard onboarding.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
As a platform user I want to onboard and manage Certifai targets from a
Next.js app inside breakpilot-platform so that onboarding lives in the
platform instead of the standalone Dioxus dashboard.
Part of #186. This is a full onboarding-design revisit, not a port — rethink
the wizard and flows.
Acceptance criteria
(targets / artifacts / scans / applicable-scans).
scans, live-URL schemes) on top of a redesigned UX.