Add symlink script and update package.json with symlink command

[brionmario]

Purpose

Adds a symlink script to the repository and registers the corresponding symlink command in package.json. This is needed to support local cross-package linking within the monorepo during development and migration workflows (branch: migrate).

Approach

• Added a dedicated symlink script (e.g. scripts/symlink.js or similar) that creates filesystem symlinks between packages in the monorepo.
• Registered the script as a symlink npm command in the root package.json so it can be invoked via pnpm run symlink (or equivalent) during local development setup.
• No changes to package exports, build output, or public API.

Related Issues

• N/A

Related PRs

• N/A

Checklist

• Followed the contribution guidelines.
• Manual test round performed and verified.
• Documentation provided. (Add links if there are any)
• Tests provided. (Add links if there are any)
  • Unit Tests
  • Integration Tests
• Breaking changes. (Fill if applicable)
  • Breaking changes section filled.
  • breaking change label added.

Security checks

• Followed secure coding standards in WSO2 Secure Coding Guidelines
• Confirmed that this PR doesn't commit any keys, passwords, tokens, usernames, or other secrets.

[coderabbitai]

Warning

Review limit reached

@brionmario, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 52 minutes and 16 seconds. Learn how PR review limits work.

Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file).

⌛ How to resolve this issue?

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 credits.

🚦 How do rate limits work?

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

For paid Pro and Pro+ PR reviews, CodeRabbit uses rolling per-developer review limits. Reviews become available again as older review attempts age out of the rolling limit window.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: a6d5681b-fc78-4a0b-83e0-7a6cf23bb7cb

📥 Commits

Reviewing files that changed from the base of the PR and between 93ec0fd and 33ca096.

📒 Files selected for processing (3)

• CONTRIBUTING.md
• package.json
• scripts/symlink.js

✨ 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.}

[Malith-19]

Suggested change

	* Copyright (c) 2025, WSO2 LLC. (https://www.wso2.com).
	* Copyright (c) 2026, WSO2 LLC. (https://www.wso2.com).

[brionmario]

Missed this, will fix in a followup PR.