Danny f36912febe docs: tick off interaction/event logging in ROADMAP

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

2026-04-19 14:04:28 +02:00

BigBiggerBiggestBot — Roadmap

Immediate bugs

#6 Can't save workout with only one exercise — investigate structured editor save path

#1 Hide "next exercise" affordance until current exercise has ≥1 set
Version display in Mini App footer — format YYYY-MM-DD <short-sha>. Primary path uses git log, pure-Python fallback parses .git/HEAD + loose commit objects for environments without git on PATH.
~~Semantic versioning tags — start tagging releases (v0.1.0, v0.2.0, ...) so the footer shows a human version instead of a SHA.~~ Decided against — keeping YYYY-MM-DD <short-sha> format.
#7 Per-user workout numbering display (global ID stays as real key, just display transform). /delete <n> now uses the per-user number too. Deleting renumbers later workouts down.

#2 Superset support in structured editor — backend already supports it; UI needs a "group with previous" toggle or drag-to-group
Exercise name standardization — OHP = shoulder press = military press. Aliases table.
Global exercise name suggestions — autocomplete draws from all users' exercises, ordered by popularity, case-insensitively grouped.
#3 Machine-to-muscle mapping — reference dataset + /machine <id> command. Seeded with gym80 IDs.
Interaction / event logging — structured events table; bot commands, workout save/update/delete, Mini App opens, and per-set additions all record events. POST /api/events endpoint lets the Mini App emit client-side events. Rest-timer prereq done.
Staging via shipyard — new features and fixes must be verified against the shipyard bot (separate Telegram bot) before merging to main and triggering the production deploy.

#8 Workout templates — save/load favorite workouts
Per-exercise history — "show me all my squat sessions"
Mini-app UI polish (loading states, skeleton screens)
News section — surface new features/fixes on release. Delivery TBD: Mini App panel, occasional bot broadcast, or both.
Profile / settings — per-user preferences (language, units, etc.)
Rest timer — show time since the last set was completed (depends on per-set timestamps from the interaction logging item; gated by a profile/settings toggle so users can turn it off).
Cardio tracking — separate data model (duration, distance, pace) alongside strength workouts
About section — Mini App panel with pre-alpha / use-at-own-risk disclaimer, version, license link.

Raw feedback from /feedback command queryable via:

sqlite workouts.db "SELECT * FROM feedback ORDER BY created_at DESC;"