docs: require needs-go-port for deferred Go ports

[Wibias]

Summary

• Lock the needs-go-port label into MAINTAINERS.md for deferred Go ports during the Transition phase.
• Mirror the label name in the AGENTS.md Transition summary (authoritative wording stays in MAINTAINERS).

Existing rule already required a tracking issue against dev2-go naming source commits; this makes the durable triage signal part of policy.

Test plan

• Read the Transition bullets in MAINTAINERS + AGENTS for consistency
• Confirm label needs-go-port still exists on the repo

[coderabbitai]

Warning

Review limit reached

@Wibias, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 29 seconds

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: bd67ecf3-7773-429f-b462-845f1f88955b

📥 Commits

Reviewing files that changed from the base of the PR and between f0867e8 and 23ff099.

📒 Files selected for processing (2)

• AGENTS.md
• MAINTAINERS.md

---

_{Comment @coderabbitai help to get the list of available commands.}

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: f743bf6f6c

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Add the new label to the transition summary

When a maintainer relies on the repository's AGENTS.md transition summary, the deferred-port workflow still says only to open an issue and name the source commits, so following that documented workflow produces an unlabeled issue and defeats the durable triage signal introduced here. Update that summary to require needs-go-port as well, as the commit description intended, so the two policy surfaces do not prescribe different completion criteria.

AGENTS.md reference: AGENTS.md:L66-L72

Useful? React with 👍 / 👎.

[Wibias]

Codex P2 is already addressed in 23ff099 (AGENTS Transition summary requires needs-go-port). First-commit-only review.