Update to Vibe Coding

{
  "description": "Audit, implement or verify a compatibility boundary through authorized reference behavior, file/protocol reconstruction, differential comparison and golden masters.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 238
    },
    {
      "relative_path": "references/compatibility-golden-master-check.md",
      "size_in_bytes": 900
    },
    {
      "relative_path": "references/reverse-engineering-audit.md",
      "size_in_bytes": 2746
    },
    {
      "relative_path": "references/reverse-engineering-polish.md",
      "size_in_bytes": 1535
    }
  ],
  "name": "vibe-compatibility",
  "skill_md_contents": "---\nname: vibe-compatibility\ndescription: \"Audit, implement or verify a compatibility boundary through authorized reference behavior, file/protocol reconstruction, differential comparison and golden masters.\"\n---\n\n# Compatibility & protocols\n\nRead [the shared workflow](../../references/workflow.md) once per task, then the one recipe matching the requested operation and boundary. Do not load every recipe. The user's request controls scope and whether edits are allowed.\n\n## Recipes\n\n| Recipe | Operation |\n|---|---|\n| [Compatibility Golden Master Check](references/compatibility-golden-master-check.md) | check |\n| [Reverse Engineering Audit](references/reverse-engineering-audit.md) | audit |\n| [Reverse Engineering Polish](references/reverse-engineering-polish.md) | implement |\n\nFor an explicit multi-stage request, follow the necessary stages without discarding requested work. For a single stage, deliver that result and stop. Use [the catalog](../../references/catalog.md) only if the requested boundary belongs elsewhere.\n"
}