<?xml version="1.0" encoding="UTF-8"?>
<!--
  002 T026 (US3, research.md D13 / contracts §C) — the STATIC root sitemap
  INDEX, served at https://chargesites.net/sitemap.xml (the S3 default
  behavior, same as robots.txt — no SSR, no CloudFront behavior change).

  Exactly two section children, per D13:
    - the digest's own sitemap (shipped 010/011, LIVE, untouched by 002)
    - the shell's dynamic sitemap (apps/shell/src/pages/sitemap.xml.ts, T024 —
      home/help/listings/providers + every PUBLISHED listing's canonical URL)

  This file changes only when a THIRD section is added (a deploy event) — it
  is intentionally not code-generated. It ships in the SAME deploy that makes
  the shell live (Stage B, T043): admission ("children must 200 before the
  index references them", D13) is enforced by that deploy being atomic, not
  by this file's build order — the digest child already 200s in production
  today, and the shell child 200s from the moment Stage B lands. The robots.txt
  Sitemap: pointer keeps pointing directly at the digest child until the
  cutover wave (US6 T040) flips it to this root index instead.

  T027 extends chargesites-tester/tests/shell-public.spec.ts to walk this
  index end-to-end against a live deploy (index -> children -> every loc
  200, zero auth-walled/redirecting locs; SC-004 evidence); that live
  verification is deliberately NOT duplicated here.
-->
<sitemapindex xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
  <sitemap>
    <loc>https://chargesites.net/au/digest/sitemap.xml</loc>
  </sitemap>
  <sitemap>
    <loc>https://chargesites.net/au/sitemap.xml</loc>
  </sitemap>
</sitemapindex>
