docs: archive outdated reports and organize references
Archived several outdated reports (`Ping-Service_Impl_01-2026.md`, `Frontend_Integration_Status.md`, etc.) and added archival notes and references to updated documents. Introduced a centralized reference structure for tech stack documentation, consolidating files under `01_Architecture/Reference/Tech_Stack`. Added new resources (`Gradle_Kotlin_DSL_Primer`, `Kotlin_2-3-0_ReleaseNotes`) for improved project organization and clarity.
This commit is contained in:
@@ -1,6 +1,6 @@
|
||||
---
|
||||
type: Report
|
||||
status: FINAL
|
||||
status: ARCHIVED
|
||||
owner: Frontend Expert
|
||||
date: 2026-01-17
|
||||
tags: [frontend, kmp, auth, ping, architecture]
|
||||
@@ -8,6 +8,10 @@ tags: [frontend, kmp, auth, ping, architecture]
|
||||
|
||||
# 🚩 Statusbericht: Frontend (17. Jänner 2026)
|
||||
|
||||
**ARCHIVED:** This report reflects a past state. Please refer to `2026-01-23_Weekend_Status_Report.md` for the current status.
|
||||
|
||||
---
|
||||
|
||||
**Status:** ✅ **Erfolgreich abgeschlossen**
|
||||
|
||||
Wir haben heute die technische Basis des Frontends massiv stabilisiert und das "Ping-Feature" als vollständige Referenz-Implementierung für gesicherte API-Kommunikation fertiggestellt.
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
type: Report
|
||||
status: ACTION_REQUIRED
|
||||
status: ARCHIVED
|
||||
owner: Lead Architect
|
||||
date: 2026-01-17
|
||||
tags: [architecture, handover, critique, roadmap]
|
||||
@@ -8,6 +8,10 @@ tags: [architecture, handover, critique, roadmap]
|
||||
|
||||
# 🏗️ Lead Architect Status Report & Handover
|
||||
|
||||
**ARCHIVED:** This report reflects a past state. Please refer to `2026-01-23_Weekend_Status_Report.md` for the current status.
|
||||
|
||||
---
|
||||
|
||||
**Datum:** 17. Jänner 2026
|
||||
**Status:** 🟡 **PARTIALLY BLOCKED** (Frontend Architecture Split)
|
||||
**Ziel:** Abschluss "Trace Bullet" (Ping Feature mit Auth, Sync & Tracing)
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
type: Report
|
||||
status: FINAL
|
||||
status: ARCHIVED
|
||||
owner: Frontend Expert
|
||||
date: 2026-01-19
|
||||
tags: [frontend, refactoring, clean-architecture, ping-feature]
|
||||
@@ -8,6 +8,10 @@ tags: [frontend, refactoring, clean-architecture, ping-feature]
|
||||
|
||||
# 🚩 Statusbericht: Frontend Refactoring (19. Jänner 2026)
|
||||
|
||||
**ARCHIVED:** This report reflects a past state. Please refer to `2026-01-23_Weekend_Status_Report.md` for the current status.
|
||||
|
||||
---
|
||||
|
||||
**Status:** ✅ **Erfolgreich abgeschlossen**
|
||||
|
||||
Wir haben die vom Lead Architect kritisierte Fragmentierung im Frontend behoben und das Ping-Feature auf eine saubere **Clean Architecture** migriert.
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
type: Report
|
||||
status: APPROVED
|
||||
status: ARCHIVED
|
||||
owner: Lead Architect
|
||||
date: 2026-01-19
|
||||
tags: [architecture, review, frontend, ping-feature]
|
||||
@@ -8,6 +8,10 @@ tags: [architecture, review, frontend, ping-feature]
|
||||
|
||||
# 🏗️ Lead Architect Review: Frontend Refactoring
|
||||
|
||||
**ARCHIVED:** This report reflects a past state. Please refer to `2026-01-23_Weekend_Status_Report.md` for the current status.
|
||||
|
||||
---
|
||||
|
||||
**Datum:** 19. Jänner 2026
|
||||
**Status:** ✅ **APPROVED**
|
||||
**Referenz:** `docs/90_Reports/2026-01-19_Frontend_Refactoring_Status.md`
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
type: Report
|
||||
status: DRAFT
|
||||
status: ARCHIVED
|
||||
owner: Frontend Expert
|
||||
date: 2026-01-20
|
||||
tags: [frontend, backend, integration, ping-feature]
|
||||
@@ -8,6 +8,10 @@ tags: [frontend, backend, integration, ping-feature]
|
||||
|
||||
# 🚩 Statusbericht: Frontend-Backend Integration (20. Jänner 2026)
|
||||
|
||||
**ARCHIVED:** This report reflects a past state. Please refer to `2026-01-23_Weekend_Status_Report.md` for the current status.
|
||||
|
||||
---
|
||||
|
||||
**Status:** ✅ **Erfolgreich verifiziert**
|
||||
|
||||
Wir haben die Integration zwischen dem KMP-Frontend (Desktop App) und dem Spring Boot Backend (via Gateway) erfolgreich getestet und stabilisiert.
|
||||
|
||||
@@ -0,0 +1,49 @@
|
||||
---
|
||||
type: Report
|
||||
status: FINAL
|
||||
owner: Lead Architect
|
||||
date: 2026-01-23
|
||||
tags: [status, milestone, tracer-bullet]
|
||||
---
|
||||
|
||||
# 🚀 Weekend Status Report: "Operation Tracer Bullet"
|
||||
|
||||
**Datum:** 23. Jänner 2026
|
||||
**Phase:** Validierung & Härtung
|
||||
|
||||
## 1. Executive Summary
|
||||
Das Projekt hat einen kritischen Meilenstein erreicht. Der "Tracer Bullet" (Ping-Service) durchdringt erfolgreich den gesamten Stack – vom Frontend (Desktop) über das Gateway bis zur Datenbank, inklusive Security und Resilience.
|
||||
Die technische Basis ist stabilisiert, die "Kinderkrankheiten" (Versionskonflikte, Docker-Networking) sind geheilt.
|
||||
|
||||
## 2. Status pro Gewerk
|
||||
|
||||
### 🏗️ Architecture & Build
|
||||
* **Status:** 🟢 GRÜN
|
||||
* **Erfolg:** Tech-Stack Stabilisierung (ADR-0013) hat Build-Probleme eliminiert.
|
||||
* **Doku:** `AGENTS.md` definiert klare Zusammenarbeit.
|
||||
|
||||
### 🐧 Infrastructure (DevOps)
|
||||
* **Status:** 🟢 GRÜN
|
||||
* **Erfolg:** Docker-Environment ist vollständig operational.
|
||||
* **Highlight:** Lösung des JWT-Validierungsproblems ("Split Horizon") ermöglicht saubere Auth in Containern.
|
||||
|
||||
### 👷 Backend (Spring Boot)
|
||||
* **Status:** 🟢 GRÜN
|
||||
* **Erfolg:** `ping-service` ist "Production Ready".
|
||||
* Flyway Migrationen aktiv.
|
||||
* CircuitBreaker & Metrics aktiv.
|
||||
* Security (RBAC) aktiv.
|
||||
|
||||
### 🎨 Frontend (KMP)
|
||||
* **Status:** 🟡 GELB (Teilweise fertig)
|
||||
* **Erfolg:** Desktop-App kann sich einloggen und synchronisieren.
|
||||
* **Offen:** Web-Support (PKCE Flow) muss nachgezogen werden.
|
||||
* **UX:** Design ist noch rudimentär ("Developer Art").
|
||||
|
||||
## 3. Risiken & Blocker
|
||||
* **Keine Blocker.** Der Weg für die fachliche Implementierung ist frei.
|
||||
|
||||
## 4. Plan für das Wochenende / Nächste Woche
|
||||
1. **Web-Auth:** Frontend Expert implementiert PKCE für Browser-Support.
|
||||
2. **Integration Test:** Einmaliger kompletter Durchstich (Frontend -> Backend -> DB) mit laufendem Docker-Stack.
|
||||
3. **Domain Start:** Beginn der Arbeit an der `Events` (Veranstaltungen) Domäne.
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
type: Report
|
||||
status: FINAL
|
||||
status: ARCHIVED
|
||||
author: Senior Backend Developer
|
||||
date: 2026-01-17
|
||||
context: Phase 3 - Sync Implementation
|
||||
@@ -8,6 +8,10 @@ context: Phase 3 - Sync Implementation
|
||||
|
||||
# Backend Status Report: Phase 3 (Sync) abgeschlossen
|
||||
|
||||
**ARCHIVED:** This report reflects a past state. Please refer to `2026-01-23_Weekend_Status_Report.md` for the current status.
|
||||
|
||||
---
|
||||
|
||||
## 1. Zusammenfassung
|
||||
Die Phase 3 der "Operation Tracer Bullet" wurde erfolgreich abgeschlossen. Der `PingService` wurde um Delta-Sync-Funktionalität erweitert, um Offline-First-Clients effizient zu unterstützen.
|
||||
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
type: Report
|
||||
status: FINAL
|
||||
status: ARCHIVED
|
||||
owner: DevOps Engineer
|
||||
last_update: 2026-01-20
|
||||
context: Phase 1-3 (Backend Ready)
|
||||
@@ -8,6 +8,10 @@ context: Phase 1-3 (Backend Ready)
|
||||
|
||||
# Infrastructure Status Report: "Tracer Bullet" Readiness
|
||||
|
||||
**ARCHIVED:** This report reflects a past state. Please refer to `2026-01-23_Weekend_Status_Report.md` for the current status.
|
||||
|
||||
---
|
||||
|
||||
**Datum:** 20. Jänner 2026
|
||||
**Autor:** DevOps & Infrastructure Engineer (Updated by Backend Developer)
|
||||
**Ziel:** Bestätigung der Einsatzbereitschaft der lokalen Entwicklungsumgebung für Phase 1 (Backend Hardening) und Phase 3 (Sync).
|
||||
|
||||
@@ -1,3 +1,17 @@
|
||||
---
|
||||
type: Report
|
||||
status: ARCHIVED
|
||||
owner: Lead Architect
|
||||
date: 2026-01-10
|
||||
tags: [backend, ping-service, task]
|
||||
---
|
||||
|
||||
# Arbeitsauftrag: Implementierung des `ping-service` (Tracer Bullet)
|
||||
|
||||
**ARCHIVED:** This is the original task description. The implementation has evolved. Please refer to `docs/05_Backend/Services/PingService_Reference.md`.
|
||||
|
||||
---
|
||||
|
||||
**An:** Senior Backend Developer
|
||||
**Von:** Lead Software Architect
|
||||
**Betreff:** Arbeitsauftrag: Implementierung des `ping-service` (Tracer Bullet)
|
||||
@@ -199,4 +213,3 @@ Der Auftrag gilt als erledigt, wenn:
|
||||
5. Die Requests in der Zipkin UI als Trace sichtbar sind.
|
||||
|
||||
Bei Fragen zur Konfiguration oder zur Architektur stehe ich dir zur Verfügung.
|
||||
|
||||
|
||||
File diff suppressed because it is too large
Load Diff
Reference in New Issue
Block a user