running

Run janus workout add --type running with flags for distance, duration, and optional heart rate, elevation, date, and notes. The CLI generates an rw-NNN identifier and appends the workout to data/workouts.md through an atomic write.

The model emits an ActivityRecord with type WORKOUT_ADDED and workout_type running, then calls ingest_activities. The gateway validates fields, computes a dedup key, and appends the workout atomically to data/workouts.md.

No. Model-driven code must never write to data/ directly or call save_workout. All persistence flows through the activity-ingestion gateway, which uses atomic writes with retry and backup. Only the human-operated CLI path may call save_workout.

Duplicates occur when a WORKOUT_ADDED record lacks both a workout_id and a date, collapsing the dedup key to ::running. Always populate evidence date or record date, and set workout_id when known, so deduplication can reject repeats.

The summary computes total distance, total duration, distance-weighted average pace, best pace, average heart rate from runs with HR data, longest run, and total elevation. Average pace is total duration divided by total distance, not a mean of per-run paces.

No. Wearable sync from Strava, Garmin, or FIT files is a separate integration that must produce ActivityRecord values first. Cross-domain goal metric updates from workouts are not yet wired and remain aspirational.