Promote develop to main: the vendored theme restored to upstream

[ptr727]

Promotes develop (43d167b) to main (2b132e4). Two commits, both merged with a clean review and green CI.

#40	Move the local edits out of the vendored theme, and document its width knobs
#41	Give .gallery-cols-5 the width its own pattern implies

What changed

themes/PaperMod/ is now byte identical to upstream 154d006e across all 125 files. It previously carried site customization in two of its own files, which made an update a diff-and-reapply rather than a directory replace, and put the repo in breach of its own CODESTYLE.md rule to override a theme template rather than edit the theme in place.

Both edits sat in extension points the theme documents for the purpose, and Hugo resolves a project's own trees ahead of the theme's, so both moved without a fork:

Customization	Now at
Lexend body font, and the gallery / gallery-cols-* rules	assets/css/extended/custom.css
Google Fonts preconnect and stylesheet links	layouts/_partials/extend_head.html

themes/README.md records the verification command, so "byte identical to upstream" stays checkable rather than asserted. It also gains a Customization points section documenting the four :root variables that govern layout width, since PaperMod exposes no width parameter to any template and finding that out otherwise costs a read of the theme's CSS.

The two root layouts/ overrides are untouched. They work around Hugo 0.158 deprecations upstream has not tracked, rather than customizing the site.

Verification

The live check was run against the local mirror, which is the half of the URL contract CI cannot reach: the validation workflow proves the 328 URLs that must render, and nothing in a build exercises the 917 redirects.

==> rules from release <id> (after 0s)
==> checking 328 URLs that must render
==> checking 917 URLs that must redirect
PASS - 1245 URLs honored

The release stamp confirmed the rules came from the release just installed rather than stale ones. The tree that passed is 71c4f05d, which is develop's tree exactly, so this result describes what is being promoted rather than an approximation of it.

Also verified across both commits:

• Rendered output byte identical before and after Move the local edits out of the vendored theme, and document its width knobs #40, hashed stylesheet filename included, by a full diff -r of the built site. That diff is the evidence the 125-file restore was safe, and is why Give .gallery-cols-5 the width its own pattern implies #41 was split out rather than folded in.
• For Give .gallery-cols-5 the width its own pattern implies #41, the rule-level diff of the emitted stylesheet is exactly one line, 25% to 20%.
• Build clean under hugo --gc --minify --panicOnWarning.
• URL contract in-build: 328/328 golden, 778/778 legacy images, 1012/1012 local assets.
• markdownlint, editorconfig-checker, and cspell scope all clean; no workflow, shell, or config files changed.

Not in this promotion

No publish. publish-release.yml is workflow_dispatch only, so merging here ships nothing, and the TODO.md item holding a release from main until the pipeline has soaked is untouched and still stands.

Switching the theme to a submodule or Hugo Modules was considered and declined; themes/README.md records why for the next reader. A submodule is the only fetch mechanism that would gain a bot, because PaperMod tags releases as v8.0, which is not valid semver, so Hugo Modules could only pin a pseudo-version and Dependabot does not upgrade those. Weighed against what a bot would have found: upstream's only commit in the three months to 2026-08-06 edited its own README. This work is the precondition either way.

One process finding came out of this and is filed at the hub as ProjectTemplate#597: #40 touched layouts/, which is one of the trigger paths for the pre-pull-request local verification in OPERATIONS.md, and that gate was missed before the pull request was opened. It has since been run and passes, as above.

Merge with a plain merge commit. Do not pass --delete-branch, which on a develop -> main promotion deletes develop.

🤖 Generated with Claude Code

[Copilot]

Pull request overview

This PR promotes develop to main, restoring the vendored PaperMod theme directory to be byte-identical with upstream and relocating prior theme customizations into Hugo’s intended project-level extension points (assets/ and layouts/).

Changes:

• Removed in-theme custom CSS and head overrides from themes/PaperMod/ and reintroduced them as project overrides (assets/css/extended/custom.css, layouts/_partials/extend_head.html).
• Expanded themes/README.md to document the upstream commit provenance, provide a reproducible verification command, and document PaperMod’s width-related CSS variables and override pitfalls.
• Updated TODO.md to track the remaining open decision around the fixed 720px content cap and point to the new documentation.

Reviewed changes

Copilot reviewed 6 out of 6 changed files in this pull request and generated no comments.

Show a summary per file

File	Description
TODO.md	Adds an open-decision note about fixed content width and references the new “Customization points” documentation.
themes/README.md	Documents upstream commit provenance, verification steps, and PaperMod width customization variables and override guidance.
themes/PaperMod/layouts/_partials/extend_head.html	Removes previously vendored Lexend font link tags to restore upstream equivalence.
themes/PaperMod/assets/css/extended/blank.css	Removes previously vendored custom body/gallery CSS rules to restore upstream equivalence.
layouts/_partials/extend_head.html	Adds the project-level extend_head.html override to load Lexend via Google Fonts without modifying the theme.
assets/css/extended/custom.css	Adds project-level custom CSS (Lexend body font selection + gallery layout rules), picked up by the theme’s extended CSS bundling.