chore: SVG comment XML-validity + drop stale "stamp time" prose

Andrew Dunnrequested to merge
andunn-reference-cleanup into main

What

Two small cleanups surfaced during the prune. Stacked on !20 (merged).

Fix Detail
SVG comment validity The template avatar.svg/hero.svg headers used -- inside an XML comment (avatar.svg -- ...), invalid per the XML spec. Strict parsers (rsvg-convert, xmllint) rejected the files even though browsers and GitLab render them. Changed to a colon. All six SVGs now pass xmllint + rsvg-convert.
Stale "stamp time" prose The site's template pages described the design subtree as "vendored at stamp time", but there is no stamp step now (new-project is gone). Reframed: the chrome is linked from the reference's Pages CDN by default, and vendored into site/public/design/ for an airgapped project.

npm run build green.

Note on vale

While here, I checked the vale advisory findings the linter now surfaces. It is 516 findings across ~70 files (SubstitutionWarning, NonStandardHyphens, LatinTerms, Possessive, FutureTense, ...), not a short list. Much of it is stylistic or domain-specific to public sector (via, airgapped, future tense). Mass-rewriting that prose is high-churn and low-value, which is why the job is advisory. Not addressed here; see the MR discussion for the recommendation (tune the ruleset vs leave advisory).

Draft for review.

Merge request reports