[maxdiluca]

Why

Current main fails a strict Hugo build because the SEO sitemap is mounted as an unrecognized render hook. A non-strict build also reports deprecated maintenance metadata and duplicate output paths for four author terms.

Changes

Extract only the three independent website repairs from draft PR #37 (40 additions, 2 deletions):

• Restrict four generated author terms to link-only rendering and exclude them from lists, leaving their file-backed profiles as the rendered route owners.
• Preserve the SEO module's assets/layouts mounts while relocating its sitemap template to layouts/sitemap.xml. The existing transitive blox-seo v0.2.2 dependency remains unchanged.
• Replace maintenance-page _build: {list: true} with build: {list: always}.

Based on main f7be069, rechecked on 11 October 2026. No profile content, synchronization code, workflows, dependency versions or deployment configuration are changed. PR #37 remains open and draft; this PR does not enable its automatic or manual handoffs.

Validation executed on 11 October 2026

• Applied the isolated three-file patch cleanly to current main; git diff --check passed.
• Installed official Hugo 0.152.2 extended (archive SHA-256 416bcfbdf5f68469ec9644dbe507da50fc21b94b69a125b059d64ed2cb4d8c27) and Go 1.25.1 in a local execution environment.
• Main strict build failed on the sitemap warning (exit 2). A non-strict main build completed and reproduced the deprecated _build warning and all four duplicate HTML/RSS author paths.
• Final sequential repair build passed, exit 0, without warnings: GOMAXPROCS=2 hugo --environment production --printPathWarnings --panicOnWarning --cleanDestinationDir --destination /tmp/vr-fixed-verified (367 pages, 12 paginator pages, 392 processed images).
• Compared generated outputs: all 141 author HTML routes preserved; author href lists unchanged in all 22 People/post/publication HTML pages checked; each of the four affected routes contains identifying file-backed profile content.
• Generated sitemap XML parses and the maintenance route exists.
• Initial overlapping build attempts encountered image-processing/runtime errors. After those attempts finished, the sequential build above completed successfully. These initial failures are not counted as passing tests.

The synthetic receiver, manual-handoff and proposal tests described in #37 on 2 October were NOT rerun and are not evidence for this PR. No profile transfer or publication was performed.

Before merging

• Review the three-file diff and deployment preview, particularly the four affected author pages, People cards, representative publication links and sitemap.
• Confirm the actual Netlify build/preview checks succeed, including its minification/plugins and redirect handling; the local strict build does not validate those host-side steps.
• Keep Prepare approved profile handoffs and strict website builds #37 draft for its separate native authorization/integration validation. Once these repairs merge, update/rebase Prepare approved profile handoffs and strict website builds #37 against main to remove the already-landed fixes from its diff.

No merge or production deployment is requested by this PR.