Fix port matching false positive in server discovery

[jfox85]

Summary

• Fixes discoverServerName() using strings.Contains(addr, ":80") which would incorrectly match :8080, :8081, etc.
• Uses strings.HasSuffix instead for exact port matching
• Adds regression test for the :8080 false positive case

Follow-up to #25 based on CodeRabbit review feedback.

Test plan

• New test case: :8080 server is not matched, :80 server is correctly selected
• All existing tests pass

🤖 Generated with Claude Code

[coderabbitai]

Warning

Rate limit exceeded

@jfox85 has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 16 minutes and 47 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch jf-fix-port-matching

---

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