fix(workout): count skipped-status exercises with logged sets as real efforts

In the workout-complete summary, an exercise whose status is 'skipped'
but which has logged sets is now treated as a real (partial) effort:
its progression is computed and its sets are shown, instead of being
struck through and labelled "skipped". Only genuinely empty skipped
exercises are counted/shown as skipped. Stats are computed on read, so
this also corrects already-completed workouts.

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

Author: tpcmurray

server/src/__tests__/integration/workouts.test.js

@@ -211,6 +211,45 @@ describe('PUT /api/workouts/:id/complete', () => {
     expect(mockClient.release).toHaveBeenCalled();
   });
 
+  it('counts a skipped-status exercise that has logged sets as a real effort', async () => {
+    const mockClient = createMockClient([
+      {}, // BEGIN
+      { rows: [{ id: WID, completed_at: null }] }, // Verify session
+      {}, // Mark pending as skipped
+      {}, // Set completed_at
+      {}, // COMMIT
+      // buildCompletionStats: workout
+      { rows: [{ id: WID, started_at: '2026-01-25T14:00:00Z', completed_at: '2026-01-25T15:00:00Z' }] },
+      // buildCompletionStats: exercises (status skipped but it has sets)
+      { rows: [{ id: 'se1', exercise_id: 'ex1', status: 'skipped', skip_reason: 'ran out of time', exercise_name: 'Stairs', muscle_group: 'legs' }] },
+      // set_logs for se1 (fetched first now)
+      { rows: [
+        { set_number: 1, weight_lbs: '1.0', reps: 8 },
+        { set_number: 2, weight_lbs: '1.0', reps: 5 },
+        { set_number: 3, weight_lbs: '1.0', reps: 6 },
+      ] },
+      // fetchLastSession: no prior session
+      { rows: [] },
+    ]);
+
+    pool.connect.mockResolvedValue(mockClient);
+
+    // buildWorkoutResponse (uses pool)
+    pool.query.mockResolvedValueOnce({
+      rows: [{ id: WID, program_day_id: DAY_ID, started_at: '2026-01-25T14:00:00Z', completed_at: '2026-01-25T15:00:00Z', notes: null }],
+    });
+    pool.query.mockResolvedValueOnce({ rows: [] }); // exercises
+
+    const res = await request(app).put(`/api/workouts/${WID}/complete`);
+
+    expect(res.status).toBe(200);
+    const prog = res.body.data.progression;
+    expect(prog.skipped).toBe(0);
+    expect(prog.progressed).toBe(1); // first_time counts as progressed
+    expect(prog.details[0].status).not.toBe('skipped');
+    expect(prog.details[0].exercise_name).toBe('Stairs');
+  });
+
   it('returns 404 when workout not found', async () => {
     const mockClient = createMockClient([
       {}, // BEGIN

server/src/controllers/workoutController.js

@@ -390,7 +390,15 @@ async function buildCompletionStats(client, workoutId) {
   let skipped = 0;
 
   for (const ex of exercises) {
-    if (ex.status === 'skipped') {
+    // Get current session sets
+    const { rows: currentSets } = await client.query(
+      'SELECT set_number, weight_lbs, reps FROM set_logs WHERE session_exercise_id = $1 ORDER BY set_number',
+      [ex.id]
+    );
+
+    // Only count as skipped when no sets were logged. An exercise with logged
+    // sets is a real (partial) effort even if its status is 'skipped'.
+    if (ex.status === 'skipped' && currentSets.length === 0) {
       skipped++;
       details.push({
         exercise_id: ex.exercise_id,
@@ -402,12 +410,6 @@ async function buildCompletionStats(client, workoutId) {
       continue;
     }
 
-    // Get current session sets
-    const { rows: currentSets } = await client.query(
-      'SELECT set_number, weight_lbs, reps FROM set_logs WHERE session_exercise_id = $1 ORDER BY set_number',
-      [ex.id]
-    );
-
     // Get last session for comparison
     const lastSession = await fetchLastSession(client, ex.exercise_id, workoutId);
     const progression = compareProgression(currentSets, lastSession?.sets || []);