Add maintainer-approved compatibility report bot

[xnetcat]

What changed

• extend the compatibility issue form with test date, optional game version, and ownership confirmation
• add a hardened issue-form converter that validates catalog IDs, sanitizes submitted Markdown, handles regional aliases, and preserves source permalinks
• add a maintainer-gated GitHub Actions workflow that opens draft report PRs when compat-approved is applied
• display optional game versions in published compatibility reports
• document activation and maintainer review steps

Why

Compatibility submissions currently stop as issues and require maintainers to manually recreate their data as Markdown. The new flow keeps issues as intake records while automating the mechanical conversion into reviewable source changes. It never auto-merges or auto-approves a report.

Repository setup already completed

The compat-report, compat-approved, and compat-pr-opened labels now exist, and all four existing compatibility issues carry the neutral compat-report intake label.

The SharpEmu organization currently blocks Actions-created PRs for the built-in GITHUB_TOKEN. Before report conversion can open PRs, an organization owner must enable that policy or a fine-grained COMPAT_BOT_TOKEN repository secret must be added as documented in the README.

Validation

• npm test — 8 files, 52 tests passed
• npm run build — 8,716 pages built and Pagefind completed
• actionlint .github/workflows/compat-report.yml
• converter parsed issues PPSA07326 - The Dragon's Trapame Name #1, PPSA28068 - Mortal Kombat: Legacy Kollection #2, PPSA01342 - Demon's Souls #4, and PPSA08329 - God of War Ragnarök #5 successfully without publishing them

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.