<?xml version="1.0" encoding="UTF-8"?>
<!-- Canonical URLs (no trailing slash, no .html) — matches the cdn-kizuna
     CloudFront canonicalization. Marketing pages only; app/auth routes are
     excluded (also Disallow'd in robots.txt). -->
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
  <url>
    <loc>https://kizuna.host/</loc>
    <changefreq>weekly</changefreq>
    <priority>1.0</priority>
  </url>
  <url>
    <loc>https://kizuna.host/about</loc>
    <changefreq>monthly</changefreq>
    <priority>0.6</priority>
  </url>
  <url>
    <loc>https://kizuna.host/terms-of-service</loc>
    <changefreq>yearly</changefreq>
    <priority>0.3</priority>
  </url>
  <!-- /privacy-policy, /refund-policy, /about-us, /community-guidelines and
       /host-agreement are hosted and routable but deliberately NOT listed:
       none has been filed in the policies repo's published/ archive (every
       <policy>/published/ is empty, and host-terms/ has no such directory).
       Each screen carries a meta-robots noindex for the same reason — a
       Disallow would hide that directive instead of delivering it, which is
       why they stay crawlable.

       ⚠️ The ORIGINAL reason — "they still print an unset [● — set on
       publication] date" — is now DEAD. Every hosted file reads "Last updated:
       26 August 2026 · Version 1.0"; no placeholder survives anywhere in the
       corpus. So seeing a real date on these pages is NOT clearance to lift the
       hold — the published/ archive is. Do not re-derive it from the dates.

       Add the five url entries and drop the five noindex tags in the same
       commit that publishes the documents — __tests__/public/seo.test.ts locks
       the pair, so a half-done flip fails CI rather than shipping.
       /terms-of-service is listed because it is the one document cleared to
       index, not because of its date. -->
</urlset>
