Update to Frontier Infra

{
  "description": "Inspect, plan, apply, verify, or audit the Maintainer Gate Blueprint for multi-agent repositories that need governed issue/PR intake, clean promotion lanes, handoff evidence, deterministic CI gates, and operator validation.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 226
    }
  ],
  "name": "maintainer-gates",
  "skill_md_contents": "---\nname: maintainer-gates\ndescription: Inspect, plan, apply, verify, or audit the Maintainer Gate Blueprint for multi-agent repositories that need governed issue/PR intake, clean promotion lanes, handoff evidence, deterministic CI gates, and operator validation.\n---\n\n# Adopt Maintainer Gates\n\nRead `../../references/threat-model.md` when defining destructive-command and cross-tenant controls.\n\n## Workflow\n\n1. Inspect the target repository before writing anything. Identify its package manager, test/lint/typecheck commands, branch and release policy, CI system, production-risk commands, and existing contributor instructions.\n2. Prepare a manifest from the Blueprint's example. Keep policy and generated paths specific to the target repository.\n3. Generate and review a project-specific manifest. Before applying, show the target paths and any CI or hook files it will create or change.\n4. Locate or provision the Maintainer Gate Blueprint before applying it. Prefer the target repository's documented vendored path or a checked-out `frontier-infra/Maintainer-Gate-Blueprint` repository. If `bin/apply-blueprint.mjs` is not present at the selected Blueprint root, stop with that prerequisite instead of invoking a plugin-local path.\n\n   ```sh\n   test -f <blueprint-root>/bin/apply-blueprint.mjs && node <blueprint-root>/bin/apply-blueprint.mjs <manifest.json>\n   ```\n\n5. Review every generated policy and command pattern against the actual repository. Tighten placeholders; do not ship generic production guards as if they were verified.\n6. Run the Blueprint checks, target lint/typecheck/tests, gate allow/deny fixtures, handoff validation, and PR-intake validation.\n7. Report separately: agent-read instructions, deterministic local hooks, CI gates, promotion/operator gates, and remaining manual controls.\n\n## Rules\n\n- Keep implementation work separate from clean dev/release reconstruction.\n- Use commit/file evidence rather than branch names as truth.\n- Never claim an operator validation or production outcome that has not occurred.\n- Do not enable destructive production-command blocks without first confirming their patterns against the target environment.\n"
}