Lars/mitai-jinkendo
1
0
Fork 0
Code Issues 28 Pull Requests Actions Packages Projects Releases 2 Wiki Activity
433 Commits 2 Branches 10 Tags 6.1 MiB
Python 60.3%
JavaScript 36.8%
PLpgSQL 1.6%
Shell 0.7%
CSS 0.5%
485aec40a0
Go to file
Lars 485aec40a0
All checks were successful
Deploy Development / deploy (push) Successful in 46s
Details
Build Test / lint-backend (push) Successful in 1s
Details
Build Test / build-frontend (push) Successful in 13s
Details
feat: Activity Cluster Placeholder Registry - Complete Implementation (17 Placeholders) 
Implements complete placeholder registry for Activity & Training metrics following
Phase 0c Multi-Layer Architecture pattern.

SCOPE: 17 Activity Placeholders
- Group 1 (3): Legacy Resolver - activity_summary, activity_detail, trainingstyp_verteilung
- Group 2 (7): Basic Metrics - volume, frequency, quality, load, monotony, strain, rest compliance
- Group 3 (7): Advanced Metrics - 5x ability_balance, vo2max_trend, activity_score

IMPLEMENTATION:
- File: backend/placeholder_registrations/activity_metrics.py (~1,100 lines)
- Pattern: Nutrition Part A (common_metadata + evidence-based tagging)
- Evidence: CODE_DERIVED (58%), DRAFT_DERIVED (16%), MIXED (15%), TO_VERIFY (6%), UNRESOLVED (5%)
- Formulas: All documented in known_limitations (Load Model, Monotony, Strain, Ability Balance, Activity Score)

CRITICAL ISSUES IDENTIFIED (NOT FIXED per NO LOGIC CHANGES):
1. quality_label field mismatch (quality_sessions_pct) - TO_VERIFY
2. RPE moderate quality mapping bug (proxy_internal_load_7d) - CODE_DERIVED
3. JSONB dependencies (6 placeholders) - ability_balance_*, rest_day_compliance
4. vo2max_trend_28d questionable category (Recovery vs. Activity) - TO_VERIFY

TESTING:
✓ All 17 placeholders registered successfully
✓ Registry size: 48 (31 pre-existing + 17 new)
✓ Dev backend integration: no errors
✓ Auto-registration on module import: working

ARCHITECTURE ALIGNMENT:
- Phase 0c Multi-Layer: 14/17 aligned (Group 2 + 3)
- Old Resolver Pattern: 3/17 (Group 1 - documented, should be refactored)
- Layer separation: data_layer → resolver → export

FILES:
- NEW: backend/placeholder_registrations/activity_metrics.py
- MODIFIED: backend/placeholder_registrations/__init__.py (added import)
- MODIFIED: CLAUDE.md (placeholder registry rules)

DOCUMENTATION:
- Gap Analysis: .claude/task/rework_0b_placeholder/ACTIVITY_CLUSTER_GAP_ANALYSIS.md
- Code Inspection: .claude/task/rework_0b_placeholder/ACTIVITY_CLUSTER_CODE_INSPECTION.md
- Implementation Report: .claude/task/rework_0b_placeholder/ACTIVITY_CLUSTER_IMPLEMENTATION_REPORT.md

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
2026-04-03 08:20:25 +02:00
.gitea/workflows ci: fix workflows - prod deploys to bodytrack/, dev to bodytrack-dev/ 2026-03-17 13:11:53 +01:00
backend feat: Activity Cluster Placeholder Registry - Complete Implementation (17 Placeholders) 2026-04-03 08:20:25 +02:00
docs feat: Placeholder Metadata V2 - Normative Implementation + ZIP Export Fix 2026-03-29 21:23:37 +02:00
frontend feat: Add Placeholder Metadata Export to Admin Panel 2026-03-29 20:37:52 +02:00
nginx feat: initial commit – Mitai Jinkendo v9a 2026-03-16 13:35:11 +01:00
.env.example small update 2026-03-18 09:07:08 +01:00
.gitignore fix: AdminUserRestrictionsPage - use exact TierLimitsPage input system 2026-03-20 11:34:48 +01:00
CLAUDE.md feat: Activity Cluster Placeholder Registry - Complete Implementation (17 Placeholders) 2026-04-03 08:20:25 +02:00
docker-compose.dev-env.yml fix: add missing /app/data volume for SQLite migration 2026-03-18 12:11:37 +01:00
docker-compose.dev.yml feat: initial commit – Mitai Jinkendo v9a 2026-03-16 13:35:11 +01:00
docker-compose.yml docker-compose.yml aktualisiert 2026-03-19 08:28:30 +01:00
find-container.sh chore: rollback point before unified prompt system refactoring (Issue #28) 2026-03-25 10:42:18 +01:00
README.md feat: initial commit – Mitai Jinkendo v9a 2026-03-16 13:35:11 +01:00
SETUP.md feat: initial commit – Mitai Jinkendo v9a 2026-03-16 13:35:11 +01:00
test-pipeline-api.sh chore: add pipeline system test scripts (Issue #28) 2026-03-25 09:47:58 +01:00
test-pipeline-backend.sh fix: use postgres container for psql commands 2026-03-25 09:54:44 +01:00
test-unified-migration.sh fix: migration 020 SQL syntax - correlated subquery issue 2026-03-25 12:58:02 +01:00

README.md

BodyTrack

Körpervermessung & Körperfett Tracker – selbst gehostet, PWA-fähig.

Features

  • Umfänge & Caliper-Messungen (4 Methoden) mit Verlauf
  • Abgeleitete Werte: WHR, WHtR, FFMI, Magermasse
  • Verlaufsdiagramme (Gewicht, KF%, Taille, …)
  • KI-Interpretationen via Claude (Anthropic)
  • Fortschrittsfotos mit Galerie
  • PDF & CSV Export
  • PWA – installierbar auf iPhone-Homescreen
  • Alle Daten lokal auf deinem Server (SQLite)

Schnellstart

1. Voraussetzungen

# Docker & Docker Compose installieren (Ubuntu)
curl -fsSL https://get.docker.com | sh
sudo usermod -aG docker $USER
# Neu einloggen

2. Projekt klonen / kopieren

mkdir ~/bodytrack && cd ~/bodytrack
# Dateien hierher kopieren

3. API Key setzen

cp .env.example .env
nano .env
# ANTHROPIC_API_KEY=sk-ant-... eintragen

4. Starten

docker compose up -d

App läuft auf: http://DEINE-IP:3000

5. iPhone – Als App installieren

  1. Safari öffnen → http://DEINE-IP:3000
  2. Teilen-Button (□↑) → „Zum Home-Bildschirm"
  3. BodyTrack erscheint als App-Icon

6. Von außen erreichbar (optional)

# Tailscale (einfachste Lösung – VPN zu deinem MiniPC)
curl -fsSL https://tailscale.com/install.sh | sh
sudo tailscale up
# Dann: http://TAILSCALE-IP:3000

Updates

docker compose pull
docker compose up -d --build

Backup

# Datenbank & Fotos sichern
docker run --rm -v bodytrack-data:/data -v bodytrack-photos:/photos \
  -v $(pwd):/backup alpine \
  tar czf /backup/bodytrack_backup_$(date +%Y%m%d).tar.gz /data /photos

Konfiguration

Variable Beschreibung Standard
ANTHROPIC_API_KEY Claude API Key (für KI-Analyse) –

Ports

Port Dienst
3000 Frontend (Nginx)
8000 Backend API (intern)