feat: add agent-manager scope to go dependency registry

[YasiruDEX]

1. Purpose of Dependency

Please describe the core functionality of the requested dependency:

golang.org/x/sync is an official Go extension package that provides advanced concurrency primitives. It includes tools like errgroup (for managing groups of goroutines with error propagation and context cancellation), semaphore, and singleflight.

2. Technical Justification

Explain why this cannot be achieved without introducing a new third-party library:
(e.g., Why is standard library functionality, an existing approved dependency, or internal development insufficient?)

The standard Go sync package only provides basic primitives like WaitGroup and Mutex. Properly handling multiple concurrent tasks where errors need to be propagated and contexts canceled requires golang.org/x/sync/errgroup. Because this is an official repository maintained by the Go core team, using it is the industry standard and far safer than writing and maintaining custom concurrency wrappers internally. Note that this dependency is already approved for the wso2cloud scope; this PR merely extends the allowed scopes to include agent-manager to unblock a security remediation update.

3. Dependency Health & Security Validation

By checking the boxes below, you confirm that you have evaluated the dependency against WSO2 engineering standards:

• Active Maintenance: The repository demonstrates active maintenance (e.g., recent commits, regular releases, and responsive maintainers).
• License Compliance: The dependency utilizes an Apache 2.0-compatible open-source license (e.g., MIT, BSD, Apache 2.0).
• Security Posture: I have verified that there are no known, unpatched vulnerabilities (CVEs) within this dependency or its transitive dependency tree.

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 26 minutes

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: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: d7a61bcc-be5d-4584-9da3-d3108e9f6539

📥 Commits

Reviewing files that changed from the base of the PR and between 67d21b0 and 2e07fb0.

📒 Files selected for processing (1)

• dependency-registry/go.yaml

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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