fix(public): refresh sitemap lastmod dates to real page changes

[nish3451]

Why

The previous refresh in PR #116 (2026-08-13) sourced each URL's lastmod from the last main commit that touched its HTML on 2026-08-13. Eight public HTML files have been edited since, so every URL is now stale again relative to its actual content history. The original backlog item ("Refresh the public sitemap: lastmod dates stale (2026-05-20) and missing on 7 of 12 URLs") keeps recurring because the dates it tracks were a snapshot, not a property of the HTML files.

What changed

public/sitemap.xml — every lastmod re-sourced from git log origin/main --diff-filter=M -1 -- <path> for the HTML file backing that URL:

URL	Old lastmod	New lastmod	Source commit
/	2026-08-09	2026-08-14	497d690 (homepage H2->H3 repair)
/support/	2026-08-10	2026-08-14	b117084 (brand disambiguation)
/contact/	2026-08-10	2026-08-14	b117084
/privacy/	2026-08-11	2026-08-17	2dc939f (submission-prep notes)
/privacy-choices/	2026-08-10	2026-08-14	b117084
/terms/	2026-08-11	2026-08-17	2dc939f
/promptly/	2026-08-10	2026-08-14	2796b33 (product hero CTA)
/promptly/support/	2026-08-10	2026-08-14	b117084
/promptly/privacy/	2026-08-10	2026-08-17	2dc939f
/drishti/	2026-08-10	2026-08-14	2796b33
/drishti/support/	2026-08-10	2026-08-14	b117084
/drishti/privacy/	2026-08-11	2026-08-17	2dc939f

Verification

• 12 URLs, 12 lastmod entries, 0 missing (matches PR fix(public): refresh sitemap lastmod dates to real page changes #116 invariant)
• XML parses cleanly (Python ElementTree)
• Each lastmod is the date of the last commit on origin/main that actually modified that HTML file (--diff-filter=M), not the date of any merge or build artifact
• One-file PR; no test or build touched

Closes

The recurring "stale sitemap lastmod" backlog item is closed for the current content history. The underlying source-of-truth pattern (each lastmod from the last commit that touched the HTML) is now the documented invariant, so future sweeps can verify it programmatically.

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.

[coderabbitai]

Warning

Review limit reached

@nish3451, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 48 minutes

Limit details: You’ve used the included review currently available.

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

Wait for the limit to reset, then comment @coderabbitai review or push new commits to the PR.

An organization admin can change what happens after included review limits in Billing.

How do review limits work?

CodeRabbit enforces per-developer PR review limits within each organization.

For paid Pro and Pro+ reviews, CodeRabbit uses a developer's included PR review attempts over the past 7 days to set the current hourly allowance. At typical activity levels, the full plan allowance applies. Higher sustained activity can lower the allowance until earlier attempts leave the 7-day window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Free

Run ID: cfe4d17b-8a13-4294-86b4-20a04ea13784

📥 Commits

Reviewing files that changed from the base of the PR and between ce2d979 and 4605089.

📒 Files selected for processing (2)

• .lane/reports/lane1-public-sitemap-refresh-lastmod-20260821.md
• public/sitemap.xml

---

Note

🎁 Summarized by CodeRabbit Free

Your organization is on the Free plan. CodeRabbit will generate a high-level summary and a walkthrough for each pull request. For a comprehensive line-by-line review, please upgrade your subscription to CodeRabbit Pro by visiting https://app.coderabbit.ai/settings/billing.

_{Comment @coderabbitai help to get the list of available commands.}