ranade-oss puts guardrails around automated PR merges

ranade-oss has tightened the verification gate that sits in front of automatic merges. The focus is not a new legal-AI feature, but a more dependable change-control process for a project that uses automated contributors.

• Automatic merging now waits for the baseline checks to pass and is limited to authorised contributors.
• Review checks now examine every unresolved discussion, not only the first batch GitHub returns.
• The gate waits for GitHub to settle uncertain merge-status results instead of acting on incomplete information.
• Bot and connector-created branches receive explicit verification, with failures surfaced rather than silently missed.

The pattern is tightly tied to this repository, but the underlying lesson is portable: automation needs its own audit trail and controls.