fix(site): starlight 0.42 removed tagline, so the config that set it stops the build

[keyurgolani]

fix(site): starlight 0.42 removed tagline, so the config that set it stops the build

Dependabot's grouped npm bump (#61) carries @astrojs/starlight 0.41.10 -> 0.42.0, and 0.42.0
removes the top-level tagline option outright. Starlight validates its config strictly, so an
unrecognised key is a hard error rather than a warning: astro sync — the first thing all three
site jobs run — dies with

[AstroUserError] Invalid config passed to starlight integration
  Hint: Unrecognized key: "tagline"

which reds "Static build and publication contract", "Lighthouse performance budgets" and
"Browser, accessibility, privacy, and visual regression" together, plus the Vercel deployment.
Three red jobs and one failed deploy, all one unrecognised key.

The upstream entry (withastro/starlight#3572) is explicit about the migration: "Removes the
tagline configuration option, which was never used" — no replacement, safe to delete. So the
sentence this repo had been setting there ("Generated from the tagged source this site was built
from.") rendered NOWHERE on 0.41 either. Deleting the key changes no pixel, and the comment in
its place says that, plus where the fact belongs if it is worth surfacing: page content, not a
key the framework ignored.

Verified in the order that makes it evidence rather than hope: reproduced the CI failure locally
FIRST (astro sync exit 1, same "Unrecognized key" hint) against the bumped lockfile, then
applied the deletion and re-ran.

• astro sync exit 0; npm run build 43 pages, exit 0.
• npm run test:static exit 0 — 5 marketing routes + 33 docs pages + registry index + 2 blog +
  1 compare validated, 117 research cross-links resolved, registry render contract verified.
• npx playwright test 139 passed — including the visual-regression suite against the
  committed darwin baselines, so the lucide-react 1.37 -> 1.41 and astro/react bumps riding
  along change no rendered pixel. That was the live risk in taking this group.
• node scripts/lighthouse-audit.mjs exit 0 — performance/accessibility/best-practices/seo 100
  on every audited route.

npm audit --audit-level=moderate exits 1 with 6 vulnerabilities (1 moderate, 5 high:
browserslist, fast-uri, js-yaml, nanoid, postcss, undici). Measured against main's lockfile
under the same command: byte-for-byte the same six. This bump introduces none of them — they are
pre-existing transitive debt and want their own change, so they are reported here rather than
folded in silently or used as a reason to hold the fix.

Why no screenshot: the deleted key rendered nothing on either version — upstream removed it
as "never used" — and the visual-regression suite passing against unchanged baselines is the
stronger evidence that the page is identical.

Closes #61

Signed-off-by: Keyur Golani keyurrgolani@gmail.com

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
personalclaw	Ready	Preview	Sep 8, 2026 9:15pm UTC