14 Commits

Author	SHA1	Message	Date
Lars	f1ee1eec7e	feat: update maturity models and version to 0.7.2 ... - Incremented application version to 0.7.2 and updated database schema version to 20260427025. - Enhanced maturity models functionality to support M:N relationships for focus areas, style directions, and target groups. - Updated frontend to allow multi-selection for focus areas, style directions, and target groups. - Documented changes in the changelog for version 0.7.2, including new migration details and UI improvements.	2026-04-27 11:42:03 +02:00
Lars	5277f4f4cf	feat: add maturity models functionality and update version ... - Introduced new maturity models feature with CRUD operations in the API. - Added routes and frontend components for managing maturity models. - Updated version to 0.7.1 with corresponding build date and schema version. - Enhanced admin navigation to include maturity models section. - Documented changes in the changelog for version 0.7.1.	2026-04-27 11:32:30 +02:00
Lars	01ed5509f8	feat: Exercises v2.0 + Migrations 014/016/017 (Clean-Room Rebuild) ... BREAKING CHANGES: - exercises.py komplett neu gebaut (kein Legacy-Code) - Legacy-Felder entfernt: age_groups, focus_area, secondary_areas, training_character - Nur M:N Relations, keine JSONB-Kataloge Migrations: - Migration 014: Variant Progression + Search Vector + Legacy DROP - exercise_variants: progression_level, sequence_order, prerequisite_variant_id - exercises: search_vector (tsvector für Volltext-Suche) - DROP age_groups, focus_area, secondary_areas, training_character - Helper: update_timestamp() Funktion für Triggers - Migration 016: Saved Exercise Searches - saved_exercise_searches (profile_id, name, filters JSONB) - Migration 017: Exercise Blocks + Template Blocks - exercise_blocks (name, description, goal, is_template) - exercise_block_items (exercise_id, variant_id, sequence_order, is_placeholder, placeholder_criteria) Backend (exercises.py v2.0): - GET /exercises: Volltext-Suche via tsvector, M:N Joins - GET /exercises/{id}: enrich_exercise_detail() mit allen M:N Relations - POST /exercises: M:N Relations (focus_areas_multi, training_styles_multi, target_groups_multi, age_groups, skills) - PUT /exercises: Partial Update + M:N Relations - DELETE /exercises: Cascade-Check für exercise_block_items Architecture: - Issue #53 konform: Import = Feld-Zuordnung, keine fachliche Interpretation - Helper: enrich_exercise_detail() für vollständige Objekte - Helper: assign_exercise_relations() für M:N Management (DELETE+INSERT Pattern) Docs: - SMW_IMPORTER_GAP_ANALYSIS.md: Vollständige Gap-Analyse + Umsetzungsplan Version: 0.7.0 Module: exercises 2.0.0 Schema: 20260424002	2026-04-24 15:04:27 +02:00
Lars	6801c60604	feat: Add MediaWiki import functionality with tracking and mapping ... - Implemented a new SQL migration for wiki import tracking tables. - Created an import router for handling MediaWiki imports of exercises, skills, and methods. - Developed a Semantic MediaWiki API client for direct API interactions. - Added a mapper to convert SMW properties to local database fields. - Introduced background tasks for asynchronous import processing. - Implemented logging and error handling for import operations. - Added endpoints for previewing imports, checking import status, and managing import references.	2026-04-24 14:41:52 +02:00
Lars	5e2820c63c	feat: Trainer-Kontext-System & Exercise Training Characters (v0.5.0) ... Migration 012: - exercise_training_characters (M:N junction table) - trainer_contexts (Fokussierte Trainer-Ansichten) - Indizes für Performance - Example seed data Backend (catalogs.py): - GET /api/trainer-contexts (list own contexts) - POST /api/trainer-contexts (create context) - PUT /api/trainer-contexts/{id} (update own context) - DELETE /api/trainer-contexts/{id} (delete own context) - Enriched responses mit focus_area_name, style_direction_name, training_type_name - Ownership-Validation (nur eigene Kontexte) Frontend: - TrainerContextsPage.jsx (vollständige CRUD-UI) - Kaskadierende Dropdowns (Fokusbereich → Stilrichtung) - is_style_independent Flag für stilunabhängige Kontexte - api.js erweitert (listTrainerContexts, create, update, delete) Architektur: - Flat Catalogs mit M:N überall - NULL = 'für alles geeignet' - Trainer-Kontexte für fokussierte Ansichten - Vorbereitung für 1000+ Übungen mit flexibler KI-Filterung version: 0.5.0 (backend + frontend) module: exercises 0.5.0, catalogs 1.5.0 page: TrainerContextsPage 1.0.0 Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>	2026-04-23 14:22:17 +02:00
Lars	155c21f018	fix: Backend SQL Queries für renamed tables (Migration 010+011) ... - Updated all SQL queries in catalogs.py to use renamed tables: - training_styles → style_directions - training_style_target_groups → style_direction_target_groups - exercise_styles → exercise_style_directions - Updated API parameter names: training_style_id → style_direction_id - Updated response field names: training_style_name → style_direction_name - Updated array field names: training_styles → style_directions - Fixes 'failed to fetch' errors on Stilrichtungen, Hierarchie, Zuordnungen tabs version: 0.4.0 (backend) module: catalogs 1.4.0 Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>	2026-04-23 12:24:50 +02:00
Lars	62b5b4c2fd	feat: Migration 010+011 - Stilrichtungen + Trainingsstil-Dimension ... Migration 010: Umbenennung (konsistente Terminologie) - training_styles → style_directions - exercise_styles → exercise_style_directions - training_style_target_groups → style_direction_target_groups - training_style_id → style_direction_id (in Junction-Tabellen) - Idempotent mit IF EXISTS checks Migration 011: Neue Dimension "Trainingsstil" - Neue Tabelle training_types (Breitensport, Leistungssport, Wettkampf) - Seed-Daten: 3 Standard-Trainingsstile - Junction-Tabelle exercise_training_types (M:N) - Indizes für Performance - ON DELETE RESTRICT: Training Types können nicht gelöscht werden wenn zugeordnet Architektur: - Fokusbereich (Karate) → Stilrichtung (Shotokan) → Trainingsstil (Breitensport) → Zielgruppe (Kinder) - Alle M:N für maximale Flexibilität - KI-freundlich: Flache Dimensionen, einfache Queries Version: 0.4.0 (BREAKING - nur DB-Migrationen, Backend/Frontend folgen)	2026-04-23 12:10:27 +02:00
Lars	1e5e18c0b3	feat: Migration 009 - Zielgruppen M:N Refactoring ... Backend Phase A (Database + API): - Migration 009: target_groups.training_style_id entfernt - Migration 009: Neue Junction-Tabelle training_style_target_groups - Migration 009: Datenmigration alte → neue Struktur (idempotent) - API: 5 neue Endpoints für M:N Management * GET /training-style-target-groups (mit Enrichment) * POST /training-style-target-groups (Upsert-Logik) * PUT /training-style-target-groups/{id} (is_primary) * DELETE /training-style-target-groups/{id} * GET /training-styles/hierarchy (für Tree-View) - API: GET/POST/PUT /target-groups jetzt global (ohne training_style_id) - API: DELETE /target-groups prüft beide Tabellen (CASCADE-Schutz) Architecture: - Eine Zielgruppe kann mehreren Stilen zugeordnet werden - Basis für Admin Tree-View + M:N Matrix UI Version: 0.3.4 Module: catalogs 1.3.0	2026-04-23 10:37:56 +02:00
Lars	2186bb3a69	fix: Admin-Navigation - Redirect /admin → /admin/catalogs ... Problem: Navigation-Link zeigte /admin, aber Route war /admin/catalogs Folge: Klick auf 'Admin' führte zu 404 (Catch-all Redirect zu /) Fix: Redirect-Route von /admin zu /admin/catalogs hinzugefügt version: 0.3.3	2026-04-23 09:00:28 +02:00
Lars	278d719e84	feat: Zielgruppen-Verwaltung (Target Groups CRUD + Admin UI) ... Backend: - GET /api/target-groups: Liste mit hierarchischem Kontext (focus_area → training_style → target_group) - POST /api/target-groups: Create (admin only) - PUT /api/target-groups/{id}: Update (admin only) - DELETE /api/target-groups/{id}: Delete (superadmin only) mit CASCADE-Schutz - Filter: by training_style_id, status Frontend: - api.js: listTargetGroups, createTargetGroup, updateTargetGroup, deleteTargetGroup - AdminCatalogsPage: Neuer Tab "Zielgruppen" (6. Tab) - Create-Form: training_style_id, name, description, min_age, max_age - List-View: Hierarchie-Anzeige (Fokusbereich → Stil → Zielgruppe + Altersbereich) - Inline-Editing mit Stil-Auswahl-Dropdown - Delete mit Confirmation Dialog Architektur: - Hierarchische Beziehung: target_groups.training_style_id → training_styles → focus_areas - CASCADE-Protection: DELETE verweigert wenn exercise_target_groups Einträge existieren - Backend liefert enriched data mit training_style_name + focus_area_name version: 0.3.2 modules: catalogs 1.2.0 pages: AdminCatalogsPage 1.1.0	2026-04-23 08:55:54 +02:00
Lars	d67f659e97	feat: Exercises-Router M:N Zuordnungen ... Backend API erweitert um M:N Katalog-Zuordnungen: - GET /exercises/{id}: Liefert focus_areas[], training_styles[], target_groups[], age_groups_catalog[] - POST /exercises: Akzeptiert focus_areas_multi[], training_styles_multi[], target_groups_multi[], age_groups_catalog[] - PUT /exercises/{id}: DELETE+INSERT Pattern für M:N Updates (konsistent mit skills) Rückwärtskompatibilität: - Legacy FK-Felder (focus_area_id, training_style_id, training_character_id) bleiben erhalten - Alte Aufrufe funktionieren unverändert - Neue M:N Felder sind optional version: 0.3.1 modules: exercises 0.4.0	2026-04-23 08:51:45 +02:00
Lars	63b1c09975	feat: Migration 008 - M:N Exercise Relations + Hierarchical Catalogs ... BREAKING CHANGE: Datenmodell-Umstellung von 1:1 auf M:N Beziehungen Migration 008: - Zielgruppen-Tabelle (target_groups) mit training_style_id Hierarchie - M:N Zuordnungstabellen: exercise_focus_areas, exercise_styles, exercise_target_groups - Altersgruppen-Dimension (exercise_age_groups) mit CHECK constraint - Hierarchische Struktur: training_styles.focus_area_id → focus_areas - Daten-Migration: Bestehende 1:1 Beziehungen zu M:N mit is_primary=true - Seed-Daten: Beispiel-Zielgruppen für Shotokan Architektur: - Smart Cascade-Logik (RESTRICT, Rerouting, Move) vorbereitet - Legacy-Spalten (focus_area_id, training_style_id) bleiben zur Rückwärtskompatibilität - Primary/Secondary Assignments via is_primary Flag Dokumentation: - .claude/docs/technical/DATABASE_SCHEMA.md (kontinuierlich gepflegt) - .claude/docs/functional/DOMAIN_MODEL.md (fachliche Anforderungen) - Migrations-Historie aktualisiert version: 0.3.0 (backend + frontend) modules: exercises 0.3.0, catalogs 1.1.0 DB_SCHEMA_VERSION: 20260423 Konzept: shinkan_anforderungsdokument_entwurf.md (§8.1, §8.3, §10.7)	2026-04-23 08:46:56 +02:00
Lars	0c7caea847	version: Bump to 0.2.0 + Changelog (Admin-Kataloge) ... CRITICAL FIX: Versions-Bump nachgeholt (war Pflicht laut ARCHITECTURE.md §2.5) Backend: - APP_VERSION: 0.1.0 → 0.2.0 - BUILD_DATE: 2026-04-21 → 2026-04-23 - DB_SCHEMA_VERSION: 20260421 → 20260422 (Migration 007) - MODULE_VERSIONS: catalogs 1.0.0 (neu), exercises 0.2.0 Frontend: - version.js neu erstellt - PAGE_VERSIONS: ExercisesPage 1.1.0, AdminCatalogsPage 1.0.0 Changelog: - Admin-Kataloge Feature komplett dokumentiert - Migration 007, Frontend-Integration, Formular-Standardisierung Deployment sollte jetzt korrekte Version zeigen + Katalog-Endpoints funktionieren.	2026-04-23 08:05:11 +02:00
Lars	a426c03598	feat: Initial Shinkan setup ... - Repository structure created - Core backend files from Mitai (auth, db, db_init) - Shinkan-specific: version.py, models.py, main.py - Documentation: CLAUDE.md, README.md - Environment: .env.example, .gitignore version: 0.1.0 date: 2026-04-21	2026-04-21 14:26:12 +02:00