docs: empty the known-gaps section now that its entry is closed

[electrohyun]

Summary

Section C of differences.md still says smocket returns undefined from emit and the listener methods, and that socket.on('a', f).on('b', g) throws. #189 fixed both, so the page describes a gap that no longer exists and contradicts the suite, which now has 13 dual-run cases pinning the opposite.

The section stays and only its list is emptied. The rule it carries is worth keeping written down, and an empty list says something: no gap of this kind is known today. Deleting the heading would throw away the rule and mean rewriting it the next time one turns up. The entry that was here is named along with where its cases now live, so the history stays readable.

Related issue

No tracking issue. Follow-up to #189.

Checklist

• Tests added or updated. Documentation only. The behaviour this text described is already covered by src/emitter-returns.test.ts from fix: return the socket from the client emitters and true from the server ones #189.
• Behavior verified against real socket.io. No source change. Both targets stay at 191, and every relative link and anchor in docs/ still resolves.

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 35 minutes

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

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: CHILL

Plan: Pro Plus

Run ID: bf709b8a-9e0f-4c04-908d-d049fde82f96

📥 Commits

Reviewing files that changed from the base of the PR and between c15a274 and b38dc86.

📒 Files selected for processing (1)

• docs/differences.md

---

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