docs(24-01): complete Fix Recording Crash plan

Tasks completed: 2/2
- Fix useRecordingHelpers.js method names and parameters
- Fix JKSessionScreen.js doStartRecording method

SUMMARY: .planning/phases/24-fix-recording-crash/24-01-SUMMARY.md

.planning/STATE.md

@@ -10,11 +10,11 @@ See: .planning/PROJECT.md (updated 2026-02-19)
 ## Current Position
 
 Phase: 24 (Fix Recording Crash)
-Plan: Not started
-Status: Ready for planning
-Last activity: 2026-02-19 — Roadmap created
+Plan: 01 of 1 complete
+Status: Phase complete
+Last activity: 2026-02-19 - Completed 24-01-PLAN.md
 
-Progress: `/gsd:discuss-phase 24` or `/gsd:plan-phase 24`
+Progress: [==========] 100%
 
 ## Performance Metrics
 
@@ -49,6 +49,11 @@ Progress: `/gsd:discuss-phase 24` or `/gsd:plan-phase 24`
 - Completion date: 2026-02-10
 - User verified: 15+ minute stability test passed, no freezes
 
+**v1.5 Fix Session Recording (In Progress):**
+- Phase 24: Fix Recording Crash - Complete (24-01)
+- Phase 25: Verify Basic Controls - Not started
+- Phase 26: Memory Leak Audit - Not started
+
 ## Accumulated Context
 
 ### Decisions
@@ -71,6 +76,8 @@ Decisions are logged in PROJECT.md Key Decisions table.
 | 2026-02-08 | 22-01 | useRef for callback cleanup stability | Avoids stale closure issues on unmount |
 | 2026-02-10 | 23-01 | UAT checklist for manual memory profiling | Cannot fully automate Chrome DevTools verification |
 | 2026-02-10 | 23-01 | 15+ minute stability as primary metric | Reflects real-world usage patterns |
+| 2026-02-19 | 24-01 | Unpack recordSettings to individual params | C++ client expects individual params, not objects |
+| 2026-02-19 | 24-01 | Match legacy recordingModel.js signature | Ensures compatibility with existing C++ client |
 
 ### Deferred Issues
 
@@ -88,20 +95,21 @@ Decisions are logged in PROJECT.md Key Decisions table.
 - **v1.2 Session Attachments** (Phases 12-16): Shipped 2026-02-07
 - **v1.3 Session Settings Tests** (Phases 17-18): Shipped 2026-02-08
 - **v1.4 Memory Leak Prevention** (Phases 19-23): Shipped 2026-02-10
+- **v1.5 Fix Session Recording** (Phases 24-26): In Progress
 
 ## Session Continuity
 
 Last session: 2026-02-19
-Stopped at: Roadmap created
+Stopped at: Completed 24-01-PLAN.md
 Resume file: None
 
 **v1.5 Fix Session Recording**
 
 Phases:
-- Phase 24: Fix Recording Crash (CRASH-01 to CRASH-04)
-- Phase 25: Verify Basic Controls (CTRL-01 to CTRL-03)
-- Phase 26: Memory Leak Audit (MEM-01 to MEM-03)
+- Phase 24: Fix Recording Crash - COMPLETE (24-01)
+- Phase 25: Verify Basic Controls - Not started
+- Phase 26: Memory Leak Audit - Not started
 
 **Next steps:**
-1. Run `/gsd:discuss-phase 24` to gather context
-2. Or `/gsd:plan-phase 24` to plan directly
+1. Phase 25: Human verification of recording controls with C++ client
+2. Phase 26: Memory leak audit for recording components

.planning/phases/24-fix-recording-crash/24-01-SUMMARY.md

@@ -0,0 +1,93 @@
+---
+phase: 24-fix-recording-crash
+plan: 01
+subsystem: ui
+tags: [recording, jam-client, c++, react-hooks]
+
+# Dependency graph
+requires:
+  - phase: none
+    provides: existing recording infrastructure
+provides:
+  - Correct jamClient.StartRecording and StopRecording method calls
+  - Unpacked parameters matching C++ client expectations
+  - Recording start/stop that matches legacy recordingModel.js pattern
+affects: [phase-25-verify-controls, phase-26-memory-audit]
+
+# Tech tracking
+tech-stack:
+  added: []
+  patterns: ["jamClient method calls with unpacked parameters"]
+
+key-files:
+  created: []
+  modified:
+    - jam-ui/src/hooks/useRecordingHelpers.js
+    - jam-ui/src/components/client/JKSessionScreen.js
+
+key-decisions:
+  - "Unpack recordSettings object to individual parameters for C++ client compatibility"
+  - "Use videoType integer (not boolean recordVideo) as first param for StartRecording"
+  - "Match legacy recordingModel.js signature exactly: (id, tracks, videoType, chatFlag, framerate)"
+
+patterns-established:
+  - "jamClient recording calls: Always unpack parameters, never pass objects to C++ client"
+
+# Metrics
+duration: 8min
+completed: 2026-02-19
+---
+
+# Phase 24 Plan 01: Fix Recording Crash Summary
+
+**Corrected jamClient recording method names and parameter format to match C++ client expectations**
+
+## Performance
+
+- **Duration:** 8 min
+- **Started:** 2026-02-19
+- **Completed:** 2026-02-19
+- **Tasks:** 2
+- **Files modified:** 2
+
+## Accomplishments
+- Fixed `StartMediaRecording` to `StartRecording` with unpacked parameters
+- Fixed `FrontStopRecording` to `StopRecording` with correct signature
+- Matched legacy recordingModel.js pattern exactly for C++ client compatibility
+
+## Task Commits
+
+Each task was committed atomically:
+
+1. **Task 1: Fix useRecordingHelpers.js method names and parameters** - `45aeb04eb` (fix)
+2. **Task 2: Fix JKSessionScreen.js doStartRecording method** - `660264312` (fix)
+
+## Files Created/Modified
+- `jam-ui/src/hooks/useRecordingHelpers.js` - Updated StartRecording and StopRecording calls with unpacked parameters
+- `jam-ui/src/components/client/JKSessionScreen.js` - Updated doStartRecording to use correct method and parameters
+
+## Decisions Made
+- Unpack `recordSettings` object to individual parameters (`videoType`, `recordChat`, `recordFramerate`)
+- Use integer values: `videoType || 0`, `recordChat ? 1 : 0`, `recordFramerate = 0`
+- Match legacy signature exactly: `jamClient.StartRecording(id, groupedTracks, recordVideo, recordChat, recordFramerate)`
+
+## Deviations from Plan
+
+None - plan executed exactly as written.
+
+## Issues Encountered
+- Build verification skipped due to Node.js v23 OpenSSL incompatibility (environment issue, not code issue)
+- Syntax validation passed via `node --check`
+
+## User Setup Required
+
+None - no external service configuration required.
+
+## Next Phase Readiness
+- Recording method calls now match legacy implementation
+- Ready for Phase 25: Verify Basic Controls (manual verification with C++ client)
+- C++ client should now receive correct method names and parameter format
+
+---
+*Phase: 24-fix-recording-crash*
+*Completed: 2026-02-19*