[Story]: Distinguish AI-generated vs PM-created onboarding steps (origin marker)

[adoLime]

User Story

As a new project member, I want to see at a glance which onboarding steps were AI-generated and which were added by my PM, so that I understand the origin of each task and can trust or question them accordingly.

As a PM, I want AI-generated steps and my own custom steps to be visually distinguishable in the PM view, so that I can quickly tell what the AI suggested vs. what I added manually, and edit accordingly.

Context & Motivation

• Type: Functional (Onboarding)
• Parent epic: 06 EPIC - Onboarding Journey & Digital Adoption #55 (06 EPIC – Onboarding Journey & Digital Adoption)
• Teams: team:backend (origin field in data model + API), team:frontend (visual marker in user + PM views), team:ai (stamp origin at generation)
• Source: Customer request (Niklas) after Sprint Review 2026-07-15
• Related: [Story]: Onboarding path generator v0 (AI-generated from artifacts) #163 (AI path generator), [Story]: Custom steps added by Project Lead #111 (PM custom steps), [Story]: Onboarding checklist data model #109 (onboarding data model), [Feature]: Rework Onboarding Step #214 (step rework), [Story]: PM view — onboarding status across team members #180 (PM view), [Story]: PM/Admin reorders onboarding steps #185 (reorder — marker must survive reorder), [Story]: RBAC with Admin / User separation #93 (RBAC).

Dependencies

• Depends on: [Story]: Onboarding checklist data model #109 (data model needs an origin/source field), [Story]: Onboarding path generator v0 (AI-generated from artifacts) #163 (generation must stamp origin), [Story]: Custom steps added by Project Lead #111 (custom-step endpoint must stamp origin).

Acceptance Criteria

User view (new project member)

• Given the user (onboardee) view, when a step is displayed, then AI-generated steps carry a visible "AI" badge/icon and are clearly distinct from PM-added steps.
• Marker labels are i18n'd (en/de); empty / loading / error states handled.

PM view

• Given the PM view, when steps are listed, then AI vs PM origins are distinguishable (badge/colour), so the PM sees AI suggestions vs. their own additions at a glance.

Data model & behaviour

• Every onboarding step carries an explicit origin value: ai (generated via [Story]: Onboarding path generator v0 (AI-generated from artifacts) #163) or pm (added by PM/Admin via [Story]: Custom steps added by Project Lead #111).
• Given a step, when inspected via API, then its origin is returned. Only PM/Admin (per [Story]: RBAC with Admin / User separation #93) or a re-generation ([Story]: Onboarding path generator v0 (AI-generated from artifacts) #163) may change origin; regular users cannot.
• Given a PM edits the content of an AI-generated step, when saved, then origin stays ai and an edited_by_pm flag is set (AI origin stays transparent); the flag is visible in the PM view.
• Given a PM reorders ([Story]: PM/Admin reorders onboarding steps #185) or edits a step, when the change is saved, then the origin marker of each step is preserved.

Sub-Tasks (by team)

• Backend — add origin/source field (+ edited_by_pm) to onboarding_step ([Story]: Onboarding checklist data model #109 schema); expose in step DTOs; enforce immutability except PM/Admin. AI generation ([Story]: Onboarding path generator v0 (AI-generated from artifacts) #163) stamps ai; custom-step endpoint ([Story]: Custom steps added by Project Lead #111) stamps pm.
• Frontend — "AI" / "PM" badge in the user onboarding view and in the PM path / team view ([Story]: PM view — onboarding status across team members #180); optional filter toggle; show edited_by_pm in PM view.
• AI — when generating a path via [Story]: Onboarding path generator v0 (AI-generated from artifacts) #163, set origin = ai on every produced step.
• QA — tests for origin stamping, immutability, marker survival across reorder/edit, and view rendering.