feat!: generalize presets and migrate database

[ReenigneArcher]

Description

• Publish preset IDs as originating issue numbers and use consumer-neutral command fields. Steam and Epic Windows launches use direct URIs; Linux Steam uses setsid.
• Show launch commands on the site and provide Sunshine application JSON as an export.
• Keep preset and exported application names equal to the game or app name; show available methods on browse cards and method, host OS, and variant on preset cards. The issue check derives a descriptive title from validated metadata.
• Use the GameDB/ThemerrDB base-path fallback so production catalog requests resolve under /PresetDB while previews use the Jekyll base URL.
• Add a master-push migration workflow. It creates a backup branch from the current database commit, migrates the active database branch, and records applied migration IDs and backup metadata in database/migrations.json. Re-runs skip completed migrations.
• PR Pages builds apply pending migrations in a temporary checkout before producing the preview, without a database commit or push.
• Verified with 30 local tests, lint, diff checks, and a migration dry run against the current approved issue [STEAM GAME PRESET]: 007 First Light #4 record.

The published record format moves to schema version 2. The site and approval path read version 1 records during rollout; the migration workflow updates the stored database after merge.

Screenshot

Issues Fixed or Closed

Roadmap Issues

Type of Change

• feat: New feature (non-breaking change which adds functionality)
• fix: Bug fix (non-breaking change which fixes an issue)
• docs: Documentation only changes
• style: Changes that do not affect the meaning of the code (white-space, formatting, missing semicolons, etc.)
• refactor: Code change that neither fixes a bug nor adds a feature
• perf: Code change that improves performance
• test: Adding missing tests or correcting existing tests
• build: Changes that affect the build system or external dependencies
• ci: Changes to CI configuration files and scripts
• chore: Other changes that don't modify src or test files
• revert: Reverts a previous commit
• BREAKING CHANGE: Introduces a breaking change (can be combined with any type above)

Checklist

• Code follows the style guidelines of this project
• Code has been self-reviewed
• Code has been commented, particularly in hard-to-understand areas
• Code docstring/documentation-blocks for new or existing methods/components have been added or updated
• Unit tests have been added or updated for any new or modified functionality

AI Usage

See our AI usage policy.

• None: No AI tools were used in creating this PR
• Light: AI provided minor assistance (formatting, simple suggestions)
• Moderate: AI helped with code generation or debugging specific parts
• Heavy: AI generated most or all of the code changes

[codecov]

Codecov Report

❌ Patch coverage is 98.72881% with 3 lines in your changes missing coverage. Please review.
✅ Project coverage is 88.29%. Comparing base (b2cc72d) to head (8bb272b).
✅ All tests successful. No failed tests found.

Files with missing lines	Patch %	Lines
gh-pages-template/assets/js/app.js	96.10%	3 Missing ⚠️

Additional details and impacted files

@@             Coverage Diff             @@
##           master       #5       +/-   ##
===========================================
+ Coverage   75.33%   88.29%   +12.95%     
===========================================
  Files          10       12        +2     
  Lines        1103     1281      +178     
===========================================
+ Hits          831     1131      +300     
+ Misses        272      150      -122     

Files with missing lines	Coverage Δ
src/build-site.js	88.76% <100.00%> (+0.25%)	⬆️
src/database.js	95.23% <100.00%> (-0.73%)	⬇️
src/issue.js	96.15% <100.00%> (+37.26%)	⬆️
src/migrate-database.js	100.00% <100.00%> (ø)
src/presets.js	95.49% <100.00%> (ø)
src/record.js	100.00% <100.00%> (ø)
gh-pages-template/assets/js/app.js	64.45% <96.10%> (+48.38%)	⬆️

... and 1 file with indirect coverage changes

---

Continue to review full report in Codecov by Harness.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update b2cc72d...8bb272b. Read the comment docs.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud