Update to AI SPACE

{
  "description": "Diagnose a Cafe24 AI SPACE deployment that failed, a site that returns an error or will not open, or a connector that reports an authorization error. Use when the user says the build failed, the page is blank or 500, the database will not connect, uploaded files disappeared, or a tool call keeps failing. Do not use for a first deployment that has not been attempted yet.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 608
    },
    {
      "relative_path": "references/failure-catalog.md",
      "size_in_bytes": 4712
    }
  ],
  "name": "troubleshoot-deploy",
  "skill_md_contents": "---\nname: troubleshoot-deploy\ndescription: Diagnose a Cafe24 AI SPACE deployment that failed, a site that returns an error or will not open, or a connector that reports an authorization error. Use when the user says the build failed, the page is blank or 500, the database will not connect, uploaded files disappeared, or a tool call keeps failing. Do not use for a first deployment that has not been attempted yet.\n---\n\n# Diagnose a failed deployment\n\n**Read the evidence before you change anything.** Most failures here have a\nknown cause, and a blind retry costs the user one of a limited number of builds.\n\nReply in the user's language.\n\n## The stop rule comes first\n\nIf the same call has already failed the same way twice, do not call it a third\ntime. Stop, report what you saw, and work out the cause with the user.\n\nNever treat an authorization error as a code problem. Fixing code will not fix\nauthentication, and you will burn build quota discovering that.\n\n## Step 1 — Gather\n\n1. `get_project_status` — is the state `success`, `failed`, or still building?\n   Note the `runtime` and the `source` field.\n2. `get_project_logs` — the build and runtime log. This is where the real cause\n   is. Read it before forming a theory.\n3. `site_verify` on the project URL if the deployment reports success but the\n   user says the page does not load.\n\nDeployment success and site reachability are two different things. Check them\nseparately.\n\n## Step 2 — Match against the known causes\n\nWork through `references/failure-catalog.md`. In order of how often each one is\nthe actual answer:\n\n1. A `Dockerfile` or `docker-compose.yml` in the repository\n2. The app bound to `127.0.0.1`, or to the wrong port (Node must use 3000,\n   Python 8000, both on `0.0.0.0`)\n3. `DB_USERNAME` used instead of `DB_USER`\n4. A missing entry file at the repository root, so the runtime was misdetected\n5. A dependency that fails to install, or a syntax error — visible in the log\n6. Files written outside `/app/user_data/`, so they vanished on redeploy\n7. Memory exhausted during the build\n\n## Step 3 — Explain, fix, redeploy once\n\nTell the user what the log actually said, in plain language, before proposing a\nfix. Then make the change and redeploy **once**. If it fails again for a\ndifferent reason, repeat this workflow. If it fails again for the same reason,\nstop.\n\nBefore any redeploy of an existing project, check `source` with\n`get_project_status`:\n\n- `source: \"internal\"` → `project_upload` with `update: true`, then\n  `update_project`\n- `source: \"github\"` → `external_repo` with `repo_update` or `repo_write_file`\n\nCalling the wrong one returns `SOURCE_MISMATCH`.\n\n## Authorization errors\n\nIf a tool call returns an authorization or re-authorization error, this is not a\ndeployment problem and there is nothing to fix in the code.\n\nTell the user to reconnect the AI SPACE plugin in ChatGPT's settings and sign in\nto their Cafe24 account again. Do not send them to a login page inside the\nproduct — the connector's own authorization flow is what needs to run.\n\nAfter two consecutive authorization failures, stop and report rather than\nretrying.\n\n## The build failed but the site still works\n\nThat is expected. A failed build leaves the previous version running. The user\nhas not lost their live site — say so, because the failure message alone reads\nas though everything is down.\n\n## What you cannot do here\n\nRollback, project deletion and power control are not available through this\nconnector. If recovery needs one of those, direct the user to the Cafe24 web\nconsole: Hosting → My Service Management → AI SPACE console.\n\n## Do not infer\n\nBuild quotas, plan limits and retention periods change. Do not quote numbers from\nmemory — point the user to `https://aispacedocs-docs.mycafe24.ai`.\n"
}