Migration to referenced GUI menus

QuestCodex category menus reference an open_gui entry through menu. This removes repeated GUI blueprints, keeps generated editor schemas lighter, and avoids publication freezes on large pages.

Required migration

For every legacy category_menu:

1. Move guiType, audio, layoutPool, and mainLayoutId into a new open_gui entry.
2. Set menu on the category menu to the new entry ID.
3. Keep category, title, rows, and sortDisplay on category_menu.

The QuestCodex repository includes scripts/migrate_category_menus_v032.py for bulk page migration. Back up the pages and update QuestCodex and GUI together.

Public servers may keep old pages while preparing the migration, but new edits should be saved in the referenced GUI format.

Multi-tracking storage

For persistent multi-tracking, add a quest_codex_tracking_artifact entry in a static page and reference it from quest_codex.trackingArtifact.

Rules:

• use a generated UUID for artifactId;
• keep the same artifactId after release, otherwise existing tracked data is orphaned;
• keep storage in a static page when distributing example pages;
• use random Typewriter page filenames/top-level page ids for portable page bundles.