[Story] Sprint 6: Usable end-to-end — simplified ingestion, complete onboarding & first demoable deployment (2026-07-29 to 2026-08-12)

[adoLime]

Sprint Goal

Sprint 5 made multi-source ingestion and PM/project setup work; Sprint 6 turns that into something usable and demoable end-to-end. Connecting a GitHub repo becomes a single action (sources enabled-by-default, org/user discovery inside the create-project wizard), the Jira connector reaches the frontend, and onboarding gets its finishing touches — including the AI Buddy as a conversational alternative to the static onboarding checklist (Sprint 5 spike integration). A seeded, non-empty deployment lets us demo the whole flow without manual setup. Capacity is still reduced this sprint, so scope is priority-ordered.

In scope

A. Simplified, complete GitHub & Jira ingestion

• Connect sources enabled-by-default — connecting a repo implies "ingest from it" (Backend/Frontend) [Story]: Connect sources enabled-by-default (simplify connect → ingest workflow) #265 — 🌋 Urgent
• Bring GitHub org/user discovery into the Create-Project wizard (Frontend) Bring GitHub org/user discovery into Create-Project wizard #266 — 🌋 Urgent
• Ingest GitHub organization-level metadata — org profile, members, teams (Backend/Frontend/AI) [Story]: Ingest GitHub organization-level metadata (org profile, members, teams) #261 — 🌋 Urgent
• Jira connector on the frontend (Frontend) [Feature]: Jira connector on frontend #262 — 🌋 Urgent
• Link existing sources to additional projects without re-ingesting (Backend/Frontend/AI) [Story]: Link existing sources to additional projects without re-ingesting #257 — 🏕️ Medium

B. Onboarding — paths, steps & the AI Buddy

• Custom steps added by Project Lead (Backend/Frontend) [Story]: Custom steps added by Project Lead #111 — 🌋 Urgent
• Onboarding path blueprint changes (Backend) 05 EPIC - Agent Orchestration & Workflow Actions #54 — 🏔️ High
• Highlight passed knowledge checks visibly (Frontend) [Story]: Highlight passed knowledge checks visibly #258 — 🏕️ Medium
• Adjust phase knowledge checks to review feedback (Backend/Frontend) [Feature]: Adjust phase knowledge checks to review feedback #263 — 🏕️ Medium
• Integrate the AI Buddy (Sprint 5 spike) as an alternative to the sequential onboarding path (AI/Frontend/Backend) — no tracking issue yet, to be created

C. Knowledge base & chat

• Render artifact summaries as proper Markdown instead of plain text (Frontend/AI) [Story]: Render artifact summaries as proper Markdown instead of plain text #259 — 🌋 Urgent
• Source filter in the chat (Backend/Frontend/AI) [Story]: Source filter in the chat #104 — 🏔️ High

D. PM/Admin UX

• PM dashboard — project list & project drilldown (project → members) (Backend/Frontend) [Story]: PM dashboard — project list & project drilldown (project → members) #239 — 🌋 Urgent
• Visual save-button state for unsaved changes (Frontend) [Story]: Visual save-button state for unsaved changes #255 — 🌋 Urgent
• Dedicated role-management view (PM/Admin) reachable from settings (Frontend) [Story]: Dedicated role-management view (PM/Admin) reachable from settings #243 — 🏔️ High

E. Demoable deployment

• Testdaten für Deployment automatisiert bereitstellen (QA) [Demo] Testdaten für Deployment automatisiert bereitstellen #264 — 🌋 Urgent

Priority / capacity note

Reduced capacity this sprint (carry-over from the Klausur phase). If scope has to slip, land in this order: #265 → #266 → #264 → #259 → #261 → #262 → #239 → #255 → #111 → #54 → #104 → #243 → #257 → #258 → #263.

Demo outcomes (Sprint Review 2026-08-12)

1. As an Admin, create a project and pick GitHub repos from an org via discovery in the same wizard; the selected repos are connected and ingest automatically (no extra enable step). [[Story]: Connect sources enabled-by-default (simplify connect → ingest workflow) #265 + Bring GitHub org/user discovery into Create-Project wizard #266]
2. As a PM/Admin, connect a Jira source from the frontend and see Jira artifacts in the knowledge base. [[Feature]: Jira connector on frontend #262]
3. As a Project Lead, add a custom onboarding step to a path; the step appears in the assigned user's onboarding. [[Story]: Custom steps added by Project Lead #111]
4. As a new joiner, choose the AI Buddy instead of the static onboarding checklist and get guided through onboarding conversationally. [Buddy integration — TBD]
5. As a user, complete a knowledge check and see the passed state highlighted; phase feedback reflects the check. [[Story]: Highlight passed knowledge checks visibly #258 + [Feature]: Adjust phase knowledge checks to review feedback #263]
6. In chat, filter answers by source system and read artifact summaries rendered as Markdown. [[Story]: Source filter in the chat #104 + [Story]: Render artifact summaries as proper Markdown instead of plain text #259]
7. As a PM, open the dashboard, drill into a project and its members. [[Story]: PM dashboard — project list & project drilldown (project → members) #239]
8. On the seeded deployment, run the full demo (projects, sources, onboarding, chat) without manual data entry. [[Demo] Testdaten für Deployment automatisiert bereitstellen #264]