Problem
Prerelease documentation and qualified artifact pins change frequently, but the generated sitemap currently publishes only generic frequency and priority hints. Crawlers can retain obsolete quickstart versions and product-status wording after the live page has changed, creating a misleading first impression for evaluators.
Acceptance
- Emit a valid
<lastmod> value for documentation and blog routes based on the route's actual source modification, not a blanket build timestamp.
- Leave unchanged routes stable across unrelated deploys so the signal remains trustworthy.
- Include the same accurate freshness signal for generated public discovery artifacts whose contents change independently.
- Preserve the complete canonical route inventory, redirects, robots policy, and existing release-audit outputs.
- Add structural tests for changed-route updates, unchanged-route stability, valid W3C date formatting, and the generated discovery entries.
- Verify the deployed sitemap contains current modification dates for the 2.0 introduction and quickstart and that both live pages serve the current published-artifact wording.
Completion
The production sitemap and live pages expose accurate, current freshness metadata, and the repository's docs build and public-boundary checks pass.
Problem
Prerelease documentation and qualified artifact pins change frequently, but the generated sitemap currently publishes only generic frequency and priority hints. Crawlers can retain obsolete quickstart versions and product-status wording after the live page has changed, creating a misleading first impression for evaluators.
Acceptance
<lastmod>value for documentation and blog routes based on the route's actual source modification, not a blanket build timestamp.Completion
The production sitemap and live pages expose accurate, current freshness metadata, and the repository's docs build and public-boundary checks pass.