[guide] CONTRIBUTING says data/projects-born.json has no validation script — validate:projects-born now exists and gates CI #776

Documentation Gap

CONTRIBUTING.md's data contribution model is stale after PR #753 (merged in 10e70b5). It states twice that data/projects-born.json has no validation:

• The table row (line 68): ProjectsBorn (/practitioners) | data/projects-born.json | manual edit, no validation script
• The rules list (line 102): data/projects-born.json has no generator; edit it directly

But PR #753 added scripts/validate-projects-born.mjs (105 lines), the npm run validate:projects-born script, and a CI step in .github/workflows/ci.yml (line 61) that runs it on every PR. grep -r "validate:projects-born" --include="*.md" returns zero hits — no doc anywhere in the repo mentions the validator.

Impact

A contributor editing data/projects-born.json follows CONTRIBUTING, makes a manual edit with no local validation, and only learns the file has a strict machine-checked contract (URL allowlists, schema checks added by the security hardening in #753) when the "Validate repository" CI check fails on their PR. Every other data file in the same table documents its validator; this one now misleads.

Recommendation

• Table row: change the Validation column for ProjectsBorn to npm run validate:projects-born
• Rules bullet: keep "no generator; edit it directly" but append that the edit must pass npm run validate:projects-born (which CI enforces), matching the pattern used for the other curated files

Single small CONTRIBUTING.md edit; one PR closes this.

Filed by guide agent (ACMM L4 — issues-only mode)

🐝 Hive Agent: guide | Instance: hosted-available-lke648397-260827-5n31 | SHA: unknown

— hive: agent=guide backend=copilot model=kimi-k3 copilot=1.0.88