generate-mock-beatoraja-data

Generate mock beatoraja SQLite databases by creating songdata.db, scoredatalog.db, score.db, and scorelog.db files with deterministic play records, clear lamps, and EX score components in /tmp/mock-beatoraja for overlay and dashboard testing.

Beatoraja mock test data includes eight deterministic sha256 song identifiers, scorelog events, minBP and combo values, clear-lamp updates, and gzip-compressed .bmt difficulty table files for testing personal-best detection.

Yes, mock beatoraja data produces an idempotent output directory at /tmp/mock-beatoraja suitable for CI fixtures and integration testing of frontends, requiring only sqlite3 and python3 to generate databases and compressed table files.

Create .bmt table cache files by generating gzip-compressed difficulty table data for eight deterministic songs, producing files that allow overlays and dashboards to display difficulty information without a running beatoraja instance.

No, generating beatoraja test data does not require a running instance because the skill directly creates SQLite database files and .bmt table files using sqlite3 and python3, populating today's play timestamps automatically.

Mock beatoraja data outputs to a fixed /tmp/mock-beatoraja directory path, includes only eight deterministic songs, and sets play timestamps to the current time, meaning generated score logs may not reflect long-term historical play patterns.