fix: allow editing phase time limits in retro board

[IJuanI]

Description

This PR fixes a missing feature in the retro editing functionality that prevented users from modifying phase time limits after retro creation.

Problem

1. Missing Edit Functionality: The EditRetro component was missing the phaseTimeLimitMin field, so users could only set phase time limits when creating a retro, but not when editing an existing retro.

2. Backend Gap: The backend EditRetro function didn't support updating phaseTimeLimitMin, making it impossible to change time limits after retro creation.

3. Inconsistent Experience: Users could set independent timer and auto-advance settings during creation, but couldn't modify the timer setting afterward, creating an inconsistent editing experience.

Solution

Frontend Changes

• Added missing field: Added phaseTimeLimitMin input field to EditRetro.svelte component
• Updated props: Added phaseTimeLimitMin to component interface and state management
• Form integration: Connected the field to the form submission logic

Backend Changes

• Database layer: Updated EditRetro function in internal/db/retro/retro.go to accept and update phaseTimeLimitMin parameter
• SQL query: Added phase_time_limit_min = $7 to the UPDATE statement
• Event handling: Updated websocket event handler in internal/http/retro/events.go to process the new parameter
• Interface updates: Updated function signatures in internal/http/types.go and internal/http/retro/retro.go

Key Benefits

• Complete editing: Users can now edit phase time limits after creating a retro
• Consistent experience: Edit functionality now matches the creation functionality
• Flexible timer usage: Timer shows when phaseTimeLimitMin > 0 regardless of phaseAutoAdvance setting
• No breaking changes: Fully backward compatible

Use Cases Now Supported

• ✅ Timer with auto-advance: phaseTimeLimitMin > 0 + phaseAutoAdvance = true
• ✅ Timer without auto-advance: phaseTimeLimitMin > 0 + phaseAutoAdvance = false (now editable)
• ✅ No timer: phaseTimeLimitMin = 0 (timer hidden regardless of auto-advance setting)

Testing Added

E2E Tests (e2e/tests/retro/retro.spec.ts)

• Test editing retro with phase time limit and disabled auto-advance
• Test timer visibility when phaseTimeLimitMin > 0
• Test timer hidden when phaseTimeLimitMin = 0

API Tests (e2e/tests/api/retros.spec.ts)

• Test retro creation with phaseTimeLimitMin and phaseAutoAdvance parameters

Files Changed

• ui/src/components/retro/EditRetro.svelte - Added missing phaseTimeLimitMin field
• ui/src/pages/retro/Retro.svelte - Pass phaseTimeLimitMin to EditRetro component
• internal/db/retro/retro.go - Updated EditRetro function signature and SQL
• internal/http/retro/events.go - Updated event handler for new parameter
• internal/http/types.go - Updated interface definition
• internal/http/retro/retro.go - Updated interface definition
• e2e/tests/retro/retro.spec.ts - Added E2E tests
• e2e/tests/api/retros.spec.ts - Added API tests

Breaking Changes

None - this is a backward-compatible bug fix and enhancement.

Checklist

• Added missing functionality to EditRetro component
• Updated backend to support phaseTimeLimitMin editing
• Added comprehensive tests
• Maintained backward compatibility
• Followed existing code patterns and conventions

[IJuanI]

Thanks for running the CI!
I see some visual tests failed, I didn't find this issues locally, will check them in more detail 👀