.planning/ROADMAP.md

@@ -15,7 +15,7 @@
 | 8 | Social Sign-in | Google sign-in creates/links local users and issues existing Xtablo sessions; Apple sign-in is disabled | AUTH-08..13 |
 | 9 | Etapes | Tasks can be grouped under one-level etapes without breaking the kanban model | ETAPE-01..06 |
 | 10 | 4/4 | Complete    | 2026-05-16 |
-| 11 | 1/2 | In Progress|  |
+| 11 | 2/2 | Complete   | 2026-05-16 |
 | 12 | Native Tablo Chat | Each tablo has persisted discussion with real-time delivery and no managed chat provider | CHAT-01..06 |
 
 ---

.planning/STATE.md

@@ -2,15 +2,15 @@
 gsd_state_version: 1.0
 milestone: v2.0
 milestone_name: Collaboration, planning, and social sign-in
-status: executing
-last_updated: "2026-05-16T05:28:12.300Z"
+status: verifying
+last_updated: "2026-05-16T07:05:52.182Z"
 last_activity: 2026-05-16
 progress:
   total_phases: 5
-  completed_phases: 3
+  completed_phases: 4
   total_plans: 15
-  completed_plans: 14
-  percent: 93
+  completed_plans: 15
+  percent: 100
 ---
 
 # STATE
@@ -30,7 +30,7 @@ See: `.planning/PROJECT.md` (updated 2026-05-15)
 
 Phase: 11 (Individual Planning) — EXECUTING
 Plan: 2 of 2
-Status: Ready to execute
+Status: Phase complete — ready for verification
 Last activity: 2026-05-16
 Resume file: .planning/phases/11-individual-planning/11-01-PLAN.md
 
@@ -120,6 +120,7 @@ Resume file: .planning/phases/11-individual-planning/11-01-PLAN.md
 | Phase 08 P04 | 20min | 2 tasks | 8 files |
 | Phase 08 P05 | 20min | 2 tasks | 7 files |
 | Phase 11 P01 | ~15min | 2 tasks | 15 files |
+| Phase 11 P02 | ~20min | 2 tasks | 4 files |
 
 ## Notes
 

.planning/phases/11-individual-planning/11-02-SUMMARY.md

