57 lines
2.7 KiB
Markdown
57 lines
2.7 KiB
Markdown
Trainlog v0.1.4 extends the local-first training workflow with factual
|
|
analysis, a synchronized Sleep Diary, improved prepared-session execution, and
|
|
an authenticated Bluetooth synchronization transport.
|
|
|
|
## Analyse and Dashboard
|
|
|
|
- The local Web Analyse workspace exposes factual 7/30/90-day and all-history
|
|
views through Trainlog Core.
|
|
- Activity, active-Program progress, compatible exercise metrics, persisted MAX
|
|
results, BODY ZONE exposure, and body measurements share the bounded Core
|
|
read model used by Dashboard summaries.
|
|
- Body-measurement trends are charted from persisted observations, and the next
|
|
session projection refreshes after synchronization.
|
|
- Analyse deliberately does not invent readiness, fatigue, recovery, body-fat,
|
|
or estimated performance values.
|
|
|
|
## Sleep Diary
|
|
|
|
- Sleep Diary V1 is available across desktop schema v29 and Android schema v26.
|
|
- Entries use absolute timestamped events, causal revisions, appreciations,
|
|
notes, medication catalog entries, and timestamped intake snapshots.
|
|
- The Web agenda uses one exact 18:00-to-18:00 projection and follows the latest
|
|
locally persisted revision without leaking another selected night.
|
|
- Local vector PDF reports are available in French and English.
|
|
- Sleep Diary participates in the full-generation synchronization and
|
|
acknowledgement flow.
|
|
|
|
## Android session execution
|
|
|
|
- Prepared continuous-duration exercises remain planning-only until actual work
|
|
is explicitly recorded.
|
|
- Target-only continuous and set-based occurrences can be edited without
|
|
fabricating performed activity or duplicate occurrences.
|
|
- Equipment can be created and selected from the active-session editor while
|
|
preserving the current durable draft.
|
|
- Program provenance is preserved through preparation, Android execution,
|
|
completion, synchronization, and progress display, including safe recovery
|
|
of compatible historical deliveries.
|
|
|
|
## Bluetooth synchronization
|
|
|
|
- The paired deployment adds Bluetooth Classic RFCOMM as the primary local
|
|
Trainlog synchronization transport and retains direct MTP as wired recovery.
|
|
- The desktop accepts only the configured bonded Android device, and Android
|
|
proves the persisted Trainlog peer identity before exchanging bounded frames.
|
|
- Reconnect noise is rate-limited and does not create repeated generations.
|
|
- This Bluetooth feature transports Trainlog synchronization data only.
|
|
Heart-rate sensor ingestion is intentionally deferred to the 0.1.5 cardio
|
|
cycle.
|
|
|
|
## Assets
|
|
|
|
- `trainlog-android-v0.1.4.apk`: signed public Android APK.
|
|
- `trainlog-tui-linux-x86_64-v0.1.4`: Linux x86-64 runtime bundle containing
|
|
the TUI, local Web adapter, synchronization helpers, Bluetooth transport
|
|
helper, and required catalogs.
|
|
- `SHA256SUMS`: SHA-256 checksums for both artifacts.
|