<?xml version="1.0" encoding="UTF-8"?>
<!--
  ttsnx.com — sitemap of the public site.  [PUBLIC-SITE-SEO-SHARE]

  Caddy serves this file AS `/sitemap.xml` on ttsnx.com, and only there.

  🔴 WHAT IS IN HERE AND WHY THE LEGAL PAGES ARE NOT.
  A sitemap lists pages whose canonical address is THIS host. ttsnx.com serves
  four public routes, and two of them canonicalise elsewhere:

    /                          → canonical https://ttsnx.com/                ✅ listed
    /integrations/allegro      → canonical https://ttsnx.com/integrations/…  ✅ listed
    /legal                     → canonical https://app.ttsnx.com/legal       ❌ not listed
    /legal/polityka-prywatnosci→ canonical https://app.ttsnx.com/legal/…     ❌ not listed

  The two /legal routes are a deliberate second copy: the legal documents
  themselves print **app.ttsnx.com/legal** as their place of publication
  (`polityka-prywatnosci.md` line 4, `regulamin.md` line 4), and the Caddyfile
  serves them here as well only so a reader of the marketing page does not have
  to change hosts. Listing a URL here while a canonical header points somewhere
  else would be two contradictory signals about the same document. If the
  publication address is ever moved to this host, the canonical headers in the
  Caddyfile move first and these two URLs follow — the gate enforces that
  order by comparing the two files against each other.

  ⚠️ NO `<lastmod>`. A hand-written date here is a claim nobody would update; a
  sitemap that always says "changed today" is a sitemap crawlers learn to
  ignore. Absent beats stale.

  ⚠️ Nothing behind the login is listed, and it could not be reached from this
  host anyway — see `robots-public-site.txt` for why.
-->
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
  <url>
    <loc>https://ttsnx.com/</loc>
  </url>
  <url>
    <loc>https://ttsnx.com/integrations/allegro</loc>
  </url>
</urlset>
