oc-docs-forge

原文涵盖的主题

• Docs Forge
• Command Reference
• Every-PR Contract
• /oc-docs pr
• /oc-docs readme
• /oc-docs standardize
• /oc-docs upkeep
• /oc-docs verify

On first invocation, read references/orchestrator.md and follow its welcome protocol. Docs Forge turns a code change into the documentation that must travel with it. It owns the content, wording, placement, and freshness checks for PR bodies, PR comments, README/catalog docs, product docs, ADRs, changelog notes, and linked ticket summaries. Boundary: Docs Forge writes and verifies documentation. Repo Ops decides whether the repository is clean enough to open the PR. Git Ops creates the branch, commit, push, and PR after these gates pass. Every PR must contain Docs Forge output in at least one visible surface: 1. The PR body, for normal documentation packets. 2. A PR comment with marker , when the documentation packet is too long for the body. 3. Both the body and a comment, when the body needs a compact summary and the comment carries migration notes, screenshots, large tables, or generated docs. The PR body must always include a ## Documentation section. If no user-facing documentation changed, say so explicitly and explain why. Silence is not a pass. Read references/pr-documentation-packet.md before generating or verifying PR documentation. Inputs: git diff --stat and changed fil

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