Update to gstack Workflows

{
  "description": "Run end-to-end QA, fix authorized defects, and re-verify them when host tools permit.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 260
    }
  ],
  "name": "qa",
  "skill_md_contents": "---\nname: qa\ndescription: Run end-to-end QA, fix authorized defects, and re-verify them when host tools permit.\n---\n\n# QA\n\nPortable ChatGPT/Codex adaptation of the `qa` 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 `qa` 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. Define the user journeys and expected outcomes in scope.\n2. Use real browser, app, or execution tools when the host exposes them.\n3. Record reproducible failures with steps, evidence, and severity.\n4. If fixes are authorized, make focused changes and re-run the failing path.\n5. Run a small regression pass around each fix.\n6. Never claim a click, browser session, screenshot, or test run that did not occur.\n\n## Completion\n\nReturn the decision, findings, changed artifacts if any, executed verification, skipped checks, and remaining blockers.\n"
}