Render configurable page metadata, starting with freshness and ownership #4183

What is getting in your way?

A page describing a deployment option, a limit, or a console workflow looks identical whether it was revised last week or three years ago. Readers either check the source file on GitHub or act on stale guidance.

Codex, the internal knowledge base, assembles content from many repositories. When a page is wrong, the reader has to identify the source repository and then the owning team before asking anyone.

The page gutter today offers "View as Markdown", "Report a docs issue", and "Edit this page". None of these answer "is this current?" or "who owns this?".

Most of the data exists already. The build computes a content-aware last-updated value for the search index and the sitemap, and resolves each page's source repository to construct the edit link. Ownership lives in each repository's CODEOWNERS file but is never read during the build.

Written in collaboration with Claude.

What would you like instead?

A generic metadata slot in the page chrome, populated by named fields that each content set enables. Freshness and ownership ship as the first two, with products, applies-to versions, or review status added later without new rendering work.

Anything else?

docs-builder documentation
Contributors directive
Add content_last_updated for content-only change tracking
Generate sitemap.xml from the index with correct last_updated dates