@@ -0,0 +1,126 @@
+---
+phase: 11-individual-planning
+plan: 02
+subsystem: planning
+tags: [planning, events, postgres, sqlc, htmx, templ, verification]
+
+requires:
+  - phase: 11-01
+    provides: Protected /planning agenda route and first implementation slice
+provides:
+  - Full backend verification for Phase 11 planning behavior
+  - Browser UAT approval for the first upcoming-agenda experience
+  - Row-level planning event date labels
+affects: [planning, events, router, templates, verification]
+
+tech-stack:
+  added: []
+  patterns:
+    - "Planning verification pairs full generated-code backend tests with browser UAT."
+    - "Planning event rows include explicit date labels because the default view spans 14 days."
+
+key-files:
+  created:
+    - .planning/phases/11-individual-planning/11-02-SUMMARY.md
+  modified:
+    - backend/internal/web/handlers_planning_test.go
+    - backend/templates/planning.templ
+    - backend/templates/planning_forms.go
+
+key-decisions:
+  - "Show each planning event's date in the compact row metadata, since the Today view is a 14-day upcoming agenda rather than a single-day list."
+  - "Keep the row date as plain server-rendered text in the existing continuous list instead of introducing grouped day headers or a calendar UI."
+
+patterns-established:
+  - "Browser UAT issues are fixed with a regression assertion before approval is accepted."
+  - "Phase 11 planning rows display date, time, title, tablo context, and optional location without description snippets."
+
+requirements-completed: [PLAN-01, PLAN-02, PLAN-03, PLAN-04]
+
+duration: ~20min
+completed: 2026-05-16
+---
+
+# Phase 11: Individual Planning Plan 02 Summary
+
+**Full backend verification and UAT-approved 14-day planning agenda with explicit event dates**
+
+## Performance
+
+- **Duration:** ~20 min
+- **Started:** 2026-05-16T05:38:00Z
+- **Completed:** 2026-05-16T06:43:00Z
+- **Tasks:** 2
+- **Files modified:** 4
+
+## Accomplishments
+
+- Ran full generated-code backend verification for the planning slice and existing web packages.
+- Completed browser UAT for `/planning` after user approval of the authenticated 14-day agenda behavior.
+- Fixed the UAT-reported date visibility issue by adding row-level date labels to planning events.
+- Added regression coverage requiring planning agenda responses to include future event date labels.
+
+## Task Commits
+
+Each task was committed atomically:
+
+1. **Task 1: Run full generated-code backend verification** - no source changes required.
+2. **Task 2: Browser UAT checkpoint and date-label fix** - `bb84d70` (fix)
+
+## Files Created/Modified
+
+- `.planning/phases/11-individual-planning/11-02-SUMMARY.md` - Documents verification, UAT approval, and closeout state.
+- `backend/internal/web/handlers_planning_test.go` - Adds regression assertions for event date labels in the planning agenda.
+- `backend/templates/planning.templ` - Renders each event row's date before its time and title.
+- `backend/templates/planning_forms.go` - Adds `DateLabel` to planning rows from `event_date`.
+
+## Decisions Made
+
+- The date label uses a readable `May 17, 2026` format to make the 14-day range understandable without grouped day headers.
+- The page remains a restrained continuous agenda list, preserving the UI-SPEC constraint to avoid recreating a calendar grid.
+
+## Deviations from Plan
+
+### Auto-fixed Issues
+
+**1. [Rule 1 - Bug] Planning rows lacked event dates in the 14-day Today view**
+- **Found during:** Task 2 browser UAT checkpoint.
+- **Issue:** The default `/planning` view spans today through 13 days after today, but each event row only showed time, title, tablo, and location. Future events were therefore ambiguous.
+- **Fix:** Added `PlanningEventRow.DateLabel`, populated it from `ListUserEventsRangeRow.EventDate`, and rendered it before the event time.
+- **Files modified:** `backend/templates/planning_forms.go`, `backend/templates/planning.templ`, `backend/internal/web/handlers_planning_test.go`
+- **Verification:** `TEST_DATABASE_URL='postgres://xtablo:xtablo@localhost:5432/xtablo?sslmode=disable' go test ./internal/web -run 'TestPlanning' -count=1`
+- **Committed in:** `bb84d70`
+
+---
+
+**Total deviations:** 1 auto-fixed bug
+**Impact on plan:** The fix is within the Plan 11-02 UAT hardening scope and improves PLAN-02 visibility without changing routing, query semantics, or the UI structure.
+
+## Issues Encountered
+
+The initial browser UAT was not approved because event dates were missing from the 14-day agenda rows. The issue was fixed with a regression assertion and approved by the user after refresh.
+
+## User Setup Required
+
+None - no external service configuration required.
+
+## Verification
+
+- `cd backend && just generate && TEST_DATABASE_URL='postgres://xtablo:xtablo@localhost:5432/xtablo?sslmode=disable' go test ./... -count=1 && git diff --check` passed before browser UAT.
+- `cd backend && TEST_DATABASE_URL='postgres://xtablo:xtablo@localhost:5432/xtablo?sslmode=disable' go test ./internal/web -run 'TestPlanning' -count=1` passed after the UAT fix.
+- Browser UAT was approved by the user on 2026-05-16 after verifying `/planning` showed event dates in the 14-day agenda.
+
+## Self-Check: PASSED
+
+- Full backend verification passed.
+- Browser UAT approval was received.
+- PLAN-01 through PLAN-04 remain covered by automated tests or UAT.
+- No unresolved deviations remain.
+
+## Next Phase Readiness
+
+Phase 11 is ready for phase-level code review, regression checking, and goal verification.
+
+---
+*Phase: 11-individual-planning*
+*Completed: 2026-05-16*