Verify and validate Kusama parachain projects-info.json

[Copilot]

Confirms that networks/kusama/parachain/projects-info.json (introduced in the base branch) correctly implements the requirements referenced in the problem statement. No structural changes were needed — the file was already valid and complete.

Validation findings

• 30 Kusama parachain JSON files — all unique ParaIDs, no conflicts at slot 2000
• Correct schema — all required fields present (ParaID, Project Name, Website Link, Owner account, etc.)
• Network-specific values consistent across kusama, polkadot, and westend equivalents
• Owner account and signature intentionally empty — require parachain owner to sign via Polkadot.js Apps before merge

Checklist

• Use the owner account that submitted registrar_reserve to sign the project information, and fill in the signature.
• After each update of the project information, please sign the latest data and submit the signature.
• Add a description for your pr, the description includes the original data.
• Fill up the signature of the original data, signature account to Signature Auto check.

Signature Auto check

Para ID Owner & Signature Account:
<REPLACE THE OWNER>

Data that needs to be signed:
file

Signature Hash: <REPLACE THE SIGNATURE>