Update to Yes2SDK

{
  "description": "Adds Yes2SDK to a Unity, Defold or JS project and confirms it resolves. Use before writing Yes2SDK code, when setting up or onboarding a project, or when a Yes2SDK reference will not compile.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 193
    }
  ],
  "name": "yes2sdk-install",
  "skill_md_contents": "---\nname: yes2sdk-install\ndescription: Adds Yes2SDK to a Unity, Defold or JS project and confirms it resolves. Use before writing Yes2SDK code, when setting up or onboarding a project, or when a Yes2SDK reference will not compile.\n---\n\n# Installing Yes2SDK\n\nInstall comes before code on Unity and Defold. `Yes2SDK` (Unity) and the `yes2sdk`\nmodule (Defold) do not resolve until the package is added, so code written first\ndoes not compile and the failure reads as a coding error. JS is different, see the\nfirst precondition.\n\n## Routing order\n\n1. `yes2sdk:detect_sdk` reports the engine and the install state. This replaces\n   asking the user which engine they are on, and replaces guessing from the file\n   tree.\n2. `yes2sdk:get_install_instructions` for that engine, when an install is still\n   required. The steps it returns are version-pinned; use them as returned rather\n   than a remembered install procedure.\n\n## Preconditions\n\n- **`installed: no` is a blocker on Unity and Defold only.** On a JS project it is\n  the expected and permanent state: there is no dev-time package, because the web\n  runtime is injected into the build by the dashboard at upload time. Blocking there\n  blocks every JS project forever. Read the report, not just that line.\n- `yes2sdk:detect_sdk` takes exactly one of two input modes, and the wrong one is\n  the most common way this fails. This plugin registers the **hosted** server, which\n  has no disk access. Read the engine-marker files locally and pass them inline as\n  `files` (repo-relative path to contents). `projectPath` there returns an error\n  result, not a thin answer; pass it only when the user runs the server on their own\n  machine.\n- **Unity needs two markers, not one:** `Packages/manifest.json` *and* a\n  `ProjectSettings/` file (`ProjectSettings/ProjectVersion.txt` will do). With only\n  one, detection returns `Engine: unknown` and every downstream step is wrong.\n  Defold needs `game.project`; JS needs `package.json`.\n- Read those markers from the project ROOT. Detection keys off root-level files;\n  markers picked up from a subfolder identify the wrong engine or none.\n- The engine passed to `yes2sdk:get_install_instructions` comes from\n  `yes2sdk:detect_sdk`. Do not pass an engine the user merely mentioned in passing.\n- Yes2SDK targets HTML5/WebGL only. On a non-web target the modules are no-op\n  stubs, so an install that looks fine still produces no platform behaviour.\n\n## Failure modes worth naming\n\n- Detection reporting an engine but no install is the normal state on a fresh Unity\n  or Defold project. Treat it as the install path, not an error.\n- A project that already has a platform SDK (Poki, CrazyGames, and so on) wired\n  directly is not \"already integrated\". Yes2SDK replaces those direct calls, and\n  leaving both wired double-fires ad and lifecycle events.\n- After installing, re-run `yes2sdk:detect_sdk` before generating code. An install\n  that needs an editor step (Unity package import plus its WebGL template, Defold\n  library fetch) is not complete when the manifest edit lands.\n"
}