[Story]: Handover dossier with review & process export

[adoLime]

User Story

As a PM, I want a versioned dossier based on our template, assembled from the interview + corpus and accepted by the receiver or by me, so that the knowledge transfer is complete and exportable.

Context & Motivation

• Type: Functional
• Parent epic: 10 EPIC - Quality Radar & Technical Debt Management #60 (10 EPIC – Quality Radar & Technical Debt Management / Knowledge Retention & Handover)
• Teams: team:ai, team:backend, team:frontend
• Dev guide: docs/handover-dev-guide-phase1-en.md § 4 (Story D) · Concept: docs/handover-feature-konzept.md § 7
• Template: docs/handover-tamplate.md (metadata + 12 sections)
• Reusable: orientation-packet assembly pattern, attestation pattern, MessageMarkdown + ArtifactViewerDrawer

Acceptance Criteria

• 12 fixed sections per handover-tamplate.md; section 3 (open tasks) with an optional receiver per task
• Assembly from interview transcript + corpus; ungrounded sections → skipped, never invented; transcript vs. corpus provenance kept separate
• Review: DRAFT → IN_REVIEW → FINAL or RETURNED with a reason (attestation pattern); attester = receiver, otherwise PM
• Process export as Markdown: dossier + interview transcript + Q&A + checklist state, including citations; audited via HandoverExportRun
• Export is re-ingest-capable (stored in the wiki → queryable again)

Sub-Tasks (by team)

AI

• dossier.py (assembly following the orientation-packet pattern) + POST /handover/dossier (SSE)
• Grounding gates: ungrounded sections → skipped; citation validation; ScriptedLLMClient tests

Backend

• HandoverDocument (version, status, 12 sections, citations) + HandoverTaskItem (receiverId?) entities
• Review workflow endpoints (submit, review ACCEPTED/RETURNED)
• Export endpoint + HandoverExportRun audit; only PII-redacted transcripts in exports
• Tests incl. review state machine, export completeness

Frontend

• Dossier view (MessageMarkdown + ArtifactViewerDrawer, collapsible evidence)
• Review UI (ACCEPT / RETURN with reason), export download

Dependencies

A → B → C → D (D needs C — the interview transcript). Final MVP story; closes the handover loop via export + re-ingest.