<?xml version="1.0" encoding="UTF-8"?>
<!--
  mend.rest - machine-readable sitemap.

  NO lastmod, changefreq or priority ON ANY ENTRY, deliberately. This file is
  written by hand and nothing regenerates it when a page changes, so a date
  here would be a claim the file cannot substantiate - which is exactly the
  thing this project treats as a defect rather than a rounding error. All
  three are hints and none of them is required.

  THE xmlns IS AN IDENTIFIER, NOT A FETCH TARGET. The 0.9 sitemap protocol
  declares a default namespace on <urlset>, and that declaration is an
  absolute URL naming a schema. Nothing dereferences it: no crawler fetches
  it, no parser retrieves it, and removing it would not remove a network
  dependency because there was never one to remove - it would only make this
  a non-conformant document.

  The portal's origin allowlist (scripts/verify-portal.sh) cannot tell an
  identifier from a URL by looking at it, so the distinction is made
  explicitly there rather than left to a reader: the host is permitted as an
  xmlns attribute value, in this file only, and the gate asserts that it is
  never an href, src, link, @import, url(), fetch, XHR or beacon target
  anywhere in the shipped tree. The portal still loads nothing from anyone.
-->
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
  <url>
    <loc>https://mend.rest/</loc>
  </url>
  <url>
    <loc>https://mend.rest/signup</loc>
  </url>
  <url>
    <loc>https://mend.rest/connect</loc>
  </url>
  <url>
    <loc>https://mend.rest/dashboard</loc>
  </url>
  <url>
    <loc>https://mend.rest/reports</loc>
  </url>
  <url>
    <loc>https://mend.rest/verify</loc>
  </url>
  <url>
    <loc>https://mend.rest/share</loc>
  </url>
  <url>
    <loc>https://mend.rest/terms</loc>
  </url>
  <url>
    <loc>https://mend.rest/privacy</loc>
  </url>
  <url>
    <loc>https://mend.rest/sitemap</loc>
  </url>
</urlset>
