stefan
9ff543dc14
Desktop CI — Headless Tests & Build / Compose Desktop — Tests (headless) & Build (push) Has been cancelled
Build and Publish Docker Images / build-and-push (., backend/infrastructure/gateway/Dockerfile, api-gateway, api-gateway) (push) Has been cancelled
Build and Publish Docker Images / build-and-push (., backend/services/ping/Dockerfile, ping-service, ping-service) (push) Has been cancelled
Build and Publish Docker Images / build-and-push (., config/docker/caddy/web-app/Dockerfile, web-app, web-app) (push) Has been cancelled
Build and Publish Docker Images / build-and-push (., config/docker/keycloak/Dockerfile, keycloak, keycloak) (push) Has been cancelled
- **Domain Enhancements:** - Introduced `TurnierNummer` (mandatory, 5 digits) field in `DomTurnier` to establish unique tournament identification. - Added `TeilnehmerKreisE` enum representing participation constraints defined in ÖTO § 3 (e.g., J, P, H). - Extended `DomTurnier` model with `einschraenkungen` field to store applicable participant restrictions. - **Infrastructure Updates:** - Updated `TurnierTable` to include `turnier_nummer` (varchar) and `einschraenkungen` (text/JSON). - Created Flyway migration to add new columns to `turniere` table and backfill existing data. - Enhanced repository methods (`TurnierRepositoryImpl`) to handle the new fields. - **Validation and API Expansion:** - Added validation for mandatory 5-digit format of `TurnierNummer` and ensured `einschraenkungen` values conform to the ÖTO spec. - Updated relevant APIs (`CreateTurnierUseCase`, `TurniereController`) to accept and process new fields. - **Documentation:** - Updated the glossary in `Ubiquitous_Language.md` to include new concepts (`TurnierNummer` and participation constraints). This enhancement lays the groundwork for ÖTO-compliant tournament management with precise scope and constraint controls.
📚 Projektdokumentation "Meldestelle"
Willkommen im "Gehirn" des Projekts. Dieses Verzeichnis ist die Single Source of Truth.
📂 Struktur
🏗️ Core
01_Architecture: Der Masterplan. ADRs, Roadmaps und C4-Modelle.- Start hier:
MASTER_ROADMAP.md
- Start hier:
02_Guides: Guides für neue Entwickler (Setup, Guidelines).03_Domain: Fachlichkeit (Turnierregeln, Entities).
🛠️ Tech Stack
05_Backend: Spring Boot Services, API-Specs, DB-Schema.06_Frontend: Kotlin Multiplatform, Compose UI, State Management.07_Infrastructure: Docker, Keycloak, CI/CD, Zora-Architektur.- Referenz:
Zora_System_Architektur.md
- Referenz:
🤖 Process
04_Agents: Playbooks für unsere KI-Mitarbeiter.90_Reports: Statusberichte und Meilenstein-Analysen.99_Journal: Tägliche Session-Logs.
📝 Regeln für die Dokumentation
- Docs-as-Code: Doku liegt beim Code und wird im selben PR aktualisiert.
- Frontmatter: Jede Markdown-Datei muss einen YAML-Header haben:
--- type: [ADR, Guide, Reference, Report, Journal] status: [DRAFT, ACTIVE, DEPRECATED, ARCHIVED] owner: [Rolle] --- - Archivierung: Lösche nichts. Verschiebe veraltetes Wissen in
_archiveOrdner oder markiere es alsARCHIVED.
🚀 Quick Links
📦 Hinweis zur Reorganisation (C-3)
Im Rahmen von C-3 wird eine Konsolidierung von Medien/Binärartefakten unter docs/80_Assets/ sowie eine feinere Gliederung von Reports/Journals vorgeschlagen. Aktuell finden keine Verschiebungen statt – Details siehe Proposal oben.