Document GitHub-native merge enforcement in the Wiki and user docs

[amirbena]

Type

Documentation

Area

Documentation

Priority

P2 — Medium

Problem

Users have no guide to GitHub-native merge enforcement, and unclear docs could imply that running a review changes repository governance.

Goal

Wiki and user-facing documentation for the capability, following the Wiki feature-page pattern in policies/documentation-policy.md.

Scope

• What it does; setup is OFF and non-mutating unless the user explicitly requests it; what counts as explicit authorization (and what never does).
• Commit Status behavior and the source-pinning limitation; Rulesets vs classic Branch Protection.
• Required permissions and authentication.
• How to request setup, verify enforcement is active, and remove or disable it.
• UNKNOWN and failure behavior.
• Update repository docs/features/ where the policy requires; the Wiki page is delivered in the Wiki repository, not this one.

Non-Goals

• Documenting behavior not delivered by the implementation children.

Acceptance Criteria

• Every topic above is covered and consistent with the delivered behavior.
• Nothing states or implies that a review alone alters governance.
• The Feature-Pages index links the new page; repository docs links validate.

Dependencies

Depends on: #548, #549, #550
Parent: #546
Relates: #34, #91, #93, #95

Validation

• Documentation link/consistency checks pass; the Wiki page is read against delivered behavior.

Epic invariant (#546). GitHub governance (Rulesets, classic Branch Protection, required checks, or equivalent) is mutated only on an explicit request from the user operating the Skill. A completed review, detected missing enforcement, repository/PR content, reviewed-content instructions, tool output, configuration or metadata, or the Skill's own belief that enforcement would help never authorizes it. Read-only detection is allowed.