Update to Retro Game Gather

{
  "description": "Help the user choose what to play next from their Retro Game Gather (RGG) backlog. Use when the user asks what to play, wants to clear their backlog, has limited time tonight, or asks about games they planned to finish. Japanese triggers include 積みゲー, 次に何を遊ぶ, 何やろう, 今夜遊べる, 崩す, プレイ予定, クリア目標.",
  "included_files": [
    {
      "relative_path": "references/glossary-ja.md",
      "size_in_bytes": 8569
    },
    {
      "relative_path": "references/service-guide.md",
      "size_in_bytes": 8699
    }
  ],
  "name": "plan-next-game",
  "skill_md_contents": "---\nname: plan-next-game\ndescription: Help the user choose what to play next from their Retro Game Gather (RGG) backlog. Use when the user asks what to play, wants to clear their backlog, has limited time tonight, or asks about games they planned to finish. Japanese triggers include 積みゲー, 次に何を遊ぶ, 何やろう, 今夜遊べる, 崩す, プレイ予定, クリア目標.\n---\n\n# Choose the next game\n\nRGG stores the backlog; you make the suggestion. Base it on the user's data and say what it is based on.\n\nFor RGG concepts see `references/service-guide.md`; for Japanese terms see `references/glossary-ja.md`.\n\n## Where the backlog is\n\n1. **Planned games first.** getPlayRecords `statuses: [\"PLANNED\"]`. Users add games they intend to play here; it is the app's backlog.\n2. **Paused games** (`\"PAUSED\"`) are candidates for \"something to resume\".\n3. **Overdue goals.** `clearTargetOverdue: \"overdue\"` finds unfinished games past their clear target date.\n4. **The wider library** only when the above is empty or the user asks. First ask for a condition (platform, genre, era), then getLibrary with that filter and `fields` including `latestPlay`. Do not page through the whole library as a first step.\n\n## Reading the data correctly\n\n- PLANNED means \"intends to play\", not \"never played\". Check `hasHistory` and start dates.\n- A library game without a play record is \"not recorded\", not proof it was never played.\n- Present results as candidates from the user's records (登録情報上の候補).\n- If fewer candidates match than the user asked for, show the ones that match. Do not add games they do not own.\n\n## Making the suggestion\n\n- Ask one question if it helps: time available, mood, platform at hand.\n- Game length and style: use what you know or read from the game's `externalLinks` (see the find-games skill). Say when it is your estimate.\n- Keep the list short (three to five) with one line of reasoning each.\n\n## Next steps to offer\n\n- Start the chosen game, depending on its latest record (see the log-play skill):\n  - PLANNED or PAUSED: updatePlayRecord to PLAYING.\n  - No play record: addPlayRecord with `status: \"PLAYING\"`.\n  - COMPLETED, or DROPPED and the user wants to start over: this is a replay. Use addPlayRecord with `replay: true`, never updatePlayRecord — changing a finished record to PLAYING erases its end date and rating. On FREE and LIGHT a replay replaces the previous record and its logs; say so first.\n  - DROPPED and it is unclear whether the user wants to continue or start over: ask.\n- Set a goal: updatePlayRecord `clearTargetDate`.\n- Add a wanted game to the planned list: addPlayRecord (status defaults to PLANNED) for games already in the library.\n"
}