Update to gstack Workflows

{
  "name": "setup-deploy",
  "description": "Inspect a repository and establish deployment configuration guidance without inventing provider details.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 295
    }
  ],
  "skill_md_contents": "---\nname: setup-deploy\ndescription: Inspect a repository and establish deployment configuration guidance without inventing provider details.\n---\n\n# Setup Deploy\n\nPortable ChatGPT/Codex adaptation of the `setup-deploy` 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 `setup-deploy` 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. Inspect current configuration and operational state.\n2. Identify provider-specific facts from repository evidence rather than guessing.\n3. Prefer reversible changes and preserve existing deployment conventions.\n4. Execute checks only through available host tools.\n5. Report what changed, what was observed, and what still needs a compatible runtime.\n\n## Completion\n\nReturn the decision, findings, changed artifacts if any, executed verification, skipped checks, and remaining blockers.\n"
}