21 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	e8eba57b3a	feat: Migration 022+023 - Vollständiger Skills-Import ... - Migration 022: Schema-Erweiterung - skill_main_categories (KARATE / ALLGEMEINE) - skills.main_category_id + focus_areas JSONB - skill_level_definitions Tabelle - Indizes für Performance - Migration 023: Produktionsreifer Skills-Import - 69 Skills mit vollständiger Kategorisierung - 2 Haupt-Kategorien, 9 Unterkategorien - KARATE: 32 Skills (karate focus) - ALLGEMEINE: 37 Skills (universal focus) - Duplikat-Bereinigung (Timing, Antizipation, etc.) - Scripts: - parse_matrix.py: Extrahiert Skills aus Fähigkeitsmatrix - generate_migration_023_direct.py: Generiert Migration direkt aus Matrix Source: https://karatetrainer.net/index.php?title=Fähigkeitsmatrix Verified auf Dev: 69 Skills importiert, korrekte Kategorisierung	2026-04-27 10:58:33 +02:00
Lars	97c1bb0c8b	feat: import 18 base skills from Fähigkeitsmatrix ... Imported from https://karatetrainer.net/index.php?title=Fähigkeitsmatrix - 9 skill categories (Kihon, Kumite, Kata, etc.) - 18 core skills with descriptions This enables skill-level assignments for imported exercises.	2026-04-27 10:26:10 +02:00
Lars	1ddbd76e36	fix: add UNIQUE constraint to exercise_skills table ... Fixes: 'no unique or exclusion constraint matching the ON CONFLICT specification' ON CONFLICT (exercise_id, skill_id) requires UNIQUE constraint. This was causing 91 import failures.	2026-04-27 10:00:02 +02:00
Lars	bcc7d61d07	fix: make exercise goal and execution optional (at least one required) ... Error: 224/225 exercises failed with NOT NULL constraint violations Root cause: exercises table requires BOTH goal AND execution (NOT NULL) Reality: Many wiki exercises have only ONE of these fields Migration 019: - ALTER COLUMN goal DROP NOT NULL - ALTER COLUMN execution DROP NOT NULL - ADD CHECK constraint: (goal IS NOT NULL OR execution IS NOT NULL) This allows: ✓ Exercises with only goal ✓ Exercises with only execution ✓ Exercises with both ✗ Exercises with neither (CHECK constraint fails) Import validation already correct (line 312): required_ok = bool(mapped.get('goal') or mapped.get('execution')) DB schema was blocking valid exercises.	2026-04-24 20:42:21 +02:00
Lars	711bdc99cb	fix: Migration 014 - correct table name exercise_style_directions (not exercise_training_styles)	2026-04-24 15:10:26 +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	0be9fd840c	fix: remove incompatible schema_migrations tracking from migrations 012-013 ... The db_init.py system uses (filename, applied_at) schema, not (version, description). Removing manual INSERT statements - db_init.py handles tracking automatically.	2026-04-23 16:17:35 +02:00
Lars	fe5d29e40e	feat: Training Types → Focus Area Hierarchie ... Migration 013: - Adds focus_area_id to training_types (context-specific types) - Migrates existing data to Karate focus area - Seeds focus-area-specific training types: * Karate: Dan-Vorbereitung * Gewaltschutz: Präventivkurse, Intensivtraining, Spezialkurse * Fitness: Gesundheitssport, Funktionelles Training - Updates unique constraint to (name, focus_area_id) Backend (catalogs.py): - list_training_types: Added focus_area_id filter, LEFT JOIN focus_areas - create_training_type: Added focus_area_id parameter - update_training_type: Added focus_area_id parameter - Enriched responses with focus_area_name and focus_area_icon Frontend (AdminCatalogsPage): - Added Fokusbereich dropdown to create form - Added Fokusbereich dropdown to edit form - Display shows focus_area_icon and focus_area_name - Training types now context-specific to focus areas Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>	2026-04-23 15:29:23 +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	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	2a5f06a8f5	feat: Refactor target groups to M:N relationship and update related endpoints	2026-04-23 09:27:13 +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	d0e9b9b764	fix: Make migration 007 idempotent (IF NOT EXISTS + ON CONFLICT) ... CRITICAL FIX: Migration 007 failed beim Startup wegen existierendem Index Problem: - Migration 007 wurde teilweise angewendet (Spalten + Indexes erstellt) - Bei erneutem Versuch: 'idx_skills_category already exists' → Abbruch - Tabellen (training_styles, training_characters, etc.) nicht erstellt - Katalog-Endpoints → 500 Error (UndefinedTable) Lösung: - Alle CREATE TABLE → CREATE TABLE IF NOT EXISTS - Alle CREATE INDEX → CREATE INDEX IF NOT EXISTS - ALTER TABLE → DO $$ BEGIN IF NOT EXISTS ... END $$ - Alle INSERT → ON CONFLICT (name) DO NOTHING Migration kann jetzt beliebig oft ausgeführt werden ohne Fehler.	2026-04-23 08:10:44 +02:00
Lars	43c6abce4a	feat: Exercise Catalogs - Admin-verwaltbare Stammdaten (Backend) ... Problem: Hard-codierte Werte (Fokusbereich, Trainingscharakter) + fehlende Dimensionen (Stil, Fähigkeiten-Matrix) + keine Rollen-basierte Sichtbarkeit Lösung: Dynamische Kataloge mit Admin-CRUD Migration 007_exercise_catalogs.sql: - focus_areas (statt hard-coded 'karate', 'selbstverteidigung', 'gewaltschutz') - training_styles (NEU: Shotokan, Goju-Ryu, Wado-Ryu, etc. mit Hierarchie) - training_characters (statt hard-coded 'grundlage', 'aufbau', etc.) - skill_categories (Matrix: Kategorien → Einzelfähigkeiten) - trainer_focus_areas (Zuordnung: Trainer → Fokusbereiche) - exercises erweitert: training_style_id, training_character_id, focus_area_id - skills erweitert: category_id, parent_skill_id, level, sort_order - Seed-Daten für alle Kataloge Backend (routers/catalogs.py): - CRUD für focus_areas (admin only) - CRUD für training_styles (admin only, mit parent_style_id) - CRUD für training_characters (admin only) - CRUD für skill_categories (admin only, mit parent_category_id) - CRUD für trainer_focus_areas (admin: assign, trainer: read own) - Alle mit status-Filter (active/inactive) Backend (routers/exercises.py): - CREATE/UPDATE erweitert um training_style_id, training_character_id, focus_area_id - Legacy-Felder (focus_area text, training_character text) bleiben parallel Backend (main.py): - catalogs Router registriert Nächster Schritt: Frontend-UI (Admin-Kataloge + Exercise-Formular-Update)	2026-04-22 22:06:11 +02:00
Lars	7f156ba085	feat: Training Planning (core feature) complete ... Backend: - Created migration 006_training_planning.sql - training_units table (planned vs actual, status, notes) - training_unit_exercises M:N (order, duration, modifications) - Created routers/training_planning.py with full CRUD - List with filters (group, date range, status) - Get detail with exercises - Create/Update/Delete with access control - Quick create endpoint (auto-fills from group defaults) - Permission: trainer for own groups, admin for all - Registered training_planning router in main.py Frontend: - Complete TrainingPlanningPage with full planning workflow - Group selector + date range picker - List view with status badges (planned/completed/cancelled) - Create/Edit modal with exercise management - Drag to reorder exercises (▲▼) - Quick create button (one-click with group defaults) - Durchführung section (actual date/time, attendance, status) - Public notes + trainer-only notes - Updated api.js with deleteTrainingUnit and quickCreateTrainingUnit - Added /planning route to App.jsx - Navigation already configured (Calendar icon) This is the CORE feature - trainers can now plan and document training sessions. Next: Admin routes, role system refinement, testing	2026-04-22 16:54:34 +02:00
Lars	de53ba3f66	fix: Add lucide-react dependency for navigation icons ... CRITICAL FIX: Build was failing because lucide-react was not in package.json - Added lucide-react ^0.344.0 to dependencies - Required for appNav.js and DesktopSidebar.jsx icon imports - Build should now succeed Apologies for missing this in initial design foundation commit!	2026-04-22 16:40:05 +02:00
Lars	88677ea29f	fix: Add missing auth columns to profiles table	2026-04-21 21:07:52 +02:00
Lars	b2bc8590c4	feat: Complete MVP setup - Docker, Frontend, Migrations, CI/CD ... Docker & Deployment: - docker-compose.yml (Prod: Port 3003/8003) - docker-compose.dev-env.yml (Dev: Port 3098/8098) - Backend Dockerfile (Python 3.12-slim) - Frontend Dockerfile (Node 20 + Nginx) - Gitea Actions (deploy-dev.yml, deploy-prod.yml) Frontend: - React 18 + Vite setup - package.json, vite.config.js, index.html - App.jsx (minimal with version display) - api.js (complete API client) - app.css + AuthContext from Mitai - main.jsx entry point Backend Migrations: - 001_auth_membership.sql (Auth + Features + Tier Limits) - 002_organization.sql (Clubs, Divisions, Training Groups) - 003_catalogs.sql (Skills + Methods with sample data) Documentation: - .claude/rules/ (ARCHITECTURE, CODING_RULES, etc.) - SHINKAN_PROJECT_SETUP.md (technical setup guide) Server: - Directories created on Pi: /home/lars/docker/shinkan[-dev] - Gitea Runner configured and running Ready for first deployment to dev.shinkan.jinkendo.de version: 0.1.0 date: 2026-04-21	2026-04-21 14:36:52 +02:00