[Tracking] Migration v4.0.5 Re-Crawl 2026-06-19 — Master-Issue

[Lionhunt3r]

Master-Tracking-Issue für die Ionic→Flutter Migration v4.0.5

Aktueller Stand

• Ionic-Version: v4.0.5 (HEAD b3ea25d, 2026-06-17)
• Re-Crawl-Datum: 2026-06-19
• Score: 57% (vs. 78% im veralteten Crawl auf v3.8.3)
• Gesamt-Findings: 315 (30 KRITISCH, 101 HOCH, 118 MITTEL, 66 NIEDRIG)
• Report: .claude/migration-crawl-report.md

Vorgeschichte

Der ursprüngliche Migration-Backlog (Issues #178-210) basierte auf Ionic v3.8.3. Das Ionic-Repo war 160 Commits hinten dran. Nach git pull und Re-Crawl mit v4.0.5 wurde klar:

• 8 komplett neue Pages (Dashboard, Bulk-Edit, Delete-Account, Files, Role-Permissions, Legal, App-Redirect, Login/Legal-Modal)
• 6 neue Cross-Cutting Services (Push, Audio, Files, Legal, RolePermission, Tracking)
• 10+ neue SQL-Migrationen
• Major-Refactorings (Cross-Tenant Person-Matching, Cold-Start Push, Profile-Redesign)

Issues #178-210 wurden als obsolet geschlossen.

KRITISCHE Cluster-Issues

#	Cluster	Effort	Sprint
#211	DSGVO-Compliance (Delete-Account, Legal-Page, Consent)	21h	0
#212	Push-Notifications komplett fehlend	19h	1
#213	Cold-Start-Race + Tenant-Auto-Close + Notiz-Reasons + Conductor-Switch	15.5h	3
#214	Cross-Tenant Person-Matching	37.5h	4
#215	Architektur: Tenant-Create + include_in_average + shift_excused_as_present	9h	0/9
#216	Songs Public-Viewer + Export ExtraFields	19.5h	8/9
#217	Files-Page + Cross-Tenant Shift-Inkonsistenz	25h	6/11
#218	Bulk-Edit-Page für Personen	24h	5

HOCH-Tracking-Issues

#	Cluster	Effort	Sprint
#219	Repository-Bypass: 20+ Stellen	30h	2
#220	Cross-Cutting Services (Tracking, AudioPlayer, Dashboard)	~16h	1
#221	Role-Permissions konfigurierbar	24h	5

Empfohlene Sprint-Reihenfolge

1. Sprint 0 — DSGVO-Compliance ([CRITICAL] DSGVO-Compliance: Delete-Account + Legal-Page + Consent-Modal fehlen #211, [CRITICAL] Architektur: Tenant-Create ohne Defaults + include_in_average + shift_excused_as_present #215 partial) — vor App-Store-Submission zwingend, 3 Tage
2. Sprint 1 — Cross-Cutting Services ([CRITICAL] Push-Notifications komplett fehlend (firebase_messaging + device_tokens) #212, [HIGH/Tracking] Cross-Cutting Services fehlen: Tracking + AudioPlayer + Dashboard #220) — Foundation für viele andere, 5 Tage
3. Sprint 2 — Repository-Bypass-Refactoring ([HIGH/Tracking] Repository-Bypass: 20+ Stellen umgehen das Repository-Pattern #219) — 4 Tage
4. Sprint 3 — Cold-Start + Realtime ([CRITICAL] Attendance: Cold-Start-Race + Tenant-Auto-Close + Notiz-Reasons + Conductor-Switch #213) — 2 Tage
5. Sprint 4 — Cross-Tenant Person-Matching ([CRITICAL] Cross-Tenant Person-Matching: Typeahead + Email-Lookup fehlen, Email case-sensitive #214) — 3 Tage
6. Sprint 5 — Neue Pages ([CRITICAL] Bulk-Edit-Page für Personen fehlt komplett (Ionic v4.0.5 NEW) #218, [HIGH] Role-Permissions konfigurierbar: tenant_role_permissions wird ignoriert (Security) #221) — 3 Tage
7. Sprint 6 — Settings-Hub-Restructuring ([CRITICAL] Files-Page komplett fehlt + Cross-Tenant Shift-Inkonsistenz #217 partial) — 3 Tage
8. Sprint 7 — People Workflows — 3 Tage
9. Sprint 8 — Songs Public-Sharing ([CRITICAL] Songs Public-Viewer fehlt + Export ohne tenant additional_fields #216 partial) — 2 Tage
10. Sprint 9 — Statistics + Export Bug-Fixes ([CRITICAL] Architektur: Tenant-Create ohne Defaults + include_in_average + shift_excused_as_present #215, [CRITICAL] Songs Public-Viewer fehlt + Export ohne tenant additional_fields #216) — 1 Tag
11. Sprint 10 — Sign-Out-Pattern + Reasons — 2 Tage
12. Sprint 11 — Attendance Workflows — 2 Tage
13. Sprint 12 — Long Tail (118 MITTEL + 66 NIEDRIG)

Patterns

• Repository-Bypass ist das dominanteste Architektur-Problem
• Cross-Cutting Services (Push, Tracking, AudioPlayer) tauchen in fast jedem Batch auf
• DSGVO-Lücken sind App-Store-Risiko
• Custom-Reason-Dialog Pattern wurde 4× kopiert (Sign-Out aller Pages)
• Force-Unwrap auf tenant.id! Pattern wiederholt sich trotz früherer Fixes
• Tenant-Konfiguration (absence_reasons, late_reasons, additional_fields, shift_excused_as_present, tenant_role_permissions) wird konsequent ignoriert/hardcoded

[Lionhunt3r]

Sprint 1a complete — merged in 4edf10f.

✅ Sprint 1a (Tracking + Audio Foundation, ~38h actual)
🔜 Sprint 1b (Push Foundation) — next, blocked on Firebase project audit

Test count: 374 → 419 (+45 new sprint tests + reclaimed 17 from base sync)
Version: 0.1.27+28 → 0.2.0+29

Polish items deferred to docs/superpowers/polish-backlog.md (11 minor findings, none blocking).

Sprint 1a closed: foundation services available for downstream sprints. Tracking observer is live on every navigation; audio mini-bar is mounted in MainShell.

[Lionhunt3r]

Sprint reorder 2026-06-19 (commit 2a48cc7):

Sprint 1b deferred to end of master plan (Firebase pre-conditions not available). Sprint 4 split into 4a (now, no Push) and 4b (with 1b, later).

Updated order:

1. 1a ✅ DONE
2. 2 (Repository-Bypass) ← next
3. 3 (DSGVO)
4. 4a (Reasons + Conductor + Tenant-Auto-Close)
5. 5 (Cross-Tenant Person-Matching)
6. 6 (Settings + Files)
7. 7 (Bulk-Edit + Role-Permissions)
8. 8 (Songs Public + Audio)
9. 9 (Stats + Export)
10. 10 (People Workflows)
11. 11 (Sign-Out Reasons)
12. 12 (Attendance Workflows)
13. 1b (Push Foundation) ← when Firebase + iPhone ready
14. 4b (Cold-Start Push)
15. 13 (Long Tail)

If Firebase never available: 1b + 4b stay in Long-Tail.

[Lionhunt3r]

Sprint 2a complete — merged in d2d2c67.

Updated progress:

• ✅ Sprint 1a (Foundation)
• ✅ Sprint 2a (Repository-Bypass — Existing Repos)
• ⏭️ Sprint 2b (next — New Repositories)
• Then: 2c, 3, 4a, 5, 6, 7, 8, 9, 10, 11, 12, 1b, 4b, 13

Test count: 419 → 442 (+23). Version: 0.2.1+30.
Bypass count outside repos: ~100 → 82 (-18 stellen).