admin/Sportstime
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
Files
5ed4e309bd62872f419c0a837de511a809ff7a06
Sportstime/.planning/ROADMAP.md
Trey t 1d7a7d9cbe docs(09-03): complete scenario C corridor efficiency TDD plan 
Phase 9 complete: All three trip planner modes validated with TDD.

Summary of 09-03 accomplishments:
- Feature 1: Corridor game inclusion (5 tests, 1 fix)
  - Enhanced findDirectionalStadiums() to exclude beyond-endpoint games
- Feature 2: Anti-backtracking validation (7 tests, all passed)
  - Confirmed existing implementation validates monotonic progress

12 tests added, 3 commits (2 test, 1 feat).

State updates:
- Progress: 30% → 40%
- Phase 9: Complete (3/3 plans)
- Next: Phase 10 (Trip Builder Options TDD)

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
2026-01-10 15:43:23 -06:00

5.3 KiB
Raw Blame History

Roadmap: SportsTime

Milestones

  • ✅ v1.0 Data Pipeline (Phases 1-7) — SHIPPED 2026-01-10
  • 🚧 v1.1 TDD & Correctness — Phases 8-12 (in progress)

Completed Milestones

v1.0 Data Pipeline (Phases 1-7) — SHIPPED 2026-01-10
  • Phase 1: Script Architecture (3/3 plans) — completed 2026-01-10
  • Phase 2: Stadium Foundation (2/2 plans) — completed 2026-01-10
  • Phase 2.1: Additional Sports Stadiums (3/3 plans) — completed 2026-01-10
  • Phase 3: Alias Systems (2/2 plans) — completed 2026-01-10
  • Phase 4: Canonical Linking (1/1 plans) — completed 2026-01-10
  • Phase 5: CloudKit CRUD (2/2 plans) — completed 2026-01-10
  • Phase 6: Validation Reports (1/1 plans) — completed 2026-01-10
  • Phase 7: Testing & Documentation (1/1 plans) — completed 2026-01-10

Full details: milestones/v1.0-ROADMAP.md

🚧 v1.1 TDD & Correctness (In Progress)

Milestone Goal: Test-driven validation of trip planning engine — tests define correctness, code must match

Constraints:

  • TDD approach: Write tests first with expected behavior, then fix code if tests fail (never modify tests to pass)
  • Tests must include edge cases and error conditions
  • Mix of short and long trips in test data, varied by region and mileage

Phase 8: DAG System TDD

Goal: Performance and edge case tests with tens of thousands of objects; fix code if tests fail Depends on: v1.0 milestone complete Research: Unlikely (internal patterns, existing code) Plans: 2 Status: Complete Completed: 2026-01-10

Plans:

  • 08-01: GameDAGRouter edge cases and anchor validation TDD — completed 2026-01-10
  • 08-02: GameDAGRouter performance with large datasets and diversity coverage TDD — completed 2026-01-10

Phase 9: Trip Planner Modes TDD

Goal: Test game scheduling (by dates), must-see games inclusion, start/end cities routing Depends on: Phase 8 Research: Unlikely (internal patterns) Plans: 3 Status: Complete Completed: 2026-01-10

Test expectations:

  • By Dates: Game scheduling fits date range, no conflicts, date boundaries respect timezone
  • Must-See: All selected games appear, filler games don't conflict, impossible combos return error
  • Start/End Cities: Route begins at start city, ends at end city, games found along corridor

Plans:

  • 09-01: Scenario A timezone & conflict TDD — completed 2026-01-10
  • 09-02: Scenario B filler conflict TDD — completed 2026-01-10
  • 09-03: Scenario C corridor efficiency TDD — completed 2026-01-10

Phase 9.1: Fix Flaky Test When Ran In Parallel (INSERTED)

Goal: Resolve test suite flakiness where tests pass individually but fail in parallel execution Depends on: Phase 9 Research: Unlikely (Swift Testing isolation patterns) Plans: 0 plans

Plans:

  • TBD (run /gsd:plan-phase 9.1 to break down)

Details: 5 tests fail in full suite but pass individually due to Swift Testing parallel execution + simulator state pollution (discovered in Phase 9 plans 01-02). This phase addresses the root cause to ensure reliable CI/CD testing.

Phase 10: Trip Builder Options TDD

Goal: Test repeat cities option (ON/OFF) and must-stops (non-game attractions) Depends on: Phase 9 Research: Unlikely (internal patterns) Plans: TBD

Test expectations:

  • Repeat Cities ON: Can visit Dallas twice for different games
  • Repeat Cities OFF: Visit each city once, algorithm picks best game
  • Must-stops: Non-game POIs (attractions) appear in itinerary

Plans:

  • 10-01: TBD (run /gsd:plan-phase 10 to break down)

Phase 11: Itinerary & Constraints TDD

Goal: Test travel itinerary output (directions, distance/time) and driving limits Depends on: Phase 10 Research: Unlikely (internal patterns) Plans: TBD

Test expectations:

  • Travel itinerary: Distance and time shown between each stop
  • Driving limits: 2 drivers × 400mi/day max = 800mi/day allowed; trips exceeding limit rejected

Plans:

  • 11-01: TBD (run /gsd:plan-phase 11 to break down)

Phase 12: Integration Validation

Goal: End-to-end scenarios and regression suite covering all planning modes Depends on: Phase 11 Research: Unlikely (internal patterns) Plans: TBD

Plans:

  • 12-01: TBD (run /gsd:plan-phase 12 to break down)

Progress

Phase Milestone Plans Complete Status Completed
1. Script Architecture v1.0 3/3 Complete 2026-01-10
2. Stadium Foundation v1.0 2/2 Complete 2026-01-10
2.1. Additional Sports Stadiums v1.0 3/3 Complete 2026-01-10
3. Alias Systems v1.0 2/2 Complete 2026-01-10
4. Canonical Linking v1.0 1/1 Complete 2026-01-10
5. CloudKit CRUD v1.0 2/2 Complete 2026-01-10
6. Validation Reports v1.0 1/1 Complete 2026-01-10
7. Testing & Documentation v1.0 1/1 Complete 2026-01-10
8. DAG System TDD v1.1 2/2 Complete 2026-01-10
9. Trip Planner Modes TDD v1.1 2/3 In progress -
9.1. Fix Flaky Test When Ran In Parallel v1.1 0/? Not started -
10. Trip Builder Options TDD v1.1 0/? Not started -
11. Itinerary & Constraints TDD v1.1 0/? Not started -
12. Integration Validation v1.1 0/? Not started -
Reference in New Issue View Git Blame Copy Permalink