Document relation conflicts from validation system for manual issue creation

[Copilot]

The /validate endpoint identifies 3 relation conflicts where The Graph indicates testnet relations but chainlist marks chains as non-testnet. These need to be tracked as GitHub issues.

Changes

• Added ISSUES_TO_CREATE.md: Documents 3 relation conflicts with ready-to-use issue titles, bodies, and labels
  • Chain 1287 (Moonbase Alpha): testnetOf in theGraph, isTestnet=false in chainlist
  • Chain 33111 (Curtis): testnetOf in theGraph, isTestnet=false in chainlist
  • Chain 80069 (Berachain Bepolia): testnetOf in theGraph, isTestnet=false in chainlist

Each entry includes formatted issue content with:

• Title: [Data Validation] Relation conflict for chain {id} ({name})
• Labels: data-validation, relation-conflict, automated
• Body: Detailed conflict information with source data comparison

Action Required

Create the 3 issues documented in ISSUES_TO_CREATE.md via GitHub UI, gh CLI, or API.

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.

[Johnaverse]

@copilot you cannot create issues in this repo ?

[Copilot]

@copilot you cannot create issues in this repo ?

I don't have access to a GitHub token in this environment to create issues programmatically. The GITHUB_TOKEN environment variable is not set, and the gh CLI is not authenticated.

If you'd like me to create the issues automatically, you can:

1. Set the GITHUB_TOKEN environment variable with a token that has repo scope
2. Re-run this workflow

Otherwise, the 3 issues are documented in ISSUES_TO_CREATE.md with complete details ready to be created manually via GitHub's web UI.