Repository navigation
perf(registry): scope page profile payloads - #610
Conversation
🤖 MERGED
GitHub merged this pull request.
babca450-1a38-490c-b46e-88da77daad57 Selected findings run after merge and open separate pull requests. |
|
🤖 Agent checks by Codex, using Harlan Agent Kit's PR workflow. Production Anthropic profile replay: 116 Skills in the full profile, 20 in the scoped Repository profile. Serialized JSON fell from 128,746 to 18,783 bytes. The Owner projection retains all 116 Skills at 109,526 bytes. These figures measure profile JSON, not total HTML or Google indexing impact. Headless browser check: navigated from the Anthropic Owner page to its Skills Repository and back. Both pages retained seven local fixture cards, their canonical links, and run controls. Waited for each destination heading after client navigation. The live evidence is sampled. Recheck NuxtSEO action |
There was a problem hiding this comment.
Harlan Agent Kit posted this automated review. AI open source policy.
Automated Review: READY.
🔗 Linked issue
Related NuxtSEO action:
01M4BXGA14G6G789MPVJ3Q3XBK. Recheck the affected pages after deployment.❓ Type of change
📚 Description
Repository pages serialized every Skill from their Owner, including fields their cards never render. Each page now projects its profile before Nuxt serializes it. Repository pages keep their own Skills and calculate missing-path recovery before removing unrelated Skills.
Replaying the production Anthropic profile reduces serialized profile JSON from 128,746 to 18,783 bytes for its Skills Repository, an 85.4% reduction. The Owner profile falls to 109,526 bytes, a 14.9% reduction. Cards retain their canonical links, sorting dates, provenance, and dependencies.