[dev-ant]

Problem and behavior

The live item sitemap projection exceeded the public renderer's five-second deadline, causing /sitemap-items.xml and the sitemap index to return 503. Sitemap projections now have a bounded 20-second deadline; other public rendering retains five seconds. Incomplete or failed responses still return 503 and are never cached as empty XML.

The homepage's item lookup and route now explicitly use the same five-minute revalidation as its rankings. This prevents caught dynamic-rendering signals or a missing build-time gateway from permanently baking unavailable text into the homepage; item detail lookups remain uncached. A fresh image can serve its build-time fallback until that ISR interval expires. The release adopts the corrected shared deployment sitemap-index probe and advances the app version to 1.0.32.

Validation

• Regression tests cover an eight-second successful projection, the default five-second deadline, and a twenty-second abort followed by a successful cached retry.
• Full npm run verify: 123 suites / 594 tests, format, lint, typecheck, Knip and production build passed. Workflow contracts: 9 passed.
• JavaScript-disabled local production-mode homepage renders a visible permanent item anchor from synthetic providers; prerender revalidation is 300 seconds.
• A gateway-free production build retains the 300-second route interval. Expiring only the local generated artifact produced a STALE fallback followed by a HIT response containing the visible item link; no production cache or clock was changed.
• Deploy Batch projection recovery #136 before this consumer. Independent review of this final diff and its verification evidence found no blocking issue.