oc-repo-ops

原文涵盖的主题

• Repo Ops
• Command Reference
• Every-PR Gate
• /oc-repo audit
• /oc-repo verify
• /oc-repo clean
• /oc-repo catalog
• Checkpoint Integration

On first invocation, read references/orchestrator.md and follow its welcome protocol. Repo Ops is the repository-level cleanliness gate. It does not write the docs packet itself; Docs Forge does that. Repo Ops verifies that the packet exists, that repo state is clean enough to review, and that generated/catalog/source surfaces agree before Git Ops opens a PR. oc-git-ops must invoke Repo Ops before creating every PR. The required order is: 0. Precondition: Bug Check has already passed before every commit on the branch (oc-git-ops runs it before each commit, including a docs-packet commit). If it has not run, or its verdict is stale, chain back to oc-bug-check. 1. Docs Forge generates or verifies the PR documentation packet. 2. Repo Ops verifies repository cleanliness and docs packet presence. 3. Git Ops opens the PR only after Repo Ops passes. Repo Ops publishes a C-contract verification.verdict handoff for the evaluator's HEAD gittreeprojection (excluding .checkpoints/) under policy pr-readiness-v1, in the branch's own file .checkpoints/handoffs/pr-readiness-v1/ .json. Opchain's Git Ops flow and requested CI wiring consume it through scripts/lib/release-evidence.mjs; missing, stale

这里只展示节选，请以完整原文和当前要求为准。