Update to gstack Workflows

{
  "name": "freeze",
  "description": "Restrict requested edits to an explicitly named directory or scope.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 251
    }
  ],
  "skill_md_contents": "---\nname: freeze\ndescription: Restrict requested edits to an explicitly named directory or scope.\n---\n\n# Freeze\n\nPortable ChatGPT/Codex adaptation of the `freeze` 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 `freeze` 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. Establish the exact allowed scope and operation before mutation.\n2. Detect destructive, irreversible, credential, production, database, history-rewrite, or broad-delete actions.\n3. Require explicit confirmation for materially risky actions.\n4. Keep edits inside the agreed scope and stop on scope ambiguity.\n5. Verify the resulting state when the host provides the needed tools.\n\n## Completion\n\nReturn the decision, findings, changed artifacts if any, executed verification, skipped checks, and remaining blockers.\n"
}