<?xml version="1.0" encoding="UTF-8"?>
<!--
  THREE URLs, and that is the whole site. The landing itself is a single page: the locale switch,
  the waitlist form and the referral link (/?ref=<code>) are all states of it, not separate
  documents, and listing a referral URL here would publish somebody's code to a crawler.

  The other two are the legal documents (F-7 / R-18, 2026-08-27). They are listed because
  robots.txt on this origin says `Allow: /` to everybody: a document that is crawlable and absent
  from the sitemap is a document we have decided to publish and then declined to announce, and the
  privacy notice in particular is the first artefact counsel, an investor checklist, the NPC and
  any ad network ask for. They are STATIC FILES in apps/landing/public/, which Vite copies into
  dist/ verbatim — no transform, no hashing — so the paths below are exactly the paths that ship.

  `talent-terms-2026-08.html` carries its version in its NAME, deliberately. That string is what
  apps/portal/src/talent-register.tsx records into the append-only `consent_events` table for every
  talent who ticks the box, and a consent row has to name a document that was actually shown. A
  counsel-reviewed replacement publishes under a NEW version string and gets its own <loc> here;
  this one does not move, because the records that name it do not move either.
  apps/landing/test/legal-documents.test.ts pins the file name against the recorded string.

  <lastmod> is a claim about the PAGE, not about this file, so it moves when that page changes in
  a way a reader would notice — not on every deploy. A lastmod that is always today is a lastmod
  nobody believes, and Google says so out loud.

  NO <changefreq> AND NO <priority>. Google's own sitemap documentation says it ignores both.
  A file that states things nothing reads still has to be kept true by whoever edits it next,
  which is a cost with no buyer.

  The origin is absolute here for the same reason it is in robots.txt — the sitemap protocol
  requires <loc> to be a full URL, and a sitemap's URLs must share the origin it is served from.
  Move this and robots.txt together, or a crawler reads a sitemap that describes another site.
-->
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
  <url>
    <loc>https://lechonliga.com/</loc>
    <lastmod>2026-08-27</lastmod>
  </url>
  <url>
    <loc>https://lechonliga.com/privacy.html</loc>
    <lastmod>2026-08-27</lastmod>
  </url>
  <url>
    <loc>https://lechonliga.com/talent-terms-2026-08.html</loc>
    <lastmod>2026-08-27</lastmod>
  </url>
</urlset>
