Update to ModRetro Chromatic Plugin

{
  "name": "modretro-chromatic-setup",
  "description": "Prepare missing game compiler or emulator dependencies for an installed ModRetro Chromatic plugin, or diagnose tools that cannot start.",
  "included_files": [],
  "skill_md_contents": "---\nname: modretro-chromatic-setup\ndescription: Prepare missing game compiler or emulator dependencies for an installed ModRetro Chromatic plugin, or diagnose tools that cannot start.\n---\n\n# Prepare game dependencies\n\nFollow the shared [agent guide](../../docs/agent-guide.md).\n\nCodex manages plugin installation and updates. A working plugin must not be\nrecreated, registered in another marketplace, or reinstalled to obtain a compiler.\nNever edit installed manifests, MCP configuration, receipts or plugin-cache files.\nDo not invoke Plugin Creator, register-personal-plugin, prepare-plugin-payload,\nor `codex plugin add` during game dependency setup.\n\n## Diagnose the failed step\n\nCall `toolchain_doctor` when available. Authoring/device tools, compiler dependencies,\nemulator dependencies, project selection and Developer Mode are separate.\nFor PROJECT_SELECTION_REQUIRED select the intended project; do not reinstall.\nFor missing compiler/emulator dependencies use the packaged commands below.\nIf MCP cannot start, report the concrete launcher error; do not manufacture a\nreplacement plugin. Codex must supply the initial Node executable.\n\n## Install only missing dependencies\n\nPrefer `toolchain_prepare {\"components\":[\"build\"]}` for missing compiler tools,\nor `[\"emulator\"]` for local play, or both. It plans and prepares dependencies\nwithout replacing the plugin. Show one concise progress update, then continue\nthe original build/preview after success. Inspect incomplete results before any\nretry; a refusal is not permission to switch callers.\n\nIf this tool is unavailable, use the exact Node executable and setup command returned by `toolchain_doctor`.\nThe installed self-contained package retains its own runtime. Even legacy\n`--components runtime,build` requests skip runtime replacement in this package.\n\n- Build or preview a game: `--components build`.\n- Play an existing ROM: `--components emulator`.\n- Build and playtest: `--components build,emulator`.\n- Add `desktop` only when the visual editor is requested.\n- Source editing or flashing an existing ROM needs no compiler setup.\n\nRun `node <installed-plugin>/scripts/setup.mjs plan --components build --json`,\nthen `apply --components build --yes --json`, then\n`doctor --components build --probes cli-version,gbdk-version --json`.\nSubstitute the exact executable/path and requested components; quote paths with\nspaces. On PowerShell prefix the quoted executable with `&`.\nA request to build/play includes necessary dependency setup; do not create an\nextra approval step. Preserve real access refusals and unresolved installer locks.\n\nUse the same stable dependency root for all commands. By default this is\n`~/Library/Application Support/modretro-chromatic` on macOS,\n`%LOCALAPPDATA%/modretro-chromatic` on Windows, and\n`${XDG_DATA_HOME:-~/.local/share}/modretro-chromatic` on Linux.\nThe launcher reads its `toolchain` subdirectory independently of plugin version.\nAn explicit GB_STUDIO_SETUP_ROOT selects another root; preserve configured roots.\nDo not silently repoint or overwrite an independently configured toolchain.\nReuse setup-owned components; never take over an unowned nonempty directory.\n\nAfter setup, continue the actual requested build in the same installed plugin.\nDo not follow legacy docs into local-payload generation or marketplace registration.\nVerify a real project build; metadata readiness alone is not completion.\n\n## Device activation and playtesting\n\nActivation is external: link to the official\n[ModRetro Updater](https://support.modretro.com/en_us/articles/chromatic-firmware-updater-ryhoYnzCx).\nNever collect activation codes or infer code validity from a generic write failure.\nUse the deployment skill for installation confirmation and unknown-write recovery.\n\nUse the built-in browser for previews unless the user explicitly selects another\nbrowser. When browser play is unavailable, use the exact ROM with the supported\nlocal emulator; see [stepped playtesting](../../docs/stepped-playtesting.md).\n"
}