<?xml version="1.0" encoding="UTF-8"?>
<!-- ninemin.lilulab.ai — derived, not typed. Re-derive before every publish.

     lastmod = the committer date of the last commit that changed that page's HUMAN
     CONTENT, derived the same way as willcall's: take every commit that touched the
     file, strip <script> and <style> from the blob at each one, and keep the newest
     commit whose stripped body differs from its parent's. All five read d225195
     (2026-09-26T10:37:56+00:00) — the commit that corrected the Vercel-analytics
     sentence, whose second clause overclaimed, on all five pages. The previous file claimed 2026-09-24, which was already stale by
     two content changes; it understated recency, which is the safe direction and was
     still wrong.

     No changefreq, no priority. Every changefreq value this file used to ship was
     contradicted by the page's own history — four of the five declared "monthly" and
     were content-edited twice in two days. Google: "changefreq specifically is also
     conceptually overlapping with lastmod." Google does not use priority at all. -->
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
  <url>
    <loc>https://ninemin.lilulab.ai/</loc>
    <lastmod>2026-09-26T11:39:53+00:00</lastmod>
  </url>
  <url>
    <loc>https://ninemin.lilulab.ai/no-output-after-50-turns/</loc>
    <lastmod>2026-09-26T11:39:53+00:00</lastmod>
  </url>
  <url>
    <loc>https://ninemin.lilulab.ai/max-turns-vs-timeout-vs-context/</loc>
    <lastmod>2026-09-26T11:39:53+00:00</lastmod>
  </url>
  <url>
    <loc>https://ninemin.lilulab.ai/died-before-the-timeout/</loc>
    <lastmod>2026-09-26T11:39:53+00:00</lastmod>
  </url>
  <url>
    <loc>https://ninemin.lilulab.ai/recursion-limit-max-iter-max-turns/</loc>
    <lastmod>2026-09-26T11:39:53+00:00</lastmod>
  </url>
</urlset>
