fix(utils): correct misleading port-range comment in calculatePortOffset

[kuishou68]

Closes #1008

Problem

The inline comment in calculatePortOffset says ports will be in 3100-3999 range, but with basePort = 3090 the actual range is 3190-4089. This contradicts the comment and confuses developers reading the code.

Fix

Updated the inline comment to correctly state 3190-4089 range. The JSDoc above the function was already accurate.

Summary by CodeRabbit

• Chores
  • Improved internal documentation clarity for port allocation logic.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 2c538e53-29a1-4739-af2b-a4d4ef539e31

📥 Commits

Reviewing files that changed from the base of the PR and between 50f96f8 and 9f6b438.

📒 Files selected for processing (1)

• packages/core/src/utils/port-allocation.ts

---

📝 Walkthrough

Walkthrough

This change corrects a misleading inline comment in the calculatePortOffset function to accurately reflect the actual port range produced by the code (3190–4089 instead of 3100–3999), aligning it with the existing JSDoc documentation and the basePort value of 3090.

Changes

Cohort / File(s)	Summary
Port Allocation Comment Fix packages/core/src/utils/port-allocation.ts	Updated inline comment to accurately describe the resulting port range (3190-4089) when offset is added to basePort (3090), correcting the misleading range previously stated in the comment.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐰 Through the code warren I did hop,
Found a comment that made my ears flop!
3190 through 4089 rings true,
Not 3100's misleading view!
Truth and docs now both align,
My little nose twitches—all is fine! ✨

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately describes the main change: correcting a misleading comment about port range in the calculatePortOffset function.
Description check	✅ Passed	The PR description clearly explains the problem, the fix, and references the linked issue, though it lacks the structured template sections like validation evidence and security impact.
Linked Issues check	✅ Passed	The PR directly addresses issue #1008 by updating the inline comment to correctly state the 3190-4089 port range, aligning with the actual basePort value and existing JSDoc.
Out of Scope Changes check	✅ Passed	The changes are strictly scoped to updating the misleading inline comment in calculatePortOffset with no behavioral code modifications or unrelated alterations.
Docstring Coverage	✅ Passed	Docstring coverage is 100.00% which is sufficient. The required threshold is 80.00%.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ 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 and usage tips.}