[Proposal] Add event organization foundations

[guyghost]

Summary

Implement core event organization features to establish the foundation for Wakeve's collaborative event planning system.

• Event Creation: Organizers can create events with proposed time slots and voting deadlines
• Availability Polling: Participants vote on slots using YES/MAYBE/NO with weighted scoring
• Date Confirmation: Organizers validate and lock the final event date
• Domain Models: Event, TimeSlot, Poll, Vote with complete scoring logic

Related Issue

Relates to #2

Documentation

• Design: https://github.com/guyghost/wakeve/blob/change/add-event-organization/docs/changes/add-event-organization/design.md
• Specs: https://github.com/guyghost/wakeve/blob/change/add-event-organization/docs/changes/add-event-organization/specs.md
• Architecture: Event, TimeSlot, Poll, Vote domain models with in-memory EventRepository
• Scoring: Weighted voting (YES=2, MAYBE=1, NO=-1) for best slot calculation

What Changed

• Created domain models in shared KMP module (Event, TimeSlot, Poll, Vote)
• Implemented EventRepository with in-memory storage
• Added PollLogic with weighted slot scoring algorithm
• Updated UI App.kt with event creation and polling UI
• Created comprehensive design and specification documentation

Implementation Status

✅ Phase 1: Core Models & Logic
⏳ Phase 2: Persistence & Full UI
⏳ Phase 3: Timezone & Validation
⏳ Phase 4: Integration with Downstream Agents

[Copilot]

Pull Request Overview

This PR adds a proposal document for implementing event organization functionality in the Wakeve application, following the OpenSpec spec-driven development workflow. The proposal outlines the addition of core event management features including event creation, availability polls, deadline management, and date validation for event organizers.

Key Changes

• Introduces proposal document for the add-event-organization change
• Defines scope to add event data models, UI components, and organizer controls
• Targets implementation across shared Kotlin module, Android (Jetpack Compose), and future iOS support

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

Pull Request Overview

Copilot reviewed 53 out of 248 changed files in this pull request and generated 4 comments.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

Using Random.nextLong().toString() for IDs can produce collisions and negative values. Use a proper UUID generator (e.g., kotlinx-uuid) or ensure unique ID generation with a prefix/timestamp to prevent ID conflicts.

[Copilot]

The hardcoded date '2024-01-01' is in the past. Consider using a dynamic date calculation (e.g., current date + offset) to avoid creating events with expired dates during testing.

[Copilot]

The Poll is initialized with the same value for both id and eventId (event.id). Consider using distinct IDs or clarifying if this duplication is intentional through documentation.

Suggested change

	class EventRepository {
	private val events = mutableMapOf<String, Event>()
	private val polls = mutableMapOf<String, Poll>()
	fun createEvent(event: Event) {
	events[event.id] = event
	polls[event.id] = Poll(event.id, event.id, emptyMap())
	import java.util.UUID
	class EventRepository {
	private val events = mutableMapOf<String, Event>()
	private val polls = mutableMapOf<String, Poll>()
	fun createEvent(event: Event) {
	events[event.id] = event
	val pollId = UUID.randomUUID().toString()
	polls[event.id] = Poll(pollId, event.id, emptyMap())

[guyghost]

Implementation Complete ✅

All 10 event organization requirements have been implemented and tested:

Summary

• ✅ Phase 1: Domain models, business logic, Android UI (16 tests)
• ✅ Phase 2 Sprint 1: SQLDelight persistence, multiplatform DB (20 tests)
• ✅ Phase 2 Sprint 2: REST API endpoints, error handling (0 failures)
• ✅ Total: 36 tests passing (100%), build successful

Test Results

• EventRepositoryTest: 10/10 ✅
• PollLogicTest: 6/6 ✅
• DatabaseEventRepositoryTest: 13/13 ✅
• OfflineScenarioTest: 7/7 ✅
• ApplicationTest (API): 1/1 ✅

Build Status

• shared module: ✅ Compiles
• composeApp module: ✅ Compiles
• server module: ✅ Compiles
• All tests: ✅ Pass

Requirements Coverage

1. ✅ Event creation with slots and deadline
2. ✅ Participant invitation and management
3. ✅ Poll status transition
4. ✅ Voting with YES/MAYBE/NO
5. ✅ Voting deadline enforcement
6. ✅ Weighted vote scoring
7. ✅ Event confirmation
8. ✅ Timezone-aware display
9. ✅ Role-based access control
10. ✅ Data persistence

Ready for approval and merge to main.