Scaffold GillyTracker reporter SPA from keboo.react and adapt to existing Azure infra

[Copilot]

This PR turns the repo into a web-based Gilly sighting reporter using keboo.react 1.13.1, while adapting deployment assumptions to existing Azure resources instead of provisioning a full new stack.
The app is now a no-auth single-page flow that captures geolocation (with manual fallback) plus reporter contact/details, and persists reports to SQL under the GillyTracker schema.

• Template bootstrap and repo initialization

  • Generated the solution from Keboo.Dotnet.Templates@1.13.1 (keboo.react) as the project baseline.

• Reporter-focused SPA flow (no auth)

  • Replaced the frontend app entry experience with a single-page report form.
  • On load, attempts navigator.geolocation.getCurrentPosition(...).
  • If location is unavailable/denied, user can manually enter latitude/longitude.
  • Added freeform details/contact field and submit path to backend API.

• Backend API and data model for sightings

  • Added SightingsController with POST /api/sightings (+ retrieval endpoint).
  • Added coordinate validation and details-length validation.
  • Added DogSightingReport entity and DbSet mapping to:
    • table: GillyTracker.DogSightingReports
    • coordinate precision configured in EF model.

• Existing-infra alignment (Terraform)

  • Updated infra composition to consume existing Azure resources via variables/data lookups (RG, ACR login server, Container App Environment, existing DB connection string).
  • Removed assumptions that this app should always create net-new SQL/SWA/shared infra for this use case.

• Docs and metadata alignment

  • Updated root README to describe the Gilly reporting workflow and existing-infra expectations.
  • Updated web metadata description and UI test README wording to remove stale Q&A-template framing.

// GillyTracker.Web/src/App.tsx (simplified)
navigator.geolocation.getCurrentPosition(
  ({ coords }) => {
    setLatitude(coords.latitude.toFixed(7))
    setLongitude(coords.longitude.toFixed(7))
  },
  () => {
    // manual entry fallback
  },
  { enableHighAccuracy: true, timeout: 10000 }
)

await apiClient.post('/api/sightings', {
  latitude: Number(latitude),
  longitude: Number(longitude),
  details,
})

Original prompt

I want to create a web based project to allow people to report the location of my dog Gilly. I have a sample react template that I would like to base this on, keboo.react inside of Keboo.Dotnet.Templates. Use version 1.13.1.

That template wants to create new infra for everything, but I have some existing infrastructure I would like to use.
Database: https://portal.azure.com/#@keboo.dev/resource/subscriptions/9f47860f-97e3-418d-b0ac-c514c26274a4/resourceGroups/KebooDev/providers/Microsoft.Sql/servers/keboodev-sql/databases/keboodevdb/queryEditor
ACR: https://portal.azure.com/#@keboo.dev/resource/subscriptions/9f47860f-97e3-418d-b0ac-c514c26274a4/resourceGroups/KebooDev/providers/Microsoft.ContainerRegistry/registries/keboodevacr/overview
Container App Environment: https://portal.azure.com/#@keboo.dev/resource/subscriptions/9f47860f-97e3-418d-b0ac-c514c26274a4/resourceGroups/KebooDev/providers/Microsoft.App/managedEnvironments/keboodev-env/containerAppEnvironment

For the database, I want to use a GillyTracker schema.
The app will not need auth.
This will be a single page application. I plan to print a QR code and put it on my dogs collar linking to the web page. When the page loads I want it to attempt to collect the user's location. If location services are not allowed or enabled, allow for the user to manually enter them. I want there to be a text field for the user to put in any details needed about themselves or contact information where I can reach them to pick up my dog.