[diegosouzapw]

Summary

Owner-authorized, narrowly scoped integration-workflow repair for the Relay closeout. This adds an opt-in queue for one precomposed, reviewed integration PR, not paid multi-PR batching.

• Require the exact owner, release target, reserved head branch and both approval labels.
• Preserve original contributor commits through merge for updates and landing.
• Exclude integration candidates from the ordinary squash queue, including when the second label is absent.
• Retain every existing merge condition and add affirmative Gate / CI and Gate / Quality; no timeout increase, failure allowance, bypass identity or subscription change.
• Document preparation, activation, attribution and exact-candidate readback.

Verification

Base: 6125870f548f417086030650280ad0a129c07498.
Head: 14be1dc2b11014e11eca43ba4f35213fbfbd260d.

• Contract RED before implementation: 3 expected new failures, 7 passes.
• Contract GREEN: 10/10, no skipped or cancelled tests.
• Focused ESLint, Prettier, git diff --check, npm run check:docs-all and normal commit hooks: PASS.
• check:docs-all retained 98 advisory drift warnings; its blocking checks passed.
• Matching-lock borrowed dependencies were used for these diagnostics; this is not clean-install/full release acceptance.

Activation HOLD

Mergify reads the default branch's configuration. This PR cannot activate its own queue. Service configuration acceptance and account availability still require verification. This change must first land under the existing policy; inherited base failures are not permission to bypass that bootstrap. No queue labels, original PR closures, repository-setting changes, direct release pushes or merges were performed.

The integration candidate does not exist yet. Its original PR heads, complete diff, ownership, contributor credit and all applicable current-candidate checks must be verified separately before admission.

References: configuration source and validation, merge strategies.

[mergify]

Merge Protections

🔴 1 of 2 protections blocking · waiting on 🙋 you

	Protection	Waiting on
🔴	🚦 Auto-queue	🙋 you
🟢	📃 Configuration Change Requirements	—

🔴 🚦 Auto-queue

Waiting for

• label = queue

This rule is failing.

When all merge protections are satisfied and these conditions match, this pull request will be queued automatically.

• label = queue

---

Show 1 satisfied protection

🟢 📃 Configuration Change Requirements

Mergify configuration change

• any of:
  • check-success = @mergify/Configuration changed
  • check-success = @mergify/Configuration has been deleted

[diegosouzapw]

Service validation readback for head 14be1dc2b11014e11eca43ba4f35213fbfbd260d:

• Mergify Configuration changed: SUCCESS, check run 116484838403.
• The service reports that the new configuration is valid and the remaining sections will be used after merge.
• It warns that Workflow Automation is not activated, so the existing pull_request_rules label-cleanup action will not run. No account setting was changed, and this warning does not turn configuration validation into proof of a completed integration merge.
• Mergify Merge Queue remains neutral/waiting; no queue label has been applied.

The activation/bootstrap HOLD remains: this PR still needs applicable exact-candidate checks under the existing default-branch policy. Neither this service check nor the 10 local contract tests authorize a red intermediate landing.

[github-actions]

CI Coverage Report

• Coverage job: skipped
• PR test policy: success

Coverage artifact was not available for this run.