47 Commits

Author	SHA1	Message	Date
Lars	97a7fe7cba	fix: reimport dict-cursor bug + add admin cleanup endpoint ... Problem 1: Reimport fails completely (all exercises fail) Root cause: Line 465 existing[0] instead of existing['id'] Fix: Changed to existing['id'] for dict-cursor compatibility Problem 2: 221 exercises skipped, only 2 in database Root cause: Orphaned wiki_import_references from failed imports Fix: New admin endpoint to manually cleanup orphaned references New endpoints: - DELETE /api/import/mediawiki/admin/cleanup-orphaned-references Deletes all references where local_id doesn't exist in target table Returns count of deleted references per type - GET /api/import/mediawiki/admin/stats Shows references vs. actual count + orphaned count Helps diagnose import state issues Usage: 1. Call cleanup endpoint to remove orphaned references 2. Run normal import (reimport=false) 3. Should import all previously failed exercises	2026-04-27 08:52:05 +02:00
Lars	3a4160fd1c	fix: detect and cleanup orphaned import references ... Problem: 221 exercises skipped, but only 2 actually in database Root cause: Failed imports created wiki_import_references entries, but exercises were never saved (due to earlier bugs) Duplicate check only verified references existed, not actual data. Result: All subsequent imports skipped 'already imported' items. Solution: - Enhanced duplicate check to verify BOTH reference AND actual entity - If reference exists but entity is missing → delete orphaned reference - Item will be re-imported on same run (no manual cleanup needed) Check logic: 1. Find reference in wiki_import_references 2. Check if exercises/skills/methods table has matching local_id 3. If both exist → skip (true duplicate) 4. If reference exists but entity missing → delete reference + re-import This auto-heals broken state from previous failed imports.	2026-04-27 08:45:27 +02:00
Lars	1a0708f152	fix: correct remaining dict cursor access (row[0] → row['id']) ... Error: 100 exercises failed with error '0' (TypeError suppressed) Root cause: More row[0] dict access in catalog assignment functions Previous fix only covered fetchone()[0] in RETURNING clauses. Missed 6 more locations in SELECT queries where row is dict-like. Fixed locations: - Line 511: focus_area_id in exercise_focus_areas INSERT - Line 524: style_direction_id in exercise_training_styles INSERT - Line 535: target_group_id in exercise_target_groups INSERT - Line 546: skill_id in exercise_skills INSERT - Line 568: skill_id in exercise_skills INSERT (with levels) - Line 589: category_id assignment in _upsert_skill All changed from row[0] to row['id'] for RealDictCursor compatibility. This should fix the remaining 100 import failures.	2026-04-27 08:24:35 +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	a37400bb22	fix: correct dict cursor access in MediaWiki import ... Error: 500 Internal Server Error on execute import Root cause: Using fetchone()[0] with RealDictCursor (dict-like rows) PostgreSQL RealDictCursor returns dict-like objects, not tuples. Accessing [0] on a dict throws TypeError. Fix: Changed all fetchone()[0] to fetchone()['id'] Locations: - Line 163: log_id after INSERT INTO wiki_import_log - Line 485: ex_id after INSERT INTO exercises - Line 599: skill_id after INSERT INTO skills - Line 616: method_id after INSERT INTO training_methods This matches the pattern used in other routers (exercises.py, etc.)	2026-04-24 20:37:31 +02:00
Lars	8b51864b53	feat: add recursive subcategory search for MediaWiki import ... Issue: Only 2 exercises found instead of 200+ Root cause: Exercises likely organized in subcategories Solution: - Added recursive parameter to get_category_members() - New _get_subcategories() helper method - Recursively traverses all subcategories - Logs subcategory counts for debugging Behavior: - get_category_members('Übungen') now finds: 1. All pages directly in 'Kategorie:Übungen' 2. All subcategories (e.g. 'Kihon', 'Kata', 'Kumite') 3. All pages in those subcategories (recursive) Example structure: Kategorie:Übungen ├─ Seite: Übung A (2 direkte) ├─ Kategorie:Kihon │ ├─ Seite: Mae-Geri │ └─ Seite: Gyaku-Zuki └─ Kategorie:Kata └─ Seite: Heian Shodan	2026-04-24 17:53:11 +02:00
Lars	c738f1234b	fix: MediaWiki import - increase limit to 500 and add validation ... Error: 422 Unprocessable Entity when limit > 100 Root cause: Backend enforced max=100, frontend allowed any value Backend fix: - Increased preview limit from 100 to 500 (consistent with execute) - import_wiki.py line 64: le=100 → le=500 Frontend fix: - Added Math.min/max validation to both limit inputs - Preview limit: max 500 with auto-clamp - Execute limit: max 500 with auto-clamp - Updated placeholder: 'Kein Limit (max 500)' Prevents 422 errors from invalid limit values	2026-04-24 17:15:17 +02:00
Lars	df569bbf6e	fix: auth register - correct column name created_at ... Error: column 'created' of relation 'profiles' does not exist Fix: Changed 'created' to 'created_at' in INSERT statement Line: backend/routers/auth.py:247	2026-04-24 16:07:13 +02:00
Lars	a67cc5f812	fix: exercises.py - use direct VARCHAR for age_groups (no catalog table in Shinkan)	2026-04-24 15:27:11 +02:00
Lars	a6ea5b95eb	fix: exercises.py - correct table name exercise_style_directions (all 3 occurrences)	2026-04-24 15:25:17 +02:00
Lars	b617b5a2d8	fix: exercises.py - handle dict rows in fetchone() for INSERT RETURNING	2026-04-24 15:23:00 +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	7314ae1436	feat: Hierarchical Admin UI - Tree View for Catalogs ... Backend: - New endpoint: GET /api/admin/hierarchy - Returns hierarchical structure: Focus Areas with nested Style Directions + Training Types - Style Directions include target_groups assignments (M:N) - JSON aggregation for efficient data loading Frontend: - New page: AdminHierarchyPage.jsx with Tree + Detail Panel layout - Tree View: Expandable/collapsible nodes (Focus Areas → Stilrichtungen/Trainingstypen) - Detail Panel: Shows selected item details, inline editing - Visual hierarchy: Icons, indentation, color coding - Responsive layout: Fixed 400px tree, fluid detail panel Routes: - /admin now redirects to /admin/hierarchy (new default) - /admin/hierarchy: Tree-based catalog management - /admin/catalogs: Legacy flat UI (still available) UX Improvements: - Visual hierarchy instead of flat tabs - M:N relationships visible (target groups per style) - Better navigation: Click to select, expand/collapse sections - Cleaner layout: Two-column design Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>	2026-04-24 07:51:40 +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	9f44cff77b	fix: Stilrichtungen → Fokusbereich Zuordnung (focus_area_id) ... Problem: Stilrichtungen-Tab zeigte falsches Feld 'Übergeordneter Stil' (parent_style_id) Lösung: Fokusbereich-Dropdown (focus_area_id) für Hierarchie Backend (catalogs.py): - INSERT: focus_area_id Parameter hinzugefügt - UPDATE: focus_area_id Parameter hinzugefügt - SELECT: LEFT JOIN focus_areas für focus_area_name + icon - Response enriched mit focus_area_name/icon Frontend (AdminCatalogsPage.jsx): - newTS State: parent_style_id → focus_area_id - Create Form: Fokusbereich-Dropdown statt 'Übergeordneter Stil' - Edit Form: Fokusbereich-Dropdown mit focusAreas - Display: Zeigt Fokusbereich-Icon + Name (accent color) - parent_style_id bleibt für optionale Stil-Hierarchien Jetzt kann Hierarchie korrekt angelegt werden: ✅ Karate → Goju-Ryu ✅ Karate → Shotokan ✅ Gewaltschutz → (eigene Stilrichtungen) version: 0.5.0 module: catalogs 1.5.0, AdminCatalogsPage 2.2.0 Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>	2026-04-23 14:36:02 +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	72c927e69e	feat: Backend API für training_types + Frontend api.js ... Backend (catalogs.py): - GET /api/training-types (Liste) - POST /api/training-types (Erstellen) - PUT /api/training-types/{id} (Bearbeiten) - DELETE /api/training-types/{id} (Löschen mit CASCADE-Check) - Cascade-Protection: Fehler wenn Übungen zugeordnet Frontend (api.js): - listTrainingTypes(filters) - createTrainingType(data) - updateTrainingType(id, data) - deleteTrainingType(id) - Export zum api-Objekt hinzugefügt Pattern: Konsistent mit anderen Katalog-Endpoints CRUD: Volle Admin-Verwaltung Version: 0.4.0	2026-04-23 12:12:48 +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	2a5f06a8f5	feat: Refactor target groups to M:N relationship and update related endpoints	2026-04-23 09:27:13 +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	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	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	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	505a8e5e38	feat: Skills & Methods catalog complete ... Backend: - Created routers/skills.py with full CRUD - Skills: list (with category filter), get, create, update, delete - Methods: list (with category filter), get, create, update, delete - Default: only show active items - Read access: all authenticated users - Write access: admin only - Registered skills router in main.py Frontend: - Complete SkillsPage with 2 tabs (Fähigkeiten, Trainingsmethoden) - Browse by category with cards layout - Admin CRUD forms (importance rating for skills, duration/group size for methods) - Mobile-responsive grid layout - Updated api.js with all skill/method functions - Added /skills route to App.jsx Migration already exists: 003_catalogs.sql (skills, training_methods + seed data) Next: Training Planning (core feature)	2026-04-22 16:50:31 +02:00
Lars	8e027e02bb	feat: Clubs & Organization Management complete ... Backend: - Created routers/clubs.py with full CRUD - Clubs: list, get, create, update, delete (admin only) - Divisions: list, create, update, delete (admin only) - Training Groups: list, get, create, update, delete (admin/trainer) - Registered clubs router in main.py - Permission checks: admin for clubs/divisions, trainer for groups Frontend: - Complete ClubsPage with 3 tabs (Vereine, Sparten, Gruppen) - Role-based UI (admin sees all actions, trainer can manage groups) - Full CRUD forms with modals - Mobile-responsive card layouts - Updated api.js with all club/division/group functions Migration already exists: 002_organization.sql (clubs, divisions, training_groups) Next: Skills & Methods display (read-only)	2026-04-22 16:48:02 +02:00
Lars	8c7cf91cef	feat: Exercise CRUD complete ... Backend: - Registered exercises router in main.py - Migration 005 already created (exercises, exercise_skills, exercise_variants, exercise_media) - Full CRUD endpoints with visibility logic Frontend: - Complete ExercisesPage with list/create/edit/delete - Filter controls (focus_area, visibility, status) - Modal form with all fields - Skills multi-select - Mobile-responsive card layout Next: Clubs Management	2026-04-22 16:44:32 +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	356ab18ec0	fix: Add /profiles/me endpoint for session persistence ... - AuthContext checks /profiles/me on mount to restore session - Without this endpoint, users had to re-login on every refresh - Returns current user's profile based on auth token Issue: Session persistence broken	2026-04-22 15:46:40 +02:00
Lars	08326bdcc6	fix: Remove Mitai-specific columns from session query	2026-04-22 06:56:57 +02:00
Lars	33032ac6c2	fix: Change created to created_at in sessions INSERT	2026-04-21 21:18:09 +02:00
Lars	88677ea29f	fix: Add missing auth columns to profiles table	2026-04-21 21:07:52 +02:00
Lars	9feead99ac	fix: Remove double prefix in router registration	2026-04-21 16:12:25 +02:00
Lars	da634d813c	fix: Add ProfileCreate and ProfileUpdate models	2026-04-21 16:05:42 +02:00
Lars	e1397277a7	fix: Add missing password reset models to models.py	2026-04-21 16:04:22 +02:00
Lars	efc2a11a76	feat: Add Auth system with Login UI ... Backend: - Auth router (login, register, logout) - Profiles router (get current profile) - Registered in main.py Frontend: - LoginPage with login/register tabs - Dashboard with welcome screen - Simplified AuthContext for Shinkan - Protected routes in App.jsx - Public routes redirect when logged in Ready for testing! version: 0.1.0	2026-04-21 14:56:16 +02:00
Lars	fd5efa8662	feat: Add automatic migrations system ... - New run_migrations.py script - Runs all SQL files in migrations/ on startup - Tracks executed migrations in schema_migrations table - Retries database connection (30 attempts) - Separate Shinkan DB (shinkan_dev / shinkan) This ensures a clean separation from Mitai database.	2026-04-21 14:49:28 +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
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