docs(04): phase 4 drag interaction (broken)

2026-01-18 16:55:09 -06:00
parent cf04ea435a
commit ac78042a7e
6 changed files with 715 additions and 0 deletions
--- a/.planning/phases/02-constraint-validation/02-VERIFICATION.md
+++ b/.planning/phases/02-constraint-validation/02-VERIFICATION.md
@@ -0,0 +1,86 @@
+---
+phase: 02-constraint-validation
+verified: 2026-01-18T21:30:00Z
+status: passed
+score: 6/6 must-haves verified
+---
+
+# Phase 2: Constraint Validation Verification Report
+
+**Phase Goal:** The system prevents invalid positions and enforces item-specific rules.
+**Verified:** 2026-01-18T21:30:00Z
+**Status:** passed
+**Re-verification:** No - initial verification
+
+## Goal Achievement
+
+### Observable Truths
+
+| # | Truth | Status | Evidence |
+|---|-------|--------|----------|
+| 1 | Games cannot be moved (CONS-01) | VERIFIED | `ItineraryConstraints.isValidPosition()` returns `false` for `.game` case (line 28-30). Tests `game_cannotBeMoved` and `success_gameNotDraggable` verify. |
+| 2 | Travel segments constrained to valid day range (CONS-02) | VERIFIED | `validDayRange()` method (line 47-60) calculates range based on departure/arrival games. Tests `travel_validDayRange_simpleCase`, `travel_cannotGoOutsideValidDayRange` verify. |
+| 3 | Travel must be after from-city games, before to-city games on same day (CONS-03) | VERIFIED | `isValidTravelPosition()` method (line 85-121) enforces sortOrder constraints. 5 tests cover this requirement. |
+| 4 | Custom items have no constraints (CONS-04) | VERIFIED | `isValidPosition()` returns `true` for `.custom` case (line 40-43). Tests `custom_canGoOnAnyDay`, `custom_canGoBeforeOrAfterGames`, `success_customNotePlacedAnywhere` verify. |
+| 5 | Tests use Swift Testing framework (@Test, @Suite) | VERIFIED | File uses `import Testing`, `@Suite("ItineraryConstraints")`, and `@Test` decorators. 22 tests total. |
+| 6 | API documentation exists for Phase 4 integration | VERIFIED | `CONSTRAINT-API.md` documents `isValidPosition()`, `validDayRange()`, `barrierGames()` with usage examples. |
+
+**Score:** 6/6 truths verified
+
+### Required Artifacts
+
+| Artifact | Expected | Status | Details |
+|----------|----------|--------|---------|
+| `SportsTimeTests/Domain/ItineraryConstraintsTests.swift` | Migrated constraint tests with @Suite | EXISTS + SUBSTANTIVE + WIRED | 398 lines, 22 @Test functions, uses Swift Testing, imports @testable SportsTime |
+| `SportsTime/Core/Models/Domain/ItineraryConstraints.swift` | Implementation with isValidPosition | EXISTS + SUBSTANTIVE | 134 lines, 3 public methods, no stub patterns |
+| `.planning/phases/02-constraint-validation/CONSTRAINT-API.md` | API documentation for Phase 4 | EXISTS + SUBSTANTIVE | 165 lines, documents all 3 public methods with examples |
+
+### Key Link Verification
+
+| From | To | Via | Status | Details |
+|------|-----|-----|--------|---------|
+| `ItineraryConstraintsTests.swift` | `ItineraryConstraints.swift` | `@testable import SportsTime` | WIRED | Line 11: `@testable import SportsTime` |
+| `CONSTRAINT-API.md` | `ItineraryConstraints.swift` | documents public API | WIRED | Documents `isValidPosition`, `validDayRange`, `barrierGames` methods |
+
+### Requirements Coverage
+
+| Requirement | Status | Test Evidence |
+|-------------|--------|---------------|
+| CONS-01: Games cannot be moved | SATISFIED | `game_cannotBeMoved()`, `success_gameNotDraggable()` |
+| CONS-02: Travel segments constrained to valid day range | SATISFIED | `travel_validDayRange_simpleCase()`, `travel_cannotGoOutsideValidDayRange()`, `edge_travelNoGamesInEitherCity_hasFullRange()` |
+| CONS-03: Travel segments must be after from-city games, before to-city games on same day | SATISFIED | `travel_mustBeAfterDepartureGames()`, `travel_mustBeBeforeArrivalGames()`, `travel_canBeAnywhereOnRestDays()`, `travel_mustBeAfterAllDepartureGamesOnSameDay()`, `travel_mustBeBeforeAllArrivalGamesOnSameDay()` |
+| CONS-04: Custom items have no constraints | SATISFIED | `custom_canGoOnAnyDay()`, `custom_canGoBeforeOrAfterGames()`, `success_customNotePlacedAnywhere()` |
+
+### Success Criteria from Roadmap
+
+| Criteria | Status | Evidence |
+|----------|--------|----------|
+| Attempting to drag a game row shows no drag interaction | VERIFIED | `isValidPosition()` returns `false` for all game positions. Test `success_gameNotDraggable()` verifies. |
+| Travel segment between Chicago and Boston cannot be placed on Day 1 if Chicago games extend through Day 2 | VERIFIED | `validDayRange()` returns minDay based on last departure game. Test `travel_cannotGoOutsideValidDayRange()` verifies. |
+| Custom note item can be placed before, between, or after games on any day | VERIFIED | Test `success_customNotePlacedAnywhere()` explicitly verifies all positions. |
+| Invalid position attempt returns rejection (constraint checker returns false) | VERIFIED | Test `success_invalidPositionReturnsRejection()` verifies false return. |
+
+### Anti-Patterns Found
+
+| File | Line | Pattern | Severity | Impact |
+|------|------|---------|----------|--------|
+| None | - | - | - | No anti-patterns detected |
+
+### Human Verification Required
+
+None - all success criteria are verifiable through automated tests.
+
+### Test Execution Summary
+
+All 22 constraint tests pass:
+- 2 tests for CONS-01 (games immutable)
+- 3 tests for CONS-02 (travel day range)
+- 5 tests for CONS-03 (travel sortOrder)
+- 2 tests for CONS-04 (custom flexibility)
+- 8 tests for edge cases (boundaries, impossible constraints)
+- 3 tests for success criteria verification
+
+---
+
+_Verified: 2026-01-18T21:30:00Z_
+_Verifier: Claude (gsd-verifier)_
--- a/.planning/phases/03-visual-flattening/03-01-SUMMARY.md
+++ b/.planning/phases/03-visual-flattening/03-01-SUMMARY.md
@@ -0,0 +1,101 @@
+---
+phase: 03-visual-flattening
+plan: 01
+subsystem: ui
+tags: [uitableview, flattening, sortorder, swift]
+
+# Dependency graph
+requires:
+  - phase: 01-semantic-position-model
+    provides: SortOrderProvider for game time → sortOrder conversion
+  - phase: 02-constraint-validation
+    provides: ItineraryConstraints for drag validation
+provides:
+  - ItineraryFlattener pure utility for deterministic display ordering
+  - Refactored reloadData() using sortOrder-based flattening
+affects: [03-02-flattening-tests, 04-drag-drop]
+
+# Tech tracking
+tech-stack:
+  added: []
+  patterns: [pure-function-for-flattening, sortorder-based-display-ordering]
+
+key-files:
+  created:
+    - SportsTime/Core/Models/Domain/ItineraryFlattener.swift
+  modified:
+    - SportsTime/Features/Trip/Views/ItineraryTableViewController.swift
+
+key-decisions:
+  - "Day headers are not positioned items - always first in each day"
+  - "Games get sortOrder from SortOrderProvider.initialSortOrder(forGameTime:)"
+  - "Travel sortOrder looked up from itineraryItems by city name matching"
+  - "Pure flatten function enables unit testing without UITableView"
+
+patterns-established:
+  - "ItineraryFlattener.flatten(): Pure function for hierarchical to flat conversion"
+  - "gamesByDay dictionary: Group games by day number before flattening"
+
+# Metrics
+duration: 3min
+completed: 2026-01-18
+---
+
+# Phase 3 Plan 1: Visual Flattening Summary
+
+**Pure ItineraryFlattener utility replacing bucket-based flattening with sortOrder-based deterministic display ordering**
+
+## Performance
+
+- **Duration:** 3 min
+- **Started:** 2026-01-18T21:52:57Z
+- **Completed:** 2026-01-18T21:55:13Z
+- **Tasks:** 2
+- **Files modified:** 2
+
+## Accomplishments
+
+- Created `ItineraryFlattener` enum with pure `flatten()` function
+- Replaced bucket-based flattening (beforeGames/afterGames) with sortOrder sort
+- Deterministic display order: same semantic state always produces same row order
+- Updated architecture documentation to reflect sortOrder-based approach
+
+## Task Commits
+
+Each task was committed atomically:
+
+1. **Task 1: Create ItineraryFlattener utility** - `fdfc912` (feat)
+2. **Task 2: Refactor reloadData() to use ItineraryFlattener** - `dd1fd82` (refactor)
+
+## Files Created/Modified
+
+- `SportsTime/Core/Models/Domain/ItineraryFlattener.swift` - Pure flatten function with sortOrder-based ordering
+- `SportsTime/Features/Trip/Views/ItineraryTableViewController.swift` - Refactored reloadData() to use flattener
+
+## Decisions Made
+
+- **Day headers not positioned:** Day headers are always first in each day, not part of the sortOrder-based ordering. This is a structural anchor.
+- **Flattener is a pure function:** No instance state, no side effects. Enables easy unit testing and guarantees determinism.
+- **gamesByDay dictionary:** Built in reloadData() to pass to flattener rather than having flattener access day.games directly.
+
+## Deviations from Plan
+
+None - plan executed exactly as written.
+
+## Issues Encountered
+
+None.
+
+## User Setup Required
+
+None - no external service configuration required.
+
+## Next Phase Readiness
+
+- ItineraryFlattener ready for unit tests in plan 03-02
+- reloadData() now uses pure flattening, enabling snapshot testing
+- Phase 4 drag-drop can rely on deterministic flatten output
+
+---
+*Phase: 03-visual-flattening*
+*Completed: 2026-01-18*
--- a/.planning/phases/03-visual-flattening/03-02-SUMMARY.md
+++ b/.planning/phases/03-visual-flattening/03-02-SUMMARY.md
@@ -0,0 +1,126 @@
+---
+phase: 03-visual-flattening
+plan: 02
+subsystem: testing
+tags: [swift-testing, itinerary, flattening, determinism]
+
+# Dependency graph
+requires:
+  - phase: 03-visual-flattening
+    plan: 01
+    provides: ItineraryFlattener.flatten() pure function
+provides:
+  - 13 tests verifying ItineraryFlattener determinism
+  - 3 success criteria tests mapping to ROADMAP requirements
+affects: [04-drag-drop]
+
+# Tech tracking
+tech-stack:
+  added: []
+  patterns: [success-criteria-test-naming, integration-style-testing]
+
+key-files:
+  created:
+    - SportsTimeTests/Domain/ItineraryFlattenerTests.swift
+  modified: []
+
+key-decisions:
+  - "success_* prefix for tests mapping to ROADMAP success criteria"
+  - "Integration tests use realistic multi-day trip configurations"
+  - "Test helpers create minimal mock data matching production types"
+
+patterns-established:
+  - "success_negativeSortOrderAppearsBeforeGames: Tests negative sortOrder positioning"
+  - "success_sameStateProducesIdenticalOrder: Tests determinism guarantee"
+  - "success_reorderPreservesNewOrder: Tests persistence after sortOrder change"
+
+# Metrics
+duration: 15min
+completed: 2026-01-18
+---
+
+# Phase 3 Plan 2: Flattening Tests Summary
+
+**13 tests verifying ItineraryFlattener produces deterministic, sortOrder-based output with explicit ROADMAP success criteria coverage**
+
+## Performance
+
+- **Duration:** 15 min
+- **Started:** 2026-01-18T21:59:19Z
+- **Completed:** 2026-01-18T22:13:59Z
+- **Tasks:** 2
+- **Tests added:** 13
+
+## Accomplishments
+
+- Created `ItineraryFlattenerTests.swift` with comprehensive test coverage
+- 3 success criteria tests mapping directly to ROADMAP requirements
+- 6 comprehensive coverage tests for edge cases
+- 4 integration tests for realistic trip data configurations
+- All tests pass, full test suite confirms no regressions
+
+## Task Commits
+
+Each task was committed atomically:
+
+1. **Task 1: Create ItineraryFlattenerTests** - `378e0ad` (test)
+2. **Task 2: Add integration tests** - `724b9f8` (test)
+
+## Files Created
+
+- `SportsTimeTests/Domain/ItineraryFlattenerTests.swift` - 765 lines, 13 tests
+
+## Success Criteria Verification
+
+The three ROADMAP success criteria now have explicit tests:
+
+| Success Criterion | Test Name |
+|-------------------|-----------|
+| Negative sortOrder before games | `success_negativeSortOrderAppearsBeforeGames` |
+| Deterministic flattening | `success_sameStateProducesIdenticalOrder` |
+| Reorder preserves position | `success_reorderPreservesNewOrder` |
+
+## Test Coverage
+
+### Success Criteria Tests (3)
+- `success_negativeSortOrderAppearsBeforeGames` - Item with sortOrder -1.0 appears before noon game
+- `success_sameStateProducesIdenticalOrder` - Repeated flatten produces identical row IDs
+- `success_reorderPreservesNewOrder` - Changed sortOrder results in new order after reflatten
+
+### Comprehensive Coverage Tests (6)
+- `flatten_dayHeaderAlwaysFirst` - Day header is structural anchor
+- `flatten_sortsByDayThenSortOrder` - Items grouped by day, sorted within
+- `flatten_gamesGetSortOrderFromTime` - 8pm game after item with sortOrder 500
+- `flatten_gamesGetSortOrderFromTime_earlyGame` - 1pm game before item with sortOrder 1000
+- `flatten_emptyDayHasOnlyHeader` - Rest day produces only header row
+- `flatten_multipleGamesOnSameDay` - Multiple games in single games row
+
+### Integration Tests (4)
+- `flatten_travelWithNegativeSortOrderAppearsBeforeGames` - Travel at -5.0 before games
+- `flatten_travelWithPositiveSortOrderAppearsAfterGames` - Travel at 1500.0 after games
+- `flatten_mixedItemTypes` - Complex day with exact order verification
+- `flatten_multiDayTrip` - 3-day trip with different configurations per day
+
+## Deviations from Plan
+
+None - plan executed exactly as written.
+
+## Issues Encountered
+
+None.
+
+## User Setup Required
+
+None - no external service configuration required.
+
+## Phase 3 Complete
+
+Phase 3 (Visual Flattening) is now complete:
+- Plan 1: Created ItineraryFlattener pure utility
+- Plan 2: Added comprehensive test coverage
+
+Phase 4 (Drag-Drop) can now build on the verified, deterministic flattening behavior.
+
+---
+*Phase: 03-visual-flattening*
+*Completed: 2026-01-18*
--- a/.planning/phases/03-visual-flattening/03-VERIFICATION.md
+++ b/.planning/phases/03-visual-flattening/03-VERIFICATION.md
@@ -0,0 +1,85 @@
+---
+phase: 03-visual-flattening
+verified: 2026-01-18T22:30:00Z
+status: passed
+score: 7/7 must-haves verified
+re_verification: false
+---
+
+# Phase 3: Visual Flattening Verification Report
+
+**Phase Goal:** Semantic items flatten to display rows deterministically, sorted by sortOrder.
+**Verified:** 2026-01-18T22:30:00Z
+**Status:** passed
+**Re-verification:** No - initial verification
+
+## Goal Achievement
+
+### Observable Truths
+
+| # | Truth | Status | Evidence |
+|---|-------|--------|----------|
+| 1 | Items with lower sortOrder appear before items with higher sortOrder | VERIFIED | ItineraryFlattener.swift:93 sorts by sortOrder ascending |
+| 2 | Items with sortOrder < 0 appear before games | VERIFIED | Test `success_negativeSortOrderAppearsBeforeGames` passes |
+| 3 | Items with sortOrder >= 0 appear after or between games | VERIFIED | Tests `flatten_gamesGetSortOrderFromTime*` pass; games have sortOrder 100+minutes |
+| 4 | Day headers always appear first in each day's section | VERIFIED | Test `flatten_dayHeaderAlwaysFirst` passes; ItineraryFlattener.swift:58 appends header first |
+| 5 | Same semantic state produces identical row order | VERIFIED | Test `success_sameStateProducesIdenticalOrder` passes |
+| 6 | Item with sortOrder -1.0 appears before all games | VERIFIED | Test `success_negativeSortOrderAppearsBeforeGames` explicitly tests this |
+| 7 | Reordering an item and re-flattening preserves new order | VERIFIED | Test `success_reorderPreservesNewOrder` passes |
+
+**Score:** 7/7 truths verified
+
+### Required Artifacts
+
+| Artifact | Expected | Status | Details |
+|----------|----------|--------|---------|
+| `SportsTime/Core/Models/Domain/ItineraryFlattener.swift` | Pure flatten function | VERIFIED | 124 lines, exports `flatten(days:itineraryItems:gamesByDay:)`, no stubs |
+| `SportsTime/Features/Trip/Views/ItineraryTableViewController.swift` | Refactored reloadData() using ItineraryFlattener | VERIFIED | Line 444 calls `ItineraryFlattener.flatten()`, no beforeGames/afterGames buckets |
+| `SportsTimeTests/Domain/ItineraryFlattenerTests.swift` | Determinism and ordering tests | VERIFIED | 765 lines, 13 tests, all pass |
+
+### Key Link Verification
+
+| From | To | Via | Status | Details |
+|------|----|-----|--------|---------|
+| `ItineraryTableViewController.reloadData()` | `ItineraryFlattener.flatten()` | function call | WIRED | Line 444 calls flattener with days, itineraryItems, gamesByDay |
+| `ItineraryFlattenerTests` | `ItineraryFlattener.flatten()` | test assertions | WIRED | 13 tests call flatten and verify output |
+
+### Requirements Coverage
+
+| Requirement | Status | Evidence |
+|-------------|--------|----------|
+| FLAT-01: Visual flattening sorts by sortOrder within each day | SATISFIED | `positioned.sort { $0.sortOrder < $1.sortOrder }` at line 93 |
+| FLAT-02: Flattening is deterministic and stateless | SATISFIED | Pure function enum with no instance state; test confirms identical output |
+| FLAT-03: sortOrder < 0 for "before games", >= 0 for "after/between games" | SATISFIED | Games get sortOrder 100+minutes; negative sortOrder items sort before |
+
+### Anti-Patterns Found
+
+| File | Line | Pattern | Severity | Impact |
+|------|------|---------|----------|--------|
+| None | - | - | - | No anti-patterns detected |
+
+Scanned files:
+- `ItineraryFlattener.swift`: No TODO/FIXME/placeholder/stub patterns
+- `ItineraryTableViewController.swift`: No beforeGames/afterGames bucket logic remains
+
+### Human Verification Required
+
+None - all phase goals are verifiable programmatically through:
+1. Code inspection (sortOrder-based sorting logic)
+2. Automated tests (13 passing tests covering all success criteria)
+
+### Verification Summary
+
+Phase 3 goal fully achieved:
+
+1. **ItineraryFlattener utility created** - Pure function that transforms hierarchical day data into flat display rows sorted by sortOrder
+2. **reloadData() refactored** - Now uses `ItineraryFlattener.flatten()` instead of bucket-based beforeGames/afterGames approach
+3. **Determinism verified** - Same semantic state produces identical row order (tested)
+4. **sortOrder conventions enforced** - Negative sortOrder items appear before games, positive after/between
+
+The old bucket-based flattening code has been completely removed. The new implementation is pure, testable, and deterministic.
+
+---
+
+*Verified: 2026-01-18T22:30:00Z*
+*Verifier: Claude (gsd-verifier)*