docs(03-01): complete hook event processing plan

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

.planning/phases/03-hook-server/03-01-SUMMARY.md

@@ -0,0 +1,92 @@
+---
+phase: 03-hook-server
+plan: 01
+subsystem: api
+tags: [http-hooks, claude-code, json, net-http, event-mapping]
+
+requires:
+  - phase: 02-daemon-et-i3-bridge
+    provides: SessionRegistry, TrackedSession, Daemon, SessionInfo
+provides:
+  - HookEvent struct parsing Claude Code hook JSON
+  - processHookEvent mapping 4 event types to State+WaitType
+  - UpdateFromHook with auto-create and WaitingSince transitions
+  - handleHook HTTP handler with POST validation and body size limit
+  - SessionInfo.WaitType field for wait type discrimination
+affects: [03-hook-server]
+
+tech-stack:
+  added: [net/http, net/http/httptest]
+  patterns: [HTTP handler with MaxBytesReader, event-to-state mapping via switch]
+
+key-files:
+  created: [hook.go, hook_test.go]
+  modified: [protocol.go, protocol_test.go]
+
+key-decisions:
+  - "WaitType omitempty: champ vide omis du JSON pour compatibilite avec les clients existants"
+  - "UpdateFromHook separe de Update: les hooks ne connaissent pas PID/GitBranch/Preview, donc methode dediee qui ne touche que les champs connus"
+
+patterns-established:
+  - "Hook event mapping: switch sur HookEventName puis NotificationType pour determiner State+WaitType"
+  - "HTTP handler pattern: method check, MaxBytesReader, JSON decode, process, 200 OK"
+
+requirements-completed: [STATE-03]
+
+duration: 3min
+completed: 2026-03-23
+---
+
+# Phase 03 Plan 01: Hook Event Processing Summary
+
+**HookEvent parsing, event-to-state mapping (Notification/Stop/PostToolUse/PreToolUse), UpdateFromHook avec auto-create, et HTTP handler POST /hook avec validation**
+
+## Performance
+
+- **Duration:** 3 min
+- **Started:** 2026-03-23T18:38:37Z
+- **Completed:** 2026-03-23T18:41:45Z
+- **Tasks:** 2
+- **Files modified:** 4
+
+## Accomplishments
+- HookEvent struct couvre tous les champs du payload Claude Code hooks
+- processHookEvent mappe les 4 types d'events (Notification, Stop, PostToolUse, PreToolUse) vers State+WaitType
+- UpdateFromHook gere les sessions inconnues et les transitions WaitingSince
+- handleHook HTTP handler valide method, body size (64KB), et JSON
+- 16 tests couvrent tous les cas
+
+## Task Commits
+
+1. **Task 1: HookEvent struct, processHookEvent mapping, UpdateFromHook, WaitType** - `e1b176c` (feat)
+2. **Task 2: HTTP handler POST /hook avec validation et protection** - `5bec943` (feat)
+
+## Files Created/Modified
+- `hook.go` - HookEvent struct, handleHook HTTP handler, processHookEvent, UpdateFromHook
+- `hook_test.go` - 16 tests (12 mapping + 4 HTTP handler)
+- `protocol.go` - SessionInfo enrichi avec WaitType
+- `protocol_test.go` - Test serialisation JSON de WaitType
+
+## Decisions Made
+- WaitType omitempty : le champ vide est omis du JSON pour ne pas casser les clients existants qui ignorent ce champ
+- UpdateFromHook est une methode separee de Update car les hooks ne connaissent pas PID, GitBranch, Preview, Workspace, Label
+
+## Deviations from Plan
+
+None - plan executed exactly as written.
+
+## Issues Encountered
+None
+
+## User Setup Required
+None - no external service configuration required.
+
+## Next Phase Readiness
+- hook.go fournit toute la logique de traitement. Le plan 03-02 peut integrer le HTTP server dans le Daemon (startHookServer, hookPort, poll slowdown).
+- handleHook est pret a etre monte sur un http.ServeMux.
+
+---
+*Phase: 03-hook-server*
+*Completed: 2026-03-23*
+
+## Self-Check: PASSED