Update to Gondwana

{
  "name": "debug-gondwana-game",
  "description": "Diagnoses and fixes Gondwana game, integration, and engine behavior using current source, tests, demos, and documentation. Use when the user reports a bug, failing test, rendering/input/collision/movement issue, unexpected lifecycle behavior, compilation problem, regression, or asks why Gondwana code is not behaving as expected.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 470
    }
  ],
  "skill_md_contents": "---\r\nname: debug-gondwana-game\r\ndescription: Diagnoses and fixes Gondwana game, integration, and engine behavior using current source, tests, demos, and documentation. Use when the user reports a bug, failing test, rendering/input/collision/movement issue, unexpected lifecycle behavior, compilation problem, regression, or asks why Gondwana code is not behaving as expected.\r\n---\r\n\r\n# Debug a Gondwana Game\r\n\r\nUse this skill to diagnose Gondwana behavior before proposing a fix.\r\n\r\nThe central question is: **which layer actually owns the problem?**\r\n\r\n## Establish current behavior\r\n\r\nFor a nontrivial problem:\r\n\r\n1. If the Gondwana MCP tools are available, call `get_repository_info`.\r\n2. Read `AGENTS.md` and `docs/ai/README.md`.\r\n3. Inspect the source named by the user or implicated by the symptom.\r\n4. Follow direct collaborators and lifecycle/ownership relationships.\r\n5. Search `Testing/Gondwana.Tests/` for the affected type or behavior.\r\n6. Inspect the closest current demo when the symptom is game-facing.\r\n7. Consult the relevant wiki page after understanding current code.\r\n\r\nTreat current source and tests as authoritative for current behavior. Use the wiki to understand intended design.\r\n\r\n## Classify the problem\r\n\r\nExplicitly determine whether the defect is primarily in:\r\n\r\n- the user's game code,\r\n- demo/sample code,\r\n- a public Gondwana API,\r\n- engine internals,\r\n- a platform adapter,\r\n- hosting/lifecycle integration,\r\n- widgets/input routing,\r\n- tooling/assets,\r\n- documentation that has drifted from current code.\r\n\r\nDo not change engine internals merely to make incorrect game usage appear to work.\r\n\r\n## Trace the relevant implications\r\n\r\nInvestigate only the cross-cutting areas that matter to the symptom, including:\r\n\r\n- initialization and attachment order,\r\n- engine-cycle versus frame-render timing,\r\n- event ordering,\r\n- world/layer/grid/screen coordinate conversion,\r\n- camera/view/viewport ownership,\r\n- dirty-region invalidation,\r\n- GPU full-viewport rendering,\r\n- collider registration and collision profile/mask resolution,\r\n- animation/frame-derived state,\r\n- serialization/deserialization,\r\n- caching/copying,\r\n- input polling, widget focus/capture, and hit testing,\r\n- dispatcher/thread affinity,\r\n- native/platform presentation,\r\n- disposal and resource ownership.\r\n\r\nDo not shotgun-edit all of these. Use the checklist to avoid missing a relevant coupling.\r\n\r\n## Fix discipline\r\n\r\nPrefer the smallest fix that restores the intended contract.\r\n\r\n- Preserve public behavior unless the task intentionally changes it.\r\n- Keep platform-specific fixes in the appropriate adapter/hosting package.\r\n- Do not force bitmap and GPU paths into artificial symmetry.\r\n- Avoid unrelated cleanup while fixing a regression.\r\n- Add a focused regression test when engine behavior changes.\r\n- Preserve an existing test unless the requested contract intentionally supersedes it.\r\n- If the documentation is stale but code/tests are correct, fix or flag the documentation rather than regressing the implementation.\r\n\r\n## Explain the diagnosis\r\n\r\nWhen reporting a fix, distinguish:\r\n\r\n1. **Observed behavior**\r\n2. **Root cause**\r\n3. **Why the proposed change belongs in this layer**\r\n4. **Other implications checked**\r\n5. **Regression coverage**\r\n6. **Anything still unverified**\r\n\r\nFor a patch request, generate an apply-ready focused patch instead of a prose-only list of edits.\r\n"
}