@trainheroic-unofficial/cli 4.0.0 → 4.1.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@trainheroic-unofficial/cli",
|
|
3
|
-
"version": "4.
|
|
3
|
+
"version": "4.1.0",
|
|
4
4
|
"license": "MIT",
|
|
5
5
|
"repository": {
|
|
6
6
|
"type": "git",
|
|
@@ -20,16 +20,16 @@
|
|
|
20
20
|
"skill"
|
|
21
21
|
],
|
|
22
22
|
"dependencies": {
|
|
23
|
-
"zod": "^4.6.
|
|
24
|
-
"@trainheroic-unofficial/dto": "4.
|
|
25
|
-
"@trainheroic-unofficial/js": "4.
|
|
23
|
+
"zod": "^4.6.5",
|
|
24
|
+
"@trainheroic-unofficial/dto": "4.1.0",
|
|
25
|
+
"@trainheroic-unofficial/js": "4.1.0"
|
|
26
26
|
},
|
|
27
27
|
"devDependencies": {
|
|
28
|
-
"@types/node": "^26.
|
|
28
|
+
"@types/node": "^26.6.4",
|
|
29
29
|
"tsdown": "^0.23.0",
|
|
30
|
-
"tsx": "^4.23.
|
|
30
|
+
"tsx": "^4.23.15",
|
|
31
31
|
"typescript": "^7.0.2",
|
|
32
|
-
"vitest": "^
|
|
32
|
+
"vitest": "^5.0.3"
|
|
33
33
|
},
|
|
34
34
|
"scripts": {
|
|
35
35
|
"start": "tsx src/cli.ts",
|
|
@@ -68,7 +68,7 @@ resolve the ids from `summarizedSavedWorkout.saved_workout`.
|
|
|
68
68
|
|
|
69
69
|
1. **Persist the entered data** — `PUT /1.0/athlete/savedworkoutsetexercise/{savedWorkoutSetExerciseId}`
|
|
70
70
|
with `{ id, saved_workout_set_id, workout_set_exercise_id, completed:1, param_N_made,
|
|
71
|
-
param_1_data_N, param_2_data_N (10 slots) }`. This is the only path that actually stores
|
|
71
|
+
param_1_data_N, param_2_data_N (10 slots) }`. This is the only path that actually stores
|
|
72
72
|
reps/weight (and it alone surfaces the result in exercise history). The
|
|
73
73
|
`savedworkoutset`/`savedworkout` PUTs accept the same fields but **silently discard** the
|
|
74
74
|
`param_N_data` values (the savedworkout PUT is the session-note / RPE write, not a log path).
|
|
@@ -114,9 +114,9 @@ Download historicals into D1 so they can be queried over time without re-hitting
|
|
|
114
114
|
One sync verb populates each zone; one query tool reads it.
|
|
115
115
|
|
|
116
116
|
- `athlete_workouts_sync { startDate, endDate }` → `athlete_workouts_stored { workoutId? |
|
|
117
|
-
startDate?/endDate? }`.
|
|
117
|
+
startDate?/endDate? }`.
|
|
118
118
|
- `athlete_training_sync { exerciseId? | batchSize?, full? }` → `athlete_training_stored
|
|
119
|
-
{ q? | exerciseId? (+prs?) | workingMaxes? }`. Omitting `exerciseId` syncs the catalog +
|
|
119
|
+
{ q? | exerciseId? (+prs?) | workingMaxes? }`. Omitting `exerciseId` syncs the catalog +
|
|
120
120
|
working maxes and drains a **batch** of un-synced exercises (repeat until `remaining` is 0
|
|
121
121
|
— bounded per call to respect Worker subrequest limits). `full:true` re-pulls every
|
|
122
122
|
exercise.
|
|
@@ -279,7 +279,7 @@ Environment-specific facts that defy reasonable assumptions:
|
|
|
279
279
|
|
|
280
280
|
The CLI enforces a `--yes` flag on `coach message send`/`coach message delete`,
|
|
281
281
|
`coach workout publish`, `coach workout remove`, `coach exercise forget`, `coach
|
|
282
|
-
athlete-invite`, `coach athlete-archive`, `coach team-delete`, `coach team-code-delete`,
|
|
282
|
+
athlete-invite`, `coach athlete-archive`, `coach team-delete`, `coach team-code-delete`,
|
|
283
283
|
`coach session-unpublish`, and `coach log-set`, but the gate above still applies: confirm
|
|
284
284
|
in the moment before adding `--yes`.
|
|
285
285
|
|