fix(data): regenerate stale anchor metadata, sitemap, and llms.txt

[raifdmueller]

Summary

Several anchors (kano-model, double-diamond, hoshin-kanri, kotter-8-step-change-model, decisional-balance-sheet and others — 15 in total) were added as .adoc files without rerunning extract-metadata.js, so the committed data files drifted out of sync.

Production was unaffected — CI runs extract-metadata.js, generate-sitemap.js and generate-llms-txt.js before building, so the deployed site always regenerates these. The staleness only affected the committed copies (which npm run dev reads directly) and made the repo misleading to read.

Regenerated anchors.json, categories.json, metadata.json, roles.json, sitemap.xml and llms.txt. anchors.json now holds all 147 anchors.

Root cause / prevention

The website prebuild chain runs sync-anchors + render-docs + render-contracts but not extract-metadata. Only the root build and CI run it. So adding an anchor and running just the website build leaves the committed data files stale. A pre-commit hook or adding extract-metadata to the website prebuild would prevent recurrence — out of scope for this PR, flagging for a follow-up.

Test plan

• npm run build succeeds
• All newly-surfaced anchors appear in the card grid and search on the live site
• sitemap.xml and llms.txt list the full anchor set

🤖 Generated with Claude Code

[coderabbitai]

Warning

Rate limit exceeded

@raifdmueller has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 31 minutes and 53 seconds before requesting another review.

You’ve run out of usage credits. Purchase more in the billing tab.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yml

Review profile: CHILL

Plan: Pro

Run ID: 3552b469-5841-429d-9718-a6707f35d308

📥 Commits

Reviewing files that changed from the base of the PR and between 0a15aa1 and 100dfc5.

📒 Files selected for processing (6)

• website/public/data/anchors.json
• website/public/data/categories.json
• website/public/data/metadata.json
• website/public/data/roles.json
• website/public/llms.txt
• website/public/sitemap.xml

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}