<?xml version="1.0" encoding="UTF-8"?>
<!--
  AIR-2196 — the sitemap for the APP HOST (local.blinko.ai).

  Why a second sitemap exists at all, and why this one is hand-written:

  `app/sitemap.ts` emits `marketingSiteUrl` (the apex) for every entry it builds
  from STATIC_MARKETING_ROUTES, so it structurally cannot list a URL that lives
  on the app host. A sitemap may only contain URLs from its own host unless it is
  cross-submitted through robots.txt — which is exactly how this one is declared.

  ⚠️ DO NOT "SIMPLIFY" THIS BY ADDING /scan/sample/ TO STATIC_MARKETING_ROUTES.
  That registry does double duty: listing a path there is also what forces the
  local -> apex 301 (hosting-rewrites.test.ts drives the AIR-1403 assertion off
  it). The apex already 301s /scan/:rest* -> local, so the result would be an
  INFINITE REDIRECT LOOP and the page would stop resolving entirely. The
  regression suite pins the absence with this reason attached.

  ONLY app-host URLs belong here, and only ones meant to be indexed. Today that
  is exactly one: /scan/ itself is Disallow'ed in robots.txt (it is a funnel, and
  /scan/report/?token= is per-visitor), while /scan/sample/ carries its own
  explicit Allow in both groups, is self-canonical, and is real content written
  to rank — a whole Growth Scan report readable without running one.

  No <lastmod>: the page is a fixture whose content changes only when the
  renderer does, and a date we would have to remember to update is worse than no
  date at all.
-->
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
  <url>
    <loc>https://local.blinko.ai/scan/sample/</loc>
    <changefreq>monthly</changefreq>
    <priority>0.7</priority>
  </url>
</urlset>
