fix(sitemap): don't drop lastmod for an epoch (0) timestamp

[durvesh1992]

Motivation

createSitemapItem decides a route's <lastmod> from route.metadata.lastUpdatedAt (a numeric timestamp, e.g. derived from front matter last_update: {date: ...}). Two checks use truthiness on that number:

// getRouteLastUpdatedAt
if (route.metadata?.lastUpdatedAt) { ... }            // 0 is falsy → skipped
// getRouteLastmod
return lastUpdatedAt ? formatLastmod(...) : null;      // 0 → null

So a legitimate timestamp of 0 (1970-01-01T00:00:00Z) is treated as "no value" and the <lastmod> is silently omitted. The adjacent === null early-return already shows the intent to distinguish absent from present — the truthiness checks defeat that for 0.

Fix

Use != null in both places so 0 is preserved (while still treating null/undefined as absent).

Test plan

pnpm vitest run packages/docusaurus-plugin-sitemap

Added a regression test (lastUpdatedAt: 0 → lastmod: '1970-01-01') that fails before this change and passes after. Full sitemap package: 53 tests pass.

[netlify]

✅ [V2]

Built without sensitive environment variables

Name	Link
🔨 Latest commit	15ac020
🔍 Latest deploy log	https://app.netlify.com/projects/docusaurus-2/deploys/6a42f75471e7ac000835085b
😎 Deploy Preview	https://deploy-preview-12212--docusaurus-2.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[slorber]

Hmmm, ok to merge this but really wonder what the use case for having a lastmod with epoch 0 ?

Is this only theoretical and for correctness, or do you plan to use this in practice?