Update to Spacefast

{
  "description": "Diagnose a failed Spacefast build, publish, or live page. Apply a fix supported by logs, or restore a known-good version when requested. Use when a deployment fails, stalls, or breaks existing behavior.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 211
    },
    {
      "relative_path": "references.md",
      "size_in_bytes": 24466
    }
  ],
  "name": "fix-deployment",
  "skill_md_contents": "---\nname: fix-deployment\ndescription: \"Diagnose a failed Spacefast build, publish, or live page. Apply a fix supported by logs, or restore a known-good version when requested. Use when a deployment fails, stalls, or breaks existing behavior.\"\n---\n\n# Fix or restore a deployment\n\nUse the connected Spacefast MCP tools. Sign-in is required. If the connection is unavailable, ask the user to reconnect in plugin settings.\n\nIf a task requires an existing Space and its identity is unclear, call `choose_space`. Use the selected Space as the target. A selection does not approve publishing or other changes.\n\nRead the MCP calls, approval, and work mode rules in [references.md](references.md) before a management operation.\n\n1. Open the affected Space's deployments view. Identify the failed build or version and its stable error code.\n2. Read **Diagnose and recover** in [references.md](references.md). Inspect the relevant logs before choosing a fix.\n3. Before a source change, read Team Memories and Skills in references.md. Retrieve applicable memories and follow the team's enabled skills.\n4. If source changes are needed, follow **Source edits**. Preserve the original error and verify the corrected behavior.\n5. Before publishing or deploying new or changed source, run the verify-design-system skill against current saved standards and the exact source/build being deployed. Inspect affected pages and states at desktop and mobile widths, and report gaps. Reuse verification only while the source/build and design revision are unchanged. Report missing standards as unavailable, not a pass. Verify before a source-workspace commit when autoDeploy is enabled. Follow the user's existing publication intent and approval rules.\n6. For a requested rollback, follow **Roll back safely**. Promote an existing ready version without rebuilding it.\n7. Verify the live pointer and the failing path. A saved commit or successful build alone does not prove recovery.\n"
}