seo: point the Person node at kriskrug.co/#person - #211
Conversation
punkrockai.com described Kris Krüg as its own entity, https://www.punkrockai.com/#kris-krug. kriskrug.co publishes the canonical Person at https://kriskrug.co/#person. bothhandsfull.com and darkcrystal.app already point there (bothhandsfull#157, dark-crystal#178). With a separate id here, search engines see a fourth, unlinked identity for one person. The Person node on the home page keeps its name, url, sameAs and knowsAbout, and takes the shared @id. The WebSite, CreativeWork and cut-up WebApplication creator references follow it. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01VrmRgcezNQxvH6hcDWgAW8
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
npm audit now fails the eval gate on sharp <0.35.4 (high, GHSA-rgj7-g3m4-5g8c: libheif GHSA-g89c-p67h-r497 and GHSA-2jg2-4ch7-h545). The advisory is newer than main's last green eval run on 2026-09-06, so every PR fails the gate until the lockfile moves. `npm audit fix` changes only the lockfile: sharp and its @img platform packages go from 0.35.3 to 0.35.5 (libvips 1.3.2 to 1.3.4). The package.json range ^0.35.3 already allows it. npm audit then reports 0 vulnerabilities, and eval, index hygiene, cut-up tests and doc links still pass. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01VrmRgcezNQxvH6hcDWgAW8
|
The first This isn't the schema change, which touches no dependency. The advisory is newer than main's last green eval run on 2026-09-06, so any PR fails the gate until the lockfile moves. I brought the fix in here as a separate commit: Generated by Claude Code |


Summary
https://www.punkrockai.com/#kris-krug. The canonical Person lives athttps://kriskrug.co/#person: kriskrug.co publishes it live, and bothhandsfull.com and darkcrystal.app already point there (WalksWithASwagger/bothhandsfull#157, WalksWithASwagger/dark-crystal#178). This is the last site in the kk-kb SEO/AEO audit of 2026-09-27 (recommendation 13) that still split the identity.name,url,sameAsandknowsAboutand takes the shared@id. Thecreatorreferences on the WebSite, the CreativeWork, and the cut-up WebApplication follow it.Verification
npm run seo:index-hygiene: all index hygiene checks passednpm run test:index-hygiene: 7/7 passnode --test tests/cut-up.test.mjs: 10/10 passnpm run eval: all eval checks passednpm run docs:links:all: ok (158 files)python3 -m pytest tests/agentic: 30 passed;check:pythoncompileshttps://kriskrug.co/publishes Person@idhttps://kriskrug.co/#person("Kris Krüg"), so the reference resolvesnpm auditwas not run for this change, which adds no dependencieshttps://www.punkrockai.com/serves the Person with@idhttps://kriskrug.co/#personAgentic Delivery
Closes #...only when every acceptance criterion is met (no issue; refs WalksWithASwagger/kk-kb#2027)🤖 Generated with Claude Code
https://claude.ai/code/session_01VrmRgcezNQxvH6hcDWgAW8
Generated by Claude Code
Note
Low Risk
SEO-only JSON-LD identifier changes plus a patch-level dev dependency lockfile update; no runtime auth or data-path changes.
Overview
Aligns structured data so Kris Krüg is no longer a site-local Person (
https://www.punkrockai.com/#kris-krug). The home page JSON-LD Person@idand allcreator@idreferences (WebSite, CreativeWork) now point at the canonicalhttps://kriskrug.co/#person. The cut-up widget’s WebApplicationcreatoris updated the same way; visible copy is unchanged.package-lock.jsonalso refreshes thesharptree (0.35.3 → 0.35.5) and matching@img/sharp-*/ libvips optional packages—likely from a lockfile regen, not application logic.Reviewed by Cursor Bugbot for commit 2140857. Configure here.