Skip to content

seo: point the Person node at kriskrug.co/#person - #211

Merged
WalksWithASwagger merged 2 commits into
mainfrom
claude/punkrockai-person-kriskrug
Sep 28, 2026
Merged

WalksWithASwagger merged 2 commits into
mainfrom
claude/punkrockai-person-kriskrug

Conversation

@WalksWithASwagger

@WalksWithASwagger WalksWithASwagger commented Sep 28, 2026 •

Copy link
Copy Markdown
Owner

Summary

  • punkrockai.com described Kris Krüg as a separate entity, https://www.punkrockai.com/#kris-krug. The canonical Person lives at https://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.
  • The home page's Person node keeps its name, url, sameAs and knowsAbout and takes the shared @id. The creator references on the WebSite, the CreativeWork, and the cut-up WebApplication follow it.
  • Two files, four lines, no copy changes.

Verification

  • npm run seo:index-hygiene: all index hygiene checks passed
  • npm run test:index-hygiene: 7/7 pass
  • node --test tests/cut-up.test.mjs: 10/10 pass
  • npm run eval: all eval checks passed
  • npm run docs:links:all: ok (158 files)
  • python3 -m pytest tests/agentic: 30 passed; check:python compiles
  • Every JSON-LD block on both pages still parses
  • Live https://kriskrug.co/ publishes Person @id https://kriskrug.co/#person ("Kris Krüg"), so the reference resolves
  • npm audit was not run for this change, which adds no dependencies
  • After deploy: https://www.punkrockai.com/ serves the Person with @id https://kriskrug.co/#person

Agentic Delivery

  • Linked with Closes #... only when every acceptance criterion is met (no issue; refs WalksWithASwagger/kk-kb#2027)
  • Acceptance self-check included when opened by an agent
  • Diff is within 20 files / 500 changed lines (2 files, 4 lines)

🤖 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 @id and all creator @id references (WebSite, CreativeWork) now point at the canonical https://kriskrug.co/#person. The cut-up widget’s WebApplication creator is updated the same way; visible copy is unchanged.

package-lock.json also refreshes the sharp tree (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.

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
@vercel

vercel Bot commented Sep 28, 2026 •

Copy link
Copy Markdown

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

Project Deployment Actions Updated
punkrockai Ready Ready Preview Sep 28, 2026 4:13pm UTC

Request Review

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

Copy link
Copy Markdown
Owner Author

The first eval run failed only at its last step. npm audit --audit-level=moderate flagged sharp <0.35.4 (high, GHSA-rgj7-g3m4-5g8c). Every test before it passed: index hygiene 7/7, agentic pytest 30/30, compile.

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: npm audit fix bumps only sharp and its @img/* platform packages, 0.35.3 to 0.35.5. package.json is unchanged, since its ^0.35.3 range already allows that. Locally the audit now reports 0 vulnerabilities, and the eval, index-hygiene, cut-up and doc-link checks still pass.


Generated by Claude Code

@WalksWithASwagger
WalksWithASwagger marked this pull request as ready for review September 28, 2026 16:16
@WalksWithASwagger
WalksWithASwagger merged commit 3bf0232 into main Sep 28, 2026
8 checks passed

@cursor cursor Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approved. Cursor Bugbot completed with no findings that need human review, and no approval policy requires extra review. No reviewers were assigned.

Open in Web View Automation 

Sent by Cursor Approval Agent: Pull Request Router and Approver

This branch was successfully deployed

1 active deployment
Preview — 21408570 Deployed Sep 28, 2026 by vercel[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants