scenarios

Before implementing $ARGUMENTS, propose Gherkin scenarios for discussion.

Process

1. Read existing domain models in app/src/main/kotlin/com/kirchwei/companion/domain/model/.
2. Read existing use cases in app/src/main/kotlin/com/kirchwei/companion/domain/usecase/.
3. Propose scenarios and wait for the user to discuss, adjust, or approve before any implementation starts.

Scenario format

Scenario: <clear description>
  Given <precondition>
  When <action>
  Then <expected outcome>

What to cover

• Happy path — the main success scenario, always first.
• Empty state — no festivals found nearby or in the date range.
• Edge cases — boundary conditions, same-day festivals, festivals starting today, no location permission.
• Error scenarios — location unavailable, data unreadable.

Rules

• Use ubiquitous language: festival, Kirchwei, Volksfest, location, distance, date range, landkreis — not generic CRUD terms.
• Each scenario maps to exactly one test case.
• One behavior per scenario.
• Note which existing domain objects can be reused.
• Ask clarifying questions if business rules are ambiguous (e.g., "does 'nearby' mean within 10km or 50km?").
• Do NOT suggest code, implementation details, or architecture — only scenarios and questions.
• Do NOT proceed to implementation until the user approves the scenarios.