290 Commits

This Branch

This Branch

All Branches

Author	SHA1	Message	Date
Lars	c9e4b6aa02	debug: diagnostic script for Migration 024 state	2026-03-27 07:39:18 +01:00
Lars	8be87bfdfb	fix: Remove broken table_exists check ... Removed faulty EXISTS check that was causing "0" error. Added debug logging and better error messages. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>	2026-03-27 07:34:29 +01:00
Lars	484c25575d	feat: manual migration 024 runner script ... Allows running Migration 024 manually if auto-migration failed. Usage: python backend/run_migration_024.py Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>	2026-03-27 07:28:43 +01:00
Lars	bbee44ecdc	fix: Better error handling for goal types loading ... - Check if goal_type_definitions table exists - Detailed error messages - Fallback if goalTypes is empty - Prevent form opening without types Helps debugging Migration 024 issues. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>	2026-03-27 07:28:14 +01:00
Lars	043bed4323	docs: Phase 1.5 complete - update roadmap ... Phase 1.5 (Flexible Goal System) erfolgreich abgeschlossen: - 8h Aufwand (geplant 8-12h) - Alle Tasks ✅ - System vollständig flexibel - Phase 0b ready to start Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>	2026-03-27 06:52:18 +01:00
Lars	640ef81257	feat: Phase 1.5 - Flexible Goal System (DB-Registry) Part 2/2 - COMPLETE ... Frontend dynamic goal types + Admin UI komplett implementiert. Frontend GoalsPage: - HARDCODED GOAL_TYPES entfernt - Dynamic loading von goal_type_definitions via API - goalTypes state + goalTypesMap für quick lookup - Dropdown zeigt alle aktiven Types aus DB - Vollständig flexibel - neue Types sofort verfügbar Admin UI: - AdminGoalTypesPage.jsx (400+ Zeilen) → Übersicht aller Goal Types (System + Custom) → Create/Edit/Delete Forms → CRUD via api.js (admin-only) → Validierung: System Types nur deaktivierbar, nicht löschbar → 8 Aggregationsmethoden im Dropdown → Category-Auswahl (body, mind, activity, nutrition, recovery, custom) - Route registriert: /admin/goal-types - Import in App.jsx Phase 1.5 KOMPLETT: ✅ Migration 024 (goal_type_definitions) ✅ Universal Value Fetcher (goal_utils.py) ✅ CRUD API (goals.py) ✅ Frontend Dynamic Dropdown (GoalsPage.jsx) ✅ Admin UI (AdminGoalTypesPage.jsx) System ist jetzt VOLLSTÄNDIG FLEXIBEL: - Neue Goal Types via Admin UI ohne Code-Deploy - Beispiele: Meditation, Trainingshäufigkeit, Planabweichung - Phase 0b Platzhalter können alle Types nutzen - Keine Doppelarbeit bei v2.0 Redesign Nächster Schritt: Testing + Phase 0b (120+ Platzhalter) Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>	2026-03-27 06:51:46 +01:00
Lars	65ee5f898f	feat: Phase 1.5 - Flexible Goal System (DB-Registry) Part 1/2 ... KRITISCHE ARCHITEKTUR-ÄNDERUNG vor Phase 0b: Ermöglicht dynamische Goal Types ohne Code-Änderungen. Backend: - Migration 024: goal_type_definitions Tabelle → 8 existierende Typen als Seed-Data migriert → Flexible Schema: source_table, aggregation_method, calculation_formula → System vs. Custom Types (is_system flag) - goal_utils.py: Universal Value Fetcher → get_current_value_for_goal() ersetzt hardcoded if/elif chain → Unterstützt: latest, avg_7d, avg_30d, sum_30d, count_7d, etc. → Komplexe Formeln (lean_mass) via calculation_formula JSON - goals.py: CRUD API für Goal Type Definitions → GET /goals/goal-types (public) → POST/PUT/DELETE /goals/goal-types (admin-only) → Schutz für System-Types (nicht löschbar) - goals.py: _get_current_value_for_goal_type() delegiert zu Universal Fetcher Frontend: - api.js: 4 neue Funktionen (listGoalTypeDefinitions, create, update, delete) Dokumentation: - TODO_GOAL_SYSTEM.md: Phase 1.5 hinzugefügt, Roadmap aktualisiert Part 2/2 (nächster Commit): - Frontend: Dynamic Goal Types Dropdown - Admin UI: Goal Type Management Page - Testing Warum JETZT (vor Phase 0b)? - Phase 0b Platzhalter (120+) nutzen Goals für Score-Berechnungen - Flexible Goals → automatisch in Platzhaltern verfügbar - Später umbauen = Doppelarbeit (alle Platzhalter anpassen) Zukünftige Custom Goals möglich: - 🧘 Meditation (min/Tag) - 📅 Trainingshäufigkeit (x/Woche) - 📊 Planabweichung (%) - 🎯 Ritual-Adherence (%) Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>	2026-03-27 06:45:05 +01:00
Lars	27a8af7008	debug: Add logging and warnings for Goal System issues ... Based on test feedback - 3 issues addressed: 1. Primary Toggle (Frontend Debug): - Add console.log in handleSaveGoal - Shows what data is sent to backend - Helps debug if checkbox state is correct 2. Lean Mass Display (Backend Debug): - Add error handling in lean_mass calculation - Log why calculation fails (missing weight/bf data) - Try-catch for value conversion errors 3. BP/Strength/Flexibility Warning (UI): - Yellow warning box for incomplete goal types - BP: "benötigt 2 Werte (geplant für v2.0)" - Strength/Flexibility: "Keine Datenquelle" - Transparent about limitations Next: User re-tests with debug output to identify root cause. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>	2026-03-27 06:24:40 +01:00
Lars	14d80fc903	docs: zentrale TODO-Liste für Goal System erstellt ... Tracking-Dokument für alle offenen Punkte: - Phase 0b Tasks (120+ Platzhalter) - v2.0 Redesign Probleme - Gitea Issues Referenzen - Timeline & Roadmap Verhindert dass wichtige Punkte vergessen werden. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>	2026-03-27 06:17:57 +01:00
Lars	87464ff138	fix: Phase 1 - Goal System Quick Fixes + Abstraction Layer ... Behebt 4 kritische Bugs in Phase 0a und schafft Basis für Phase 0b ohne spätere Doppelarbeit. Backend: - NEW: goal_utils.py mit get_focus_weights() Abstraction Layer → V1: Mappt goal_mode zu Gewichten → V2 (später): Liest aus focus_areas Tabelle → Phase 0b Platzhalter (120+) müssen NICHT umgeschrieben werden - FIX: Primary goal toggle in goals.py (is_primary im GoalUpdate Model) → Beim Update auf primary werden andere Goals korrekt auf false gesetzt - FIX: lean_mass current_value Berechnung implementiert → weight - (weight * body_fat_pct / 100) - FIX: VO2Max Spaltenname vo2_max (statt vo2max) → Internal Server Error behoben CLAUDE.md: - Version Update: Phase 1 Fixes (27.03.2026) Keine Doppelarbeit: - Alle zukünftigen Phase 0b Platzhalter nutzen get_focus_weights() - v2.0 Redesign = nur eine Funktion ändern, nicht 120+ Platzhalter Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>	2026-03-27 06:13:47 +01:00
Lars	e3f1e399c2	docs: Goal System Redesign v2.0 - comprehensive concept ... Created comprehensive redesign document addressing all identified issues: Problems addressed: 1. Primary goal too simplistic → Weight system (0-100%) 2. Single goal mode too simple → Multi-mode with weights 3. Missing current values → All goal types with data sources 4. Abstract goal types → Concrete, measurable goals 5. Blood pressure single value → Compound goals (systolic/diastolic) 6. No user guidance → Norms, examples, age-specific values New Concept: - Focus Areas: Weighted distribution (30% weight loss + 25% endurance + ...) - Goal Weights: Each goal has individual weight (not binary primary/not) - Concrete Goal Types: cooper_test, pushups_max, squat_1rm, etc. - Compound Goals: Support for multi-value targets (BP: 120/80) - Guidance System: Age/gender-specific norms and examples Schema Changes: - New table: focus_areas (replaces single goal_mode) - goals: Add goal_weight, target_value_secondary, current_value_secondary - goals: Remove is_primary (replaced by weight) UI/UX Redesign: - Slider interface for focus areas (must sum to 100%) - Goal editor with guidance and norms - Weight indicators on all goals - Special UI for compound goals Implementation Phases: 16-21h total - Phase 2: Backend Redesign (6-8h) - Phase 3: Frontend Redesign (8-10h) - Phase 4: Testing & Refinement (2-3h) Status: WAITING FOR USER FEEDBACK & APPROVAL Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>	2026-03-26 22:05:05 +01:00
Lars	3dd10d3dc7	docs: Phase 0a completion - comprehensive documentation ... CLAUDE.md: - Version updated to v9e+ (Phase 0a Goal System Complete) - Added Phase 0a feature section with full details - Updated 'Letzte Updates' with Phase 0a completion - Links to new documentation files docs/issues/issue-50-phase-0a-goal-system.md (NEW): - Complete Phase 0a implementation documentation - Technical details: Migration 022, goals.py, GoalsPage - 4 commits documented (337667f to 5be52bc) - Lessons learned section - Basis for Phase 0b documented - Testing checklist + acceptance criteria docs/NEXT_STEPS_2026-03-26.md (NEW): - Comprehensive planning document - Option A: Issue #49 - Prompt Page Assignment (6-8h) - Option B: Phase 0b - Goal-Aware Placeholders (16-20h) - Option C: Issue #47 - Value Table Refinement (4-6h) - Recommendation: Szenario 1 (Quick Wins first) - Detailed technical breakdown for both options - Timeline estimates (4h/day vs 8h/day) - 120+ placeholder categorization for Phase 0b All documentation reflects current state post Phase 0a. Next decision: Choose between Issue #49 or Phase 0b. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>	2026-03-26 21:49:07 +01:00
Lars	5be52bcfeb	feat: goals navigation + UX improvements ... Analysis Page: - Add 'Ziele' button next to page title - Direct navigation to /goals from analysis page - Thematic link: goals influence AI analysis weighting Goals Page: - Fix text-align for text inputs (name, date, description) - Text fields now left-aligned (numbers remain right-aligned) - Better UX for non-numeric inputs Navigation strategy: Goals accessible from Analysis page where goal_mode directly impacts score calculation and interpretation. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>	2026-03-26 16:50:22 +01:00
Lars	75f0a5dd6e	refactor: mobile-friendly goal form design ... - Full-width inputs throughout the form - Labels above inputs (mobile best practice) - Section headers with emoji (🎯 Zielwert) - Consistent spacing (marginBottom: 16) - Read-only unit display as styled badge - Primary goal checkbox in highlighted section - Full-width buttons (btn-full class) - Scrollable modal with top padding - Error display above form Matches VitalsPage design pattern for consistency. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>	2026-03-26 16:32:37 +01:00
Lars	906a3b7cdd	fix: Migration 022 - remove invalid schema_migrations tracking ... The migration system tracks migrations via filename automatically. Removed manual DO block that used wrong column name (version vs filename). Also removed unused json import from goals.py. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>	2026-03-26 16:26:48 +01:00
Lars	337667fc07	feat: Phase 0a - Minimal Goal System (Strategic + Tactical) ... - Strategic Layer: Goal modes (weight_loss, strength, endurance, recomposition, health) - Tactical Layer: Concrete goal targets with progress tracking - Training phases (manual + auto-detection framework) - Fitness tests (standardized performance tracking) Backend: - Migration 022: goal_mode in profiles, goals, training_phases, fitness_tests tables - New router: routers/goals.py with full CRUD for goals, phases, tests - API endpoints: /api/goals/* (mode, list, create, update, delete) Frontend: - GoalsPage: Goal mode selector + goal management UI - Dashboard: Goals preview card with link - API integration: goal mode, CRUD operations, progress calculation Basis for 120+ placeholders and goal-aware analyses (Phase 0b) Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>	2026-03-26 16:20:35 +01:00
Lars	ae93b9d428	docs: goal system priority analysis - hybrid approach ... Key Decision: Minimal Goal System BEFORE Placeholders Critical Finding: - Same data = different interpretation per goal - Example: -5kg FM, -2kg LBM - weight_loss: 78/100 (good!) - strength: 32/100 (LBM loss critical!) - Without goal: 50/100 (generic, wrong for both) Recommended Approach (Hybrid): 1. Phase 0a (2-3h): Minimal Goal System - DB: goal_mode field - API: Get/Set Goal - UI: Goal Selector - Default: health 2. Phase 0b (16-20h): Goal-Aware Placeholders - 84 placeholders with goal-dependent calculations - Scores use goal_mode from day 1 - No rework needed later 3. Phase 2+ (6-8h): Full Goal System - Goal recognition from patterns - Secondary goals - Goal progression tracking Why Hybrid Works: ✅ Charts show correct interpretations immediately ✅ No rework of 84 placeholders later ✅ Goal recognition can come later (needs placeholders anyway) ✅ System is "smart coach" from day 1 File: docs/GOAL_SYSTEM_PRIORITY_ANALYSIS.md (650 lines)	2026-03-26 16:08:00 +01:00
Lars	8398368ed7	docs: comprehensive functional concept analysis ... Analysis Results: - 84 new placeholders needed from Fachkonzept - Issues #26 & #27 too narrow (complementary, not conflicting) - Recommend 4-phase approach: Placeholders → Charts → Rules → KI - Transform: Data Collector → Active Coach Key Findings: - Fachkonzept defines 3 levels (Deskriptiv, Diagnostisch, Präskriptiv) - 18 dedicated charts (K1-K5, E1-E5, A1-A8, C1-C6) - Goal-mode dependent interpretation - Lag-based correlations mandatory - Confidence & data quality essential Recommended Actions: - Create Issues #52-55 (Baseline, Scores, Correlations, Metrics) - Expand #26 & #27 based on Fachkonzept - Start Phase 0: Implement 84 placeholders File: docs/KONZEPT_ANALYSE_2026-03-26.md (385 lines)	2026-03-26 15:26:12 +01:00
Lars	cd2609da7c	feat: Feature Request #49 - Prompt-Zuordnung zu Verlaufsseiten ... UX Enhancement: Kontextbezogene KI-Analysen Features: - Prompts auf Verlaufsseiten verfügbar machen - Mehrfachauswahl: Prompt auf mehreren Seiten - Inline-Analyse via Modal - Wiederverwendbare PagePrompts Komponente Technisch: - DB: available_on JSONB column - API: GET /api/prompts/for-page/{page_slug} - UI: Page-Auswahl im Prompt-Editor Aufwand: 6-8h, Priority: Medium Gitea: Issue #49	2026-03-26 15:12:39 +01:00
Lars	39db23d417	docs: comprehensive status report 26.03.2026 ... Audit Results: - 2 Issues closed: #28 (AI-Prompts), #44 (Delete bug) - 1 Issue created: #47 (Value Table Refinement) - 12 commits today, 3 major features completed - All documentation synchronized with Gitea Next: Testing on dev, then Production deployment	2026-03-26 14:53:45 +01:00
Lars	582f125897	docs: comprehensive status update and Gitea sync ... Updates: - Clarify Gitea issue references (prefix with 'Gitea #') - Mark #28 (AI-Prompts) as CLOSED - Mark #44 (Delete insights) as CLOSED - Update #47 reference (Wertetabelle Optimierung) - Add 'Letzte Updates' section for 26.03.2026 - Document Issue-Management responsibility Gitea Actions: - Closed Issue #28 with completion comment - Closed Issue #44 with fix details - Created Issue #47 (Wertetabelle Optimierung)	2026-03-26 14:52:44 +01:00
Lars	21bdd9f2ba	docs: add Claude Code responsibilities section ... - Issue-Management via Gitea API - Dokumentation pflegen - Entwicklungs-Workflow	2026-03-26 14:46:20 +01:00
Lars	713f7475c9	docs: create Issue #50 - Value Table Refinement ... - Normal-Modus: Nur Einzelwerte (übersichtlich) - Experten-Modus: Zusätzlich Stage-Rohdaten - Beschreibungen für alle Platzhalter vervollständigen - Schema-basierte Beschreibungen für extrahierte Werte Aufwand: 4-6h, Priority: Medium	2026-03-26 14:43:23 +01:00
Lars	6e651b5bb5	fix: include stage outputs in debug info for value table ... - stage_debug now includes 'output' dict with all stage outputs - Fixes empty values for stage_X_outputkey in expert mode - Stage outputs are the actual AI responses passed to next stage	2026-03-26 14:33:00 +01:00
Lars	f37936c84d	feat: show all stage outputs as collapsible JSON in expert mode ... Backend: - Add ALL stage outputs to metadata (not just referenced ones) - Format JSON with indent for readability - Description: 'Zwischenergebnis aus Stage X' Frontend: - Stage raw values shown in collapsible <details> element - JSON formatted in <pre> tag with syntax highlighting - 'JSON anzeigen ▼' summary for better UX Fixes: Stage X - Rohdaten now shows intermediate results	2026-03-26 13:17:58 +01:00
Lars	159fcab17a	feat: circ_summary with best-of-each strategy and age annotations ... - Each circumference point shows most recent value (even from different dates) - Age annotations: heute, gestern, vor X Tagen/Wochen/Monaten - Gives AI better context about measurement freshness - Example: 'Brust 105cm (heute), Nacken 38cm (vor 2 Wochen)'	2026-03-26 13:09:38 +01:00
Lars	d06d3d84de	fix: circ_summary now checks all 8 circumference points ... - Previously only checked c_chest, c_waist, c_hip - Now includes c_neck, c_belly, c_thigh, c_calf, c_arm - Fixes 'keine Daten' when entries exist with only non-primary measurements	2026-03-26 13:06:37 +01:00
Lars	b0f80e0be7	docs: document Issue #47 completion in CLAUDE.md ... - Added comprehensive documentation for Value Table feature - Expert mode, category grouping, stage output extraction - Updated version header to reflect #28 and #47 completion	2026-03-26 13:03:49 +01:00
Lars	adb5dcea88	feat: category grouping in value table (Issue #47) ... FEATURE: Gruppierung nach Kategorien - Wertetabelle jetzt nach Modulen/Kategorien gruppiert - Bessere Übersicht und Zuordnung der Werte BACKEND: Category Metadata - Für normale Platzhalter: Kategorie aus Catalog (Profil, Körper, Ernährung, etc.) - Für extrahierte Werte: "Stage X - [Output Name]" - Für Rohdaten: "Stage X - Rohdaten" - Fallback: "Sonstiges" FRONTEND: Grouped Display - sortedCategories: Sortierung (Normal → Stage Outputs → Rohdaten) - Section Headers: Grauer Hintergrund mit Kategorie-Name - React.Fragment für Gruppierung SORTIERUNG: 1. Normale Kategorien (Profil, Körper, Ernährung, Training, etc.) 2. Stage Outputs (Stage 1 - Body, Stage 1 - Nutrition, etc.) 3. Rohdaten (Stage 1 - Rohdaten, Stage 2 - Rohdaten) 4. Innerhalb: Alphabetisch BEISPIEL: ┌────────────────────────────────────────────┐ │ PROFIL │ ├────────────────────────────────────────────┤ │ name │ Lars │ Name des Nutzers │ │ age │ 55 │ Alter in Jahren │ ├────────────────────────────────────────────┤ │ KÖRPER │ ├────────────────────────────────────────────┤ │ weight_... │ 85.2 kg │ Aktuelles Gewicht │ │ bmi │ 26.6 │ Body Mass Index │ ├────────────────────────────────────────────┤ │ ERNÄHRUNG │ ├────────────────────────────────────────────┤ │ kcal_avg │ 1427... │ Durchschn. Kalorien│ │ protein... │ 106g... │ Durchschn. Protein │ ├────────────────────────────────────────────┤ │ STAGE 1 - BODY │ ├────────────────────────────────────────────┤ │ ↳ bmi │ 26.6 │ Aus Stage 1 (body) │ │ ↳ trend │ sinkend │ Aus Stage 1 (body) │ ├────────────────────────────────────────────┤ │ STAGE 1 - NUTRITION │ ├────────────────────────────────────────────┤ │ ↳ kcal_... │ 1427 │ Aus Stage 1 (nutr.)│ └────────────────────────────────────────────┘ Experten-Modus zusätzlich: ├────────────────────────────────────────────┤ │ STAGE 1 - ROHDATEN │ ├────────────────────────────────────────────┤ │ 🔬 stage...│ {"bmi"..│ Rohdaten Stage 1 │ └────────────────────────────────────────────┘ version: 9.10.0 (feature) module: prompts 2.5.0, insights 1.8.0	2026-03-26 12:59:52 +01:00
Lars	da803da816	feat: extract individual values from stage outputs (Issue #47) ... FEATURE: Basis-Analysen Einzelwerte Vorher: stage_1_body → {"bmi": 26.6, "weight": "85.2kg"} (1 Zeile) Jetzt: bmi → 26.6 (eigene Zeile) weight → 85.2kg (eigene Zeile) BACKEND: JSON-Extraktion - Stage outputs (JSON) → extract individual fields - extracted_values dict sammelt alle Einzelwerte - Deduplizierung: Gleiche Keys nur einmal - Flags: - is_extracted: true → Wert aus Stage-Output extrahiert - is_stage_raw: true → Rohdaten (JSON) nur Experten-Modus BEISPIEL Stage 1 Output: { "stage_1_body": { "bmi": 26.6, "weight": "85.2 kg", "trend": "sinkend" } } → Metadata: { "bmi": { value: "26.6", description: "Aus Stage 1 (stage_1_body)", is_extracted: true }, "weight": { value: "85.2 kg", description: "Aus Stage 1 (stage_1_body)", is_extracted: true }, "stage_1_body": { value: "{\"bmi\": 26.6, ...}", description: "Rohdaten Stage 1 (Basis-Analyse JSON)", is_stage_raw: true } } FRONTEND: Smart Filtering Normal-Modus: - Zeigt: Einzelwerte (bmi, weight, trend) - Versteckt: Rohdaten (stage_1_body JSON) - Filter: is_stage_raw === false Experten-Modus: - Zeigt: Alles (Einzelwerte + Rohdaten) - Rohdaten: Grauer Hintergrund + 🔬 Icon VISUAL Indicators: ↳ bmi → Extrahierter Wert (grün) weight → Normaler Platzhalter (accent) 🔬 stage_1_* → Rohdaten JSON (grau, klein, nur Experten) ERGEBNIS: ┌──────────────────────────────────────────┐ │ 📊 Verwendete Werte (8) (+2 ausgeblendet)│ │ ┌────────────────────────────────────────┐│ │ │ weight_aktuell │ 85.2 kg │ Gewicht ││ ← Normal │ │ ↳ bmi │ 26.6 │ Aus St..││ ← Extrahiert │ │ ↳ trend │ sinkend │ Aus St..││ ← Extrahiert │ └────────────────────────────────────────┘│ └──────────────────────────────────────────┘ Experten-Modus zusätzlich: │ 🔬 stage_1_body │ {"bmi":...│ Rohdaten││ ← JSON version: 9.9.0 (feature) module: prompts 2.4.0, insights 1.7.0	2026-03-26 12:55:53 +01:00
Lars	e799edbae4	feat: expert mode + stage outputs in value table (Issue #47) ... FEATURE: Experten-Modus 🔬 - Toggle-Button in Wertetabelle - Normal: Nur gefüllte Werte anzeigen - Experten: Alle Platzhalter inkl. leere/technische - Anzeige: "(+X ausgeblendet)" wenn Werte gefiltert - Button-Style: Accent wenn aktiv FILTER: Leere Werte ausblenden (Normal-Modus) - Filtert: '', 'nicht verfügbar', '[Nicht verfügbar]' - Zeigt nur relevante Nutzer-Daten - Experten-Modus zeigt alles FEATURE: Stage-Outputs in Wertetabelle ✅ ROOT CAUSE: stage_N_key Platzhalter hatten keine Werte - Stage-Outputs (z.B. stage_1_body) sind Basis-Analysen-Ergebnisse - Wurden nicht in cleaned_values gefunden (nur statische Platzhalter) FIX: - Collect stage outputs aus result.debug.stages[].output - Store als stage_N_key dict - Lookup: erst stage_outputs, dann cleaned_values - Description: "Output aus Stage X (Basis-Analyse)" - JSON-Werte automatisch serialisiert BEISPIEL Pipeline-Wertetabelle: ┌──────────────────────────────────────────────┐ │ 📊 Verwendete Werte (8) (+3 ausgeblendet) 🔬│ │ ┌──────────────────────────────────────────┐ │ │ │ weight_aktuell │ 85.2 kg │ Gewicht │ │ │ │ stage_1_body │ {"bmi":...│ Output...│ │ ← Stage output! │ │ stage_1_nutr... │ {"kcal"...│ Output...│ │ │ └──────────────────────────────────────────┘ │ └──────────────────────────────────────────────┘ AKTIVIERUNG Experten-Modus: 1. Analyse öffnen 2. "📊 Verwendete Werte" aufklappen 3. Button "🔬 Experten-Modus" klicken 4. Zeigt alle Platzhalter (auch leere stage outputs) version: 9.8.0 (feature) module: prompts 2.3.0, insights 1.6.0	2026-03-26 12:44:28 +01:00
Lars	15bd6cddeb	feat: untruncated values + smart base prompt display (Issue #47) ... FEATURE: Volle Werte (nicht abgeschnitten) - Backend holt ungekürzten Werte direkt von placeholder_resolver - get_placeholder_example_values() statt debug.resolved_placeholders - Debug bleibt gekürzt (100 chars), Metadata ungekürzt FEATURE: Smart Display für Basis-Prompts - Basis-Prompts mit JSON-Output: Nur Wertetabelle anzeigen - JSON-Output in Collapsible "Technische Daten" verschoben - Wertetabelle auto-expanded bei Basis-Prompts - Pipeline + Text-Prompts: Wie bisher (Content + Wertetabelle) UI: Bessere Wertetabelle - Werte: word-break + max-width (400px) → kein Overflow - Alle Spalten: verticalAlign top für bessere Lesbarkeit - Platzhalter: nowrap (keine Umbrüche) BEISPIEL: ┌─────────────────────────────────────────┐ │ ℹ️ Basis-Prompt Rohdaten │ │ [Technische Daten anzeigen ▼] │ │ │ │ 📊 Verwendete Werte (8) ▼ ← expanded │ │ ┌──────────────────────────────────────┐│ │ │ Platzhalter │ Vollständiger Wert... ││ │ │ kcal_avg │ 1427 kcal/Tag (Ø 30...││ ← ungekürzt │ └──────────────────────────────────────┘│ └─────────────────────────────────────────┘ version: 9.7.0 (feature) module: prompts 2.2.0, insights 1.5.0	2026-03-26 12:37:52 +01:00
Lars	19414614bf	fix: add metadata to newResult for immediate value table display ... BUG: Wertetabelle wurde nicht angezeigt bei neuer Analyse ROOT CAUSE: newResult hatte nur {scope, content}, kein metadata FIX: Build metadata from result.debug.resolved_placeholders - Für Base: direkt aus resolved_placeholders - Für Pipeline: collect aus allen stages - Metadata structure: {prompt_type, placeholders: {key: {value, description}}} NOTE: Immediate preview hat keine descriptions (nur values) Saved insights (nach loadAll) haben full metadata with descriptions aus DB version: 9.6.2 (bugfix)	2026-03-26 12:29:05 +01:00
Lars	4a2bebe249	fix: value table metadata + |d modifier + cursor insertion (Issues #47, #48) ... BUG: Wertetabelle wurde nicht angezeigt FIX: enable_debug=true wenn save=true (für metadata collection) - metadata wird nur gespeichert wenn debug aktiv - jetzt: debug or save → metadata immer verfügbar BUG: {{placeholder|d}} Modifier funktionierte nicht ROOT CAUSE: catalog wurde bei Exception nicht zu variables hinzugefügt FIX: - variables['_catalog'] = catalog (auch wenn None) - Warning-Log wenn catalog nicht geladen werden kann - Debug warning wenn |d ohne catalog verwendet BUG: Platzhalter in Pipeline-Stages am Ende statt an Cursor FIX: - stageTemplateRefs Map für alle Stage-Textareas - onClick + onKeyUp tracking für Cursor-Position - Insert at cursor: template.slice(0, pos) + placeholder + template.slice(pos) - Focus + Cursor restore nach Insert TECHNICAL: - prompt_executor.py: Besseres Exception Handling für catalog - UnifiedPromptModal.jsx: Refs für alle Template-Felder - prompts.py: enable_debug=debug or save version: 9.6.1 (bugfix) module: prompts 2.1.1	2026-03-26 12:04:20 +01:00
Lars	c0a50dedcd	feat: value table + {{placeholder|d}} modifier (Issue #47) ... FEATURE #47: Wertetabelle nach KI-Analysen - Migration 021: metadata JSONB column in ai_insights - Backend sammelt resolved placeholders mit descriptions beim Speichern - Frontend: Collapsible value table in InsightCard - Zeigt: Platzhalter | Wert | Beschreibung - Sortiert tabellarisch - Funktioniert für base + pipeline prompts FEATURE #48: {{placeholder|d}} Modifier - Syntax: {{weight_aktuell|d}} → "85.2 kg (Aktuelles Gewicht in kg)" - resolve_placeholders() erkennt |d modifier - Hängt description aus catalog an Wert - Fein-granulare Kontrolle pro Platzhalter (nicht global) - Optional: nur wo sinnvoll einsetzen TECHNICAL: - prompt_executor.py: catalog parameter durchgereicht - execute_prompt_with_data() lädt catalog via get_placeholder_catalog() - Catalog als _catalog in variables übergeben, in execute_prompt() extrahiert - Base + Pipeline Prompts unterstützen |d modifier EXAMPLE: Template: "Gewicht: {{weight_aktuell|d}}, Alter: {{age}}" Output: "Gewicht: 85.2 kg (Aktuelles Gewicht in kg), Alter: 55" version: 9.6.0 (feature) module: prompts 2.1.0, insights 1.4.0	2026-03-26 11:52:26 +01:00
Lars	c56d2b2201	fix: delete insights + placeholder cursor insertion (Issue #44) ... BUG #44: Analysen löschen schlug fehl (kein Auth-Token) FIX: - api.deleteInsight() in api.js hinzugefügt - Analysis.jsx nutzt jetzt api.js mit Error-Handling - Nicht mehr raw fetch() ohne Token BUG: Platzhalter wurden am Ende eingefügt statt an Cursor-Position FIX: - useRef für baseTemplateRef hinzugefügt - Cursor-Position tracking (onClick + onKeyUp) - Insert at cursor: template.slice(0, pos) + placeholder + template.slice(pos) - Focus + Cursor-Position nach Insert wiederhergestellt version: 9.5.2 (bugfix) module: prompts 2.0.2, insights 1.3.1	2026-03-26 11:40:19 +01:00
Lars	7daa2e40c7	fix: sleep quality calculation using wrong key (stage vs phase) ... BUG: sleep_avg_quality showed 0% despite valid sleep data ROOT CAUSE: sleep_segments use 'phase' key, not 'stage' FIX: Changed s.get('stage') to s.get('phase') in get_sleep_avg_quality() version: 9.5.1 (bugfix) module: prompts 2.0.1	2026-03-26 10:31:39 +01:00
Lars	ae6bd0d865	docs: Issue #28 completion documentation (v9e) ... - Marked Issue #28 as complete - Documented all 4 original phases - Documented debug tools added 26.03.2026 - Documented placeholder enhancements (6 new functions, 7 reconstructed) - Documented bug fixes (PIPELINE_MASTER, SQL columns, type errors) - Listed related Gitea issues (#43, #44, #45, #46) - Updated version status to v9e Ready for Production version: 9.5.0 (documentation update)	2026-03-26 10:28:42 +01:00
Lars	a43a9f129f	fix: sleep_avg_quality uses lowercase stage names ... Problem: Schlafphasen werden lowercase gespeichert (deep, rem, light, awake), aber get_sleep_avg_quality() prüfte Titlecase (Deep, REM) → 0% Match Fix: Ändere Prüfung zu lowercase: ['deep', 'rem'] Jetzt wird {{sleep_avg_quality}} korrekt berechnet aus JSONB segments. Quelle: backend/routers/sleep.py → phase_map speichert lowercase Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>	2026-03-26 10:22:55 +01:00
Lars	3ad1a19dce	fix: calculate_age now handles PostgreSQL date objects ... Problem: dob Spalte ist DATE (PostgreSQL) → Python bekommt datetime.date, nicht String → strptime() schlägt fehl → age = "unbekannt" Fix: Prüfe isinstance(dob, str) und handle beide Typen: - String → strptime() - date object → direkt verwenden Jetzt funktioniert {{age}} Platzhalter korrekt. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>	2026-03-26 10:19:36 +01:00
Lars	a9114bc40a	feat: implement missing placeholder functions (sleep, vitals, rest) ... Implementiert 6 fehlende Platzhalter-Funktionen die im Katalog waren aber keine Berechnung hatten. Neue Funktionen: - get_sleep_avg_duration(7d) → "7.5h" - get_sleep_avg_quality(7d) → "65% (Deep+REM)" - get_rest_days_count(30d) → "5 Ruhetage" - get_vitals_avg_hr(7d) → "58 bpm" - get_vitals_avg_hrv(7d) → "45 ms" - get_vitals_vo2_max() → "42.5 ml/kg/min" Datenquellen: - sleep_log (JSONB segments mit Deep/REM/Light/Awake) - rest_days (Kraft/Cardio/Entspannung) - vitals_baseline (resting_hr, hrv, vo2_max) Jetzt in PLACEHOLDER_MAP registriert → sofort nutzbar. Fixes: Platzhalter-Export zeigt jetzt alle Werte (statt "nicht verfügbar") Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>	2026-03-26 10:14:17 +01:00
Lars	555ff62b56	feat: global placeholder export with values (Settings page) ... Zentraler Export aller verfügbaren Platzhalter mit aktuellen Werten. Backend: - GET /api/prompts/placeholders/export-values - Returns all placeholders organized by category - Includes resolved values for current profile - Includes metadata (description, example) - Flat list + categorized structure Frontend SettingsPage: - Button "📊 Platzhalter exportieren" - Downloads: placeholders-{profile}-{date}.json - Shows all 38+ placeholders with current values - Useful for: - Understanding available data - Debugging prompt templates - Verifying placeholder resolution Frontend api.js: - exportPlaceholderValues() Export Format: { "export_date": "2026-03-26T...", "profile_id": "...", "count": 38, "all_placeholders": { "name": "Lars", ... }, "placeholders_by_category": { "Profil": [...], "Körper": [...], ... } } Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>	2026-03-26 10:05:11 +01:00
Lars	7f94a41965	feat: batch import/export for prompts (Issue #28 Debug B) ... Dev→Prod Sync in 2 Klicks: Export → Import Backend: - GET /api/prompts/export-all → JSON mit allen Prompts - POST /api/prompts/import?overwrite=true/false → Import + Create/Update - Returns: created, updated, skipped counts - Validates JSON structure - Handles stages JSON conversion Frontend AdminPromptsPage: - Button "📦 Alle exportieren" → downloads all-prompts-{date}.json - Button "📥 Importieren" → file upload dialog - User-Prompt: Überschreiben? Ja/Nein - Success-Message mit Statistik (created/updated/skipped) Frontend api.js: - exportAllPrompts() - importPrompts(data, overwrite) Use Cases: 1. Backup: Prompts als JSON sichern 2. Dev→Prod: Auf dev.mitai entwickeln → exportieren → auf mitai.jinkendo importieren 3. Versionierung: Prompts in Git speichern Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>	2026-03-26 09:44:08 +01:00
Lars	8b287ca6c9	feat: export all placeholders from debug viewer (Issue #28 Debug A) ... Added "📋 Platzhalter exportieren" button in debug viewer: - Exports all resolved placeholders with values - Includes all available_variables - For pipelines: exports per-stage placeholder data - JSON format with timestamp and prompt metadata - Filename: placeholders-{slug}-{date}.json Use case: Development aid - see exactly what data is available for prompt templates without null values. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>	2026-03-26 09:40:26 +01:00
Lars	97e57481f9	fix: Analysis page now uses unified prompt executor (Issue #28) ... BREAKING: Analysis page switched from old /insights/run to new /prompts/execute Changes: - Backend: Added save=true parameter to /prompts/execute - When enabled, saves final output to ai_insights table - Extracts content from pipeline output (last stage) - Frontend api.js: Added save parameter to executeUnifiedPrompt() - Frontend Analysis.jsx: Switched from api.runInsight() to api.executeUnifiedPrompt() - Transforms new result format to match InsightCard expectations - Pipeline outputs properly extracted and displayed Fixes: PIPELINE_MASTER responses (old template being sent to AI) The old /insights/run endpoint used raw template field, which for the legacy "pipeline" prompt was literally "PIPELINE_MASTER". The new executor properly handles stages and data processing. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>	2026-03-26 09:38:58 +01:00
Lars	811ba8b3dc	fix: convert Decimal to float before multiplication in protein targets ... - get_protein_ziel_low: float(weight) * 1.6 - get_protein_ziel_high: float(weight) * 2.2 Fixes TypeError: unsupported operand type(s) for *: 'decimal.Decimal' and 'float' Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>	2026-03-26 09:23:50 +01:00
Lars	b90c738fbb	fix: make test button always visible in prompt editor ... - Removed conditional hiding of test button (prompt?.slug) - Button now always visible with helpful tooltip - handleTest already has save-check logic Improves discoverability of test functionality. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>	2026-03-26 09:16:59 +01:00
Lars	dfaf24d74c	fix: correct SQL column names in placeholder_resolver ... - caliper_summary: use body_fat_pct (not bf_jpl) - circ_summary: use c_chest, c_waist, c_hip (not brust, taille, huefte) - get_latest_bf: use body_fat_pct for consistency Fixes SQL errors when running base prompts that feed pipeline prompts. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>	2026-03-26 09:10:55 +01:00
Lars	0f2b85c6de	fix: reconstruct missing placeholders + fix SQL column names ... Added missing placeholders: - caliper_summary, circ_summary (body measurements) - goal_weight, goal_bf_pct (goals from profile) - nutrition_days (count of nutrition entries) - protein_ziel_low/high (calculated from weight) Fixed SQL errors: - protein → protein_g - fat → fat_g - carb → carbs_g Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>	2026-03-26 09:03:35 +01:00
Lars	f4d1fd4de1	feat: add activity_detail placeholder for detailed activity logs ... - New placeholder: {{activity_detail}} returns formatted activity log - Shows last 20 activities with date, type, duration, kcal, HR - Makes activity analysis prompts work properly Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>	2026-03-26 08:20:18 +01:00