Update to gstack Workflows

{
  "description": "Regenerate native iOS debug bridge artifacts only on a compatible local host.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 254
    }
  ],
  "name": "ios-sync",
  "skill_md_contents": "---\nname: ios-sync\ndescription: Regenerate native iOS debug bridge artifacts only on a compatible local host.\n---\n\n# iOS Sync\n\nPortable ChatGPT/Codex adaptation of the `ios-sync` workflow from `garrytan/gstack`. Preserve the original job and safety intent while mapping execution to capabilities the current host actually exposes.\n\n## When to use\n\nUse this Skill when the user explicitly names `ios-sync` or asks for the same job described above.\n\n## Host contract\n\n- Inspect repository or file evidence before making claims about the current state.\n- Use host-native read, list, search, grep, patch, write, shell, browser, computer, and Python capabilities only when they actually exist.\n- Never claim commands, tests, browser actions, device actions, file writes, Git operations, or external mutations that were not executed.\n- Prefer read-only discovery before mutation.\n- Respect repository instructions and preserve unrelated work.\n- When the original native gstack runtime is available in Codex, it may be used as an implementation detail after inspecting the installed upstream Skill. Do not hard-code Claude-only paths as a requirement.\n\n## Workflow\n\n1. Detect whether the host has the required local iOS tooling, project, and device/simulator access.\n2. Inspect the exact target and current bridge/configuration before changing anything.\n3. Use real device or simulator evidence for QA claims.\n4. Keep modifications scoped and reversible.\n5. If compatible tooling is unavailable, provide analysis or setup guidance only and label execution as unavailable.\n\n## Completion\n\nReturn the decision, findings, changed artifacts if any, executed verification, skipped checks, and remaining blockers.\n\n## Surface note\n\nThis workflow is published for Codex discovery because its full behavior depends on a local runtime, device, browser session, or credential-aware command environment. ChatGPT can still discuss the workflow, but must not claim native execution.\n"
}