<?xml version="1.0" encoding="UTF-8"?>
<!--
  ALIAS, NOT THE REAL SITEMAP (12 Aug).

  @astrojs/sitemap emits sitemap-index.xml and sitemap-0.xml, and robots.txt
  declares sitemap-index.xml. That is correct and unchanged. But /sitemap.xml is
  the conventional filename and crawlers try it directly: it turned up in
  Cloudflare's 4xx paths, which is how this was noticed.

  This file is an index pointing at the generated sitemap-0.xml rather than a
  copy of it, so it cannot go stale — the URL list lives in one place. If the
  sitemap integration is ever reconfigured to emit different filenames, this
  needs updating with it.

  Chose a static alias over a _redirects rule.

  THE REASON ORIGINALLY RECORDED HERE — that the project had no _redirects file
  and adding redirect machinery for one path was too heavy — STOPPED BEING TRUE
  ON 5 Sep, when a _redirects file was added for the /approach and /advisory
  renames. Corrected rather than deleted, because it was written down as the
  basis for the choice and the next person to read it would otherwise fold this
  into _redirects as an obvious simplification.

  THE CHOICE STILL STANDS ON ITS OWN. A redirect answers /sitemap.xml with a 301
  the crawler then has to follow; this answers it with the index directly. The
  4xx paths that prompted this file came from crawlers guessing a conventional
  filename, and the cheapest thing to hand them is the document, not a detour.
-->
<sitemapindex xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
  <sitemap>
    <loc>https://www.cernoglobal.com/sitemap-0.xml</loc>
  </sitemap>
</sitemapindex>
