[SPIKE] Figure out how to connect with DOOT

Description:

Let's figure out how we can connect to DOOT and how this aligns with reservation scheduling business rules.

Acceptance Criteria:

[Note: Use 'Given/When/Then' format if it makes sense to. Otherwise, a simple checklist that can be tested.]

Development Checklist:

• ...
• ...
• ...

Dependencies

• Blocked by
• Blocking

Relevant documentation as reference

Definition of Ready

• Acceptance criteria are included
• Wireframes are included (if applicable)
• Design / Solution is accepted by Product Owner (if applicable)
• Dependencies are identified (technical, business, regulatory/policy)
• Story has been estimated (under 13 pts)

Definition of Done

• In progress:
  • Acceptance criteria are tested (Functionality meets the acceptance criteria defined in the ticket)
  • UI meets accessibility requirements
  • Unit tests are written
  • Work is traceable in GitHub
  • PR linked to ticket number
  • If needed/required - Dev adds flag/label to highlight any migration steps necessary prior to PROD deployment
• Code review:
  • Code is peer reviewed and has passed CI/CD tests
• QA:
  • Acceptance criteria are tested (Functionality meets the acceptance criteria defined in the ticket)
  • Code is potentially shippable to the production environment
  • Functional features have been tested and passed by QA
  • UI components tested by designer
  • Code is deployed to PROD when moved to 'done' column (unless requested otherwise by PO)
• PO Review:
  • Acceptance criteria are tested (Functionality meets the acceptance criteria defined in the ticket)
  • Reviewed and approved by Product Owner

Notes:

No files, tests, entry points, acceptance criteria, or relevant documentation are identified. Start by investigating how the TypeScript application could connect to DOOT and how that fits reservation scheduling business rules; define testable Given/When/Then or checklist criteria, dependencies, and a decision for Product Owner review.